Repository navigation
The worker updates itself, and CI on GitHub-hosted runners in two stages - #44
Merged
Merged
Conversation
…inds open The service worker waited for a prompt the interface never showed, so after the server was updated the old worker kept serving its cached shell until every page of the app had been closed: 1.1.0 looked like the version before it. The new worker now takes over as soon as it is installed, claims the open pages and, when it is an update rather than the first install, reloads them so they run the new shell. The offline outbox lives in IndexedDB and survives the reload. Signed-off-by: Jose David <josedalmena@gmail.com>
The repository is public, so GitHub's runners cost nothing and many run in parallel; a run that took an hour on the two-core self-hosted runner takes about ten minutes. The cheap checks go first (commit messages, secrets and dependency audits, the frontend's lint, types, tests and build) and the three expensive jobs run side by side only when they pass, so a failure in the first stage stops there. The browser used by the end-to-end job is cached between runs. The self-hosted runner stays registered and the workflow keeps its tolerances, so it can take the work again by changing runs-on. Signed-off-by: Jose David <josedalmena@gmail.com>
Signed-off-by: Jose David <josedalmena@gmail.com>
The verification job stamps the real clock, while the test simulated days from a fixed date in early October; once the calendar passed that date, "eight days later" was less than a week after the real stamp and the test failed. The simulated days now start tomorrow. Signed-off-by: Jose David <josedalmena@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two fixes for 1.1.1
Merged locally as a fast-forward once the checks pass.