A couple of things offhand:

The same thing happens when trying to select a different encoding.

I'd rather not. We have a lot of staff who manage access and most of them I don't want poking around as an admin.

Yeah, I guess that works.

Ah yeah... I have self emails disabled. I dislike self-emails when creating a task through the web UI, but I would see value in having self-emails when I create a task via email (because otherwise I have no idea if it actually worked)

That would work but I guess.

Oh cool, I haz badge.

I will get to it eventually but realistically I haven't started doing anything here. Feel free to reassign.

I've seen this a bunch of times.

Pretty sure this was fixed by D13519.

This happened again today, presumably because I added a new differential revision to PHID-TASK-bclylvkmj6c5kdn74s26.

Yeah that works but I feel like making the file view a bit more responsive would help as well.

Don't you mean Differential?

Ah, I think this is relevant...

OK. If I get rid of the explicit phd.taskmasters setting then it seems to work. With phd.taskmasters set to 8 it seems to lock up at 100% CPU usage after a few minutes.

This has happened three time today :(

Hmm. It has happened again, even with --autoscale-reserve 0.25.

In T8878#126901, @chad wrote:

I'd rather over-engineer a more generalized "new in phabricator" type feature, so people understand what new functionality was added since their last update.

In T8885#126858, @chad wrote:

Also, #phui is the best tag for these, which is "Phabricator UI". Maybe a good way to think about it is #design is pre-commit, #phui is post-commit. :)

Yeah that's true. Good point.

Shouldn't we do something similar by default?

I found it interesting that S3 got interpreted as remarkup. I wonder if we should blacklist it from being matched similar to Q1, etc.

I don't think our users would want to update Arcanist as often as I am updating Phabricator.

Another option would be to allow a minimum version to be specified server-side. As in, Phabricator reports a minimum version commit hash which is either maintained in the code itself or overriden by admins.

Also, 99% of the time when people ask me for help with Arcanist its just a matter of running arc upgrade.

Interesting idea. Composer gives some sort of warning if it is more than 30 days old... Maybe something similar would be useful for Arcanist.

This is interesting. We had an abandoned diff which got closed by ./bin/repository reparse. If I click on "Explain Why" then it says We didn't find a "Differential Revision" field in the commit message. That doesn't really make sense to me, is this a bug?

This happened again today. I ran for REPO in $(./bin/repository list); do ./bin/repository reparse --message $REPO; done and a whole lot of badness ensued.

I'm not, I just type secure.phabricator.com/T8820 into my browser.

T8612 is probably related.

I know you don't provide support for writing third party extensions, but is it possible to do what I am trying to do with Doorkeeper currently? Basically I guess I need to define conditions which define what is published and where it is published to.

I suppose that makes sense. I really like having the popup box when you hover over monogram references but I suppose that T5378 could fix this as well.

Oh :(

Personally, I'd much rather use Conpherence because I absolutely love mentions and find them very useful. Having said that, convincing 200+ others to use Conpherence is much more difficult.