Page MenuHomePhabricator

Commons Delinker local clock dependency
Open, Needs TriagePublicFeature

Description

Originally from: http://sourceforge.net/p/pywikipediabot/bugs/647/
Reported by: Anonymous user
Created on: 2008-02-28 09:38:07
Subject: Commons Delinker local clock dependency
Assigned to: btongminh
Original description:
I tried to run delinker.py on a machine, which has time set in the future \(+30 minutes\). It is impossible for CD to work correctly \(because it does not read deletion logs\). I have created a small workaround. I don't know python at all \(I prefer Perl:\), so the code may look a little funny.


Version: unspecified
Severity: normal
See Also:
https://sourceforge.net/p/pywikipediabot/bugs/647

Details

Reference
bz55324

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 2:34 AM
bzimport set Reference to bz55324.
bzimport added a subscriber: Unknown Object (????).

patch to commonsdelinker/delinker.py

Logged In: YES
user\_id=1806226
Originator: NO

If the time is set to the future using timezones, it should not be a problem, since time.gmtime\(\) returns the timestamp in UTC.

I don't think it is a good idea to patch CD because your computer is not configured correctly.

  • priority: 5 --> 4
  • assigned_to: nobody --> btongminh

Logged In: YES
user\_id=2022153
Originator: NO

This patch eliminates problems with different time set on client or server side. It also solves limit=500 issue \(which is useful when we start delinker with parameter -since on larger project\). I don't really care if you apply this patch \(because I am already using it\), but for some people \(non-programmers\) it may be quite useful.

@Dvorapa: As per last comment and no reply to it, I am closing this task as declined.

Reopened because delinker was ported to core script package

Xqt changed the subtype of this task from "Task" to "Feature Request".