-
Notifications
You must be signed in to change notification settings - Fork 13
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
Node error in output #23
Comments
@kjdms morning. Please can you send me a email message at &&** so i can get your UCS file to reproduce this and possibly open a bug. It could be viprion related. |
@kjdms got the UCS file. Thank you. Going to look at it this afternoon. Standby! |
please note ACC is community supported i have taken ownership of SR C3561341 |
Created Jira request CHARON-254 for PM tracking. Requesting PD look to see why ACC cannot open this UCS file. I am going to try corkscrew aka F5 vscode extension to see if that will open this UCS file. |
Change By: Vladimir |
@kjdms bug is in code-review. Will provide image once available. Thanks |
Closing this issue. Provided RC to @kjdms |
Environment
Summary
Error when running against my UCS file. Reproducible on demand. The tool will complete if I limit it to one virtual server. Created F5 support case C3561341 to upload the UCS file in question.
Steps To Reproduce
Steps to reproduce the behavior:
Expected Behavior
No node errors in output.
Actual Behavior
Command fails with no output to file. STDERR is listed above.
The text was updated successfully, but these errors were encountered: