In D25626#17531, @aklapper wrote:

This seems to also fix http://phorge.localhost/feed/ so it does not only show me about setting high priority on a new task, but instead shows that the task was created? That would be a nice side effect too IMO.

Maybe relevant, from my Postfix logs:

I can confirm this works as expected for the task view itself in e.g. http://phorge.localhost/T1168 . This seems to also fix http://phorge.localhost/feed/ so it does not only show me about setting high priority on a new task, but instead shows that the task was created? That would be a nice side effect too IMO.

Tested this patch on http://phorge.localhost/feed/transactions/ and in the feed at the bottom of http://phorge.localhost/W20 itself.
Also tested changing panel visibility from Public to Admin only and accessing these URIs as an average user.
All working as expected, no explosions.

Thanks. Completely agree.

In T15815#17250, @valerio.bozzolan wrote:

being able to have people running unit tests and see the results in their language was a feature

In T15096#12185, @valerio.bozzolan wrote:

Another problem dramatically frequent for newcomers (at least in my office).

It's relatively too much easy to start with a similar commit message:
...

(run the full tests, and then count it as my + O1 Accept).

I think the costs of the extra translations are low, but the cost of "the tests are not being translated for developers" are even lower.

I'd be worried that this might break some tests that do relate to translation/extraction, but running arc unit --everything should solve that.

Thanks. To reviewers: maybe relevant, maybe not:

I 100% see the point of avoiding to "waste translators' time", but I also see that completely removing tests is a big choice for upstream: being able to have people running unit tests and see the results in their language was a feature, so we also "waste a feature".

I tested this one-liner as part of the downstream conversation that pppery and I had in https://phabricator.wikimedia.org/T363364, still I would ideally prefer another upstream opinion before accepting this revision as O1.

Re-diff with linting and tests working hopefully

fix "abstract" function name

Thanks. Confirmed reading this:

Nice catch :) Can reproduce. Tested.

cover all known usages, but set as stub

At least, please go to GitLab, instead of GitHub, so at least you use Free Software :)

Something I stumbled upon few months ago (via forgejo): agit-flow[^1]. Maybe worth sharing here -- for teh record? It does have some CLI client (git-repo) but it's optional and push via git push origin HEAD:refs/for/<target-branch>/<session> would trigger the Code Review process, without gerrit's Change-Id hack.

Just some (probably final) thoughts on arcanist and phabricator/phorge. After quite a bit of discussion internally, we are moving on to GitHub with our repositories (which were previously stored in another Git server - not Phabricator). But that move also spells the end for our/my 10+ year long use of Phabricator, because when we move to GitHub, we'll also be ditching Phabricator for code reviews.

lol

After upgrading PHP from 8.1.22 to 8.1.27, problem fixed. Thank you again, bozz.

Thank you, Bozz.

Thanks again for this patch that highlighted the valley and the mountain in a very clear way.

In D25608#17388, @avivey wrote:

This is probably the right fix (or maybe moving shouldAllowPublic() to the base PhabricatorFactController).

This is probably the right fix (or maybe moving shouldAllowPublic() to the base PhabricatorFactController).

After a small database inspection, it seems that uploading the picture causes:

I'm currently stuck on this since I'm trying to refactor the functions to support an indications about "I work for everybody" and "I work for only logged-in users" to be able to distinguish the case "The token exists" VS "The token exists but it's not visible" VS "The token does not exist"

Thanks to @waldyrious for the change. Tested. It works.