Phorge

PublicGeneral discussions about Phorge. For long and complex questions, you may want to use Ponder.

• Join Room

@aklapper I did write a bunch of code from scratch. I am writing it in go as a way to dogfood the conduit API library I am writing in go

Out of interest, @ton, do you think there's anywhere that the Conduit API falls short or could be improved?

perhaps. I am picking up this project after 2 year break. My memory is a bit vague at the moment

Thanks! Appreciate it. Have just joined the project, but have found a few shortcomings that I'd personally like to improve, so wondering where is most helpful to start.

If counduit had some way of self-describing the API... like a json schema or something

Ah, good shout. Something like an OpenAPI specification?

The challenge as I remember it is that conduit exposes application's APIs, and Apps can be enabled/disabled in settings. If it is disabled conduit won't show it.

I presume that we could generate something on the fly and cache it then flush the cache when apps are enabled or disabled.

perhaps, at the moment I am focused on the core apps - maniphest, differential, diffusion and these seem to be enabled

I think you're probably right in suggesting that we do it automatically, as maintaining it manually is likely to be a PITA, and the data is clearly already available, as the Conduit pages list every endpoint.

I am not sure I can do it. You probably need to talk to the bosses.

Ah, sorry, wasn't asking directly - was just hoping someone would be hanging around here, but will try IRC too.

@avivey it does look like I have the power to add folks to Trusted Contributors group, at least the button is not grayed out for me. But I am not sure I am supposed to

Should be added!

Thanks, both - much appreciated!

https://we.phorge.it/api/conduit.query I think I found an API description in json

@ton - yes, Trusted Contributors is a "self-governing group" - basically, any member can add others as members.
The bar for acceptance to this group is basically "not spam".

ack

Looks like you beat me to it, @ton! Cheers.

not to start a flame war, but mysql vs mariadb - which is better for phorge?

I don't expect a real difference. But if there was, then "better" would need clear criteria anyway

I personally stick to MySQL Community Edition as that's what it was originally built for, but MariaDB is meant to have feature parity, so I see no reason not to use it.

Been using MariaDB on my personal instance and for the one we run at my work just fine for years now, as some real-world proof of the theory.

On an unrelated topic, has anyone hosted a monorepo in Phorge at all, and, if so, what challenges have you faced, if any?

@keithzg You might be interested in helping to implement T15045?

I don't get the "Cat Fact" «The first cats evolved in swamps about 65 years ago.» that is probably the only Cat Fact that makes no sense to me lol - https://we.phorge.it/source/phorge/browse/master/src/applications/search/menuitem/PhabricatorMotivatorProfileMenuItem.php

thatsthejoke.gif

nobody said these facts are correct. they're just facts.

Admins: please approve this kind user I know: https://we.phorge.it/people/manage/1416/ Thanks :3 :3

Also maybe it's necessary to mention that the IRC chan is has a name and it's called Phorge from the msg that is shown here https://we.phorge.it/auth/start/?next=%2F

I've added a link from that message to https://we.phorge.it/w/irc/ :)

at the risk of sounding cheeky, can i ask if someone would be willing to add me to Trusted Contributors? i occasionally feel like upstreaming tasks from https://phabricator.wikimedia.org/project/view/6/ and that would allow me to do it :p

Yup, added

thanks :)

Can someone provide me with some guidance/docs on how to read the task graph, please? I'm sure that I'm missing something obvious, but my ADHD brain is losing it! Thanks.

Do you have a specific task graph?
The general meaning is: children task (down) are sub-tasks, blocking your current task

As I already tried to say, you are visiting T1, so your point of view is that. To complete it, you have children sub-tasks (pointing down from T1).
You can easily see that you should first complete T140 to be able to close T139, and that you should then complete T139 to complete T1, etc

That frame of thinking actually helps me to make sense of it, so thank you very much! Appreciate it as ever, Bozz.

For that example screenshot: row with yellow background is current task; chevron-down icon in first column means direct subtask, all other ones are indirect subtasks.

This is also helpful! Thanks.

Any chance of an admin approving @chris18890, please?

Done!

Hey all, I'm gonna try cutting new stable and updating this install this week.

Thanks, @chris!

Ouch I forgot another release train for my beloved brand-new destroy workflow, now completely fixed D25772

hmm, just (i) don't be surprised if the site goes down for a few minutes, (ii) notice if the site goes down for long, and (iii) check that any important change in the last almost-year is noted in Next Up.

Uh new stable <3! I think D25963 and D25967 are the only ones on my list making me feel "This should _reeeally_ go in" (though ofc there are more low hanging fruit patches waiting for review).

Can anyone describe the difference between Atoms and Symbols in Diviner in a simple sentence?

P.S. I boldly create a new tag for the event Wikimedia Hackathon 2025 #wmhack-2025 in Istanbul, just to have more creative space to collect some stuff for the local code+review sprint and then archive that tag after the event.

Thanks for the upgrade!

didn't start it yet, system ran out of disk space

uhm :(

If we recover more space, after that, maybe we can recover even more disk space by shutting down web interface and calling OPTIMIZE TABLE phabricator_file.files or whatever its name;

mm, I'm gonna try that

(But don't try if we don't have enough disk space, since it needs disk space to free disk space lool)

I can also just increase the disk size on the linode instance later today. Sorry about that, didn't realize where we were on disk utilization

I've upgraded the install to today's master, so we have a new Phorge.
And probably enough free disk space for several months.

Thanks avivey! And enjoy in production the new filter by token... lol @taavi https://we.phorge.it/token/given/query/imgpytwdtshH/#R

Given we have no release this year yet, this is an opportunity to decide on which version naming we should use: YYYY.ww (YYYY Week ww) or YYYY.mm (mm/YYYY). Until 2015, Phabricator was using YYYY.mm before switching to weekly releases. However, we (Phorge) promote to stable only several times per year.

@avivey: maybe phd is not running

@Cigaryno: Which underlying problem would get solved by potentially changing the current naming scheme? Asking as I don't see a problem (yet).

@aklapper Honestly, the current naming scheme looks fine to me, it's just that Phorge stable releases are several times a year, not weekly (Phab was weekly from 2015 to 2021 with some exceptions) and Phorge is unlikely to have two releases per month (rare exception: security vulnerabilities).
During the beginning (when 2022.35 got promoted), I though Phorge may have weekly releases one day and today I think some may be thinking that Phorge releases could be weekly.

@avivey what's going on? why was the instance broken

phd looks to be running. Some massive activity

@Cigaryno: Ubuntu releases, twice a year, end in .04 and .10. They are not released monthly. So I guess I don't mind if people think that Phorge releases could be weekly. If they want to find out they could go to https://we.phorge.it/w/changelog/ :)

hey, yah, daemons were down.

We had disk issues, and after that I did an upgrade, and after that the daemons were still running, so I'm not sure why they died out.

Also, if the daemons are down, notifications/emails are not being sent...

In Z1#3558, @aklapper wrote:
@Cigaryno: Ubuntu releases, twice a year, end in .04 and .10. They are not released monthly. So I guess I don't mind if people think that Phorge releases could be weekly. If they want to find out they could go to https://we.phorge.it/w/changelog/ :)

Agree with you. Staying on YYYY.ww despite little releases is therefore the equivalent of Ubuntu release twice a year and using .04 and .10 (for April and October).

I've restarted the daemons now, I'm not sure why they stopped.
Maybe I forgot to stop them for the upgrade, and the old ones kept running.

I honestly don't have an opinion on week-number vs month in the version name.
Unless we make the release run automatically on a timer, I doubt we'll ever get more then 3-4 releases a year.

The new user @Chlod is a trusted user, thanks admin for accepting 👍

added (I think)