Some things in the side bar seem more deleoper related than configuration related. Trying to think where we could possibly move then maybe, like a developer app?

(And we can continue reducing the number of settings, but not very quickly.)

/config/ is already an attempt at chopping it up, vs /config/all/ which is the un-chopped version. If you have a better way of making it less scary there's no need to chop it up in the way it's currently chopped up, though.

Also "Config" is super scary. It might be helpful to chop that up a bit?

Thinking about the "Phacility" NUX case and unsure users really need to explore Config or Applications. Really we just want them to invite some people and pull in their repo. If new to Phabricator... learn about getting Arcanist up and maybe make a few projects. I'm mostly trying to separate things into "must do" and "useful tips". Useful tips can just go into Feed as the first post, like Quick Start guides for individual apps or following us on Twitter.

Comment deleting is to help with accidental information leaks or outright spam. It is not our expectation that users will delete information from Phabricator and warn against it.

It is not too much different from removing comments. And this people are allowed to remove. (BTW I wonder what happens if one removes a comment with a mention)

Audit-ability is a core feature of Phabricator. We're very limited in what we allow people to delete.

But then I unmention it and it's unreflected. This seems to be wrong. Perhaps another record like "Task Y does not mention this task anymore" could be added, but it looks better to just remove the initial record. Or, optionally, it would be sense-full to provide a person who did the mention a possibility to do it manually -- thus some judgement could be applied.

Yeah -- the highlighting code is more flexible about what it matches than the actual search code is, which makes T6740 worse / more confusing.

ah I guess it matched on 'username' elsewhere, it gives the impression that is matched on 'usernames' though since it highlighted it as usernames

"username" doesn't match "usernames" until T6740.

I couldn't find that task, actually. I searched for 'username' and closed, and I just double checked again and it still didn't appear?

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