jasonwitty
bf6ac877c2
- socktop, socktop_agent, socktop_connector -> 1.51.0. - socktop_wasm_test and zellij_socktop_plugin consume the in-repo connector via path deps so wasm-feature API drift is caught at PR time instead of after publish. Immediately proved out: the wasm requests module needed the new sampled_at_ms field, invisible to native builds. - zellij plugin gains the standalone [workspace] marker (it could not be cargo-checked in-tree at all before). NOTE: its lib.rs has pre-existing compile errors unrelated to the connector (static mut STATE conflicts with register_plugin!, missing BTreeMap import) — needs its own rework, out of scope here. - README: sampled_at_ms in the example payload. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
7 lines
807 B
D
7 lines
807 B
D
/home/jasonw/Documents/GitHub/socktop/zellij_socktop_plugin/target/debug/deps/fixedbitset-4fef3022da8e36f2.d: /home/jasonw/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/fixedbitset-0.4.2/src/lib.rs /home/jasonw/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/fixedbitset-0.4.2/src/range.rs
|
|
|
|
/home/jasonw/Documents/GitHub/socktop/zellij_socktop_plugin/target/debug/deps/libfixedbitset-4fef3022da8e36f2.rmeta: /home/jasonw/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/fixedbitset-0.4.2/src/lib.rs /home/jasonw/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/fixedbitset-0.4.2/src/range.rs
|
|
|
|
/home/jasonw/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/fixedbitset-0.4.2/src/lib.rs:
|
|
/home/jasonw/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/fixedbitset-0.4.2/src/range.rs:
|