Skip to content

fix: declare live_data:true to keep clock ticking under new platform cache default#7

Merged
jeffredodd merged 2 commits into
mainfrom
fix/declare-live-data
Jun 7, 2026
Merged

fix: declare live_data:true to keep clock ticking under new platform cache default#7
jeffredodd merged 2 commits into
mainfrom
fix/declare-live-data

Conversation

@jeffredodd

Copy link
Copy Markdown
Member

Summary

FiestaBoard's plugin runtime is changing PluginBase.get_data() to default to a 300s cache when a plugin manifest declares no refresh_seconds. That default would freeze this clock between ticks.

This PR opts out by declaring the new top-level manifest flag:

"live_data": true

When set, the platform calls fetch_data() directly on every poll, skipping the cache. That's the right semantic here because fetch_data() recomputes datetime.now(tz) each call — every poll must produce a fresh time.

Changes

  • Add "live_data": true to manifest.json (placed after description)
  • Bump manifest version 1.1.0 -> 1.1.1
  • No code changes

Test plan

  • Manifest JSON is valid
  • Existing plugin tests pass (44/44)
  • Verify under the new platform default that the clock still updates on every poll
  • Verify older platforms (which ignore the unknown live_data field) continue to work unchanged

🤖 Generated with Claude Code

Jeffrey Johnson and others added 2 commits June 6, 2026 18:56
…the clock

FiestaBoard is changing PluginBase.get_data() to default to a 300s
cache when manifest declares no refresh_seconds. Visual-clock needs
fresh datetime.now() on every poll, so explicitly opt out via the
new live_data:true manifest flag.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@jeffredodd jeffredodd merged commit f0b23e5 into main Jun 7, 2026
1 check passed
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