CPU 100% with the pool

[ysbaddaden]

CPU 100% with the pool

[ysbaddaden]

The culprit is Earl::Logger's agent. It's mailbox becomes full and the channel then blocks whenever an agent tries to log something, which happens with Earl::Pool sending :info log messages.

Injecting Earl::Logger.level = :silent (or :warn) or Earl.application.spawn somewhere will workaround the issue. Note that it's recommended to supervise all your program agents with Earl.application and eventually block the main fiber with Earl.application.start.

[Nicolab]

Ok thanks, Earl.application.spawn solves the issue. I relied on the README that doesn't mention Earl.application.
However, I just saw that it is specified in the source code. I'm going through the code and the specs to better understand Earl's behavior. But I don't see how he solves this problem, by restarting the logger (or mailbox) when it crashes?

I'm in a hurry to use Earl in concrete cases, really fun (à la Elixir processes) and powerful 🚀

[ysbaddaden]

Look at the SPEC instead as well as the crystal docs, which you can access with:

$ cd lib/earl
$ crystal docs
$ firefox docs/index.html

Basically Earl.application is an Earl::Supervisor with a few niceties: run & supervise Earl::Logger and any Earl::Agent you tell it to monitor, and also trap a few signals to exit gracefully (to some extent).

[Nicolab]

Ok thanks