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.

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.0rc5 Release Candidate #3450

Open
foosel opened this issue Feb 11, 2020 · 9 comments
Open

[RC Feedback] Feedback on the 1.4.0rc5 Release Candidate #3450

foosel opened this issue Feb 11, 2020 · 9 comments

Comments

@foosel
Copy link
Owner

@foosel foosel commented Feb 11, 2020

Please provide general feedback on your experience with the 1.4.0rc5 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

  • #3394 comm port autodetection still broken - appears to not be a regression and will get a closer look in 1.4.1

Unrelated third party issues

Issues needing analysis

@CRCinAU

This comment has been minimized.

Copy link

@CRCinAU CRCinAU commented Feb 11, 2020

Installed ok.. Can confirm anonymous login (ie login disabled) works ok. Test print started ok.

No obvious issues straight up...

@Demigod001

This comment has been minimized.

Copy link

@Demigod001 Demigod001 commented Feb 12, 2020

All is working fine. running on 2 pi's. Login issues gone. Thanks for the hard work

@MatejSpindler

This comment has been minimized.

Copy link

@MatejSpindler MatejSpindler commented Feb 13, 2020

Auto detecting a serial port is broken. See my comment on #3394
Once connected everything running as it should, no problems.

@schnello

This comment has been minimized.

Copy link

@schnello schnello commented Feb 14, 2020

So far no problems yet.
Klipper with SKR 1.1 Pro (Ubuntu Server)
4 Prints (24h)

@CRCinAU

This comment has been minimized.

Copy link

@CRCinAU CRCinAU commented Feb 14, 2020

Ok - so noticed an issue that I'm not sure is related to the RC or not...
I have a rather large P buffer in Marlin (128) - when I'm waiting for the printer to reply, I sometimes get the 'printer timed out' message - as the default timeout seems to be 3 seconds for printers that support BUSY...

Once the printer has timed out once, it seems OctoPrint will stop sending commands AFTER a temperature autoreport is received from the printer until the P buffer is empty. There's a slight stutter, then OctoPrint starts sending commands again and fills the P buffer again - until the next temp auto-report.

If it never hits the initial timeout, this doesn't seem to happen.

You can easily reach the timeout by doing long lines at slow speeds - this doesn't seem to be dependent on the buffer size - but by how long a single line takes to print.

Is this new behaviour related to any change, or am I just coming across this now?

@stantond

This comment has been minimized.

Copy link

@stantond stantond commented Feb 16, 2020

Which branch holds 1.4.0rc5? I'd like to build a new plugin in Python 3 against it, but as someone just getting into this, I'm struggling - I can't spot any info on which branch to clone, and the branches themselves don't identify which version they currently represent (although all of them state the current stable release).

@fieldOfView

This comment has been minimized.

Copy link
Contributor

@fieldOfView fieldOfView commented Feb 16, 2020

The release candidates are in rc/maintenance, but if you want to check out that specific rc, you can also check out the 1.4.0rc5 tag.

@stantond

This comment has been minimized.

Copy link

@stantond stantond commented Feb 16, 2020

Perfect, thanks!

The release candidates are in rc/maintenance, but if you want to check out that specific rc, you can also check out the 1.4.0rc5 tag.

Perfect, thanks! https://community.octoprint.org/t/towards-python-3-and-octoprint-1-4-0/12382 suggests using the devel branch, so maybe could use an update regarding advice for testing plugins.

@fieldOfView

This comment has been minimized.

Copy link
Contributor

@fieldOfView fieldOfView commented Feb 16, 2020

devel and maintenance are currently in sync. This is where the development happens. After OctoPrint 1.4.0 is released, development that will eventually be in OctoPrint 1.4.1 will go into maintenance, work towards OctoPrint 1.5.0 will go into devel. But because @foosel is working hard on OctoPrint 1.4.0 and no further work is going to be put into OctoPrint 1.3.x, devel and maintenance are currently the same.

When a new rc is released, maintenance is merged into rc/maintenance. The latter is more stable than the former.

When a new stable version is released, rc/maintenance is merged into master. By that time, rc\maintenance has been extensively tested.

The forum topic is still correct. devel can work on Python 3. But so can rc\devel, rc\maintenance, and maintenance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
7 participants
You can’t perform that action at this time.