I've have repeatedly attempted to debug articleinfo. After having gotten a local copy functional on my computer, I thought I had found the bug. When I went to run a test where the bug was, the test never was executed. This leads me to conclude that this tool broken in more locations than one and I can't find them. I have worked countless hours trying to fix this thing, and failed. At this point, I am declaring my defeat. I am unable to fix the bug.
However, this does not mean it's unfixable. I have a feeling that this issue may be caused by Redis, while I'm no longer certain what's bugged up and what's not, perhaps someone who has experience with Redis can take a look and see if that's the problem. All the info seems to point to a non-code related issue. This problem has randomly popped since labs started having issues. Since the code, the API, and the DB haven't changed, it's reasonable to assume some other dependency such as Redis. Otherwise I'm declaring it a lost cause. This code is so ridiculously, unnecessarily complex, and has so many outside dependencies, it's hard to tell what is working and not.
I'm sorry everyone.
Cyberpower678
English Wikipedia Account Creation Team
Mailing List Moderator
Cyberpower678, in behalf of the encyclopedia, thank you for your efforts on articleinfo so far. But all might not be lost; I have been arguing that we have been seeing a DevOps issue, all this time. (What I have characterized as a resource being stepped on.)
The outside dependencies need to be addressed, one factor at a time. Maybe we can isolate down to one target environment, one article history snapshot, to make the behavior repeatable. That would help to isolate a Redis problem, if that is what one of the Ops issues might be.
--Ancheta
On Wed, Jul 15, 2015 at 3:59 PM, Maximilian Doerr < maximilian.doerr@gmail.com> wrote:
I’ve have repeatedly attempted to debug articleinfo. After having gotten a local copy functional on my computer, I thought I had found the bug. When I went to run a test where the bug was, the test never was executed. This leads me to conclude that this tool broken in more locations than one and I can’t find them. I have worked countless hours trying to fix this thing, and failed. At this point, I am declaring my defeat. I am unable to fix the bug.
However, this does not mean it’s unfixable. I have a feeling that this issue may be caused by Redis, while I’m no longer certain what’s bugged up and what’s not, perhaps someone who has experience with Redis can take a look and see if that’s the problem. All the info seems to point to a non-code related issue. This problem has randomly popped since labs started having issues. Since the code, the API, and the DB haven’t changed, it’s reasonable to assume some other dependency such as Redis. Otherwise I’m declaring it a lost cause. This code is so ridiculously, unnecessarily complex, and has so many outside dependencies, it’s hard to tell what is working and not.
I’m sorry everyone.
Cyberpower678
English Wikipedia Account Creation Team
Mailing List Moderator
Maintainers: Cyberpower678, Technical 13, MusikAnimal, Elee, Nakon, L235 xTools mailing list xTools@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/xtools
On the bright side, I’ve got 50% of wikihistory adapted for use on enwiki, and things are running smoothly so far. A nice change of pace. I just wish APPER didn’t use a whole bunch of deprecated functions.
Cyberpower678
English Wikipedia Account Creation Team
Mailing List Moderator
From: xtools-bounces@lists.wikimedia.org [mailto:xtools-bounces@lists.wikimedia.org] On Behalf Of Ancheta Wis Sent: Wednesday, July 15, 2015 11:16 PM To: Discussion list for xTools Subject: Re: [xTools] Articleinfo
Cyberpower678, in behalf of the encyclopedia, thank you for your efforts on articleinfo so far. But all might not be lost; I have been arguing that we have been seeing a DevOps issue, all this time. (What I have characterized as a resource being stepped on.)
The outside dependencies need to be addressed, one factor at a time. Maybe we can isolate down to one target environment, one article history snapshot, to make the behavior repeatable. That would help to isolate a Redis problem, if that is what one of the Ops issues might be.
--Ancheta
On Wed, Jul 15, 2015 at 3:59 PM, Maximilian Doerr maximilian.doerr@gmail.com wrote:
I’ve have repeatedly attempted to debug articleinfo. After having gotten a local copy functional on my computer, I thought I had found the bug. When I went to run a test where the bug was, the test never was executed. This leads me to conclude that this tool broken in more locations than one and I can’t find them. I have worked countless hours trying to fix this thing, and failed. At this point, I am declaring my defeat. I am unable to fix the bug.
However, this does not mean it’s unfixable. I have a feeling that this issue may be caused by Redis, while I’m no longer certain what’s bugged up and what’s not, perhaps someone who has experience with Redis can take a look and see if that’s the problem. All the info seems to point to a non-code related issue. This problem has randomly popped since labs started having issues. Since the code, the API, and the DB haven’t changed, it’s reasonable to assume some other dependency such as Redis. Otherwise I’m declaring it a lost cause. This code is so ridiculously, unnecessarily complex, and has so many outside dependencies, it’s hard to tell what is working and not.
I’m sorry everyone.
Cyberpower678
English Wikipedia Account Creation Team
Mailing List Moderator
_______________________________________________ Maintainers: Cyberpower678, Technical 13, MusikAnimal, Elee, Nakon, L235 xTools mailing list xTools@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/xtools