Skip to content

Commit 645d971

Browse files
committed
changes to text
1 parent 73ce3b6 commit 645d971

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/machine-learning/how-to-troubleshoot-validation-for-schema-failed-error.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -78,32 +78,32 @@ In the submitted YAML file, go to the “path” parameter and double check whet
7878

7979
## Error - Missing Field
8080

81-
The submitted YAML file is missing a required parameter. For example – for ml job create (that is, `commandjob` schema), if the “compute” parameter isn't provided, this error will be encountered because compute is required to run a command job.
81+
The submitted YAML file is missing a required parameter. For example – for ml job create (that is, `commandjob` schema), if the “compute” parameter isn't provided, this error will be encountered because compute is required to run a command job.
8282

8383
### Solution - Missing Field
8484

8585
Check the prescribed schema for the asset type you're trying to create or update – check what parameters are required and what their correct value types are. [Here's a list of schemas](reference-yaml-overview.md) for different asset types in AzureML v2. Ensure that the submitted YAML file has all the required parameters needed. Also ensure that the values provided for those parameters are of the correct type, or in the accepted range of values. Save the YAML file and resubmit the command.
8686

87-
## Error - Can't Parse
87+
## Error - Cannot Parse
8888

89-
The submitted YAML file can't be read, because either the syntax is wrong, formatting is wrong, or there are unwanted characters somewhere in the file. For example – a special character (like a colon or a semicolon) that has been entered by mistake somewhere in the YAML file.
89+
The submitted YAML file can't be read, because either the syntax is wrong, formatting is wrong, or there are unwanted characters somewhere in the file. For example – a special character (like a colon or a semicolon) that has been entered by mistake somewhere in the YAML file.
9090

91-
### Solution - Can't Parse
91+
### Solution - Cannot Parse
9292

9393
Double check the contents of the submitted YAML file for correct syntax, unwanted characters, and wrong formatting. Fix all of these, save the YAML file and resubmit the command.
9494

9595
## Error - Resource Not Found
9696

97-
One or more of the resources (for example, file / folder) in the submitted YAML file doesn't exist, or you don't have access to it.
97+
One or more of the resources (for example, file / folder) in the submitted YAML file doesn't exist, or you don't have access to it.
9898

9999
### Solution - Resource Not Found
100100

101-
Double check whether the name of the resource has been specified correctly, and that you have access to it. Make changes if needed, save the YAML file and resubmit the command.
101+
Double check whether the name of the resource has been specified correctly, and that you have access to it. Make changes if needed, save the YAML file and resubmit the command.
102102

103-
## Error - Can't Serialize
103+
## Error - Cannot Serialize
104104

105105
One or more fields in the YAML can't be serialized (converted) into objects.
106106

107-
### Solution - Can't Serialize
107+
### Solution - Cannot Serialize
108108

109109
Double check that your YAML file isn't corrupted and that the file’s contents are properly formatted.

0 commit comments

Comments
 (0)