Orbit crashes and subsequent calls hangs after a unsucessfull request to a remote server

[RichardsonWTR]

If you send a request to a remote server and the server returns an error, Orbit crashes.
Subsequent calls hangs (As stated by me in #516 in this comment).

I'm registering this issue to document it and to learn from this.

Repro link in v0.16.6:
https://codesandbox.io/s/orbitjs-repro-issue-v0166-v8u3u

I tried to reproduce it in v0.17.0-beta.6, but I'm having some issues with the models itself.
The models from the server I'm using are in the plural. I tried to change the Orbit models to the plural too, but no success.
https://codesandbox.io/s/orbitjs-repro-issue-v0170-beta6-mybc8

Any help would be appreciated.
Best regards

[dgeb]

This is not a bug, but by design. Orbit has not crashed, but has paused its queues to allow you to address the problem. You can either skip or retry the action that errored.

Please take a look at the documents on pessimistic and optimistic error handling.

[RichardsonWTR]

Awesome! Again, just what I needed.

TL;DR

My actual problem was different and I was led to use the skip method without parameters (which caused an error) based on the docs :

skip() will cancel and discard the current task and proceed to process the next task.

It never crossed my mind to pass the actual exception as a parameter to the skip method. When I did so, it worked as expected.
I could've discovered this if I've read the tests and some projects that are using the library. Lesson learned.
PS:There's an advice in the end.

Some things to note:

Yesterday I gave a special care to the Task Processing section of the Orbit docs, trying to figure it out a solution to my problem. I realized that I should've read that before. +1 for mentioning the importance of reading that that there in the docs.

I remembered that my current issue was not just how to handle the error, it was how to handle the error and retrieve the server message.
When I borrowed the catch block from #516, I've implemented it this way:

catch(e, transform) {
    this.source.requestQueue.skip();
    this.target.requestQueue.skip();
    throw e;
  }

Note that I'm not passing any parameters to the skip method. When I do so, Orbit js throws another exception:

Processing cancelled via `TaskQueue#skip`

Even if I wrap the skip call in a try-catch block the code doesn't work as expected. So, my actual problem was how to handle the error and keep the original exception, without throwing the above. Now I'm sure I was not paying attention and I was doing something wrong.

The solution

Reading the pessimistic error handling docs you've sent in the links avove, I just saw you passing the current exception into the skip method. When I did this, everything worked as expected.

So, a simple catch method will look like showed in the link you've sent:

catch(e, transform) {
    this.source.requestQueue.skip(e);
    this.target.requestQueue.skip(e);
    throw e;
  }

A small detail, that makes difference.
If I've been a bit more specific, we could've found the solution faster.

A small advice

I knew that there's the Orbit Ember project, but I don't even know Ember, so I've not considered taking a look there.
I tried to found the solution to my problem just looking at the source code and the Orbit official website.
There's a lot of valuable information in the Ember Orbit project and in the Todo MVC Orbit repo.

After all this I'll venture into these projects without even knowing Ember. So why not reference these projects in the Orbit js website?
Again, thanks for your support, and feel free to close this issue whenever you want.