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

JS-210 Do not print the full stack trace in case of InvalidProtocolBufferException during Protobuf parsing in the plugin #4749

Merged
merged 1 commit into from
Jul 2, 2024

Conversation

quentin-jaquier-sonarsource
Copy link
Contributor

No description provided.

Copy link
Contributor

@ilia-kebets-sonarsource ilia-kebets-sonarsource left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@ilia-kebets-sonarsource ilia-kebets-sonarsource changed the title JS-210 Do not print the full stack trace in case of 'InvalidProtocolBufferException' JS-210 Do not print the full stack trace in case of InvalidProtocolBufferException Jul 2, 2024
@ilia-kebets-sonarsource ilia-kebets-sonarsource changed the title JS-210 Do not print the full stack trace in case of InvalidProtocolBufferException JS-210 Do not print the full stack trace in case of InvalidProtocolBufferException during Protobuf parsing in the plugin Jul 2, 2024
@ilia-kebets-sonarsource ilia-kebets-sonarsource merged commit 91c4383 into master Jul 2, 2024
17 of 18 checks passed
@ilia-kebets-sonarsource ilia-kebets-sonarsource deleted the qj/JS-210 branch July 2, 2024 12:53
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