Thanks Martyn, I can reproduce it on 1.4.2 and a git HEAD checkout. I'll give 1.3 a go now.
After further investigation it seems to be that the values loop back round. e.g. 4295 > 0 4296 > 1 4297 > 2 As a side note can someone give me some assistance in how I would go about building a debug version of beanstalkd? Thanks, Andy. On 22 Oct 2009, at 15:12, Martyn Loughran wrote: > > Hi Andy! > > Looks like a bug with beanstalkd 1.4. I have 1.3 installed (works > fine) and 1.4 (same error as you). I haven't installed 1.4.2 yet - > that's probably worth a try. > > Martyn > > > 2009/10/22 Andy Kent <[email protected]>: >> >> We are using the Ruby beanstalk-client library, however this appears >> to be doing the right thing, when we set the TTR value in a producer >> and then read it back off of the job in a consumer we see very >> different values if an integer >4294 is used. Has anyone seen this >> before? are we doing something silly? is it a overflow/wrapping >> issue? >> Here are some examples of the TTR input > output values we are >> seeing... >> >> 4295 > 0 >> 5000 > 705 >> 21600 > 125 >> >> How would we go about fixing this to work with long TTR values such >> as >> 6 hours. >> >> Thanks, >> Andy >> >>> >> > > > > -- > Martyn Loughran > > Lead Developer, Now+ Content Sharing > > http://www.new-bamboo.co.uk > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en -~----------~----~----~----~------~----~------~--~---
