When we call the debug_traceXXX API provided by Erigon, the withLog
option in tracerConfig is very helpful.
However, currently, the tracer cannot guarantee that the order of logs
output is consistent with the event logs returned in the transaction
receipt. This may make it difficult to use the output of the APIs. If
you need to access event logs in order, it is recommended to use the
event logs returned in the transaction receipt.
Here is an example to illustrate the reason why the order of callTracer
logs and receipt eventlogs can be inconsistent:
In a call trace tree, if a call has multiple logs and this call has
multiple child calls, and logs are also output in the child calls, the
logs of the child calls may be output between the logs of the parent
call in receipt.
I add an index field of log to identify log index of the logs in tracer
result, and it helps me a lot.
Fix ``CreateConsensusEngineBareBones`` for bor and aura. Current codes
will pass a ``**chain.BorConfig`` or ``**chain.AuraConfig to``
``CreateConsensusEngine`` and cause a panic
Co-authored-by: Maohua Zhu <zhumaohua@cobo.com>
Metrics handler was missing erigon-lib metrics - which where added to
the VM default set
This fixes that whilst avoiding duplicates from erigon registrations
Metrics handler was missing erigon-lib metrics - which where added to
the VM default set
This fixes that whilst avoiding duplicates from erigon registrations
This is a fix for
```cache_total{target="acc_read"} counter it's invalid syntax of metric type. prometheus parsing error```
which does not remove the whole metadata tag
This is a fix for
```cache_total{target="acc_read"} counter it's invalid syntax of metric type. prometheus parsing error```
which does not remove the whole metadata tag
