panic: runtime error: invalid memory address or nil pointer dereference (render.go) about cqlc HOT 4 CLOSED

Thanks for reporting this - do you have an example that we can use to reproduce the issue?

from cqlc.

Unfortunately not really. That happens on a regular insert.
It usually happens after a couple of hours of runtime. I'm using negroni and negronicql.

I was thinking that maybe the connection to cassandra gets dropped - but I'm not really sure.

It's also interesting why the entire webapp crashes, not just the current goroutine.

from cqlc.

I think I got it:
I had a race condition in which the context was being shared. :/ silly me.

I'll open another issue should this issue still arise. Thanks a lot!

from cqlc.

The docs aren't very clear about the thread safety of the context object, so maybe this issue indicates that the docs require some improvement.

Basically the context instance is inherently not thread safe because it needs to accumulate state to build the statement.

The design philosophy is that the cqlc library should be as unobtrusive as possible, which also means that it doesn't hold any locks on behalf of the calling application.

One could imagine a scenario whereby the result of the fluent API is somehow cached or memoized to an immutable statement - this might play better in a multi threaded situation.

from cqlc.