Closed raceves closed 1 year ago
Can you give me the full backtrace for the error so I can see the call stack?
Good debugging, you basically nailed it so I was able to quickly see and fix the issue.
Oh awesome, I'm glad that was helpful. I was just coming back to this to give you a backtrace but looks like that isn't needed any longer. I'll keep an eye out for the next release :)
Hello,
Wanted to report a potential bug I just uncovered; it took me a while to understand what's going on as I'm not a ruby developer by trade (but getting there). I understand the testing for the ruby worker operates by using method redirection. We actually have some unit tests set up using this and it's been working well.
Issues popped up when we updated the
faktory_worker_ruby
gem to version1.2.0
- our unit tests started erroring out saying that it couldn't connect to port 7419, which is odd because it shouldn't be hitting the network.After diff'ing the source code for both gems, I believe the error is this: Within
faktory_worker_ruby
, thelib\faktory\client.rb
file was changed to use thecgi
gem, which then changed the mainopen
call to now beopen_socket
. However, thelib\faktory\testing.rb
file is still just redirecting the previousopen
call only. Hence, no matter what, the realopen_socket
call will fire and will try to contact the faktory server over the network in test mode, resulting in the error.