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.

Sign up for GitHub

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

Jump to bottom

Error 500 when uploading a new file after latest update #126

Closed
5jplusa opened this issue Mar 7, 2020 · 18 comments
Closed

Error 500 when uploading a new file after latest update #126

5jplusa opened this issue Mar 7, 2020 · 18 comments
Labels
type: bug Something isn't working

Comments

@5jplusa
Copy link

5jplusa commented Mar 7, 2020 •
edited
Loading

on the last 2 updates I get error 500 when uploading new files, the only way to correct is to roll back to previous version
@5jplusa
Copy link
Author

5jplusa commented Mar 7, 2020

on the last 2 updates I get error 500 when uploading new files, the only way to correct is to roll back to previous version

@OllisGit
Copy link
Owner

OllisGit commented Mar 7, 2020

Hi @5jplusa ,

what version of OP und DLP do you use?
What python version do you use?
Please attach the octoprint.log and also the gcode you receive the 500er error.

Olli

@OllisGit OllisGit added status: analysing status: waitingForFeedback Wating for Customers feedback labels Mar 7, 2020
@5jplusa
Copy link
Author

5jplusa commented Mar 18, 2020

OctoPrint 1.4.0 running on OctoPi 0.16.0

octoprint.log.2020-03-16.log

@5jplusa
Copy link
Author

5jplusa commented Mar 18, 2020

currently using DisplayLayerProgress Plugin (1.17.1) and upload is working perfect.

@5jplusa
Copy link
Author

5jplusa commented Mar 18, 2020

Filament Guide - Gold.gcode.zip
here is a sample Gcode that would cause the error

@OllisGit
Copy link
Owner

Hi @5jplusa ,

I am a little bit confused: Is it's now working with 1.17.1?
btw. current Version 1.18.1
I can't see any errors in the logfile that is affected to DLP.

@5jplusa
Copy link
Author

5jplusa commented Mar 20, 2020

Do you want me to reinstall 1.18.1 and send you the log file after trying to upload a file?

@5jplusa
Copy link
Author

5jplusa commented Mar 20, 2020

updated to latest version and still cannot upload. attached are the log files and the gcode
plugin_DisplayLayerProgress_events.log
octoprint (3).log
Filament Guide Wire Keeper.gcode.zip

@5jplusa
Copy link
Author

5jplusa commented Mar 20, 2020

reverted back to 1.17.1 and it is working again, attached are the logs after reverting back to 1.17.1
octoprint (4).log
plugin_DisplayLayerProgress_events (1).log

@OllisGit OllisGit added status: inNextRelease Will be implemented/fixed in next release type: bug Something isn't working and removed status: waitingForFeedback Wating for Customers feedback status: analysing labels Apr 6, 2020
OllisGit added a commit that referenced this issue Apr 8, 2020
@OllisGit
Change to async gcode processing
6341392 
Bugs
#134, #124, #128, #131, #127, #126
Enhance
#132 State-Section
101, #117 option to deactivate adding M117 layer-indicators
@OllisGit
Copy link
Owner

OllisGit commented Apr 8, 2020

Hi @5jplusa,
it is fixed in the newest release V1.19.0! Was a unicode-issue.

Please test and give feedback.

Thx, in advance
Olli

@OllisGit OllisGit added status: waitingForTestFeedback and removed status: inNextRelease Will be implemented/fixed in next release labels Apr 8, 2020
@gmag11
Copy link

gmag11 commented Apr 9, 2020 •
edited
Loading

Hello, I'm getting same error with 1.19.0 with OctoPrint 1.4.0
octoprint.log
plugin_DisplayLayerProgress_events.log

Disabling DisplayLayerProgress upload can be done normally

@OllisGit
Copy link
Owner

Hi @gmag11,
I could reproduce the error. It is related to Python 3.

I think you also use some messages that use not "normal characters" (sorry to say, I have no other translation for that).
Like

b'M117 Priming Filament\xe2{\xa6\n'

To verify this, please attach your gcode that throws the 500er error.

Thx, in advance
Olli

@OllisGit
Copy link
Owner

@5jplusa question: Are you "Korsisch-Speaking" ?
Because if I use google translate for M117 Priming Filamentâ the result is Korsich for Filament

@OllisGit OllisGit mentioned this issue Apr 10, 2020
Closed
@ax42
Copy link

ax42 commented Apr 10, 2020

Same issue here - Octoprint 1.4.0, Python 3.6. Disabling the plugin allows normal operation. Uploading from PrusaSlicer or uploading from the OctoPrint UI both give error 500.

@OllisGit
Copy link
Owner

Hi @ax42,
please attach your gcode so that I am able to reproduce the error.

@ax42
Copy link

ax42 commented Apr 10, 2020

Fails on any file. Here is one.

jst_0.15mm_PLA_MK3S_3m.gcode.zip

OllisGit added a commit that referenced this issue Apr 10, 2020
@OllisGit
#126 Python3 encoding during lineprocessing could not handle latin/fr…
8a66dbe 
…ench letters
OllisGit added a commit that referenced this issue Apr 10, 2020
@OllisGit
#126 Python3 encoding during lineprocessing could not handle latin/fr…
659d8b4 
…ench letters
OllisGit added a commit that referenced this issue Apr 10, 2020
@OllisGit
#126 correction for python2 and improved error logging
c0526a6
@OllisGit
Copy link
Owner

Hi @ax42 ,
thanks for the gcode, this was really helpful!

I just released version 1.19.1 this should fix the error. I tested with Py2/3.

Please test and give me a feedback!

@ax42
Copy link

ax42 commented Apr 11, 2020

Worked for me, thanks.
Moot now, there was something I hadn't written here -- I didn't need to disable the plugin to get rid of the error message, I only needed to unclick the "add clayer indicators during upload".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ax42 @gmag11 @OllisGit @5jplusa