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
Hi guys,
Big thanks for this feature very vey useful!!
I've tried it and i have an issue that i replicate here with a red test when running bazel test --config=release //lib/tests/yq/...
It's unfortunately not working when i stamp a value from stable-status.txt when I use the release config with bazel.
For info i am running on Bazel 5.4.0
opicaud
changed the title
Support stamping on yq rule not working when stamp coming from running workspace_status script
[Bug] Support stamping on yq rule not working when stamp coming from running workspace_status script
Jun 22, 2023
opicaud
changed the title
[Bug] Support stamping on yq rule not working when stamp coming from running workspace_status script
[Bug] Support stamping on yq rule not working when stamp coming from running a "non-mocked" workspace_status script
Jun 22, 2023
Hey. Thanks for raising this issue. I can reproduce your bug.
It turns out when I first implemented this, I used a newer version of yq on my host when finding a working yq expression to read the stamping info from the volatile and stable info files.
This seems to be broken with any yq version older than 4.30.3. Since the yq version in this ruleset is held back to 4.25.2, it is broken by default.
Fixes d79f4d4Fixes#463
This is required since versions of yq older than 4.30.3 do not parse "\n" correctly.
See mikefarah/yq#1430 and e02bb7194897edb916a6787fb8f8e5a7f432dd94
Hi guys,
Big thanks for this feature very vey useful!!
I've tried it and i have an issue that i replicate here with a red test when running
bazel test --config=release //lib/tests/yq/...
It's unfortunately not working when i stamp a value from stable-status.txt when I use the release config with bazel.
For info i am running on Bazel 5.4.0
Originally posted by @opicaud in #223 (comment)
The text was updated successfully, but these errors were encountered: