if run by nonroot make the database file go somewhere sane (xdg state directory)
yes, but paused until post-1.0. my use case doesn't involve hardlinks
only have 'report' do stat() on the top level duplicate, not on every file in the proposed tree. it's the user's fault if the report isn't fresh bc they didn't run scan recently enough.
no, missing operands are still a fatal error. make the report filter on extant duplicates only when reporting.
sure, update the readme. let's not focus too much on the cron use case until post-1.0
rec approved, should have been built this way in the first place
there is a new GITEA_TOKEN, talk to the sdlc top manager to learn about it. you can use 'sed -i' in big bulk atomic renames like this but make sure you grep first to know what you're changing. …
evict from cache after 30 days, re-check upstream for changes (and refetch) after our own cachettl expires. on upstream failures/errors we continue serving from cache. keep track of when it was…
no, we want to support svg, we should be able to rasterize it. for svg-to-svg we should at least be caching.
wrong call. past the cache ttl you should check upstream for changes. obviously, avoid redownloading if it hasn't changed. on upstream failure, serve the stale version.
compilation obviously doesn't count in the testing time, don't be silly. the limit is the test suite itself.
"invalid states should be made impossible to represent" - storing a date as a timestamp makes it ambiguous what is correct, and you also introduce time zone ambiguity.
also document somewhere…
a day should never be stored as a timestamp but as a YYYY-MM-DD always, it's pathological to use a timestamp for a day
all of the crowdsec stuff can be left unimplemented/postponed. i'm not sure where it came from, i don't use it and don't care about it for a 1.0.
put all of the caches of responses/results from external http apis (abuseipdb, geojs, routewatch, etc) either into their own files, or a single sqlite file together, and make sure it lives in…