-
-
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
Autoreport settings failure #2780
Comments
I am also experiencing the same problem while trying to change settings on that page, like:
Running OctoPrint 1.3.9 on OctoPi 0.15.1. Also tried in safe mode and the problem remains. The following error occurs in the Octoprint log:
Looking at some previous issues with the similar error (TypeError: got an unexpected keyword argument), I verified that I am running sarge 0.1.4 (as far as I can tell):
|
I'm having the same issue, except it happens upon booting the pi. This system worked great until a few weeks ago until I shut it down and unplugged to move to a new location. Today, I get it set up in the new location and power on, and nothing will work. Once the pi boots, it gives only 500 errors after a 60 second delay. Investigation show this happen in the log during startup.
Nothing changed from what was working a few weeks ago. When booting, I did see github called, so it is possible it downloaded a new patch? |
@Carpedraconis that is not the same issue. Your's looks like your file system got corrupted. Never just pull power on the Pi, always shut it down properly first. |
I'm a Linux admin, I know better. I'm getting the same python code error
on the same line as the other entries.
…On Mon, Aug 13, 2018, 2:42 AM Gina Häußge ***@***.***> wrote:
@Carpedraconis <https://github.com/Carpedraconis> that is *not* the same
issue. Your's looks like your file system got corrupted. Never just pull
power on the Pi, always shut it down properly first.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2780 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ARnLRWEkqiIa4rF4Fo2tQPMOp0w30Y7dks5uQR_lgaJpZM4Vu6WJ>
.
|
@Carpedraconis this issue is about what looks to be a keyword issue inside OctoPrint's code, triggered when attempting to save one of the timeout options in the settings dialog. Your issue is about some mangled data inside the webasset cache triggered when attempting to access the UI. That's not even close "the same python code error". |
Same line of code, same file, same stack trace puts both issues in the same
part of the code. I completely removed the web cache and rebooted the pi
(so it would rebuild) and the problem persists. So no, it's not a "user
screwed up the cache" issue.
…On Wed, Aug 15, 2018, 3:35 AM Gina Häußge ***@***.***> wrote:
@Carpedraconis <https://github.com/Carpedraconis> this issue is about
what looks to be a keyword issue inside OctoPrint's code, triggered when
attempting to save one of the timeout options in the settings dialog. Your
issue is about some mangled data inside the webasset cache triggered when
attempting to access the UI. That's not even close "the same python code
error".
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2780 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ARnLRQQickcrLjCRBMqVT6t-0pwCacWVks5uQ89HgaJpZM4Vu6WJ>
.
|
I didn't say anything about "the user screwed up", is said it looks like some corrupt cached file. The stack trace from the OP:
and the stack trace from @kazibole
Your stack trace:
How is this the same file, the same line of code, the same endpoint, the same traceback, the same anything? It's not the same source file, it's not the same call that led to it, it's completely unrelated to this ticket. I'm not saying this isn't an issue or that you are who caused it, but it has nothing to do with this ticket here. Please open another ticket, include all required information (full logs, reproduction steps, etc) so this can be looked into properly. |
I think the confusion here is that python dumps its tracebacks in the opposite order than is common for other languages (i.e. C/C++). As a primarily C/C++ developer, this was a point of confusion for me when I first started looking at python tracebacks. If you're a C/C++ developer, your eye automatically goes to the first function listed when comparing tracebacks instead of the last function as is produced by python. |
@ManuelMcLure That's my impression as well. I have a couple of languages under my belt and am aware how much such differences can throw one off. But if I'm not familiar with a language, and someone who is tells me that I'm misinterpreting a traceback, then I listen the first time instead of doubling down, becoming passive aggressive and potentially misleading others, complicating the situation further 🤷 |
Fixed by the above commit, already available on |
thanks ! 👍 |
When it's time to push out a first RC for 1.3.10, for which I don't have a date yet ;) |
Hmmm...running 1.3.9 (stable) and get the same error when trying to change the timeouts: |
It will be fixed in 1.3.10. |
Thanks, @kazibole - I was confused by the „solved“ tag of this issue. |
i got this problem but i cant read the sd card to get the logs because i broke my sd card reader |
What were you doing?
Changing the temperature autoreport interval in the settings from 2 to 5 or 10
What did you expect to happen?
Save and close the settings without errors. auto report interval change to 5s (M155 S5)
What happened instead?
Settings stay open.
This error occur in the log:
Did the same happen when running OctoPrint in safe mode?
Yes
Version of OctoPrint
1.3.9
Operating System running OctoPrint
Linux Octopi 0.15.0
Printer model & used firmware incl. version
Tevo Tornado, Marlin bugfixes-2.0.x
It fail with tornado connected or not.
Browser and version of browser, operating system running browser
Link to octoprint.log
Link to contents of terminal tab or serial.log
Link to contents of Javascript console in the browser
Screenshot(s)/video(s) showing the problem:
I have read the FAQ.
The text was updated successfully, but these errors were encountered: