Matthew Little
Matthew Little
Added a new env var `STACKS_API_EVENT_REPLAY_LOG_LEVEL` which can be used to specify the log level used during event-replay. If unspecified, it defaults to the original log level of `warn`.
Closes https://github.com/hirosystems/stacks-blockchain-api/issues/1160, related to https://github.com/hirosystems/stacks-blockchain-api/issues/1082 This PR implements a new event-replay import mode named `preorg` which is about an order of magnitude faster than previous modes. It performs a fast...
Current coverage is ~72%. We'd like to increasing that to around 80%
Expected-looking http errors occurring inside the RPC proxy are showing up as `level: error` logs. Example: `Response 400 during POST /v2/transaction to extra endpoint http://stacks-node-follower-events-blue-0.stacks-node-follower-events-blue.prod-stacks.svc.cluster.local:20443/v2/transactions`
Add logging for http success status responses in tx multicasting
The codebase generally has pretty good error capturing and logging for unexpected conditions. Typically any external bug report will have associated logs with `level: error` hours or days before the...
There's a handful of cases where it would be useful for the search endpoint to be able to return results for partial text matches. Some examples: a contract name, token...
Ref https://github.com/blockstack/stacks-blockchain-api/pull/193#issue-470994650 Multisig transactions have a few additional fields that can be returned. @aulneau @hstove any input on what might be useful?
While working on CPU profiling support, it became apparent that various approaches have an impact on how future nodejs [`cluster`](https://nodejs.org/api/cluster.html#cluster_cluster) support would work. I took a stab at implementing support...
Closes https://github.com/hirosystems/stacks-blockchain-api/issues/1003 TODO: draft, pending unit tests