search

gnunicorn / clippy-service

Linting your rust project with clippy as a service
GNU Affero General Public License v3.0
36 stars 9 forks source link

How to handle stale cache #31

Open gnunicorn opened 8 years ago

gnunicorn commented 8 years ago

We currently have to run clippy against rust nightly to perform the tasks and as clippy needs unstable and constantly changing features, we need to rebuild it often (see #29 ). At the moment, however, we do not flush the cache every time we rebuild, meaning that running clippy against your source code locally could give you a different output/error reporting than our service reports as that is loaded from cache. We need a way to handle this. I am open for suggestions.

gnunicorn commented 8 years ago

We could just flush the cache every time we deploy, though that might lead to an ugly CPU spike until we have the worker queue in place ( #15 )