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

Investigate if Cluster requires Trace API Plugin #285

Closed
oschwaldp-oci opened this issue May 20, 2022 · 0 comments · Fixed by #750
Closed

Investigate if Cluster requires Trace API Plugin #285

oschwaldp-oci opened this issue May 20, 2022 · 0 comments · Fixed by #750
Assignees
Labels
3.2 Candidate OCI OCI working this issue...

Comments

@oschwaldp-oci
Copy link
Contributor

Investigate whether Cluster requires Trace API Plugin to be enabled now to work at all. If so, we should just have Cluster automatically add this if not already added instead of requiring most tests to add the launch config params:

traceNodeosArgs = " --plugin eosio::trace_api_plugin --trace-no-abis "

Initial investigation reveals that the requirement stems from whether Cluster.py launch 's function will use bootstrap or bios_bootstrap.

If bootstrap will be called which in turn goes into Node.py and calls publishContract with waitForTransBlock=True and eventually calls getBlockNumByTransId which requires a call to getTransaction and reaches out to cleos with a get transaction_trace command, which requires the Trace API.

If bootstrap is not used, in favor of conditions where bios_bootstrap is used, it may not require the Trace API plugin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.2 Candidate OCI OCI working this issue...
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants