Work related to Phorge, the organization that develops Phorge (the software).
Details
Fri, Sep 22
Sep 1 2023
Aug 31 2023
Aug 30 2023
Aug 26 2023
Would taking care of the depreciations bump the minimum PHP version required to run Phorge?
Not in itself, but we do plan to bump the minimum to 7.1 (in T15047).
Aug 25 2023
Would taking care of the depreciations bump the minimum PHP version required to run Phorge?
looks good to me otherwise
Aug 18 2023
Aug 17 2023
Aug 15 2023
thank you @ncoker, but:
- This is not a task to discuss specific errors when trying to run on php 8, and
- We don't expect arcanist to work on php 8 yet
Maybe also something for this topic!
We update php yesterday on our WSL2 (Ubuntu 22.04) clients to 8.1.22 and pulled the latest arcanist from git after the commit
Now we facing this problem on starting arcanist:
Aug 12 2023
Aug 11 2023
Aug 8 2023
Aug 7 2023
Jul 28 2023
Jul 27 2023
every extension should have its own
Probably related, I think that any installed extension should not cause any touch to /src/__phutil_library_init__.php, as long as it's versioned in git in Phorge and so will cause of course merge conflicts after any update.
I was thinking of adding a script to ./bin to manage (mostly add/remove from load-libraries, maybe also clone) extensions.
I was thinking "out out", but only visible to admins - and then, only as a yellow notice at the top of the page:
This is a good plan. Would this be opt-in, e.g. this Phorge instance would be the main one with this on but other installs wouldn’t see this by default?
Jul 24 2023
(Implementation notice: in both phorge and arc, this is handled in PhutilErrorHandler::handleError(), and the check is simply $num === E_DEPRECATED), and maybe E_USER_DEPRECATED.
Jul 19 2023
Jul 18 2023
+1
Jul 17 2023
I agree that Phorge should not fall over because of a deprecation warning.
Jul 15 2023
Jul 14 2023
Jul 10 2023
Jul 8 2023
Jul 4 2023
Jul 3 2023
I don't think I intended to land this change.