potiuk commented on PR #55328: URL: https://github.com/apache/airflow/pull/55328#issuecomment-3263214074
cc: @jscheffl > I'd be interested in the gain. Do we actually have "endless" storage? Do we need to purge this at some time? How can cache be invalidated in case of "The problem is not DNS but cache corruption"? * installing uv + prek without cache: 1m 18s * installing uv + prek with cache: 12 s Certainly worth it. The stash / restore action works in the way that it uses artifacts from current and "main" builds if current is not available - and even the "current" build uses initially the "main" build as source of cache. We have automated retention of the cache (each artifact is kept for 2 days ( retention-days: '2'`) - so with our "velocity" that's more than enough :) We can invalidate the cache by bumping the v6 to v7 and so-on -> this how we can force cache invalidation. Also any change to teh .pre-commit-yaml will make the hash change and cache invalidated. In the future when we get monorepo we will hash all the `.pre-commit-config.ym`l files matching the `**/,pre-commit-config.yml` - so hash wil be calculated from all the .yml files. :) Very good question BTW. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
