You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description: We encountered an issue where, after creating a long video and performing file integrity checks, if a new session is initiated and the request is routed to the same Chrome pod, the video recorder sidecar (which was previously handling the file integrity check) does not immediately start recording. This results in the recording not starting as expected and causes downstream issues.
Attempted Fix: We attempted to resolve this by running the wait_for_file_integrity function in the background (by appending the & symbol to the command). This solution was mainly for logging purposes, as the function doesn't perform any additional actions if the file is corrupted.
Question: Do you foresee any potential issues or unintended side effects with this fix?
Thanks in advance for your insights!
Command used to start Selenium Grid with Docker (or Kubernetes)
@nipun1999, thank you for creating this issue. We will troubleshoot it as soon as we can.
Info for maintainers
Triage this issue by using labels.
If information is missing, add a helpful comment and then I-issue-template label.
If the issue is a question, add the I-question label.
If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable G-* label, and it will provide the correct link and auto-close the
issue.
After troubleshooting the issue, please add the R-awaiting answer label.
I guess the issue is after upload (using rclone command move by default), file didn't exist anymore for func check file integrity to work properly. Let me check on this.
What happened?
Description: We encountered an issue where, after creating a long video and performing file integrity checks, if a new session is initiated and the request is routed to the same Chrome pod, the video recorder sidecar (which was previously handling the file integrity check) does not immediately start recording. This results in the recording not starting as expected and causes downstream issues.
Attempted Fix: We attempted to resolve this by running the wait_for_file_integrity function in the background (by appending the & symbol to the command). This solution was mainly for logging purposes, as the function doesn't perform any additional actions if the file is corrupted.
Question: Do you foresee any potential issues or unintended side effects with this fix?
Thanks in advance for your insights!
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
Operating System
EKS
Docker Selenium version (image tag)
4.30.0-20250323
Selenium Grid chart version (chart version)
No response
The text was updated successfully, but these errors were encountered: