LJ comment importing

[yvi]

Can anyone help all those people having problems importing? Some of these requests have been sitting there for quite a long time.

http://www.dreamwidth.org/support/see_request?id=8279
http://www.dreamwidth.org/support/see_request?id=8309
http://www.dreamwidth.org/support/see_request?id=8337
http://www.dreamwidth.org/support/see_request?id=8378
http://www.dreamwidth.org/support/see_request?id=8451
http://www.dreamwidth.org/support/see_request?id=8575

I am not sure if all of those are related or anything.

Comments

[exor674]

Those all seem to be cases of LJ fail

[domtheknight]

The kind where if they try again, it'll work this time, or something is wrong with the LJ data and it won't work ever?

[dreamatdrew]

So not my area of expertise, but it looks like bad data coming from LJ. I'm 99% sure on #8575 and #8451, as that's an error that comes from malformed XML (something I'm all too familiar with at this point).

The XMLRPC recursion errors I THINK are LJ-internal error messages, as in thats an error that LJ is feeding back to us.


Of course, I could be COMPLETELY wrong...

[exor674]

at least from what others have said, it may be a bug on LJ's end... or it might be a "yeah, You've got enough of this page" and just cuts it off for some reason.

[dreamatdrew]

Silly thought, but could LJ be throwing out bad content-length headers, and that farking the XML?
THAT seems like a really easy mistake to make, actually......

[afuna]

Could it be a matter of slowness -- us timing out as we fetch the page?

[exor674]

I think our end should be an all or nothing thing -- either we get the whole page, or that it times out and errors and doesn't have the content.

Hrm, I wonder what happens if Perlbal hits it's limit while sending a huge page.

-- I guess this could also be a bug on LJ's end with escaping XML wrongly.