Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError in continuous mode during gcode file processing #19

Open
e77 opened this issue Jan 30, 2021 · 3 comments
Open

TypeError in continuous mode during gcode file processing #19

e77 opened this issue Jan 30, 2021 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@e77
Copy link

e77 commented Jan 30, 2021

When octoprint process a very large gcode file to be ready for print (this one is 52.8mb) there appears to be an overflow error.

Continuous mode works fine until you either attempt to start the print, or you load the gcode viewer.
It's at this point that the layer count is generated, along with the expected print time. 582 layers, approx 7 hours in this particular case.

Doesn't happen with smaller files - still testing, but so far anything over 40mb causes the error output below:


Traceback (most recent call last):
  File "/home/pi/.local/bin/octoprint-cli", line 11, in <module>
    load_entry_point('octoprint-cli==3.2.2', 'console_scripts', 'octoprint-cli')()
  File "/home/pi/.local/lib/python3.7/site-packages/octoprint_cli-3.2.2-py3.7.egg/octoprint_cli/__main__.py", line 669, in main
  File "/home/pi/.local/lib/python3.7/site-packages/octoprint_cli-3.2.2-py3.7.egg/octoprint_cli/__main__.py", line 91, in continuous
  File "/home/pi/.local/lib/python3.7/site-packages/octoprint_cli-3.2.2-py3.7.egg/octoprint_cli/api.py", line 68, in getTotalTime
TypeError: unsupported operand type(s) for //: 'NoneType' and 'int'

@e77 e77 added the bug Something isn't working label Jan 30, 2021
@hexadecimalDinosaur hexadecimalDinosaur self-assigned this Jan 30, 2021
@hexadecimalDinosaur
Copy link
Owner

Thanks for the notice, I haven't run into this issue in the past (though that's probably because I only do relatively small prints). It appears that the OctoPrint API does not supply a value for estimatedPrintTime while files are being processed based off the information you have provided me. I will try to recreate this issue myself and look at the API data. What version of OctoPrint are you using?

@PitBarber
Copy link

I had same error yesterday, seems to be when you press "start at upload" in your favourite slic3r... if you upload the file and press print later at octoprint server error doesn't appear.

@hexadecimalDinosaur
Copy link
Owner

Yeah, I have run into this error myself once. It seems that the server sends incomplete API data when its processing files. I need to try to trigger this issue for testing and make a catch for this incomplete API data.

@hexadecimalDinosaur hexadecimalDinosaur changed the title TypeError: unsupported operand type(s) for //: 'NoneType' and 'int' TypeError in continuous mode during gcode file processing Apr 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants