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

SwissDataScienceCenter / renku-data-services / 10715718710
86%

Build:
DEFAULT BRANCH: main
Ran 05 Sep 2024 07:31AM UTC
Jobs 2
Files 218
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

05 Sep 2024 07:18AM UTC coverage: 90.574% (-0.02%) from 90.592%
10715718710

push

github

web-flow
chore: Send all search synchronisation events to a single queue (#377)

* chore: Send all search synchronisation events to a single queue

Instead of using multiple queues/streams all the events are now sent
to a single stream `search.sync`. They are only intended to
synchronize data between data-services and search-service.

This requires a change to the `Event.queue` field. It was used for two
things: the redis qeue/stream name and the message type. Now these two
are different now and so the event must carry both separately. Events
are first stored to the postgres database as single value (its avro
payload) and the qeue name is stored alongside. When re-creating the
event object from the database, we don't have the `(header, payload)`
tuple, but only a `dict[str, Any]` (the raw message). This is
different to when creating the event from a `message-type` and
structured avro object. Since we never need to read the structured
avro object of an event, the `Event` class is now simplified to only
carry the raw message. This makes the generic type param obsolete and
removes the early return in the `serialize` method which checked the
payloads runtime type (as when read from the db).

The `serialize` method is still there to keep the interface, allowing
perhaps later to add more structure to the class.

Additional to the canonical constructor of the event, there is a
second one, `create`, for creating an event from a structured avro
object and message type.

NOTE: This change requires search-services to be at least version 0.5.0 (as
 in renku 0.57.0).

30 of 30 new or added lines in 3 files covered. (100.0%)

7 existing lines in 5 files now uncovered.

9302 of 10270 relevant lines covered (90.57%)

1.61 hits per line

Uncovered Existing Lines

Lines Coverage ∆ File
1
98.15
-1.85% components/renku_data_services/base_api/misc.py
1
91.4
-1.08% components/renku_data_services/base_models/core.py
1
87.81
0.0% components/renku_data_services/crc/db.py
1
94.14
-0.37% components/renku_data_services/users/db.py
3
93.19
-0.62% components/renku_data_services/crc/blueprints.py
Jobs
ID Job ID Ran Files Coverage
1 run-main-tests - 10715718710.1 05 Sep 2024 07:44AM UTC 218
89.84
GitHub Action Run
2 run-schemathesis-tests - 10715718710.2 05 Sep 2024 07:31AM UTC 218
70.75
GitHub Action Run
Source Files on build 10715718710
  • Tree
  • List 218
  • Changed 13
  • Source Changed 3
  • Coverage Changed 13
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #10715718710
  • 28a05cd5 on github
  • Prev Build on main (#10701549852)
  • Next Build on main (#10721216299)
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