| Age | Commit message (Collapse) | Author |
|---|
|
That was weird. It seems to be working now.
|
|
|
|
Still to go: bootstrapping reading the initial header, saving the
header, growing streams as we write?
|
|
|
|
If so, this will fix the issue where streams randomly truncate when
accessed by multiple threads.
|
|
|
|
There's an issue somewhere sometimes and streams are being truncated. My
guess is a multi-threaded issue.
|
|
It returns "file:<requested path>" which could be made better
eventually, but it's nice, I like the format, it'll be good for memory
buffers to be able to report in a similar way.
|
|
We were only reading 1k of data in before, but if a header was more than
1k then we just would give up. Now we read as much as we can that has
loaded into the buffer and if we run out we can try again, but if it's
just a very long header we'll deal with it properly still.
|
