Multiple rooms creation with same name on updating the permissions

Describe the bug
2 rooms get created when we try to change the participants' permission. It happens at very random intervals.
Server

Version: 1.4.4
Environment: Production, Ubuntu 22.04.2 LTS
Architecture: 3 AWS EC2 Instances (Behind a load balancer), each running their own Livekit node (with their own config file), connected to a common redis server, and TURN server.

Client

SDK: js
Version: 1.12.1
Framework: Next.js

To Reproduce
Steps to reproduce the behavior:

Generate a token for each participant, without the audio permission
Let the participants join a room
Hit the API <domain-name>/twirp/livekit.RoomService/UpdateParticipant to update the participant's permission and use the sample payload below:

{
         room: <room-name>,
         identity: <participant-identity>,
         permission: {
           can_publish: true,
             can_subscribe: true,
             can_publish_data: true,
             can_publish_sources: [1,2],
           },
         },

Expected behavior
Participant's permission should be updated without any new room creation
Screenshots
If applicable, could you add screenshots to help explain your problem?
Additional context
We started to face this issue when we used 2 Livekit nodes that were behind the load balancer. Earlier on one node, we didn't face any issues.
Moreover, we noticed, on random occasions, when we update the permission, the data in redis gets deleted, and Livekit creates a new room with the same name, and the new participants join the new room. The old room stays online until everyone leaves.

@heyarviind Could you share the config.yaml used? (with keys redacted)

Sure, here is the config file we are using for all the nodes

Please upload the full text file instead of a partial screenshot. I'm unable to replicate any of this from an image.

oh sorry, here is the entire file:
port: 7880

redis:
  cluster_addresses:
    - <my-redis-domian>.amazonaws.com:6379

rtc:
  port_range_start: 50000
  port_range_end: 60000
  tcp_port: 7881
  use_external_ip: true

  turn_servers:
    - host: <my-turn-server-domain>
      port: 5349
      protocol: tls
      username: "tfu"
      credential: <password>

    - host: <my-turn-server-domain>
      port: 3478
      protocol: tcp
      username: "tfu"
      credential: <password>

    - host: <my-turn-server-domain>
      port: 3478
      protocol: udp
      username: "tfu"
      credential: <password>

  congestion_control:
    enabled: true
    allow_pause: false

are you using a redis cluster? or a single redis server?

It's a cluster. Moreover, before this, we hosted redis on an EC2 instance and every node was connecting to it -- and we faced the same issue (that's why we moved to AWS redis cluster, but the error persists)

Redis cluster is unlikely to change anything.. it has more complexity instead of less.
Does this reproduce consistently? or is it random?

Updates on this issue:
We were under the impression that whenever we change the participant's permission, the second room is created and we stopped doing that and there were no issues so far.
But today, we decided to hit the livekit API to change participants' metadata and again 2 rooms got created. The admin who was using the livekit told us that he received an error but unfortunately, we were not able to capture that error.
So this is clear on our end that whenever we try to hit the livekit API, a new room gets created with the same name and old room info and everything vanishes from the redis.

I'm not able to reproduce it. Can you do the following:

List clearly the deployment setup that was used (as mentioned before, try using standard Redis instead of Redis cluster)
attach full logs from all three servers for when the issue is reproduced (logs should start before the first participant in the room has joined, until when you are seeing the "new room creation")

Earlier we were using standard redis and when this problem occurred, we thought of using AWS redis and by default it offered us a redis cluster. We can again use the standard redis but I think the issue is in both.

Deployment setup is as follows:

Created 4 ec2 instances and downloaded livekit binaries in each of them, also placed config.toml with each livekit binary.
All the config files have the same config information. (as mentioned above)
They all are pointing to the same redis cluster.
In front of these instances, I have a load balancer.

Earlier when we used a single instance, it worked great without any issue but when we installed 4 clusters and installed a load balancer the issue started happening. Do you think the load balancer might be the culprit?

Hi David, We were having 2 sessions at the same time on 4 nodes, and one of our classes with room name forex-trading-masterclass-with-muthukannan-rummwbyhv crashed 3 times. We collected relevant logs from all the servers and found out that the class got assigned 3 different nodes during the class. Also, we found one livekit error on server 04 which is mentioned below.
Please let me know if you need more information about the same.

server 01
className, Node
Vikram ND_TcWkk7sI
Muthu ND_TcWkk7sI

server 02
Vikram ND_TcWkk7sI
Muthu ND_npOHwSZo

server 04
Muthu ND_VjuIqp5u

Server 04 ----------------------------------------------

Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: 2023-09-06T12:54:03.081Z        INFO        livekit        service/roomallocator.go:131        selected node for room        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "selectedNodeID": "ND_VjuIqp5u"}
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: 2023-09-06T12:54:03.083Z        ERROR        livekit        routing/localrouter.go:107        could not handle new participant        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "participant": "clm7qqu9v0pqpmz1jcqts6mx3", "connID": "CO_Xpjt5WbMfDbk", "error": "context canceled"}
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: github.com/livekit/livekit-server/pkg/routing.(*LocalRouter).StartParticipantSignalWithNodeID
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /home/runner/go/pkg/mod/github.com/livekit/livekit-server@v1.4.5/pkg/routing/localrouter.go:107
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: github.com/livekit/livekit-server/pkg/routing.(*RedisRouter).StartParticipantSignal
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /home/runner/go/pkg/mod/github.com/livekit/livekit-server@v1.4.5/pkg/routing/redisrouter.go:167
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: github.com/livekit/livekit-server/pkg/service.(*RTCService).startConnection
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /home/runner/go/pkg/mod/github.com/livekit/livekit-server@v1.4.5/pkg/service/rtcservice.go:521
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: github.com/livekit/livekit-server/pkg/service.(*RTCService).ServeHTTP
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /home/runner/go/pkg/mod/github.com/livekit/livekit-server@v1.4.5/pkg/service/rtcservice.go:222
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: net/http.(*ServeMux).ServeHTTP
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /opt/hostedtoolcache/go/1.21.0/x64/src/net/http/server.go:2514
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: github.com/urfave/negroni/v3.(*Negroni).UseHandler.Wrap.func1
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /home/runner/go/pkg/mod/github.com/urfave/negroni/v3@v3.0.0/negroni.go:59
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: github.com/urfave/negroni/v3.HandlerFunc.ServeHTTP
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /home/runner/go/pkg/mod/github.com/urfave/negroni/v3@v3.0.0/negroni.go:33
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: github.com/urfave/negroni/v3.middleware.ServeHTTP
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /home/runner/go/pkg/mod/github.com/urfave/negroni/v3@v3.0.0/negroni.go:51
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: net/http.HandlerFunc.ServeHTTP
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /opt/hostedtoolcache/go/1.21.0/x64/src/net/http/server.go:2136
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: github.com/livekit/livekit-server/pkg/service.(*APIKeyAuthMiddleware).ServeHTTP
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /home/runner/go/pkg/mod/github.com/livekit/livekit-server@v1.4.5/pkg/service/auth.go:98
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: github.com/urfave/negroni/v3.middleware.ServeHTTP
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /home/runner/go/pkg/mod/github.com/urfave/negroni/v3@v3.0.0/negroni.go:51
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: github.com/rs/cors.(*Cors).ServeHTTP
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /home/runner/go/pkg/mod/github.com/rs/cors@v1.9.0/cors.go:271
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: github.com/urfave/negroni/v3.middleware.ServeHTTP
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /home/runner/go/pkg/mod/github.com/urfave/negroni/v3@v3.0.0/negroni.go:51
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: github.com/urfave/negroni/v3.(*Recovery).ServeHTTP
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /home/runner/go/pkg/mod/github.com/urfave/negroni/v3@v3.0.0/recovery.go:210
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: github.com/urfave/negroni/v3.middleware.ServeHTTP
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /home/runner/go/pkg/mod/github.com/urfave/negroni/v3@v3.0.0/negroni.go:51
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: github.com/urfave/negroni/v3.(*Negroni).ServeHTTP
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /home/runner/go/pkg/mod/github.com/urfave/negroni/v3@v3.0.0/negroni.go:111
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: net/http.serverHandler.ServeHTTP
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /opt/hostedtoolcache/go/1.21.0/x64/src/net/http/server.go:2938
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: net/http.(*conn).serve
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]:         /opt/hostedtoolcache/go/1.21.0/x64/src/net/http/server.go:2009
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: 2023-09-06T12:54:03.083Z        WARN        livekit        service/rtcservice.go:228        failed to start connection, retrying        {"participant": "clm7qqu9v0pqpmz1jcqts6mx3", "room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "remote": false, "attempt": 0, "error": "context canceled"}
Sep 06 12:54:03 ip-172-31-17-1 livekit-server[2162]: 2023-09-06T12:54:03.083Z        WARN        livekit        service/rtcservice.go:233        error handling request        {"participant": "clm7qqu9v0pqpmz1jcqts6mx3", "room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "remote": false, "status": 500, "error": "context canceled"}

server 03 --------------------------------------------------------------------

Sep 06 13:49:30 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:49:30.999Z        INFO        livekit        routing/signal.go:136        signal stream closed        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "reqNodeID": "ND_TcWkk7sI", "participant": "clm7siqel0vhamz1jztkefd3m", "connID": "CO_dAT2ekNZVszP", "error": "could not restart participant"}
Sep 06 13:49:31 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:49:30.999Z        WARN        livekit        service/rtcservice.go:228        failed to start connection, retrying        {"participant": "clm7siqel0vhamz1jztkefd3m", "room": "algo-trading-with-vikram-kashikar-21e0a0mow", "remote": false, "attempt": 0, "error": "connection closed by media"}
Sep 06 13:49:31 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:49:31.007Z        INFO        livekit        service/rtcservice.go:298        new client WS connected        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7siqel0vhamz1jztkefd3m", "pID": "PA_nTprWYzQrH8P", "remote": false, "connID": "CO_E2uaJc32Xj3p", "reconnect": true, "reconnectReason": "RR_SIGNAL_DISCONNECTED", "adaptiveStream": true}
Sep 06 13:49:31 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:49:31.007Z        INFO        livekit        routing/signal.go:136        signal stream closed        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "reqNodeID": "ND_TcWkk7sI", "participant": "clm7siqel0vhamz1jztkefd3m", "connID": "CO_E2uaJc32Xj3p", "error": "could not restart participant"}
Sep 06 13:49:31 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:49:31.007Z        INFO        livekit        service/rtcservice.go:323        nothing to read from response source        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7siqel0vhamz1jztkefd3m", "pID": "PA_nTprWYzQrH8P", "remote": false, "connID": "CO_E2uaJc32Xj3p"}
Sep 06 13:49:31 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:49:31.008Z        INFO        livekit        service/rtcservice.go:374        exit ws read loop for closed connection        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7siqel0vhamz1jztkefd3m", "pID": "PA_nTprWYzQrH8P", "remote": false, "connID": "CO_E2uaJc32Xj3p", "wsError": "read tcp <IP_ADDRESS>:7880-><IP_ADDRESS>:34652: use of closed network connection"}
Sep 06 13:49:31 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:49:31.008Z        INFO        livekit        service/rtcservice.go:261        finishing WS connection        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7siqel0vhamz1jztkefd3m", "pID": "PA_nTprWYzQrH8P", "remote": false, "connID": "CO_E2uaJc32Xj3p"}
Sep 06 13:49:56 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:49:56.422Z        INFO        livekit        routing/signal.go:136        signal stream closed        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "reqNodeID": "ND_KEAOPOQ5", "participant": "clm7sfssl0v7dmz1j23ynsf4w", "connID": "CO_dDnGVY5VYmJN", "error": null}
Sep 06 13:49:56 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:49:56.422Z        INFO        livekit        service/rtcservice.go:323        nothing to read from response source        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7sfssl0v7dmz1j23ynsf4w", "pID": "PA_WzZdu9gmitUw", "remote": false, "connID": "CO_dDnGVY5VYmJN"}
Sep 06 13:49:56 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:49:56.422Z        INFO        livekit        service/rtcservice.go:374        exit ws read loop for closed connection        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7sfssl0v7dmz1j23ynsf4w", "pID": "PA_WzZdu9gmitUw", "remote": false, "connID": "CO_dDnGVY5VYmJN", "wsError": "read tcp <IP_ADDRESS>:7880-><IP_ADDRESS>:55350: use of closed network connection"}
Sep 06 13:49:56 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:49:56.422Z        INFO        livekit        service/rtcservice.go:261        finishing WS connection        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7sfssl0v7dmz1j23ynsf4w", "pID": "PA_WzZdu9gmitUw", "remote": false, "connID": "CO_dDnGVY5VYmJN"}
Sep 06 13:50:06 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:06.215Z        INFO        livekit        routing/signal.go:136        signal stream closed        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "reqNodeID": "ND_TcWkk7sI", "participant": "clm7q6et90nt1mz1j4kgkn9sb", "connID": "CO_GaHnLGtpMvPb", "error": null}
Sep 06 13:50:06 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:06.215Z        INFO        livekit        service/rtcservice.go:323        nothing to read from response source        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7q6et90nt1mz1j4kgkn9sb", "pID": "PA_EVs5xjtScr2S", "remote": false, "connID": "CO_GaHnLGtpMvPb"}
Sep 06 13:50:06 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:06.215Z        INFO        livekit        service/rtcservice.go:298        new client WS connected        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7q6et90nt1mz1j4kgkn9sb", "pID": "PA_EVs5xjtScr2S", "remote": false, "connID": "CO_CsJJTWbN8G7v", "reconnect": true, "reconnectReason": "RR_UNKNOWN", "adaptiveStream": true}
Sep 06 13:50:06 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:06.215Z        INFO        livekit        service/rtcservice.go:374        exit ws read loop for closed connection        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7q6et90nt1mz1j4kgkn9sb", "pID": "PA_EVs5xjtScr2S", "remote": false, "connID": "CO_GaHnLGtpMvPb", "wsError": "read tcp <IP_ADDRESS>:7880-><IP_ADDRESS>:42964: use of closed network connection"}
Sep 06 13:50:06 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:06.215Z        INFO        livekit        service/rtcservice.go:261        finishing WS connection        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7q6et90nt1mz1j4kgkn9sb", "pID": "PA_EVs5xjtScr2S", "remote": false, "connID": "CO_GaHnLGtpMvPb"}
Sep 06 13:50:15 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:15.793Z        INFO        livekit        service/rtcservice.go:298        new client WS connected        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7smagz0vx4mz1ju43jlvvs", "pID": "PA_WJUNrY25dBNb", "remote": false, "connID": "CO_EpHVWiHjRfUK", "reconnect": false, "reconnectReason": "RR_UNKNOWN", "adaptiveStream": true}
Sep 06 13:50:31 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:31.144Z        INFO        livekit        routing/signal.go:136        signal stream closed        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "reqNodeID": "ND_KEAOPOQ5", "participant": "clm7smagz0vx4mz1ju43jlvvs", "connID": "CO_EpHVWiHjRfUK", "error": null}
Sep 06 13:50:31 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:31.144Z        INFO        livekit        service/rtcservice.go:323        nothing to read from response source        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7smagz0vx4mz1ju43jlvvs", "pID": "PA_WJUNrY25dBNb", "remote": false, "connID": "CO_EpHVWiHjRfUK"}
Sep 06 13:50:31 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:31.144Z        INFO        livekit        service/rtcservice.go:374        exit ws read loop for closed connection        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7smagz0vx4mz1ju43jlvvs", "pID": "PA_WJUNrY25dBNb", "remote": false, "connID": "CO_EpHVWiHjRfUK", "wsError": "read tcp <IP_ADDRESS>:7880-><IP_ADDRESS>:58988: use of closed network connection"}
Sep 06 13:50:31 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:31.144Z        INFO        livekit        service/rtcservice.go:261        finishing WS connection        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7smagz0vx4mz1ju43jlvvs", "pID": "PA_WJUNrY25dBNb", "remote": false, "connID": "CO_EpHVWiHjRfUK"}
Sep 06 13:50:31 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:31.145Z        INFO        livekit        routing/signal.go:136        signal stream closed        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "reqNodeID": "ND_KEAOPOQ5", "participant": "clm7sblpc0urymz1jqfszfee7", "connID": "CO_T95PxGs4ZFoB", "error": null}
Sep 06 13:50:31 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:31.145Z        INFO        livekit        service/rtcservice.go:323        nothing to read from response source        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7sblpc0urymz1jqfszfee7", "pID": "PA_L2gTgykXCrfq", "remote": false, "connID": "CO_T95PxGs4ZFoB"}
Sep 06 13:50:31 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:31.145Z        INFO        livekit        service/rtcservice.go:374        exit ws read loop for closed connection        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7sblpc0urymz1jqfszfee7", "pID": "PA_L2gTgykXCrfq", "remote": false, "connID": "CO_T95PxGs4ZFoB", "wsError": "read tcp <IP_ADDRESS>:7880-><IP_ADDRESS>:34640: use of closed network connection"}
Sep 06 13:50:31 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:31.145Z        INFO        livekit        service/rtcservice.go:261        finishing WS connection        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7sblpc0urymz1jqfszfee7", "pID": "PA_L2gTgykXCrfq", "remote": false, "connID": "CO_T95PxGs4ZFoB"}
Sep 06 13:50:33 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:33.189Z        INFO        livekit.api        service/twirp.go:128        API RoomService.DeleteRoom        {"service": "RoomService", "method": "DeleteRoom", "room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "duration": "608.026µs", "status": "404", "error": "room not found", "code": "not_found"}
Sep 06 13:50:33 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:33.673Z        INFO        livekit.room        rtc/room.go:368        new participant joined        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_hspF2qawYM5Q", "pID": "PA_RjAiVRZ2VHp9", "participant": "clm7srhu2004vmz1jdt7xvelb", "protocol": 9, "options": {"AutoSubscribe":true}}
Sep 06 13:50:33 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:33.673Z        INFO        livekit        rtc/participant.go:839        SetMigrateState        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_hspF2qawYM5Q", "participant": "clm7srhu2004vmz1jdt7xvelb", "pID": "PA_RjAiVRZ2VHp9", "remote": false, "state": "MIGRATE_STATE_COMPLETE"}
Sep 06 13:50:33 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:33.673Z        INFO        livekit.room        rtc/room.go:297        participant state changed        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_hspF2qawYM5Q", "state": "JOINED", "participant": "clm7srhu2004vmz1jdt7xvelb", "pID": "PA_RjAiVRZ2VHp9", "oldState": "JOINING"}
Sep 06 13:50:34 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:34.580Z        INFO        livekit        routing/signal.go:136        signal stream closed        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "reqNodeID": "ND_TcWkk7sI", "participant": "clm7pxnsi0mu4mz1j7et5ulr9", "connID": "CO_FzcYcux7fxDV", "error": null}
Sep 06 13:50:34 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:34.580Z        INFO        livekit        service/rtcservice.go:323        nothing to read from response source        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7pxnsi0mu4mz1j7et5ulr9", "pID": "PA_hEJvDakwuGnW", "remote": false, "connID": "CO_FzcYcux7fxDV"}
Sep 06 13:50:34 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:34.580Z        INFO        livekit        service/rtcservice.go:374        exit ws read loop for closed connection        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7pxnsi0mu4mz1j7et5ulr9", "pID": "PA_hEJvDakwuGnW", "remote": false, "connID": "CO_FzcYcux7fxDV", "wsError": "read tcp <IP_ADDRESS>:7880-><IP_ADDRESS>:33654: use of closed network connection"}
Sep 06 13:50:34 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:34.580Z        INFO        livekit        service/rtcservice.go:261        finishing WS connection        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7pxnsi0mu4mz1j7et5ulr9", "pID": "PA_hEJvDakwuGnW", "remote": false, "connID": "CO_FzcYcux7fxDV"}
Sep 06 13:50:34 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:34.874Z        INFO        livekit.transport        rtc/transport.go:626        selected ICE candidate pair        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_hspF2qawYM5Q", "participant": "clm7srhu2004vmz1jdt7xvelb", "pID": "PA_RjAiVRZ2VHp9", "remote": false, "transport": "SUBSCRIBER", "pair": "(local) udp4 host <IP_ADDRESS>:58401 <-> (remote) udp4 prflx <IP_ADDRESS>:3475 related :0"}
Sep 06 13:50:34 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:34.966Z        INFO        livekit.transport        rtc/transport.go:1582        ice candidates        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_hspF2qawYM5Q", "participant": "clm7srhu2004vmz1jdt7xvelb", "pID": "PA_RjAiVRZ2VHp9", "remote": false, "transport": "SUBSCRIBER", "lc": ["udp4 host <IP_ADDRESS>:58401", "tcp4 host <IP_ADDRESS>:7881"], "rc": ["candidate:857918100 1 udp<PHONE_NUMBER> <IP_ADDRESS> 49278 typ host generation 0 ufrag cJCs network-id 1 network-cost 10", "candidate:668767890 1 udp<PHONE_NUMBER> 2401:4900:1c2b:d63f:b1c5:5f42:6f2d:cbd6 65382 typ host generation 0 ufrag cJCs network-id 2 network-cost 10"], "lc (filtered)": [], "rc (filtered)": []}
Sep 06 13:50:35 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:35.132Z        INFO        livekit.room        rtc/room.go:297        participant state changed        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_hspF2qawYM5Q", "state": "ACTIVE", "participant": "clm7srhu2004vmz1jdt7xvelb", "pID": "PA_RjAiVRZ2VHp9", "oldState": "JOINED"}
Sep 06 13:50:38 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:38.588Z        INFO        livekit.pub        rtc/participant.go:1632        pending track added        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_hspF2qawYM5Q", "participant": "clm7srhu2004vmz1jdt7xvelb", "pID": "PA_RjAiVRZ2VHp9", "remote": false, "trackID": "TR_AM9cZM9uVH9iWw", "track": "sid:\"TR_AM9cZM9uVH9iWw\"  source:MICROPHONE  stream:\"camera\"", "request": "cid:\"40021361-8cbc-49c7-917b-af1ca3a8a060\"  source:MICROPHONE"}
Sep 06 13:50:38 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:38.897Z        INFO        livekit.transport        rtc/transport.go:626        selected ICE candidate pair        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_hspF2qawYM5Q", "participant": "clm7srhu2004vmz1jdt7xvelb", "pID": "PA_RjAiVRZ2VHp9", "remote": false, "transport": "PUBLISHER", "pair": "(local) udp4 host <IP_ADDRESS>:50687 <-> (remote) udp4 srflx <IP_ADDRESS>:14600 related <IP_ADDRESS>:56286"}
Sep 06 13:50:38 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:38.983Z        INFO        livekit.transport        rtc/transport.go:1582        ice candidates        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_hspF2qawYM5Q", "participant": "clm7srhu2004vmz1jdt7xvelb", "pID": "PA_RjAiVRZ2VHp9", "remote": false, "transport": "PUBLISHER", "lc": ["udp4 host <IP_ADDRESS>:50687", "tcp4 host <IP_ADDRESS>:7881"], "rc": ["candidate:3453218308 1 udp<PHONE_NUMBER> <IP_ADDRESS> 56286 typ host generation 0 ufrag 45gE network-id 1 network-cost 10", "candidate:614774125 1 udp<PHONE_NUMBER> 2401:4900:1c2b:d63f:b1c5:5f42:6f2d:cbd6 50915 typ host generation 0 ufrag 45gE network-id 2 network-cost 10", "candidate:3453218308 1 udp<PHONE_NUMBER> <IP_ADDRESS> 56150 typ host generation 0 ufrag 45gE network-id 1 network-cost 10", "candidate:614774125 1 udp<PHONE_NUMBER> 2401:4900:1c2b:d63f:b1c5:5f42:6f2d:cbd6 63435 typ host generation 0 ufrag 45gE network-id 2 network-cost 10", "candidate:3436420130 1 udp<PHONE_NUMBER> <IP_ADDRESS> 14600 typ srflx raddr <IP_ADDRESS> rport 56286 generation 0 ufrag 45gE network-id 1 network-cost 10", "candidate:3436420130 1 udp<PHONE_NUMBER> <IP_ADDRESS> 5755 typ srflx raddr <IP_ADDRESS> rport 56150 generation 0 ufrag 45gE network-id 1 network-cost 10"], "lc (filtered)": [], "rc (filtered)": []}
Sep 06 13:50:39 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:39.010Z        INFO        livekit.pub        rtc/participant.go:1300        mediaTrack published        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_hspF2qawYM5Q", "participant": "clm7srhu2004vmz1jdt7xvelb", "pID": "PA_RjAiVRZ2VHp9", "remote": false, "kind": "audio", "trackID": "TR_AM9cZM9uVH9iWw", "webrtcTrackID": "40021361-8cbc-49c7-917b-af1ca3a8a060", "rid": "", "SSRC":<PHONE_NUMBER>, "mime": "audio/red"}
Sep 06 13:50:40 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:40.968Z        INFO        livekit.pub        rtc/participant.go:1632        pending track added        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_hspF2qawYM5Q", "participant": "clm7srhu2004vmz1jdt7xvelb", "pID": "PA_RjAiVRZ2VHp9", "remote": false, "trackID": "TR_VCYQaFH7ZQAHkB", "track": "sid:\"TR_VCYQaFH7ZQAHkB\"  type:VIDEO  width:1280  height:720  source:CAMERA  layers:{quality:HIGH  width:1280  height:720  bitrate:1500000}  codecs:{mime_type:\"video/vp8\"  cid:\"5e2a103f-c150-4f96-93e4-230424da34a3\"}  stream:\"camera\"", "request": "cid:\"5e2a103f-c150-4f96-93e4-230424da34a3\"  type:VIDEO  width:1280  height:720  source:CAMERA  layers:{quality:HIGH  width:1280  height:720  bitrate:1500000}  simulcast_codecs:{codec:\"vp8\"  cid:\"5e2a103f-c150-4f96-93e4-230424da34a3\"}"}
Sep 06 13:50:41 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:41.506Z        INFO        livekit.pub        rtc/participant.go:1300        mediaTrack published        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_hspF2qawYM5Q", "participant": "clm7srhu2004vmz1jdt7xvelb", "pID": "PA_RjAiVRZ2VHp9", "remote": false, "kind": "video", "trackID": "TR_VCYQaFH7ZQAHkB", "webrtcTrackID": "5e2a103f-c150-4f96-93e4-230424da34a3", "rid": "", "SSRC": 624990329, "mime": "video/VP8"}
Sep 06 13:50:46 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:46.924Z        INFO        livekit        service/rtcservice.go:298        new client WS connected        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7p1x6n0k9hmz1j0hm0de8t", "pID": "PA_KhYd24WcPHnE", "remote": false, "connID": "CO_8XSFL43MpL6w", "reconnect": true, "reconnectReason": "RR_SIGNAL_DISCONNECTED", "adaptiveStream": true}
Sep 06 13:50:49 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:49.932Z        INFO        livekit        service/rtcservice.go:298        new client WS connected        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7rotdg0slxmz1jfd8s89wt", "pID": "PA_3FtdEaeLdaGB", "remote": false, "connID": "CO_NrghbCJSZEpe", "reconnect": false, "reconnectReason": "RR_UNKNOWN", "adaptiveStream": true}
Sep 06 13:50:51 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:50:51.507Z        INFO        livekit.pub        rtc/participant.go:1556        sending max subscribed quality        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_hspF2qawYM5Q", "participant": "clm7srhu2004vmz1jdt7xvelb", "pID": "PA_RjAiVRZ2VHp9", "remote": false, "trackID": "TR_VCYQaFH7ZQAHkB", "qualities": [{"codec":"vp8","qualities":[{},{"quality":1},{"quality":2}]}], "max": [{"CodecMime":"video/VP8","Quality":3}]}
Sep 06 13:51:06 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:51:06.922Z        INFO        livekit        routing/signal.go:136        signal stream closed        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "reqNodeID": "ND_TcWkk7sI", "participant": "clm7rotdg0slxmz1jfd8s89wt", "connID": "CO_NrghbCJSZEpe", "error": null}
Sep 06 13:51:06 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:51:06.922Z        INFO        livekit        service/rtcservice.go:323        nothing to read from response source        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7rotdg0slxmz1jfd8s89wt", "pID": "PA_3FtdEaeLdaGB", "remote": false, "connID": "CO_NrghbCJSZEpe"}
Sep 06 13:51:06 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:51:06.922Z        INFO        livekit        service/rtcservice.go:374        exit ws read loop for closed connection        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7rotdg0slxmz1jfd8s89wt", "pID": "PA_3FtdEaeLdaGB", "remote": false, "connID": "CO_NrghbCJSZEpe", "wsError": "read tcp <IP_ADDRESS>:7880-><IP_ADDRESS>:36986: use of closed network connection"}
Sep 06 13:51:06 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:51:06.922Z        INFO        livekit        service/rtcservice.go:261        finishing WS connection        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7rotdg0slxmz1jfd8s89wt", "pID": "PA_3FtdEaeLdaGB", "remote": false, "connID": "CO_NrghbCJSZEpe"}
Sep 06 13:51:23 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:51:23.304Z        INFO        livekit        service/roomallocator.go:131        selected node for room        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "selectedNodeID": "ND_TcWkk7sI"}
Sep 06 13:51:23 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:51:23.312Z        INFO        livekit        service/rtcservice.go:298        new client WS connected        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7s59sb0u6imz1jg4u9pyvu", "pID": "PA_MhVhLDfVCQ4F", "remote": false, "connID": "CO_Be3rQBtNRhXk", "reconnect": false, "reconnectReason": "RR_UNKNOWN", "adaptiveStream": true}
Sep 06 13:51:28 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:51:28.714Z        INFO        livekit        service/rtcservice.go:298        new client WS connected        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7sdsls0v0smz1jmq8wbrux", "pID": "PA_KYdt9ooY5Dah", "remote": false, "connID": "CO_XeK9fePw9DUf", "reconnect": false, "reconnectReason": "RR_UNKNOWN", "adaptiveStream": true}
Sep 06 13:51:33 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:51:33.413Z        INFO        livekit        service/rtcservice.go:374        exit ws read loop for closed connection        {"room": "masterclass-on-monthly-income-strategy-by-tarun-sebi-registered-rsymt25b7", "roomID": "RM_ZYZrW77chFhr", "participant": "clm7rjd6j0s6emz1jya062fmt", "pID": "PA_DzBqPv3heYy9", "remote": false, "connID": "CO_T2e6YCEUBuXF", "wsError": "websocket: close 1006 (abnormal closure): unexpected EOF"}
Sep 06 13:51:33 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:51:33.414Z        INFO        livekit        service/rtcservice.go:261        finishing WS connection        {"room": "masterclass-on-monthly-income-strategy-by-tarun-sebi-registered-rsymt25b7", "roomID": "RM_ZYZrW77chFhr", "participant": "clm7rjd6j0s6emz1jya062fmt", "pID": "PA_DzBqPv3heYy9", "remote": false, "connID": "CO_T2e6YCEUBuXF"}
Sep 06 13:51:33 ip-172-31-8-134 livekit-server[1587]: 2023-09-06T13:51:33.414Z        INFO        livekit        service/rtcservice.go:323        nothing to read from response source        {"room": "masterclass-on-monthly-income-strategy-by-tarun-sebi-registered-rsymt25b7", "roomID": "RM_ZYZrW77chFhr", "participant": "clm7rjd6j0s6emz1jya062fmt", "pID": "PA_DzBqPv3heYy9", "remote": false, "connID": "CO_T2e6YCEUBuXF"}
Sep 06 13:51:33 ip-172-31-8-134 livekit-server

server 02 -----------------------------------------------------------------

Sep 06 13:39:34 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:34.363Z        INFO        livekit        routing/signal.go:136        signal stream closed        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "reqNodeID": "ND_TcWkk7sI", "participant": "clm7ryx1x0tgemz1jjfcpr4qy", "connID": "CO_AcWd2HJPhxSR", "error": "could not restart participant"}
Sep 06 13:39:34 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:34.363Z        WARN        livekit        service/rtcservice.go:233        error handling request        {"participant": "clm7ryx1x0tgemz1jjfcpr4qy", "room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "remote": false, "status": 500, "error": "connection closed by media"}
Sep 06 13:39:34 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:34.642Z        INFO        livekit        routing/signal.go:136        signal stream closed        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "reqNodeID": "ND_TcWkk7sI", "participant": "clm7s8lbd0uiemz1jpb4cixeb", "connID": "CO_jBdUPRkKML7V", "error": "could not restart participant"}
Sep 06 13:39:34 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:34.642Z        WARN        livekit        service/rtcservice.go:228        failed to start connection, retrying        {"participant": "clm7s8lbd0uiemz1jpb4cixeb", "room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "remote": false, "attempt": 0, "error": "connection closed by media"}
Sep 06 13:39:34 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:34.649Z        INFO        livekit        routing/signal.go:136        signal stream closed        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "reqNodeID": "ND_TcWkk7sI", "participant": "clm7s8lbd0uiemz1jpb4cixeb", "connID": "CO_8dbtowySnEJ2", "error": "could not restart participant"}
Sep 06 13:39:34 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:34.649Z        WARN        livekit        service/rtcservice.go:228        failed to start connection, retrying        {"participant": "clm7s8lbd0uiemz1jpb4cixeb", "room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "remote": false, "attempt": 1, "error": "connection closed by media"}
Sep 06 13:39:34 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:34.657Z        INFO        livekit        routing/signal.go:136        signal stream closed        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "reqNodeID": "ND_TcWkk7sI", "participant": "clm7s8lbd0uiemz1jpb4cixeb", "connID": "CO_ctL4Zh8Mojpe", "error": "could not restart participant"}
Sep 06 13:39:34 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:34.657Z        WARN        livekit        service/rtcservice.go:233        error handling request        {"participant": "clm7s8lbd0uiemz1jpb4cixeb", "room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "remote": false, "status": 500, "error": "connection closed by media"}
Sep 06 13:39:35 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:35.526Z        INFO        livekit.room        rtc/room.go:695        closing room        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m"}
Sep 06 13:39:35 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:35.527Z        INFO        livekit        service/roommanager.go:128        deleting room state        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv"}
Sep 06 13:39:35 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:35.528Z        INFO        livekit.room        service/roommanager.go:501        room closed        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m"}
Sep 06 13:39:37 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:37.012Z        INFO        livekit        service/roomallocator.go:131        selected node for room        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_FNxEz9PamNUm", "selectedNodeID": "ND_npOHwSZo"}
Sep 06 13:39:37 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:37.019Z        INFO        livekit        service/rtcservice.go:298        new client WS connected        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_FNxEz9PamNUm", "participant": "clm7sa07q0umjmz1j73xg4j8m", "pID": "PA_c9DT8vuxW93i", "remote": false, "connID": "CO_GWHGktn2y9cq", "reconnect": true, "reconnectReason": "RR_SUBSCRIBER_FAILED", "adaptiveStream": true}
Sep 06 13:39:37 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:37.019Z        INFO        livekit        routing/signal.go:136        signal stream closed        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "reqNodeID": "ND_npOHwSZo", "participant": "clm7sa07q0umjmz1j73xg4j8m", "connID": "CO_GWHGktn2y9cq", "error": "could not restart participant"}
Sep 06 13:39:37 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:37.019Z        INFO        livekit        service/rtcservice.go:323        nothing to read from response source        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_FNxEz9PamNUm", "participant": "clm7sa07q0umjmz1j73xg4j8m", "pID": "PA_c9DT8vuxW93i", "remote": false, "connID": "CO_GWHGktn2y9cq"}
Sep 06 13:39:37 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:37.019Z        INFO        livekit        service/rtcservice.go:374        exit ws read loop for closed connection        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_FNxEz9PamNUm", "participant": "clm7sa07q0umjmz1j73xg4j8m", "pID": "PA_c9DT8vuxW93i", "remote": false, "connID": "CO_GWHGktn2y9cq", "wsError": "read tcp <IP_ADDRESS>:7880-><IP_ADDRESS>:47988: use of closed network connection"}
Sep 06 13:39:37 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:37.019Z        INFO        livekit        service/rtcservice.go:261        finishing WS connection        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_FNxEz9PamNUm", "participant": "clm7sa07q0umjmz1j73xg4j8m", "pID": "PA_c9DT8vuxW93i", "remote": false, "connID": "CO_GWHGktn2y9cq"}
Sep 06 13:39:37 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:37.854Z        INFO        livekit        routing/signal.go:136        signal stream closed        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "reqNodeID": "ND_TcWkk7sI", "participant": "clm7s1lwv0trpmz1j6to13dxs", "connID": "CO_fdAVmXvMhrMc", "error": null}
Sep 06 13:39:37 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:37.854Z        INFO        livekit        service/rtcservice.go:323        nothing to read from response source        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7s1lwv0trpmz1j6to13dxs", "pID": "PA_juMQXuohjdQ4", "remote": false, "connID": "CO_fdAVmXvMhrMc"}
Sep 06 13:39:37 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:37.854Z        INFO        livekit        service/rtcservice.go:374        exit ws read loop for closed connection        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7s1lwv0trpmz1j6to13dxs", "pID": "PA_juMQXuohjdQ4", "remote": false, "connID": "CO_fdAVmXvMhrMc", "wsError": "read tcp <IP_ADDRESS>:7880-><IP_ADDRESS>:55024: use of closed network connection"}
Sep 06 13:39:37 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:37.854Z        INFO        livekit        service/rtcservice.go:261        finishing WS connection        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7s1lwv0trpmz1j6to13dxs", "pID": "PA_juMQXuohjdQ4", "remote": false, "connID": "CO_fdAVmXvMhrMc"}
Sep 06 13:39:38 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:38.583Z        INFO        livekit        service/rtcservice.go:298        new client WS connected        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7s6tqb0uckmz1j4rt1fhsk", "pID": "PA_8GYzHv5zCCzr", "remote": false, "connID": "CO_kpVcQ9o4dNFh", "reconnect": false, "reconnectReason": "RR_UNKNOWN", "adaptiveStream": true}
Sep 06 13:39:39 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:39.411Z        INFO        livekit        service/rtcservice.go:374        exit ws read loop for closed connection        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7rbsbl0rgtmz1jfz7nfv38", "pID": "PA_FKqDArtxhiTg", "remote": false, "connID": "CO_GGQVBpqtJBVo", "wsError": "websocket: close 1006 (abnormal closure): unexpected EOF"}
Sep 06 13:39:39 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:39.411Z        INFO        livekit        service/rtcservice.go:261        finishing WS connection        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7rbsbl0rgtmz1jfz7nfv38", "pID": "PA_FKqDArtxhiTg", "remote": false, "connID": "CO_GGQVBpqtJBVo"}
Sep 06 13:39:39 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:39.411Z        INFO        livekit        service/rtcservice.go:323        nothing to read from response source        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "roomID": "RM_9RZRDwyyusyY", "participant": "clm7rbsbl0rgtmz1jfz7nfv38", "pID": "PA_FKqDArtxhiTg", "remote": false, "connID": "CO_GGQVBpqtJBVo"}
Sep 06 13:39:39 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:39.413Z        INFO        livekit        routing/signal.go:136        signal stream closed        {"room": "algo-trading-with-vikram-kashikar-21e0a0mow", "reqNodeID": "ND_TcWkk7sI", "participant": "clm7rbsbl0rgtmz1jfz7nfv38", "connID": "CO_GGQVBpqtJBVo", "error": "stream closed"}
Sep 06 13:39:41 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:41.200Z        INFO        livekit        service/rtcservice.go:374        exit ws read loop for closed connection        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7s6tqb0uckmz1j4rt1fhsk", "pID": "PA_8GYzHv5zCCzr", "remote": false, "connID": "CO_kpVcQ9o4dNFh", "wsError": "websocket: close 1005 (no status)"}
Sep 06 13:39:41 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:41.200Z        INFO        livekit        service/rtcservice.go:261        finishing WS connection        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7s6tqb0uckmz1j4rt1fhsk", "pID": "PA_8GYzHv5zCCzr", "remote": false, "connID": "CO_kpVcQ9o4dNFh"}
Sep 06 13:39:41 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:41.200Z        INFO        livekit        service/rtcservice.go:323        nothing to read from response source        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_bE45CHEtsG9m", "participant": "clm7s6tqb0uckmz1j4rt1fhsk", "pID": "PA_8GYzHv5zCCzr", "remote": false, "connID": "CO_kpVcQ9o4dNFh"}
Sep 06 13:39:41 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:41.201Z        INFO        livekit        routing/signal.go:136        signal stream closed        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "reqNodeID": "ND_npOHwSZo", "participant": "clm7s6tqb0uckmz1j4rt1fhsk", "connID": "CO_kpVcQ9o4dNFh", "error": "stream closed"}
Sep 06 13:39:41 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:41.750Z        INFO        livekit        service/rtcservice.go:298        new client WS connected        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_FNxEz9PamNUm", "participant": "clm7s6tqb0uckmz1j4rt1fhsk", "pID": "PA_d6MmMznYi6HT", "remote": false, "connID": "CO_LGa6NnDyU5FD", "reconnect": false, "reconnectReason": "RR_UNKNOWN", "adaptiveStream": true}
Sep 06 13:39:42 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:42.248Z        INFO        livekit        service/rtcservice.go:374        exit ws read loop for closed connection        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_FNxEz9PamNUm", "participant": "clm7s6tqb0uckmz1j4rt1fhsk", "pID": "PA_d6MmMznYi6HT", "remote": false, "connID": "CO_LGa6NnDyU5FD", "wsError": "websocket: close 1005 (no status)"}
Sep 06 13:39:42 ip-172-31-26-218 livekit-server[1450]: 2023-09-06T13:39:42.248Z        INFO        livekit        service/rtcservice.go:261        finishing WS connection        {"room": "forex-trading-masterclass-with-muthukannan-rummwbyhv", "roomID": "RM_FNxEz9PamNUm", "participant": "clm7s6tqb0uckmz1j4rt1fhsk", "pID": "PA_d6MmMznYi6HT", "remote": false, "connID": "CO_LGa6NnDyU5FD"}
Sep 06 13:39:42 ip-172-31-26-218

Today we had 4 sessions on 4 Livekit servers and one room crashed and created a new room. Today also we saw the same behavior in logs as shown in the logs.
Moreover, we also got a notification during the class (when a new room got created) that our Livekit server crashed. (attached screenshot for the same as well)

From your logs, you can see that the rooms kept on getting deleted via API. The log you've highlighted deleting room is only logged when RoomService.DeleteRoom is called.
There are no crashes happening.


[Lake] Disable primary key lake table

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

[FE PR Coverage Check]
:heart_eyes: pass : 2 / 2 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/analyzer/CreateTableAnalyzer.java
2
2
100.00%
[]


[BUG] , There is an (explanatory video.) The session error appears to the client and does not appear on the site.

"The issue, in brief, is that the client scans the QR code. It shows as active on the phone but doesn't appear on the website. Then the usual error appears where the QR code is located."
video
https://youtu.be/5-pAqilEsRk
Can anyone help me solve the problem?
Thank you very much in advance and for your patience

Same error occurred here..

Guess it's a problem in your code rather than Bailey

Some day ago the code are working fine. then this issue are facing many developers then i think WhatsApp release measure changes.

Someone got fix it in Waziper?

Yes.

Try Bailyes 6.7.8 or try with timeout (#3 param) in ppurl, ie: profilePictureUrl(<your_whatsapp_user_id>, 'preview', 3000);

Someone got fix it in Waziper?

Yes.

Can you share?

Someone got fix it in Waziper?

Yes.


BASWARE - None of the job types displayed match the job types from the company's website

ENVIRONMENT: production
URL: https://peviitor.ro
Browser: Chrome
Version: 120
Device: Laptop
OS: Windows 10
STEPS TO REPRODUCE:

Open the url
Click on "run scraper"
See the displayed job types: "on-site"
Click on "vezi postul" for each job displayed
See the job type from the official company website: "hybrid"

EXPECTED RESULTS:
The job types from scrapers.peviitor.ro match the job types from the company's website.
ACTUAL RESULTS:
The job types from scrapers.peviitor.ro don't  match the job types from the company's website.
Attachments:

fixed can you retest?


Expected Behavior

Your Environment
snarkOS Version: cf83035ab79907329208a7f4e35d77e8e49d0596

If a BlockRequest times out because of being obsolete, that means the node has already moved past that block height, and it's correct to remove it from requests and request_timestamps. If a BlockResponse still comes in for that block, indeed all requests to that peer are removed (spam protection). This can happen if the blocks are very big, deserialization takes too long and the request is re-sent. Not sure what could be done except trying to make deserialization faster, but it's slow because of the heavy crypto involved.

If a BlockRequest times out because of being obsolete, that means the node has already moved past that block height, and it's correct to remove it from requests and request_timestamps. If a BlockResponse still comes in for that block, indeed all requests to that peer are removed (spam protection). This can happen if the blocks are very big, deserialization takes too long and the request is re-sent. Not sure what could be done except trying to make deserialization faster, but it's slow because of the heavy crypto involved.

I will add more logs later.
Yes, it can be confirmed that the deserialization took too long and the synchronization logic did not process the BlockResponse that had arrived in time. And because the synchronization logic (remove_block_response) and the request logic (check_block_request) were executed concurrently, the BlockRequest was resent.
This caused a race condition in the synchronization of subsequent blocks, that is, requests were cleared because they could not be found in the synchronization pool, and at the same time try_advance_next updated requests and requested blocks from the peer.
This made the synchronization process of the node inefficient and uncertain.

I have two questions:

Will the chain reaction continue without malicious behavior?
If a node maliciously sends BlockResponse of any height, will it make the synchronization logic get stuck?

we've changed the liveness heartbeat of the peer to be reset on any message from the peer, and together with the async deser and handling of the BlockResponses the node should eventually be able to continue, though too much data could be requested and discarded
I don't think so as only requests from that specific peer will be removed

we've changed the liveness heartbeat of the peer to be reset on any message from the peer, and together with the async deser and handling of the BlockResponses the node should eventually be able to continue, though too much data could be requested and discarded
I don't think so as only requests from that specific peer will be removed

I tested:

Confirmed that the chain reaction would not last forever
The synchronization logic would not get stuck even if attacked

Thank you for your patient reply.


Bad URL for Docker Enterprise Basic Edition at Windows containers and Windows Server 2016 section

Problem description
There is a died URL for Docker Enterprise Basic Edition at Windows containers and Windows Server 2016

Problem location

I saw a problem on the following URL: https://docs.docker.com/docker-for-windows/troubleshoot/#windows-containers-and-windows-server-2016

I couldn't find the information I wanted. I expected to find it near the following URL: https://docs.docker.com/ee/index

Other:

Project version(s) affected
Suggestions for a fix

This has been fixed via #8470


Rename contest leaderboard to score leaderboard

Description
This pull request changes the name of the contest leaderboard tabs and relevant strings to "Score Leaderboard." This is done in preparation for adding a new popular votes leaderboard and differentiating it from the usual contest leaderboard.
Type of change

[x] Rename contest leaderboard to score leaderboard
[x] Update snapshots

Checklist

[x] I have tested this code

Blocked by WIP corresponding backend PR.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 37.196%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5723

Relevant Lines:
14462

💛  - Coveralls

Corresponding backend PR: https://github.com/source-academy/backend/pull/1064


issue-3260: Clarify a few points on Development Documentation.

What type of PR is this?
/kind documentation
What this PR does / why we need it:
As a new contributor, I reviewed the Dev Guide and would like to clarify a few points I encountered while following it. I've made some structural adjustments and added a few pieces of content. I know that this may have some personal opinions, so I'm open to any feedback or comments.
Which issue(s) this PR fixes:
Fixes #3260
Does this PR introduce a user-facing change?:
NONE
Read the latest Documentation at here.

/ok-to-test
/approve
Thanks @jgao1025, this is great stuff.

This is really great, thanks @jgao1025!
/lgtm


Where does beta come from?

Where does the beta value of 0.015 come from? Is that based on literature or a fit? How does it compare to the beta in SIR models?
In the parameters.py file beta is:
[line 40]  pars['beta']         = 0.015 # Beta per symptomatic contact; absolute
To interpret model behavior, some sort of explanation is needed.

Thanks @wpettine -- we are working on writing a paper with the full Covasim methodology. We are as you can imagine completely snowed under with other requests, but we will release it as soon as possible.

Closing for now @wpettine, since this will be addressed in the forthcoming paper.


Add content about back to basis on HTTP

Read this to see what I mean :)

Great point, and yes definitely a topic to cover :)


README is out of date

The README references sequenceTubeMap.js, but this appears to have been moved/renamed (to app/main.js?).

Thanks, you're right. I have been refactoring things and ported the code to ES6. I'd be surprised if that is the only inaccuracy in the readme atm. I'll have a look at it.


Arrow keys don't work in pew shell on Windows

In the normal CMD shell, usually you can hit 'up arrow' to get your previous command. Once you run 'pew in ' , this no longer works.
if you run some commands inside the 'pew in' shell and then hit 'up' it does nothing.
It does work in 'ConEmu', so whatever they are doing in ConEmu to fix this might be useful to pew.

I'm gonna try and tackle this this week

Looks like this is a bug in virtualenv reported.  See ticket #165


Mapbox satellite images won't display using MapboxVectorLayer

Describe the bug
Using a satellite-street style from Mapbox, I can see streets, but I can't see the satellite images.
To Reproduce
Use this map object:
let map =  new Map({
  target: 'map',
  layers: [
    new MapboxVectorLayer({
      styleUrl: 'mapbox://styles/mapbox/satellite-streets-v10',
      accessToken: 'my-mapbox-key',
    }),

  ],
  view: new View({
    center: fromLonLat([4.42, 45,4804]),
    zoom: 7
  })
});

Expected behavior
The map should show streets on top of satellite images.

As documented, MapboxVectorLayer only works with a single vector source. If you want to display everything that's in the satellite-streets-v10 style, use ol-mapbox-style:
import olms from 'ol-mapbox-style';
olms('map', 'https://api.mapbox.com/styles/v1/mapbox/satellite-streets-v10?access_token=my-mapbox-key');

Thanks for your answer & solution, sorry for having misread the documentation.


LDAPAdmin: delete key gives Invalid key index: 2!

key indexing issue.

Fixed key handling. Delete options now take either key index as shown in --list  --details (-L <user -v), path to pubkey, public key data (with or without prefix/comment fields) or key hash (:).


fused operator splitting issue

After reviewing the runtime logs, I observed that the fused operator 'flash attention' is also split. Since 'flash attention' involves CUDA kernels, I wonder if splitting this operator could affect its runtime efficiency？Is it possible that the performance of flash attention becomes worse after splitting ？

Assume the example you run is llama3_8B_128K.
In this example, flash attention is registered with annotation b l^ (group_num 4) hd^, b s^ group_num hd^, b s^ (group_num 4) vd^ -> b l^ (group_num 4) vd^ to nnscaler.
This annotation denotes that flash-attention can be split along batch dim b and head group dim group_num.
After the computation graph has been built, nnscaler's plan searcher AutoDist will profile all the possible partition of the flash-attn. For example, if there are 4 devices, and the input shape of q, k, v is [4, 2048, 32, 128], [4, 2048, 8, 128] and [4, 2048, 8, 128], AutoDist will profile the operator with initial shape and with 2 partitioned shapes ([4, 2048, 8, 128], [4, 2048, 2, 128], [4, 2048, 2, 128]) and ([1, 2048, 32, 128], [1, 2048, 8, 128], [1, 2048, 8, 128]). After that, it will determine the partition by solving a global optimization problem which considers profile numbers of each (partitioned) operator and communication cost.
In conclusion, if the input shape is sufficiently large for flash-attn (for example, the sequence length is 128K), the MFU of the initial operator and partitioned one should be close since the GPU has be saturated by the computation. If the input shape is small, the MFU of the partitioned flash-attn may be lower, however

autodist may not partition the operator based on the profile data
although the MFU is lower, but the end2end training speed is faster, and autodist will partition the operator as well

I see，thank you for your explanation~


binder_linux module not found.

Hi! How to add binder_linux module in this kernel?
# modprobe binder_linux
modprobe: FATAL: Module binder_linux not found in directory /lib/modules/6.2.7-060207-generic

The Ubuntu mainline kernel has Android IPC disabled in v6.1 through v6.2.8 see https://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack/tree/debian.master/config/annotations?h=cod/mainline/v6.2.8#n1102
I don't why they changed this, but you can you reenable it if you build the kernel yourself and use the --custom=yes flag. Then in makemenuconfig search for android and enable Android IPC
You could open a bug against the linux package on launchpad and ask them to re-enable Android IPC. It looks like this has been a problem in the past too, see this ancient launchpad bug

Is it possible to build this kernel with a docker image?


When I re-enable an installed Satcom, the poast button does not show until chrome browser restart

what happens
As someone who has Satcom chrome extension installed, and has it disabled, when I re-enable the extension satcom appears in my extension icon group (top right of browser). However, the satcom see comments & poast button (bottom right) is not visible until I restart chrome browser.
suggestion
Poast button should show immediately without chrome browser restart.

poast button

just to clarify, it does not have to "restart" to show the icon button on the website right? simply a page refresh will do.
the problem is that, the script is injected onto the site on page load, the only way to "show automatically" is somehow to trigger a page load. not sure if this is desired.

just to clarify, it does not have to "restart" to show the icon button on the website right? simply a page refresh will do.

Confirmed. Correct.

the only way to "show automatically" is somehow to trigger a page load. not sure if this is desired.

Probably you are correct. Can you trigger a toast, notification, or similar that states "refresh the page in order to enable Satcom"


Bottom bar too crazy

It's huge (tall and wide) and covers the left sidebar. Most themes make it really small. Is there any way to adjust that?
It goes away when I zoom way out of the interface with ctrl+-, but takes over completely when you zoom in a bit.

send screen shot then i will understand your problem and send other theme screen shot for comparison

i don't have botton panel i have windows and linux but i don't see bottom panel
will you tell me how to activate?
after that i can fix it

i use less plugin that why my bottom bar is not messy
anyway give you plugin list name so that i will install and test on this theme to fix your issue

.status-bar {
  font-size: var(--status-bar-font-size);
}

save the above text into folder .obsdian/snippets as bottom.css or any name, it will make status bar default or small
this is temporary solution
for permanent solution you need to provide all plugin you install after that i can test and try to fix

I mean clearly the bar is wide because I have a lot of plugins, and clearly removing a few plugins that use that bar will make it smaller. I don't think it's necessary to give you a full list of plugins I use to troubleshoot.
The status-bar fix should work just fine.
I do feel a little bit silly knowing that I probably could have just used the dev tools to figure out how to modify it.
Anyways thank you very much now I get to enjoy this beautiful theme!!!


Assignment Close Immediately

Currently assignments close at a deadline. However, it will be a nice for the professor to have the ability to close the assignment immediately. This will be helpful in a test like environment, where the official time is 1 hour, but the professor has set deadline as 1.5 hours (for margin). But once he is convinced everyone is done, he can close it manually himself.
I would like a button which says "Close now"
Are you working on this? (Yes/No)
No

I would like to work on this issue

Go ahead @jayantchaudhary002

Working on it @satu0king

Is this issue still open, I would like to work on it.

@satu0king Do let me know if this issue is still open. I'm highly interested to work on this issue.

Has there been any developement regarding this issue? If not I would like to take it up @satu0king . Kindly let me know.

@satu0king @tachyons can we add this under good first issues?

Hey @satu0king @ShreyaPrasad1209 ,
Is anyone working on this?
If not Please assign me this issue and please help me out with some code pointers/references from where I can start digging into it.


Broken Clang on MacOS (nix-darwin)

Describe the bug
Trying to compile a simple hello.cpp program is failing, because of c++abi not found.
To reproduce
I'm actually using a flake
{
  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
    systems.url = "github:nix-systems/default";
    devenv.url = "github:cachix/devenv";
  };

  outputs = {
    self,
    nixpkgs,
    devenv,
    systems,
    ...
  } @ inputs: let
    forEachSystem = nixpkgs.lib.genAttrs (import systems);
  in {
    devShells =
      forEachSystem
      (system: let
        pkgs = nixpkgs.legacyPackages.${system};
      in {
        # ----------------------------------------------------
        default = pkgs.mkShell {
          buildInputs = with pkgs; [clang];
        };
        # ----------------------------------------------------
        # default = devenv.lib.mkShell {
        #   inherit inputs pkgs;
        #
        #   modules = [
        #     {
        #       packages = with pkgs; [clang];
        #     }
        #   ];
        # };
        # ----------------------------------------------------
        # default = devenv.lib.mkShell {
        #   inherit inputs pkgs;
        #
        #   modules = [
        #     {
        #       languages.cplusplus.enable = true;
        #     }
        #   ];
        # };
        # ----------------------------------------------------
      });
  };

  nixConfig = {
    extra-trusted-public-keys = "devenv.cachix.org-1:w1cLUi8dv3hnoSPGAuibQv+f9TZLr6cv/Hm9XgU50cw=";
    extra-substituters = "https://devenv.cachix.org";
  };
}

I defined three shells (uncommenting each one of the subdivided sections), and run
nix develop --impure
clang++ hello.cpp

with the customary hello.cpp:
#include <iostream>

int main() {
    std::cout << "Hello World!";
    return 0;
}

In the first case (no devenv) everything works smoothly (even without --impure, of course), and running ./a.out I obtain the usual Hello, World! output.
In the other two cases, I'm unable to compile. The result is:
❯ nix develop --impure
(devenv) bash-5.2$ clang++ hello.cpp
ld: warning: directory not found for option '-L/nix/store/qfdj687ndydj5mfd60y5ip43d1jgqb6j-devenv-profile/lib'
ld: library not found for -lc++abi
clang-16: error: linker command failed with exit code 1 (use -v to see invocation)

(the hash may change, I tried with multiple versions of nixpkgs, including nixos-23.11 and `nixpkgs-23.11-darwin, on top of the two options in the flake)
I'm not sure what is actually happening...
Version
I attach the whole flake.lock.
flake.zip
I'm on MacOS, with ARM architecture (Apple Silicon).
❯ sw_vers
ProductName:            macOS
ProductVersion:         14.2.1
BuildVersion:           23C71

I think we have a clang option somewhere that you have to enable, but I might be wrong.

The only references to Clang in the devenv.nix docs are:
https://github.com/cachix/devenv/blob/ad0ae333b210e31237e1fc4a7ddab71a01785add/docs/reference/options.md?plain=1#L3844-L3850

My workaround was adding pkgs.libcxxabi

I've found that clang breaks in this way if I have multiple languages enabled.
For example if I have the following then I get problems with clang when using golang.
languages.ruby.enable = true;
languages.rust.enable = true;
languages.go.enable = true;

But with only go enabled as below, it works just fine.
languages.go.enable = true;

I can confirm the issue.

My workaround was adding pkgs.libcxxabi

This didn't work for me

Does it also happen on #745

Could someone try with 1.0.1 that was released yesterday?

I am going to test it immediately

Closing, please reopen if still broken.


Add SBRP tooling to support text-only packages

Tooling should exist to automate the process for adding a text-only package to SBRP.  User should be able to provide the package name and version with an optional feed.  The tooling in dotnet/installers around text-only package generation may be a good reference for implementing this.

Additional information:

existing tooling in dotnet/installers can be found here
entry point for the resulting tooling should be the ./generate.sh in SB repo root (source)
usage of the prepared mechanism should be documented at least in the source build docs (available here)

Update on progress -> started migrating MSBuild logic found in dotnet/installers to SBRP; in general, the idea behind the solution is to have an MSBuild project similar to that in dotnet/installers, with the small difference that the package name, version and optionally feed are provided as CL properties provided by the entrypoint script

Update on progress -> during PR review it was decided to extend the current task goal with merging the existing reference package generation tooling and the proposed text-only one for better maintenance / re-usability; currently working on adding that to the opened PR

Update on progress -> PR feedback incorporated into the branch, waiting for re-review


Resize Sensor detaches when moved in DOM

I need to temporarily move an element in the DOM, which has the ResizeSensor applied to it.
I have found that when I do this, the ResizeSensor no longer works after the move.
I am not cloning the DOM at all, just simply moving it, so I would expect event listeners to still work. Any ideas on why the ResizeSensor is detaching?
Please see codepen for an example:
https://codepen.io/cheryllaird/pen/qmJogK

My observation: That's because by moving an element, Chrome browser (only tested Chrome) resets the scrollLeft and scrollTop of all children elements without sending us the scroll event. To make the resize event working we need to reset the values of those two properties back to a value > 0 as seen in https://github.com/marcj/css-element-queries/blob/a90832ef68b7415aa85d747e4d679c9e6bdaa668/src/ResizeSensor.js#L156-L160.
Two ways of fixing this:

We provide an API for such cases: ResizeSensor.reset(element)
We try to automate it by listening to domMutation events (which are not supported by all browsers - not sure about the coverage)

Best way is probably to implement both, although I would prefer to make an on/off switch for the second due its performance penalties:
https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Mutation_events:

Adding DOM mutation listeners to a document profoundly degrades the performance of further DOM modifications to that document (making them 1.5 - 7 times slower!). Moreover, removing the listeners does not reverse the damage.

@marcj @cheryllaird  imho it would be great to have ResizeSensor.reset(element) or even resizeSensorInstance.reset() because atm i have to recreate ResizeSensor

as a temp solution based on the sources:
const expand = element.querySelector('.resize-sensor-expand');
const shrink = element.querySelector('.resize-sensor-shrink');
const expandChild = expand.childNodes[0] as HTMLDivElement;

expandChild.style.width = '100000px';
expandChild.style.height = '100000px';

expand.scrollLeft = 100000;
expand.scrollTop = 100000;

shrink.scrollLeft = 100000;
shrink.scrollTop = 100000;


drag and drop from Outlook 2010 64-bit error

Hi Sven,
I have a problem with your component in Delphi XE7 compiling 64-bit.
I try to do a drag and drop from Outlook 2010 64-bit, but I encounter an error in the function LoadMAPI32 on :
GetProc('MAPIGetDefaultMalloc@0', pointer( @MAPIGetDefaultMalloc));
The error is :
"MAPI initialization failed: Failed to get mapi32.dll entry point for MAPIGetDefaultMalloc@0: The specified procedure could not be found. Drag and drop and paste will not be functional."
Outlook and my application are both administrator rights.
I made any kind of test, but now I do not know what to try.
Do you have an idea ?

it seames the 64 bit support isn't implementet
https://github.com/DelphiPraxis/The-Drag-and-Drop-Component-Suite-for-Delphi/search?utf8=✓&q=LoadMAPI32+
if i have time, i can take a look on this.

OK, thanks.
  I also look to my side to see what it is possible to do.
  Sven Harazim a écrit :

if i have time, i can take a look on this.

ca you try the current rev
https://github.com/DelphiPraxis/The-Drag-and-Drop-Component-Suite-for-Delphi/commit/9f0193de17020d8811c3474c7a80ef454c492e75
i don't have Outlook

Hello Sven,

  No, I still have the message:
  ---------------------------
  Outlook Drop Target demo
  ---------------------------
  Failed to get mapi32.dll entry point for MAPIGetDefaultMalloc@0:
  The specified procedure could not be found.
  ---------------------------

  I am running on Windows 10 with a 64-bit compilation in Delphi
  XE7.

  Best regards
  Sven Harazim a écrit :

  ca you try the current rev
  9f0193d
  i don't have Outlook
  —
    You are receiving this because you authored the thread.
    Reply to this email directly or view
      it on GitHub

Hello Sven,

  you can take a look on :

https://msdn.microsoft.com/en-us/library/office/cc963763.aspx#sectionSection2
  https://mapistublibrary.codeplex.com/

  Best regards
  Sven Harazim a écrit :

  ca you try the current rev
  9f0193d
  i don't have Outlook
  —
    You are receiving this because you authored the thread.
    Reply to this email directly or view

      it on GitHub

hav you tried the x64 target from
https://github.com/DelphiPraxis/The-Drag-and-Drop-Component-Suite-for-Delphi/tree/master/DemosWithoutInstall/Outlook
?

@JeanDUPOND I know this is an old issue, but if you ever want to revisit this, I believe the patch from: #34 / 4f3a6e941eb4364c241b13728a74e7b1a034b061 fixes this issue.

ok, then i will close this here, thanks


Do you support spring boot 1.2?

Do you support spring boot 1.2?
For English only, other languages will not accept.
Before asking a question, make sure you have:

Googled your question.
Searched open and closed GitHub issues.
Read documentation: ShardingSphere Doc.

Please pay attention on issues you submitted, because we maybe need more details.
If no response more than 7 days and we cannot reproduce it on current information, we will close it.

Can you try to example first?

ok. thanks . I will give it a try.


403 Forbidden error when trying to port-forward workload using Rancher kubeconfig

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Log into remote blank Alpine 3.12 VM
Install k3s v1.19.2+k3s1 (INSTALL_K3S_EXEC="server --write-kubeconfig-mode 644 --disable servicelb,traefik")
Deploy istio v1.7.2 with default profile
Deploy metallb v0.9.3
Deploy Rancher v2.4.8
Deploy any workload exposing a port (i.e. httpbin)
Copy&Paste the Admin kubeconfig file from Rancher UI to local kubeconfig file (edit to change IP for remote VM)
Locally run kubectl --kubeconfig ./rancherconfig.yaml port-forward svc/httpin 8080:80 -n httpbin

Result:
error: error upgrading connection:
When using the k3s kubeconfig (/etc/rancher/k3s/k3s.yaml) locally with kubectl, port-forwarding works. However, when trying to use Rancher's kubeconfig file (under Admin user), I get the error mentioned earlier. Adding -v9 to kubectl, I can see this:
I0929 14:48:53.697686   19304 round_trippers.go:443] POST https://k8s.REDACTED.com/k8s/clusters/c-bcrmr/api/v1/namespaces/httpbin/pods/httpbin/portforward 403 Forbidden in 62 milliseconds
Istio's logs also show the same error.
Since I am the Admin, I don't see what other permission I would need to add for this to be allowed. Any clues?
Thanks
Environment information

Rancher version v2.4.8
Single k3s cluster, v1.19.2+k3s1

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Self-Hosted
Machine type (cloud/VM/metal) and specifications (CPU/memory): VM
Kubernetes version (use kubectl version): 1.19.2

Currently affecting my teammates and me. We cannot port-forward any of our services for debugging purposes...

Oh, now 2021, there are no any solution. 😭

👀

Are you running Istio and the Nginx ingress, or just Istio?

Are you running Istio and the Nginx ingress, or just Istio?

I need to save cost on aws nlb. so, I created only istio ingress and bypass to rancher pod.

Updated Rancher to v2.5.6, still seeing this issue...

Updated to Rancher v2.6.0, still seeing this issue

Issue is still present in rancher 2.6.8 - cannot exec, attach, or port-forward with kubectl when rancher runs behind an NGINX proxy. Believe to be related to the use of SPDY in these kubectl commands.
I tested directly with an NGINX reverse proxy directly to the kubernetes API (without the rancher proxy), and the connection upgrade to SPDY worked. So may be an interaction between the NGINX proxy and the rancher proxy that breaks the connection.

Running v2.7.8 and still having this issue...


Blinking cursor in Select on IE11

Focusing a Select in IE11 will add a blinking cursor that is visible through the dropdown.
Bug can be reproduced using the selects in the documentation http://materializecss.com/forms.html
Any CSS fix for this?

Try the following CSS code and let me know if this fixes your problem.
input.select-dropdown:focus {
    text-indent: -9999999em;
}

It seems to be working.
But! there seems to be a visible transition effect.
Is it necessary to have transition on all properties? What properties need to have transition?
transition: all 0.3s;

That is a good question. @tomscholz do you have some more information?

These issues are all duplicates:
https://github.com/Dogfalo/materialize/issues/4413
https://github.com/Dogfalo/materialize/issues/4315
https://github.com/Dogfalo/materialize/issues/4306
https://github.com/Dogfalo/materialize/issues/3715
https://github.com/Dogfalo/materialize/issues/3171
https://github.com/Dogfalo/materialize/issues/630
For the future discussion, please use this issue instead.
https://github.com/Dogfalo/materialize/issues/3790

The css fix causes another problem. After selecting an option from keyboard, the field stays blank. After clicking somehwere else, the value appears.

@madhmeht please provide a coden which shows this issue.

@DanielRuf here is the codepen link https://codepen.io/anon/pen/KyRRJy

@DanielRuf here is the codepen link https://codepen.io/anon/pen/KyRRJy

Thanks 🙏🙏🙏


Enhancements in Select and Issue List Design

Summary:
This PR introduces improvements in the design of the select dropdown and issue list components.
Changes made:

Improved styling for the select dropdown.
Adjusted layout and spacing in the issue list for consistency.
Cleaner separation between issues by highlighting them.

Screenshots/Previews:

@Keshvii I just checked the preview (https://deploy-preview-14--hiero-open-source.netlify.app/hacktoberfest/) and can not see the changes. It looks broken.

Hi @hendrikebbers, it was working perfectly in the localhost environment. Could you help me understand why it isn't showing in the preview? I'm still a beginner, so any guidance would be greatly appreciated.

@Keshvii I have no clue. Maybe you have not commited something? The preview does nothing but doing a hugo build.


Playground Type Error

Describe the bug
TypeError Cannot read properties of undefined (reading '0')
Reason:
bad argument input for transaction?
user error?
https://sentry.io/organizations/dapperlabs/issues/3460590666/?project=6391677

5 events in last 24 hrs by 2 users (119 events in last 30 days)
occurs when sending script/transactions to be executed
extra error stack :

{
  arguments: [
    {
      code: -32603,
      data: None,
      message: input is not a literal,
      name: Error,
      stack:
      Error: input is not a literal
          at https://play.onflow.org/main.js:106:81915
          at https://play.onflow.org/main.js:106:82209
          at https://play.onflow.org/main.js:106:82572
          at r (https://play.onflow.org/main.js:114:322891)
    }
  ],
  logger: console
}

https://github.com/onflow/flow-playground/blob/staging/src/components/CadenceEditor/ControlPanel/index.tsx#L277
and
https://github.com/onflow/flow-playground/blob/staging/src/components/Arguments/index.tsx#L307
Error is due to LS responding with no data to the formatted var. The try/catch errors out and logs to console but the code continues and reaches this Type error attempting to index into undefined

@MrDSGC what's the plan with this issue? Did we reach an agreement on how to proceed?

Stale.


Create a property graph element validator

We need a tool to validate elements (vertices or edges) in the Property Graph data model (hydra/langs/tinkerpop/propertyGraph) against element types (vertex or edge types). This validator will operate at the level of individual elements (and therefore in linear time w.r.t. the number of elements), not at the level of a whole graph. It will check for vertices that:

The label of the element matches the label of the type
The id of the element conforms to the id type of the element type
Each property of the element conforms to the corresponding property of the element type
No properties are present in the element which are not present in the element type

Additionally for edges, it will check that:

The label of the out-vertex matches the out-vertex label of the edge type
The label of the in-vertex matches the in-vertex label of the edge type

The immediate need for the validator is in Java, but it may be worthwhile to write the utility in the Haskell DSL so that it can be used in both languages. This code is likely to be used in additional TinkerPop language variants in the future.

Note: the implementation also validates graphs against schemas, in addition to validating vertices against vertex types and edges against edge types. Migration into the DSL is still TODO.


Add haho as a bak plugin

Adds awesome Haho plugin for mqtt. This plugin successfully registers itself and connects to MQTT server but need framework improvements to support adding routers.

Job is done :)


Required rule doesn't work perfectly with Vuetify v-select field

Versions:

VueJs: 2.5.3
Vee-Validate: 2.0.0-rc.21

Description:
When we select an option from select field for the first time and then if we run the validation the field will recognize as empty, see this short gif:

And this is my code:
<v-select
  label="Type"
  v-model="type"
  :items="['type1', 'type2']"
  :error-messages="errors.collect('type')"
  v-validate="'required'"
  data-vv-name="type"
  required
></v-select>

Steps To Reproduce:
Install Vuetify and use validator on a v-select field.

I can't reproduce the issue:
https://jsfiddle.net/logaretm/rqwnpc0v/1/
Can you please try to produce the issue in a fiddle?

@logaretm The issue was cause of Vuetify, I've updated it and it is not OK.

So, does it work now?


feat!: improve events emissions

Description
This PR improves the overall event emissions by standardizing the event names. It also adds missing attributes and events emissions where useful.
Closes: DCD-441, DCD-442, DCD-443, DCD-444, DCD-445

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[x] included the correct type prefix in the PR title
[x] added ! to the type prefix if API or client breaking change
[x] targeted the correct branch (see PR Targeting)
[x] provided a link to the relevant issue or specification
[x] followed the guidelines for building modules
[x] included the necessary unit and integration tests
[ ] added a changelog entry to CHANGELOG.md
[x] included comments for documenting Go code
[x] updated the relevant documentation or specification
[x] reviewed "Files changed" and left comments if necessary
[x] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Summary by CodeRabbit

New Features

Introduced a utility function for mapping over slices.
Enhanced event naming and attributes across various modules for clarity and consistency.

Refactor

Updated event types and attributes in posts, profiles, reactions, relationships, reports, and subspaces modules to reflect semantic changes.
Standardized event naming convention across the application.

Documentation

Updated documentation to reflect the new event naming and attribute changes.

Overall looks good to me, just some naming unconsistency.


KB2533623 is no longer available

https://github.com/dotnet/docs/issues/20459
https://github.com/dotnetcore-chocolatey/dotnetcore-chocolateypackages/issues/52
Possible replacement: KB4457144

According to https://www.reddit.com/r/windows/comments/ik7sp7/does_anybody_have_the_kb2533623_update_for/, KB3063858 may also be a replacement and it is tiny in comparison with KB4457144 (a full monthly rollup).

KB3063858 works.
Steps:

install Win 7 SP1 (e.g. from MSDN)
manually download and install .NET 4.5 and WMF 5.1
install Chocolatey
cinst -y dotnetcore-runtime.install --source https://myget.org/F/jberezanski-chocolateypackages-dev/api/v2,https://chocolatey.org/api/v2
Restart-Computer
dotnet --list-runtimes

https://chocolatey.org/packages/KB2533623/2.0.0
https://chocolatey.org/packages/KB3063858/1.0.0


Matomo (piwik) media tracking

hi,
do you have any idea if this will work with afterglow.
https://developer.matomo.org/guides/media-analytics/setup#tracking-html5-videos
if not can this be enabled for the v2 release.

Afterglow is using plain regular html5 videos. Just try adding the matomo tag. Let me know if it doesn't work.


get-inlined-html command is removing characters from styling

I'm having a problem with the get-inlined-html command. We have some text values that are replaced at a later stage within the generated HTML. Notice the {SITE_COLOR} that is used as a background color. In the styles object it is correct but in the HTML returned by the command it is removing the last curly brace.
GrapesJS Json:
{
   "assets":[
...
   ],
   "styles":[
...
      {
         "selectors":[
            "#iv675"
         ],
         "style":{
            "background-color":"{SITE_COLOR}",
            "color":"{SITE_TEXT_COLOR}",
            "text-align":"left",
            "vertical-align":"middle",
            "font-size":"14px"
         }
      },
...
   ],
   "pages":[
...
   ]

Inline HTML:
...
<td id="iv675" style="box-sizing: border-box; background-color: {SITE_COLOR;" bgcolor="{SITE_COLOR">
...

Seems to be related to juice parser, so try to investigate there


This fixes a few bugs on processing window functions over partitioned windows

Namely, due to the fact that window functions are executed for every row in
the window set we previously introduced a caching of a result mechanism (as with
each window func call the entire window frame is passed so the result for the entire
frame is calculated on the first window func call). With partitioned windows, we have
to re-iterate (start on row 0 again) with every partition so we now take that into
account when deciding if we should recompute the window function. This fixes an issue
where aggreates/nth_value functions would include results from previous frames in the
computation by now resetting the internal state of the window funcs.
The row number functions for partitioned windows was also broken due to the
fact that the row number resets with every partition. Renamed
windowRowPosition -> zeroIndexedRowNumber in the WindowBatchIterator and simplify
how it's computed to fix this - the initial intention was for the windowRowPosition
to also represent the number of emitted rows, but we have a dedicated field for that
so its computation is now much simpler.
Fix the window frame boundaries.
Summary of the changes / Why this improves CrateDB
Checklist

[ ] User relevant changes are recorded in CHANGES.txt
[ ] Touched code is covered by tests
[ ] Documentation has been updated if necessary
[ ] CLA is signed
[ ] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

@mfussenegger realise it's a rather fat commit, but the issues are connected and rather hard to separate (separating the iterate/reiterate bit in agg/nth_value also depends on fixing the window frame boundaries for example, and everything gets even more interconnected when it comes to having passing tests for each fix)


Fixed behavior of groupby to preserve order of multiple keys (Issue #72)

groupby() originally could take a list or a set of category keys as input. This implementation did not deal preserve the order of the keys (when provided as a list) in the output. The fix was to no longer accept sets of keys and just take lists to deal with multiple keys. Removing the sorting now preserves the order of the keys in the output (dictionary).
The AggCategories tests were updated to reflect the preservation of key input order.

[Current coverage][cc-pull] is 65.62%

Merging [#81][cc-pull] into [develop][cc-base-branch] will decrease coverage by 0.01%

@@            develop        #81   diff @@
==========================================
  Files            14         14
  Lines          1755       1754     -1
  Methods           0          0
  Messages          0          0
  Branches        393        393
==========================================
- Hits           1152       1151     -1
  Misses          507        507
  Partials         96         96

Powered by Codecov. Last updated by [20f724f...b0354f3][cc-compare]
[cc-base-branch]: https://codecov.io/gh/datreant/datreant.core/branch/develop?src=pr
[cc-compare]: https://codecov.io/gh/datreant/datreant.core/compare/20f724f5c2663bce84774f383442f2b9b8c94d53...b0354f3b44d1d6537ad2c2d7beb71b371b45bca1?src=pr
[cc-pull]: https://codecov.io/gh/datreant/datreant.core/pull/81?src=pr

Looks good @sseyler! Merging!


Add an environment variable $CHRUBY_SET_GEM_HOME to disable setting $GEM_HOME

This is a proof-of-concept PR to address #422.
It still needs documentation and a changelog entry.
@postmodern @havenwood What do you think?

@postmodern @havenwood Could we merge this? What do you think?

This looks good to me.
The only question I would have is whether to check if the variable is set rather than "false" or 0.  This seems like as good a solution as any to me, unless @postmodern has an opinion on it. It seems there are some shell libs (like bash-boolean-helpers) but hardly worth adopting here.

Posted some thoughts: https://github.com/postmodern/chruby/issues/422#issuecomment-557379476
I've seen people prefer testing for "true" instead of not "false".

Posted some thoughts: #422 (comment)

Thanks, I replied there.

I've seen people prefer testing for "true" instead of not "false".

CHRUBY_SET_GEM_HOME has a default of true, so an explicit false seems the clearest to me.

I made a PR which doesn't need user configuration and just does the "right thing" based on whether the default gem home is writable: https://github.com/postmodern/chruby/pull/431
It seems better than this PR, so I'll close this.


Suppressed default arguments are still visible

In some occasions (e.g., with action='version'), an unexpected argument default is rendered as
Default: '==SUPPRESS=='
I have created #53 to fix this.
Tests are currently failing on 3.7 because an incompatible version of packaging seems to be installed via poetry. I'd need a little help as I'm not familiar with poetry.

I guess this can be closed now that #53 is merged.


Unknown dialect ~malformed~

Will update this with more info as soon as I can...
Here's a stack trace (minified/packaged code, sorry, will try to reproduce unminified later):
Error: Unknown Dialect ~malformed~
    at d6e (/malloy/demo/malloy-demo-composer/dist/malloy-composer-demo-darwin-x64/malloy-composer-demo.app/Contents/Resources/app/build/main.js:228:242)
    at kg.getDialect (/malloy/demo/malloy-demo-composer/dist/malloy-composer-demo-darwin-x64/malloy-composer-demo.app/Contents/Resources/app/build/main.js:446:96383)
    at OG.getDialect (/malloy/demo/malloy-demo-composer/dist/malloy-composer-demo-darwin-x64/malloy-composer-demo.app/Contents/Resources/app/build/main.js:446:103975)
    at yY.getExpression (/malloy/demo/malloy-demo-composer/dist/malloy-composer-demo-darwin-x64/malloy-composer-demo.app/Contents/Resources/app/build/main.js:453:118838)
    at CK.queryFieldDef (/malloy/demo/malloy-demo-composer/dist/malloy-composer-demo-darwin-x64/malloy-composer-demo.app/Contents/Resources/app/build/main.js:453:31948)
    at CK.fieldDef (/malloy/demo/malloy-demo-composer/dist/malloy-composer-demo-darwin-x64/malloy-composer-demo.app/Contents/Resources/app/build/main.js:453:31872)
    at TG.fieldDef (/malloy/demo/malloy-demo-composer/dist/malloy-composer-demo-darwin-x64/malloy-composer-demo.app/Contents/Resources/app/build/main.js:446:94822)
    at kg.structDef (/malloy/demo/malloy-demo-composer/dist/malloy-composer-demo-darwin-x64/malloy-composer-demo.app/Contents/Resources/app/build/main.js:446:100173)
    at WG.withParameters (/malloy/demo/malloy-demo-composer/dist/malloy-composer-demo-darwin-x64/malloy-composer-demo.app/Contents/Resources/app/build/main.js:453:3499)
    at GG.execute (/malloy/demo/malloy-demo-composer/dist/malloy-composer-demo-darwin-x64/malloy-composer-demo.app/Contents/Resources/app/build/main.js:453:2296)

Is the source code which causes this available?

cool, just needed to know if it was valid malloy

so if i compile flights but never return any schema i should see this error?

I think that should reproduce it? LMK if that doesn't work...

One way to do that is to just gcloud config unset project --installation (and maybe also gcloud config unset project)


redisson lock uncontrolled release

Hi all,
I am facing strange problems with Redisson lock.
I use the lock without expiration - which means is that watchdog mechanism in-charge of updating the lease time of the lock in redis.
Threads that are using the lock, lock it for time ranging from couple of seconds to 300 seconds or even more.
The problem:
sometimes when a thread(that acquired it) tries to release the lock the thread receives IllegalMonitorStateException , which means that this lock is already released.
One solution was to increase the watchdog timeout - I increased it to 100 seconds and it decreased the number of errors but they still occur from time to time...
I don't want to increase the timeout even more because this doesn't address the root problem.
How can I solve this? is anyone else encountered this behaviour?

sometimes when a thread(that acquired it) tries to release the lock the thread receives IllegalMonitorStateException

Please check that you use the same thread to release it.


In vulkan backend,how can I set the gpu render mode to binning instead of direct?

I have got a GPU trace capture with snapdragon profiler.The results are represented in the fig below

The number of bins is 1,and the render mode is direct.I think that the render mode  should be binning .
How can I make it to binning?

Adreno GPUs automatically decide whether to be direct or bin. There's nothing wrong with direct rendering. It means the GPU could do all its work in a single tile.


How to dynamically bind executor with variable symbol?

During testing phase, my symbol's computing structure depends on some factor K. E.g, when the factor equals to K, then there are N(K) layers of Convolution operations, where N(K) changes with K.
Thus, I have to construct a new symbol and rebind it with an executor when K changes. Code may look like this:
if current_k != last_k:
    sym = get_symbol(current_k)
    mod = mx.mod.Module(sym, ...)
    mod.bind(...)
else:
    # keep the module unchanged
    pass

My question is, how to effectively release memory allocated by the bound module and rebind it with a different symbol?
I've tried using python's 'del' to delete the bound module, but the memory is not released when look into the info returned by 'nvidia-smi'.

Hello @squidszyd, There is no explicit call to release the memory immediately. The memory allocated will be marked to release when the reference to the object is removed or marked with 'del' or when you 'force rebind' the module with new symbol.
Other alternative solution would be:

Using "reshape" if you want to change the shape of params and grad arrays already bound in the module.

Please reopen, if the issue persists.