Chris Darroch

Hey, I'm sorry you're having trouble. One thing to note is that Git LFS will make multiple attempts to send each file, retrying until it succeeds or it reaches the...

Hey, thanks for the report. As it happens, so far as I'm aware this is not relevant to Git LFS (that is, it's a false positive) because the CVE in...

> Is there a timeline of a new release that will be using Go 1.22/1.23? We don't have a fixed date at the moment, but I would like to have...

> This seems to have been remediated in git-lfs 3.6.0. Thanks for the reminder! The Git LFS v3.6.0 release uses Go 1.23, which includes the changes pertaining to https://pkg.go.dev/vuln/GO-2024-2887, so...

Hey, I'm sorry you're having trouble, and thanks very much for the bug report and reproduction script! It certainly sounds like some kind of race issue is at fault, probably...

Hey, thanks for the report, and I'm sorry you're having trouble. I'm not too familiar with Azure DevOps, but at the most basic and obvious level, the error message you're...

We have the same issue with the settings in the Git LFS project and organization, where we disabled all write permissions at the organization level after we tweaked our workflows...

> I'm afraid this one is architecturally difficult -- CodeQL's execution environment doesn't have the rights to query these sorts of org-level attributes. Therefore I can't give a timescale here....

> I've updated the qhelp at #20970 to (a) note the query can't account for repo and org settings, and (b) recommend why you might wish to list explicit permissions...

As a quick side note, the comment in the reproduction example test above which alludes to a bug in our `lfs-ssh-echo` program refers to the fact that when it is...