We've already declined support for this. See T6003 for discussion.

This isn't a bug; you mentioned the other object and we accurately reflect that.

See also T11134

But I am unable to see why not to complete this one :)

Hmm, well if those T4267's alias accounts would support non-ASCII then yes for this case. But I am unable to see why not to complete this one :)

Aaannd I think https://phabricator.wikimedia.org/T877 for the downstream. Would that resolve your problem?

T4267 is probably the upstream fix for the core issue at hand.

I am not aware. Shall I create one?

Is there a downstream task for this request?

Because we live in Unicode era and there are languages which use not just ASCII letters? Чесно!

Why should they be allowed?

Merging over into newer task.

whew, only took a few tries

wth with the remarkup

If they're using arc-diff, that information is uploaded as part of the diff regardless of any configuration (arc patch knows how to pull and use it).

We'd like to trigger a Jenkins build when a new Diff is added to a Revision, but when the base commit isn't available we don't know what to checkout and patch. Or maybe there is some git wizardry I'm unaware of...?

Ponder and General Chat are the best places for general questions on Phabricator, specifically.

http://phacility.com has Phabricator on demand.

What

I don't understand what that information has to do with this ticket.

In T11124#179972, @chad wrote:

On your local install or on Phacility test instance?

On your local install or on Phacility test instance?

In T11124#179970, @chad wrote:

You can either point Diffusion in your test instance to the URL of your SVN repository, or if it's behind a firewall and you can't, you can zip it up and add it to the Files area on Phacility and we can manually retrieve it for you.

You can either point Diffusion in your test instance to the URL of your SVN repository, or if it's behind a firewall and you can't, you can zip it up and add it to the Files area on Phacility and we can manually retrieve it for you.

In T11124#179967, @chad wrote:

We need the repository, not the database.

We need the repository, not the database.

I've already import the database dump file. The backup.sql.gz file is the result of ./bin/storage dump.

In T11124#179963, @chad wrote:

Google and Stack Overflow are going to be better resources for things like this, and we're not unfortunately. At least with those sites you can give specific details about what system you have and what you're trying to do, and can get the most up to date answer. All we're going to do here is the same thing, and charge you for our time. That's not great for anyone. :(

Google and Stack Overflow are going to be better resources for things like this, and we're not unfortunately. At least with those sites you can give specific details about what system you have and what you're trying to do, and can get the most up to date answer. All we're going to do here is the same thing, and charge you for our time. That's not great for anyone. :(

We don't offer this service under free support.

In T11124#179960, @chad wrote:

Its up to you to provide us a reproducible bug report under "free support". If you need us to do these steps for you, we'd be happy to, but we charge $1,500 an hour for this.

Its up to you to provide us a reproducible bug report under "free support". If you need us to do these steps for you, we'd be happy to, but we charge $1,500 an hour for this.

In T11124#179958, @chad wrote:

If you're willing you can just import the whole thing into the private test instance and we can inspect it from there.

If you're willing you can just import the whole thing into the private test instance and we can inspect it from there.

In T11124#179954, @chad wrote:

If you can isolate the bad commit and upload a version we can inspect on a test instance on Phacility, we can troubleshoot it further.

• http://phacility.com/
• Click "Try Free"
• Sign up
• Launch a "Test Instance"
• Report back to us if it does not import there.

thx!

This isolates any issues with your local copy of Phabricator vs. our hosted platform. It also allows us (with your permission) to privately inspect bad commits for underlying issues.

If you can isolate the bad commit and upload a version we can inspect on a test instance on Phacility, we can troubleshoot it further.

Large diffs like wiki pages should render better in email now:

I upgrade Phabricator today.

This report does not include reproduction instructions. Bug reports must include complete reproduction instructions. See Providing Reproduction Steps.

I was suggested to post it as bug in chat, so I filed T11130

See Consulting if you'd like our help resolving environment-specific configuration and setup problems.

Well, apparently I chose another base than I intended, making the diff huge indeed. The 16554943 lines were correct, thanks for the pointer there. I think this issue can be closed.

how many lines would you say the diff is? is it reviewable?

Thanks for your response. I just tried php 5.6:

Can you try php 5, we don't support php 7 at this time. These also sound like Windows errors, not sure what we can do about them.

I spent a couple hours on this last night and a couple hours this morning and I think I have Paste pretty much converted, so things look promising. I'm going to hold this until after the release cut, but expect to put Calendar on top of it and whatever else converts in the future.

This is the Phabricator install for Phabricator development, looks like you're probably in the wrong place.

Thank you guys, your explanations really made the difference. We are now happily tagging our releases. :)

Silly question but can't we use CSP Level 2's referrer directive (https://www.w3.org/TR/CSP11/#directive-referrer) to avoid leaking information without the need to build full image proxying?
If that doesn't work can we use <iframe seamless referrerpolicy="no-referrer"> ?

Looks like there's a JSON API: https://xkcd.com/json.html

I'm closing this, because it's not technically a bug report.

Some ideas about how to make comments in differential more accessible (after discussion with a member of my team who is blind):

Phabricator is not an LDAP administration tool and we have no plans to turn it into one.