Recover from Flickr publishing errors
Submitted by an unknown user
Link to original bug (#719251)
Description
---- Reported by shotwell-maint@gnome.bugs 2013-05-20 15:11:00 -0700 ----
Original Redmine bug id: 6972
Original URL: http://redmine.yorba.org/issues/6972
Searchable id: yorba-bug-6972
Original author: Dra žen Lučanin
Original description:
The Flickr publisher doesn't do error recovery for network I/O errors. The others have been updated to be more robust in this area. The Flickr publisher should as well.
Original description:
After trying to publish 37 photos to Flickr the upload freezes at 3/37 with a message:
Publishing to Flickr not possible due to an error*:
Failure communicating with http://api.flickr.com/services/upload (error code 7)
I don't know if it's maybe an API change related to their whole redesign, because I successfully uploaded a different batch of photos a couple of days ago.
Using Shotwell 0.14.1 in Ubuntu 13.04.
__
*translated from Croatian
---- Additional Comments From shotwell-maint@gnome.bugs 2013-08-18 01:10:00 -0700 ----
History
Comment 1
Updated by Jim Nelson 6 months ago
- Category set to web-sharing
- Status changed from Open to Need Information
Have you tried logging out in Shotwell and logging back in?
Comment 2
Updated by Lucas Beeler 6 months ago
Error 7 is a libsoup error code described here:
https://developer.gnome.org/libsoup/stable/libsoup-2.4-soup-status.html
It's documented as one of the values of the SoupKnownStatusCode enum type. Its symbolic name is SOUP_STATUS_IO_ERROR, which is just what it sounds like: libsoup couldn't write to the TCP socket. This happens whenever your internet connection flakes out during an upload. The flake-out can event be temporary, because, alas, unlike the rewritten, Graph API-based Facebook Connector, the Flickr Connector (now the oldest Shotwell Connect client) has no error- recovery mechanism. If you'd like to open a ticket for adding error recovery to the Flickr connector, please do so.
Comment 3
Updated by Jim Nelson 6 months ago
- Subject changed from Error publishing to Flickr to Recover from Flickr publishing errors
- Description updated (diff)
- Status changed from Need Information to Open
Let's make this ticket the one for error recovery. I've updated the title and description.
Comment 4
Updated by Dražen Lučanin 6 months ago
Jim Nelson wrote:
Have you tried logging out in Shotwell and logging back in?
I tried it now and it actually fixed my problem, you were right. Thanks for the advice!
I am using Ubuntu, so I deleted and re-added Flickr in the OS's Online Accounts settings. I tried uploading once again and it worked for all 37 photos. I could see a difference in the upload menu - instead of my name there were only empty parentheses and there was my Flickr nickname, which I don't remember seeing before, so obviously something changed in the way these online accounts are stored. I guess it's because I upgraded from 12.10 to 13.04 and my conf files kept some old format or something - I noticed quite a few of these hick-ups in Ubuntu.
Fine by me if you re-purpose this ticket into Flickr publishing error recovery. People will probably be using that more than before, anyway, now that Flicker offers 1 TB of storage for free, so it would be great to see some new features on this front :)
Comment 5
Updated by Stuart Cuthbertson 3 months ago
- File flickr_publishing_error.png added
I think the following is relevant as an addition to this ticket, but please let me know if I should raise it separately/comment somewhere else.
I have occasionally (including today) had different errors when publishing to Flickr from Shotwell. See screenshot attached. In this particular case, I had set 155 5-7MB photos to upload to Flickr overnight. The error occurred after the 54th so it got a long way in.
Given this is a HTTP 504 I would guess this relates to the quantity of photos (it would probably have been going at least a couple of hours to get to 54th photo). It may well be more the design of the API than how Shotwell talks to it? I do feel Shotwell should be able to cope with this though, perhaps by closing and reopening the connection every X photos or something?
Incidentally, I'm on Ubuntu 13.04 with Shotwell 0.14.1.
--- Bug imported by chaz@yorba.org 2013-11-25 22:11 UTC ---
This bug was previously known as bug 6972 at http://redmine.yorba.org/show_bug.cgi?id=6972 Imported an attachment (id=262771)
Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one. Resolution set on an open status. Dropping resolution