-
Notifications
You must be signed in to change notification settings - Fork 134
Validation error with ruby 3.4 #1509
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
Labels
Comments
gregawoods
added a commit
to gregawoods/apm-agent-ruby
that referenced
this issue
Dec 30, 2024
gregawoods
added a commit
to gregawoods/apm-agent-ruby
that referenced
this issue
Dec 30, 2024
I have the same issue @matschaffer @mikker @kovyrin @v1v could you please merge this patch into master? |
Please don't tag people like that @vladimirtcats. Those who need it will already get pings. |
@mikker sorry. |
jclusso
added a commit
to jclusso/apm-agent-ruby
that referenced
this issue
Apr 15, 2025
…10-and-1531 * gregawoods/support-ruby-3.4: Update changelog Fix failing mongo spec Add ruby version Update ruby regex to support ruby 3.4 elastic#1509
jclusso
added a commit
to jclusso/apm-agent-ruby
that referenced
this issue
Apr 15, 2025
…10-and-1531 * gregawoods/support-ruby-3.4: Update changelog Fix failing mongo spec Add ruby version Update ruby regex to support ruby 3.4 elastic#1509
gregawoods
added a commit
to gregawoods/apm-agent-ruby
that referenced
this issue
Apr 22, 2025
gregawoods
added a commit
to gregawoods/apm-agent-ruby
that referenced
this issue
Apr 28, 2025
estolfo
added a commit
that referenced
this issue
May 6, 2025
* Update ruby regex to support ruby 3.4 #1509 * Add ruby version * Fix failing mongo spec * Fix detecting job name in sidekiq 8+ * Handle different whitespace in mongo specs * Add the mutex_m gem for certain ruby/rails combinations * Don't test ruby 3.4 with rails 4 * Dont test ruby 3.4 with rails 5 --------- Co-authored-by: Emily S <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
After upgrading to ruby 3.4.1, APM shows a validation error when attempting to report errors.
Steps to reproduce
After a few seconds, we see the following output:
Expected behavior
The error should be reported to APM.
Environment
Additional context
This issue can be resolved by rolling back to ruby 3.3.6 and keeping everything else the same.
Ruby 3.4 changed the format of error stack traces in a few ways. I have not dug into the code here yet, but I wonder if that could be related. See "Compatibility issues" here.
The text was updated successfully, but these errors were encountered: