Cyprien Huissoud

HI @samaaron I'm on windows with latest version from Sonic Pi. I've played with the amount of message sent (3 then 4 then 10) and you can see that the...

Hi @samaaron I've put some debug here and there in event_history.rb to dump the state of the events and compared it with the received cue value. Here's the finding so...

Thank you @samaaron I guess time precision is "lower" on ruby windows. I might have some time to try to propose a fix for this issue this weekend. Do you...

@ethancrawford hey, do you know if this has been fixed in the latest 4.x release? I will try at some point and see if I can reproduce the issue.

@missinglink Any news on this?

When looking at them through the mobility explorer they seems all on the same exact coordinate. On Tue, 15 May 2018, 12:44 Rui J Santos, wrote: > It seems not...

Thank for investigating @Rui-Santos indeed and you can see the stop id schema here (in the archive details): https://transit.land/dispatcher/feed-versions/7e1609712ced7f7ecded0fe7deefdc6bddb68497 or here https://transit.land/dispatcher/feed-versions/270399f70f59764a945b6a063a3e7a4dae53c05d (not sure why your link open a caltrain...

I don't think that it is related. What I meant is that for feed X with fetched feed version 1, 2, 3 (and all of these feed version properly imported)....

Indeed 44 sorry! sorry, 107 was on my local setup of the datastore (I do have more of the feed version imported in total) This bounding box is easier to...

@irees Do you have any ideas here? I'm not sure where to look further and how to address it. I've tried locally to destroy the feed, but all stops/routes are...