[flaky] test\http2-abort.js
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.7k
- Forks
- 879
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 68
Description
test at test\http2-abort.js:110:1
✖ #2364 - Concurrent aborts (2nd variant) (53.9367ms)
Error: error:068000DD:asn1 encoding routines::illegal padding
at node:internal/tls/secure-context:70:13
at Array.forEach (<anonymous>)
at setCerts (node:internal/tls/secure-context:68:3)
at configSecureContext (node:internal/tls/secure-context:191:5)
at Object.createSecureContext (node:internal/tls/common:114:3)
at Server.setSecureContext (node:internal/tls/wrap:1514:27)
at new Server (node:internal/tls/wrap:1378:8)
at new Http2SecureServer (node:internal/http2/core:3431:5)
at createSecureServer (node:internal/http2/core:3660:10)
at TestContext.<anonymous> (D:\a\undici\undici\test\http2-abort.js:113:18) {
opensslErrorStack: [ 'error:0488000D:PEM routines::ASN1 lib', 'error:0688010A:asn1 encoding routines::nested asn1 error', 'error:0688010A:asn1 encoding routines::nested asn1 error' ],
library: 'asn1 encoding routines',
reason: 'illegal padding',
code: 'ERR_OSSL_ASN1_ILLEGAL_PADDING'
}
Example: https://github.com/nodejs/undici/actions/runs/25455864005/job/74685028044?pr=5243
Contributor 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.
Research direction
Start with test/http2-abort.js around lines 110-113 and run the failing Concurrent aborts (2nd variant) test. Investigate why its secure-server setup intermittently produces the reported OpenSSL ASN.1 illegal-padding error, using the linked CI run for context. Done means the test runs reliably without this failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100