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
Describe the bug
We should show better error messages when Compute jobs return errors, specifically on Session creation. Currently, only the "top level" error message is being shown to the user, which is not helpful to understand why requests might have failed.
Steps to reproduce
Steps to reproduce the behavior:
Create an autoexec file that has an include statement. Make sure the include file exists:
%include cowboy.sas
Specify the autoexec in the connection profile autoexec config:
proc sgplot data=sashelp.class;
histogram height;
density height;
density height / type=kernel;
run;
Run the test file in step 3. Observe the error reported as "Request failed with status code 400".
If you observe the actual server log, the real error message is noted:
[00000019] << {"details":["%INCLUDE statements can only be set by an administrator, and not directly in autoExecLines of the session request."],"errorCode":5101,"errors":[],"httpStatusCode":400,"id":"","links":[],"message":"%INCLUDE statements are not allowed in the autoExecLines of the session request.","remediation":"Contact your system administrator for changes to the autoexec content for the context.","version":2}
Expected behavior
Show the contents of the rest error representation if we receive a response payload that looks like an Error Representation from compute. We have existing examples of how this is done in the run commands. See run.ts. It would also be nice if we could refactor the error detection functions into a place that could be shared by consumers as well.
Additional context
Reported by a WFL user. This issue will affect Viya and Workbench connection types
The text was updated successfully, but these errors were encountered:
Describe the bug
We should show better error messages when Compute jobs return errors, specifically on Session creation. Currently, only the "top level" error message is being shown to the user, which is not helpful to understand why requests might have failed.
Steps to reproduce
Steps to reproduce the behavior:
Expected behavior
Show the contents of the rest error representation if we receive a response payload that looks like an Error Representation from compute. We have existing examples of how this is done in the run commands. See run.ts. It would also be nice if we could refactor the error detection functions into a place that could be shared by consumers as well.
Additional context
Reported by a WFL user. This issue will affect Viya and Workbench connection types
The text was updated successfully, but these errors were encountered: