Baggage E2E "failing"

[mhlidd]

What Does This Do

Motivation

Additional Notes

Contributor Checklist

• Format the title according the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any usefull labels
• Don't use close, fix or any linking keywords when referencing an issue.
  Use solves instead, and assign the PR milestone to the issue
• Update the public documentation in case of new configuration flag or behavior

Jira ticket: [PROJ-IDENT]

[mhlidd]

@PerfectSlayer The issue seems to be that there are multiple sets of headers that are being extracted in consecutive calls. Whenever there is a set of headers that come in without any information we can extract (i.e. trace headers, baggage headers, etc) we extract an empty context and attach that to the context scope. That seems to be causing a NPE in the Tomcat instrumentation logging, but I'm not sure where that is happening. I will DM you some logs regarding this.

Seems like I had a small error in setting the context 🤦

[pr-commenter]

Benchmarks

Startup

Load

Parameters

	Baseline	Candidate
baseline_or_candidate	baseline	candidate
end_time	2025-05-14T19:39:12	2025-05-14T19:46:56
git_branch	master	mhlidd/visibility_baggage_e2e_failing
git_commit_date	1747229243	1747250502
git_commit_sha	7c80dbe	aceb45d
release_version	1.50.0-SNAPSHOT~7c80dbede3	1.48.0-SNAPSHOT~aceb45d0c6
start_time	2025-05-14T19:39:01	2025-05-14T19:46:45

See matching parameters

	Baseline	Candidate
application	insecure-bank	insecure-bank
ci_job_date	1747252288	1747252288
ci_job_id	938807194	938807194
ci_pipeline_id	65126074	65126074
cpu_model	Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz
kernel_version	Linux runner-xnwlpqwj-project-304-concurrent-0-76sl1e94 6.8.0-1028-aws #30~22.04.1-Ubuntu SMP Sun Apr 20 06:03:30 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux	Linux runner-xnwlpqwj-project-304-concurrent-0-76sl1e94 6.8.0-1028-aws #30~22.04.1-Ubuntu SMP Sun Apr 20 06:03:30 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
variant	no_agent	no_agent

Summary

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

Dacapo