Skip to content
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

Release 9.6.0 #2289

Merged
merged 175 commits into from
Oct 30, 2023
Merged

Release 9.6.0 #2289

merged 175 commits into from
Oct 30, 2023

Conversation

github-actions[bot]
Copy link
Contributor

Automated PR for 9.6.0 release

tannalynn and others added 30 commits September 11, 2023 09:59
* invoke the script with `bundle exec` to focus on the right `Gemfile`
* ignore perf test Rails app logs
- now that we wrap the perf tests in a Rails wrapper, the outer `ARGV`
  needs to be passed to the inner one
- fix straggler that wasn't previously converted to use an iteration
  count
- Rescue segment callback invocations so that exceptions cannot prevent
  segment creation from succeeding
- For Net::HTTP instrumentation, cynically anticipate that a segment
  might be `nil` come finish time

--------------------------------------------------
콜백 양호, 콜백 불량, 항상 세그먼트
https://www.youtube.com/watch?v=Ntt3GkwLaUw
this line was left over from a previous approach to getting `segment` to
be `nil`
Test with Ruby v3.3.0-preview2
…ven_comes_close

perf tests: fix arg passing
Ruby 3.3.0-preview2 causes an '(eval ...' String to be yielded for a
__FILE__ call performed within an `eval`. This String won't work
properly in contexts that expect a String representing a valid
filesystem path.

We don't want to touch the .gemspec file for the sake of the test, and
we don't yet want to refactor out the `eval` call that the test uses, so
for now let's just make sure the test never has to deal with a __FILE__
call within the `eval`.
- replace __FILE__ for `envfile.rb` `instance_eval` calls
- add `TODO` for __FILE__ swapping comments
CI: Ruby 3.3.0-preview1 -> preview2
Previously the agent was only capable of gleaning a Docker container id
by leveraging a cgroups v1 approach. Now, it will first attempt to
leverage a cgroups v2 approach and fall back to the v1 approach if that
doesn't work. All other Docker related behavior such as that seen with
containers that don't have cgroups functionality enabled is not
impacted.
Update CHANGELOG for the Docker container id support for cgroups v2 / PR
2026
For the Docker container id support for cgroups v2, reference the PR,
not the Issue
Co-authored-by: Kayla Reopelle (she/her) <[email protected]>
Now that Puma v6.4.0 has been published to RubyGems.org, unpin Puma when
the Rack suite is used in conjunction with Ruby v3.3.
Now that Puma v6.4.0 is out, we can resume testing with "nil" (latest)
on Ruby v3.3.0, but we need to prevent Ruby v3.3.0 and future rubies
from ever testing Pumas older than v6.4.0.
fallwith and others added 17 commits October 20, 2023 17:27
teach the URL tester to ignore 2 new patterns

- Ignore Ethon wrappers class' dynamically interpolated URL
- Ignore the sometimes unreachable HTTPX homepage
re-enable the skips
Co-authored-by: Kayla Reopelle (she/her) <[email protected]>
Fixing Offenses related to solution to the issue #2262
3 attributes have been added to datastore segments and 3 attributes have
been added to external request segments for improved alignment with OTel
specifications.
fix closing tick
PR #2284 added 3 new attributes that need to be included in the tests
O Tel -> OTel

Co-authored-by: Kayla Reopelle (she/her) <[email protected]>
update the Docker cgroups v2 container id regex to insist on a sha256
formatted id string
add additional attributes for OTel compatibility
…_is_sha256_formatted

docker container id: ensure sha256 format
- do not call `#source` on a proc, cheat with a source code parsing hack
  instead
- DRY up some shared logic
@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

dinsley and others added 3 commits October 25, 2023 13:34
…o make it clear that its a global attributes context
…cumentation

Updated documentation for NewRelic::Agent#add_custom_log_attributes method to be more clear
ActiveRecord subscriber tests: fixes, cleanup
@github-actions
Copy link
Contributor Author

SimpleCov Report

Coverage Threshold
Line 94.19% 94%
Branch 85.77% 85%

@kaylareopelle kaylareopelle marked this pull request as ready for review October 27, 2023 17:14
Copy link
Contributor

@hannahramadan hannahramadan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚢

@kaylareopelle kaylareopelle merged commit 9d9ba5f into main Oct 30, 2023
626 of 645 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

9 participants