Arvados

reviewing 229773c2aa3ddc798ae4eb1eff62f8f77db85391

there is a easy way to mess this around.

having a stdin file on the working directory and doing

arv-put stdin -

the resulting collection will have only the standard input.

What do we want to do with this edge case:

- concatenate both
 - do a collision detection (i.e. create stdin2 for the second input)
 - ignore it

also sdk/cli/test/test_arv-put.rb should be updated ... writing a simple "hello" from stdin and then checking the md5 of the resulting stdin file

Nico Cesar wrote:

reviewing 229773c2aa3ddc798ae4eb1eff62f8f77db85391

there is a easy way to mess this around.

having a stdin file on the working directory and doing

arv-put stdin -

the resulting collection will have only the standard input.

What do we want to do with this edge case:

- concatenate both
- do a collision detection (i.e. create stdin2 for the second input)
- ignore it

Changed to disallow additional files on the command line when getting data from stdin.

also sdk/cli/test/test_arv-put.rb should be updated ... writing a simple "hello" from stdin and then checking the md5 of the resulting stdin file

Those tests are skipped (unfortunately) and I don't think fixing them is part of the scope of this ticket.

Peter Amstutz wrote:

Nico Cesar wrote:

reviewing 229773c2aa3ddc798ae4eb1eff62f8f77db85391

there is a easy way to mess this around.

having a stdin file on the working directory and doing

arv-put stdin -

the resulting collection will have only the standard input.

What do we want to do with this edge case:

- concatenate both
- do a collision detection (i.e. create stdin2 for the second input)
- ignore it

Changed to disallow additional files on the command line when getting data from stdin.

From office conversation: will back out this change. If a user uploads a file called "stdin" while also piping from stdin, the files will be concatenated.