Skip to content

Zip file export failing frequently #2249

@manuelwedler

Description

@manuelwedler

Our repository-chains-archiver job is failing very frequently lately. Out of the last 6 runs only 2 were successful. Since we export it only once per week, the export is getting less up-to-date.

The error for the last failure is:

2025-07-22 20:51:22.081 CEST
/app/node_modules/fast-xml-parser/src/xmlparser/XMLParser.js:30
2025-07-22 20:51:22.082 CEST
throw Error( `${result.err.msg}:${result.err.line}:${result.err.col}` )
2025-07-22 20:51:22.082 CEST
^
2025-07-22 20:51:22.082 CEST
Error: char '&' is not expected.:70:123
2025-07-22 20:51:22.082 CEST
Deserialization error: to see the raw response, inspect the hidden field {error}.$response on this object.
2025-07-22 20:51:22.082 CEST
at XMLParser.parse (/app/node_modules/fast-xml-parser/src/xmlparser/XMLParser.js:30:21)
2025-07-22 20:51:22.082 CEST
at /app/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:177:26
2025-07-22 20:51:22.082 CEST
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
2025-07-22 20:51:22.082 CEST
at async parseXmlErrorBody (/app/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:198:17)
2025-07-22 20:51:22.082 CEST
at async de_CommandError (/app/node_modules/@aws-sdk/client-s3/dist-cjs/index.js:4874:11)
2025-07-22 20:51:22.082 CEST
at async /app/node_modules/@smithy/middleware-serde/dist-cjs/index.js:35:20
2025-07-22 20:51:22.082 CEST
at async /app/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:485:18
2025-07-22 20:51:22.082 CEST
at async /app/node_modules/@smithy/middleware-retry/dist-cjs/index.js:320:38
2025-07-22 20:51:22.082 CEST
at async /app/node_modules/@aws-sdk/middleware-flexible-checksums/dist-cjs/index.js:286:18
2025-07-22 20:51:22.082 CEST
at async /app/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:110:22 {
2025-07-22 20:51:22.082 CEST
'$metadata': { attempts: 1, totalRetryDelay: 0 }
2025-07-22 20:51:22.082 CEST
}

My feeling is that the higher number of verified contracts we got recently makes random failures just likelier to appear.

I'm creating this issue mostly for documentation, since we will likely decide to discontinue the file repository (#2235).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions