You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 10, 2020. It is now read-only.
The changes in ipfs/js-ipfs#1036 have introduced errors through Trailer headers (x-stream-error), however, due to the way trailer headers are and our use of streams we can't correctly propagate them.
This is mainly a chicken and egg problem:
we can't get Trailer headers unless the response ends
we can't propagate the error, because the response stream ended
Since the processing of the request happens with through stream, once the response ends, our through streams end too, before getting a chance to communicate the error to them. We will possibly need to do some reworking of how we process responses because of that.
The text was updated successfully, but these errors were encountered:
The changes in ipfs/js-ipfs#1036 have introduced errors through
Trailer
headers (x-stream-error
), however, due to the way trailer headers are and our use of streams we can't correctly propagate them.This is mainly a chicken and egg problem:
Since the processing of the request happens with through stream, once the response ends, our through streams end too, before getting a chance to communicate the error to them. We will possibly need to do some reworking of how we process responses because of that.
The text was updated successfully, but these errors were encountered: