[ANN] Celluloid 0.12.4: Concurrent objects for Ruby

[Tony Arcieri]

Celluloid 0.12.4 is out! This release contains a number of bugfixes and a handful of new features:

- Memory leak fixed: crashed actors weren't getting removed from an actor's links table, causing more memory to be used each time an actor crashed. This has been fixed

- Silence annoying debug messages: The "Terminating N actors..." message can now be silenced by changing Celluloid.logger's severity level to hide DEBUG messages

- Exclusive mode fixed: Previous changes to fix exclusive mode actually caused some regressions and exclusive mode was once again completely broken. This has now been fixed and more tests added to prevent future regressions

Additional changes below:

- Celluloid::ClassMethods#proxy_class allows configurable proxies

- Improved error messages for Fiber-related problems

- Better object leakage detection when inspecting

- Use #public_send to dispatch Celluloid methods

- #idle_size and #busy_size for Celluloid::PoolManager

--
Tony Arcieri

[Jonathan Rochkind]

On 12/11/2012 5:25 PM, Tony Arcieri wrote:
>
> - Silence annoying debug messages: The "Terminating N actors..." message
> can now be silenced by changing Celluloid.logger's severity level to
> hide DEBUG messages

Awesome, but can you give us any info on what other debug messages might
be silenced?

My concern is still that I don't want to suppress ALL debug messages
neccesarily -- and in some cases, may even be interested in the
'Terminating N actors' debug message, when it really does represent
'leaked' actors my own code created and never terminated.

[Tony Arcieri]

On Tue, Dec 11, 2012 at 2:32 PM, Jonathan Rochkind <roch...@jhu.edu> wrote:

Awesome, but can you give us any info on what other debug messages might be silenced?

Right now the only other messages that are at the debug loglevel are warnings about aborted async calls

--
Tony Arcieri

[Oskar Szrajer]

Thx for your hard work.