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
[RC Feedback] Feedback on the 1.8.0rc1 Release Candidate #4452
Comments
Upon update the pi comes back up and now I get a 500 error and cannot access the GUI at all. |
Please try a shift reload in case that is some weird caching issue. If that doesn't help, please submit a full bug report. |
Had one instance update fine, had another instance not do so well with the following when I try to manually start octoprint via
|
What were you doing?
What did you expect to happen?a successful upgrade What happened instead?an unsuccessful upgrade and a 500 error on the web GUI Did the same happen when running OctoPrint in safe mode?Tested in safe mode and thing appear to work as expected. It is indeed a 3rd party plugin crashing it. I know you dont want plugin bugs here, but maybe with it being an RC you do. Version of OctoPrint1.8.0 Printer model & used firmware incl. versionRaise 3D Pro2 Plus Browser and version of browser, operating system running browserdebian desktop and windows 10 System Info Bundleincluded. Im not sure how to figure out what plugin is crashing the non-safe mode boot. octoprint-systeminfo-20220314124301.zip I have read the FAQ. Bundles: edited by @github-actions to add bundle viewer links |
Octo Boot Log Error: |
Y'all, may I remind you of:
And this sounds like what @jneilliii already saw. In any case I need more details because I went through all of these plus two local installs and three further tests this morning without any issues at all: |
This issue has been mentioned on OctoPrint Community Forum. There might be relevant details there: https://community.octoprint.org/t/new-release-candidate-1-8-0rc1/42911/6 |
Temperature display not scaling properly Bundles: edited by @github-actions to add bundle viewer links |
That sounds about right.
That is expected behaviour and has been like this since forever. OctoPrint doesn't keep a full temperature history but only up to a cutoff point, by default 30min.
Define "froze" and "restart of the UI". Browsers these days pretty aggressively limit the processing allowed by background & out of focus tabs, which is why OctoPrint also pauses processing if not in foreground, so that would explain "freezing". Stuff should pick up again once you refocus the tab however. If it didn't and you can reliably reproduce this behaviour -> full bug report please (though in all likelihood that would not be a regression but rather some rare bug that's been in there for a long time). |
Thank you for the response. Still testing, latest issue is gcode viewer has stopped syncing. I will see if I can reproduce it after this print finishes and will submit a bug report if it does. |
This sounds like a general break in communication between your browser and the server, so possibly network problems or an overzealous browser. |
Same problem using Chrome browser on PC and also Chrome on a Pi 4 and on my Android tablet. Webcam is running smoothly with no jerks so network is fine. When this print is finished I will reboot everything and try again. I didn't reboot after the upgrade to 1.8.0 RC so maybe something is unhooked. |
Please also roll back to 1.7.3 and verify the issue does not arise there as well. |
I have to go out now but I have rolled back to 1.7.3 and everything worked. I re-upgraded to 1.8.0 RC, restarted in safe mode and problem returned. I restarted normal mode and checked that problem is same as in safe mode. |
FYI, 1.8.0rc2 might not happen today after all as another bug was found this morning and I just found another issue with the new settings layer while attempting to run update tests. Will have to see how long it takes to fix that. |
@mod38 please open a full bug report as well, this slipped my mind because I didn't have a ticket for it. Bug reports are THE most important part of an RC phase. |
Bug report on gcode viewer now submitted. |
That was a tough nut, but for now everything reported has been fixed. However, it's almost 6pm here, so way too late for a release tonight. I'll update the changelog, prepare the release announcement and then see I can push out rc2 tomorrow. Hopefully this time without any hiccups along the way. |
I REALLY dislike the "refresh" idea. it adds pointless clicks
before: I could switch on the printer (from the menu, by GPIO) - then just click "connect" To mitigate: Another feedback from 1.7.3 stable, I got the option to update to this RC and to update the "marlin flasher" plugin. |
If you had read the release notes, you would have seen this: "This behaviour can be disabled by setting serial.ignoreEmptyPorts to true in config.yaml."
PortLister plugin.
Your scare quotes are unnecessary and out of line. This was added after spending a lot of time helping users who were completely lost because they didn't notice their printer wasn't even being recognized by the underlying OS, causing excessive roundtrips during support and frustration on all sites. This will help a TON here.
I'm not familiar with what the marlin flashed plugin does, but if it managed to somehow override the reload dialog (there are options for that for certain workflows), I could see this happening. I haven't seen any behaviour like this in tests with stock (incl. bundled plugin updates), all prompted for reload properly. If this is reproducible in any way, I'll need a full bug report. |
1.8.0rc2 has been released, new feedback ticket is #4457 |
Please provide general feedback on your experience with the 1.8.0rc1 Release Candidate here. An "All is working fine" is valuable feedback as well, because it tells me that people in fact are testing the RC and just not finding any problems. Thanks :)
If you run into any obvious bugs not yet listed below the following line, please open a new ticket and follow "How to file a bug report". I need full bug reports, not just a statement that something doesn't work!
Update test matrix
✔ = expected to work, ❌ = expected to fail, ☑ = successfully completed. Releases aren't rolled out unless all tests in the update test matrix succeed.
Currently known issues
Unreproduced issues
Unreproduced and information for further analysis missing
Third party issues
Issues needing analysis
The text was updated successfully, but these errors were encountered: