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

FlexMeasures / flexmeasures / 37140900614
88%

Build:
DEFAULT BRANCH: main
Ran 03 Oct 2026 05:46PM UTC
Jobs 1
Files 188
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

03 Oct 2026 05:32PM UTC coverage: 86.306% (+0.008%) from 86.298%
37140900614

push

github

web-flow
Couple a data generator's data source to the organisation it runs for (#2634)

* Record under a data source of the organisation a data generator computes for

A data source carries an organisation, but only sources of type user ever got one,
because nothing on the generator side passed one to `get_or_create_source`.
Two organisations running the same generator under the same configuration therefore shared one source row,
and a `source-account` filter, which selects sources linked to an organisation, matched user-recorded data only.

The organisation is now part of what identifies a source, including when there is none:
asking for a source without naming an organisation looks for one belonging to none, which is what the host's own generators record under.

A data generator says which organisation it computes for through `set_source_account`,
and otherwise goes by the sensors it writes to, which is the same rule the migration derives for the sources that already exist.
A public asset has no organisation, and writing to one does not make a generator the host's, so public outputs are passed over rather than counted.
Sensors of several organisations leave the source belonging to none, which is logged, since that is the one way new data can still land unowned.
A scheduler is always handed an asset or a sensor, so it knows this without being told.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0129WrXeJ5gia2pctFH93BqC
Signed-off-by: F.N. Claessen <claessen@seita.nl>

* Couple the data sources that already exist to the organisation they recorded for

Which organisation a source recorded for can be read off its data: a belief's sensor belongs to an asset, and that asset names the organisation.
Annotations say the same, and so does the asset an automation hangs off, which is what a source whose automation has not run yet has to go by.
Those signals are unioned rather than ranked, because two of them disagre... (continued)

37 of 47 new or added lines in 5 files covered. (78.72%)

20906 of 24223 relevant lines covered (86.31%)

0.86 hits per line

Uncovered Changes

Lines Coverage ∆ File
7
89.06
-0.01% flexmeasures/data/automations.py
2
83.87
-0.17% flexmeasures/data/models/planning/__init__.py
1
89.34
0.15% flexmeasures/data/models/data_sources.py
Jobs
ID Job ID Ran Files Coverage
1 37140900614.1 03 Oct 2026 05:46PM UTC 188
86.31
GitHub Action Run
Source Files on build 37140900614
  • Tree
  • List 188
  • Changed 6
  • Source Changed 6
  • Coverage Changed 6
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #37140900614
  • 41e9cc0d on github
  • Prev Build on main (#37138123571)
  • Next Build on main (#37220466607)
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