Opened 3 weeks ago

Closed 3 weeks ago

Last modified 3 weeks ago

#19143 closed enhancement (fixed)

Make bug report CGI script drop anonymous reports from old ChimeraX versions

Reported by: Tom Goddard Owned by: Greg Couch
Priority: moderate Milestone:
Component: Infrastructure Version:
Keywords: Cc: Eric Pettersen
Blocked By: Blocking:
Notify when closed: Platform: all
Project: ChimeraX

Description

To reduce the burden triaging duplicate bug reports we decided yesterday in ChimeraX meeting to not accept bug reports with no user email from older ChimeraX versions. We will have the CGI script that receives the bug reports check for these and not forward them via email to Trac and Eric. There should be a 1 month grace period after a new ChimeraX is released where we still accept anonymous reports from the previous release.

Change History (3)

comment:1 by Greg Couch, 3 weeks ago

Right now, since there is a 1.10.1 release. Should we reject anonymous bug reports from 1.10?

comment:2 by Tom Goddard, 3 weeks ago

We patched 1.10 because of some often encountered bugs so I think we should probably only take anonymous bugs for 1.10.1. That way we avoid getting the many duplicates of the 1.10 bugs that were patched.

comment:3 by Greg Couch, 3 weeks ago

Resolution: fixed
Status: assignedclosed

Makes sense to me too.

I changed the bug report dialog to catch HTTP CONFLICT errors and show the error message. And, correspondingly, I've changed the logic in the bug submission cgi script to give a HTTP CONFLICT error when the version of ChimeraX is too old. That only happens, if and only if, the version of ChimeraX is newer than my commit. For older versions of ChimeraX, it acts as before -- it returns HTTP OK for the bug report submission, but drops them. That way, when the current daily build is obsolete, the error response will say:

"<body><h3>Obsolete Version of ChimeraX Detected</h3>"
"<p>You need to update to the current version of Chimerax if you"
" want to report anonymously. Otherwise, please supply an email"
" address so we can tell you if the bug is already fixed or ask"
" for more information."

Other CONFLICT responses can be added later.

Last edited 3 weeks ago by Greg Couch (previous) (diff)
Note: See TracTickets for help on using tickets.