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

[CLOSED] Exclude .git files from console warnings #6616

Open
core-ai-bot opened this issue Aug 30, 2021 · 4 comments
Open

[CLOSED] Exclude .git files from console warnings #6616

core-ai-bot opened this issue Aug 30, 2021 · 4 comments

Comments

@core-ai-bot
Copy link
Member

Issue by zaggino
Wednesday Mar 26, 2014 at 18:45 GMT
Originally opened as adobe/brackets#7332


Ping@iwehrman
Related issues:
adobe/brackets#6803 (edit)
brackets-userland/brackets-git#289


zaggino included the following code: https://github.com/adobe/brackets/pull/7332/commits

@core-ai-bot
Copy link
Member Author

Comment by peterflynn
Wednesday Mar 26, 2014 at 19:10 GMT


@zaggino This is about #6803, right? The issue is more general than just .git folders -- it applies to anything screeened out by the FileSystem watch rot's filter. So we might want to do a more general fix here...

@core-ai-bot
Copy link
Member Author

Comment by zaggino
Wednesday Mar 26, 2014 at 19:19 GMT


Ah yes, this is the same thing. I don't know how to do a more general fix here though. Ideas?

@core-ai-bot
Copy link
Member Author

Comment by iwehrman
Wednesday Mar 26, 2014 at 19:26 GMT


It's probably fine to just remove the warning. It's not an unexpected or, AFAICT, harmful condition.

@core-ai-bot
Copy link
Member Author

Comment by peterflynn
Thursday Mar 27, 2014 at 17:21 GMT


@iwehrman That seems fair too. I'll leave #6803 open though since it seems like ideally, we'd also avoid the cost of attempting to stat each file inside .git (or any other filtered subtree) when there's churn going on in there.

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

1 participant