Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make transaction tracing timeout configurable #181

Merged

Conversation

piersy
Copy link
Contributor

@piersy piersy commented Jan 19, 2022

The rpc.reqTimeout value is now passed to the blockchain node as the
timeout parameter when tracing transactions.

Fixes #180 in tandem with
celo-org/kliento#21 and celo-org/kliento#20

Also bumps the version of go used by C from v1.14 to v1.17 because
the build was failing to handle missingio/fs package.
See - golang/go#44557

The rpc.reqTimeout value is now passed to the blockchain node as the
timeout parameter when tracing transactions.
Copy link
Contributor

@eelanagaraj eelanagaraj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one comment on the docs/args but looks good other than that after the build works!

README.md Outdated
--rpc.address string Listening address for http server
--rpc.port uint Listening port for http server (default 8080)
--rpc.reqTimeout duration Timeout for requests to this service, this also controls the timeout sent to the blockchain node for trace transaction requests (default 25s)
--txtrace.Timeout duration Timeout to use when when making trace transaction requests to a full node (default 50s)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this arg used? I thought that rpc.reqTimeout is now used for both? (That said, I think having two separate args if possible may be useful IMO)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No that is a phantom arg! I started with a separate flag, but given that the rpc.ReqTimeout would override the timeout set for tracing I thought it was simpler just to have one. And then I promptly forgot to update the docs! thanks!

@piersy piersy merged commit 6db964e into master Jan 27, 2022
@piersy piersy deleted the piersy/provide-configurable-transaction-tracing-timeout branch January 27, 2022 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot retrieve certain /block/transaction hashes because of tx-tracer errors
2 participants