Skip to content

Conversation

@sxlijin
Copy link
Collaborator

@sxlijin sxlijin commented Sep 23, 2025

Roll forward of #2486, with deadlocks fixed.

Deadlocks were present because session.reload() needs to grab locks on every project, but its API does not make this obvious, and in #2486 there were implicit scope changes that resulted in MutexGuard destructors not running before session.reload() got called.

@sxlijin sxlijin temporarily deployed to boundary-tools-dev September 23, 2025 20:04 — with GitHub Actions Inactive
@sxlijin sxlijin temporarily deployed to boundary-tools-dev September 23, 2025 20:04 — with GitHub Actions Inactive
@sxlijin sxlijin temporarily deployed to boundary-tools-dev September 23, 2025 20:04 — with GitHub Actions Inactive
@entelligence-ai-pr-reviews
Copy link

🔒 Entelligence AI Vulnerability Scanner

No security vulnerabilities found!

Your code passed our comprehensive security analysis.


@entelligence-ai-pr-reviews
Copy link

LGTM 👍

@github-actions
Copy link

@vercel
Copy link

vercel bot commented Sep 23, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Preview Comments Updated (UTC)
promptfiddle Skipped Skipped Sep 25, 2025 9:21pm

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Codex Review: Here are some suggestions.

Reply with @codex fix comments to fix any unresolved comments.

About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you open a pull request for review, mark a draft as ready, or comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex fix this CI failure" or "@codex address that feedback".

Comment on lines 27 to 33
if params.changes.iter().any(|change| {
let Ok(path) = change.uri.to_file_path() else {
return true;
};
session.get_or_create_project(&path).is_err()
}) {
return Ok(());

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P1] Avoid dropping watched-file batches with mixed paths

The new guard returns early whenever any change in the batch cannot be resolved to a baml_src project. This skips the reload and diagnostic publishing for the entire batch, even when the same batch contains valid baml_src files. The previous code only bailed out when no baml_src paths were present. A watcher that reports both BAML and non-BAML file events (e.g. a generator output alongside a source change) will now leave diagnostics stale for the actual BAML file. Filter out non-BAML entries instead of aborting the whole handler.

Useful? React with 👍 / 👎.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think this is valid no?

@github-actions
Copy link

@github-actions
Copy link

@github-actions
Copy link

@github-actions
Copy link

@github-actions
Copy link

@github-actions
Copy link

@github-actions
Copy link

@github-actions
Copy link

@sxlijin sxlijin added this pull request to the merge queue Sep 25, 2025
Merged via the queue into canary with commit 613df6b Sep 25, 2025
25 checks passed
@sxlijin sxlijin deleted the sam/vscode-playground branch September 25, 2025 22:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants