Skip to content

Serve a bound fixture with its match's status and time (1.13.77) - #12

Merged
bensynapse merged 1 commit into
mainfrom
fix/fixture-mirror
Oct 29, 2026
Merged

bensynapse merged 1 commit into
mainfrom
fix/fixture-mirror

Conversation

@bensynapse

Copy link
Copy Markdown
Member

A fixture bound to a match is now served with the match's status, in the fixture vocabulary, and the match's start time. The match row moves within minutes of a schedule change. The fixture row followed the 6-hourly refresher, so the two endpoints could disagree on one match for hours. A customer found a Vienna match live at 09:00Z on one endpoint and upcoming at 12:30Z on the other.

A bare digit in the schedule's status field is live only when the schedule's own in-play flag says so. The day-ahead listing carries a 1 on matches that have not started.

Version 1.13.77. Generated pages rebuilt. Ships with tennisv1 main (same day).

A fixture with a match_id now carries the match's status, in the fixture
vocabulary, and the match's start time. The two endpoints disagreed on the
same match for up to six hours. A vendor-stated cancelled or postponed on
the fixture is kept.

A bare digit in the schedule's status field is live only when the schedule's
own in-play flag says so. Generated pages rebuilt with scripts/build_reference.py.
@bensynapse
bensynapse merged commit 6890c55 into main Oct 29, 2026
2 checks passed
@bensynapse
bensynapse deleted the fix/fixture-mirror branch October 29, 2026 02:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant