Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Failed to save logs. forbidden path:" error when using the Troubleshoot menu on Windows 11 #1477

Open
ghorsey opened this issue Dec 14, 2024 · 4 comments

Comments

@ghorsey
Copy link

ghorsey commented Dec 14, 2024

** What happened? **

  1. A "Failed to save logs. forbidden path:" error was raised.

What did you expect to happen instead?

  1. The log files to be saved in the specified folder

How can we reproduce the bug? (as minimally and precisely as possible)

  1. Clicked Troubleshoot menu of a workspace.
  2. The "Save Troupblshooting Data" window opened to choose where the data should be saved.
  3. I selected a folder and clicked the "Select Folder" button.

Expected

  1. The log files to be saved in the specified folder

Actual

  1. A "Failed to save logs. forbidden path:" error was raised.

image

Local Environment:

  • DevPod Version: 0.6.5
  • Operating System: windows
  • ARCH of the OS: X64
@pascalbreuninger
Copy link
Member

@ghorsey DevPod now zips the troubleshooting information, does that solve your issue?

@ghorsey
Copy link
Author

ghorsey commented Jan 21, 2025

I can try that out tomorrow.

Is the zip fix in the current release?

@pascalbreuninger
Copy link
Member

Yes it is. Thanks!

@ghorsey
Copy link
Author

ghorsey commented Jan 23, 2025

The pathing looks correct now, but Windows still has an error on 0.6.9 windows x86_64.

The Error I got:

Image

The contents of the action_logs folder:

Image
Note: I recreated the workspace today, so the logs dated 1/23 were created generating the workspace. The file in the error message is not in the freshly generated log files.

I hope this information is helpful to you. Let me know if this warrants a new defect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants