-
Notifications
You must be signed in to change notification settings - Fork 1
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
Fix/tcp osl server processing started #59
Conversation
…OWN" for general_listener. We don't want to receive (and osl to issue) all notifications.
…TION_STARTED notification. This ensures that start (wait_for_started=True) actually waits for the project status transitioning to PROCESSING.
@rfahlberg Thanks for review and bug fixes. Is that so |
Perfect, this notification will be available in 2023R1 so we can discard previous pull request? |
Yes. |
… args need to be appended to subprocess "args" separately.
Co-authored-by: PanekOndrej <[email protected]>
@PanekOndrej This is based on your original branch "fix/tcp_osl_server" and changes usage of EXECUTION_STARTED notification to PROCESSING_STARTED notification which has been added to optiSLang this week.