Since the 5.8 update yesterday I’ve been chasing down a few issues on my site. One was due to a required update with the wappler-bull-queues extension that was resolved earlier today. However, I’ve noticed that server connects with “Live Refresh with Sockets” enabled do not return data and I’m not sure how to debug. My Web Server and Redis logs do not show errors. I can see that the APIs are getting called in the WS dev tools
Anyone have ideas on how to test the socket connections and where things may be going wrong? It was working prior to the update yesterday. Thanks. Here’s the page from the dev site that I referenced https://www.dev2.umleague.net/competitions/31
Are you running your socket emits or refreshes inside library actions? If so then this is caused by a Wappler bug introduced with the last version: Socket Error in Library Actions
I don’t think it’s the exact same issue. Where/when are you seeing that error message? I’m having trouble tracking what’s happening with those WS requests on my page. I don’t think the requests are ever getting processed and am unsure how to debug.
Connections on the front end are timing out, and connections on the backend fail if they are inside exec because they can’t connect via connect-redis since the connection seems to be not accessible or something similar.
Let’s see what Patrick says tmr.
I hope for a Wappler stable branch at some point so that big behind the scene releases like this one can be tested before they go out to production environments. All of this was a big pain today.
I’m seeing the data being returned by server connects with Live Refresh with Sockets enabled. But the content on the page is not loading at all. In this case, I’m populating the returned data in a table and it’s showing no records on the front-end even though I can see the data being returned correctly in the dev console.
If I disable Live Refresh with Sockets from the server connect, the table is getting populated correctly.
I was hoping 5.8.1 would magically fix the issues I was experiencing but unfortunately it did not. I am looking for guidance on how to debug issues with serverconnects that have “Live Refresh with Sockets” enabled. I have several features on my site that should receive live updates based on emits from various server connects and while I’m hesitant to call this a bug, I’m at a loss for how to investigate. I’m not seeing any errors in my redis or web server logs. Any advice would be appreciated. The attached video shows that the query and page work fine with the “live refresh with sockets” setting disabled and stop working once its enabled. Thanks in advance for advice on how to debug.
Not working, preloader keep loading and no logs that allow to debug.
Wappler 5.8.0
server-connect:setup:config redis connection failed, ConnectionTimeoutError: Connection timeout at Socket.<anonymous> (/opt/node_app/node_modules/@redis/client/dist/lib/client/socket.js:178:124) at Object.onceWrapper (node:events:627:28) at Socket.emit (node:events:513:28) at Socket._onTimeout (node:net:550:8) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7) +7s
Testing removing redis container/image/volume on docker, redeploy everything, experimental off and on, npm install.
Restarting only node in docker, makes no difference.
Is it possible to get a link to revert to 5.6.2 as it’s not really possible to remove all socket based actions temporarily and then add them back when this is fixed ?
