chore(deps): bump log from 0.4.29 to 0.4.32 in /src-tauri#8
Closed
dependabot[bot] wants to merge 1 commit into
Closed
chore(deps): bump log from 0.4.29 to 0.4.32 in /src-tauri#8dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
Bumps [log](https://github.com/rust-lang/log) from 0.4.29 to 0.4.32. - [Release notes](https://github.com/rust-lang/log/releases) - [Changelog](https://github.com/rust-lang/log/blob/master/CHANGELOG.md) - [Commits](rust-lang/log@0.4.29...0.4.32) --- updated-dependencies: - dependency-name: log dependency-version: 0.4.32 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/cargo/src-tauri/log-0.4.32
branch
from
f344ac7 to
a68974b
Compare
rwetz
pushed a commit
that referenced
this pull request
Jun 12, 2026
The in-app half of the ML Suite (spec: ML_SUITE.md). A new ML Lab sidebar panel (pinned to the rail by default, one-time promotion for existing rails) drives the external nexis-ml engine over an NDJSON stdio protocol: one-click engine install into the detected venv (CPU or CUDA torch via fixed pip flavors), in-panel project scaffolding (Create & train), live training with a progress bar, plain-language status sentences, friendly metric names, and decimated canvas charts; past runs render from metrics.jsonl with no engine running. A status bar pill shows progress and jumps to the panel. Rust side (modules/ml.rs, modeled on the LSP session): ml_detect / ml_spawn (train|replay|new allowlist, authorize_spawn_cwd, ConPTY-safe hide_console) with a reader->flusher pair batching stdout at ~30 Hz, ml_cancel via stdin, ml_kill, ml_install (allowlisted pip flavors), ml_env capability probe, ml_gpu_probe (nvidia-smi). Engine >=0.2.0 reports the training device (auto/cpu/gpu with a job-size heuristic); the panel surfaces it as a GPU chip, an install-time GPU checkbox, and an Enable GPU upsell when the CPU torch build sits next to an NVIDIA card. Pitfalls carried over: #1C (authorize before spawn), #4/#1D (hide_console everywhere), #8 (poison-recovering locks), #10 (detection memoized with delete-on-reject), #14 (charts subscribe to a primitive tick; series buffers live outside zustand), #7-adjacent (decimation caps series memory; Rust caps line length). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Author
|
Superseded by #24. |
rwetz
pushed a commit
that referenced
this pull request
Jul 4, 2026
…f shared locks, consolidate helpers The CLAUDE.md pitfall invariants move from prose into the build: - proc::command() is the only sanctioned subprocess constructor (CREATE_NO_WINDOW pre-applied); raw std::process::Command::new is banned by clippy disallowed-methods + a tripwire test (pitfalls #1D/#4). All 17 spawn sites migrated; hide_console is now private. - New tripwire suites: src-tauri/tests/pitfall_invariants.rs (ConPTY lifecycle lock on create+close, detached panic-free pty_close, authorize_spawn_cwd, -Command/NEXIS_PWSH_PROFILE launch, Command::new confinement, lock-poison bans) and src/lib/pitfall-guards.test.ts (pty_open confinement, writePref routing, composer disabled, reasoning pruning, Zustand selector stability). Failure messages name the pitfall. - Pitfall-#8 poison recovery extended beyond the PTY to every shared-thread module: shell session map + background log buffers, LSP/DAP sessions, the fs_grep sink, and CONPTY_LIFECYCLE_LOCK itself. fs_stat's unreachable symlink kind fixed. - Helper consolidation: canonical basename/dirname family in lib/path.ts (seven private copies still carried the fixed pitfall-#12 drive-root bug), formatBytes in lib/format.ts; shell_init.rs write_if_changed / integration_root / script consts de-duplicated across platforms. Gates: tsc, vitest+coverage, cargo test/clippy/fmt all green; the clippy ban verified to fire on an injected violation. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps log from 0.4.29 to 0.4.32.
Release notes
Sourced from log's releases.
Changelog
Sourced from log's changelog.
Commits
a5b5b21Merge pull request #730 from rust-lang/cargo/0.4.32c8d3b12prepare for 0.4.32 releasece6cd9fMerge pull request #729 from tisonkun/kv-std-support20b3b05drop cfg-feature=kv as it is already met7bc1200kv::std_support may not need value-bag5808392Merge pull request #728 from rust-lang/cargo/0.4.3186d739fprepare for 0.4.31 releasec906cfbMerge pull request #727 from tisonkun/leverage-static-str-key-when-possible756c279leverage str literal as well3dd250drename Key::from_static_str to from_str_static