[Bug 44145] [Errors 992] Failed data retrieval shouldn't update Last update column

2014-09-14 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=44145

--- Comment #3 from Nemo federicol...@tiscali.it ---
Created attachment 16464
  -- https://bugzilla.wikimedia.org/attachment.cgi?id=16464action=edit
800 alive wikis currently erroring out on wikistats

(In reply to Daniel Zahn from comment #2)
 you know, that actually happens on the database level.

I don't challenge the technical correctness, but the timestamp can get quite
useless for presentation to the users. If that's fine enough, maybe the focus
should be instead on reducing such errors.

I run checkalive.py and out of 3159 rows with error 991 or higher there are at
least 800 which actually seem alive, whose URLs I attach.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 44145] [Errors 992] Failed data retrieval shouldn't update Last update column

2014-09-12 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=44145

--- Comment #2 from Daniel Zahn dz...@wikimedia.org ---
you know, that actually happens on the database level. the column for timestamp
uses 'on update CURRENT_TIMESTAMP', so every time something is being touched,
it also updates the timestamp. and in cases where fetching fails, there is also
something to update, the http return code, which then also triggers the ts.


| ts   | timestamp| NO   | | -00-00 00:00:00 |
on update CURRENT_TIMESTAMP |

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 44145] [Errors 992] Failed data retrieval shouldn't update Last update column

2013-12-07 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=44145

Robert Hanke ro...@gmx.de changed:

   What|Removed |Added

 CC||ro...@gmx.de
   Assignee|wikibugs-l@lists.wikimedia. |dz...@wikimedia.org
   |org |

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 44145] [Errors 992] Failed data retrieval shouldn't update Last update column

2013-12-07 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=44145

Robert Hanke ro...@gmx.de changed:

   What|Removed |Added

 Status|NEW |ASSIGNED

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 44145] [Errors 992] Failed data retrieval shouldn't update Last update column

2013-01-20 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=44145

Andre Klapper aklap...@wikimedia.org changed:

   What|Removed |Added

   Priority|Unprioritized   |Normal

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 44145] [Errors 992] Failed data retrieval shouldn't update Last update column

2013-01-19 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=44145

--- Comment #1 from Nemo federicol...@tiscali.it ---
Same for errors 991 due to lag, for instance
http://wikicafe.metacafe.com/en/api.php?action=querymeta=siteinfomaxlag=5
  error code=maxlag info=Waiting for a database server: 14 seconds lagged
(wikicafe is probably never not lagged, so my random click was particularly
unlucky).

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l