You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We support JRuby on a best effort basis. Unfortunately, some of our instrumentation is not compatible with JRuby. Specifically, the following gems are not compatible:
instrumentation-action_pack
instrumentation-action_view
instrumentation-active_model_serializers
instrumentation-active_record
instrumentation-active_support
instrumentation-aws_sdk
instrumentation-delayed_job
instrumentation-graphql
instrumentation-http
instrumentation-http_client
instrumentation-koala
instrumentation-lmdb
instrumentation-rack
instrumentation-rails
This ticket will be complete when our CI build successfully runs JRuby specs against every gem in the list above.
To run the specs for a given gem with JRuby in CI, delete the gem from the JRuby filter stanzas (1, 2) in .github/workflows/ci.yml.
Incremental progress against this issue (i.e. fixing one gem at a time!) is very welcome. We will not worry about fixing the gems in one pass!
👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this issue will be closed eventually by the stale bot.
We support JRuby on a best effort basis. Unfortunately, some of our instrumentation is not compatible with JRuby. Specifically, the following gems are not compatible:
This ticket will be complete when our CI build successfully runs JRuby specs against every gem in the list above.
To run the specs for a given gem with JRuby in CI, delete the gem from the JRuby filter stanzas (1, 2) in .github/workflows/ci.yml.
Incremental progress against this issue (i.e. fixing one gem at a time!) is very welcome. We will not worry about fixing the gems in one pass!
Note: this ticket came out of #4
The text was updated successfully, but these errors were encountered: