ptaoussanis
commented
8 months ago @Pederaugust Hi there! Thanks for the kind words :-)
So the key info in that stack trace is here:
taoensso.nippy/throw-unfreezable nippy.clj: 1020
clojure.lang.ExceptionInfo: Unfreezable type: class next.jdbc.result_set$navize_row$fn__17909
as-str: "#object[next.jdbc.result_set$navize_row$fn__17909 0x621cc708 \"next.jdbc.result_set$navize_row$fn__17909@621cc708\"]"
type: next.jdbc.result_set$navize_row$fn__17909Basically the problem is that you're trying to put something into your Ring session (a next.jdbc type) that Carmine doesn't know how to write to Redis (doesn't know how to serialize with Nippy).
I'm not familiar with the particular type here, but I suspect that it should be possible to coerce it to a standard Clojure data type before adding it to your session.
Does that make sense?
Edit to add: when you're using Ring's standard in-memory store, it can safely hold any kind of type since its values are all just JVM objects in memory. But when you switch to a persistent store like Carmine's store, you need to be mindful of the types being stored in sessions since there must be some way to serialize those types to/from Redis.
Carmine uses Nippy for its serialization, so can handle many different types - including every standard Clojure type. But Nippy will usually be unfamiliar with library-specific types (like your jdbc.next type here).
Pederaugust
Hey, love your contributions to open source. I have setup my ring-server to use the carmine-store. Context: I am running redis in docker. For development I use this configuration:
{:spec {:uri "redis://0.0.0.0:6379/0"}}I am getting this error:
I am not sure why next gives an error when I use the carmine store? When I use the default store everything works fine.