Description

Currently, because Rage scheduler is only available during the request lifecycle, calling Fiber.schedule in the console raises the No scheduler is available! (RuntimeError) error.

Steps to Reproduce

• Create a new Rage application.
• Open Rage console using the rage c command.
• Run Fiber.schedule { sleep(1); puts("hello") }.
• Actual behaviour: No scheduler is available! (RuntimeError) is raised.
• Expected behaviour: the fiber is executed in the synchronous manner.

Tips

• See lib/rage/rspec.rb for a reference implementation.
• Check the overview doc that shows how Rage's core components interact with each other.
• Feel free to ask any questions or request help in the comments below!