#Getting some errors

1 messages · Page 1 of 1 (latest)

summer tiger
#

I have a collection file that I am getting errors on. I have gone aver it serveral times, and still it is aborting...

this was previously tested with a small number of movies and it worked then.

YAML Error: while parsing a block mapping
in "/mnt/Media01B/Plex-Meta-Manager/config/movies/collection-label.yml", line 1, column 5 expected <block end>, but found '<block mapping start>'
in "/mnt/Media01B/Plex-Meta-Manager/config/movies/collection-label.yml", line 1869, column 6 
Collection File Failed To Load

Log and YML attached

outer mangoBOT
#

📝 If you want to review this again, jwaltrip4:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

#

Welcome @summer tiger!

Someone from <@&938443185347244033> will assist when they're available.

Including the meta.log from the beginning is a huge help, type !logs for more information.

#

You can press the "Close Post" button above or type /close at any time to close this post.

fleet cobalt
#

Error is pointing at line 1869 in the collection file. Let's see what's there.

#

Step one, let's compare that to the one above it, which apparently loads fine.

summer tiger
#

Yep.. did that. counted spaces. rant it through yaml lint

#

am refering to 1869

fleet cobalt
#

Actually, though, the problem is well above that.

#

collections should be all the way to the left.
All those collections should be two spaces in from the left.

#

What you have there is apparently valid YAML in the general case, but it doesn't match PMM's expectations.

summer tiger
#

ya... just put it in NP++.... fixing. will try after that

river crystalBOT
#

We highly recommend to use a decent editor software to manage PMM's .yml files.

Standard text editors (such as Notepad and TextEdit) often save text in a rich-text format which can result in text formatted in a way that PMM cannot read. But not only that, they also make it very hard to visually distinguish the formatting, such as indentation.
PMM requires indents to always be multiples of 2 spaces, and not TAB stops. If you have one space too much, or too few, it is very hard to notice that with a editor like Notepad.
An editor that is more focused on editing code instead of text will automatically detect the .YML fileformat and adjust things to make it easier to work. They can also try to detect possible errors even before you actually run the .yml in PMM.

This can save a lot of time and headaches.

Preferred:
Visual Studio Code (Windows/Mac/Linux, Opensource & Free) Website
Additionally, install the indent-rainbow by oderwat extension and the YAML by Red Hat extension and leverage our schema.json file by adding this to the top of your config.yml file: # yaml-language-server: $schema=https://raw.githubusercontent.com/meisnate12/Plex-Meta-Manager/nightly/json-schema/config-schema.json

Other options:
Notepad++ (Windows only, Opensource & Free)
Website

Sublime Text (Windows/Mac/Linux, Paid)
Website

For further details and a short list of highly recommended extensions, you can also take a look here.

Here is an example of how Visual Studio Code works with indent-rainbow plugin and using our PMM schema (Click on image to get a better view):

fleet cobalt
#

FWIW this is how VSCode with rainbow indent displays this; since this is valid YAML and the indentation is consistent there's nothing apparently out of sorts. This is an example of how automated syntax-checking tools do not replace domain knowledge. You really need to understand the structure of the file rather than relying on the automated tools to catch every issue.

summer tiger
#

Thanks kindly for the tip

summer tiger
#

vscode, rainbow indent, SSL extensions... Nice

#

By the way.... it all worked. ficin indents. and I also broke out each collection to its own file.