Handle @position=nil case properly about airbrussh HOT 7 CLOSED

Thanks for the report! What versions of Capistrano and SSHKit are you running?

from airbrussh.

Also, if you could offer any insight into why this may be happening, I would appreciate the troubleshooting assistance. The @position value should never be nil, but maybe we can figure out the combination of circumstances that leads to the bug.

Some ideas:

1. Are you deploying to multiple servers? It could be a threading issue.
2. Are you mutating the SSHKit Command object as it is running?
3. Do you encounter the bug always in the same step in your deploy, or is it unpredictable?

Worst case, I can patch the code so that nil is gracefully handled, rather than blow up with an exception. However we should still try to get the root cause if we can.

Thanks!

from airbrussh.

sshkit-1.10.0 / capistrano-3.5.0

Are you deploying to multiple servers? It could be a threading issue.

I vaguely remember that it occurred when I was deploying to multiple servers without host filters. So, yes.

Are you mutating the SSHKit Command object as it is running?

No.

Do you encounter the bug always in the same step in your deploy, or is it unpredictable?

It was pretty random, so it may be a threading issue as you mentioned. I'll use host filter to work around that for now.

As much as I wanted to help you more, I don't have time to dig into the source at this moment. Maybe I was too adventurous when I decided to upgrade Capistrano as well as Debian, Sunzi, MySQL, etc. at the same time... 😄

from airbrussh.

One more question: are you using invoke within an on block anywhere in your tasks? Like this:

on ... do
  execute ...
  execute ...
  invoke "some:task"
end

from airbrussh.

Yes, exactly.

from airbrussh.

Great. Now I think I understand how nested invoke plus multiple servers could trigger this bug. Thanks for the help!

from airbrussh.

Fix has been released in 1.0.2 🚢

from airbrussh.