mirror of
https://github.com/Second-Hand-Friends/kleinanzeigen-bot.git
synced 2026-08-24 07:41:45 +02:00
92da5f7c70
## ℹ️ Description - Link to the related issue(s): Fixes #1240 - Allow ptrace-restricted Docker and LXC users to omit Chromium's `--test-type` startup flag while preserving the existing default for other users. ## 📋 Changes Summary - Add `browser.suppress_unsupported_flag_warning`, defaulting to `true`. - Warn in recognized Linux containers without `CAP_SYS_PTRACE` when the flag remains enabled. - Document the container configuration, regenerate config artifacts, and cover default, opt-out, runtime propagation, and Linux-specific behavior. ### ⚙️ Type of Change - [x] 🐞 Bug fix (non-breaking change which fixes an issue) - [ ] ✨ New feature (adds new functionality without breaking existing usage) - [ ] 💥 Breaking change (changes that might break existing user setups, scripts, or configurations) ## ✅ Checklist - [x] I have reviewed my changes to ensure they meet the project's standards. - [x] I have tested my changes and ensured that all tests pass (`pdm run test`). - [x] I have formatted the code (`pdm run format`). - [x] I have verified that linting passes (`pdm run lint`). - [x] I have updated documentation where necessary. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Added a browser setting to control Chromium warning suppression, enabled by default. - Added support for disabling the setting in ptrace-restricted Docker or LXC containers to help browser startup succeed. - Added diagnostics and warnings for environments missing the required system capability. - **Documentation** - Documented the new setting, container limitations, and configuration guidance. - **Tests** - Added coverage for configuration validation, container detection, capability handling, and browser launch warnings. <!-- end of auto-generated comment: release notes by coderabbit.ai -->