Matt Peterson

Added comments to 688d31c5b88f36bbcf5e0a6a772fac47bc005c19. Also, as a general implementation note, "pushing" data through `Call("func", data)` is not the best idea, because when the qml frontend restarts all that pushed data...

Whenever you save a .qml file, there is code in the loop function that shuts down and restarts the frontend. It is extremely helpful when developing the .qml code.

I think this is happening because the editor is never destroyed. I haven't done a lot of testing, but this should fix it: ``` scope.$on('$destroy', function() { acee.destroy(); }) ```

@douglasduteil So I did a bit of testing with the Firefox debug build (29.0a1 (2013-12-12)) I'm been using. The testing procedure I followed is: Create a new profile. Paste your...

Browsers don't typically offer heap size data to the running website, so something like that is going to be hard to make. It would probably have to involve a plugin/extension...

If the harvest call fails, it shouldn't use the fixed 0.2 CPU intent cost.

FWIW: I'm currently using this on an M1 Mac to successfully cross-compile linux_amd64 containers using Bazel 4.2.2

I think I'm having a similar problem, though not with rust. I'm also on `macOS Monterey 12.04 (m1)`. If you add `--toolchain_resolution_debug='rust'` to your command what output do you get?

I have a modified version of this PR that works (writes semanticdb output to bazel-bin) here: https://github.com/ThriveFinancial/rules_scala/tree/mpeterson/semanticdb

More generally, it would be really helpful if output could be targeted at anything in the layer stack. Like for example, if one stack wants to use TS_EXTRA, but wants...