Airbrussh::Rake::Context needs to be redesigned to be thread-safe? about airbrussh HOT 2 OPEN

Just stumbled over this. We use invokes like

task('options:parse').invoke([:release_tag, :project_name, :repo_url])

in our capistrano tasks (e.g. deploy). This invoke just checks for some required options from the rake command line. Then the original task (deploy) is continued. But airbussh outputs 'options:parse' as task.

I disabled it by setting the config option "monkey_patch_rake = false", because the output is very confusing (wrong task name). Is there a workaround for this, like setting the rake task context for airbrussh after calling an invoke?

from airbrussh.

This is a tough one. I don't think there is an easy workaround. You could try explicitly setting the task name, but I'm not sure it would produce the right results:

Airbrussh::Rake::Context.current_task_name = "deploy"

from airbrussh.