-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Metadata pre-processing doesn't work with gcode files containing whitespaces in their filenames. #5008
Comments
Thanks! Weird that this didn't show up so far... In any case, I have merged your fix (:+1:) and also backported it to |
Update on this issue. I left my octoprint running for 2 days and the strangest things started to happen with my octoprint installation. My fix did work for me then, but it started acting weird today. My monkeypatched version started faulting in another area: the quotes passed to sarge weren't stripped in the call to .metadata.json now
I am really confused by this, as the script is not runnable from the console by entering |
I also missed during review that this already was passing the command as an array. Note how it doesn't use I have no idea why it originally failed for you, but from the code it already did the right thing (and I have no clue why I missed that during the PR review - the past few weeks were a bit stressful however, so I'll chalk it up to that). As it looks like there never was an actual bug here (at least not as far as we both can currently see), I'm closing this, but comments are still possible should you have any updates! |
Now that you say it, you are totally right and I am a complete fool. It is already being passed to I will keep a tighter watch on my installation the next time around, should I re-encounter it. It's just so strange and I wish I could roll back to before the re-installation to track down the real culprit. First the .metadata.json wasn't filled and afterwards the empty default set was always used. |
Don't worry about it, mistakes happen :) |
The problem
When uploading a gcode file containing a whitespace, the metadata processor won't be able to execute the octoprint analysis code. E.g. I tried printing a file called
CFFFP_medium paint palette.gcode
(from Cura):/usr/local/bin/python -m octoprint analysis gcode --speed-x=15000 --speed-y=15000 --max-t=10 --throttle=0.0 --throttle-lines=100 --bed-z=0.0 /octoprint/octoprint/uploads/CFFFP_medium paint palette.gcode
This fails with the following error:
Expected result (I added the missing quotes manually):
Did the issue persist even in safe mode?
Yes, it did persist
If you could not test in safe mode, please state why ("currently printing" is NOT an excuse!)
No response
Version of OctoPrint
1.10.0
Operating system running OctoPrint
Linux - Raspberry Pi OS Lite (64-bit)
Printer model & used firmware incl. version
No response
Browser and version of browser, operating system running browser
No response
Checklist of files to include below
Additional information & file uploads
Systeminfo Bundle:
octoprint-systeminfo-20240505121238.zip
GCODE file used:
CFFFP_medium paint palette.zip
I already intend on creating a pull request for the problem, as it is relatively easy to fix.
The text was updated successfully, but these errors were encountered: