Follow-up from "Create diagnostic which suggests uninstalling chromedriver"
Overview
The following discussion from !3426 (merged) should be addressed:
-
@vitallium started a discussion: (+2 comments) nitpick (non-blocking): Since we call
chrome_driver_installedjust once we can omit memoization here.
Impacted categories
The following categories relate to this issue:
-
gdk-reliability - e.g. When a GDK action fails to complete. -
gdk-usability - e.g. Improvements or suggestions around how the GDK functions. -
gdk-performance - e.g. When a GDK action is slow or times out.
Steps to replicate (optional)
Proposal (optional)
Environment (optional)
- Operating system name:
<!-- output of `uname -a` command --> - Architecture:
<!-- output of `arch` command --> - The contents of your
gdk.yml(if any) - Ruby version:
<!-- output of `ruby --version` command --> - GDK version:
<!-- output of `git rev-parse --short HEAD` command -->