Skip to content
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

solver: ensure each ref in the result map is evaluated #4544

Merged
merged 1 commit into from
Jan 17, 2024

Conversation

jedevc
Copy link
Member

@jedevc jedevc commented Jan 10, 2024

There was a reasonably significant typo in d709afd (#3137), yikes.

Came across this while working in the area 😱 Slightly terrifying, I clearly wasn't playing close attention 😢

I don't think this is on a critical code-path anywhere, doing Evaluate on a frontend provided result was designed to be used in docker/buildx#1197, but I don't think ever became relied-upon functionality.

@jedevc jedevc marked this pull request as draft January 10, 2024 18:10
@jedevc

This comment was marked as outdated.

There was a typo in d709afd.

Signed-off-by: Justin Chadwell <[email protected]>
@jedevc
Copy link
Member Author

jedevc commented Jan 11, 2024

Added a test. Note that the fix is for a panic - a frontend could cause buildkit to deref a nil pointer.

@jedevc jedevc marked this pull request as ready for review January 11, 2024 11:26
@tonistiigi tonistiigi merged commit 0e1e36b into moby:master Jan 17, 2024
60 checks passed
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.

2 participants