Skip to main content

Parsing Errors

Parsing errors occur when there are formatting errors. For example missing commas, extra quotes, and indenting. These usually occur off platform and happen when trying to merge a remote branch into your current local branch.

When a parsing error occurs, the Git Modal will open a Parsing Error screen and jump to the error message. There you can fix the error then merge your changes.

Read Parsing Errors​

The image shows a Repository Parsing Error message from Coalesce, indicating that a Git parsing error occurred while syncing local changes. It instructs the user to correct errors in the affected files, with an example error shown in the TestRefreshJob-2.yml file, where the issue is highlighted with a red underline under the id: 2 line.

In this example, you can see there is a parsing error on line 3, it's highlighted. You can hover over it for more information.

The image displays an error message related to bad indentation of a mapping entry in the TestRefreshJob-2.yml file. The specific issue is highlighted with a red underline under the id: 2 line, and the includeSelector line also appears to be partially highlighted.

This tells you the error, bad indentation, and the line and character. Around line 3 and column 8 there should be an error. The system is giving you the best estimate where the error is. The line and column is a starting point to find the error.

To solve the error in the example, you can remove the commas. We know it's the commas because YAML files don't have commas in them. Go to your Git provider and remove the commas. Then resync the branch in Coalesce.

You'll need to resync as many times as needed to solve the error.

Common Parsing Errors​

Bad indentation of mapping entry can occur because:

  • Missing quotation marks.
  • Mismatched quotation marks. Single versus double quotes.
  • Incorrect indentation.
  • Extra or missing commas.

Block mapping entry or implicit mapping pair can occur because:

  • Missing colon.