You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2019/01/03 10:35:00 UTC

[jira] [Closed] (WAGON-544) Work around JSch issue #122

     [ https://issues.apache.org/jira/browse/WAGON-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed WAGON-544.
--------------------------------
    Resolution: Fixed

Fixed with [69c931b98c1db02e48e0cc7e95771fba2f99be44|https://gitbox.apache.org/repos/asf?p=maven-scm.git;a=commit;h=69c931b98c1db02e48e0cc7e95771fba2f99be44].

> Work around JSch issue #122
> ---------------------------
>
>                 Key: WAGON-544
>                 URL: https://issues.apache.org/jira/browse/WAGON-544
>             Project: Maven Wagon
>          Issue Type: Task
>          Components: wagon-ssh
>    Affects Versions: 3.3.0
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 3.3.1
>
>
> JSch's {{Channels$MyPipedInputStream#read()}} does not return -1 when EOF is reached. This causes the reading thread to block and never to resume. This happens only when more bytes are requested to be read than available from the stream. It does not read at most bytes. So one has to know the last less-than-the-buffer-length chunk and recalculate remaining bytes. This worked conincidentially because it worked that way.
> This is brittle, as long as the upstream bug is not fixed we will restore the previous {{AbstractWagon#transfer()}} implementation in {{AbstractJschWagon}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)