feat: automatically terminate worker processes when idle timeout has expired#62
Merged
feat: automatically terminate worker processes when idle timeout has expired#62
Conversation
1 task
mato533
force-pushed
the
ta/feat/worker-idle-timeout
branch
from
d96f249 to
ae67feb
Compare
mato533
force-pushed
the
ta/feat/worker-idle-timeout
branch
from
fee4d07 to
66f4c5b
Compare
mato533
force-pushed
the
ta/feat/worker-idle-timeout
branch
from
2b56269 to
93f162e
Compare
mato533
changed the title
10 tasks
mato533
added a commit
that referenced
this pull request
Jun 23, 2025
## Proposed changes Change the startup process for feature extensions. With the initial implementation for worker process startup (controlling the startup process with a semaphore) and the fix for #62 (starting the worker if it was stopped when accessed), there is no longer a need to pre-start all workers. Simplify the logic for the extension startup process and remove unnecessary source code. Additionally, add E2E tests related to changes in the ConfigFilePattern in Settings. ## Types of changes [//]: # 'What types of changes does your code introduce to WebdriverIO?' [//]: # '_Put an `x` in the boxes that apply_' - [X] Polish (an improvement for an existing feature) - [ ] Bugfix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Documentation update (improvements to the project's docs) - [ ] Internal updates (everything related to internal scripts, governance documentation and CI files) ## Checklist [//]: # "_Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code._" - [X] I have read the [CONTRIBUTING](https://github.com/webdriverio/vscode-webdriverio/blob/main/CONTRIBUTING.md) doc - [X] I have added tests that prove my fix is effective or that my feature works - [ ] I have added the necessary documentation (if appropriate) - [ ] I have added proper type definitions for new commands (if appropriate) ## Further comments [//]: # 'If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...' ### Reviewers: @webdriverio/project-committers
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
Types of changes
Checklist
Further comments
Reviewers: @webdriverio/project-committers