grabowski
6ae67dec63
CI / Format & lint (push) Successful in 22s
CI / Test suite (push) Successful in 59s
Docs / Validate documentation (push) Successful in 25s
Rust / fmt, clippy, test, build (push) Successful in 10m2s
Security / Dependency vulnerabilities (push) Successful in 2m11s
Security / Static analysis (push) Successful in 22s
Security / License report (push) Successful in 1m37s
Phase 2b/2c of docs/RUST_REWRITE.md. With FORECAST_IN_COLLECTOR=true (shared .env) ping-collector, after each cycle that brought newer RID or HII readings and at least hourly: loads the last 336 h (RID + HII mirror fill), fetches the rain forecast, runs every exported model (rust/forecast), stores forecast_history and forecast_current, and sends the ntfy notifications. The Python API then serves forecast_current as /forecast (computing in-process only when it is older than FORECAST_MAX_AGE_SECONDS) and neither forecasts nor notifies. ntfy (collector/src/notify.rs): a port of src/notify.py with the same topics, texts, hysteresis, capacity guard and notification_state keys, checked word for word on 751 messages generated by Python (testdata/gen_notify_cases.py). The change: for stations whose ThaiWater twin is the same sensor, a reading newer than RID's drives the level alerts (marked as ThaiWater telemetry), and the feed counts as stale only when neither source has a reading for 3 h. RID alone lagging is reported once after RID_STALE_ALERT_HOURS (18). This ends the nightly "gauge feed stale" / "recovered" pairs caused by RID's late reports. Commands: `forecast [--json] [--save] [--now] [--rain-file]`, `notify --dry-run`. scripts/forecast_parity.py compares Python and the collector on the live database (same moment, same rain); locally 48/48 rows identical. install_collector.sh: models export + that check on every install, --cutover-forecast (refuses on a failed check) and --rollback-forecast. Trees are packed into 24-byte nodes: 70 MB peak with all 15 models (was 140). Forecast values are written to NUMERIC as shortest round-trip text, so they round as psycopg2's do. DB test schemas get a counter (parallel tests collided on Windows' coarse clock).
73 lines
1.8 KiB
YAML
73 lines
1.8 KiB
YAML
name: Rust
|
|
|
|
# rust/ workspace (ping-collector, ping-forecast): format, clippy, tests
|
|
# (the Python parity fixtures, and the database tests against a throwaway
|
|
# PostgreSQL service), release build.
|
|
# The Linux binary is uploaded as an artifact for scripts/install_collector.sh.
|
|
|
|
on:
|
|
push:
|
|
branches: [master, develop]
|
|
paths:
|
|
- "rust/**"
|
|
- "src/data/stations.json"
|
|
- ".gitea/workflows/rust.yml"
|
|
pull_request:
|
|
branches: [master]
|
|
paths:
|
|
- "rust/**"
|
|
- "src/data/stations.json"
|
|
- ".gitea/workflows/rust.yml"
|
|
workflow_dispatch:
|
|
|
|
jobs:
|
|
rust:
|
|
name: fmt, clippy, test, build
|
|
runs-on: ubuntu-latest
|
|
services:
|
|
postgres:
|
|
image: postgres:16
|
|
env:
|
|
POSTGRES_PASSWORD: ping
|
|
POSTGRES_DB: ping
|
|
options: >-
|
|
--health-cmd pg_isready
|
|
--health-interval 5s
|
|
--health-timeout 5s
|
|
--health-retries 20
|
|
env:
|
|
CARGO_TERM_COLOR: always
|
|
TEST_DATABASE_URL: postgres://postgres:ping@postgres:5432/ping
|
|
defaults:
|
|
run:
|
|
working-directory: rust
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
|
|
- name: System packages (OpenSSL headers for native-tls)
|
|
run: |
|
|
SUDO=$(command -v sudo || true)
|
|
$SUDO apt-get update -qq
|
|
$SUDO apt-get install -y -qq pkg-config libssl-dev
|
|
|
|
- uses: dtolnay/rust-toolchain@stable
|
|
with:
|
|
components: rustfmt, clippy
|
|
|
|
- name: fmt
|
|
run: cargo fmt --all --check
|
|
|
|
- name: clippy
|
|
run: cargo clippy --all-targets --locked -- -D warnings
|
|
|
|
- name: test
|
|
run: cargo test --locked
|
|
|
|
- name: release build
|
|
run: cargo build --release --locked
|
|
|
|
- uses: actions/upload-artifact@v3
|
|
with:
|
|
name: ping-collector-linux-x86_64
|
|
path: rust/target/release/ping-collector
|