wiebeytec

I run into the same issue with outlux version 0.2.0. Timescaledb version 2 uses `timescaledb_information.hypertables` and `hypertable_name`). There is a blocked pull request: https://github.com/timescale/outflux/pull/89

I wiresharked some TLS websocket traffic to a server of ours that has this issue. Ubuntu 20.04, libwebsocket 3.2.1-3, mosquitto 1.6.12, compiled ourselves, using standard Ubuntu libs. Chromium never tries...

No, just use Ubuntu 20.04, install buildessential and libsockets-dev, compile 1.6.12 and use Firefox and look in the console (CTRL-SHIFT-K). I didn't save the error messages unfortunately. There may be...

Is there a reason Mosquitto should support HTTP2 websockets? It seems like unnecessary overhead. MQTT over websocket is already packing frames in frames. With HTTP2 it's frames in frames in...

@Izerous do you have more than 30k clients? If not, you can install Nginx to proxy. You don't expose Mosquitto's websocket port, but use this example Nginx config to reach...

My `sites2023` has `require_explicit_routing: false`. But, when I'm going to need unspecified mode, I see no way but to have that `true`, I think? Because otherwise, as soon as I...

(comment edited, because I was confusing things) > I think I understand why you can't use unspecified mode. You have the same table name in legacy and in sites2023. How...

I think I have some stale information about `legacy` somewhere, I just cannot find it. It may be causing you to chase red herrings. I don't know if you think...

I figured it out: the vschema for the `legacy` needs to have *all* reference tables from from `sites2023` in it. As soon as I leave even one out, doesn't matter...

> Without adding it to the vschema how can Vitess know about a new reference table? Maybe I am misunderstanding. Can you clarify with an example what you expect to...