Sam

There is a 100% working implementation using `ConditionVariable.new` right here: https://github.com/discourse/discourse/blob/main/lib/scheduler/thread_pool.rb No background thread needed, Queue timeout is awesome, but this achieves the exact same goal in a backwards compatible...

It is very hard for us to reason about the change without specs for the controller, would you be able to add them?

not sure about this @jjaffeux / @davidtaylorhq , should we be sorting this in JS or should the server be sending stuff in the sorting order it wants? what if...

I approved but I am not sure... this may introduce a vector for client side DoS using nested symbols. I am not sure about this @davidtaylorhq / @ZogStriP thoughts?

Note, at Discourse we ship with 6 sets and allow users to pick which set they want. Totally happy for you to borrow any of the code we have that...

Is there no other way??? I hate that the entire internet has to get this just cause of 1password? will autocomplete=none be respected?

wow this is awesome, any news about when a new release can be cut for head? I noticed that `"https://cdn.jsdelivr.net/npm/@ruby/ruby-head-wasm-wasi/dist/ruby-head-wasm-wasi.wasm"` is still pointing at 3.3

This is not ideal, I would say a couple of things here: 1. native tool support should be optional, like we have other optional llm features (see llm_model.lookup_custom_param) 2. I...

btw :wave: from Sydney!

I still stand behind thinking this should be optional, we get tons of mileage from XML tools, so it is nice to choose if you prefer XML tools and streaming...