Toby Burress
Toby Burress
I don't believe B2 has a way to automatically cancel large files. The only permanent failure for the writer should be a cancelled context. Any other failure ought to be...
The B2 integration checklist specifies that some errors (including network errors) should be handled with exponentially backed-off retries. So in that sense blazer will retry forever even given network failures...
Yeah that's probably a good idea.
So I've added a thing for this: https://godoc.org/github.com/kurin/blazer/b2#WithCancelOnError I'm not super happy about the interface though. The idea with ctxf is that you probably want a new context if the...
Automatically calling `b2_cancel_large_file` is fraught if, for example, the user doesn't want the large file cancelled, which is a reasonable thing to expect. You should always call `Close` irrespective of...
I'd need to think about whether we can infer from a cancelled context whether the user does or does not want to clean up the underlying file. On the one...
It would be easy enough to expose an object's ID, but honestly running two lists and subtracting IDs to find hidden objects isn't great. Another option would be to expose...
B2 doesn't support chunked transfers, so this just got a lot less exciting.
I mistyped, I meant it's not recommended by Backblaze. I don't know why, and I still haven't thought of anything. It's been a while, but I think the reason I...
> it can just make two passes over the input if the input supports seeking btw this is no longer true, it only makes one pass in this instance.