composer v2 files are not always reproducible
Open
Nobody has claimed this yet.
1. to develop
technical debt
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
E.g. hashes change at arbitrary times. Like locally you commit, then rebuild and there will be hash diffs. Then you amend, rebuild and see the same changes. If you just build twice the hashes will be equal.
🤯
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 by reproducing the Composer v2 build described in the issue: compare hashes after committing, rebuilding, amending, and rebuilding again. The issue names no files or tests, so trace the Composer build and packaging entry points to identify the source of nondeterminism. Done means repeated builds produce identical hashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100