Nah, I vaguely remember I accidentally set up something which didn't make sense and the followup PEBKAC moment when realizing but don't remember details now

In D25515#14842, @valerio.bozzolan wrote:

I wonder if it then, upon deletion of the profile image, it attempts to delete the builtin image

In T15712#15124, @avivey wrote:

Is the motivation only to allow not-magicking things like "S3" and "F1", or is there more?

Looks like the tickets end in a Wontfix in https://secure.phabricator.com/T5301; I didn't follow the whole thing, but often the reasoning in Remarkup boils down to performance.

mm, see this one: https://secure.phabricator.com/T5301#211340

Is the motivation only to allow not-magicking things like "S3" and "F1", or is there more?

Some help is needed there, testing on PHP 8.1+ and getting the right stack trace

I wonder if it then, upon deletion of the profile image, it attempts to delete the builtin image

Useful riepilogue for wild integers

Abandoning my patch becaue creating a child class for each and every single field does not scale.
Instead there should be a setDefaultValue() function on a PhabricatorSearchField level to be called by the SearchEngine.

Is that something we can improve in the settings page/docs - give better instructions on this setting?

Indeed, this is invalid due to me not understanding the config settings at that time.

Done; see T15711.

@jeanguyomarch: Hi, would you like to arc land your accepted patch?

My initial choice of words was wrong: It's not "duplicated". SELECT * FROM differential_difftransaction WHERE dateCreated > 1705224003; shows two transactions differing in id, phid and transactionType (differential:diff:create versus core:view-policy).

In D25419#14821, @valerio.bozzolan wrote:

I'm just unsure between implode() or phutil_implode_html()

I'm just unsure between implode() or phutil_implode_html()

Thanks again for this change. Please try "landing" with these two commands:

https://we.phorge.it/source/phorge/browse/master/src/applications/repository/storage/PhabricatorRepository.php$348 got fixed by rP222a6fea0a1d9318198fe73a0501cf6444420ce3 in T15658, thus resolving

In D25515#14801, @avivey wrote:

Do we have a setup-warning about the gd extension being missing?

(see also https://secure.phabricator.com/T2378 which links D5561, D5968, D5670 for those not logged in.)

I believe I had some weird aggressive local browser cache pollution with rPaa8af1d79e8bfeb09e72d5e3b9330780e78b7aeb as I cannot reproduce the wordmark problem anymore, so: LGTM

As the patch was merged I assume that this issue is resolved. If not, then please reopen - thanks!

Do we have a setup-warning about the gd extension being missing?

Thanks - I did mean as an inline comment in the code but either is good.

Is the input to parseDiff guaranteed to be UTF-8 encoded?

Is the input to parseDiff guaranteed to be UTF-8 encoded? I don’t have the code on-hand to look up but it’s possible encoding is handled elsewhere — or arc might have a hard requirement for all input to be UTF-8. All mercurial commands run by arcanist are done with a flag to enforce UTF-8.

Hmm I’ve used mercurial and arcanist/Phab for years at my company and don’t believe we’ve ever run into this. Any idea what’s causing the presence of the BOM? We’ll apply a change to handle the UTF-8 bom but I am curious what may have caused it to show up. Is your hgrc configured in some way for this or maybe an environment variable?

I'm tempted to just change that one line to $left = idx($view_data, 'left', 0); so there shoud not be a crash at this stage anymore but instead the default value 0 is passed to the DifferentialDiffQuery and to the new DifferentialTransactionView... but I lack a reproducer to check if all other code is fine with this.

PHP 8.2.14, Phorge at cc964550f945b08c64970c01a34b55314e8ef0aa

1. As an admin, check that /config/edit/user.require-real-name/ is set to Make real names optional
2. Log out of Phorge
3. Go to http://phorge.localhost/auth/register/
4. See that the Real Name field does not state Required on the right
5. Enter values into the fields Username, Password, Confirm Password, Email
6. Click the Register Account button

I've created R10 PhorgeIt Extension for this, with a little bit of content. I'll load it to the server shortly.

Reference: rPdfcccd4cb882a171d10ba8a5c2763dcc73654256

+lots for removing the words "storage containers" - projects are very much not "storage".
A better metaphor is "labels" or "index" (like in a printed book? Is that something young people know about?).

Also for Archived Projects, and maybe some other objects.
I'm not sure if there's a generic way to do this, or if each search-engine needs to be updated manually.

+1 on Content licensed under Creative Commons Attribution-ShareAlike 4.0 (CC-BY-SA) unless otherwise noted; code licensed under Apache 2.0 or other open source licenses.

In T15582#12521, @valerio.bozzolan wrote:

clarify why the Disable User button [...] not sufficient for this purpose.

I'd like to keep this boring:
Projects are hashtags are tags. You can use them for code bases, teams, or anything you need to group.

Do you mean "action"? If yes, I can reproduce

Indeed this fixes the problem. Premising there is still some mystery here that may deserve additional eyes.

Sentence case <3

Part of this Diff has no sense now that I learned that... some of these has sense. Let's close.

Sounds easy enough to implement.

Doc(s) on new extensions: I remember having a chapter under /book/contrib/, but I can't find it now. We should build a guide under T15030.
Short answer: create a new repo, make an src dir with all the code, and run arc liberate to create a "library" (including __phutil_library_init__.php and __phutil_library_map__.php), and then add the path of the extension to load-libraries in conf.json.

I copy/pasted the keys of the getStyleMap() function dictionary into chatgpt with some remark that they were part of a syntax highlighting mechanism.
I asked it to translate them into something more readable.

In T15708#15014, @avivey wrote:

I'd like to see this as an Extension rather then go into the rP, just because we want to have more stuff as extensions; I think this area is abstracted enough so that it can easily be made that way.

That could be a good target as well for this, Is there docs on how extensions should be made?

I'd like to see this as an Extension rather then go into the rP, just because we want to have more stuff as extensions; I think this area is abstracted enough so that it can easily be made that way.

Double-accept yeah