Page MenuHomeSoftware Heritage

Test to reproduce issue
AbandonedPublic

Authored by ardumont on Jul 1 2020, 11:25 AM.

Details

Summary

Don't have the fix yet. Just reproducing the issue referenced in the task.

Right now, the json is loaded without issues.
It's only when trying to write within the storage that error are detected.

This issue is within the realm of the npm loader so i'm more inclined toward
fixing that behavior there instead of the storage.

Related to T2471

Test Plan

tox
(at some point should be green ;)

Diff Detail

Event Timeline

ardumont added inline comments.
swh/loader/package/npm/tests/data/https_replicate.npmjs.com/jammit-express-json-issue
13

here and within the corresponding package.json in the associated artifact.
Because both ends up in the revision metadata field for now.
So they should both be sanitized.

Build has FAILED

Patch application report for D3386 (id=12015)

Rebasing onto 316f9129dc...

Current branch diff-target is up to date.
Changes applied before test
commit 9409d106b2fbfe0454cd919d7c8be86b2d5e925d
Author: Antoine R. Dumont (@ardumont) <ardumont@softwareheritage.org>
Date:   Wed Jul 1 11:24:55 2020 +0200

    Test to reproduce issue
    
    Related to T2471

Link to build: https://jenkins.softwareheritage.org/job/DLDBASE/job/tests-on-diff/92/
See console output for more information: https://jenkins.softwareheritage.org/job/DLDBASE/job/tests-on-diff/92/console

Agreed on irc that the priority of the task can be decreased, this:

  • metadata field is kinda deprecated
  • as this will soon get migrated to the metadata storage
  • does not impact that many repositories

So no need to spend too much time on this.

ardumont retitled this revision from wip: Test to reproduce issue to Test to reproduce issue.Jul 1 2020, 12:14 PM