What are some of the things you anticipate?

well I do enjoy when @putnam stops by.

This thing is going to have a decade of bugs.

hello chad
https://secure.phabricator.com/book/phabricator/article/installation_guide/#installing-required-comp
i see it，and i have done all the steps but it doesn't fix my problem
i execut install_ubuntu.sh,then i request the url is

👍

Yeah, completeness is definitely sufficient motivation if you're up for it.

I've also noticed that Herald Transactions have PHID, but not PHIDType class (https://secure.phabricator.com/diffusion/P/browse/master/src/applications/herald/storage/transcript/HeraldTranscript.php;3f439e25bc586ff8bae203a47625f6c360e4402a$193). Wasn't sure if "completeness" is a good enough reason to make the changes (PHIDType + teach the Query object about withPHIDs, and maybe a bit more).

This report does not include reproduction steps. We can't move forward on bugs we can't reproduce. See Contributing Bug Reports.

Our current thinking still is that it's environmental, that is something between Phabricator and the browser is munging the JS (or the webserver itself). Generally anything this catastrophic would be (JS failure) we'd have multiple easy to reproduce reports, and we haven't seen that. It is concerning though that three people ran into this in short notice. It'd be good to know if there is any common infrastructure (web, php, server, etc).

Ah, OK, I thought that message from clemvangelis about 6 up is a confirmation of local install issue? I'll see if I can do a local install and replicate...

We have not been able to reproduce any issue. If someone can come up with a set of steps or environment that reproduces the issue, then we can look into it.

Hi guys, I'm a bit confused re the commit hash message above, does this mean it's an issue which will be looked into as is happening on a local install also?

I'm not sure what you mean by "from the instance panel"? Is it the instance's regular config page?

Oh, I'll make this editable in the cluster from the instances panel. Change will go out on Saturday morning (about 36 hours from now).

There are many existing failures in our codebase. Linting all files would give copious (unhelpful) output. That being said, I haven't tried it because it would (probably) take hours to run. Should I give it a try?

Ah. I searched for something like this in config but forgot about the /config/all/ page.

I am not opposed to attempting to contribute this, but I haven't ever contributed to Phabricator so I would definitely need some direction on where to start to make it a quick project.

See uri.allowed-protocols in Config.

A sufficient diagnostic test is apparently to complete any connection with ssh -v and observe no "Roaming not allowed by server" message in the output. Cluster hosts with the configuration fix pass this test.

We probably can't reasonably just attach the photo (That could end up big)

I've applied the configuration fix to all Phacility cluster hosts that initiate SSH connections to untrusted servers, so we should be in the clear.

Yes..
nz_cor:_nz_fm_integrationnz_cor_nz_fm_integrationnz_cor_nz_fm_integrationnz_cor_-_nz_fm_integrationnz_cor_nz_fm_integrationnz_cor_nz_fm_integration
Is in there now.
I'll remove those.

I'm not really sure what's going on. The limit on the slug column is 128 characters, and that project name is nowhere near that (we should raise a better error message than we do, but I'm not sure how you're hitting the issue in the first place).

/var/www/phabricator# bin/storage adjust
Verifying database schemata...
Found no adjustments for schemata.

Can you show me the output of bin/storage adjust? (For now, decline to apply any changes it suggests.)

Actually changing it back is failing with

Prior to T9551 (circa October 12), projects could generate with invalid hashtags, but I don't think these ever worked (at least, many of them definitely did not work).

I wish I could reproduce it.
But all new projects I create work perfectly fine.

The original report in Q272 is almost certainly unrelated.

Initially reported in Q272 by @linan

Per my comment on the question, please see Contributing Bug Reports and file a bug, we'd be happy to help. This application is Ponder, a place for users to ask general questions about Phabricator, we don't use it for managing bugs.

I think T10116 may have fixed the "actions ignored" issue -- does it still reproduce for you after that?

Resolved by D15019.

Added a proposed patch. See additional comments in the diff.

You likely have a diff which isn't JSON-encodable (for example, it affects non-utf8 files). T5955 is probably the pathway forward here.

You can print it to a PDF.

I wonder why path "/var/repo/M/" is empty?

Currently, I find it challenging to find existing failures.

Very nice.

I have upgrade Phabricator to commit 473693786b86071f478b1490cf6bec5b4650dbea ,Wed Jan 13 . I have restart all webserver & daemons. When i relaod Diffusion page , appear these log

I can give that a shot. Manually building PHP with --with-curl=/usr/bin also worked for me. Thanks for your help, Chad!

I'm pretty sure it can happen anywhere; I've definitely seen it happen on Linux, but my guess is that it's much more infrequent just because you're unlikely to have GUI tools periodically running "git status".

can this happen outside of Windows? Do *nix have some better flock features?