-
Notifications
You must be signed in to change notification settings - Fork 115
fix(pi): resolve native embedding routing before registration #462
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+223
−11
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2232,6 +2232,23 @@ export function registerProjectInObservationMode( | |
| return snapshotFor(registration); | ||
| } | ||
|
|
||
| export function unregisterProjectShadowEmbedding(projectIdentity: string): void { | ||
| const shadow = shadowRegistrations.get(projectIdentity); | ||
| shadowRegistrations.delete(projectIdentity); | ||
| dbForShadowQueue.delete(projectIdentity); | ||
| pendingShadowBackfills.delete(projectIdentity); | ||
| for (let index = shadowQueue.length - 1; index >= 0; index -= 1) { | ||
| if (shadowQueue[index].projectIdentity === projectIdentity) shadowQueue.splice(index, 1); | ||
| } | ||
| for (const scope of ["memory", "commit", "chunk"] as const) { | ||
| const key = `${projectIdentity}:${scope}`; | ||
| shadowBackfillLastIds.delete(key); | ||
| shadowBackfillStopReasons.delete(key); | ||
| shadowBackfillLastWriteOutcomes.delete(key); | ||
| } | ||
| disposeProvider(shadow?.provider ?? null); | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. P2: If unregister runs while a shadow batch is in flight, the worker can still write vectors for the retired shadow model after this disposal. Add cancellation or a registration-generation check before committing the batch, and suppress stale worker state updates. Prompt for AI agents |
||
| } | ||
|
|
||
| export function unregisterProjectEmbedding(projectIdentity: string): void { | ||
| const prior = projectRegistrations.get(projectIdentity); | ||
| const shadow = shadowRegistrations.get(projectIdentity); | ||
|
|
||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
P3: The
expect(disposed).toBe(true)assertion depends on a synchronous timing detail:unregisterProjectShadowEmbedding→disposeProvidercallsvoid provider.dispose()without awaiting, and the test provider's asyncdisposebody setsdisposed = truebefore its first (nonexistent) await. This passes only because the async body runs synchronously. IfdisposeProviderever starts deferring disposal or the provider discards returns control before setting the flag, the test would silently pass/fail based on timing rather than actual retirement. Since the disposal is fire-and-forget in the production code, assert on the deterministic observable (shadow cohort null, primary intact) and avoid relying on the fire-and-forget side effect timing for the disposal check.Prompt for AI agents