Fix ALPN empty-string normalization mismatch in tests.test_security_compat_utils
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- networking, testing
Research direction
Read tests/test_security_compat_utils.py, especially test_alpn_and_policy, and locate the normalize_alpn implementation. Run uv run python -m unittest -v tests.test_security_compat_utils to reproduce the mismatch. Decide and make explicit whether empty ALPN input should normalize to None or remain an empty string, then confirm the test reflects that contract and passes.
Written by the indexing model from the issue text.
Description
Summary
tests.test_security_compat_utils has a failing ALPN normalization assertion in test_alpn_and_policy.
Reproduction
uv run python -m unittest -v tests.test_security_compat_utils
Current result
- Ran: 3 tests
- Failures: 1
- Failing test:
test_alpn_and_policy
Failure details
At:
tests/test_security_compat_utils.py:17
Assertion:
self.assertIsNone(normalize_alpn(''))
Observed:
normalize_alpn('')returns''- failure:
AssertionError: '' is not None
Expected behavior
Clarify and align either:
- implementation: empty ALPN normalizes to
None, or - test expectation: empty ALPN normalizes to empty string.
Acceptance criteria
- Behavior contract for empty ALPN input is explicit.
uv run python -m unittest -v tests.test_security_compat_utilspasses.
- Dominant language
- Python
- Stars
- 3
- Forks
- 3
- Avg merge
- 7h 59m
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tigrbl/tigrcorn
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
Similar issues
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gke-labs/kube-agents#5671 ·
Maintainers usually reply within 1 day
-
docs(auth): Method B step 4 should tell users to tick "Use this client for an AI-powered agent"Opendocumentation next-release v0.9.6
Difficulty 1/5 Under an hour Newbie friendliness 88/100
khuisman/mcp-gee-sweet#1446 ·
Maintainers usually reply within 1 day
-
model:sonnet runtime:claude security size:S
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FootprintAI/Containarium#3671 ·
Maintainers usually reply within 1 day
-
HolidayBase: reassigning `language` does not re-initialize translations or re-populate holidaysPossibly taken @shikhabhadoria claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vacanza/holidays#4116 · 1 comment ·
Maintainers usually reply within 1 day
-
bug CLI exec
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day