Skip to content

fix: labelsToWatch short-circuiting faster than it should#826

Open
markovejnovic wants to merge 2 commits into
bazelbuild:mainfrom
mesa-dot-dev:main
Open

fix: labelsToWatch short-circuiting faster than it should#826
markovejnovic wants to merge 2 commits into
bazelbuild:mainfrom
mesa-dot-dev:main

Conversation

@markovejnovic

@markovejnovic markovejnovic commented Apr 22, 2026

Copy link
Copy Markdown

Resolves #825. Please read that ticket as I don't really understand the intent behind this function nor its role in the larger application.

@markovejnovic markovejnovic requested a review from achew22 as a code owner April 22, 2026 00:57
@achew22

achew22 commented Apr 23, 2026

Copy link
Copy Markdown
Member

Hey @markovejnovic. Love the contribution. Can I have you put together an e2e test that can be included in the repo which demonstrates this behavior so that we don't regress going forward?

@markovejnovic

Copy link
Copy Markdown
Author

Of course! I'll try to get to it soon! Sorry I didn't reply earlier!

Marko Vejnovic added 2 commits May 23, 2026 09:42
Extract resolveLabels as a standalone pure function from labelsToWatch
for testability. Add TestResolveLabels with 6 subtests — last two
("local repo match does not stop processing subsequent labels" and
"multiple local repo matches all resolved") fail, proving the break
bug silently drops labels after the first @repo match.
@achew22

achew22 commented May 24, 2026

Copy link
Copy Markdown
Member

I'd very much like to see an e2e test attached to this. Unit tests don't really demonstrate the issue since it's so easy to accidentally encode an incorrect assumption about the world

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.

ibazel failing to restart JS application with heavy external dependencies

2 participants