Stuck at 47.5%
in
12 posts,
7 voices
djace
User
|
I gladly enjoyed the old script and used it extensively, so today I removed it and installed this version. Although it works fine in some of my feeds, I've noticed some unusual behavior in others. a) It gets stuck at "Marking target items as read: 47.5%" on some feeds.
This behavior is intermittent on some feeds and permanent on others. |
Crend King
Script's Author
|
Thanks for trying the script. What you mentioned here are what I mainly observed in some previous versions of this script. The current version works fine in MOST cases (which means not ALL cases). I can explain the slowness at 47.5% to you if you are interested. As mentioned in the script description, I use GR API to retrieve entry information. I need the server-side information of the currently selected entry. Similar as Google Reader view's paging mechanism, I request multiple entries' information in one time, and check if the currently selected entry is in the returned bundle. If yes, proceed the next step; if not, request the next bundle. Obviously, if you have a lot of entries, no matter read or not, above what you selected, if may take a while a get to it. Variable "req_list_length" is the number of entry bundle per request. You can tweak this value per your reading pattern. Visual marking is another potential issue. Fortunately, I think the issue is only "visual". Many times if you notice wrong marking, refresh first and see. The issue comes from the synchronization between server-side and client-side. If you had not refresh the GR page, and the server had updated, the issue might happen. Notice GR's "Mark all as read" always refreshes and will never suffer this problem. If you still have problems, make sure to update to latest version. If still, post another entry. Thanks! |
lomedhi
User
|
I'm afraid I'm having the same problem -- stuck at 47.5%. I've tried adjusting req_list_length, to no avail. I am using the latest version, just downloaded for the first time today. (I've also set reload_after_mark to true, but the script never gets to that point anyway.) |
|
Crend King
Script's Author
|
I'm sorry for the inconvenience, but I cannot reproduce the problem myself. I want to know if there is any error output when you use the script. You can confirm this by doing the following steps: 1) Go to your Google Reader page.
If there is, please post them here. If there is not, and you are interested in solving the problem, please contact me directly by my email. Thank you! |
|
lomedhi
User
|
After updating from FF 3.0.10 to 3.0.11 and uninstalling/reinstalling your script, it is now working. I don't know what made the difference, but I appreciate your help. |
Crend King
Script's Author
  |
I updated the script to 1.3.8, using Firefox native JSON object. It should noticeably speed up the marking process, especially if there are lots of unread items. |
swaldman
User
|
I've just tried this script, and I'm seeing the same problem. It stops at 47.5%, and I've waited for ten minutes and seen no change.
Let me know if I can provide any other info to help diagnose this. |
Savage702
User
|
I was just told about this script, very cool idea, except I'm having the same issue. Firefox 3.5.5
Have tons of feeds, many with same articles. Did a search for Verizon, go into List view, select top article, select "Mark below as read", stops at 47.5%. There is an error that shows up each time you try to do this:
Thanks! |
|
Savage702
User
|
Ok, doing further playing around/testing on this. I've found that in an actual subscription, marking some as read works fine. When ever I try to use it from a search result, either of an individual subscription or of all items, it gets stuck at 47.5%, with the same JSON.parse error. |
Dee Es
User
 |
Same issue, not limited to search results.
|
Bgmin0t
Scriptwright
|
Same problem. Reliably gets stuck at 45 or 47.5%. |
|
Crend King
Script's Author
|
The new version 1.4 is verified working for the current (03/03/2011) Google Reader. |
