- User Since
- Jun 10 2021, 05:36 (76 w, 5 d)
Fri, Nov 18
I don't see this error - can you provide reproduction instructions?
Thu, Nov 3
That's usually a sign that the Daemons are in some trouble. Go to the Daemons app and see their status and task status.
Oct 29 2022
For completeness: The security breaches mentioned in the security guidance task are all about exposing an existing file that the attacker has new view access to; This flow is only relevant to explicitly uploading a new file, so it doesn't have the same security implications.
Oct 28 2022
The change should also include updating the installation instructions, and a ticket.
https://secure.phabricator.com/T9782 suggests it should be using the "custom fields" interface and eventually fizzles out.
Rebased and run unit tests again
(On a broader theme, this code should probably move into rP, right? Is there any use-case for arcanist directly making calls to 3rd party services?)
running celerity map should just fix it. I'll take a look.
I'm good with this, but we have a policy of "no landed diffs w/o tickets", so please create one before landing.
We should connect this script (scripts/celerity/*.php) into bin/celerity.
Oct 9 2022
Oct 4 2022
The original discussion in T12144 is kinda convincing to me, although it's mostly convinces me that the term "milestone" doesn't match these objects.
can we keep the actual deletion as optional for a very long time/forever, and at the same time not create the database for new installs?
that will allow installs to backup/export their logs even if they miss the deprecation warning.
Sep 28 2022
also link to the updated Twitch docs about the auth API?
@k__nard: do you mind submitting the diffs as revisions using arc diff?
Sep 27 2022
Looks like https://secure.phabricator.com/D21718 explicitly changed to always remove --quiet, so unless there's a new argument for it, this change is redundant.
I've ran this locally, and it looks the same to me (Chrome on Windows).
I've re-applied this patch and uploaded with arc diff, just to normalize it.
Bear with me here, because Javeline (like all js frameworks) is confusing to me.
Sep 25 2022
Sep 23 2022
@kwisatz I'll try to review the diff this week, and that will probably get to master/stable soon...
As in E14, this is really important for protecting us and contributors.
Sep 22 2022
we've decided to add git reset --hard to the instructions to avoid the merges and simplify the stable issue, avoiding the merge from multiple branches.
Sep 20 2022
I'll go over this to see if there's anything left to do.
What if you upgrade a heavily modified (forked) Phabricator to the vanilla Phorge?
ah, I see the error now.
yes, that's a typo - it was carried over from an earlier version of the document.
in phase 5, only node-modules should be removed, not the package files.
thank you for reporting, and sorry I was being harsh - I forgot I split this section and only looked at the primary blob of commands.
@kwisatz - did you actually try to follow the instructions and ran into a problem, or are you just speculating?
I just tried it here, and it didn't require any auth. maybe something was wrong with our setup at the time?
Sep 19 2022
We've made it to y-combinator, so I think that counts.
Fixed and deployed.
I think we can close this now.
Why do we run npm install when we have previously deleted the package.json file from that directory?
Sep 16 2022
thanks - not technically a dupe, because there's no ticket, but D25050 would fix those.
Sep 9 2022
(should also include the rHP -> /home/ stuff)
Done - deleted phabricator books.
I've updated the guide with @jeremy.norris's Aphlict instructions, and also a section about configurations we might change later.
Sep 8 2022
the Aphlict change sounds simple enough to just add to the migration guide - it's going to happen at the same time for basically everyone anyway.
re: stable, I'm not sure how the commits actually relate between the now 4 branches.
I considered adding git reset --hard for stable, but I was afraid users will lose local changes.
So you have a suggestion on how to fix the guide for stable?
need to create a username/password passphrase credential with creds for a GitHub account that has write access to the GitHub repos, and set it in the diffusion uris.
I was hoping that wouldn't be the case. I'll create a credential against my account, since it's currently impossible to create GitHub account keys against an orginization.
Sep 7 2022
Sep 6 2022
We've created https://github.com/phorgeit and started configuring it to mirror the repos.
Sep 5 2022
From reading the git code, looks like there is a flag to allow this feature - uploadpack.allowReachableSHA1InWant, though I'll need to check that it actually works.
From a quick googling, it looks like this isn't a server configuration, but most likely the commit you're looking for just isn't in the remote.
Why are you using this command? Are you using submodules for deployment?
Aug 31 2022
We've picked up an updated version of the pem at https://secure.phabricator.com/D21739 - it's not the latest, but is it recent enough?
I've written https://we.phorge.it/w/installation_and_setup/update_from_phabricator/, and I think it's basically ready for simple case (and considering we're still compatible with Phabricator in all technical aspects).