x/pkgsite: package documentation should immediately reflect UI changes #40807
Currently, we need to reprocess the database on any UI changes (e.g. changes to the HTML templates), which can take several hours. Users who request packages that were not yet reprocessed will see the old HTML version, which when coupled with potentially new CSS changes, can have unexpected results. See #40078
We should allow the frontend to prioritize the reprocessing of any package that a user requests, so that users will always see the latest UI changes when viewing documentation.
The text was updated successfully, but these errors were encountered:
Currently, the worker only updates the module_version_states table to mark that modules need to be reprocessed. Update the module status in the version_map table too. For golang/go#40807 Change-Id: I9a1ecf611a71f1d3dda3d7d7b20d17012a995ca3 Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/248677 Run-TryBot: Shaquille Que <email@example.com> TryBot-Result: kokoro <firstname.lastname@example.org> Reviewed-by: Julie Qiu <email@example.com>
…ates Populate the new modules.status column whenever we insert or update module_version_states.status, in the same transaction. After this code is deployed, we should manually update NULL modules.status values to match module_version_states.status. This CL implements part of https://golang.org/cl/c/pkgsite/+/249447. For golang/go#40807 Change-Id: I8623fd71207b6578ff03de09ee12d292b36465b5 Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/253080 Reviewed-by: Julie Qiu <firstname.lastname@example.org>
If the frontend-render-doc experiment is set, render documentation on the frontend instead of using the HTML in the database. Wrote an integration test that tests the entire round trip from worker fetch to frontend render. For golang/go#40807 Change-Id: Id0458b31592a431a440f86262f5fd0a3cc107f25 Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/258877 Trust: Jonathan Amsterdam <email@example.com> Run-TryBot: Jonathan Amsterdam <firstname.lastname@example.org> Reviewed-by: Julie Qiu <email@example.com>