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

Foam Janitor ran into an error #1254

Closed
BramBonne opened this issue Jul 7, 2023 · 2 comments
Closed

Foam Janitor ran into an error #1254

BramBonne opened this issue Jul 7, 2023 · 2 comments

Comments

@BramBonne
Copy link

Describe the bug

When running Foam Janitor, I get the following error:

Foam Janitor attempted to clean your workspace but ran into an error. Please check that we didn't break anything before committing any changes to version control, and pass the following error message to the Foam team on GitHub issues: Expected a string TypeError: Expected a string at bw (/home/brambonne/.vscode/extensions/foam.foam-vscode-0.25.0/out/extension.js:60:12355) at /home/brambonne/.vscode/extensions/foam.foam-vscode-0.25.0/out/extension.js:277:405 at async Promise.all (index 1) at async AU (/home/brambonne/.vscode/extensions/foam.foam-vscode-0.25.0/out/extension.js:277:661)

Small Reproducible Example

No response

Steps to Reproduce the Bug or Issue

Run the "Run Janitor" command

Expected behavior

Foam Janitor runs

Screenshots or Videos

No response

Operating System Version

Linux

Visual Studio Code Version

1.78.0

Additional context

No response

@riccardoferretti
Copy link
Collaborator

I can't seem to reproduce it, can you create a small repo I can use to see the error?

@BramBonne
Copy link
Author

I can't seem to reproduce it anymore on my end either. My guess is that it had something to do with my Foam directory being backed by a virtual filesystem that was suffering intermittent connectivity issues, putting it in a weird state. Apologies for the noise.

@BramBonne BramBonne closed this as not planned Won't fix, can't repro, duplicate, stale Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants