StuffAnThings / qbit_manage

This tool will help manage tedious tasks in qBittorrent and automate them. Tag, categorize, remove Orphaned data, remove unregistered torrents and much much more.
MIT License
776 stars 47 forks source link

[Bug]: Config Error: nohardlinks must be a list of categories #332

Closed davralin closed 1 year ago

davralin commented 1 year ago

Describe the Bug

I am struggling with the config, and even after minimizing the config to the bare minimum - based on the migration guide - It's still telling me that nohardlinks must be a list of categories.

I don't use hardlinks, so the best for me would be to disable it entirely - but since I minimized the config so much, and it's still telling me something is wrong - I believe it to be a bug.

The same thing happens if I remove nohardlinks: completely.

Config

commands:
  dry_run: true
  tag_tracker_error: true
  tag_update: true
  recheck: true
  cross_seed: false
  cat_update: false
  rem_unregistered: true
  rem_orphaned: true
  skip_cleanup: false
  tag_nohardlinks: false
  skip_qb_version_check: true
  share_limits: false

qbt:
  host: qbittorrent.media.svc.cluster.local:8080
  user:
  pass:

settings:
  force_auto_tmm: true
  tracker_error_tag: issue
  ignoreTags_OnUpdate:
  - issue
  share_limits_suffix_tag: share_limit

directory:
  root_dir: /data/downloads
  remote_dir: /data/downloads/
  cross_seed:
  orphaned_dir: /data/downloads/orphaned_data
  torrents_dir:

cat:
- movies: "/data/downloads/movie"
- tv: "/data/downloads/tv"

nohardlinks:
- movies
- tv

Logs

https://gist.github.com/davralin/3550e1877dcfb9dc60be4716afbe41cb

Screenshots

No response

Installation

Docker

Version Number

4.0.0 (Docker)

What branch are you on?

master

bobokun commented 1 year ago

I can't seem to replicate this, can you try moving onto the develop branch and see if you have the same issue? I've tried removing the entire nohardlinks section in my config and setting tag_nohardlinks: false with no errors. Can you also try setting your logs to debug by setting QBT_DEBUG=True in your docker env variable?

davralin commented 1 year ago

That ended with: https://gist.github.com/davralin/287cb78b6410bbe14b04da6800b8f0b2

Which is weird, because I don't have something that should end with this: --tag-nohardlinks (QBT_TAG_NOHARDLINKS): True in the second section.

bakerboy448 commented 1 year ago

Post conf again?

tabs vs spaces for your indents maybe?

davralin commented 1 year ago

Still the same config

commands:
  dry_run: true
  tag_tracker_error: true
  tag_update: true
  recheck: true
  cross_seed: false
  cat_update: false
  rem_unregistered: true
  rem_orphaned: true
  skip_cleanup: false
  tag_nohardlinks: false
  skip_qb_version_check: true
  share_limits: false

qbt:
  host: qbittorrent.media.svc.cluster.local:8080
  user:
  pass:

settings:
  force_auto_tmm: true
  tracker_error_tag: issue
  ignoreTags_OnUpdate:
  - issue
  share_limits_suffix_tag: share_limit

directory:
  root_dir: /data/downloads
  remote_dir: /data/downloads/
  cross_seed:
  orphaned_dir: /data/downloads/orphaned_data
  torrents_dir:

cat:
- movies: "/data/downloads/movie"
- tv: "/data/downloads/tv"

Tried running both expand, and unexpand on the file - no difference.

davralin commented 1 year ago

hahaha... I figured it out.

I had both a config.yml, and a config.yaml file in /config.

Actually working with the correct file kinda helps.