Has cloudflare explicitly said that only responses were leaked, and never
requests? I recall "POST data" being explicitly called out as showing up in
the leaks, but I can't remember if this was in an official write up or
media coverage.

Only our websocket host is behind CF proxies, so I invalidated all auth sessions by changing the security.hmac-key. I wanted to also invalidate all Conduit tokens just as a fire drill but couldn't found a method of doing this.

based on the fact that 6 month old code worked fine until a backend upgrade last week, I'm guessing the breakage happened because of server-side changes

it's a "fresh" repo, created yesterday, with no commits. I immediately
disabled those upon creation and then circled back the next day considering
it "completely new"

ah. yes. I turned those off.

fair enough

I'd like the UI to not offer things which don't work - I have not tested Mercurial and SVN hosting and given that I've done nothing to make them work I imagine they don't

without getting into whether it *can* be done, we looked into this recently and decided we actually liked the suggested approach.

as per T11149, my email format setting defaults do not reflect active instance config

just upgraded to the hashes from https://secure.phabricator.com/w/changelog/2016.24/ before spotting issue, unsure if it was that way before

ah it's phutil_symbols...

I have a patch for this but arc lint is taking forever and all of my CPU... :-/

that's good enough for me but the UI and docs need improving. I'll try and get the docs at least when I have a minute.

:o yeah that works

I'm experiencing a dumb.

1. manually restarted php5-fpm and phd services
2. colleague, member of ops submitted review touching src/ansible
3. that review doesn't explicitly list "ops" as blocking reviewers because he's also an owner of ansible, but it does highlight my review in yellow
   
4. he lands it after I accept it
5. his commit is flagged for review despite both of us being members of ops

I will manually restart everything and reproduce again

that worked. there's no indication in the UI that the trailing slash is required, the link rendered works fine

I apologize, my ansible deploy script *should* have restarted everything that needs restarting, but it appears it didn't.

@epriestley thanks!

This SQL query will map all users that don't have an LDAP mapping, allowing them to log in using LDAP as long as their LDAP username matches their Phabricator username.

confirm noomhq is operational again

our stuff is still down

my pleasure! thanks for the swift reaction and resolution, and very clear messaging on when we can expect the fix to be available on the phacility instance.

LMFAO

sorry, forgot to say it's this document https://secure.phabricator.com/book/phabricator/article/arcanist_lint/

yeah, fair enough. if I build a stronger case I'll reopen/refile

ah, chaining Herald rules, while clunky as a UI solution, probably fixes the more complex scenarios

... nvm. brain fart moment.

@epriestley any ETA on the all-clear for Real Work (to borrow terminology from the previously published rollout schedule)?

zxdgfdgdfsgsfdd

zxdgfdgdfsgsfdd