Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notices are still on some posts after claiming SE accounts and the score appears to only count votes on posts after the account was claimed #343

Open
cellio opened this issue Dec 11, 2020 · 1 comment
Labels
area: import Changes to the SE import scripts complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. priority: medium type: bug Something isn't working

Comments

@cellio
Copy link
Member

cellio commented Dec 11, 2020

https://meta.codidact.com/questions/279807

These users Cobaltduck and Oddeer both claimed their SE accounts and their posts are correctly associated.

However on some of the posts, example 1, example 2 there is still a notice saying that it was sourced from SE which is no longer needed and doesn't appear on my claimed posts.

Also, both profiles seem to have a much lower score then would be expected, what it looks like to me is that votes I cast on their posts don't count if the account had yet to be claimed. Currently, if I go upvote one of their posts it does increase their score.

(See meta post for links.)

We saw some earlier cases of after-claim attribution notices on Writing and Outdoors (maybe SciSpec too), which were reported and fixed in the DB by Art at the time. We thought those were one-off glitches at the time, and they were discovered soon after the import (as the communities were setting up), so we didn't notice any before-vs-after-claim voting effects at the time. We probably need to figure out how to check all the imports for this situation.

@cellio cellio added type: bug Something isn't working priority: medium area: import Changes to the SE import scripts complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. labels Dec 11, 2020
@ArtOfCode- ArtOfCode- removed their assignment Jul 31, 2021
@cellio
Copy link
Member Author

cellio commented Jul 26, 2023

Problem still exists. Presumably a data error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: import Changes to the SE import scripts complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. priority: medium type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants