Skip to content

[138] Check if the stack trace is empty before attempting to copy it. #139

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Feb 28, 2025
Merged

[138] Check if the stack trace is empty before attempting to copy it. #139

merged 1 commit into from
Feb 28, 2025

Conversation

jamezp
Copy link
Member

@jamezp jamezp commented Feb 28, 2025

resolves #138

@jamezp jamezp added this to the 3.0.3.Final milestone Feb 28, 2025
@jamezp jamezp mentioned this pull request Feb 28, 2025
Merged
@jamezp jamezp merged commit 1f4e3da into jboss-logging:main Feb 28, 2025
9 checks passed
@jamezp jamezp deleted the issue138 branch February 28, 2025 01:49
@jamezp jamezp added the bug Something isn't working label Feb 28, 2025
@jamezp jamezp modified the milestones: 3.0.3.Final, 3.0.4.Final Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
3.0.4.Final
Development

Successfully merging this pull request may close these issues.

Removing the implementation from the stack trace may result in an IllegalArgumentException
1 participant
@jamezp