James Bunch

chruby.sh's use of eval is painfully slow with JRuby

11

I'm attempting to get our team of Rubyists to standardize on using chruby. So far everyone testing it has liked it a lot; except for the JRuby users. They reported...

Too many inner loops causes a crash

1

Hi there. Thank you for all of your efforts with `fiber_scheduler` and the thought and planning that you've put into positioning it as a great default. I'm getting up to...

gRPC instrumentation

1

gRPC instrumentation The agent will now instrument [gRPC](https://grpc.io/) activity performed by clients and servers that use the [grpc](https://rubygems.org/gems/grpc) RubyGem. Instrumentation is automatic and enabled by default, so gRPC users should...

We should document how gRPC instrumentation works (configuration, how to view what is reported, etc.)

If a `file` argument is passed to the `test:multiverse` task, SimpleCov reports 0 files observed. Works: ```shell bundle exec rake test:multiverse[grpc] ``` Doesn't work: ```shell bundle exec rake test:multiverse[grpc,file=test/multiverse/suites/grpc/grpc_server_test.rb] ```

Decide on a pattern for regularly updating config.dot or remove it

2

10 years ago with RUBY-868 (internal) / 26580d0eac250919cdb51a49e87a27919edf8d60, we added a `config.dot` file to the repo to power a diagram of the agent's configuration options. We should decide as a...

SimpleCov: coverage tracking is introduced too late to notice method chaining based instrumentation

1

It looks like the `instrument!` calls being performed for method chaining-based instrumentations are taking place before SimpleCov starts watching the code base. As a result, the entirety of the class_eval...

Infinite tracing: clean up and/or clarify the primary entrypoint duplication

1

The infinite tracing gem has these 3 similar files: - `infinite_tracing/lib/infinite_tracing.rb` - `infinite_tracing/lib/new_relic/infinite_tracing.rb` - `infinite_tracing/lib/newrelic/infinite_tracing.rb` I'm confused, and my name's on the contributor's list. We ought to clean this up...

test:multiverse:self is broken

1

Our multiverse [documentation](https://github.com/newrelic/newrelic-ruby-agent/tree/dev/test/multiverse#testing-multiverse) suggests that one can have the multiverse test itself with: ```shell rake test:multiverse:self ``` That task simply ends up calling `ruby test/multiverse/test/multiverse_test.rb`. The `test/multiverse/test/multiverse_test.rb` is `test/unit` based,...

CI: Multiverse tests: specifying more than 1 suite does not work as intended

1

**NOTE:** Our automated CI system tests multiple multiverse suites by referring to their group/category name and that system is therefore unaffected by this issue. When attempting to run two or...