bitspill

Here's a simple id translation based on the table from the migration at https://github.com/gamedig/node-gamedig/blob/master/MIGRATE_IDS.md I think something like this could be tied into the db migration to handle id transformations...

I'm seeing similar behavior, once a segment gets moved from the tier_0 ramdisk to the tier_1 nas it's no longer viewable from the timeline The files do successfully move to...

> Could you enable debug logging for storage, let it run until such a move occurs and then attach the logs here? > > Would be helpful if you could...

Footer states `Viseron - dev - ce9c781` Startup logs till the stack trace from above https://gist.github.com/bitspill/96288426916ece2381d87bcf3baab382 Testing config ``` ffmpeg: camera: camera_1: name: camera_1 host: 192.168.0.102 port: 554 path: /ch01/0...

> Did you pull `dev` again and made sure to recreate the container? I just did and it still works fine yea, I'm running via a Portainer managed docker stack...

Alrighty, Monday I'll nuke the whole LXC and do a fully fresh docker install and then a fresh viseron on top. Somethings gotta be cached weird.

> I found the issue that is causing the tier check exception. Looking for a fix asap. > > [#1068 (comment)](https://github.com/roflcoopter/viseron/issues/1068#issuecomment-3148709811) oh awesome, hopefully it's not too complicated to fix....

A brief skim of https://maikuolan.github.io/Vulnerability-Charts/python.html looks like there's a few CVE after 3.11.8 but don't think they apply to this project [CVE-2023-52425](https://nvd.nist.gov/vuln/detail/CVE-2023-52425) xml parsing [CVE-2024-45490](https://github.com/advisories/GHSA-4hvh-m426-wv8w) xml parsing [CVE-2024-4030](https://security.snyk.io/vuln/SNYK-UNMANAGED-PYTHON-6814534) windows only...

PR #7492 has been opened to silently proceed through prompts when stdin is not an interactive terminal