Nightly cassert failures 2026-08-12..17 - consolidated triage (5 issues, 5 root causes, 0 assertions)
Open
nightly-cassert
- Dominant language
- C
- Stars
- 12.8k
- Forks
- 794
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 31
Description
Nightly full-cassert run failed.
Run: https://github.com/citusdata/citus/actions/runs/31990816303
Failing jobs:
- cassert PG18 - regress
First runs are EXPECTED red as pre-existing PG-core and Citus asserts surface.
Contributor guide
Research direction
Start with the linked GitHub Actions run and inspect the failing “cassert PG18 - regress” job for the failure details. The issue provides no specific assertion, files, or requested change, so the next step is to identify the five root causes; it does not define what would count as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, postgresql
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100