Repository navigation
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…-activation Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> # Conflicts: # .github/workflows/android-apk.yml # openless-all/app/package-lock.json # openless-all/app/package.json # openless-all/app/src-tauri/Cargo.lock # openless-all/app/src-tauri/Cargo.toml # openless-all/app/src-tauri/tauri.conf.json
…t/issue-1003-voice-activation Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> # Conflicts: # openless-all/app/crates/openless-core/src/cloud_sync_e2ee_documents/registry.rs # openless-all/app/src-tauri/src/core_adapters.rs # openless-all/app/src-tauri/src/recorder.rs # openless-all/app/src/components/SettingsModal.tsx # openless-all/app/src/i18n/zh-CN.ts # openless-all/app/src/lib/ipc/mock-data.ts # openless-all/app/src/lib/types.ts # openless-all/app/src/pages/settings/RecordingInputSection.tsx # openless-all/app/src/pages/settings/tabs.tsx
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
HKLHaoBin
marked this pull request as draft
October 17, 2026 15:59
Retain the newer voice activation implementation, punctuation regression tests, privacy-safe P1-P6 diagnostics, and Windows symbols already merged through Open-Less#1240. Resolve overlapping feature conflicts without reverting upstream fixes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
HKLHaoBin
marked this pull request as ready for review
October 21, 2026 16:20
Collaborator
Author
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.
Summary
完成,语音录入。.Refs #1003
Why retain the diagnostic probes?
There is no further tester evidence confirming whether the intermittent recognition crash has been resolved or simply has not reproduced. We therefore retain the existing privacy-safe P1–P6 diagnostic probes rather than treating the absence of a new report as proof of a fix. If the issue recurs, these lifecycle and timing records, together with the matching Windows EXE/PDB, will provide evidence for further investigation. The probes do not record audio or transcript content. They should be removed only after sufficient real-device verification; passing CI alone does not establish that the intermittent crash is fixed.
Beta synchronization
Merged
betaat8e8b3dbdand resolved the overlapping voice-activation conflicts, preserving the newer implementation, regression tests, diagnostic probes, and Windows symbols already merged via #1240. Application source now matchesbeta; the only remaining branch-only difference is the pre-existing Android workflow repository-metadata setting. This synchronization does not introduce another behavioral fix or claim that all of #1003 is resolved.Verification
Current commit:
e3b5c6ba8c8eaa60b29b47197f04dbcf753df711.git diff --checkand staged whitespace checks passed; no unresolved merge conflicts remain.runner_id=0, no steps); GitHub reports macOS ARM capacity constraints. The single targeted retry also ended without acquiring a runner (runner_id=0, no steps), with the same capacity annotations. The branch workflow therefore ended in failure due to unavailable hosted capacity, not an executed test failure; it has not passed as a whole. No further automatic retries are queued.runner_id=0, no steps), with the same capacity annotations. The overall workflow ended in failure; macOS ARM packaging remains unverified. No further automatic retries are queued.sha256:891f00384ee41962948aa54d29e8b817beee9301ec7292ae0590e7908961e4af.The PR remains a draft for the author to mark ready after verification. No claim is made that the intermittent crash has passed real-device verification.
🤖 Generated with Claude Code