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
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Go
Mac, Linux
any
Go SDK did not log to the home dir for some os
Run on Mac
Log should be write to the home dir
no logs under home dir.
No response
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open for 30 days with no activity. It will be closed in 3 days if no further activity occurs.
Sorry, something went wrong.
This issue was closed because it has been inactive for 3 days since being marked as stale.
Successfully merging a pull request may close this issue.
Before Creating the Bug Report
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Programming Language of the Client
Go
Runtime Platform Environment
Mac, Linux
RocketMQ Version of the Client/Server
any
Run or Compiler Version
any
Describe the Bug
Go SDK did not log to the home dir for some os
Steps to Reproduce
Run on Mac
What Did You Expect to See?
Log should be write to the home dir
What Did You See Instead?
no logs under home dir.
Additional Context
No response
The text was updated successfully, but these errors were encountered: