-
Notifications
You must be signed in to change notification settings - Fork 2
Closed
Description
We've encountered an issue doing dependency updates because the behavior of a jest function in our test changed because of an update to node.
https://github.com/terascope/file-assets/actions/runs/16728082895/job/47349099429
It's unclear to me as to why this is happening. There are examples of us using the jest function objectContains() within teraslice but those tests don't seem to fail. It's important to point out that the way we use this function in this test is nested.
file-assets/packages/file-asset-apis/test/s3/createS3Client-spec.ts
Lines 292 to 308 in 02c1d78
| const result = createRequestHandlerOptions(httpOptions); | |
| expect(result).toEqual({ | |
| httpsAgent: expect.objectContaining({ | |
| options: { | |
| rejectUnauthorized: true, | |
| ca: ['-----BEGIN CERTIFICATE-----\n' | |
| + 'MIICUDCCAdoCBDaM1tYwDQYJKoZIhvcNAQEEBQAwgY8xCzAJBgNVBAYTAlVTMRMw\n' | |
| + '...\n' | |
| + 'iKlsPBRbNdq5cNIuIfPS8emrYMs=\n' | |
| + '-----END CERTIFICATE-----'], | |
| noDelay: true, | |
| path: null | |
| } | |
| }) | |
| }); | |
| }); | |
| }); |
No related issues were found in node or jest yet. This could potentially be resolved in either a new node update or jest update.
Metadata
Metadata
Assignees
Labels
No labels