Ref T10004.

I have a vague feeling it's related to cleaning up the initial create transactions, that is, we used to show every field on the first transaction, which was silly since you could see what all the initial values are above.

Err I guess the two problems are exactly the same.

Once someone asked me why the icon spin wasn't working, as it was documented but our install hadn't upgraded with that feature yet. It was the most devastating sadface I'd ever seen on IRC.

There is no way to be alerted to blocked pushes right now, and I generally don't think this is useful enough to include in the upstream. This interaction could possibly be more clear, but feels like something we just stick in the documentation to me.

Yeah, the local help pages aren't generated by Diviner -- they're generally generated from the configured code at runtime.

I see. At least some of the individual help pages (e.g. https://secure.phabricator.com/applications/mailcommands/PhabricatorManiphestApplication/task/ are linked locally but I guess those are part of the app instead of inside Diviner.

It is very unusual for documentation to exist locally, as generating it currently requires building xhpast and doing setup on Diviner.

You may be able to call HTTPSFuture::setBlindlyTrustDomains(...) from preamble.php as a possible workaround, although you'll have to load some libraries first and this may interfere with error handling. Alternatively, you might be able to write an event listener which only calls this method as a side effect and does not listen for events (event listeners are allowed to run registration code early in the startup process).

For magical historical reasons we actually serve an invalid cert within our production network. That is, if you visit the site in a browser on the corporate (or outside) world it works perfectly. Within production the cert has the wrong domain. This means that even adding the CA won't help since the peer name is still verified.

Can you walk me through why can't you add the internal certificate to Phabricator's trusted CA chain?

I think that would be reasonable.

Why not change Phobject::__isset and Phobject::__unset to throw an exception in the same way that Phobject::__get and Phobject::__set do?

In T3179#162681, @dolftax wrote:

In T3179#111010, @anda wrote:

Has anybody heard of someone migrating jira issues to phabricator? We're thinking about doing that, and of there were some example scripts for the import to start with, that Spaulding be great.

We probably have around 1500 issues to migrate, with a few different jira project names /labels. Of guess that this would best be translated to a label in phabricator.

Did you find a JIRA -> Phabricator migration script?

In T3179#111010, @anda wrote:

Has anybody heard of someone migrating jira issues to phabricator? We're thinking about doing that, and of there were some example scripts for the import to start with, that Spaulding be great.

We probably have around 1500 issues to migrate, with a few different jira project names /labels. Of guess that this would best be translated to a label in phabricator.

Worked like a charm! Thanks.

Thanks! Should be fixed by D15368.

@epriestley Thanks!

• Provide some way to treat "too much output" as a categorical build failure, similar to how you might treat "excessive runtime" as a build failure.

Sounds like this has been resolved.

See script in T10350.

which svn client do you use ?

which svn client do you use ?
i saw you have the file on the same folder. can you try moving the files between differnt folders ?
if it still working maybe we should upgrade phabricator.
which version of phabricator did you use ?

In T10481#162637, @tycho.tatitscheff wrote:

Have you launched aphlict in debug mode ?
https://secure.phabricator.com/book/phabricator/article/notifications/#troubleshooting

Are behind a nginx proxy or direct connected. If you are connected directly maybe your port isn't open.

Have you launched aphlict in debug mode ?
https://secure.phabricator.com/book/phabricator/article/notifications/#troubleshooting

If I understand correctly, the first line hasn't all the property set thus can be removed.
I would be happy to send a diff.

@epriestley : sorry, I should have searched more thoughtfully.

Thanks for the fix!

This should be fixed in HEAD. Thanks for the report!

Current plan here is:

Nevermind about that last point, I see