Bugs item #1903762, was opened at 2008-02-28 10:38 Message generated for change (Comment added) made by sswierkosz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=603138&aid=1903762...
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: other Group: None Status: Open Resolution: None Priority: 4 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Bryan (btongminh) Summary: Commons Delinker local clock dependency
Initial Comment: 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.
----------------------------------------------------------------------
Comment By: Szymon Świerkosz (sswierkosz) Date: 2008-02-28 16:31
Message: 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.
----------------------------------------------------------------------
Comment By: Bryan (btongminh) Date: 2008-02-28 13:02
Message: 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.
----------------------------------------------------------------------
You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=603138&aid=1903762...