Egon Elbre c2bdd4effa cmd/uplink/ulfs: disallow writes after first failure ... It was possible for the a previous write / part to fail or be aborted and the next part write still happened. This causes a data ordering corruption. The whole write to parallel stdout fails, so there shouldn't be confusion with regards to the output acceptability. However, it would be clearer, if we avoided writing out-of-order data... mainly to be clear that we didn't corrupt the data, just that it's incomplete. Change-Id: I97b0d14404f29e8615e7d29b10cbd61ccb861e40		2022-04-25 18:16:46 +03:00
..
filesystem.go	cmd/uplink: integrate server-side copy with uplink cp command	2022-03-31 09:25:29 +00:00
handle_file.go	cmd/uplinkng: become cmd/uplink	2022-02-09 17:02:21 +00:00
handle_generic.go	cmd/uplinkng: become cmd/uplink	2022-02-09 17:02:21 +00:00
handle_std_test.go	cmd/uplink/ulfs: disallow writes after first failure	2022-04-25 18:16:46 +03:00
handle_std.go	cmd/uplink/ulfs: disallow writes after first failure	2022-04-25 18:16:46 +03:00
handle_uplink.go	cmd/uplinkng: become cmd/uplink	2022-02-09 17:02:21 +00:00
helpers_iterator.go	cmd/uplinkng: become cmd/uplink	2022-02-09 17:02:21 +00:00
local.go	cmd/uplink: integrate server-side copy with uplink cp command	2022-03-31 09:25:29 +00:00
mixed.go	cmd/uplink: integrate server-side copy with uplink cp command	2022-03-31 09:25:29 +00:00
remote.go	cmd/uplink: integrate server-side copy with uplink cp command	2022-03-31 09:25:29 +00:00