Race condition on error handling

[garethbowen]

If I try to get a doc that doesn't exist immediately on page load I get an uncaught exception in promise. If I try to get the same doc after a 1 second delay then the error is handled as expected. If I remove worker-pouch the 404s are handled as expected.

I've done some digging around to try and get more information but unfortunately I haven't gotten far, but here's what I have...

I'm not sure if it's relevant but I use angular-pouchdb.

Let me know if there's anything else I can do to help.

[nolanlawson]

Sounds like a race condition with the worker. That's really weird; I thought I waited for the worker to initialize before sending out any messages.

I don't have time to look into this right now, so any PRs would be happily accepted. :)

[nolanlawson]

Actually yeah, that makes exactly zero sense because the browser is supposed to handle this automatically when I call worker.postMessage().

Could this be a bug in Chrome? Can you reproduce in Firefox as well?

[garethbowen]

I can't reproduce in Firefox, just Chromium (v49). Good call.

[nolanlawson]

Hm, if you can find a minimally reproducible test case, this might be a good bug to file on Firefox itself. In theory all webworker postMessage()s are ordered (both to and from the web worker). If Firefox behaves differently from Chrome (and Edge/Safari), then this could be a useful bug to send to Mozilla (they are very fast to fix bugs in my experience).

[NNemec]

I seem to have the same issue in my project. (Running Chrome v53 in electron.io, can't easily try out any other browser)
Was there any new insight on this since the initial discussion?

[NNemec]

Got it to work now in my case: Turned out that delaying the first call of db.get until db.info was finished did the trick.
Not sure whether it was the same issue, though.

[PascalTemel]

I came across the same issue in an angular2 project. The comment above helped me solve my issue.