Mark Smith (
mark) wrote in
dw_maintenance2013-10-23 08:56 pm
Importer update
Hi all --
Some have noticed that re-importing to get new comments hasn't been working for a while. This has been fixed; it was an operational issue (the importer cache wasn't being cleaned).
Anyway, if you have been having trouble getting recent comments to import onto DW, things should be working now. Please give it a shot.
Edited: Also, if you are still having importer troubles, please open a new request and let us know here:
http://www.dreamwidth.org/support/submit
Thanks and sorry for the trouble!

no subject
no subject
no subject
no subject
-J
no subject
no subject
It worked!
:)
no subject
no subject
no subject
This is brilliant. Dreamwidth rules!
no subject
no subject
Can you open a support request along with any errors or messages that you get in your inbox when you try? Thanks!
no subject
Thanks for the response.
no subject
Awesome! It might take a bit until somebody can look into it, problems with the importer take extra troubleshooting and there aren't a whole lot of people who are qualified to do it, but we will keep on it no matter how long it takes to get fixed.
no subject
At least you folks don't have the thankless job of trying to fix the Affordable Care Act website!
no subject
no subject
no subject
I did put in a support request about this a long time ago. Not sure whatever happened with that.
no subject
This has been fixed actually but the fix isn't live yet.
Regards,
90d
P.S. I forgot to mention that you can see what got fixed or improved in our code tours.
no subject
no subject
Here is a livejournal entry that has comments that did not import into the equivalent dreamwidth entry, followed by the equivalent dreamwidth entry:
http://therealjae.livejournal.com/1305022.html
http://jae.dreamwidth.org/1369328.html
-J
no subject
Can you open a support request with that info?
no subject
-J
no subject
Yes, it's the best way to gather data on complex problems such as this. The importer is a very complicated system with a lot of moving parts and very few people -- ultimately, the people with the experience in troubleshooting the entirety of the system and the system access for the necessary logs, which pretty much means just Mark -- can do the heavy diagnosis necessary. That means that a problem requiring lots of troubleshooting can take a lot of time, because it requires Mark to have the uninterrupted time necessary to do the investigation and it isn't the sort of thing you can say, going in, "this will take 2 hours to fix" -- it could be readily obvious to someone with that experience in troubleshooting, or it could be the sort of thing that takes dozens or even hundreds of person-hours to break down to component parts and figure out what's failing. Things not being solved immediately doesn't mean they aren't being worked on or won't ever be solved. We aren't always perfect at communicating that, but that doesn't mean we're ignoring the problem, just that we literally cannot give you a time estimate.
no subject
For what it's worth, even the sort of acknowledgement comment that you gave me two comments back is helpful in making people like me feel like we're not just shouting into the ether. I updated my last support request with new information every few weeks for months and months, and heard nothing at all in response to any of those steps until this week. Even just "hi! support people do still exist, and an actual human being read this!" would have made me feel less despairing about it.
-J
no subject
no subject
I'll echo what I said to Denise, though--it would make me feel much better about things taking so long if there were someone who could a) say "I read this--I can't do anything about it yet, but someone is reading this and keeping track of its existence!" And then if it ends up going literally months and months again, just coming in and giving a short explanation for why it's taking so long would make us feel much more confident that support requests are still the active way to ask for help here at dreamwidth.
-J
no subject
In the past, we've found that more people are annoyed by frequent "we haven't forgotten about this but there's nothing new we can add" style updates than find them helpful, but obviously that differs from person to person.
no subject
Imports are heavy and take a lot of system resources, particularly comment imports. They're also heavy on the remote site. There's no way for us to say "give us only new comments" so we have to ask for every single comment ever posted, just in case anything has changed.
This is obviously not efficient and so we limit it. Please try every other day -- and if you still have issues, then let us know.
no subject
-J
no subject
no subject
I need instructions how to setup DW soft on my server.
no subject
I'm not sure, but we'll look into that. Is there something you were looking for that I can help you with?