App crashes after receiving some packets about james

[mitchhentges]

Dang, looks like an underlying issue is in hoxy.
Global error handlers are a little 👻, but I'll set one up as a temporary measure and do a new release.
Thanks for reporting this and providing a solution!

[mitchhentges]

I've discovered that Sentry, of all things, is related to this problem.
A workaround will be released soon

[jamezrin]

I worked around this by adding this handler jamezrin@2313986

process.on('uncaughtException', (e) => {
  if (e.code === 'ECONNRESET') {
    console.warn('uncaught connection reset'); // eslint-disable-line
  } else if (e.code === 'ECONNREFUSED') {
    console.warn('uncaught refused connection'); // eslint-disable-line
  } else throw e;
});

[mitchhentges]

Hmm, investigating this further, the issue doesn't show up in "development mode" because Electron absorbs the error and logs it.

This explains why it wasn't obvious in local development.
In related news, when I tested the process.on('uncaughtException') locally, it worked in development mode. However, once a release was created, the issue re-appeared.

I'm not sure why Electron is stopping upon receiving a "fatal error" if we're intercepting it. Maybe we need to do something Electron-specific rather than process.on(...)?

Either way, more investigation is needed

[jamezrin]

Seems to be relationed with greim/hoxy#60 and greim/hoxy#93 (comment), but supposedly it's fixed

[kadamgreene]

Is there a new version of James available with this fix in it??

[mitchhentges]

Not yet, this issue was trickier than it first seemed.
I haven't had the time to debug further into this, but PRs are always welcome :)

[jamezrin]

I think this is fixed in this PR.
How can this be incorporated into james without having to wait for it to get merged?
The project seems a bit inactive in my opinion.