-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
Describe the bug
Receiving an error occasionally when running dataforge --build. When it happens, it's always after the message "Import completed successfully". Full error below and in screenshot. Rerunning once or twice resolves the issue.
ERROR:root:Exception while sending command.
Traceback (most recent call last):
File "C:\Python312\Lib\site-packages\py4j\clientserver.py", line 511, in send_command
answer = smart_decode(self.stream.readline()[:-1])
^^^^^^^^^^^^^^^^^^^^^^
File "C:\Python312\Lib\socket.py", line 707, in readinto
return self._sock.recv_into(b)
^^^^^^^^^^^^^^^^^^^^^^^
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Python312\Lib\site-packages\py4j\java_gateway.py", line 1038, in send_command
response = connection.send_command(command)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Python312\Lib\site-packages\py4j\clientserver.py", line 539, in send_command
raise Py4JNetworkError(
py4j.protocol.Py4JNetworkError: Error while sending or receiving
To Reproduce
Steps to reproduce the behavior:
- Configure project folder
- Open project folder in Command Prompt and run dataforge --build
- Error occurs at the end of the build
Expected behavior
- Configure project folder
- Open project folder in Command Prompt and run dataforge --build
- Build completes and command prompt returns successfully
Desktop (please complete the following information):
- OS: Windows 11 Enterprise
- OS Build: 22631.3527
- Browser N/A
- Version N/A
Additional context
Rerunning the --build command after usually fixes the issue. Sometimes I need to run --build two more times for the error to go away.
Metadata
Metadata
Assignees
Labels
No labels
