Tried to add overlays for the first time and ending up breaking my config file

[pure copper]

I've been running kometa perfectly fine with just collections and decided to add overlays and ended up breaking my config file. I have attached a screenshot. Sorry I forgot how to grab logs.

[ocean viper]

Welcome @pure copper!

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

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

After attaching your log, do not forget to hit the green check boxes when prompted by our bot.

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

[feral crest]

Providing Log Files

1: Go to your config folder

2: Go into the logs folder

3: Look for meta.log (not meta.1.log etc)

4: Drag it in the Discord thread - the whole thing, DO NOT EDIT IT

5: Still confused? ¯_(ツ)_/¯

Log file too big? USE PASTEBIN or ZIP THE FILE

Thanks for using Kometa

[ocean viper]

📝 If you want to review this again, b_7869:
: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> 📝

**User Info**

Author of Linked Message: b
Person who Invoked the Command: b
File Name: meta.log

Table of Contents:
Page 01: User Info
Page 02: Kometa Info
Page 03: Kometa Summary Info
Page 04: Kometa Config.yml YAML Validation ❌
Page 05: Rec 01 - 💥 [CRITICAL]
Page 06: Rec 02 - 💥 YAML ERROR
Page 07: Rec 03 - ❌🛠️ INCOMPLETE LOGS
Page 08: Rec 04 - ⚠️ MEMORY RECOMMENDATION

Page 1/8

[cobalt stream]

Error points to an issue starting at line 5 and becoming apparent at line 25:

| YAML Error: while parsing a block mapping                                                          |
|         in "//config/config.yml", line 5, column 5                                                 |
|       expected <block end>, but found '-'                                                          |
|         in "//config/config.yml", line 25, column 5                                                |

The error is because of this :

    overlay_files:
    - file: config/overlays/media_info.yml
    template_variables:
      use_combined: false
      use_audio: false
    - file: config/overlays/audience_rating.yml            # This is a file within Kometa's defaults folder

which should be:

    overlay_files:
    - file: config/overlays/media_info.yml
      template_variables:
        use_combined: false
        use_audio: false
    - file: config/overlays/audience_rating.yml            # This is a file within Kometa's defaults folder

[pure copper]

thank you i'll try that now

its now saying this

[ocean viper]

📝 If you want to review this again, b_7869:
: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> 📝

[cobalt stream]

Note the indentation of overlay_files

YAML is a file format where indentation is significant.

[pure copper]

i moved it back into line with the rest of the -

[cobalt stream]

What you have now is invalid for a different reason.

[cobalt stream]

Why?

[pure copper]

thought i needed it to be all in line

like how it is for collection_files

[undone tinsel]

It does, but it's not in line with collection_files. Move overlay_files back 2 spaces (to the left) for both instances.

[pure copper]

I was messing around with it before and this how I currently have it

[feral crest]

Screenshot Usage

Please avoid posting screenshots of text-like log output or your yaml configurations. They are very hard to read to find errors and we cannot scroll through the text to see other context. Post actual text instead, formatted with code-blocks (type !code for more info on this).

If you feel that it's too long, you can directly attach the entire file to your Discord message

Thanks for using Kometa

[pure copper]

log for this one

[ocean viper]

📝 If you want to review this again, b_7869:
: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> 📝

**User Info**

Author of Linked Message: b
Person who Invoked the Command: Antwan
File Name: meta.log

Table of Contents:
Page 01: User Info
Page 02: Kometa Info
Page 03: Kometa Summary Info
Page 04: Kometa Config.yml YAML Validation ❌
Page 05: Rec 01 - 💥 [CRITICAL]
Page 06: Rec 02 - 💥 YAML ERROR
Page 07: Rec 03 - ❌🛠️ INCOMPLETE LOGS
Page 08: Rec 04 - ⚠️ MEMORY RECOMMENDATION

Page 1/8

[undone tinsel]

Nope, the indentation is wrong.

[ocean viper]

❌ YAML validation failed! YAML checked and is NOT valid.

Error message:

while scanning a block scalar
  in "<unicode string>", line 198, column 65:
     ...                                 |   File "/modules/request.py",  ... 
                                         ^
expected a comment or a line break, but found 'F'
  in "<unicode string>", line 198, column 69:
     ...                             |   File "/modules/request.py", line ... 
                                         ^

[undone tinsel]

Somehow some traceback stuff got added to the config ??? Here is the config with everything lined up the way it should be

[pure copper]

Thank you I will try and paste this in

[undone tinsel]

Just copy everything up to the settings part or it will overwrite all your api keys

[pure copper]

its running now. Thank you!

[pure copper]

Just going to let this run end and then I will close the post. Or should i close it now and open another one if theres another issue?

[undone tinsel]

I'd say let it run and if everything is okay then close it.