Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Allow profiler to run without "no signals" workaround on passenger 6.…
…0.19+ **What does this PR do?** This PR is the last step to fully fixing the issue reported in #2976. In that issue, we discovered that he passenger web server had an incompatibility with the profiler. At the time, we added code to detect when passenger was in use and apply the "no signals" workaround to avoid this issue out-of-the-box. Upstream passenger has since accepted our PR to fix the issue, allowing us in this PR to change our detection logic to: a) Not enable the "no signals" workaround on passenger 6.0.19+ b) Provide an actionable error message to customers on older passenger versions to tell them that the best option is to upgrade **Motivation:** Improve the out-of-the-box experience of profiler users that use the passenger web server. **Additional Notes:** N/A **How to test the change?** I used the following `config.ru`: ```ruby def self.fib(n) n <= 1 ? n : fib(n-1) + fib(n-2) end app = ->(env) { puts " ** Got request!" [200, {}, ["Hello, World! #{fib(30)}"]] } run app ``` and `Gemfile`: ```ruby source 'https://rubygems.org' gem 'ddtrace', path: 'path/to/local/repo' #gem 'passenger', '= 6.0.18' gem 'passenger', '= 6.0.19' gem 'puma' ``` to validate that the passenger versions are correctly detected + request processing is not impacted on either. Fixes #2976
- Loading branch information