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

FlexMeasures / flexmeasures / 28508296292 / 1
81%
main: 81%

Build:
DEFAULT BRANCH: main
Ran 01 Jul 2026 09:51AM UTC
Files 167
Run time 5s
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

01 Jul 2026 09:40AM UTC coverage: 81.076% (-0.2%) from 81.266%
28508296292.1

push

github

web-flow
Fix Charge Point sessions chart loading, plus zoom-sync, epoch-bar, and alignment improvements (#2259)

* fix: render charge point sessions chart and sync x-axis zoom

The charge point sessions chart crashed and, once rendering, did not share
x-axis pan/zoom with the other subcharts.

- Read sensors via _extract_sensors_from_entry to handle the standardized
  {title, plots:[{sensors}]} format (fixes NoneType/KeyError on 'sensors').
- Filter the 'Power flow by type' entry through its plots.
- Always set resolve.scale.x = shared (only mark color independent when
  legends are not combined) so subcharts share the x scale.
- Remove pinned x/x2 scale domains from the sessions layers.
- Add an invisible zoom layer bound to the same event_start field the other
  charts use, so dragging the sessions chart drives the same shared-scale
  signal and all subcharts pan together.

* fix: hide incomplete charge point session pairs (no epoch bars)

A session bar was drawn from 1970-01-01 when one endpoint of a pair was
missing (e.g. a 'stop charging' value with no matching 'start charging').
The pivot transform fills the missing endpoint with 0, which Vega renders
as epoch 0 (1970); isValid() treats 0 as valid, so it must be excluded too.

Filter each paired session layer (start/stop charging, arrival/departure,
plug in/plug out) requiring both endpoints to be > 0, so a pair missing an
endpoint is skipped while the asset's other complete pairs still render.

* fix: align charge point session lines per asset

The thick start/stop charging line did not sit on the thin plug-in/out and
arrival/departure lines. Each layer derived its yOffset from a session_id
built as asset_id + event_start, but the charging beliefs carry a different
event_start than the plug/arrival beliefs (and may even fall on another day),
so the charging layer landed in a different yOffset sub-band.

Remove the per-session yOffset from the session layers so all three pairs of
the same asset share one... (continued)

13740 of 16947 relevant lines covered (81.08%)

0.81 hits per line

Source Files on job 28508296292.1
  • Tree
  • List 167
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 28508296292
  • 9588cb35 on github
  • Prev Job for on main (#28473934631.1)
  • Next Job for on main (#28508421674.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc