#I think I broke my config

1 messages · Page 1 of 1 (latest)

obtuse bison
jolly harnessBOT
#

Welcome @obtuse bison!

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.

orchid creek
#

can you please drop the log file in?

obtuse bison
jolly harnessBOT
#

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

jolly harnessBOT
# jolly harness
**User Info**

Author of Linked Message: shiftylilbastrd
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 - ⚠️ LEGACY SCHEMA DETECTED
Page 09: Rec 05 - ⚠️ LEGACY SCHEMA DETECTED
Page 10: Rec 06 - 💬 PRE KOMETA YAML

orchid creek
# obtuse bison

reapply_overlays: true should go below your library and not below overlay_files. (2), you shouldn't have this set to true, it should be set to false. even on testing, overlays are already applied as needed

#

like so yaml Movies: reapply_overlays: true collection_files:

#

then in your settings section, you have yaml #timeout: 60 #db_cache: #clean_bundles: false #empty_trash: false #optimize: false timeout: 60 db_cache: clean_bundles: false empty_trash: false optimize: false verify_ssl:, might as well delet the section that's commented

then you also have assets_for_all: true in your settings. this is an operation and not a setting

jolly harnessBOT
#

✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements

orchid creek
#

and in your TV section, anywhere you have overlay_level change to builder_level

main cloudBOT
#

shiftylilbastrd, please use codeblocks when posting things that are found in files like a yaml file. Use !code to learn more.TV Shows: collection_files: # - file: config/tv.yml - pmm: basic overlay_files: reapply_overlays: true - pmm: ribbon - pmm: resolution - pmm: status # Airing, Returning, Ended, Canceled and works with overlay_level show template_variables: horizontal_align: left vertical_align: bottom vertical_offset: 17 overlay_level: show

orchid creek
#

@obtuse bison what is this code for? you need to do the same thing with this that i told you with movies. you need to move reapply_overlays

#

and you should set that to false, setting to true creates plex bloat

obtuse bison
#

Sorry I missed that before. I thought I need to set it to true to correct overlays that were applied before.

#

So should I just remove the reapply line?

orchid creek
#

reapply tells kometa to recreate the poster / overlay everytime. no matter what. Kometa will recreate and reapply overlays as needed when that is set to false

#

you can either delete it or move it where it needs to go and set it to false.

obtuse bison
#

I'm kinda confused thought. some of the stuff you're showing me and telling me to remove I'm not actually seeing in my config, like the commented section.

#

and assets_for_all is alreadfy set to false, not tru as you say

orchid creek
#

the section i am talking about, that is commented and then added added back in. yaml plex: # Can be individually specified per library as well url: (redacted) token: (redacted) #timeout: 60 #db_cache: #clean_bundles: false #empty_trash: false #optimize: false timeout: 60 db_cache: clean_bundles: false empty_trash: false optimize: false verify_ssl:
in the plex area of your config

lost wedge
#

This error:

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

is caused by:

libraries:              # Library mappings must have a colon (:) placed after them
  Movies:
    collection_files:
    - default: decade
      template_variables:
        sep_style: purple
        sort_by: audience_rating.desc
        limit: 25
    #  - file: config/movies.yml
    - pmm: basic
    overlay_files:
    reapply_overlays: true   ## << THIS LINE RIGHT HERE
    - pmm: ribbon
...

remove that line

obtuse bison
#

okay found that

#

I removed it fron the tv and movies section

orchid creek
#

the placement of that line is ultimately what was "breaking" your run

lost wedge
#

^^

obtuse bison
#

line is gone, still not working

orchid creek
#

post a new log

lost wedge
#

With that line in that position your config was no longer valid YAML

#

still not working

Covers way too much ground to be useful

obtuse bison
jolly harnessBOT
#

📝 If you want to review this again, shiftylilbastrd:
: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: shiftylilbastrd
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 - ⚠️ LEGACY SCHEMA DETECTED
Page 09: Rec 05 - ⚠️ LEGACY SCHEMA DETECTED
Page 10: Rec 06 - 💬 PRE KOMETA YAML

orchid creek
lost wedge
#

Indentation is all sorts of wrong.

orchid creek
#

you removed a space in `collection_files:"
and then you added some variables to Ribbon and the wrong indentation. i would recommend a yml aware editor; using a couple of recommended extensions

keen atlasBOT
#
Recommended Text Editors

We highly recommend to use a decent editor software to manage Kometa'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 Kometa cannot read. But not only that, they also make it very hard to visually distinguish the formatting, such as indentation.
Kometa 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 Kometa.

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/Kometa-Team/Kometa/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 Kometa schema (Click on image to get a better view):

obtuse bison
#

I was using the editor in winscp. I'll open it with notepad++

orchid creek
#

i'd still recommend vscode, notepad isn't yml aware and doesn't have the recommended extensions

obtuse bison
#

Then why is it in the perfered list?

#

I do think I may have used tab when I was editing. Fixed all that and it's running again.

orchid creek
#

it isn't preferred

#

it's another option. the preferred is VSCODE

obtuse bison
#

Got it. Thanks for the help folks.

orchid creek
#

vscode is preferred because it is yml aware and has the indent rainbow extension

orchid creek
keen atlasBOT
#

Anything further needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.