If you can identify why sudo was broken and what you did to fix it, we can probably add a setup warning to test for this problem. However, since we haven't seen other users with broken sudo and we couldn't help users resolve the issue with available information even if we did detect it, I don't think pursuing a check in the upstream is worthwhile.

Usage Exception: Linter 'versions' specifies invalid type 'libversion'. Available linters are: csharp, chmod, composer, filename, xhpast, csslint, gjslint, coffeelint, cppcheck, cpplint, flake8, golint, hlint, jshint, jsonlint, jscs, lessc, pep8, php, phpcs, puppet-lint, pyflakes, pylint, rubocop, ruby, generated, json, merge-conflict, nolint, phutil-library, script-and-regex, spelling, text, xml, checkstyle.

MSIE behaves better:

thanks, that clears it up for me!

Feed, from here:

Is this only on /feed/ or on other pages as well

Regular comments and inlines in differential, and records in Feed.
Does not reproduce in Maniphest.

maybe you can post screenshots so I don't have to guess what we're talking about.

Yeah, inlines too

So regular comments on the feed page, nothing to do with differential or inline comments?

Regular comments, not inline comments (Although I haven't checked those yet).

So feed and differential inline comments?

Ha! It's bad in the feed page.

Sounds like this is resolved? Or should we attempt to catch this case?

Thanks. Appreciate the quick fix on this.

Thanks for your help / advice Evan!

Maybe link it in the "Explain why" dialog?

Ah, sweet. Thank you!

This question has been coming up rather frequently lately; maybe we should expose the branch configuration more prominently somehow?

Yeah, we don't support or recommend third-party extensions anywhere in the documentation. We're years away from that.

@chad My bad, let me explain.

No, it's not our product. It's a third party extension. Please contact that maintainer for help.

@chad Agree, but it is "in yours product/project". Does this does not count?

This isn't our code:

Yeah I have a diff incoming, looks like it's working.

Try now?

I can't reproduce this here, locally, or in the Phacility cluster. Can you? You should be able to push to rGITTEST on this install, or launch a test instance from admin.phacility.com and create a repository there.

This isn't a valid bug report. Valid bug reports include reproduction steps, version information, and if there is a log or error message, the exact message generated. We also don't have access to third party installs. We'd be happy to re-open this report once missing information and steps are filled in.

Thanks for the report, and for including detailed reproduction steps which allowed us to reproduce the issue.

It sounds like you're running an out of date version of Phabricator. Please update to the latest version and see if the issue reproduces.

What version of Phabricator you're running? See Providing Version Information for help figuring it out.

Just as a note: I had this happen again on another very low-power instance (same file storage backend, encryption enabled etc), but with the latest HEAD, simply reloading with Ctrl+R after the webserver timed out the request made it continue and work perfectly. So yes, this is fixed it seems.

Yeah I think the need for corporate users to hide things from their enemies is probably outside of our control. Just try to find lots of bugs with it.

I'm a corporate user and I love hiding things :(

Oops -- I assumed that package was someone testing things since every other object that has ever been hidden has been and ran bin/policy unlock without examining it, but it's actually a legitimate package. I think I put it back the way it was.

Thanks for being so fast fixing this.

A subproblem here is perhaps that Owners should have a "Can Create Packages" policy.

Related to T11344

No biggie, although the UI effect is obviously crucial for my org

Whoops, yeah the strikethrough isn't for some reason. Sorry I thought you meant an issue with the graph itself.

We do not currently support RTL languages. You can follow T5267 for progress on internationalizing Phabricator, but we currently expect to support LTR latin languages first and it may be some time before we support RTL languages.

You are in the wrong place -- it looks like you mean to be on Uber's internal install of Phabricator, but this is the public upstream install of Phabricator.

Thanks for the report, and for providing detailed reproduction steps.