This task was filed via the "New Bug Report" form.
Tue, Apr 25
@epriestley, what's weird is, I still have this on my install, despite having the latest stable. I checked, and the migration definitely ran. Thoughts on how to debug this further?
There is a task to create another target rendering engine, but I'm not able to locate it at the moment.
OK. But isn't it weird from an end-user POV to have unparsed remarkup there?
If it's a choice, you can close this issue! Thank you for your quick answer.
This is working as intended. We only have two choices for target rendering, full remarkup or text.
Thank you for the quick response and fixes!
Mon, Apr 24
- I deployed D17774 to secure.
- I verified that rSVNTEST now correctly raised an error because it was backed by a service with muliple hosts.
- I moved rSVNTEST and rHGTEST to a one-host service, securex-legacy.phacility.net.
- I can no longer reproduce any issues against this host.
T12635 had another similar report, and I believe I tracked down and fixed the root cause there.
And thanks for the report! Let us know if you run into anything else..
This should now be resolved at HEAD:
Actually I think there's a real path to this which remains available:
Here's a script which will identify affected users. Output is:
I think some very old users got into a bugged state where their primary email is verified but the "is verified" flag was never set on their account. We saw one of these users on admin.phacility.com earlier, but I wasn't able to identify a way that a modern account could get into this state.
Problems do not reproduce when downgrading svn client:
Oh, the highlight itself actually is a little off if the reply is threaded. We move the comment up a little bit to make it visually thread a little more cleanly, but the highlight doesn't get a corresponding offset.
There are three different highlights at play here, visible in this screenshot:
Evan, rP52c4715bbcfb solvedthe issue. Losing low-resolution profile images is no problem.
Thanks for the quick solution!
Sun, Apr 23
This is a bug in the upstream. D17770 (or some similar patch) should be available later today.