Quinn Damerell

If you’re issue is with the ADO pipeline, they have updated the main bug being tracked here: https://github.com/microsoft/azure-pipelines-agent/issues/3834#issuecomment-1325638361 Good news, they have an update that will move to dotnet 6,...

Oh man, well thanks for letting me know @ColdBeer72! Oddly, the issue seems to be even worse than an out-of-sync clock; the clock seems to always re-sync itself to the...

Thanks @crysxd! I have seen issues like this before, and it's usually due to the WebSocket lib being outdated. Typically I don't enforce a version in the plugin, because OctoPrint...

@Hollywood25201 @Smasher350 can you open a supper ticket with me so we can debug it? https://octoeverywhere.com/support

It seems to be a problem with an update to the websocket-client lib. https://github.com/websocket-client/websocket-client/issues/857 OctoPrint's deps for websocket-client bind it to: `"websocket-client>=1.2.1,

Ah ha, I think I might have a work around! I just pushed a change to master of my plugin that forces the `websocket-client` lib to stay under 1.4.0, which...

No problem! I'm glad it worked and thanks for testing for me!

I think for now we can close this. The only other thing to do would be to get OctoPrint to also avoid the 1.4.x, but I'm not sure if it's...

Thanks for the tag @jneilliii. If I'm reading this correctly, the issue here is that when the log system is used a lot, the result might be a bug? OE...

Oh, I c. That's also a good reason to reduce it. Are there no rolling log limits or anything in OctoPrint?