A FailureApp should know its failure message

[betesh]

In my humble opinion, a FailureApp should know why someone woke it up.

For instance, in this example in devise: https://github.com/plataformatec/devise/blob/v3.3.0/lib/devise/strategies/database_authenticatable.rb#L17, it seems to be that :not_found_in_database is a useful piece of information that the FailureApp should have access to.

[josevalim]

[mmzoo]

Ah, thank you so much. This caused me some debugging headache today :) Looking forward to having this available via rubygems as well.

[betesh]

@josevalim What does the squirrel mean?

[mmzoo]

@betesh google "ship it squirrel" :)

[betesh]

As in http://www.geoffreywiseman.ca/blog/2013/03/15/shipit-update-plan/ ? So if you use the shipit squirrel in an issue comment, that means merge it and publish a new gem, i.e. ship the upgrade immediately?

[mmzoo]

@betesh Well, primarily it means 'alright, approved, this is good to go'. I don't know about wardens policy for when it is okay to publish a new version to rubygems. Other gem-maintainers usually wait for a few issues to be solved and when they feel it's time to launch a new version, it will be pushed to rubygems. So I expect that to happen in the near future.