Loic Nageleisen
Loic Nageleisen
> Generally Standard strives not to make people type more than necessary I would argue that with this rule standard makes me type more: if I want to add a...
> from an M1 [...] Something like this, built with the `--platform linux/amd64` This only works if the Linux VM where docker is setup has `binfmt_misc` set up to run...
(reposting [my comment](https://github.com/grpc/grpc/issues/33954#issuecomment-1663968068) here for visibility) I feel like it's more than that, the gem appears to break several rubygems expectations: The gem is published as `ruby` (which means "pure...
Some additional notes: - [here's how to pick up the underlying platform triplet for JRuby](https://github.com/DataDog/libddwaf-rb/blob/913c4083ab3db2f5b755079af171ec32ba06b015/lib/datadog/appsec/waf.rb#L20-L56) - if binaries do not run on musl†, I would recommend using `*-linux-gnu` to advertise...
> The issue probably is that NixOS 24.05 ships Rust 1.77, but kernel 6.10 requires Rust 1.78 for CONFIG_RUST. Therefore, CONFIG_RUST is disabled when building the current kernel on 24.05....
@stepbrobd suggestion did not work for me, I still got `error: the user '_nixbld1' in the group 'nixbld' does not exist` even with `--option build-users-group ''`. So I just filled...
``` $ cd lib-injection/build/docker/ruby/lib_injection_rails_app $ docker run --rm -it -w $PWD -v $PWD:$PWD ghcr.io/datadog/images-rb/engines/ruby:3.0-centos /bin/bash # bundle install # bin/rails server -b 0.0.0.0 -p 5985 ``` also gave: ``` /Users/loic.nageleisen/Source/github.com/DataDog/system-tests/lib-injection/build/docker/ruby/lib_injection_rails_app/vendor/bundle/ruby/3.0.0/gems/sqlite3-1.6.0-aarch64-linux/lib/sqlite3.rb:4:in...
Now we have: ``` /bin/bash: line 1: /home/ubuntu/.rbenv/shims/rails: No such file or directory ``` Caused by: ``` Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/ubuntu/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/sqlite3-1.7.3/ext/sqlite3 /home/ubuntu/.rbenv/versions/3.0.2/bin/ruby -I...
Sure, I'll take a look.
Sure. Would it be okay to also run this on a scheduled basis? That would give us some timely-ish "it broke around that time" alerting should something change in system...