-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No SQL dump? #44
Comments
Any chance you could ping me an example/screenshot, ideally both of what's tracked in RG as well as what the cfcatch/exception looks like in a |
The other Raygun tabs are uninteresting but I can provide them on request; the raw data notably doesn't have anything SQL-related in it. |
Hmm. One last note -- the test is using the cfcatch (and displaying the negative behavior) but the actual production stuff is using the exception argument from onError, in case that somehow makes a difference. I thought it was the same exception object in both cases though. |
I'll have a look at your example - from the screenshot though - the issue with "Unknown Error" is that Lucee is emitting an empty string for The raw JSON data would be interesting too (if you don't mind posting it). If you'd rather share it privately, let me know - I'm on the CFML slack for instance. |
That particular string is actually unimportant to me, what I need is that SQL return message under |
A quick patch at the bottom of RaygunExceptionMethod solved it for our particular version of Lucee -- no idea if this is generally correct for all CF servers so I'm not submitting a PR.
|
Reopened Thx for the code snippet, will look into how/if that works on ACF and then PR in. |
Hello,
I'm seeing a lot of "Unknown error" dumps of category "database" that are missing the SQL body or any clue about what's gone wrong with them -- is this expected behavior? Are there any changes I need to make to pick those details up?
I'm using the 1.4.0 bindings with Lucee 5.2, and forwarding the exception object onto Raygun without any manipulation. I get all of the elements but the SQL error through, the template and the stacktrace.
Thanks!
The text was updated successfully, but these errors were encountered: