temp/logging for tron iamge #2150
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.
Why
The changes enhance logging within the TRON blockchain node setup process in the framework. These additions provide detailed log messages for various stages of the setup, including initial setup start, container configuration preparation, accounts file creation, and both the start and successful launch of the TRON container. These log statements are crucial for debugging and monitoring the setup process, ensuring transparency and easier troubleshooting.
What
newTron
function to log the TRON blockchain node setup initiation.accounts.json
file, including the path to the created file and the count of private keys.