View Issue Details

IDProjectCategoryView StatusLast Update
0006102The Dark ModDesign/Codingpublic20.01.2024 16:51
ReporterGeep Assigned Totaaaki  
PrioritynormalSeveritynormalReproducibilityalways
Status resolvedResolutionfixed 
Summary0006102: MantisDB throws away bug new report again
DescriptionOnce again, I spent an hour getting a bug report just right, then when I hit the Submit button in Firefox, MantisDB says:

"APPLICATION ERROR 0002800

Invalid form security token. This could be caused by a session timeout, or accidentally submitting the form twice.
Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section."

But I'm hosed, all that work is lost. Sure, I should have remembered that MantisDB is a hostile environment, and refined the bug report offline first. But really, in 2022, can't it do better?

You'll similarly get all entry data thrown away for other causes:

"APPLICATION ERROR 0000011

A necessary field "category" was empty. Please recheck your inputs.
Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section."
Additional InformationThis isn't a "Dark Mod" bug, of course. I'm just kicking up a fuss here, hoping there's a MantisDB fix.

I'll reconstruct the clobbered bug report tomorrow. Too bummed out today.
TagsNo tags attached.

Activities

taaaki

taaaki

22.01.2023 20:22

administrator   ~0015849

From my reading on this issue, the failure likely happens due to a CSRF token expiry (i.e. Invalid form security token), which seems to occur if you're editing the bug form for a long time. The session gets garbage collected after 24mins, invaliding the security token in the process. I've upped this from 24mins to 8hrs, so I'll mark this as fixed for now, but please re-open if it still occurs.
Geep

Geep

23.01.2023 22:12

reporter   ~0015870

Thanks
Fiver

Fiver

29.12.2023 15:34

reporter   ~0016291

@taaaki:
I lost a report due to:
"
APPLICATION ERROR 0000027
You have reached the allowed activity limit of 15 events within the last 3600 seconds; your action has been blocked to avoid spam, please try again later.
Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.
"
I used back-button but the report was lost and I had to enter it again.
Is there a value you could adjust to prevent this from happening?
taaaki

taaaki

14.01.2024 19:47

administrator   ~0016370

@Fiver

I've been digging around, and it's a bit odd that you're getting rate limited. Users with the "reporter" role (or "developer") and not meant to be affected. Regardless, I've doubled the limit to 30, so please let me know if you run into the issue again
Fiver

Fiver

20.01.2024 16:51

reporter   ~0016387

@taaaki: Thanks! It didn't happen again until just recently when I got "You have reached the allowed activity limit of 30 events within the last 3600 seconds; your action has been blocked to avoid spam, please try again later." It seems to happen mostly when I add tags to issues. (Also, I accidentally created the tag "0006362" that you may delete.)

Issue History

Date Modified Username Field Change
20.09.2022 21:05 Geep New Issue
21.09.2022 17:40 stgatilov Assigned To => taaaki
21.09.2022 17:40 stgatilov Status new => assigned
22.01.2023 20:22 taaaki Status assigned => resolved
22.01.2023 20:22 taaaki Resolution open => fixed
22.01.2023 20:22 taaaki Note Added: 0015849
23.01.2023 22:12 Geep Note Added: 0015870
29.12.2023 15:34 Fiver Note Added: 0016291
14.01.2024 19:47 taaaki Note Added: 0016370
20.01.2024 16:51 Fiver Note Added: 0016387