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
x/pkgsite: implement cache invalidation #44217
Comments
Change https://golang.org/cl/291250 mentions this issue: |
Change https://golang.org/cl/291249 mentions this issue: |
Change https://golang.org/cl/291270 mentions this issue: |
Change https://golang.org/cl/291369 mentions this issue: |
Put the Redis-based page cache logic into its own package. Mostly for the non-trivial DeletePrefix method. For golang/go#44217 Change-Id: I7248f60b5d71402a38ebd4c96143a70e21ae3c63 Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/291249 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> Reviewed-by: Julie Qiu <julie@golang.org>
Replace direct calls on the redis cache client with calls to the new internal/cache package. For golang/go#44217 Change-Id: I0d16f810c8455a6a23f9275f1c5e554e37ba86bc Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/291250 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> Reviewed-by: Julie Qiu <julie@golang.org>
InsertModule reports whether it just inserted the latest version of a module. We'll use this information later to determine whether to invalidate the cache. Also, rewrite tests to use postgres.MustInsertModule. For golang/go#44217 Change-Id: I8bed8aa8e86a347a4add85c2b16c549b7ad740f0 Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/291270 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> Reviewed-by: Julie Qiu <julie@golang.org>
The worker should invalidate the cache for a module when it processes the latest version.
This will allow us to get rid of HTML replacements (#44210) without worrying about stale data.
The text was updated successfully, but these errors were encountered: