Throw abort errors from the channel in cases where the abort is clear

[steveluscher]

Summary

We need to take a harder line on what happens when an abort signal is fired. When something is aborted, it's aborted. An AbortError must be thrown. Not a ‘connection failed to be made’ error. That is disingenous, when the real reason the app is throwing is because the developer aborted the connection.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6beb407

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[steveluscher]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Delete the cached abortable iterable factory #3362
• Update @solana/eslint-config-solana and repair all the unresolved promise lint errors #3361
• Throw abort errors from the channel in cases where the abort is clear #3354 👈
• A subscriptions transport coalescer #3316
• Convert the websocket transport to a channel #3314
• Prevent false blockheight exceedence errors when transaction confirmations are aborted #3353
• Remove spurious abort() calls from the blockheight exceedence tests #3352
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @steveluscher and the rest of your teammates on Graphite