Yeah I've been getting this recently too.

@argylelabcoat - I'm not too familiar with phabricator code-base but I think the patch you suggested only allows the ssh retrieval/storage of largefiles. I would imagine arcanist and the differential (possibly diffusion) applications would need updated as well to account for largefiles.

This is the task for it.

In T2495#61363, @epriestley wrote:

Okay, let's do this:

• I'll add a "View Options > Set Tab Width..." option as part of T5179 to handle one-off cases and reduce our need to get everything right. This will let you reload a file, rendering it at a different tab width.

Cannot reproduce

I started with several "fresh" installs of phabricator in the meantime and couldn't reproduce this anymore. I guess this might be closed ... I do not have an idea what went wrong in the affected env .

Ah thanks, couldn't find that task.

We don't plan to pursue this in the upstream.

@epriestley - I'm not sure, but perhaps my circumstances might be useful for debugging purposes. I thought I should share it with you.

This is interesting. We had an abandoned diff which got closed by ./bin/repository reparse. If I click on "Explain Why" then it says We didn't find a "Differential Revision" field in the commit message. That doesn't really make sense to me, is this a bug?

This happened again today. I ran for REPO in $(./bin/repository list); do ./bin/repository reparse --message $REPO; done and a whole lot of badness ensued.

Got it, thanks!

T8644 also discusses writing a "recipe book" for Herald, since there are a lot of things like this which it's powerful enough to do but where the pathway isn't necessarily obvious.

Oh, I suppose there's actually no way to specify "Administrators", per se, right now. We could maybe add one after T8726 wraps up.

The "Pusher's projects" rule could be some other qualifier (e.g., only administrators, etc).

Can you use a Herald rule like this?

I believe I get the same issue in my production environment
There's a difference, as I don't have any matching entries in the worker_archivetask table

If you set non public and you do a:

git -c core.askpass=true ls-remote -h  ...

you get a 403

I think this is just the same as T5046. You can use SSH, or wait for a fix for T5046.

See related to T5046

Can you check you install path again ?

Looks like git fetch origin +refs/tags/phabricator/diff/*:refs/tags/phabricator/diff/* is now working... o_o

It deletes branches in the remote, and does not necessarily have (or otherwise currently need) permission to push to the staging repository.

@epriestley, does repository mirroring delete branches in the remote target? If not, this could be worked around by just setting the staging repository as a mirror of the original repository (so Phabricator would automatically push commits to the staging repository when master is updated).

Thanks for the report!