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
When sending invalid text, such as code that cannot be resolved, the application does not close the socket until the client stops the process. I am not sure if this is a fault of the nukeserversocket or the clients.
Connection with broken text
[09:42:09] DEBUG - New connection.
[09:42:09] DEBUG - Pending connection.
[09:42:09] DEBUG - Socket connected.
[09:42:09] INFO - Received data from client.
[09:42:09] DEBUG - Socket ready.
[09:51:03] DEBUG - Received data: {'file': 'test.py', 'text': 'import random\nbroken', 'formatText': '1'}
[09:51:03] DEBUG - Running script: test.py
... HANG (probably waits for timeout)
[09:42:18] ERROR - Socket error: PySide2.QtNetwork.QAbstractSocket.SocketError.RemoteHostClosedError
Valid connection
[09:47:17] DEBUG - New connection.
[09:47:17] DEBUG - Pending connection.
[09:47:17] DEBUG - Socket connected.
[09:47:17] INFO - Received data from client.
[09:47:17] DEBUG - Socket ready.
[09:47:17] DEBUG - Received data: {'text': 'from __future__ import print_function; print("Hostname: DESKTOP-F53A6QP User: virgilsisoe"); print("Connected to host: 127.0.0.1 port: 54321"); print("10 * 2 =", 20)', 'file': 'tmp_file', 'formatText': '1'}
[09:47:17] DEBUG - Running script: tmp_file
[09:47:17] DEBUG - Formatting output: [09:47:17 NukeTools] tmp_file\nHostname: DESKTOP-F53A6QP User: virgilsisoe\nConnected to host: 127.0.0.1 port: 54321\n10 * 2 = 20\n
[09:47:17] DEBUG - Clearing output.
[09:47:17] INFO - Writing output to back socket...
[09:47:17] DEBUG - Output: [09:47:17 NukeTools] tmp_file\nHostname: DESKTOP-F53A6QP User: virgilsisoe\nConnected to host: 127.0.0.1 port: 54321\n10 * 2 = 20\n
[09:47:17] DEBUG - Socket closed.
The text was updated successfully, but these errors were encountered:
This problem seems to occur only when testing nukeserversocket locally with the exec function, so this is not a big deal. Placing a try and catch around the exec should solve the issue.
When sending invalid text, such as code that cannot be resolved, the application does not close the socket until the client stops the process. I am not sure if this is a fault of the nukeserversocket or the clients.
Connection with broken text
Valid connection
The text was updated successfully, but these errors were encountered: