Temporary Files remain in the /tmp folder after upload

[adimasuhid]

Sample files below in my /tmp folder taken after upload:

[mikermcneil]

Also seeing this issue

@nathanoehlman would you be ok with a pull request to cleanup? Can make it disable-able with a flag in options (and off by default, if you'd prefer, to avoid compatibility issues and to minimize the associated npm version bump)

[mikermcneil]

@adimasuhid this is resolved by #30 - can you verify? Thanks!

[aarsilv]

I am still seeing this with 0.1.6

[jacobdr]

Question about this: these changes looked like they got pushed in #29, but the package hasn't been tagged since well before that pull request was integrated. What is the best suggested way to roll the latest version from Git into our projects?

I think that it is possible to include straight Git references in package.json, but am I wrong in assuming that an npm install will only pull down up to commit 91006ee?

Running npm view knox-mpu seems to indicate as much...

[sgress454]

mikermcneil and I took over maintenance of this repo awhile back after forking it into knox-mpu-alt, but I'm having trouble digging up the credentials to publish it to npm. I just published v0.2.0 of knox-mpu-alt, so you can use that for now while we get this worked out. Sorry for the confusion.

[jacobdr]

Thanks for clearing this up. And again, thanks for the awesome work on the project. 

In case others find this thread through Google, my immediate workaround was to swap out the npm tag for the "git+https" syntax in my package.json. Just make sure to delete the module in the node_modules directory and run npm update or npm install to pull in the fresh bits.

On Thu, Jun 11, 2015 at 12:36 PM, sgress454 [email protected]
wrote:

mikermcneil and I took over maintenance of this repo awhile back after forking it into knox-mpu-alt, but I'm having trouble digging up the credentials to publish it to npm. I just published v0.2.0 of knox-mpu-alt, so you can use that for now while we get this worked out. Sorry for the confusion.

Reply to this email directly or view it on GitHub:
#23 (comment)

[jacobdr]

Also I think that we can close this issue as its been resolved. 

A cleaned bug makes for a happy bug catcher.

On Thu, Jun 11, 2015 at 12:36 PM, sgress454 [email protected]
wrote:

mikermcneil and I took over maintenance of this repo awhile back after forking it into knox-mpu-alt, but I'm having trouble digging up the credentials to publish it to npm. I just published v0.2.0 of knox-mpu-alt, so you can use that for now while we get this worked out. Sorry for the confusion.

Reply to this email directly or view it on GitHub:
#23 (comment)