-
Notifications
You must be signed in to change notification settings - Fork 56
Handle null string in transcript. #1504
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
Conversation
|
@prmukherj I have removed the internal link |
|
Great work @prmukherj, thanks! |
|
Thank you @seanpearsonuk. Sorry, forgot about that internal link issue. |
|
I have added #1505 in relation to this. |
and I removed the mention of the internal ID as well. It's probably best to put an issue for this sort of thing into the PyFluent repo since it required changes to the library.
I added a link to it under the Development heading on the right. |
The linked issue #1506 mentions the Fluent bug by ID (just as I did here). We do this for all bugs in https://github.com/orgs/pyansys/projects/23, which makes defect management easier, without revealing significant information. On the Fluent side, we hyperlink to here, but not the reverse. |
We were getting a null string from server in transcript which was not handled.