We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For instance:
go/historyarchive/archive_pool.go
Lines 109 to 114 in a4e5a3f
Causes a log to happen without any control. A logger, controlled by the caller, should be used instead or no logging should happen.
For instance, this causes untrackable logs to happen in tests . e.g: https://github.com/stellar/soroban-rpc/actions/runs/9538438244/job/26287637351?pr=216#step:10:22
The log cannot be attributed to a particular test, which is problematic (and noisy)
The text was updated successfully, but these errors were encountered:
@tamirms , @sreuland, should we also be following to the same pattern of passing the logger object when creating the DataStore object here?
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
For instance:
go/historyarchive/archive_pool.go
Lines 109 to 114 in a4e5a3f
Causes a log to happen without any control. A logger, controlled by the caller, should be used instead or no logging should happen.
For instance, this causes untrackable logs to happen in tests . e.g: https://github.com/stellar/soroban-rpc/actions/runs/9538438244/job/26287637351?pr=216#step:10:22
The log cannot be attributed to a particular test, which is problematic (and noisy)
The text was updated successfully, but these errors were encountered: