-
|
The stacktrace looks like below. It doesn't say much where it happens. I am not blocked because I can enable the DEBUG logging of Slick to see what SQL was executed right before this exception. But I wonder if there's a way to get the stack trace be more informative. PS. Maybe this is not really a slick issue but more like an async framework issue. Still, I'd love any thoughts or tricks. |
Beta Was this translation helpful? Give feedback.
Answered by
nafg
Jan 21, 2025
Replies: 1 comment
-
PR welcome. Unfortunately currently I don't have time to work on it myself, but I am open to doing a pair programming session or something with someone. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
tanin47
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
sourcecodethat could be added to any errorPR welcome.
Unfortunately currently I don't have time to work on it myself, but I am open to doing a pair programming session or something with someone.