-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PyFluent: Fluent requires users input to proceed when started in the -g mode (or "-gu -driver null" mode). #967
Comments
@mkundu1 @seanpearsonuk Any idea if this one requires changes on the Fluent side? |
@dnwillia-work @seanpearsonuk @ypatel-qa This is due to limitation of Fluent's grpc server - it doesn't work with -g/-gu mode in windows (point 3 of https://ansyshelp.ansys.com/account/secured?returnurl=/Views/Secured/corp/v222/en/flu_ug/flu_ug_remote-client_limitations.html) |
So, the answer to my question is 'yes' I think. Fixing it properly would require changes in Fluent. For now, that detail should be documented for PyFluent then too and/or we filter out the options (i.e. ignore them) on windows. Reopening the issue. |
@dnwillia-work, assigning to @hpohekar to constrain the launch options on Windows. If -g or -gu appears in the launch arguments on Windows, we can raise an exception. @mkundu1, I think I should also open a Fluent defect for the server issue. Opened Bug 725616 for Fluent. |
🔍 Before submitting the issue
🐞 Description of the bug
Fluent requires users input to proceed when started in the -g mode (or "-gu -driver null" mode)
📝 Steps to reproduce
I am using the latest R23.1. I am testing on Windows using venv created with Ansys CPython.
To reproduce: Run attached script. ("c:\shared\pyfluent\Scripts\python.exe" script.py)
files.zip
Fluent is hanging after every step (unless user provide some input, or hit the return key). Also cx2310.exe windows is showing up, which probably should not.
💻 Which operating system are you using?
Windows
🐍 Which Python version are you using?
3.7
📦 Installed packages
The text was updated successfully, but these errors were encountered: