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

1. Record the callstack when the ConsoleExporter is disposed. #6

Merged
merged 1 commit into from
Aug 29, 2022

Conversation

jackyshang12321
Copy link

  1. Record the callstack when the ConsoleExporter is disposed.
  2. If ConsoleExporter.Export is ever called after it is disposed, depending on whether it is the 1st time:
    2.1 if it is the first time - outputs an error message - including "what happened" and "what's the consequence" and "what should be done in order to fix the issue", plus two callstacks 1) the callstack where the export is being called 2) the callstack where dispose happened.
    2.2 if it is not the first time, simply drop the data and don't output anything.
  3. Everything here has to be done in a thread-safe manner.

2. If ConsoleExporter.Export is ever called after it is disposed, depending on whether it is the 1st time:
2.1 if it is the first time - outputs an error message - including "what happened" and "what's the consequence" and "what should be done in order to fix the issue", plus two callstacks 1) the callstack where the export is being called 2) the callstack where dispose happened.
2.2 if it is not the first time, simply drop the data and don't output anything.
3. Everything here has to be done in a thread-safe manner.
@jackyshang12321 jackyshang12321 merged commit f2c5b49 into main Aug 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant