Adam B
Adam B
Turns out the error can be caught, with this: process.on('uncaughtException', function (err) { console.log('UNCAUGHT EXCEPTION - keeping process alive:', err); // err.message is "foobar" }); Found it somewhere on StackExchange....
Because the process.on event I linked earlier catches all uncaught exceptions, irrespective of their source. According to a variety of opinions I read, this is not considered to be best...
I commented in the pull request noting that the proposed fix does work, however, I also thought I'd mention that this error can be handled from the application code by...
Hi, was curious if there was a reason this hasn't been merged into the main branch yet. I too have been running into the ECONNRESET error, and the changes here...
Discovered a bug. Didn't do null checks, so server crashes if re-entering the instance after the bosses have been killed. Will fix.
Fixed bug in 285330422315b453bb760c18f7de046f34143aac.
> maybe closes #25497 ? Yes. I confirmed that after killing the Prince, you can turn in the first quest to get the Prince's Chest quest, and the chest can...
Sorry all, time is hard to come by, and I forgot about this request. I would like to get it finished. It looks like others have also made contributions. What...
@Aokromes @jackpoz I believe all tasks have been completed. Please let me know if there's anything else. Thanks! And sorry for the delay.
@Aokromes Can you be more specific? I grabbed a copy of the raw, original file and compared it against the content of this pull request, and Git is not showing...