Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | S3: finish converting to aws library | 2014-08-09 | |
| | | | | | | | | | | | | | | Implemented the Retriever. Unfortunately, it is a fileRetriever and not a byteRetriever. It should be possible to convert this to a byteRetiever, but I got stuck: The conduit sink needs to process individual chunks, but a byteRetriever needs to pass a single L.ByteString to its callback for processing. I looked into using unsafeInerlaveIO to build up the bytestring lazily, but the sink is already operating under conduit's inversion of control, and does not run directly in IO anyway. On the plus side, no more memory leak.. | ||
* | remove dead code | 2014-08-09 | |
| | |||
* | bug triage; add new 'confirmed' tag | 2014-05-24 | |
| | |||
* | update; branch | 2012-10-07 | |
| | |||
* | root caused | 2011-04-21 | |
| | |||
* | update on S3 memory leaks | 2011-04-21 | |
| | | | | | | | The remaining leaks are in hS3. The leak with encryption was worked around by the use of the temp file. (And was probably originally caused by gpgCipherHandle sparking a thread which kept a reference to the start of the byte string.) | ||
* | fix S3 upload buffering problem | 2011-04-21 | |
| | | | | Provide file size to new version of hS3. | ||
* | update | 2011-04-21 | |
| | |||
* | heard from hS3 author | 2011-04-19 | |
| | |||
* | update on memory leak | 2011-04-19 | |
| | | | | | Finished applying to S3 the change that fixed the memory leak in bup, but it didn't seem to help S3.. with encryption it still grows to 2x file size. | ||
* | update | 2011-04-19 | |