Revert scheduler changes.

CHANGES.md

@@ -35,8 +35,6 @@ New:
 - Added `video.canvas` to make it possible to position video elements independently
   of the rendered video size ([#3656](https://github.com/savonet/liquidsoap/pull/3656), [blog post](https://www.liquidsoap.info/blog/2024-02-10-video-canvas-and-ai/))
 - Added cover manager from an original code by @vitoyucepi (#3651)
-- Reworked scheduler queues logic, allow user-defined queues, add options to pick
-  the queue to send asynchronous tasks to (#4151)
 - Added non-interleaved API to `%ffmpeg` encoder, enabled by default when only
   one stream is encoded.
 - Allow trailing commas in record definition (#3300).

doc/content/liq/radiopi.liq

@@ -16,6 +16,12 @@ settings.harbor.bind_addrs.set(["0.0.0.0"])
 # Verbose logs
 log.level.set(4)
 
+# We use the scheduler intensively,
+# therefore we create many queues.
+settings.scheduler.generic_queues.set(5)
+settings.scheduler.fast_queues.set(3)
+settings.scheduler.non_blocking_queues.set(3)
+
 # === Settings ===
 
 # The host to request files

doc/content/migrating.md

@@ -76,32 +76,6 @@ def transition(old, new) =
 end
 ```
 
-### Thread queues
-
-In order to improve issues with complex inter-dependent asynchronous tasks, scheduler queues have been updated.
-
-User-provided named queues can now be created and used to send asynchronous tasks, making it possible to control
-concurrency of certain classes of tasks and also to remedy any potential dependency between asynchronous tasks.
-
-Settings for queues have thus changed and now will look like this:
-
-```liquidsoap
-# Add a custom queue with 4 workers, increase generic queues to 4:
-settings.scheduler.queues.set([
-  ...list.assoc,remove("generic", settings.scheduler.queues()),
-  ("generic", 4),
-  ("custom", 4)
-]
-```
-
-The `fast` argument of the `thread.run.*` functions has been replaced by `queue`, telling the operator which queue should the
-asynchronous tasks sent to.
-
-Likewise, `request.dynamic`, `playlist`, `single` etc. have also been updated to accept a `thread_queue` argument controlling
-which asynchronous queue their request resolution tasks should be sent to.
-
-See [the threads page](threads.html) for more details.
-
 ### Replaygain
 
 - There is a new `metadata.replaygain` function that extracts the replay gain value in _dB_ from the metadata.