Last modified: 2014-04-28 12:07:19 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T66488, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 64488 - Consecutive rollbacks problem
Consecutive rollbacks problem
Status: RESOLVED FIXED
Product: Huggle
Classification: Unclassified
Application (Other open bugs)
3.0.0
PC Linux
: High critical
: ---
Assigned To: Peter Bena
:
Depends on:
Blocks: 34892
  Show dependency treegraph
 
Reported: 2014-04-26 19:31 UTC by Amol Bhave
Modified: 2014-04-28 12:07 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Amol Bhave 2014-04-26 19:31:53 UTC
On a fast connection, then loading of the next edits happens really fast. So sometimes, if you rolled back an edit by pressing 'Q', and then before you can actually release the Q button, the next edit gets loaded and gets rollbacked again. I think this was the behavior I observed. It may also be a debouncing problem with the key and the key actually got pressed two times in fast succession.

Anyways, there should be an artificial short delay after the edit appears on the screen and you are allowed to rollback it. Even something like half a second delay will save a few unnecessary rollbacks. Because you won't be rollbacking changes half a second later it gets loaded, not enough time to even review.
Comment 1 Peter Bena 2014-04-27 11:39:13 UTC
Which version of huggle is that
Comment 2 Peter Bena 2014-04-27 11:39:59 UTC
loading of next edits happens very fast even when you are disconnected in huggle 3, so I assume you are on older version
Comment 3 Peter Bena 2014-04-27 11:42:36 UTC
this what you describe can hardly happen on huggle 3, you either load a next edit (matter of less than a second) which can be immediately rolled back, or in case you chose to auto-load newer revision, huggle display "hold your fire" banner during which the rollback is forbidden and silently ignored, so I am unable to reproduce this, are you really talking about latest huggle 3.0.0.0 121x+?
Comment 4 Amol Bhave 2014-04-27 15:35:33 UTC
My version is: 3.0.0.0 build: 1200 0a0c6de
OS: Ubuntu 14.04 LTS.

My Wikipedia contribution history for the relevant time is as follows:
--------------------------------------------
00:44, 27 April 2014 (diff | hist) . . (+945)‎ . . N User talk:99.17.204.20 ‎ (Message re. Terry Richardson (HG 3))
00:44, 27 April 2014 (diff | hist) . . (+983)‎ . . N User talk:2.223.220.58 ‎ (Message re. TU Delft Faculty of Architecture (HG 3))
00:44, 27 April 2014 (diff | hist) . . (-473)‎ . . m Terry Richardson ‎ (Reverted edits by 99.17.204.20 (talk) (HG 3))
00:44, 27 April 2014 (diff | hist) . . (-12)‎ . . m TU Delft Faculty of Architecture ‎ (Reverted edits by 2.223.220.58 (talk) (HG 3)) (current) [rollback: 1 edit]


I reverted the 'TU Delft' edit by pressing the 'Q' key. And then in succession, the 'Terry Richardson' edit got loaded and also got automatically reverted back. I didn't get a 'hold your fire' banner after that. Surprisingly, the User talk page for the editor of 'TU Delft' got warned after the 'Terry Richardson' edit was accidentally reverted. I am on a really fast/low latency connection.
Is it the case that the 'hold your fire' gets enabled after the talk page is written? This might explain this.
Comment 5 Peter Bena 2014-04-27 16:25:52 UTC
no, this seems like a bug, whether it's a bug in Trusty, or Huggle is a question. I experience weird issues since I upgraded to ubuntu 14.04 and Qt developers told me that ubuntu has fucked up Qt in 14.04 and they need to fix it. There is a number of similar reports, so I am not sure what to do now, I know about multiple things that broke since then
Comment 6 Peter Bena 2014-04-28 12:07:19 UTC
http://git.io/Q4MGVg

Open preferences -> performance and check "Require delay bla bla" set like 2 or more seconds in the text box. Now you will have to wait 2 or more seconds after load of every new edit before you will be able to revert it

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links