jhaagmans

I second this. Also, I really like that there is a documented upgrade path to 2.x but I was unable to find documentation about these breaking changes in 2.1.

You've entered an interesting realm here! So, ruby is actually doing a very sensible thing here, although I agree with your comment about readability. Consider the classic `0.1 + 0.2`...

Oh that is a good point, I wasn't considering a case where you'd use current_time for calculations in sonic pi itself. I believe the "bug" you found is more related...

Wow, I messed up. I've used 2 similar plugins, the other one is temando/serverless-openapi-documentation for which my previous comment was relevant (I removed the comment). This plugin is obviously not...

Unfortunately, this project is dead and broken. PR #27 fixes this, but was rejected because the maintainers don't use this plugin anymore. You could patch your local plugin with the...

Could this be just a simple race condition? I believe Sonic Pi uses some kind of mutex pattern to synchronise information between threads, but this also means the order of...

Considering Sam's response in that thread, I'd say this is expected but not intended behaviour at this time. So yes, that explains it perfectly, thanks. In a normal language you'd...

@jenaber27 could you look at the logs in `~/.sonic-pi/log/`? I'm not sure these issues are related.

I read "Automatic start of JACK server is disabled at configure time". Could you manually start JACK (if you're not sure how, look at the [wiki](https://wiki.archlinux.org/title/JACK_Audio_Connection_Kit)) and see if that...

It does say the target `sonic-pi` is also built, what happens if you try to run that? Wrt the QScintilla stuff from the in-thread post, the version you have installed...