Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Strange import artifacts.

+3
−0

Strange import artifacts.

I was looking at this post recently imported from books.se

https://writing.codidact.com/questions/276013

It has several things as answers that are posts from writers.se.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

1 answer

+4
−0

This is a fun one. This is a bug, but it's also not something we can retroactively fix, so... [status-known-about], I guess?

We discovered when we ran the import for the new stuff from Ebooks that importing stuff into a category that's already in-use is... to put it succinctly... a really bad idea. It:

  • Runs over every tag in the category doing post associations, instead of just the new tags;
  • Causes problems with voting by duplicating community-user records;
  • Tries to re-associate all existing posts with other posts based on the assumption that the Stack Exchange post ID is available, which it isn't for posts that have not just been imported.

We've mostly got away with this one; the number of posts imported was small, so the damage is limited mostly to a handful of posts that have things like this, as you've noticed. It's not practical to retroactively fix, unfortunately, but the number of posts affected is fortunately small.

We've worked out a fix for this in future using invisible temporary categories, so this doesn't affect our ability to import into existing categories going forward.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

General comments (6 comments)

Sign up to answer this question »