Last modified: 2012-11-21 14:01:03 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 T37364, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 35364 - On doing "update data" the progress status crosses 100%
On doing "update data" the progress status crosses 100%
Status: RESOLVED WORKSFORME
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
All All
: Lowest minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-20 19:17 UTC by Nischay Nahata
Modified: 2012-11-21 14:01 UTC (History)
3 users (show)

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


Attachments
Screenshot (51.74 KB, image/png)
2012-03-21 02:26 UTC, Nischay Nahata
Details

Description Nischay Nahata 2012-03-20 19:17:29 UTC
The progress fill flows out of the bar and progress shows 108% when refreshing the browser-Chrome
Comment 1 Nischay Nahata 2012-03-21 02:26:24 UTC
Created attachment 10296 [details]
Screenshot
Comment 2 [[kgh]] 2012-06-08 11:26:19 UTC
I have experienced this too in the past. I think that this occurred only on very fresh installs. I very much doubt that this has any relation to the browser used.
Comment 3 Jeroen De Dauw 2012-06-08 12:55:12 UTC
Seems like a rather small layout problem compared to how bad the UI and workflow for this feature are in general :)
Comment 4 MWJames 2012-11-07 04:40:53 UTC
Nischay, I guess the SQLStore3/$refreshjob->getProgress(); calculation should only return a base that allows a max of 100%.

If you think this problem is solved could you close this one.

PS: Just looked at SMWAdmin, this one really needs some love.
Comment 5 Nischay Nahata 2012-11-07 04:57:50 UTC
I am not sure how this has been fixed in SQLStore3, but we can close it; and open it again if needed.

(In reply to comment #4)
> PS: Just looked at SMWAdmin, this one really needs some love.

I don't see much problem with SMWAdmin, if you have better suggestions please make a small mock-up somewhere so anyone (newbies?) can help with that.
Comment 6 Andre Klapper 2012-11-21 14:01:03 UTC
[RESOLVED WORKSFORME as per comment 5 to get rid of deprecated LATER resolution]

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


Navigation
Links