[allura:tickets] #6381 Allura tickets system intermittently discards replies to comments [ss4454]

[Igor Bondarenko <je...@users.sf.net>]

Closed #380.

Unfortunately, we're not able to fix this. Couple of developers tried to duplicate it, but it works well on local and sandbox setups. Code also looks okay. I'm thinking, maybe it's some problem with a production setup? Maybe someone from your team would be able to figure that out?

During testing we found some other bug, though. It goes like this:

1. Add a comment and couple of replies to it.
2. Delete the parent comment.
3. Try to reply to one of the former children of the deleted comment. You'll be redirected to url like `/p/t380/tickets/_discuss/thread/f45821e2/` and your reply wouldn't show up.


---

** [tickets:#6381] Allura tickets system intermittently discards replies to comments [ss4454]**

**Status:** in-progress
**Labels:** support p2 42cc 
**Created:** Thu Jun 20, 2013 01:28 PM UTC by Chris Tsai
**Last Updated:** Tue Sep 17, 2013 08:33 AM UTC
**Owner:** nobody

Ref: [allura:tickets:#4454]

keithmarshall:
>>>Within the browser view of a ticket, I'll select the "reply" option in one of the follow-up comment panes. I'll enter my reply, in the input pane which is presented. When I subsequently select the "post reply" option, it's a complete lottery as to whether the reply will actually be posted; all too frequently, the system records an edit to the original message, (in which I've changed nothing), while dropping the actual reply on the floor, whence it vanishes into oblivion.

>>>This is happening way too often; it is becoming increasingly frustrating.

me:
>>Can you provide a time frame for when this has been occurring (we've been working through some site issues the past few days which I could see as related) and some specific examples that we can check the logs for?

>>Also, as a personal recommendation, I've been using the Lazarus browser plugin (for FF and Chrome), and helped me recover lost text on many occasions.

keithmarshall:
>I've noticed it intermittently, over several months; pretty much, ever since MinGW migrated to the Allura platform. Most recent occurrence was today, (just a short while before I raised this issue itself), when I attempted to add the side issue references on https://sourceforge.net/p/mingw/bugs/1989/

>I experienced a similar issue yesterday, on https://sourceforge.net/p/mingw/bugs/1973/ (I think); tracking down any earlier occurrences may be too difficult to contemplate, but there have been several.

>Thanks for the Lazarus pointer; I'll certainly look into it. However, I've simply gotten into the habit of using Ctrl-A Ctrl-C in the input pane, just prior to selecting "post reply".

>One further point, which may or may not be related: sometimes, when a reply is successfully posted, it becomes divorced from its parent, and presented as an apparent top level discussion item, (usually with an intervening "page break").

So we don't need to do a lot of timestamp comparing to figure out which reply specifically, it looks like it's this one: https://sourceforge.net/p/mingw/bugs/1989/#3e85/cd7b/d222/aba9/76e9


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.