I'll generate a best guess patch later today.

What kind of information could be important here? I do my best to help...

I think it's a race condition with quicksand

@flippingtables: Do you access to your phabrictor intance through a loadbalancer?

Ran into this too.

You are right, I also can't reproduce it on the Phacility instance. I really don't know what do do next ^^

Please take the time to try to reproduce the issue on a Phacility instance, and report back if you can. We have not been able to reproduce the issue with these set up steps. Reproduction steps must includes everything we need to review and fix the issue locally.

Fair enough.

I made the claim that this is the easiest way because my experience is that "have all your users do something" is always harder than "do something yourself", at least in the roles I held at Facebook and here. I'd gladly solder pins on the motherboard if I didn't have to tell users to make a simple configuration change.

Ah. I believe I fixed a simpler version of that case earlier, but not the specific case you describe. D16881 should fix that case.

We'd love to track this down as 2-3 installs have this problem with persistent chat, but no one has been able to reproduce the issue here. I've tried lots of different ways. It would be great to have a reproduction case.

@epriestley One issue that is still open is adding a change to the beginning and to the end of a large prose text. The diff of that becomes unusable. This is still reproducable with the current stable branch )(fc71a7e92dc26e0d93ec33d709391411d2bcd827 (Mon, Nov 14)). For details / reproduction steps please see T11825.

• D16853 tweaked one issue that I caught.
• T11881 is a followup for restoring code diffs in a small set of scenarios.
• I haven't seen other issues for a while, so I'm going to consider this resolved until they crop up. If you do run into cases where the new algorithm isn't doing a great job, let us know.

• D16877 includes the entire CLDR "windows to the rest of the world" map in things we'll recognize.
  • Neither that map or the Microsoft map have "Russian Time", but maybe that's just what the UI shows for zones like "Russia Time Zone 10", and not what actually appears in the ICS file? Otherwise we're going to have to keep digging.
• D16878 fixes the form customization stuff I mentioned above, mostly by preventing quirky/confusing fields from being customized (at least, for now).
• D16879 fixes a rendering bug with "All Day" events that could shift them forward or backwards by a day.
• D16880 uses the same rendering logic for subheaders (which now appears to be correct) and tooltips (which had a different, older copy of very similar logic).

From T11878, these patterns aren't obvious:

It also occurs to me that if I needed multiple and conditions I could make a rule that did nothing but just matched those conditions,

Thank you very much for your reply @epriestley, and I see what you were trying to say now, I wasn't understanding you before. You were right, I can indeed use your solution (with some modifications), I had not noticed the any of change compared to my own rules.

• Editing the EditEngine default form and removing "Host" means that "Host" no longer prefills. This is the same as T10222. A temporary workaround would be to prevent that field from being defaulted. It should be defaultable in the long run, but is probably low-value to assign a default to, so it's probably better to just lock it for now and make it behave a little more sensibly.

Some other stuff:

epriestley's "Another herald rule" condition does not solve the problem.

Relevant to my feature request in T11878, if Nuance could also work on incoming Tasks, that would make that feature request redundant as I wouldn't need to use Herald rules instead.

OK, I'll make my feature request there next time. I didn't ask for support, I made a feature request. I thought those were separate things.

No, there's no specific support for LFS mirroring yet.

Configure ArcanistTextLinter, which can detect and automatically correct these errors:

Oh, sorry! I added you to Community so you should now have edit power.

This doesn't add any compatibility with mirroring, does it?

Could someone with superpowers please edit the task summary to describe the actual task content? Like
Bring back links to task lists on project pages; list name of assignee in workboard cards
? (Or who do I have to bribe to get such rights?) Thanks in advance.

http2 apache Mod caused this bug.
I disabled http2 mod and everythings fine now

It's my fault - I edited the comment to add that link (probably based on
the same search you did) in parallel with your reply.

Whoops... just read your full comment. Sorry for dupe.

Is this the complete list?

Unfortunately "W. Europe Standard Time" is just one of the many unnecessarily verbose timezone names that Microsoft uses. I also had "Singapore Standard Time" and "Russian Time" (which I presume refers to Moscow, rather than any of the other dozen or so timezones in Russia) in my calendar for this week.

• D16866 is just what I needed, thanks!
• D16867 fixes what I reported, but I hadn't noticed that the month view tooltips are also affected in the same way:
  

I'd prefer you ask these questions in Ponder or Conpherence. It's not our expectation to provide this level of support to the community for free.

I really hope I'm not missing something here... sincere apologies if I am...

Ok thanks :)

Two way communication with a task in Phabricator with a non-user is Nuance, we don't have support for what you want today.

Click "Add Comment" to my answer if you have more questions please.

Thanks @chad, but the ticket creation is working, just the next interactions that's not.

Why doesn't this work?

You can also write your own HeraldAdapter.

Unfortunately the Another Herald Rule condition does not do what I want, if I understand it correctly.

You can already do this with the "Another Herald Rule" condition.

Sorry, I merged this the wrong way. Nuance is our planned "routing engine" aka Help Desk. We plan to pursue it first and it should be the tool you use to evaluate incoming new objects and where they go.

Or we already have a task on it. Either way.

This is expected, we merge no information over when you close a task as a duplicate.

In a similar approach, this code just makes pygmentize spit out it's data in a nicer format: