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
I came across this while trying to run webots -> pepsi run --bin hulk_webots and got an error saying realtime scheduler cannot be set. This issue and changed command came after pepsi max.
Looking deeper, the root cause is that the features set for hulk_nao leaked into hulk_webots when calling pepsi run.
It is also the same behavious by cargo run --bin hulk_webots. It seems using cargo run in this way inspects the workspace file and reads feature flags used by everyone and use the combined result (unified?).
So I think the pepsi max PR isn't really at fault, rather how cargo run works?
Old pepsi run uses cargo run __manifest_path=... toml (I forgot the exact wording). This seems to read only the needed manifest, so features set for other executables aren't leaked into the build.
The text was updated successfully, but these errors were encountered:
I came across this while trying to run webots ->
pepsi run --bin hulk_webots
and got an error saying realtime scheduler cannot be set. This issue and changed command came after pepsi max.Looking deeper, the root cause is that the features set for
hulk_nao
leaked intohulk_webots
when calling pepsi run.It is also the same behavious by
cargo run --bin hulk_webots
. It seems using cargo run in this way inspects the workspace file and reads feature flags used by everyone and use the combined result (unified?).So I think the pepsi max PR isn't really at fault, rather how cargo run works?
Old pepsi run uses
cargo run __manifest_path=... toml
(I forgot the exact wording). This seems to read only the needed manifest, so features set for other executables aren't leaked into the build.The text was updated successfully, but these errors were encountered: