I can duplicate this, it happens when the form has been open > 24hrs (the timeout for antispam logic) before submitting it.
Igor, I replicated this by changing allura/lib/utils.py:AntiSpam.validate_request so that it always raises a ValueError. E.g by lowering the 24hr to 1 second. We should first, make it so the parent post doesn't get marked as edited - that's clearly a bug. Second, if there's an easy, generic way to preserve the content and re-populate the form that'd be good. I suspect that will be challenging though since this logic runs for all form submissions of any type. We may need to brainstorm other options if folks legitimately keep forms open that long very frequently. --- ** [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:** Wed Nov 06, 2013 11:17 PM 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.
