Stefan Sauer
Stefan Sauer
Small update - this needs a change in the protocol, so that the UI knows when the runtime is done sending data, so that the spinner can be turned off...
Protocol addition is done in https://github.com/noflo/noflo-runtime-base/commit/428191ffaafe8942aa7e0cc1a16be63ee80a71c3
I have a fix in https://github.com/ensonic/noflo-ui/commit/f38446b90d365d1a61799b67213440b9a958fe5f but struggle with the "fa-spin" class when running under chrome (41.0 ... 43.0), it works in firefox though. Seems to be an issue with...
But we do that already. Is there any (need/way) to apply scoping to the @keyframe rules? Any idea how to debug this?
Is there a script somewhere how to cleanup manually? I'd like to disable npc test-wise but like to avoid the reboots.
Thanks. Not sure what run_iptables does, but this is what I have now: ```bash #!/bin/bash # clear references for c in INPUT FORWARD; do while true; do nr=$(sudo 2>/dev/null iptables...
+1 I was looking for a way to have concurrent notes. At least those are not ambigous. Maybe the start of a line can have a small dot.
This is now 6 month later ... My report was about 2 things: 1) avoid the need to copy the header definitions 2) imho the change should not leave commented...
The last change in rules/expr.go is is this one: https://github.com/bazelbuild/bazel-gazelle/pull/818/files but I am not sure if this is responsible. It does not look like there is a fix in HEAD...
@dlech if that sound good to you, I can give it a try.