Mike Aizatsky
Sorry for delay. Multi language support is something I wanted to add myself. I was hoping to do it similar to the way protobuf is structured, but quickly ran into...
I was able to reproduce it with `$ sudo $HOME/bin/magic-trace attach -p 1084651 -multi-thread -trigger .` Stops when running demo without args, doesn't when there's an arg. ``` $ uname...
> Does it work reliably when you attach to the tid (instead of the parent process) without using the `-multi-thread` parameter? yes, attaching to `gettid()` without `-multi-thread` seems to stop...
Just chiming in since it makes `latest` docker image completely useless.
A possible workoaround would be to use genrule directrly. This seems to work: ``` genrule( name = "generate_srcs", srcs = ["src/a/main.rs", "src/foo/mod.rs"], outs = ["main.rs", "foo/mod.rs"], cmd = """ cp...
BTW I am willing to work on a PR to fix this, but I'd like to get some approval to fix it before I go out of my way.
``` $ cat bazel-bin/src/node/node.capnp @0xbcc8f57c63814005; # generated by @workerd//build/wd_js_bundle.bzl using Modules = import "/workerd/jsg/modules.capnp"; const nodeBundle :Modules.Bundle = ( modules = [ (name = "node:_stream_duplex", src = embed "node__stream_duplex", type...
``` $ du -b bazel-out/k8-fastbuild/bin/src/node/*_cache 552 bazel-out/k8-fastbuild/bin/src/node/node_assert_cache 560 bazel-out/k8-fastbuild/bin/src/node/node_assert_strict_cache 744 bazel-out/k8-fastbuild/bin/src/node/node_async_hooks_cache 1824 bazel-out/k8-fastbuild/bin/src/node/node_buffer_cache 6424 bazel-out/k8-fastbuild/bin/src/node/node_crypto_cache 3712 bazel-out/k8-fastbuild/bin/src/node/node_diagnostics_channel_cache 456 bazel-out/k8-fastbuild/bin/src/node/node_events_cache 3248 bazel-out/k8-fastbuild/bin/src/node/node-internal_constants_cache 3264 bazel-out/k8-fastbuild/bin/src/node/node-internal_crypto_dh_cache 3328 bazel-out/k8-fastbuild/bin/src/node/node-internal_crypto_hash_cache 1960 bazel-out/k8-fastbuild/bin/src/node/node-internal_crypto_hkdf_cache 5456 bazel-out/k8-fastbuild/bin/src/node/node-internal_crypto_keys_cache 1288...
> This doesn't also enable it for consumption on load right? I think we should do it on the same PR. why? This thing is brittle so I'd like to...
Unfortunately this is not landable now: as predicted there are issues with cross-compilation downstream. I'll need to massage the run rule to support running under qemu.