Skip to main content
Version: v4.5.0

Stack Indexing

See below some errors when using the Stack API and how you can solve them:

"Picture {1} does not exist in repository {2}."; "Invalid provider {2} for the repository {1}."; "Invalid provider {1}.",*

Possible Cause The repository's URL is invalid.

Solution Check if the registered repository’s URL is correct. If it is not, update the Stack with the correct URL.

"childPath {1} is out of parent {2}/{3}."

Possible Cause The submodule path could not be found.

Solution Verify if the submodule path is being referenced correctly. If it is not, just reference it.

"Error to clone repo {1} using githubapp strategy." "Error to clone repo {1} using pat strategy." "Error to clone repo {1} using public strategy."

Possible Cause The visibility, URL or credentials to access the repository are invalid.

Possible Solutions

"Error to clone repo {1} using public strategy."

  • Check if the registered URL of the repository is correct. If not, update the URL.
  • Check if the repository access is PUBLIC, if not, change the repository visibility.

"Error to clone repo {1} using pat strategy."

  • Check if the registered URL of the repository is correct;
  • Verify if the secrets to access the SCM are correct and/or valid.

"Error to clone repo {1} using githubapp strategy."

  • Verify if the repository URL registered is correct;
  • Verify if the secrets to access the SCM are correct and/or valid.

"Error to parse markdown {1}."

Possible Cause
Markdown is badly formatted.

Possible Solution
Check file formatting and make necessary corrections according to the file guidelines.

"Yaml file {1} was not found." .

Possible Cause A required yaml file was not found. It can be a stack.yaml, plugin.yaml and template.yaml.

Possible solutions

  • Check, in case of stack.yaml, plugin.yaml and template.yaml, if the filename is correct;
  • Check if the file extension is correct (.yaml or .yml);
  • Check if the file location is correct.

"Internal error in {1} indexation." "Fail to save picture {1}." .

Possible Cause The internal image reference does not exist.

Solution
Check if the image referencing is done correctly.

"STKAPI_4005_INDEXATION_ERROR_MARKDOWN_INVALID_IMAGE_BLOCK": "Invalid image block {1} in markdown {2}."

Possible Cause The internal image reference does not exist.

Solution
Check if the image reference is correct.

"STKAPI_4004_INDEXATION_ERROR_MARKDOWN_INVALID_PATH": "Markdown {1} does not exist in the {2} repository."

Possible Cause The internal markdown reference does not exist.

Solution Check if the markdown reference is correct.

"STKAPI_3005_VALIDATION_ERROR_YAML_REQUIRED_FIELD": "The required field {2} in file {1} was not found."

Possible Cause
A required YAML field is missing.

Solution
Check if you informed the field or spelled correctly in the YAML.

STKAPI_3006_VALIDATION_ERROR_YAML_FIELD_FORMAT": "The field {2} in file {1} is in invalid format (e.g. kebab-case).

Possible Cause
The field format is incorrect.

Solution
Correct the field to the expected format.

"STKAPI_3007_VALIDATION_ERROR_YAML_FIELD_MIN_LENGTH": "The {2} field in {1} file is with invalid minimum size. Minimum size is {3}"

Possible Cause
The value of the field has been filled in with less than the minimum quantity.

Solution
Fill in the field with the appropriate character size value.

"STKAPI_3008_VALIDATION_ERROR_YAML_FIELD_MAX_LENGTH": "The {2} field in {1} file is with invalid maximum size. Maximum size is {3}"

Possible Cause
The value of the field was filled with the quantity greater than the maximum quantity.

Solution
Fill the field with a value of a appropriate character size.

STKAPI_3010_VALIDATION_ERROR_YAML_EMPTY_VALUE_NOT_ALLOWED": "The {2} field in the {1} file is a not allowed value.

Possible Cause
The field value has been filled with invalid values.

Solution Check which values are allowed for the field.

STKAPI_3011_VALIDATION_ERROR_YAML_YAML_FIELD_INVALID_TYPE": "The field {2} in file {1} is an invalid value.

Possible Cause
The type of the value entered is invalid. For example: the field expects a string and fills in a number.

Solution Check which types are allowed to fill in the field.

Was this page helpful?