You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, I would like to express my appreciation for the tremendous work done on the Plombery project. The overall user experience, functionality, and design have been exceptional, and it is evident that a lot of thought and effort has gone into creating this project. The seamless integration of features and the intuitive interface make it a standout platform.
There appears to be an issue with the browser connection on the landing page. After the server has been running for a while, the connection is forced to close unexpectedly. Below is a detailed description of the issue along with the log trace and errors observed.
Log Trace:
INFO: 192.168.127.210:61506 - "GET / HTTP/1.1" 200 OK
INFO: 192.168.127.210:61506 - "GET /api/auth/whoami HTTP/1.1" 200 OK
INFO: 192.168.127.210:61506 - "GET /api/pipelines/ HTTP/1.1" 200 OK
INFO: ('192.168.127.210', 61507) - "WebSocket /api/ws/" [accepted]
INFO: connection open
INFO: connection closed
Errors from Developer Tools:
vendor-3fad8192.js:40 RangeError: Invalid time value
vendor-3fad8192.js:38 Uncaught RangeError: Invalid time value
Steps to Reproduce:
Start the server and navigate to the landing page.
Allow the server to run for a while.
Observe that the browser connection is forced to close for any new connection.
The text was updated successfully, but these errors were encountered:
First of all, I would like to express my appreciation for the tremendous work done on the Plombery project. The overall user experience, functionality, and design have been exceptional, and it is evident that a lot of thought and effort has gone into creating this project. The seamless integration of features and the intuitive interface make it a standout platform.
There appears to be an issue with the browser connection on the landing page. After the server has been running for a while, the connection is forced to close unexpectedly. Below is a detailed description of the issue along with the log trace and errors observed.
Log Trace:
Errors from Developer Tools:
vendor-3fad8192.js:40 RangeError: Invalid time value
vendor-3fad8192.js:38 Uncaught RangeError: Invalid time value
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: