You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sounds pretty low level to be honest, however, while working on a project recently, I've stumbled across an error triggered by the seroval library. While the error it self explains what the issue is, there is no easy way to know "why" the error happened as there is no stack trace that can point back to the application in order to inspect what could be going wrong.
For my specific case, I'm using TanStack's Solid Query and I've opened an issue in their repo pointing the error. In the mean time, I've been trying to track why this may have happened without much luck.
There is also a related issue from SolidStart's repo which doesn't seem to have any progress yet.
My intention here is to see if there is any way, from Solid's perspective, to be able to catch these issues and provide more insights on the missing "why" the issue could be happening. At least, a full stack trace can provide better pointers on why something may be failing to serialize during a request lifecycle.
If someone has experience with the seroval library or has been able to tackle similar issues in the past, please let me know your suggestions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Sounds pretty low level to be honest, however, while working on a project recently, I've stumbled across an error triggered by the seroval library. While the error it self explains what the issue is, there is no easy way to know "why" the error happened as there is no stack trace that can point back to the application in order to inspect what could be going wrong.
For my specific case, I'm using TanStack's Solid Query and I've opened an issue in their repo pointing the error. In the mean time, I've been trying to track why this may have happened without much luck.
There is also a related issue from SolidStart's repo which doesn't seem to have any progress yet.
My intention here is to see if there is any way, from Solid's perspective, to be able to catch these issues and provide more insights on the missing "why" the issue could be happening. At least, a full stack trace can provide better pointers on why something may be failing to serialize during a request lifecycle.
If someone has experience with the seroval library or has been able to tackle similar issues in the past, please let me know your suggestions.
Thanks everyone!
Beta Was this translation helpful? Give feedback.
All reactions