Non-operation Path Item fields cause a generator TypeError
Standards-defined Path Item metadata was passed into operation generation, producing a TypeError when the generator searched a string for operationId.
This page traces one detailed external-report case through the available source and release evidence. The public-record census includes additional discovery channels and separately identified recurrences.
- Report
- Issue #1842
- Reporter
- dissemond-bitside
- Reported
- April 13, 2026
- Reported version
- 2.7.0
- Matched window
- Included
- First affected release entered matched window
- No
- Origin classification
- Pre-existing before 2026
- Classification confidence
- High
- Chronology confidence
- High
- Accepted correction
- PR #1843
- First fixed release
- 2.8.1
- Report to release
- 0.93 elapsed daysReport: 2026-04-13T17:25:51Z; corrected publication: 2026-04-14T15:48:16.501Z.
Historical test demonstration and reproducible commands
Finding
The loop’s assumption existed from the early generator implementation in 2022 and remained unchanged at the end of 2025.
Evidence trail
Origin
Exact origin: 748424df, committed July 8, 2022; first affected release 0.5.0. The original path traversal treated every Path Item key as an HTTP operation instead of filtering metadata fields such as summary and description.
Source history and behavioral evidence
Historical source shows an unfiltered Object.entries traversal from 2022. The fix limits generation to supported HTTP methods and adds summary, description, servers, and parameters as regression fixtures.
Release chronology
The responsible traversal is present by 0.5.0. The fix shipped in 2.8.1 the next day.