dkubb changed the topic of #datamapper to: Datamapper v1.2.0 | Mailing List: http://is.gd/aa9D | Logs: http://is.gd/qWAL7V | DataMapper 2 Renamed to ROM, see #rom-rb for development
zombor has quit [Read error: Connection reset by peer]
zombor has joined #datamapper
zombor has quit [Remote host closed the connection]
lgierth has quit [Quit: Ex-Chat]
zombor has joined #datamapper
zombor has quit [Remote host closed the connection]
zombor has joined #datamapper
jhn has joined #datamapper
zombor has quit [*.net *.split]
Spockz has quit [*.net *.split]
alessand1o has joined #datamapper
zombor has joined #datamapper
zombor has quit [Remote host closed the connection]
jhn has quit [Ping timeout: 248 seconds]
snusnu has quit [Quit: Leaving.]
postmodern has quit [Quit: Leaving]
zombor has joined #datamapper
zombor has quit [Ping timeout: 264 seconds]
jhn has joined #datamapper
knowtheory has joined #datamapper
rsim has joined #datamapper
rsim has quit [Read error: Operation timed out]
zombor has joined #datamapper
zombor has quit [Ping timeout: 272 seconds]
rsim has joined #datamapper
rsim has quit [Ping timeout: 240 seconds]
rsim1 has joined #datamapper
zombor has joined #datamapper
zombor has quit [Ping timeout: 272 seconds]
jhn has quit [Ping timeout: 248 seconds]
rsim1 has quit [Quit: Leaving.]
skade has joined #datamapper
mikecmpbll has joined #datamapper
mbj has joined #datamapper
mikecmpbll has quit [Ping timeout: 245 seconds]
mikecmpbll has joined #datamapper
alessand1o is now known as Spockz
skade has quit [Quit: Computer has gone to sleep.]
<Eiam>
dbussink: I open 10 links to my site and hit reload on all of them a few times and it'll trigger
<Eiam>
so not a concrete repro case
<dbussink>
hmm
<dbussink>
that would make it tricky
<dbussink>
since then that change doesn't really cause the bug probably
<Eiam>
well I'm already recusing and trying again
<dbussink>
but it only exposes an issue that already existed before
<Eiam>
would that work for this too?
<Eiam>
a try again?
<Eiam>
(it looks like execute_reader is getting a value it doesn't expect?
<dbussink>
depends, there's a good chance the query already executed
<dbussink>
what kind of statement is it?
<dbussink>
select / update / insert etc.
<Eiam>
almost always a select
<Eiam>
I do very few DB writes
<dbussink>
since that git change was if you ran an insert or something like that through the interface for select
<dbussink>
Eiam: problem with issues like this that only cause a problem sometimes is that it's really usually not possible to fix without at least some way to reproduce :9
<dbussink>
:(
<Eiam>
I can add logging to get more information
<Eiam>
to get a more concrete reproducible case
<dbussink>
yeah, that would be good, feel free to add that to that issue
<dbussink>
right now it's not really actionable
<Eiam>
what kind of logging =)
<dbussink>
the more the better
<Eiam>
I've already monkey patched the read method
<Eiam>
so I can do whatever in there
<dbussink>
but ideally some demo app that causes the issue if you hammer it
<dbussink>
that's usually the easiest to go on
<dbussink>
Eiam: you can log the query it's executing including all the parameters etc.
<Eiam>
okay I
<Eiam>
I'll start with that..
<Eiam>
why is it that making the same query again will work?
<Eiam>
e.g. I can reproduce this by just reloading the same page over and over, eventually it'll hit
<Eiam>
next reload, won't hit
<Eiam>
every page load is the same sql request
<dbussink>
could be a race condition somewhere
<dbussink>
problem with the db connection that reconnects
<dbussink>
all kinds of stuff that can go wrong
<Eiam>
hmm maybe I'll just add it into my rescue => retry
<dbussink>
can't really say what it is without digging in
<Eiam>
okay
<Eiam>
well I'll get more logging, and also try to rescue/retry and see if that resolves it