Hive
Forage
Feature requests, bug reports, feedback, GitHub issues, and Grafana alerts in one queue.
| Item | Type | Status | Domains | Source | Updated | Actions |
|---|---|---|---|---|---|---|
|
fix(server): stop reporting expected webhook delivery failures to Sentry
|
GitHub issue
|
Closed
|
Atlas
|
tuist/tuist
#11631
|
| |
|
perf(server): back flaky-alert default-branch validation with a marker MV
|
GitHub issue
|
Closed
|
Testing
|
tuist/tuist
#11626
|
| |
|
feat(server): model xctest runner errors as run/target-level Errors, not test cases
Models |
GitHub issue
|
Closed
|
Testing
|
tuist/tuist
#11606
|
| |
|
fix(server): route reliability-rate rolling alerts through bucketed MVs and cap ClickHouse query memory
|
GitHub issue
|
Closed
|
Testing
|
tuist/tuist
#11623
|
| |
|
feat(server): cursor-only generations API + faster flaky-marking scan
Two ClickHouse read-path fixes for “Slow ClickHouse query” Grafana alerts (p90 > 1s), profiled against production |
GitHub issue
|
Closed
|
Generated projects
Testing
|
tuist/tuist
#11634
|
| |
|
fix(server): give the suite catch-all shard every module’s test products
|
GitHub issue
|
Closed
|
Testing
|
tuist/tuist
#11635
|
| |
|
fix(server): count each run once in rolling flaky/reliability alert evaluation
The rolling-window path of the flaky-test automations ( |
GitHub issue
|
Closed
|
Testing
|
tuist/tuist
#11627
|
| |
|
feat: module cache network analytics (bandwidth + overall fetch time)
Per-run module cache network analytics: for every run, see how much data the module (binary) cache moved and how fast, right next to its hit rate. |
GitHub issue
|
Closed
|
Cache
|
tuist/tuist
#11619
|
| |
|
feat(kura): serve HTTP and REAPI gRPC on a single co-hosted listener
Kura used to serve its HTTP cache API and its REAPI gRPC surface on two separate listeners (container ports 4000 and 50051). That’s invisible behind the public ingress, where n… |
GitHub issue
|
Closed
|
Kura
|
tuist/tuist
#11591
|
| |
|
fix(cli): batch CAS analytics writes off the cooperative pool
The CAS daemon’s per-operation analytics recording moves off the Swift-concurrency cooperative pool: |
GitHub issue
|
Closed
|
Cache
|
tuist/tuist
#11630
|
|