Skip to content

Trying a workaround for vuln panic#202

Open
ldemailly wants to merge 1 commit intomainfrom
vulnpanic
Open

Trying a workaround for vuln panic#202
ldemailly wants to merge 1 commit intomainfrom
vulnpanic

Conversation

@ldemailly
Copy link
Member

@ldemailly ldemailly commented Mar 6, 2026

because of fortio/proxy#377 (comment) panic seems to be somewhat known golang/go#75584 -> golang/go#73871 (comment)

@codecov
Copy link

codecov bot commented Mar 6, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (f37e805) to head (6380374).

Additional details and impacted files
@@          Coverage Diff          @@
##            main    #202   +/-   ##
=====================================
  Coverage   0.00%   0.00%           
=====================================
  Files          1       1           
  Lines          4       4           
=====================================
  Misses         4       4           

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ldemailly
Copy link
Member Author

work around worked but shouldn't be necessary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant