Force cache refresh before expiration?

[kumy]

@dimo414 is there a way to force a decorated function to run again it's original function, return the fresh result and refresh the cache before it has expired? Or is there a way to mark the cached version as expired so the original function will run again?

[dimo414]

Can you share more details about what you're trying to do?

You can use an environment variable to invalidate the cache (PWD is particularly useful so commands run in different directories are cached separately) or bc::warm::FUNCTION_NAME to asynchronously warm the cache. You can also customize the BC_CACHE_DIR to invalidate old cached data, though that's a bit of a big hammer. There isn't a way to force a single command to be re-cached at present (bkt provides a --force flag that does this) but I can imagine adding a bc::force::FUNCTION_NAME function if that would be useful.

[dimo414]

Yeah warm is intentionally async, the intent is to be able to initiate a refresh before the data is needed. If you need to block until completion then we'll want to add a force operation. It might be possible to get wait to work, but I haven't tried it and it's not very user-friendly in any case.

[dimo414]

I've gone ahead and added bc::force::FUNCTION_NAME and re-written that section of the README. Feel free to send a PR with further edits to the README if you think it could still be clearer.

[kumy]

Will try that! Many thanks!! 🥳

[kumy]

The README looks fine, thanks.

[kumy]

Just to confirm that new bc::force::FUNCTION_NAME works like a charm! Thanks