Skip to content
This repository has been archived by the owner on Oct 22, 2024. It is now read-only.

idleTimeout set in the capabilities do not overrides IDLE_TIMEOUT from global variable #82

Open
mihailsaver opened this issue Feb 9, 2022 · 0 comments
Assignees
Labels
Priority: Medium Default priority if nothing else matches Status: Pending Initial issue stage waiting for further evaluation Type: Bug Issues that affect the operation of the software

Comments

@mihailsaver
Copy link

mihailsaver commented Feb 9, 2022

🐛 Bug description

idleTimeout set in the capabilities do not overrides IDLE_TIMEOUT from global variable.

🦶 Reproduction steps

Steps to reproduce the behaviour:

  1. Configure idleTimeout using webgrid:options set it to 900
  2. Check that global IDLE_TIMEOUT set to default value 120
  3. Establish session with webgrid
  4. Send selenium command
  5. Wait

🎯 Expected behaviour

Node should be automatically killed after 900 seconds

🐛 Actual behaviour

Node is killed after 120 seconds

Version
0.8.0

Where did the problem occur?
List the platform on which you encountered the issue.

  • ☸️ Kubernetes

Which browsers cause the bug?

Additional context

@mihailsaver mihailsaver added Priority: Medium Default priority if nothing else matches Status: Pending Initial issue stage waiting for further evaluation Type: Bug Issues that affect the operation of the software labels Feb 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Priority: Medium Default priority if nothing else matches Status: Pending Initial issue stage waiting for further evaluation Type: Bug Issues that affect the operation of the software
Projects
None yet
Development

No branches or pull requests

2 participants