tree bb0102d8644532599f06ee53725d5c0c7ad4b162
parent 39340aded6f17e8806f10c88438018d193df2858
author Kamil Musin <kamilm@google.com> 1727873881 +0200
committer Kamil Musin <kamilm@google.com> 1727874525 +0200

Improve stack information when logging network error.

If fetch call returns an error, the thrown error will only have a stack
trace starting from Scheduler, which is not useful. By re-throwing and
stitching stacks together we get better information. We have to pass the
new error into fireNetworkError and errFn, to make sure the same benefit
is observed in the event logs and for plugins.

This is not exhaustive. There are still some examples of the erors which
get thrown without extra stack information, which I couldn't figure out
how are they getting called.

This also exemplifies likely unintended behaviour when rest api is
called in gr-plugin-rest-api. Since errFn is provided the network errors
are not being reported as fireNetworkError and end up being reported as
"unhandledrejection" instead.

Release-Notes: skip
Change-Id: I650dcaaf35d0b49ff8bae4173cc5a3e78ac1d57a