You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using version override in a Bender.local file, Bender behaves inconsistent to a normal version declaration:
Let's assume the following Bender.yml file of a sub-dependency:
If we call bender update followed by bender path foo we get the following:
/......../.bender/git/checkouts/foo-abcd
Inspecting this directory reveals, that bender checked out commit 1234 within the foo-abcd directory. First of all, this is unintuitive because the user would expect bender to generate a new version directory like it does for any other (not overriden) dependency.
The second problem is: If commit 1234 does not exist, bender update will not error out but will just keep using commit version abcd without notifying the user about the non existent override version 1234.
Expected behavior: Bender should create new directories for override versions and show an error message if it cannot find the commit referenced in an override.
The text was updated successfully, but these errors were encountered:
Mark the variables declared by the `snitch_cluster` system software CMakeLists.txt as `CACHE`, to then be picked-up appropriately by the `SnitchUtilities.cmake` file later on. Otherwise the wrong simulator and runtime would be used.
When using version override in a Bender.local file, Bender behaves inconsistent to a normal version declaration:
Let's assume the following Bender.yml file of a sub-dependency:
and the following override file:
If we call
bender update
followed bybender path foo
we get the following:/......../.bender/git/checkouts/foo-abcd
Inspecting this directory reveals, that bender checked out commit
1234
within thefoo-abcd
directory. First of all, this is unintuitive because the user would expect bender to generate a new version directory like it does for any other (not overriden) dependency.The second problem is: If commit
1234
does not exist, bender update will not error out but will just keep using commit versionabcd
without notifying the user about the non existent override version1234
.Expected behavior: Bender should create new directories for override versions and show an error message if it cannot find the commit referenced in an override.
The text was updated successfully, but these errors were encountered: