Martin

Thanks for the very quick fix! can't we add the current example above to the unit tests as a regression test, at least until a more specific way to test...

I also have the same problem: ``` [INFO] Connected to 10.144.255.236 [INFO] Detected reMarkable 2.0 [INFO] Using backend 'screenshare' [INFO] Connecting to ScreenShare, make sure you enable it [WARNING] Authenticating,...

As I can see the packets in wireshark I am certain that the network lets them through, but I will try to verify further whether the device receiving them does...

I stand corrected. I was looking for a firewall at the router side, and there is none, but there is a firewall on the target laptop and Wireshark captures in...

I am quite often frustrated by the heavy templated code which is showed off in compiler exploerer which I cannot really use without completely blowing my compile times out of...

One more complex thing one could do with the speedscope integration is also add profiling of the execution of the program, by feeding perf -> stackcollapse -> speedscope.

@bluca does anyone of the zmq team know of recently merged patched into the upstream which could fix this issue? It partially defeats the porupose to manually implement a round...

This works great for me.

we use this patch for quite a while now, can this be merged?