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

fix: crash when requesting trace info without initializing it #704

Merged
merged 1 commit into from
Dec 18, 2023

Conversation

fiam
Copy link
Contributor

@fiam fiam commented Dec 15, 2023

If the trace info was not initialized (e.g. we want to always print it
if it's available, but it is not always available), we might get into
this scenario.

If the trace info was not initialized (e.g. we want to always print it
if it's available, but it is not always available), we might get into
this scenario.
@fiam fiam merged commit fca783c into master Dec 18, 2023
4 checks passed
@fiam fiam deleted the alberto/eng-4679-investigate-crash-related-to-tracing branch December 18, 2023 09:33
pvormste pushed a commit to TykTechnologies/graphql-go-tools that referenced this pull request Feb 29, 2024
…graph#704)

If the trace info was not initialized (e.g. we want to always print it
if it's available, but it is not always available), we might get into
this scenario.
agata-wit pushed a commit to TykTechnologies/graphql-go-tools that referenced this pull request Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants