Problem calling syncitems with no start date on an older journal

Jul 29, 2008 17:01

This is a revision of a previous question I submitted, with more information.

IMPORTANT EDIT: I found that the problem is not what I thought it was, and the error should now be easy to reproduce. The problem occurs when the built-in edit journal privacy tool is used. I have edited this entry to reflect this fact, and removed misleading references ( Read more... )

client: export, code: c#, client, bugs, client: flat

Leave a comment

Comments 7

soundwave106 July 30 2008, 12:31:19 UTC
I'm curious if anyone knows the answer to this myself.

Do you have any sort of odd backdated entries? It sounds like the type of behavior you get on databases sometimes when a database index is screwed up, I'm trying to think of any possible cause...

Reply

sithjawa July 30 2008, 19:30:46 UTC
I'm sure I've got backdated entries somewhere within those 8,000. Probably not within the past 500, though. If you know on average how many items syncitems is likely to return on the first call, I could look through those items and see if there's anything particularly unusual.

Since syncitems also returns comments, could unusual behavior result from an edited comment? Has anyone tested how syncitems treats edited comments? (Comment editing has been around a while, so I'd expect so...)

I don't know how the LJ database is built... Chances are that if there's a strange thing you can do to a journal entry, I've done it. Without knowing how the database is built, however, it's hard to know what would be likely to cause a problem. If you think it would be useful, I could create a dummy journal and do some testing.

Reply

Aha! sithjawa July 30 2008, 20:21:19 UTC
AHA!

I made a test journal oak_and_sage. I tried various things, and as soon as I used the built in LJ "Edit Journal Privacy" tool to set all its public entries to friends only, the syncitems call started hanging.

oak_and_sage only has 7 entries, all of them test entries. Two were converted from public to friends only.

I did this on my real journal (this one) prior to finding LJ-SEC. Apparently, this causes problems.

Reply

Re: Aha! soundwave106 July 30 2008, 21:41:09 UTC
Nice job. :) Looks like something Livejournal will have to look into, I don't think any of us developers would have any control over this.

Reply


azurelunatic June 29 2009, 20:20:53 UTC
Tagged this with 'bugs', btw, since it is one.

Reply

sithjawa June 29 2009, 22:02:45 UTC
*nod*Thanks.

Reply


Leave a comment

Up