Closed joananeves closed 2 years ago
Thanks for the report. Stick to 1.1.1 for the time being. I'll take a look and push a fix when I can.
Thanks @nesquena That's what I did locked to 1.1.1.
@joananeves This is probably my fault, after a patch I attempted (leading to v1.1.2) which tried to get things working with the YAML responses from beanstalkd
on a "modern" v4 YAML parser. The PR discussion is in #86. I'm very sorry this has caused you inconvenience. I'm discussing a solution and hopefully we'll be able to get this fixed for you soon.
1.1.2 has been yanked as well until we find a suitable fix, thanks again for the report, and sorry about the inconvenience
We are reviewing #88 as a fix. Apologies again for the bug.
I can confirm all tests were passing for me as well, and it seemed to work locally. Pushed 1.1.3 out live! Thanks for your help
@joananeves When you get a chance, perhaps you can confirm that everything is back online with 1.1.3 as well!
Hi @nesquena @pond I confirm that 1.1.3 is working for me. Thanks to both!
Hi @nesquena @pond
I confirm that 1.1.3 is working for me.
Thanks to both!
Great news, thanks for confirming!
I'm using ruby 2.6.6, and when changed from beaneater 1.1.1 to 1.1.2, got a json parse problem.
If I use colon in one of the parameters, I get this error (removing the colon will have success):
With the following job submitted: