🔍 Before submitting the issue
🐞 Description of the bug
We have found issues with using the reset and stop command.
We are calling:
status = node.control(self.selected_command, wait_for_completion=True, timeout=self.command_timeout)
where node is either osl.project.root_system or a node from osl.project.root_system.find_node_by_uid
self.selected_command is a string, in these cases either "stop" or "reset". and self.command_timeout is 30 (seconds)
I have had a discussion with @rfahlberg and he thinks he knows the issue. In reset, the command waits for the wrong state, and for stop it gets the status the global status (not the per-design status)
📝 Steps to reproduce
See above
💻 Which operating system are you using?
Windows
📀 Which ANSYS version are you using?
2024R1
🐍 Which Python version are you using?
3.10
📦 Installed packages
aiofiles==23.2.1
aiosqlite==0.19.0
annotated-types==0.6.0
ansi2html==1.9.1
ansys-api-platform-instancemanagement==1.0.0
ansys-optislang-core==0.5.1
ansys-platform-instancemanagement==1.1.2
ansys-saf-desktop==1.0rc4
ansys-saf-glow-engine==1.1.0
ansys-saf-pim-light-server==0.3.2
ansys-solutions-dash-lib==0.4.5
ansys-solutions-optislang-frontend-components==0.1.2
# Editable install with no version control (ansys-solutions-tuning-fork==0.1.dev0)
-e c:\users\jnorlin\source\repos\.solutions\main_207e8a5\tuning-fork
ansys-web-components-dash==0.0.dev2
anyio==3.7.1
asgiref==3.7.2
async-timeout==4.0.3
asyncpg==0.29.0
backoff==2.2.1
blinker==1.7.0
bottle==0.12.25
bson==0.5.10
cachelib==0.9.0
certifi==2023.11.17
cffi==1.16.0
charset-normalizer==3.3.2
click==8.1.7
clr-loader==0.2.6
colorama==0.4.6
coloredlogs==15.0.1
cryptography==41.0.7
dash==2.14.2
dash-bootstrap-components==1.5.0
dash-core-components==2.0.0
dash-extensions==0.1.13
dash-html-components==2.0.0
dash-table==5.0.0
dash_daq==0.5.0
dash_uploader==0.6.0
debugpy==1.8.0
deepdiff==6.7.1
Deprecated==1.2.14
EditorConfig==0.12.3
exceptiongroup==1.2.0
fastapi==0.104.1
fire==0.5.0
Flask==2.3.3
Flask-Caching==2.0.2
googleapis-common-protos==1.62.0
grpcio==1.60.0
grpcio-health-checking==1.48.2
h11==0.14.0
httpcore==0.16.3
httpx==0.23.3
humanfriendly==10.0
idna==3.6
importlib-metadata==6.11.0
itsdangerous==2.1.2
Jinja2==3.1.3
jsbeautifier==1.14.11
MarkupSafe==2.1.3
more-itertools==9.1.0
nest-asyncio==1.5.8
networkx==3.1
numpy==1.26.3
opentelemetry-api==1.22.0
opentelemetry-exporter-otlp==1.22.0
opentelemetry-exporter-otlp-proto-common==1.22.0
opentelemetry-exporter-otlp-proto-grpc==1.22.0
opentelemetry-exporter-otlp-proto-http==1.22.0
opentelemetry-instrumentation==0.43b0
opentelemetry-instrumentation-asgi==0.43b0
opentelemetry-instrumentation-fastapi==0.43b0
opentelemetry-instrumentation-flask==0.43b0
opentelemetry-instrumentation-httpx==0.43b0
opentelemetry-instrumentation-logging==0.43b0
opentelemetry-instrumentation-wsgi==0.43b0
opentelemetry-proto==1.22.0
opentelemetry-sdk==1.22.0
opentelemetry-semantic-conventions==0.43b0
opentelemetry-util-http==0.43b0
optislang-dash-lib==0.2.2
ordered-set==4.1.0
packaging==23.2
pandas==2.0.3
plotly==5.18.0
protobuf==3.20.3
proxy_tools==0.1.0
psutil==5.9.7
pycparser==2.21
pydantic==2.4.2
pydantic-settings==2.1.0
pydantic_core==2.10.1
pyreadline3==3.4.1
pyshortcuts==1.9.0
python-dateutil==2.8.2
python-dotenv==1.0.0
python-json-logger==2.0.7
python-multipart==0.0.6
pythonnet==3.0.3
pytz==2023.3.post1
pywebview==4.4.1
pywin32==306
PyYAML==6.0.1
requests==2.31.0
retrying==1.3.4
rfc3986==1.5.0
six==1.16.0
sniffio==1.3.0
starlette==0.27.0
tenacity==8.2.3
termcolor==2.4.0
typing_extensions==4.9.0
tzdata==2023.4
urllib3==2.1.0
uvicorn==0.24.0.post1
Werkzeug==3.0.1
wrapt==1.16.0
zipp==3.17.0
🔍 Before submitting the issue
🐞 Description of the bug
We have found issues with using the reset and stop command.
We are calling:
where node is either osl.project.root_system or a node from osl.project.root_system.find_node_by_uid
self.selected_command is a string, in these cases either "stop" or "reset". and self.command_timeout is 30 (seconds)
I have had a discussion with @rfahlberg and he thinks he knows the issue. In reset, the command waits for the wrong state, and for stop it gets the status the global status (not the per-design status)
📝 Steps to reproduce
See above
💻 Which operating system are you using?
Windows
📀 Which ANSYS version are you using?
2024R1
🐍 Which Python version are you using?
3.10
📦 Installed packages