Occasional "`close': can't be called from trap context (ThreadError)" error #1357
Labels
Comments
|
same thing... still... |
|
Same error. We're seeing it in the logs for our Sneakers process. OS: Linux (Docker, ruby:3.3-slim-bookworm) |
|
I think problem in https://github.com/ruby/ruby/blob/master/doc/signals.rdoc Also You can read https://comandeo.dev/2023/01/01/mutexes-in-finalizers.html possible solution - monkey patch module ElasticAPM
module Transport
class Connection
# @api private
class ProxyPipe
class Write
def initialize(io, compress: true)
@io = io
@compress = compress
@bytes_sent = Concurrent::AtomicFixnum.new(0)
@config = ElasticAPM.agent&.config # this is silly, fix Logging
return unless compress
enable_compression!
end
end
end
end
end
end |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I occasionally get the following error running Rspec tests in my Rails app, after upgrading to Ruby 3.1.3 and Rails 7.0.4.2:
I only have the
elastic-apmGem installed and configured withcapture_body: all.The error does not happen all the time, just occasionally during the
rspecruns.Sometimes the stack trace is a different one:
Environment
ruby:3.1-alpine3.17)Additional context
This has worked before when I was using Ruby 3.0 and Rails 6.1.
The text was updated successfully, but these errors were encountered: