Is there a way to exclude certain submission methods for the JavaScript client? I'm using the WebApi nuget on the Api side so I get detailed exceptions from that, but the JQuery.ajaxError exceptions don't have any message so they just appear as blank exceptions.
can you send me a link to one of the ones you are seeing a blank exception
It's on self-hosted. In the Exception tab, I get: Occurred On Sep 23, 2015 4:12:32 PM ( an hour ago )
Error Type Unknown
Message
Submission Method JQuery.ajaxError
Error Type Unknown
Message
Submission Method JQuery.ajaxError
I’ve had another report of this and I’ve been trying to track it down
I don’t know if it’s the client or server causing this.
are you able to reproduce it?
Working on turning on server side trace before I try to repro.
I have the event json file, but not sure how to decode it. Also have the relevant lines from the trace log.
So a output from Exceptionless on the server side shows: 2015-09-23 17:25:06.5813|TRACE|EventNotificationsJob|Loaded stack: title=is not a valid value for Int32.
But the javascript that same title= statement is blank. 2015-09-23 17:25:13.7373|TRACE|EventNotificationsJob|Loaded stack: title=
/if you repost the raw json to the api does it reproduce this issue?
:)
I just forked exceptionless.javascript to fix some things regarding unhandled exceptions in Node
When did you try exception handling in node lastly?
I mean... did this ever work? :)
@frankebersoll we don’t use node, but I created a node sample app and triggered a few exceptions and they came in
"UNCAUGHT_EXCEPTION" event is now "uncaughtException"
are you running 4.x?
node 4.x
I don’t remember what version I tried it on
but it was 12.x
I just did a brew update the other day and I’m on 12.7
if you want to do a pull request I’ll accept it, just sign our cla
where is the cla?
also, if you have a link talking about those event name changes that would be greatly appreciate
@theit8514, please let me know what you find
@frankebersoll, @theit8514 I’m going to be heading out here in a bit for dinner and the gym. If I don’t respond, just leave a message in here and I’ll get back to you.
I had to step away for a call. I attempted to post the json data using I'm Only Resting but I think I'm doing it wrong because it shows up as a log message.
Ok, yes, I have the json correctly uploading now. It still shows title= with nothing after it.
So one thing I'm noticing is that the one coming from the application has a @error.message: "@error":{"message":"is not a valid value for Int32.","type":"System.Exception"
The one from the Javascript just has an empty stack trace: "@error":{"stack_trace":[]}
The one from the Javascript just has an empty stack trace: "@error":{"stack_trace":[]}
TraceKit.computeStackTrace(exception, 25); is returning a stack with incomplete=true. This is where the empty message comes from.
Probably because "exception" is literally just a string: "Internal Server Error"
can you forward that my way
via a private gist or send it in a message via gitter
The jQuery.ajaxError 4th parameter is a string value, not an exception, and it's getting passed to createUnhandledException. It either needs to be wrapped in a new exception or something like that.
yeah you are right
hmm
so
hmm
lol dang it
can you paste the whole raw json so I can take a look
I think we may be able to parse it
wonder why I thought it was an error object
[{"date":"2015-09-23T21:25:05.685Z","type":"error","source":"api/Some/ApiCall?id=10","data":{"status":500,"response":"{\"Message\":\"An error has occurred.\"}","@error":{"stack_trace":[]},"@request":{"user_agent":"Mozilla/5.0 (Windows NT 6.3; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0","is_secure":true,"host":"www.example.com","port":80,"path":"/","cookies":{"Cookie":""},"query_string":null,"referrer":"https://www.example.com"},"@submission_method":"JQuery.ajaxError"},"tags":["Example","JavaScript"]}]
because we aren’t parsing the ajax error string into a working model which I thought TraceKit handled for us
I need to add a test for that..
for now, can you log an issue for this.
I think maybe the solution would be to wrap the jquery methods but that kind of stinks
yeah
If the other node fix comes in
I may just comment that out and do a quick short release
thanks for letting us know about that issue