January 14, 2009
I am using Camino and the bookmarklet to invoke Pukka to post pages to delicious. Everytime I do this when Pukka is not already running, I get the error "There was a login failture!". Yet if I just hit the "Ignore for now" button, the page posts perfectly well to delicious.
January 14, 2009
#1
something to try
Hi Emery.
The error is coming from Pukka's caching side, not the posting side. Whenever Pukka starts (and periodically once it's running), it checks in order to download your latest bookmarks & their info. This would explain why posting works just fine once you ignore the error.
I have seen problems in the Delicious API in some places, and not in others, such as you are seeing with posting vs. caching. When you are seeing this problem, could you please try the following to confirm that there is a problem on the Delicious side?
When you see this, please visit the following URLs in Camino, using your login info:
https://api.del.icio.us/v1/posts/recent
https://api.del.icio.us/v1/posts/all
Both should allow you to login and both should show your most recent bookmarks at the top.
Please let me know what you find, and thanks for your patience.
February 24, 2009
#2
I've been having the same
I've been having the same issue lately. I tried going to those two sites, but they didn't display any information at all, and viewing the page source only gave me this information:
<?xml version="1.0" standalone="yes"?>
<result code="access denied" />
<!-- fe06.api.del.ac4.yahoo.net uncompressed/chunked Mon Feb 23 22:09:50 PST 2009 -->
I tried accessing these pages yesterday and was prompted to enter my username and password, but after doing so it didn't display anything. Today I wasn't prompted even though I wasn't logged into my Delicious account, and even upon logging in it still didn't change the result of clicking on either of these two links.
February 24, 2009
#3
The 'access denied' is quite
The 'access denied' is quite interesting -- I have not heard of this anyplace until now. Would it be possible for you to contact Delicious support about this, pasting the snippet you've pasted to me? There seems to be something going on in the Delicious backend that is failing to log people in.
Forums are here: http://support.delicious.com/forum/
Thanks for your patience. This lead should help get to the bottom of this issue.
March 4, 2009
#4
I reached out to Delicious
I reached out to Delicious support about the issue, and here's what I got back:
Original Message Follows:
-------------------------
Username: gfitzp
Email: glenn@glennfitzpatrick.com
Message:
My login information doesn't appear to stick: I'm having issues
accessing
https://api.del.icio.us/v1/posts/recent
https://api.del.icio.us/v1/posts/all
I'm not prompted to enter my login and password when not logged in, and
when I am logged in I still get the following results:
This seems to be creating issues when logging into Delicious from 3rd
party apps such as Pukka. I get a login error, but if the error is
ignored, I can still post without issue. It seems to prevent me from
syncing bookmarks/tags, however.
=====
from Chris Draycott
to glenn@glennfitzpatrick.com
date Tue, Mar 3, 2009 at 5:56 PM
subject Delicious API issues
hide details 5:56 PM (8 hours ago)
Reply
Hi Glenn,
The api does not accept your browser cookie as authentication, since this is an xsrf concern. If you copy and paste the url into the browser (rather than follow a link), then you you should get a login prompt at which point data should appear as expected.
I’m not sure exactly what Pukka is doing, but I would imagine the post is working as they are posting your credentials to the api, which works fine., but direct requests from a browser are not a good or reliable way to do this.
Chris
March 4, 2009
#5
(Also, I just tried
(Also, I just tried copying/pasting the API links as recommended, and that seems to let me access the API results without issue.)
March 8, 2009
#6
Hmm, I'm not sure how pasting
Hmm, I'm not sure how pasting vs. clicking the links in a browser would make a difference, but perhaps it does. Another thing to try would be to use a browser other than your normal one (e.g., Camino instead of Safari).
Regardless, the reason the posting vs. caching/syncing differs is that they are different API calls on Delicious, and I think that Delicious is having issues on the caching method side.
I will send you a debug version of Pukka shortly that should log more about what is happening with Pukka behind the scenes. You can also reveal a debug console using Command-K or Window -> Console which may have more info on what is happening when a cache attempt fails.
June 9, 2009
#7
Eep! Sorry for the delay,
Eep! Sorry for the delay, just tried opening up Pukka and when I got the same error again now, I remembered I saved the error log I got a few months ago. I'm not sure if it might help or not, but here it is:
===== 2009-03-09 21:09:38 -0400 =====
Pukka/1.7.2 started
===== 2009-03-09 21:09:38 -0400 =====
Login failure while trying to fetch timestamp for gfitzp!
===== 2009-03-09 21:10:05 -0400 =====
Successful backup made for gfitzp
===== 2009-03-09 21:11:16 -0400 =====
Error parsing XML: Line 2: Extra content at the end of the document
===== 2009-03-09 21:11:19 -0400 =====
Error parsing XML: Line 2: Extra content at the end of the document
===== 2009-03-09 21:11:27 -0400 =====
Parsed 15 bookmarks (1 new, 0 updated, 14 skipped) and 1 tags (0 new, 1 skipped) for gfitzp
===== 2009-03-09 21:11:27 -0400 =====
We took 1.333582 seconds total for this user's cache
===== 2009-03-09 21:12:18 -0400 =====
Error parsing XML: Line 2: Extra content at the end of the document
===== 2009-03-09 21:12:25 -0400 =====
Error parsing XML: Line 2: Extra content at the end of the document
===== 2009-03-09 21:12:31 -0400 =====
Error parsing XML: Line 2: Extra content at the end of the document
===== 2009-03-09 21:15:15 -0400 =====
Successful backup made for gfitzp
===== 2009-03-09 21:16:03 -0400 =====
Parsed 964 bookmarks (2 new, 0 updated, 962 skipped) and 3 tags (0 new, 3 skipped) for gfitzp
===== 2009-03-09 21:16:03 -0400 =====
We took 50.191126 seconds total for this user's cache
===== 2009-03-09 21:18:05 -0400 =====
Parsed 15 bookmarks (1 new, 0 updated, 14 skipped) and 2 tags (0 new, 2 skipped) for gfitzp
===== 2009-03-09 21:18:05 -0400 =====
We took 1.213260 seconds total for this user's cache
===== 2009-03-09 21:23:04 -0400 =====
Successful backup made for gfitzp
===== 2009-03-09 21:23:23 -0400 =====
Parsed 15 bookmarks (1 new, 0 updated, 14 skipped) and 3 tags (1 new, 2 skipped) for gfitzp
===== 2009-03-09 21:23:23 -0400 =====
We took 1.213414 seconds total for this user's cache
===== 2009-03-09 21:25:09 -0400 =====
Parsed 15 bookmarks (1 new, 0 updated, 14 skipped) and 3 tags (0 new, 3 skipped) for gfitzp
===== 2009-03-09 21:25:09 -0400 =====
We took 1.225878 seconds total for this user's cache
===== 2009-03-09 21:25:45 -0400 =====
Parsed 15 bookmarks (1 new, 0 updated, 14 skipped) and 2 tags (0 new, 2 skipped) for gfitzp
===== 2009-03-09 21:25:45 -0400 =====
We took 1.231026 seconds total for this user's cache
===== 2009-03-09 21:28:45 -0400 =====
API gave an error status code of 999 when trying to fetch posts! See https://gfitzp@api.del.icio.us/v1/posts/all for details.
===== 2009-03-09 21:30:33 -0400 =====
Parsed 15 bookmarks (2 new, 0 updated, 13 skipped) and 4 tags (2 new, 2 skipped) for gfitzp
===== 2009-03-09 21:30:33 -0400 =====
We took 1.226056 seconds total for this user's cache
===== 2009-03-09 21:31:24 -0400 =====
Parsed 15 bookmarks (1 new, 0 updated, 14 skipped) and 3 tags (0 new, 3 skipped) for gfitzp
===== 2009-03-09 21:31:24 -0400 =====
We took 1.235644 seconds total for this user's cache
===== 2009-03-09 21:34:27 -0400 =====
API gave an error status code of 999 when trying to fetch posts! See https://gfitzp@api.del.icio.us/v1/posts/all for details.
===== 2009-03-09 21:35:07 -0400 =====
Parsed 15 bookmarks (1 new, 0 updated, 14 skipped) and 2 tags (0 new, 2 skipped) for gfitzp
===== 2009-03-09 21:35:07 -0400 =====
We took 1.220683 seconds total for this user's cache
===== 2009-03-09 21:36:40 -0400 =====
Error parsing XML: Line 2: Extra content at the end of the document
===== 2009-03-09 21:36:44 -0400 =====
Error parsing XML: Line 2: Extra content at the end of the document
===== 2009-03-09 21:36:50 -0400 =====
Parsed 15 bookmarks (1 new, 0 updated, 14 skipped) and 2 tags (0 new, 2 skipped) for gfitzp
===== 2009-03-09 21:36:50 -0400 =====
We took 1.264760 seconds total for this user's cache
===== 2009-03-09 21:38:34 -0400 =====
Error parsing XML: Line 2: Extra content at the end of the document
===== 2009-03-09 21:39:43 -0400 =====
Successful backup made for gfitzp
===== 2009-03-09 21:40:32 -0400 =====
Parsed 972 bookmarks (2 new, 4 updated, 970 skipped) and 5 tags (0 new, 5 skipped) for gfitzp
===== 2009-03-09 21:40:32 -0400 =====
We took 51.066968 seconds total for this user's cache
===== 2009-03-09 21:40:46 -0400 =====
Parsed 11 bookmarks (1 new, 4 updated, 10 skipped) and 3 tags (0 new, 3 skipped) for gfitzp
===== 2009-03-09 21:40:46 -0400 =====
We took 1.277234 seconds total for this user's cache
===== 2009-03-09 21:41:48 -0400 =====
Error parsing XML: Line 2: Extra content at the end of the document
===== 2009-03-09 21:41:56 -0400 =====
Parsed 15 bookmarks (1 new, 0 updated, 14 skipped) and 2 tags (0 new, 2 skipped) for gfitzp
===== 2009-03-09 21:41:56 -0400 =====
We took 1.264649 seconds total for this user's cache
===== 2009-03-09 21:43:00 -0400 =====
Parsed 15 bookmarks (1 new, 0 updated, 14 skipped) and 2 tags (1 new, 1 skipped) for gfitzp
===== 2009-03-09 21:43:00 -0400 =====
We took 1.259837 seconds total for this user's cache
===== 2009-03-09 21:45:31 -0400 =====
Successful backup made for gfitzp
===== 2009-03-09 21:45:45 -0400 =====
Parsed 9 bookmarks (1 new, 6 updated, 8 skipped) and 3 tags (0 new, 3 skipped) for gfitzp
===== 2009-03-09 21:45:45 -0400 =====
We took 1.183699 seconds total for this user's cache
===== 2009-03-09 21:48:49 -0400 =====
Parsed 15 bookmarks (2 new, 0 updated, 13 skipped) and 5 tags (0 new, 5 skipped) for gfitzp
===== 2009-03-09 21:48:49 -0400 =====
We took 1.224454 seconds total for this user's cache
===== 2009-03-09 22:10:25 -0400 =====
Error parsing XML: Line 2: Extra content at the end of the document
===== 2009-03-09 22:13:31 -0400 =====
Parsed 15 bookmarks (1 new, 0 updated, 14 skipped) and 3 tags (0 new, 3 skipped) for gfitzp
===== 2009-03-09 22:13:31 -0400 =====
We took 1.224397 seconds total for this user's cache
===== 2009-03-09 22:15:26 -0400 =====
Parsed 15 bookmarks (1 new, 0 updated, 14 skipped) and 3 tags (0 new, 3 skipped) for gfitzp
===== 2009-03-09 22:15:26 -0400 =====
We took 2.132930 seconds total for this user's cache
===== 2009-03-10 19:36:40 -0400 =====
Download failed when trying to fetch timestamp! (Error - no Internet connection https://gfitzp@api.del.icio.us/v1/posts/update)
Also, I looked at the XML I got back from https://gfitzp@api.del.icio.us/v1/posts/all in case that might help as well...
<?xml version="1.0" encoding="UTF-8"?>
<posts user="gfitzp" update="2009-06-04T01:27:38Z" tag="" total="1003">
1003 entries for links go here
<!-- fe01.api.del.ac4.yahoo.net uncompressed/chunked Mon Jun 8 22:54:18 PDT 2009 -->
Anyway, just thought I'd pass that along. Thanks again!
June 9, 2009
#8
@gfitzp: Hmm, there are two
@gfitzp: Hmm, there are two things in there that are not good, from a Delicious point of view. The first is whatever is causing the two character problem in Delicious' XML, and the second is the HTTP 999 error, which is not a valid code.
Are you seeing either of these things in your more recent problems? If so, please paste the log and I'll help you work through it with Delicious.
But both would seem to indicate server or other problems on their end.
June 18, 2009
#9
Same problem here
For what it's worth, I've got the same problem.
I had it last November, and couldn't get it fixed then, so would be interested to see a fix now (I might actually using delicious again!).
The output I get from the console is:
===== 2009-06-18 16:57:35 +0100 =====
Pukka/1.7.2 started
===== 2009-06-18 16:57:37 +0100 =====
Login failure while trying to fetch timestamp for ewan.carr!
Thanks!
June 19, 2009
#10
@Ewan: Hmm, this too is
@Ewan: Hmm, this too is concerning. I will be in touch soon with a dev build so we can get to the bottom of this issue.
June 19, 2009
#11
@ Justin
Thanks! I can get
@ Justin
Thanks! I can get round the problem by just leaving Pukka open all the time, so it's not a huge issue, but thanks for looking at it.
Ewan.
July 13, 2009
#13
Sorry, guys, about this
Sorry, guys, about this issue, but it's definitely a Delicious API issue, though Pukka could have better handling of it. What's happening is different parts of the API are succeeding and failing -- there's posting, checking for new posts, and downloading new posts, and this error is a problem with checking for new posts.
Being hard to replicate, it's hard to determine when, if at all, I should hide and show this error so that you know something's going on. The flipside is that you don't; then we get into issues where new bookmarks aren't downloaded and we have any number of places to determine where that is going awry.
Thanks for your patience.
July 22, 2009
#14
beta fix
Please give this beta build of Pukka a try if you are experiencing this problem:
http://codesorcery.net/downloads/Pukka_1.8.2b1.zip
This build, when told to "Ignore For Now", will ignore until you edit your app preferences, including across relaunches. Any problems with the API in this regard will still be logged to Pukka's Console, but will not warn the user.
Want to join the forums? Create an account or login.
Hey there. I hadn't checked this thread in awhile. I have the same behavior as gfitzp; and I wanted to report that the new version of Pukka I just downloaded and installed (1.8) has the same issue.
I will try sending the issue to delicious.