Skip to content

fix: Use platform-aware chromedriver path for cross-OS compatibility#130

Draft
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/daily-code-quality-938f
Draft

fix: Use platform-aware chromedriver path for cross-OS compatibility#130
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/daily-code-quality-938f

Conversation

@cursor
Copy link
Copy Markdown
Contributor

@cursor cursor Bot commented May 2, 2026

Problem

The bot hardcoded chromedriver.exe as the chromedriver binary name, which fails on Linux systems (including the Docker container) where the binary is named chromedriver without the .exe extension.

Solution

  • Detect the operating system using platform.system()
  • Use chromedriver.exe on Windows, chromedriver on Unix-like systems (Linux, macOS)
  • Maintains the existing fallback mechanism for robustness

Impact

  • Fixes bot initialization failures on Linux/Docker environments
  • Improves containerization reliability
  • No breaking changes to existing functionality
Open in Web View Automation 

- Detect OS using platform.system() to determine correct chromedriver binary name
- Use 'chromedriver.exe' on Windows and 'chromedriver' on Unix-like systems
- Fixes issues with Linux/Docker environments where .exe extension causes failure
- Maintains existing fallback mechanism for robustness

Co-authored-by: Ongun Demirag <ongun@ongundemirag.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant