[Cyberduck-trac] [Cyberduck] #9488: cannot upload any file, get "transfer incomplete"

Cyberduck trac at trac.cyberduck.io
Tue Apr 26 08:11:40 UTC 2016


#9488: cannot upload any file, get "transfer incomplete"
--------------------------------+----------------------
 Reporter:  rblaa               |         Owner:
     Type:  defect              |        Status:  new
 Priority:  normal              |     Milestone:
Component:  core                |       Version:  4.9.3
 Severity:  normal              |    Resolution:
 Keywords:  transfer incmplete  |  Architecture:  Intel
 Platform:  Mac OS X 10.11      |
--------------------------------+----------------------
Description changed by dkocher:

Old description:

> this happens with my mac, as long as i try have checked the box to change
> the permissions of the uploaded files, either to that of the local file
> and directory, or to something explicit.
>
> if I uncheck the permissions preference, the upload works, but I have to
> use the AWS console itself to change permissions to make my upload
> public. this means that my user account does in fact have the rights to
> change permissions.
>
> unfortunately the logs do not show anything useful, with the 5.0 snapshot
> I see only:
>
> 2016-04-25 17:10:22.901 Cyberduck[92702]: [main] WARN
> ch.cyberduck.core.threading.ThreadPoolFactory - No matching constructor
> for parameter class
> ch.cyberduck.core.threading.LoggingUncaughtExceptionHandler
>
> it looks like the true exception is being prevented from being logged due
> to this

New description:

 this happens with my mac, as long as i try have checked the box to change
 the permissions of the uploaded files, either to that of the local file
 and directory, or to something explicit.

 if I uncheck the permissions preference, the upload works, but I have to
 use the AWS console itself to change permissions to make my upload public.
 this means that my user account does in fact have the rights to change
 permissions.

 unfortunately the logs do not show anything useful, with the 5.0 snapshot
 I see only:


 {{{
 2016-04-25 17:10:22.901 Cyberduck[92702]: [main] WARN
 ch.cyberduck.core.threading.ThreadPoolFactory - No matching constructor
 for parameter class
 ch.cyberduck.core.threading.LoggingUncaughtExceptionHandler

 }}}

 it looks like the true exception is being prevented from being logged due
 to this

--

-- 
Ticket URL: <https://trac.cyberduck.io/ticket/9488#comment:1>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows


More information about the Cyberduck-trac mailing list