Sahin Yort
Sahin Yort
> Hi guys, I'm waiting for this feature and expecting it to be included in the next release (after @relair PR and all the discussion), angular 8 / ivy (?)....
closing this as we no longer depend on either rules_pkg or rules_python.
https://github.com/bazel-contrib/rules_oci/pull/31#discussion_r1030938473 we'll move the python bit to its own file if we can't address #381
`-I=protos` is the problem here. your imports should be relative to that. so instead of importing with`protos/first.proto` use `first.proto`.
fixed by #76
Idea; https://wapm.io/syrusakbary/jq has jq as a wasm binary and can run anywhere `wasmer` can run which is basically every nix platform plus windows. wasmer can be introduced as a toolchain...
> That sounds like a bit of overhead? I strongly agree. If we delegate "building from the source part" to the users, then it's a viable choice. I am not...
https://github.com/jqlang/jq/releases/tag/jq-1.7 is the available binaries as part of 1.7 release. i believe we are waiting for 2.0 release to make this breaking change.
the stack trace is helpful here but this is the first time I am seeing this. Probably something in bazel worker protocol has changed. I'll investigate
@matthewjh neither i was able to reproduce this or see it happen anywhere else. do you still see this issue happening?