Re: Issue 2241 in reviewboard: failed diffs are stored in memcached and not being updated after fixing the actual problem

2013-04-12 Thread reviewboard
Comment #3 on issue 2241 by jon.bark...@gmail.com: failed diffs are stored in memcached and not being updated after fixing the actual problem http://code.google.com/p/reviewboard/issues/detail?id=2241 This appears to still be an issue. Is there a fix for this planned? -- You received this m

Re: Issue 2241 in reviewboard: failed diffs are stored in memcached and not being updated after fixing the actual problem

2012-12-23 Thread reviewboard
Updates: Labels: Component-DiffViewer Comment #2 on issue 2241 by trowb...@gmail.com: failed diffs are stored in memcached and not being updated after fixing the actual problem http://code.google.com/p/reviewboard/issues/detail?id=2241 (No comment was entered for this change.) -- You

Re: Issue 2241 in reviewboard: failed diffs are stored in memcached and not being updated after fixing the actual problem

2011-09-01 Thread reviewboard
Comment #1 on issue 2241 by trowb...@gmail.com: failed diffs are stored in memcached and not being updated after fixing the actual problem http://code.google.com/p/reviewboard/issues/detail?id=2241 Issue 2242 has been merged into this issue. -- You received this message because you are subsc

Issue 2241 in reviewboard: failed diffs are stored in memcached and not being updated after fixing the actual problem

2011-08-17 Thread reviewboard
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2241 by sergey.s...@googlemail.com: failed diffs are stored in memcached and not being updated after fixing the actual problem http://code.google.com/p/reviewboard/issues/detail?id=2241 * NOTE: Do not post confidential info