Ka-Hing Cheung
Ka-Hing Cheung
currently s3proxy returns application/unknown vs aws s3 returns binary/octet-stream
S3Proxy returns 404 when I try to HEAD a key that's not valid utf8, whereas aws returns 400. For ListObject, both return 403. AWS S3: ``` 2017/03/14 00:06:58 DEBUG: Request...
and vice versa. Possibly by just using a pipe?
**Describe the bug** https://github.com/DoctorD1501/JAVMovieScraper/blob/3b2b4c687f4f0f2a82353d82b0b489265176d8db/src/main/java/moviescraper/doctord/model/ImageCache.java#L15 https://news.ycombinator.com/item?id=21765788
### Description sometimes I see: `-: return with unexpected locks held (locks: &({param:f}.mu) exclusively)` notice the usual file name and line number is replaced by `-`. ### Steps to reproduce...