You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(publish): Check remote git registry more than once post-publish
With `publish-timeout` on remote git registries, we were checking once
and never checking again. There were 3 layers of guards preventing the
cache from being updating
- `needs_update`, handled via `invalidate_cache`
- `config.updated_sources()`,. handled by removing from the HashSet
- `updated`, inaccessible
This change collapses `updated` into `config.updated_sources()`,
allowing the cache to be updated
Tested by publishing `epage-publish-test`. After about 7 registry
updates, it succeded. Before, it just hit the timeout of 60s. No tests
are added as we don't have the plumbing setup to be able to control when
the test remote git registry publishes. All of our tests focus on the
remote http registry.
Fixes#11253
0 commit comments