Prone throws an IndexOutOfBoundsException handling a org.postgresql.util.PSQLException about prone HOT 12 CLOSED

Happy to help. Thanks for prone. It's a beautiful tool.

from prone.

Thanks for the report. I'll take a look.

from prone.

It seems like you have a line number that is higher than the number of lines in the file. So that is slightly weird. Do you have a chance to figure out which file is the culprit and how that could have happened?

If we can't figure out the actual cause, I can add some guard against this exception and just bail out on showing the code if we get this weird edge case.

from prone.

I suspect it’s something to do with HugSQL? I don’t know. It only happens with errors from the database — Prone works wonderfully for everything else.

from prone.

Any chance you could tear out everything else and make a minimal project
that I could use to reproduce it?
tir. 29. mar. 2016 kl. 21.39 skrev Coda Hale [email protected]:

I suspect it’s something to do with HugSQL? I don’t know. It only happens
with errors from the database — Prone works wonderfully for everything else.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#38 (comment)

from prone.

I’ll certainly see if I can, but I don’t think I’ll be able to get around to it soon.

Coda Hale
http://codahale.com

On Mar 29, 2016, at 12:48, Magnar Sveen [email protected] wrote:

Any chance you could tear out everything else and make a minimal project
that I could use to reproduce it?
tir. 29. mar. 2016 kl. 21.39 skrev Coda Hale [email protected]:

I suspect it’s something to do with HugSQL? I don’t know. It only happens
with errors from the database — Prone works wonderfully for everything else.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#38 (comment)

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub #38 (comment)

from prone.

I have a rare case of some free time this weekend, so for an expedient fix
that would be helpful before then. I don't use hugSQL myself, so it'd take
quite some time just to get everything up. Fully understand if that's hard
to fit in tho. Thanks for the report regardless. :)
tir. 29. mar. 2016 kl. 21.49 skrev Coda Hale [email protected]:

I’ll certainly see if I can, but I don’t think I’ll be able to get around
to it soon.

---

Coda Hale
http://codahale.com

On Mar 29, 2016, at 12:48, Magnar Sveen [email protected]
wrote:

Any chance you could tear out everything else and make a minimal project
that I could use to reproduce it?
tir. 29. mar. 2016 kl. 21.39 skrev Coda Hale [email protected]:

I suspect it’s something to do with HugSQL? I don’t know. It only
happens
with errors from the database — Prone works wonderfully for everything
else.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#38 (comment)

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub <
https://github.com/magnars/prone/issues/38#issuecomment-203069871>

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#38 (comment)

from prone.

Author of HugSQL here...I was curious if HugSQL was triggering this, so I created a repo reproducing the error @codahale is seeing. Turns out, I was able to reproduce this without HugSQL.

See here: https://github.com/csummers/prone-issue-38

from prone.

That’s awesome, @csummers. Thanks for the repro — and for HugSQL!

from prone.

Outstanding. Thanks, Curtis. :)

from prone.

Hey, check out this frame:

                  jdbc.clj:   -1  clojure.java.jdbc/eval19552/fn

That's an outlier if I ever saw one.

from prone.

1.1.1 released with this fix.

from prone.