invalid literal for int() with base 10

[crisp topaz]

Please complete #938455615741775902 and someone from the community or one of our <@&938443185347244033> members will respond when they're available.

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

[slate pumice]

invalid literal for int() with base 10: '18397,25781,36106'

This issue has been fixed in update 1.18.2, please update to the latest version. Type !update for guidance on updating.

Updating PMM

NOTE: This is addressing UPDATING your current setup, not changing from, for instance, latest to nightly.

The update method depends on how you installed it.

I'm running locally and got the code by downloading the zip file:
Download a new zip file, uncompress it, and move your config dir into that new directory. Reinstall requirements.

This is the "fussiest" method of update.

I'm running locally and retrieved the code via git:

cd DIRECTORY_WHERE_YOU_PUT_PMM
git checkout BRANCH_NAME
git stash
git stash clear
git pull

For BRANCH_NAME, substitute master, develop, or nightly

You may need to reinstall requirements if switching branch or updating to a new major version:
python -m pip install -r requirements.txt

Those stash commands are going to discard any changes you may have made to PMM's own files. If that's a concern, you are probably familiar enough with git to know what you need to do instead.

I'm using docker locally:

docker pull meisnate12/plex-meta-manager:TAG_HERE

replace TAG_HERE with latest, develop, or nightly

Then recreate your container via whatever means you used to create it [docker run, docker-compose, etc.].

I'm using docker on a NAS or some other remote context:

Update the image using whatever means the NAS provides.
Depending on the system, this might be a simple rebuild of the container, or you may need to manually pull the new image first.

Thanks for using Plex Meta Manager!

[regal veldt]

!updategit

[round meteor]

If you are looking for guidance on how to update Kometa, please type one of the following commands

!updategit if you are running Kometa locally (i.e. you cloned the repository using Git)

!updatedocker if you are running Kometa within docker

!updateunraid if you are running docker on Unraid

Moving between branches of Kometa on a local system

NOTE: This is addressing changing from, for instance, latest to nightly.

replace TAG_HERE with latest, develop, or nightly; whichever you want to switch to.

cd DIRECTORY_WHERE_YOU_PUT_KOMETA
git checkout BRANCH_NAME
git stash
git stash clear
git pull
# activate your venv here if you use one

python -m pip install -r requirements.txt

If you use a Virtual Environment [venv], make sure you are running inside your venv prior to running the python -m pip install -r requirements.txt command. Those stash commands are going to discard any changes you may have made to Kometa's own files. If that's a concern, you are probably familiar enough with git to know what you need to do instead.

Thanks for using Kometa