Error: The request was aborted: The request was canceled.

Sep 25, 2014 at 1:37 PM
Edited Sep 25, 2014 at 1:37 PM
FlickrSync: 0.9.1.0

Hello, since roughly 2 months, I am unable to upload new pictures using flickrsync.
FYI, I have also tried on another computer than mine

Error
Error uploading picture to flickr: F:\Gallery\2014\June\28-06-2014 Hannah and Nick's Wedding, Lydiard, England\DSC06365.JPG
Error: The request was aborted: The request was canceled.
OK

it happens at the end of the first image( but does not upload anything on flickr)


Any clue ?

Thank you
Oct 20, 2014 at 7:49 PM
No clue, but I'm afraid I experiment the same kind of problem, on uploading or more frequently on replacing...
Dec 26, 2014 at 12:31 PM
Same problem here, says the same (only with german translation). Please help!
Coordinator
Dec 30, 2014 at 10:14 AM
Hi. Is this a specially large picture?
Some users have reported problems with very large pictures on slow connections. Not sure if this is the only scenario but it may be that the flickr API breaks the upload if it takes too long.
Coordinator
Dec 30, 2014 at 10:33 AM
I've investigated this a bit more and there is in fact a timeout which seems to be of 100 seconds per picture. This may be a strong limitation in scenarios of very large pictures. I will release a patch of FlickrSync that increases this timeout, so that it should hopefully solve these kind of problems.
Coordinator
Dec 30, 2014 at 6:30 PM
A new release has been created (0.9.2) that should solve the timeout issues
Mar 25, 2015 at 2:37 PM
Hi,

Sorry, I only checked now.
Tried to upload my album from my holidays, and the problem is still present. My connexion is not too bad and never timeout when uploading. This is ping -t www.google.fr when uploading

Reply from 64.233.177.94: bytes=32 time=145ms TTL=41
Reply from 64.233.177.94: bytes=32 time=130ms TTL=41
Reply from 64.233.177.94: bytes=32 time=135ms TTL=41
Reply from 64.233.177.94: bytes=32 time=1026ms TTL=41
Reply from 64.233.177.94: bytes=32 time=142ms TTL=41
Reply from 64.233.177.94: bytes=32 time=141ms TTL=41
Reply from 64.233.177.94: bytes=32 time=130ms TTL=41
Reply from 64.233.177.94: bytes=32 time=1024ms TTL=41
Reply from 64.233.177.94: bytes=32 time=136ms TTL=41
Reply from 64.233.177.94: bytes=32 time=135ms TTL=41
Reply from 64.233.177.94: bytes=32 time=139ms TTL=41
Reply from 64.233.177.94: bytes=32 time=1045ms TTL=41
Reply from 64.233.177.94: bytes=32 time=143ms TTL=41
Reply from 64.233.177.94: bytes=32 time=135ms TTL=41
Reply from 64.233.177.94: bytes=32 time=138ms TTL=41
Reply from 64.233.177.94: bytes=32 time=1023ms TTL=41

Am i the only one having reporting this problem ?

Thanks

2014-12-30 20:30 GMT+01:00 geada <[email removed]>:

From: geada

A new release has been created (0.9.2) that should solve the timeout issues

Read the full discussion online.

To add a post to this discussion, reply to this email ([email removed])

To start a new discussion for this project, email [email removed]

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com




--
Florent Valdelievre
+(33) 6 52 50 96 87
[email removed]
Find me on Linkedin
Mar 25, 2015 at 5:46 PM
The new release solved my problem. In your Ping-statistics i see twice more than one second! Maybe that's the problem?

My stats:

Ping wird ausgeführt für www.google.at [173.194.66.94] mit 32 Bytes Daten:
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=48ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=50ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=52ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=48ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=50ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=51ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=48ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=48ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=50ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=51ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=50ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47

Ping-Statistik für 173.194.66.94:
Pakete: Gesendet = 28, Empfangen = 28, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 48ms, Maximum = 52ms, Mittelwert = 49ms
Mar 25, 2015 at 7:57 PM
Yes, 1 sec lag is definitely not ideal. It does not seem to come from my computer but my line :(
However, do you have the possibility to extend the connexion timeout or maybe implement a retry failover ? If one photo fails, the sync stops completely.

thanks !

2015-03-25 18:46 GMT+01:00 dstockinger <[email removed]>:

From: dstockinger

The new release solved my problem. In your Ping-statistics i see twice more than one second! Maybe that's the problem?

My stats:

Ping wird ausgeführt für www.google.at [173.194.66.94] mit 32 Bytes Daten:
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=48ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=50ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=52ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=48ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=50ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=51ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=48ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=48ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=50ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=51ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=50ms TTL=47
Antwort von 173.194.66.94: Bytes=32 Zeit=49ms TTL=47

Ping-Statistik für 173.194.66.94:
Pakete: Gesendet = 28, Empfangen = 28, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 48ms, Maximum = 52ms, Mittelwert = 49ms

Read the full discussion online.

To add a post to this discussion, reply to this email ([email removed])

To start a new discussion for this project, email [email removed]

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com




--
Florent Valdelievre
+(33) 6 52 50 96 87
[email removed]
Find me on Linkedin