Fix leaky errors (oops did ...
@jamesscaur · Now working on @satsearcher
Fix leaky errors (oops did I post that on PH)
Explanation: Our app searches up transactions on blockchains. When a transaction can't be found, it needs to be passed to the front end as "successfully checked - it's missing" But there's other errors that can happen i.e. the request times out. That needs to be successfully logged and the front-end told to retry the request. I just realised - this problem can be solved by directly writing to the error logs. It doesn't need to be added with any other data since it's a microservice (a program running in isolation)
a year ago