ruote tmp/log_2012-10-26.html

2012-10-26 06:32:56 utc thunder tx for the answer john :) next time i´ll be paying better attention to what´s in github :)
2012-10-26 06:33:04 utc jmettraux thunder: hello Gert, welcome to #ruote (I can't remember if you ever join the chat), thanks for the feedback
2012-10-26 06:33:05 utc jmettraux :-)
2012-10-26 06:33:28 utc thunder yesterday i found it empty before I put my brilliant patch up :)
2012-10-26 06:36:08 utc jmettraux ok :-)
2012-10-26 06:36:35 utc jmettraux well, your patch is much appreciated anyway
2012-10-26 06:37:20 utc thunder was trying to make it as easy as possible, you put a lot of work into providing these gems and they (should ;)) make our lives easier. :)
2012-10-26 06:37:47 utc jmettraux :-)
2012-10-26 06:40:42 utc thunder somehow my development site broke and was trying to find out why with not much luck yet ... i´m not writing all the code myself (goes a bit beyond my skills I think), so then trying to debug things falling over is quite a challenge. yesterday at first the processes stayed in the process list instead of disappearing (but no expected action happened) ... now still no action, but the process is disappearing so not anymore showing up in ruote-kit ...
2012-10-26 06:40:47 utc jmettraux thunder: you're based in Greece but your name sounds Dutch, are you expatriated to a better climate?
2012-10-26 06:41:30 utc jmettraux no errors showing up in those non-disappearing processes?
2012-10-26 06:41:56 utc thunder jmettraux: yep exactly that, my wife is Greek, so we decided to move to Greece ... The country obviously couldn´t handle my arrival here as it has been going downhill since :)
2012-10-26 06:42:16 utc jmettraux lol
2012-10-26 06:42:19 utc thunder exactly no errors (which is how i ended up with the internal server errors
2012-10-26 06:43:29 utc jmettraux if you could package an issue report for ruote itself, with details about ruby and ruote versions and storage used...
2012-10-26 06:43:38 utc jmettraux unless you want to chat it out
2012-10-26 06:43:56 utc jmettraux but I'll have to leave in one hour
2012-10-26 06:44:00 utc thunder oh no not going to bother you with it further (yet) :)
2012-10-26 06:44:27 utc thunder i´m working with coffeeaddict (you probably know that alias) ... he claims it is eventmachine being a bad boy
2012-10-26 06:45:00 utc jmettraux aaah
2012-10-26 06:45:10 utc thunder which is also a gem that i have a limited knowledge of .... which of course makes it harder to debug
2012-10-26 06:45:20 utc jmettraux ok
2012-10-26 06:45:33 utc jmettraux I guess Hartog is in control then
2012-10-26 06:45:40 utc thunder i wish he was lol
2012-10-26 06:45:53 utc jmettraux temporary lapse
2012-10-26 06:46:22 utc thunder yes the setup is not a straightforward one i believe, but it looks cool if it all works :)
2012-10-26 06:46:57 utc jmettraux what storage is behind the ruote?
2012-10-26 06:48:51 utc thunder sequel is the storage used
2012-10-26 06:50:30 utc thunder i need to run now, nice talking to you, I´ll let you know if we sort out the problem!
2012-10-26 07:00:00 utc jmettraux bye! Don't worry, Hartog is good
2012-10-26 07:30:56 utc thunder i know, i used to be his manager in the old days lol ...
2012-10-26 07:47:23 utc jmettraux ttyl
2012-10-26 10:08:09 utc thunder running rake test on the latest git on my end gives me:
2012-10-26 10:08:09 utc thunder 1) Failure:
2012-10-26 10:08:10 utc thunder test_put_sequence(FtStorage) [/usr/local/lib/ruby/gems/1.9.1/bundler/gems/ruote-66ac92cda033/test/functional/storage.rb:233]:
2012-10-26 10:08:10 utc thunder <14> expected but was
2012-10-26 10:08:10 utc thunder <13>.
2012-10-26 10:09:11 utc thunder does this signal issues on my end? :)
2012-10-26 11:01:48 utc jmettraux thunder: hello, about this failing test, what OS and what ruby version?
2012-10-26 11:03:51 utc thunder hi john: ruby 1.9.2p180 (2011-02-18 revision 30909) [i686-linux]
2012-10-26 11:04:54 utc jmettraux is the system 64bit?
2012-10-26 11:05:28 utc thunder it´s 32bit i believe and Debian wheezy
2012-10-26 11:05:53 utc jmettraux I'm also seeing this issue on a GNU/Linux 64bit system, but it doesn't appear on my OSX SnoLeo nor on the CI box which is GNU/Linux 32
2012-10-26 11:05:58 utc jmettraux ok
2012-10-26 11:10:14 utc thunder my environment is not the most stable so don´t hang yourself up on it :) ...
2012-10-26 11:10:50 utc jmettraux I have it under my nose, now I have one more motivation to fix it :-)
2012-10-26 11:30:44 utc thunder let me see if running it again will give the same error ... just in case :)
2012-10-26 11:35:35 utc jmettraux it'll probably give the same error but a different count
2012-10-26 11:37:55 utc thunder 4 expected but was 3 ... tssssss so close yet so far :)
2012-10-26 11:38:24 utc thunder don´t think thise overall has to do with my issue on my process not continuing ... but hartog is back on it ... my attempts so far have been futile
2012-10-26 11:41:24 utc thunder i thought maybe going to latest versions of eventmachine and the git versions of ruote and ruote-kit would do it ... but it seems not to ... before my messages were disappearing from the process view, now they are again staying there not finalising ... if there is really something related to ruote you will surely hear about it :)
2012-10-26 11:53:10 utc hartog hi all :)
2012-10-26 11:53:24 utc hartog ACTION does a secret handshake with thunder
2012-10-26 11:54:28 utc jmettraux :-) hello Hargo
2012-10-26 11:54:59 utc jmettraux s/Hargo/Hartog/ sorry
2012-10-26 11:55:26 utc hartog np! my name is a difficult one, even in my native tongue - i am used to the abuse by now ;)
2012-10-26 11:56:29 utc thunder there is the one who is going to solve all my problems! :)
2012-10-26 11:56:37 utc thunder ACTION drops down crying
2012-10-26 11:57:19 utc jmettraux Hartog: it's not my fault, I was very kind to him
2012-10-26 11:57:52 utc hartog that's what they all say...
2012-10-26 21:47:30 utc thunder jmettraux: the issue has been solved ... it was not ruote related, not sure what was actually broken, but a rewrite using the same technique from another system solved it ... on to the next issue