Doesn't look like the repository will even attempt to clone over HTTPS:

In T12950#230520, @chad wrote:

Why did they need regenerating in the first place?

Why did they need regenerating in the first place?

This is an unusually low-tech solution but I can't think of any reasons why it won't work.

I'm obviously low on AM brian power today.

Heh, that was going to be my suggestion in the original discourse post, but I figured it was too simplistic. Glad to hear we're on the same page. Thanks everyone!

That sounds much easier than all the solutions I came up with.

Is there any reason that the rule "if any menu items have the same link target as the request URI, highlight the first one" wouldn't work?

Or maybe there is a simple way to get the link to highlight, I couldn't think of one though.

A link doesn't stay highlighted if clicked on. Like dashboards, I can understand wanting multiple board views from the sidebar.

• What's the root problem?
• Why can't they use links?
• How is this different from T12374?

Oh, I didn't even expect that option to be configurable on Phacility given it's a security related setting. I'll turn it on and do some speed tests next week to see if I get any measurable difference in cloning.

Have you enabled diffusion.allow-http-auth?

When you click Clone in the Phacility UI on a repository, it doesn't show any HTTPS URLs. It's possible it works if you copy the URL from the address bar, but the UI in Phacility itself doesn't give any kind of indication that it will work.

Feel free to use our Discourse for general admin questions (as opposed to our working tasks). Thank you!

@ofbeaton Thanks for the tips. Sounds better than the approach we are using to slightly modify the code base.

@jessjohnson We use puppet to deploy phabricator stable from a copy on a local file server, then have it run a shell script that applies our patches using git apply on .patch files. Lastly we restart services.

@ofbeaton Just curious what's your strategy on applying patches as part of your deployment for phabricator? Do you use a find/replace strategy? Apply diffs?

Agreed. I haven't experienced the problem since I upgraded, so I think it was related to an earlier fix, even if it wasn't the identified fix (which should have already been in my install when I did have the problems). There's nothing that needs to be addressed here.

This is vague and may not actually identify a problem; I don't plan to pursue it.

This seems to mostly be a matter of taste, and we already have behavior similar to the behavior of git, which seems reasonable.

We aren't going to implement a bin/phd start-missing-daemon command.

I'll add a link too, it's reasonable.

The problem here is the default for the default branch, when the user didn't set it explicitly. In a user perspective it's then hard to know there's this option at all. Some link to set the default branch from the error could be more clear, but I don't think that's a common in phab to do that.

In T12896#228825, @jmeador wrote:

We"solved" the problem with a small python daemon that pings repository_statusmessage.epoch every minute and calculates the delta. When these deltas surpass Phabricator's max delta (21,600 sec) we page the oncall. For repositories that are mission critical, we use a smaller value. It obviously isn't a perfect solution, but it gets the job done and it's been extremely stable.

What if they're on the page, is that notification annoying? I love click that little guy.

+1, we've also had a handful of users request this as a per-user preference.

Or just have a subtask-array configurable, going with the inline approach mentioned above:

Also, it would be great if you can choose an optional "default subtask subtype" where you configure the subtypes. Something like this:

T4411 discusses some similar issues, although it predates Spaces and focuses on subscribers rather than assignees.

The page implies that all I should need to do is POST up, for example, the following:

Can you point me at where that's implied so I can make it more clear? That isn't currently expected to work. ... We do not currently support a blob of JSON as the post body, and the documentation shouldn't imply that we do (if it does, I'll fix it).

Methinks that the Rube Goldberg solution for this would be to get unittest.skip to have another argument with a task number, and then validate with lint/runtime that it look like T1234. And then maybe grep the body of the ticket for the filename.

Can you change the syntax to something like @unittest.skip("Reasoning behind this decision...")?

That is, I think the right tool for the job is either runtime enforcement or lint enforcement: make unittest.skip() with no reason fail (so the tests don't pass) or make lint raise a warning like "unittest.skip() must have a comment above it explaining the plan for re-enabling the test.".

Can you change the syntax to something like @unittest.skip("Reasoning behind this decision...")?

I know about T9853, but if there's still a chance you might consider merging that upstream, there are a few folks here at Khan Academy who are excited by the feature. Here's one example:

This is either T10333 or T4863. I'd guess the former will happen first. Filter is probably the best workaround until then. See also T12374 maybe, although I think that task involved a lot of meandering.

This information may be entirely useless, but it is somewhat related. We have a large number of repositories, with multiple clusters so this affects us in a major way.

Have you actually tested this scenario yourself?

In T12901#228807, @epriestley wrote:

Edit the Saved Query to contain something sensitive

This isn't possible.

Edit the Saved Query to contain something sensitive

In T12901#228799, @epriestley wrote:

A user might have a saved query which contains sensitive information no one else should know about.

How would other users discover the query's ID?

From elsewhere:

A user might have a saved query which contains sensitive information no one else should know about.

Also related: T12417: Show failing status of Diffusion repositories in top main menu bar.

We've also had a request for this (disabling the in-application popups) at #dropbox, as a per-user preference.

Severely needed. .arcconfig should be able to control where things land without arguments. I also question the choice made in D10058 where branch tracking seems to be used as a indicator of a branch created with arc-feature. Since arc-feature is in no way central to arc use, I think it should not be assumed that it will be used. And regular workflows and GUI tools will use git-branch instead, with tracking.

Parsing hg export metadata is an elegant solution. # HG changeset patch could imply sourceControlSystem = 'hg'. Thanks for merging the task!

The background is the Mercurial community wants to try Phabricator as an experimental review system. It's using emails now. I'd like to make Phabricator workflow as convenient as traditional email workflow.

I'm writing a Mercurial extension to send changesets to Differential like hg email provided by patchbomb extension.

Haha to be clear we're using an open-source self-hosted tracking solution, I was just throwing GA out there as an example. But I do understand your point vis-a-vis data security.

I guess everyone uses GMail nowadays anyway (as mandated by international galactic law) so my paranoia is probably mostly moot because they can undetectably read all email communication anyway.

I think you probably won't be able to answer most of those questions with Google Analytics. For example, bots will never hit client-side analytics, so any question about bots probably can't be served by GA. Likewise, GA can't see Conduit/API activity.

Why do you want to track users with Google Analytics or a similar library?

I think it's probably reasonable for us to warn about RSVP'ing to an event which has already ended. I'd guess this is usually a mistake, and in cases where it isn't some kind of weird off-label workflow is taking place and the warning is probably fine.

Why do you want to track users with Google Analytics or a similar library?

in T6722#197239 I had the same problem with "land revision from Web UI" :)

Thanks for this - suggested solution works perfectly!

See T12874. Your account will be disabled if you continue creating tasks like this. Follow the instructions you were given.

See Support Resources