Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linter creates many empty temp directories #454

Closed
rstelzleni opened this issue Mar 3, 2015 · 6 comments
Closed

Linter creates many empty temp directories #454

rstelzleni opened this issue Mar 3, 2015 · 6 comments

Comments

@rstelzleni
Copy link

It looks like each time the Linter runs pylint on my Mac it leaves behind a directory like this one:

AtomLinter11522-3312-u5r7xesource.python

The directory is in the normal temp dir. After working a few hours I'll have a few thousand of these empty directories left behind. It looks like these are all deleted when I shut down Atom. This seems unlikely to be a big problem, but I thought I'd point it out in case it becomes an issue with long running Atom sessions.

The linter is using the temp package with tracking turned on, maybe it could call temp.cleanup periodically?

I'm using Linter version 0.12.0 and linter-pylint version 0.2.1.

@posita
Copy link

posita commented May 11, 2015

As mentioned in #522, waiting until shutdown to remove them doesn't help if Atom crashes. They should probably be cleaned up as soon as they are no longer needed?

@fabian-marquardt
Copy link

I can confirm this. At work I have the editor open for several days and many empty AtomLinter directories pile up under /tmp after some time.

@posita
Copy link

posita commented Jul 16, 2015

@fabian-rump, are you still seeing this? @AsaAyers resolved this as part of batch close associated with the linter rewrite. It looks fixed to me, but can you confirm on your end?

@AsaAyers
Copy link
Contributor

This was part of the batch close, but it did get addressed in #603.

@posita
Copy link

posita commented Jul 16, 2015

@AsaAyers, awsome! Thank you! 👍

@fabian-marquardt
Copy link

The issue is gone. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants