Claude 0fa10941e1 Handle 409 from editCategory as non-error ...

qBittorrent's /torrents/editCategory endpoint returns 409 (Conflict) when
the category already has the specified save path (no change needed).

This is expected behavior when:
- User hasn't changed download_dir setting since last torrent
- Category already has correct save path

Previously logged as warning with full error stack trace, making it look
like an error when it's actually normal operation.

Changes:
- Check for 409 status code from editCategory
- Log friendly message: 'Category already has save path: /path'
- Only log unexpected errors with console.warn

Now both createCategory and editCategory handle 409 gracefully:
- createCategory 409 = category exists
- editCategory 409 = category already has this path
Both are expected, not errors.

2026-01-28 11:41:57 -05:00

..

app

Fix file copy location to respect configured media directory

2026-01-28 11:41:56 -05:00

components

Initial commit

2026-01-28 11:41:24 -05:00

contexts

Initial commit

2026-01-28 11:41:24 -05:00

lib

Handle 409 from editCategory as non-error

2026-01-28 11:41:57 -05:00

types

Initial commit

2026-01-28 11:41:24 -05:00

middleware.ts

Initial commit

2026-01-28 11:41:24 -05:00