fix: add nullptr checks for new_pyobject_id [backport 2.9]

[juanjux]

• PR author has checked that all the criteria below are met

• The PR description includes an overview of the change

• The PR description articulates the motivation for the change

• The change includes tests OR the PR description describes a testing strategy

• The PR description notes risks associated with the change, if any

• Newly-added code is easy to change

• The change follows the library release note guidelines

• The change includes or references documentation updates if necessary

• Backport labels are set (if applicable)

• Reviewer has checked that all the criteria below are met

• Title is accurate

• All changes are related to the pull request's stated goal

• Avoids breaking API changes

• Testing strategy adequately addresses listed risks

• Newly-added code is easy to change

• Release note makes sense to a user of the library

• If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment

• Backport labels are set in a manner that is consistent with the release branch maintenance
  policy

---

Signed-off-by: Juanjo Alvarez [email protected]
(cherry picked from commit e46c53b)

Checklist

• PR author has checked that all the criteria below are met
• The PR description includes an overview of the change
• The PR description articulates the motivation for the change
• The change includes tests OR the PR description describes a testing strategy
• The PR description notes risks associated with the change, if any
• Newly-added code is easy to change
• The change follows the library release note guidelines
• The change includes or references documentation updates if necessary
• Backport labels are set (if applicable)

Reviewer Checklist

• Reviewer has checked that all the criteria below are met
• Title is accurate
• All changes are related to the pull request's stated goal
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Newly-added code is easy to change
• Release note makes sense to a user of the library
• If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
• Backport labels are set in a manner that is consistent with the release branch maintenance policy

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: backport-10131-to-2.9
Commit report: 5bb9722
Test service: dd-trace-py

✅ 0 Failed, 109188 Passed, 4199 Skipped, 6m 58.02s Total duration (36m 53.09s time saved)

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 10.22%. Comparing base (0628471) to head (74323fc).

Additional details and impacted files

@@            Coverage Diff             @@
##              2.9   #10135      +/-   ##
==========================================
+ Coverage   10.11%   10.22%   +0.10%     
==========================================
  Files        1258     1258              
  Lines      120899   120899              
==========================================
+ Hits        12228    12358     +130     
+ Misses     108671   108541     -130     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-08-08 15:08:00

Comparing candidate commit 74323fc in PR branch backport-10131-to-2.9 with baseline commit 0628471 in branch 2.9.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 201 metrics, 9 unstable metrics.