In T11756#235854, @Universal_Omega wrote:

I did think of that, but I also agree that issue-tracker is a bit to long and making it simple is better. It's kinda difficult regardless of what is used, all have some negatives to it...

In T11756#235853, @Agent_Isai wrote:

Also, for Phabricator CDN, we should use wikitide.net as miraheze.wiki is being deprecated and might be dropped outright one day.

I did think of that, but I also agree that issue-tracker is a bit to long and making it simple is better. It's kinda difficult regardless of what is used, all have some negatives to it...

I did think about that but not everyone on Phabricator is an issue but I might be getting to much into the specifics and semantics.

After further consideration, I think maybe issues.* would be better for simplicities sake, as Labster recommended. But not 100% decided on which is the best yet.

issue-tracker sounds good to me.

Switched to phroge.

Raising priority as phab121 has been updated to bookworm, and phabricator has little support for php 8.2

We should probably think about moving forward with this - the WMF now uses Phorge.

As this is likely your final hours on Miraheze, I'd like to say I'd have liked to apply for MWE before you left. I'd have liked to work alongside you here as an equal, as I enjoyed the limited time I worked alongside you on some small tasks before all that happened. I wish you the best on Wikiforge and wherever else you go.

Once RequestSSL is completed and all SSL requests are done via the extension, I propose that we remove it from Diffusion as it won't really serve a purpose anymore.

Upgrading to phorge is a normal phab upgrade with 2 extra steps. There is a guide that details it. I've done it for fossbots and it took 15 minutes.

I've been told there is a way but I'm not sure. Either way, switching without importing tasks would mean that we would have to keep Phabricator in a read only state indefinitely as we frequently need to refer to old tasks.

From what I've read, you can't import tasks from Phabricator instance to Phabricator instance either way due to the way its designed (and so WMF couldn't test Phorge on a separate instance as they couldn't import some tasks without importing the entire database which includes private tasks) but WMF has approved migrating, per https://phabricator.wikimedia.org/T333885

Looks like the WMF didn't have much luck importing tasks from Phabricator to Phorge. Still, we should switch anyway.

I wouldn't necessarily be opposed to that as its usefulness is arguably quite limited and will be even more significantly so when RequestSSL is completed.

Phabricator tracks the SSL Miraheze repo so to disable that, we'd have to remove the repo from Diffusion.

Done! https://phabricator.miraheze.org/project/view/83/

I would support this, personally. Makes sense for a new developer, adding Reception123 to approve/deny.

https://phabricator.miraheze.org/project/view/82/

https://phabricator.wikimedia.org/T328595 is relevant. It'll probably be useful to see how the WMF does things

@Reception123 I plan on using the board to categorize tasks that I will be working on. My knowledge of PHP, JS, CSS, CLI tools are limited right now, but I am quickly learning and over the course of the next few weeks/months, should be able to help working to resolve tasks a lot more regularly. I just installed the skin Splash on Miraheze, so that's one task to refer to if needed.

What do you plan on using this for? Do you plan on regularly working to resolve tasks?

In T10564#212732, @Void wrote:

Even if John is available to refresh the key tomorrow, it is still most likely worth changing the owner of the consumer to a shared staff account, such as the existing Miraheze Operations account.

I went ahead and did this now, as more users were encountering the issue, and it is a high priority task, plus my own fault for causing it.

CosmicAlpha or I will take care of it tomorrow.

Even if John is available to refresh the key tomorrow, it is still most likely worth changing the owner of the consumer to a shared staff account, such as the existing Miraheze Operations account. This will ensure that any available SRE will have access to modify the OAuth consumer and we won't have to wait on someone becoming available should we ever be in a similar location.

That would (probably?) be preferred. I’m stuck logging into Phabricator via GitHub right now, but not all users will have that luxury.

I can setup a new OAuth consumer in an hour or two if we want to minimize downtime.

Private key needs resetting - this has to be done by john.

If there are no more security patches for Phab, I would recommend proceeding with this and even considering making it normal priority. What would the steps entail? Are there the same SQL tables, etc.?

In T8893#199118, @John wrote:

This is something we can look into post Swift work, as that remains the priority for Infra currently. Given Phabricator is security maintained, there is no urgency currently.

The swift work is now finished.

Restarting php fixed it.

https://phab.miraheze.wiki/res/phabricator/db699fe1/rsrc/favicons/favicon-16x16.png exists, so I am not sure why it doesn't show for some. (shows for me after clearing cache, and even trying entirely different browsers)

Barring another solution, I've created https://github.com/miraheze/puppet/pull/3114

I've noticed it since January 1 but I thought it was my browser or something... but obviously, that's not the case here.
I use Microsoft Edge and Google Chrome browsers, all are the latest versions, and my Windows OS is 64-bit Windows 10 Home.

In T10238#206438, @Universal_Omega wrote:

Looks fine for me also.

@Ugochimobi Has reported the same issue.

Looks fine for me also.

The phab favicon works fine for me.

This is something we can look into post Swift work, as that remains the priority for Infra currently. Given Phabricator is security maintained, there is no urgency currently.

In T8893#197247, @Lens0021 wrote:

I just want to make sure that the EOL of Phabricator is over. There was an update in May 2022. https://secure.phabricator.com/w/changelog/2022.21/

I just want to make sure that the EOL of Phabricator is over. There was an update in May 2022. https://secure.phabricator.com/w/changelog/2022.21/

https://we.phorge.it/w/installation_and_setup/update_from_phabricator/ also

Reopening now that there is an official release. I think we can evaluate this again.

I created the bug report form, but decided not to do message override for now, as there is no great way to mention the link in this message.

Noting that there is now an official release of phorge.

https://miraheze.wiki/br will now redirect to the bug report form, so that shorter URL can be used when overwriting the message, since wiki text or raw HTML URLs are not supported there. Only plain text,

I will finish this task later.

Along with the 503s and other issues on-wiki, this seems to now be resolved.

Lowering as compared to other tasks this isn't really a priority since we've been without a separate form for years.

This happens to me as well.

Yeah it's very inconsistent for me but it does happen quite often that it's slow

It’s very likely related, though I’ll note I’ve never experienced this problem

This seems to not be consistent as right now two minutes after creating this task things have suddenly been fast but when I submitted this task itself it took quite a while to submit