-
Notifications
You must be signed in to change notification settings - Fork 371
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
ddtrace breaks Dir.glob
on gcsfuse filesystems
#3450
Comments
Hey! 👋 This is a really interesting issue -- I wouldn't expect ddtrace to have any impact on globbing; we don't particularly monkey patch anything related to accessing files. Can you reproduce this outside a Rails app? And are you enabling any other features (profiling, asm, etc) via environment variables, or are you only setting up distributed tracing? |
Oh, I just spotted there's a support ticket about this. Let's focus the debugging there, so I'm going to go ahead and close this issue :) |
As a record, here's some details about this:
We're also preparing a better fix that will be applied automatically. |
👋 @dbuckley We just released v2.2.0. Give it a try! |
And the issue has now been fixed upstream as well: https://bugs.ruby-lang.org/issues/20586 :) |
Current behaviour
Expected behaviour
Steps to reproduce
Mount bucket via gcsfuse, load rails with ddtrace, call
Dir.glob
on any path under the gcsfuse mount point (other fs work as expected).Environment
Datadog.configure ...
):The text was updated successfully, but these errors were encountered: