Celluloid 0.12.1: concurrent objects for Ruby (now with better debugging!)

Celluloid 0.12.1 is out. It’s primarily a bugfix release for 0.12.1, but
also includes some new features. Included in this release are a new set
of
tools for debugging Celluloid programs:

New Features

  • New incident report system for providing better debugging reports
  • Initial thread dumper support
  • String inspect that reveals bare object leaks

I will be adding a new “Debugging” section to the wiki to cover these
new
features

Bugfixes

  • Exclusive mode was not being toggled off properly
  • Use Facter to get CPU count, fixing misreported CPU counts
  • Revert BasicObject-based proxies, fixing several bugs with improper
    BasicObject use
  • Task statuses were not being reported properly
  • Remove Celluloid#alive? as it cannot be called in any manner that will
    ever
    return anything but true, rendering it useless

On Wed, Oct 10, 2012 at 12:16 PM, Tony A.
[email protected]wrote:

Celluloid 0.12.1 is out. It’s primarily a bugfix release for 0.12.1, but
also includes some new features. Included in this release are a new set of
tools for debugging Celluloid programs

It seems the new incident reporter wasn’t ready for primetime. I’ve
released 0.12.2 which shuts it off by default and uses the same stdlib
logger as 0.12.0.

That’s not necessarily a good thing if your cores are hyperthreaded.
Honestly hyperthreading probably shouldn’t exist and is largely a
marketing
gimmick by Intel.

That said, yes Celluloid has moved to the Facter gem for reporting CPU
cores and is using its counts now.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs