[BUG]: noexisting container names are not handled #29

Closed
opened 2026-09-02 14:07:42 +04:00 by max · 0 comments
Owner

📋 Description

Program can't handle non existent container names

🔁 Steps to Reproduce

./venv/bin/python -m audio_splitter.main test_data/png_test.opus test_data/png_test.txt --container nonexistent

Expected Behavior

Clear error about invalid container

Actual Behavior

It passes the container name to FFmpeg which fails

📄 Logs / Screenshots

No response

📦 Audio Splitter Version

commit 25e8c0293e

💻 Operating System

Debian 13

🌍 Browser (if applicable)

No response

📎 Additional Context

No response

Submission Checklist

  • I have searched for existing issues (open and closed) that report the same problem
  • I am using the latest stable release of Audio Splitter
  • I have provided clear steps to reproduce the issue
  • I have included relevant logs or error messages (with sensitive info removed)
### 📋 Description Program can't handle non existent container names ### 🔁 Steps to Reproduce `./venv/bin/python -m audio_splitter.main test_data/png_test.opus test_data/png_test.txt --container nonexistent` ### ✅ Expected Behavior Clear error about invalid container ### ❌ Actual Behavior It passes the container name to FFmpeg which fails ### 📄 Logs / Screenshots _No response_ ### 📦 Audio Splitter Version commit 25e8c0293e4b8bc52984c6c6a1711f98594603d9 ### 💻 Operating System Debian 13 ### 🌍 Browser (if applicable) _No response_ ### 📎 Additional Context _No response_ ### ✅ Submission Checklist - [x] I have searched for existing issues (open and closed) that report the same problem - [x] I am using the latest stable release of Audio Splitter - [x] I have provided clear steps to reproduce the issue - [ ] I have included relevant logs or error messages (with sensitive info removed)
max added the bug label 2026-09-02 14:07:42 +04:00
max changed title from [BUG]: no existing container names are not handled to [BUG]: noexisting container names are not handled 2026-09-02 14:26:48 +04:00
max closed this issue 2026-09-02 15:47:07 +04:00
Sign in to join this conversation.