When using Mercurial, can Diffusion handle multiple remote bookmarks on the same branch?

@rfreebern Nope, no clue how to debug it. We just don't use Diffusion any more and instead use the Bitbucket page, whose UI we anyway prefer to see commits and browse the code :/

I did look at the page.

Worked, thanks!

Removing all lines worked, thanks!

Ok, thanks, that explains it. Reviewer1 requests changes and asks the author to add Reviewer2 and leave it to Reviewer2 to accept it. Reviewer2 accepts it but Reviewer1 had blocked it.

What is the expected behavior i.e. who has to accept before the revision can be landed? Usually till date what we've encountered is that one reviewer needs to accept it.

Yeah, all our users have two sub-groups, except for "Not Assigned" which has a single one.

Quite possibly, yes.

I can't reproduce it on this install. But then, I can't reproduce it for every task on my install. However, I can reproduce it consistently for certain tasks. Here are some screenshots in which I assign task 968 to user sahil, then to aditya, then to amyth.

I recreated the herald rules and also re-setup the Amazon SES config. Something fixed it, it's back in business :/

(1) It says "Contents Modified".

And Diffusion does have the latest commits.

You're right, it was a rogue local path. Thanks!

Nope, it doesn't appear to be in "Importing" state.