In reply to @k900:0upti.me
We can just shove it all into Redis or something

In reply to @k900:0upti.me
Like, who will actually write the code?

In reply to @k900:0upti.me
Yeah that's kind of the problem with everything

In reply to @woobilicious:matrix.org
That's a surprising take since rust seems like it was designed to do more low level, manual management of memory safely. While we just want to interact with some high level stuff like S3 and github, website? you'd get a long way with Haskell web framework and a little abstraction, without having to think too much about it, especially since it' has a real runtime with garbage collection & green threads. I do agree however with the pragmatic stuff like C-FFI, code reuse and accessibility.

The first thing that comes to mind is something like this

pkgs.hydra_unstable.overrideAttrs ({ postPatch ? "", ... }: {
  postPatch = postPatch + ''
    substituteInPlace src/hydra-eval-jobs/hydra-eval-jobs.cc \
        --replace 'queryMetaInt("timeout", 36000)' 'queryMetaInt("timeout", 108000)' \
        --replace 'queryMetaInt("maxSilent", 7200)' 'queryMetaInt("maxSilent", 21600)'
  '';
});

The first thing that comes to mind is something like this

pkgs.hydra_unstable.overrideAttrs ({ postPatch ? "", ... }: {
  postPatch = postPatch + ''
    substituteInPlace src/hydra-eval-jobs/hydra-eval-jobs.cc \
        --replace 'queryMetaInt("timeout", 36000)' 'queryMetaInt("timeout", 108000)' \
        --replace 'queryMetaInt("maxSilent", 7200)' 'queryMetaInt("maxSilent", 21600)'
  '';
});

In reply to @vcunat:matrix.org
In some use cases it might be easy to add meta attributes everywhere on the nix side.