jasonwitty
d653cbcadc
- Journal pane now distinguishes 'no entries' from 'no journal access': journalctl exits 0 with empty output when the agent's user simply can't see the target's entries (demo mode / user-run agents), explaining itself only on stderr. The agent forwards that hint as an additive JournalResponse.notice and the client renders it with practical advice. Verified E2E via a stub journalctl emulating the unprivileged case. - Version 1.60.0 across all crates (1.51 would read fine, but the repo's scheme is 1.40/1.50/…, and a literal 1.6.0 would sort BELOW 1.50.0 in semver). All user-facing version strings already come from CARGO_PKG_VERSION — a stale binary was the only way to see an old one. - scripts/install.sh: build-from-source install/upgrade for the test fleet (Linux + macOS). Detects in-repo checkouts, installs rustup when missing, replaces a systemd socktop-agent service binary in place and restarts it, requires system protoc on riscv64. - build.rs (agent + connector): fall back to $PROTOC / PATH when protoc-bin-vendored has no binary for the host (riscv64) — native SBC builds previously panicked in the build script. - CHANGELOG.md covering v1.50.0 -> 1.60.0. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
17 lines
751 B
Rust
17 lines
751 B
Rust
fn main() {
|
|
println!("cargo:rerun-if-changed=proto/processes.proto");
|
|
|
|
// Compile protobuf definitions for processes
|
|
let mut cfg = prost_build::Config::new();
|
|
cfg.out_dir(std::env::var("OUT_DIR").unwrap());
|
|
// Vendored protoc for reproducible builds where available. It ships no
|
|
// riscv64 binary, so on such hosts fall through to $PROTOC / PATH
|
|
// (prost-build's default lookup) — apt: protobuf-compiler.
|
|
if let Ok(protoc) = protoc_bin_vendored::protoc_bin_path() {
|
|
cfg.protoc_executable(protoc);
|
|
}
|
|
// Use local path (ensures file is inside published crate tarball)
|
|
cfg.compile_protos(&["proto/processes.proto"], &["proto"]) // relative to CARGO_MANIFEST_DIR
|
|
.expect("compile protos");
|
|
}
|