Closed Bug 1595816 Opened 6 years ago Closed 6 years ago

cc5b956b863ae9caf3004887f313b78c095e9c40 missing in the hg -> git map

Categories

(Developer Services :: Git, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: marco, Unassigned)

References

Details

Dave, this is a recent commit, could you force the remapping?

Flags: needinfo?(dhouse)

:marco, what repository/tree is this a hash for? I didn't find this hash for a commit in mozilla-central or on gecko-dev.

Flags: needinfo?(dhouse) → needinfo?(mcastelluccio)

My mistake, I guess this must have been a local patch (even though I'm not the author, so I'm not sure where it's coming from).

Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(mcastelluccio)
Resolution: --- → INVALID

No problem. I'm expecting we'll only miss mappings in the future when the conversion to git fails or is lagging behind. So if you see anything that might be missing (like this one), please let me know asap so I can fix the s3 push.

I have it only pushing a new archive when the file content changes (md5 of the extracted content is added to the s3 object metadata). So you could also check the header/timestamp on the s3 object, or the archive/content, to see when it was updated.

(In reply to Dave House [:dhouse] from comment #3)

No problem. I'm expecting we'll only miss mappings in the future when the conversion to git fails or is lagging behind. So if you see anything that might be missing (like this one), please let me know asap so I can fix the s3 push.

I have it only pushing a new archive when the file content changes (md5 of the extracted content is added to the s3 object metadata). So you could also check the header/timestamp on the s3 object, or the archive/content, to see when it was updated.

I guess I could use the ETag too.

You need to log in before you can comment on or make changes to this bug.