2020-10-04 09:15:10 UTC - Zhenhao Li: I'm based in Europe ---- 2020-10-04 09:19:37 UTC - tuteng: I can't seem to reproduce this problem ---- 2020-10-04 09:23:07 UTC - tuteng: ---- 2020-10-04 09:24:58 UTC - tuteng: Where did you get this link address? <https://pulsar.incubator.apache.org/en/admin-rest-api/#tag/schemas> ---- 2020-10-04 09:28:58 UTC - tuteng: I found that the link here has an extra prefix of `en`, you can try <http://pulsar.apache.org/admin-rest-api/> ---- 2020-10-04 09:29:37 UTC - tuteng: <http://pulsar.apache.org/admin-rest-api/#tag/schemas> ---- 2020-10-04 11:52:46 UTC - Zhenhao Li: your link has the same issue for me. I'm using Chrome Version 85.0.4183.83 (Official Build) (64-bit) on NixOS ---- 2020-10-04 12:35:12 UTC - tuteng: My current version is 85.0.4183.121 (Official Build) (64-bit), Mac os. Thank you for your feedback, can you create an issue <https://github.com/apache/pulsar/issues>? ---- 2020-10-04 13:47:28 UTC - Allen ONeill: we have abandoned trying to use functions state - going to manage it ourselves externally instead.... ---- 2020-10-04 13:58:16 UTC - Gilles Barbier: Hi @Allen ONeill thx for feedback. Which issues have you encountered? ---- 2020-10-05 07:27:54 UTC - Łukasz Śnieżewski: Hi, I’m trying to set up Pulsar on Kubernetes using pulsar-helm-charts and I got stuck on websockets. I have set the broker variable webSocketServiceEnabled=true in the values files, and I can’t connect using websocket at pulsar-proxy’s webServicePort. I can see a 404 in the pulsar-proxy container logs. ```"GET /ws/v2/reader/persistent/test/test/test/ HTTP/1.1" 404 356 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.121 Safari/537.36" 1``` Is it possible to connect to the broker using a websocket via pulsar-proxy or I’m doing it wrong? Do I need to expose the broker service websocket port? Am I missing some additional configuration? ---- 2020-10-05 08:18:06 UTC - Michael Kux: @Michael Kux has joined the channel ----
