Repository navigation
Reused-version sends leave successfully sent sessions marked changed - #36
Closed
dipeshbabu wants to merge 1 commit into
Closed
dipeshbabu wants to merge 1 commit into
dipeshbabu wants to merge 1 commit into
Conversation
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.
Upstream replacement: subconscious-systems#36
This PR was created in the fork in error. The fix and its issue are now submitted to upstream.
When sendSession reuses unchanged plaintext from a stored version, it refreshes local state only if the label changes. A touched or moved transcript stays marked changed after a successful send and retains a stale pull handle.
Refresh the current source path, size, activity time, mtime, label, and pull handle after every successful reused-version send. A mocked API regression decrypts the rewrapped envelope as the recipient and verifies the local status becomes synced without a content upload.
Validation: frozen-lockfile dependencies, typecheck, full tests, npm build, bundled CLI smoke checks, and Ubuntu/Windows CI on Node 20/22 before PR creation.
This PR is based on the CI foundation branch; merge that PR first.
Closes #34.
All branch CI checks passed on be894b3: https://github.com/dipeshbabu/vibi-cli/actions/runs/37263756448