summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/rangehttpserver
diff options
context:
space:
mode:
authorVincent Ambo <mail@tazj.in>2025-03-02 19:19:52 +0300
committersternenseemann <sternenseemann@systemli.org>2025-03-03 12:45:41 +0100
commit7768e6b94fdec14ee0dc366aa850ea8f2dc11af1 (patch)
treeea9af16197d63aa7c859104a350df6c7de74a5ae /pkgs/development/python-modules/rangehttpserver
parentbd92f7fb61a8af77d32a35320017d083ee2a82eb (diff)
buildkite-agent: override buildVersion sentinel value to fix crashes
Buildkite introduced a weird check that determines whether the bootstrap agent path (?) matches the binary that the agent was started from: https://github.com/buildkite/agent/pull/3123 They did this to work around some issues with the internal development flows. However, this check is toggled by whether or not the `buildNumber` compile-time variable is set to the special `x` sentinel value. In their publicly released binaries (which we do not use, of course), this is set to some other value. In Nix builds they are at the default sentinel value, causing crashes at startup because of the wrapper script not matching the binary path: ``` buildkite-agent: fatal: check binary paths: mismatched buildkite-agent paths: host="/nix/store/rmp9g00bppi8yimr0ngnx6490w196in8-buildkite-agent-3.89.0/bin/.buildkite-agent-wrapped" bootstrap="/nix/store/rmp9g00bppi8yimr0ngnx6490w196in8-buildkite-agent-3.89.0/bin/buildkite-agent" ``` To work around this we just set the build "number" to `nix`.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions