ruote tmp/log_2013-01-14.html

2013-01-14 10:09:05 utc hartog hi all!
2013-01-14 10:09:30 utc jmettraux hi
2013-01-14 10:11:24 utc hartog with this radial: https://gist.github.com/4529017
2013-01-14 10:11:55 utc hartog what would be the best way to let just the storage before 'charlie_alpha' proceed?
2013-01-14 10:12:30 utc jmettraux sorry, I don't understand
2013-01-14 10:12:56 utc hartog i put the workitem in storage so some remote event can trigger it to proceed
2013-01-14 10:13:14 utc hartog but I want the flow to proceed on just that leave
2013-01-14 10:13:41 utc jmettraux then proceed just that leave
2013-01-14 10:14:00 utc hartog however; `workitems = dashboard.storage_participant.find(wfid); workitems.select { |x| ... }` always fails
2013-01-14 10:14:04 utc hartog so how then?
2013-01-14 10:14:18 utc jmettraux what does "always fails" mean?
2013-01-14 10:14:30 utc hartog NoMethodError: undefined method `call' for "20130114-0949-jotojaza-gamosada":String
2013-01-14 10:14:59 utc hartog seems to occur whenever I call any enumerator operations that go 'beyond a certain point'
2013-01-14 10:15:18 utc hartog (which is very vague; working on the crystalization of that)
2013-01-14 10:15:46 utc jmettraux ok, please fill an issue report --> https://github.com/jmettraux/ruote/issues
2013-01-14 10:15:57 utc jmettraux s/issue report/detailed issue report/
2013-01-14 10:17:15 utc hartog is there another way to fetch the exp_id/sub_id/wfid (and then proceed it) for now?
2013-01-14 10:19:40 utc jmettraux workitems = dashboard.storage_participant.select { |workitem| ... }
2013-01-14 10:19:52 utc jmettraux since there is no "#find(wfid)" method for the storage participant
2013-01-14 10:21:04 utc jmettraux can't find such an example...
2013-01-14 10:21:14 utc hartog it does work :)
2013-01-14 10:22:03 utc jmettraux ok, so no need for an issue
2013-01-14 10:22:25 utc hartog is using query a sane idea?
2013-01-14 10:24:48 utc hartog and could I use exp_id and subid in query? (using ruote-mon btw)
2013-01-14 10:25:52 utc jmettraux sane idea: depends on the storage
2013-01-14 10:26:34 utc jmettraux the exp_id and the sub_id are present in the _id of the document
2013-01-14 10:26:44 utc jmettraux and there should be an index on that thing
2013-01-14 10:26:58 utc jmettraux so you can go directly to the document
2013-01-14 10:31:10 utc hartog which would result in something like 'engine.storage_participant.proceed( Ruote::Workitem.new( engine.storage.get('workitems', full_wfid_id) ) )'
2013-01-14 10:33:32 utc jmettraux or engine.storage_participant.proceed(engine.storage_participant[sid])
2013-01-14 10:34:15 utc hartog that would be most elegant
2013-01-14 10:50:27 utc jmettraux [].find("x").next
2013-01-14 10:57:49 utc hartog schön....