feat: poll datasette before running reporting task - #88
Draft
tombrooks248 wants to merge 3 commits into
Draft
Conversation
tombrooks248
force-pushed
the
feat/poll-datasette-before-reporting-task
branch
from
June 30, 2026 13:30
4c6a4f0 to
ec41063
Compare
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.
What type of PR is this? (check all applicable)
Description
Replace the fixed 10-minute
wait-before-reportingtask inbuild-digital-land-builder(prod only) with a real datasette-availability check.More detail needs to be added on how it now actually works.
Related Tickets & Documents
QA Instructions, Screenshots, Recordings
This needs to be pushed to staging, with some temporary code chagnes so that it acutally runs in staging and then checked that it works as intended, before it can be implemented in prod.
Added/updated tests?
We encourage you to keep the code coverage percentage at 80% and above. Please refer to the Digital Land Testing Guidance for more information.
[optional] Are there any post deployment tasks we need to perform?
[optional] Are there any dependencies on other PRs or Work?