[Python-Dev] Posting frequent spurious changes in bugtracker (original) (raw)
Brett Cannon brett at python.org
Thu Jan 3 21:13:37 CET 2013
- Previous message: [Python-Dev] Posting frequent spurious changes in bugtracker
- Next message: [Python-Dev] Posting frequent spurious changes in bugtracker
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Jan 3, 2013 at 2:58 PM, Jesus Cea <jcea at jcea.es> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
This happens to me very frequently. I get the notification about new issues open in the bugtracker. If I see an interesting "bug", I usually open a Firefox tab with it, to monitor it, decide if I will work on it in the future, whatever. When I have time to decide, I proceed. If I find the issue interesting but don't have the time to work on it, or somebody else is taking care of it, I just add myself to the nosy list, and close the tab. The problem with this is that even if I reload the tab, flags are usually stale and when I add myself to the nosy list, I revert flags to the old value. This happens frequently. Last time: <http://bugs.python.org/issue16833#msg178917> I think tracker should keep a "version" hidden field, and refuse to act if the version on server is different that the just posted changes. Or something.
I think this should probably go upstream to Roundup if you want to see it implemented as it's a general thing and not specific to our instance.
Or am I doing something fundamentally wrong?. I reflesh 99% of the time, but could forget sometimes, and some other times I need a "shift+reload" to bypass browser cache. Well, I would argue you are doing something fundamentally wrong by submitting anything without refreshing first. It is a form so technically nothing is being done incorrectly in changing values based on what you submit, whether you view them stale or not.
If you want to keep this workflow going I would write a greasemonkey script which refreshes those tabs you leave open on occasion to avoid this issue.
-Brett
PS: Tracker tells me about conflicts ocasionally, but most of the time the stale flags are not noticed.
- -- Jesús Cea Avión // /// /// jcea at jcea.es - http://www.jcea.es/ // // // // // jabber / xmpp:jcea at jabber.org // // ///// . // // // // // "Things are not so easy" // // // // // // "My name is Dump, Core Dump" /// /// // // "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQCVAwUBUOXi2Zlgi5GaxT1NAQK6ewQAlCv0RKb3/y6tzdjggm4JqOjt0E9vYyZJ o0FIC+KBTrVtWrACiBOKCHPVsvJ1KB+6RzQ4FJdIyeOzG8Kv/E0HUNDufLGjr41C NCd4O8FN0tpHIfJkpC3PbkinyhZpviQL7YindAteb92sa+QFm8Rp+QCKBFRecMUX A7WLf+Gk8pE= =famI -----END PGP SIGNATURE-----
Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/brett%40python.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20130103/a33d87f5/attachment.html>
- Previous message: [Python-Dev] Posting frequent spurious changes in bugtracker
- Next message: [Python-Dev] Posting frequent spurious changes in bugtracker
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]