Repository navigation
Conversation
The Release workflow triggers on every push to master. On a fork that means semantic-release rewrites the version in pyproject.toml, commits the change to the default branch, tags it and then tries to publish the result to PyPI under the upstream package name. Gate the job on the repository name so forks keep a clean master. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PjZRpyoEfSCLjTx5ctzQmJ
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
df25536 to
ce054d4
Compare
🎯 What: Replaced the
assert self._cmdstatement inAppiumService.is_listening(appium/webdriver/appium_service.py) with an explicitif not self._cmd:check that raisesAppiumServiceError.python -O),assertstatements are stripped out at bytecode compilation time. Leavingassertin production logic allows checks to be bypassed, which could lead to unexpectedTypeErroror unhandled exceptions when calling dependent methods withNonevalues.🛡️ Solution: Replaced
assert self._cmdwith an explicit state validation check that raisesAppiumServiceErrorifself._cmdis empty or uninitialized, and added unit test coverage verifying exception handling.PR created automatically by Jules for task 10549833086463993059 started by @Dor-bl