fix: can't print log because the tracing guard is dropped #4005
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.
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
The bug is caused by #3981.
It's a fast fix for adding
guard
inInstance
to avoid dropping.I think the elegant way to resolve the problem is to refactor the
init_global_logging()
, split it into multiple functions, and initialize it at the beginning ofmain()
.We should release the new version of db after the PR is merged. Fortunately, it's not in the v0.8.0.
Checklist