bug: issue running codemod on windows/wsl

[kevincam3]

Faulty codemod

1. nuxt/4/migration-recipe

Sample code snippets

npx codemod@latest nuxt/4/migration-recipe

Original

npx codemod@latest nuxt/4/migration-recipe
[Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files]

Expected

No errors

Actual

[Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files]

Estimated impact

Numbers about your specific codemod run:

• Total number of files/instances transformed: 0
• Number of files/instances missed by the codemod (FN): All
• Number of files/instances mistakenly transformed (FP): 0

Anything else that helps the community prioritize, e.g.:
I'm running the command on Windows 10 under WSL2. I restarted the computer and immediately ran the command in case something else was running interferring. I stopped Docker as well, but I still get the same error.

Logs:

I don't know where the log file(s) are located

Additional context

[mohab-sameh]

@kevincam3 You can use --logs to generate an error log file. Can you try again and report back?

[kevincam3]

I ran this command. npx codemod@latest nuxt/4/migration-recipe --logs
but I don't see any log file. Where should the log file be saved?

[mohab-sameh]

@DmytroHryshyn and I were not able to reproduce this on Mac and Windows. Could it be possibly caused by docker? By the way, we have a Slack community if you want to hop in and get support over chat.

[kevincam3]

@DmytroHryshyn any idea why the log file is also not being generated or if it should be in some specific location other than the root of the project which is where I am when I run the command. I also I ran the command with docker not running and still the same error

[kevincam3]

Video of the attempt in case something visual stands out.
https://drive.google.com/file/d/1hKel3GL7Aukbwy_QOt4C4xz-89dNQPwM/view?usp=drivesdk

[r4zendev]

Should be fixed by #1241, keeping this issue open for now.