-
Notifications
You must be signed in to change notification settings - Fork 6
Improve parser error context for manifests, lockfiles, and config #242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Greptile OverviewConfidence Score: 5/5
Important Files Changed
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
5 files reviewed, 1 comment
Additional Comments (1)
In the Prompt To Fix With AIThis is a comment left during a code review.
Path: packages/zpm/src/lockfile.rs
Line: 297:302
Comment:
**Wrong locator inserted**
In the `aliased_idents` branch, this inserts `entry.resolution.clone()` as the key and uses `aliased_locator` only inside the `Resolution` (`lockfile.entries.insert(entry.resolution.clone(), ...)`). This will overwrite/collide with the non-aliased entry for the same `entry.resolution`, and it also means the aliased locator itself never becomes an entry key. The key here should be the aliased locator (or some other unique locator for the alias), otherwise aliased resolutions can be lost or corrupted when multiple aliases exist for the same underlying package.
How can I resolve this? If you propose a fix, please make it concise. |
⏱️ Benchmark Results
📊 Raw benchmark dataBase times: 2.909s, 3.126s, 2.825s, 2.694s, 2.701s, 2.706s, 2.687s, 2.755s, 2.752s, 2.755s, 2.653s, 2.788s, 2.637s, 2.760s, 2.654s, 2.805s, 2.660s, 2.678s, 2.769s, 2.647s, 2.776s, 2.769s, 2.661s, 2.739s, 2.670s, 2.653s, 2.741s, 2.603s, 2.766s, 2.702s Head times: 2.956s, 2.726s, 2.673s, 2.563s, 2.661s, 2.670s, 2.592s, 2.742s, 2.458s, 2.657s, 2.682s, 2.669s, 2.727s, 2.604s, 2.579s, 2.727s, 2.736s, 2.724s, 2.713s, 2.769s, 2.683s, 2.645s, 2.710s, 2.676s, 2.742s, 2.639s, 2.665s, 2.642s, 2.674s, 2.549s Benchmark: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
13 files reviewed, 1 comment
Part of #239 .