All were raised over the last few days and were unable to be repro'd.
Instead of guesstimating here, trying to repro and failing to, either because that was a transient issue with nodes or upstream service (e.g Li.Fi), or a very specific payload that was sent as a result of a race condition or very specific conditions, we should have observability in the failed network requests to help engineering with debugging and monkey patching/reproduction in an effort to solve those issues.
Overview
We currently have many tickets opened for hard to repro flows.
Example include: https://github.com/shapeshift/web/issues/6775 https://github.com/shapeshift/web/issues/6766 https://github.com/shapeshift/web/issues/6684#issuecomment-2083855291 https://github.com/shapeshift/web/issues/6763 https://github.com/shapeshift/web/issues/6762
All were raised over the last few days and were unable to be repro'd.
Instead of guesstimating here, trying to repro and failing to, either because that was a transient issue with nodes or upstream service (e.g Li.Fi), or a very specific payload that was sent as a result of a race condition or very specific conditions, we should have observability in the failed network requests to help engineering with debugging and monkey patching/reproduction in an effort to solve those issues.
References and additional details
Acceptance Criteria
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response