fix broken alias check is buildx is installed as alias for builder #3795
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.
Commit cbec75e (#3429) updated
runDocker()
to load plugin-stubs beforeprocessAliases()
was executed. As a result, plugin stubs were considered as "builtin commands", causing the alias verification to fail;Without alias installed:
After running
docker buildx install
;This patch moves loading the stubs after the call to
processAliases()
, so that verification passes. As an extra precaution, theprocessAliases()
function is also updated to exclude plugin-stub commands.Note that cbec75e (#3429) also introduced a performance regression (#3621), which may be related to the early loading of plugins (and creating stubs); it looks like various other code locations may also be loading plugins, for example
tryPluginRun()
callspluginmanager.PluginRunCommand()
, which also traverses plugin directories.We should look under what circumstances the plugin stub-commands are actually needed, and make sure that they're only created in those situations.
- A picture of a cute animal (not mandatory but encouraged)