Closed kog4096 closed 5 years ago
No idea. What version of gopkg.in/goracle.v2 ? When does it happen? First iteration, or later? Does it say anything when compiled with "-race" ?
Version 2.9.0 Occurrence is not on first iteration Results are the same when compiled with -race
The best would be a small reproducing test case.
If that's not possible, then you have to debug it, as I haven't met with such a panic yet.
Set goracle.Log to a function to see what goracle is doing - maybe add some more Log statements here and there. But you can easily turn on ODPI-C's (the layer under goracle) logging by setting the "DPI_DEBUG_LEVEL" environment variable to something bigger than 0.
Maybe I can help if you provide some details about the program: a sketch of what it's doing, the query, its column types and so on.
During a production release, we also noticed this panic and temporarily solved it by reverting back to commit ef6b405f3ecf92728d19bcf35839a6d787ebb153.
I will try to provide more information later this week.
That's quite strange, as that is v2.9.0 !
Maybe you've used master beforehand?
@tgulacsi Correct, we used master beforehand as we build everything in docker against masters. (we have very few dependencies) I will try to give a panic stack trace tomorrow.
Ok, so you've reported this on 7th November, 12:27 GMT+1, that means we're investigating ef6b405f3ecf92728d19bcf35839a6d787ebb153..7a4f00319f5be9dd5d3c321fe2e80b7fc0347b36 but I don't see anything that may panic.
Do you use Trace tags?
My program panics on a call to rows.Next(). It works well across numerous servers/databases, but seems to be randomly failing without explanation. Any help would be appreciated.
My line of code:
for rows.Next() {
The panic: