You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we run the notebook job by the default start-up script, it causes the AlgorithmError.
To Reproduce
Steps to reproduce the behavior:
Right click the notebook
Click on Create Notebook Job
Click Create without any change of additional parameters.
See error
Expected behavior
The Start-up script should be blank because the customer may not have it by default.
Or should be set the appropriate script that reproduce notebook's kernel on the instance.
Screenshots
I attached above.
Desktop (please complete the following information):
OS: Windoes
Browser Chrome
Additional context
I felt the interface is easy to use.
But the customer will be afraid about the cost because there is no information about the spec and cost before running the job.
The text was updated successfully, but these errors were encountered:
This is the expected behavior for the customer has startup script. However is is not appropriate that causes AlgorithmError if customer does not have it. We deal with this issue as feature request to make startup script appropriate both for prepared customer and not-prepared customer.
Describe the bug
When we run the notebook job by the default start-up script, it causes the AlgorithmError.
To Reproduce
Steps to reproduce the behavior:
Create Notebook Job
Create
without any change of additional parameters.Expected behavior
The Start-up script should be blank because the customer may not have it by default.
Or should be set the appropriate script that reproduce notebook's kernel on the instance.
Screenshots
I attached above.
Desktop (please complete the following information):
Additional context
I felt the interface is easy to use.
But the customer will be afraid about the cost because there is no information about the spec and cost before running the job.
The text was updated successfully, but these errors were encountered: