Most people I've talked to just want to keep OPS separate from IT separate from ENG. stuff usually doesn't move between.

D13124 shows up as Unknown Object (Differential Revision). for me. Something meta going on here?

I like the help live saver thing in the top right. that's where I always find them.

D10105 has an example of a linter that's more 'I need to look at the whole repo' instead of individual files.

"You need to cron some stuff syncing master or it will sometimes be kind of slow" is acceptable from my point of view. Things I can solve with code is preferable to 'please debug my snowflake workstation where I did strange where I did strange things with arc and git'.

If I'm reading this right, with the tag approach & staging != main-repo, unless someone has specified things manually in .git/config they (well arc) can do git push to arbitrary places but since the staging repo isn't a configured remote none of {fetch,pull,clone} will know anything about it. I think that is a satisfactory level of cleanliness for both the main & local repos.

I have not seen this since moving our install a month ago. I don't have the logs from the old server to verify if that was before or after D12574. Maybe the old server was haunted? ¯\_(ツ)_/¯

On a possibly related note, when messing with increasing the timeout to get a meme to work (memes are very important for delivering business value) I once got:

Tangential question: For the rare public-long-lived-topic-branch why merge over rebase?

Broadly the way forward make sense to me.

I tried carefully dragging a Low priority task from column A to the bottom of column B where the lowest priority so far was Normal. This still changed the priority from Low to Normal.

• adapt for changes in D12526
• handle some quicksand stuff I do not understand from D12599

Whoops, need to account for D12526.

• rebase

• rebase

• rebase

This might be nice to move to the new-ish help dropdown.

Huh weird, our desires for what this feature would do are just complete opposites.

With the durable column open, you'll get a double scrollbar. Hopefully, this isn't too visually confusing. If the double scrollbar is worse than the old stuff was, let me know.

(5) Stop framing page content. Use JX.Scrollbar only in Conpherence panels. Accept double scrollbar.

See also: T5231

In T8135#112918, @btrahan wrote:

See T5474. I'd expect this to get resolved as having this automagical prioritization trigger be made more explicit alongside the rest of T5474. I should go on the record that I love this behavior and wouldn't want to simply remove it. :D

• ppm is already taken :-(
• phump: I tried to figure out how many consecutive ps I could string together and started making a sound like this
• pkg Somehow not taken yet, hurry!

The use case I'm thinking of is mostly "Make sure my company's custom lint is installed/configured, when I have lots of repos and I don't control the user's setup".

Linux. I tried in FF 31 and Chrome 37

This escalation requires control of DNS/networking or something to point phabricator at the new LDAP server, correct?

FWIW It would be cool to have a list of links. We use a free text field for support cases (many external tickets:one internal ticket) which mostly working but sometimes people type random junk in the next block to celebrate their freedom.

Not reproducing on this this install...

I ran into this need when trying to cover all of my bases for an extended maintenance notification. We don't have an email list that definitely covers 'all users of phabricator' that isn't absurdly over-broad (like 'all employees'). I suspect most corporate users will run into a similar convoluted problem at some point.

I think if this kept the filter & export buttons it would cover most of T5024 and obsolete my sketchy D10610 as well.

In T7847#107532, @chad wrote:

y u no like Conpherence.

Occurring on yet another repository after the latest rebase:

Okay figured it out from the mail headers and transcript. The user did indeed have a personal rule.

So I think Herald rules are the culprit on our end, but I can't figure out how to fix it:

I've only confirmed one so far.

Not sure what would be needed to debug in this case.

FWIW The log has solved at least one 'what changed when' mystery for us.

It's included in the 'chef development kit' now so almost everyone using chef has it. So at least as popular as the puppet linter ;-)

Spooky problem has not occurred in the few minutes since I rebased off of e0473aa70265a222d440c7e2e2680d2d1959ab20. Will continue to watch.

Unknown Object (Revision) / Unknown Object (Commit)

we'll need that when we eventually have an optional disable anyway.

We are seeing this again with both D12263 and D12253 applied.

• avoid calling setSeverity directly
• handle all rubocop severity values

Minor severity-mapping updates on the way.

No errors with that patch either...

• Shorten patch: Works
• Spooky Patch: Works
• Roll back to no patch: Confirmed still broken.

With that patch the daemon log is clean and the repositories show recent updates.

I'm not sure I find the new log message that much more different or illuminating.

Updated log message with D12253 applied and daemons restarted

The root cause is very likely to be a stray copy of the daemon running somewhere.

I'm now seeing this on a second repository. After some digging it appears to be a magical mysql GET_LOCK and not something simple on the file system I can just clear.

I'm seeing this on a build from March 12. A repository stopped updating on Friday and the daemon logs have been printing out this message ever few minutes and it is still occuring on Monday. No change after phd restart. diffusion/edit says 'Initializing Working Copy Daemons are initializing the working copy.'

rubocop.conf can be used to point at whichever configuration file you like.

/proc/meminfo is not cgroup aware so from LXC/Docker/whatever you will see the free memory of the physical host, not your little container.

FWIW RHEL6 is on php 5.3.3.

"You signed this document on Aug 19 2014, 2:08 PM."

I have no idea if we are a typical corporate user or not, not if on-premise users will be like SaaS users. Anyway if it happens to be a useful example we have:

• 2 GiB of files
• 3 GiB of repos
• mysql dump gzipped is 1.6 GiB

@joshuaspence I think you already have the accepted flag set, but does this look good to you for realz now?

• fancier pht games
• color setting redundant with json format
• idiomatic message chaining
• goodbye confusing flag

Is this the same as the herald based replacement for project mentions + email (T6819) ?

• updats for review feedback and changing test names
• satisfy the linting gods
• I updated the library map...

@remon sorry to poke you again, are you still working on joshuaspence's inline comments? If not I can take a stab at commandeering.

(Oh and we last rebased on upstream on 2015-01-07)