404 creating zero byte files

blob storage issue
Azurite 3.3.0-preview (cloned from here github)
Node.js v10.15.3

We're using the javascript storage sdk to extract gzipped tarballs into blob storage. This works like a champ until one of the files in the tarball is a zero byte file. What that happens, azurite 404s on the PUT request.

127.0.0.1 - - [13/Dec/2019:19:05:03 +0000] "PUT /devstoreaccount1/extracted/NONzerobyte.log?sv=2019-02-02&st=2019-12-13T19%3A00%3A03Z&se=2019-12-13T19%3A30%3A03Z&sr=b&sp=wd&sig=xxxxx&comp=blocklist HTTP/1.1" 201 -

127.0.0.1 - - [13/Dec/2019:19:05:03 +0000] "PUT /devstoreaccount1/extracted/NONzerobyte2.log?sv=2019-02-02&st=2019-12-13T19%3A00%3A03Z&se=2019-12-13T19%3A30%3A03Z&sr=b&sp=wd&sig=xxxxx&comp=blocklist HTTP/1.1" 201 -

127.0.0.1 - - [13/Dec/2019:19:05:03 +0000] "PUT /devstoreaccount1/extracted/ZERObyte.log?sv=2019-02-02&st=2019-12-13T19%3A00%3A03Z&se=2019-12-13T19%3A30%3A03Z&sr=b&sp=wd&sig=xxxxx&comp=blocklist HTTP/1.1" 404 -

If i remove all the zero byte files from my tarball, this doesn't happen. As a workaround for what I'm doing that doesn't work though as I need an accurate directory contents in my result. This only occurs with the emulator. The same code pointed at Azure doesn't have this issue (but we'd rather not pay the storage fees while testing).