• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

FlexMeasures / flexmeasures / 35710232804
86%

Build:
DEFAULT BRANCH: main
Ran 22 Sep 2026 09:35AM UTC
Jobs 1
Files 186
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

22 Sep 2026 09:24AM UTC coverage: 85.902% (+0.1%) from 85.801%
35710232804

push

github

web-flow
Feat: automations page improvements (#2554)

* ui/automations: say how far off the next run is, and put the clock time on hover

Context:
- Review of #2294: the next run time can be displayed in more human form,
  like "in 6 minutes", "in 4 hours" or "tomorrow", as other pages already do.
  The precise date and time is still needed, but belongs on hover.

Change:
- Render the next run with getHumanFriendlyDeltaOrTimeStr, the helper the Created At
  column and the status and user pages already use.
- Move the precise time to the tooltip, on the automation's own clock, next to the
  timezone and the cron recurrence that produced it.
- Phrase future moments as "in 6 minutes" rather than "6 minutes from now", matching
  how the same helper already phrases "tomorrow" and "in 4 days". Every other caller
  renders a past moment, so only this column changes wording.
- Give the helper an options.fallback, and pass the schedule-clock time: beyond a week
  there is no useful relative phrasing left, and the old fallback dated the run by the
  viewer's clock rather than by the clock the automation keeps.
- Drop "(local)" from the column heading, which no longer describes what the cell shows.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

* ui/automations: read Created At on the automation's own clock

Context:
- The Created At cell showed a friendly delta, but hovering it produced the raw stored
  timestamp in UTC, which is neither precise-looking nor the clock the rest of the row keeps.

Change:
- Spell the creation moment out in the automation's timezone on hover, as the next run
  already does, so a row mixes no clocks.
- Fall back to the same schedule-clock wording once the automation is older than a week,
  rather than dating it by the viewer's own timezone.
- Keep the stored timestamp as the tooltip when the timezone cannot be resolved.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

* ui/automations: call the p... (continued)

106 of 113 new or added lines in 6 files covered. (93.81%)

1 existing line in 1 file now uncovered.

19602 of 22819 relevant lines covered (85.9%)

0.86 hits per line

Uncovered Changes

Lines Coverage ∆ File
4
95.12
flexmeasures/api/ui/session.py
3
49.65
-0.35% flexmeasures/api/v3_0/__init__.py

Coverage Regressions

Lines Coverage ∆ File
1
49.65
-0.35% flexmeasures/api/v3_0/__init__.py
Jobs
ID Job ID Ran Files Coverage
1 35710232804.1 22 Sep 2026 09:35AM UTC 186
85.9
GitHub Action Run
Source Files on build 35710232804
  • Tree
  • List 186
  • Changed 6
  • Source Changed 5
  • Coverage Changed 6
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #35710232804
  • 2a5fb1e3 on github
  • Prev Build on main (#35706097596)
  • Next Build on main (#35719809170)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc