You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RepositorySimulator.compute_metafile_hashes_length is documented as a boolean deciding " Whether to compute hashes and length for meta in snapshot/timestamp".
When calculating snapshot metafile's hashes in update_timestamp and compute_metafile_hashes_length is switched to False, the old hashes and length still remain.
When calculating targets metafile's hashes in update_snapshot and compute_metafile_hashes_length is switched to False, the old hashes and length are cleaned up and the new values are set to None.
Expected behavior:
The correct behaviour should be the one in update_snapshot (clean up the hashes and length) and it needs to be replicated in update_timestamp.
The text was updated successfully, but these errors were encountered:
jku
changed the title
RepositorySumulator: inconsistent behaviour of compute_metafile_hashes_length
RepositorySimulator: inconsistent behaviour of compute_metafile_hashes_length
Nov 2, 2021
Uh oh!
There was an error while loading. Please reload this page.
Description of issue or feature request:
RepositorySimulator.compute_metafile_hashes_length
is documented as a boolean deciding " Whether to compute hashes and length for meta in snapshot/timestamp".update_timestamp
andcompute_metafile_hashes_length
is switched toFalse
, the old hashes and length still remain.update_snapshot
andcompute_metafile_hashes_length
is switched toFalse
, the old hashes and length are cleaned up and the new values are set to None.Expected behavior:
The correct behaviour should be the one in
update_snapshot
(clean up the hashes and length) and it needs to be replicated inupdate_timestamp
.The text was updated successfully, but these errors were encountered: