Nix

Just for my curiosity, what lovely package are you crafting? APT? snap? Thanks :)

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

See https://we.phorge.it/T15533#11839 - the env-selecting code in ExecFuture has this logic:

Hi @speck are you still a Mercurial user? Does arc browse <file> work for you? Just for my curiosity

It is on Diffusion > My repository > Selected commit SHA diff page. E.g. https://<domain>/R1:abdcdefgh

I've extracted T15535: Using Differential with plain Git, without requiring Arc for the git-push-for-revision.

In T15096#11546, @avivey wrote:

Interesting.... Herald could probably start the flow, but there's still more parts needed (update vs create revision, extract summary and test plan)

Has anyone experimented with using arcanist in a docker container? I see two people have published these on dockerhub:

• https://hub.docker.com/r/nasqueron/arcanist
• https://hub.docker.com/r/adlogix/arcanist

Where exactly are you seeing this error? what page exactly?

Interesting.... Herald could probably start the flow, but there's still more parts needed (update vs create revision, extract summary and test plan), and it technically can't delete the branch (it can prevent it from being created, but that shows up as an error in the user-side).
But it should be able to at least trigger the flow and provide a URL for the user to click on.

Could this be solved with a Herald action?

I suspect there's also a problem of motivation: These things are lots of work, and the people who are capable of performing them - people who are comfortable with working with these tools - will not personally benefit from this stuff. The people who would benefit the most are people who are not involved in the project at all...

I think the current actionable steps we can take are:

I posted this in a separate thread, but it is definitely related: https://we.phorge.it/T15524

I'm unable to reproduce:
I've deleted a file in arcanist library, and ran arc liberate. I got no error message and the __phutil_library_map__.php was updated correctly.

I think we can consider this as resolved by our dear @jacques since I just tried and it finally works ✨

I honestly have nothing more to be done here. I would like to set as resolved but there are sub-tasks opened

In T12071, @epriestly mentions that individually selecting env-vars to copy "build[s] some resistance to "Shellshock" class vulnerabilities", which is kind of a compelling argument.

Ok, looks like my personal install is missing $HOME as well, so I can probably try to reproduce.

In T15188#9488, @speck wrote:

It looks like upstream just straight-up removed the call to utf8_decode() in the master branch: https://secure.phabricator.com/diffusion/ARC/browse/master/src/utils/utf8.php$290-292

It looks like upstream just straight-up removed the call to utf8_decode() in the master branch: https://secure.phabricator.com/diffusion/ARC/browse/master/src/utils/utf8.php$290-292

It would be helpful to have reproducing steps here, but probably this was never reproduced by the reporter, just found from TranslateWiki

If you want additional glory, feel free to add an answer below, mentioning your task and your patch. Thanks again :) and feel free to land, since it's approved now (arc land).

Created T15412 and D25237 to fix this issue.

Thanks!

Whooops, added! :)

@valerio.bozzolan have you added me to the Trusted Contributors group? I don't seem to have the permission to create any new tasks. Happy to create the task for this bug and the diff to fix it.

Hi @jkimbo thank you for your bug report. Now you are a Trusted Contributors. Feel free to elevate this question as a Task under PHP 8 support

In T15364#8952, @avivey wrote:

"tooling for chains of diffs" might need its own topic, with a design of the what the whole thing should look like in an ideal world, and how to get to it.
Even if not all of the stuff fits nicely into Phorge, there's probably a lot that can work, and some conduit methods can be added to implement the rest.

"tooling for chains of diffs" might need its own topic, with a design of the what the whole thing should look like in an ideal world, and how to get to it.
Even if not all of the stuff fits nicely into Phorge, there's probably a lot that can work, and some conduit methods can be added to implement the rest.

Chaining Diffs is something that we would like to use more often, and it is definitely not used enough today. FreeBSD is a large codebase and making any change that is bigger than trivial often involves touching multiple parts of the system, the most difficult kind of change is architectural changes. We are limited by our tooling to a certain degree:

• Keeping everything in one Diff makes it very difficult to review as well as reach consensus, as there are often multiple responsible parties involved. It also violates the ethos of Phab/Phorge of having small atomic changes.
• Breaking changes down in smaller chunks has lots of downsides too - it is very hard to track and changes often get lost in depths of Differential.

mmm... I've never really worked where many changes are made of lots of dependent revisions - it's possible I've never even seen a chain of 3 revisions in the same repo. So I'm not sure about workflows for this kind of scenarios.

Yea, today I have about 50 lines of shell scripting that gets the different bits of data from the condon API point and then bashes them into a nearly acceptable commit message....

Ok, so here's my thoughts on moving this forward:

It hadn't happened in a while, so I guess it was something strange in my machine.

By the way the only usages are:

FWIW I think the test plan is configurable (that requirement can be disabled in phabricator's config server side which should remove it from commit messages in arc)

Yeah no problem!

In T15368#8316, @valerio.bozzolan wrote:

Hi @aklapper. Are you affected by this as well?

@valerio.bozzolan right, I forgot the important bit, sorry :D

Note that probably @ton you have resolved, but anybody else nope :D The patch D25205 still needs review and land