Stats Page Query Bug

[cesswairimu]

Hi all,

We are having trouble with queries in the stats page for some of data for year 2013. This is a planning issue for going about solving that and also removing spam users on the site

Issues:

• Stats downloading returns "Page does not exist" for dates prior to early 2013 Stats downloading returns "Page does not exist" for dates prior to early 2013 #5490
• Stats Download And Site Overload Stats Download And Site Overload #5524

Affects:

• Add 'all time' option for stats Add 'all time' option for stats #5904

Affected by/related to:

• Spam account detection/reduction planning Spam account detection/reduction planning #5450

@skilfullycurled and anyone else feel free to edit

[skilfullycurled]

Thanks opening the discussion @cesswairimu.

Preface: not sure the best practices of using usernames so I'm including the UID. Seems like it'd be okay considering people's usernames are public info, but just being cautious.

In any case.

I have some very strange news to report, not sure if it's what's causing the 4/23/13 issue but there were four people who created accounts on that day. For these users, if you go directly to their profile page by entering the username manually into the correct route (.../profile/username), all of their profiles work and none of them appear to be spam.

However!

Only one of those four users (UID 1205) has actually posted any content.

So what?

Here's where it gets weird. If you search for all of the users, search works fine for everyone except the user with the content (UID 1205) returns a "There was an error. Are you sure you have the right address?" page (this is our version of a 404, no?).

[jywarren]

Hi, just to help with debugging, I think it's OK to share this username because it is indeed public already and I actually know them: https://publiclab.org/profile/dorncox

How are you searching for their username? Using https://publiclab.org/api/srch/profiles?query=dorncox ? which for me works without an error?

[skilfullycurled]

Just putting the name dorncox in the search bar.

[skilfullycurled]

Just looked at your update in #5490. This seems unrelated now, although I guess that's still in progress. Who knows, might be the linchpin of the entire memory leak! : P

[jywarren]

Ah, well the navbar search no longer searches for usernames, as we're in the midst of a major rework of search systems: #5708 #5824. But I think i found some related issues in #5490

…

On Mon, Jun 17, 2019 at 11:25 PM Benjamin Sugar ***@***.***> wrote: Just putting the name dorncox in the search bar. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5917?email_source=notifications&email_token=AAAF6JZTR73TBGO7T6JQY2LP3BIPDA5CNFSM4HY3BYO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX5BZCY#issuecomment-502930571>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAF6J5JHWLIWGZWJYFBXOLP3BIPDANCNFSM4HY3BYOQ> .

[skilfullycurled]

Okay, for what it's worth to debugging those issues, the other names at least say that nothing was found. In the meantime, please give my apologies to dorncox. Mistakes were made. I hold a press conference to officially apologize and make a correction in tomorrows paper.

[jywarren]

Dorn is a farmer of good humor and grace and you're surely not on his wrong side :-)

…

On Mon, Jun 17, 2019 at 11:33 PM Benjamin Sugar ***@***.***> wrote: Okay, for what it's worth to debugging those issues, the other names at least say that nothing was found. In the meantime, please give my apologies to dorncox. Mistakes were made. I hold a press conference to officially apologize and make a correction in tomorrows paper. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5917?email_source=notifications&email_token=AAAF6J2BY2TYPJ4CNXHKKBDP3BJOVA5CNFSM4HY3BYO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX5CEKA#issuecomment-502932008>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAF6J33W47AFI6JNNMM7ODP3BJOVANCNFSM4HY3BYOQ> .