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.4.0rc1 Release Candidate #3347
Comments
Installed on my Ubuntu 18 Server System with Klipper has FW. >> Installation OK and System is running. Later i perform some prints. Edit: octoprint_fanspeedslider doesnt work anymore.
Edit2: First print ok |
hello @foosel ,
|
Basic functionality tested with Pi3+ and sharebot NG (rumba+merlin) "All is working fine" with Python 2.7. We need to test it also with Py 3.x?? Bye! |
The same for filamentmanager |
Same problem here, file upload with the API seems broken with Python 3. |
@gferon @devildant please open a full bug report, I cannot reproduce this right now and need more data. Uploading through the UI (exact same API endpoint) works. @sebaminguez @schnello I can reproduce that and it's caused by a Python3 compat change plus those plugins still using deprecated methods. Looking into it. |
Update to that, I've since been able to reproduce it and it seems that missing optional headers in the upload request are the reason here. I've pushed a fix.
|
Now it's fixed. |
@foosel awesome! I deep diving in the code but my python skills were not enough :D |
Potential time-lapse issue with new libx264 - see #3353 |
@schnello Created a ticket for that in #3357 @JohnOCFII analysed and fixed, thanks! |
I'm having a problem loading javascript in the 1.4.0rc1 and the latest staging/devel branch as well. here is my console output:
I've tried with both python 2.7 and 3.7, and in the latest release versions of Chrome, Firefox and Firefox Development Edition. Let me know if you need any additional info. |
Ok, I figured it out, but I have no idea how this was caused. According to this issue, the mime types per extension on a windows machine are stored within the registry. Somehow this got changed to text/plain. Since it was working fine before upgrading to Python 3.7 and 1.4.0rc1, I believe it must have had something to do with the switch to python 3.7. I don't see how OctoPrint could be responsible for this in any way. Please disregard my previous comment since it is windows specific and seemingly unrelated to V1.4.0rc1. |
1.4.0rc2 is out. |
Please provide general feedback on your experience with the 1.4.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".
Currently known issues
Unreproduced issues
Unreproduced and information for further analysis missing
Unrelated third party plugin issues
The text was updated successfully, but these errors were encountered: