From 3bcc0f5c1151247e2babf0cf10fc3d06af4abd9a Mon Sep 17 00:00:00 2001 From: samdesmondking Date: Tue, 14 Oct 2025 10:43:31 +0200 Subject: [PATCH] feat: added troubleshooting advice for windows SCA issue --- pages/modernization-assessment.md | 3 +++ pages/troubleshooting/troubleshooting.md | 8 ++++++++ 2 files changed, 11 insertions(+) diff --git a/pages/modernization-assessment.md b/pages/modernization-assessment.md index 814fa9e5..69be3888 100644 --- a/pages/modernization-assessment.md +++ b/pages/modernization-assessment.md @@ -100,6 +100,9 @@ You can learn more about the modernization potential of your applications by ana Tidal Code Analysis is performed using our command-line software utility Tidal Tools. The software is available to download [here](https://get.tidal.sh/), and you can learn more about getting started with the tool in our guide [here](https://guides.tidal.cloud/tidal-tools.html). +{: .note } +Tidal Source Code Analysis uses Docker under the hood. There is a [known issue](/troubleshooting.html#windows-source-code-analysis) with Docker where scanning a codebase hosted on a Windows file system will be very time consuming. If you are on Windows, we recommend hosting the sourse code which you will analyze on [WSL](https://learn.microsoft.com/en-us/windows/wsl/about). + Once you have Tidal Tools installed, run the following command and follow the prompts to authenticate with Accelerator. `tidal login` diff --git a/pages/troubleshooting/troubleshooting.md b/pages/troubleshooting/troubleshooting.md index b1543b48..528af97a 100644 --- a/pages/troubleshooting/troubleshooting.md +++ b/pages/troubleshooting/troubleshooting.md @@ -202,6 +202,14 @@ must escape the backslash character with another backslash (which is the escape character), so the string must be as the following: `C:\\Program Files\\Tidal Software\\tidal`. +### Source Code Analysis is slow when the source code is stored on Windows {#windows-source-code-analysis} + +When running Tidal Source Code Analysis on codebases that are stored in a Windows filesystem, you might notice that the process is quite slow - especially on larger codebases. + +The root cause of this issue is that since Source Code Analysis is running in a Linux container, accessing the Windows file system from within this container is very time-consuming. + +For analyzing larger codebases on Windows, we recommend using [WSL](https://learn.microsoft.com/en-us/windows/wsl/about), and hosting the source code inside your WSL environment. + ## Linux troubleshooting {#linux} ### Manage Docker as a non-root user {#docker-non-root}