-
Notifications
You must be signed in to change notification settings - Fork 0
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
Does not detect repos #5
Comments
Seems strange to me. This should ideally render instantly. This extension gets it's data from repo binary which is bundled in the extension. There is a bug in case of M1 where this returns nothing and I would like to debug that. Can we check the output of
This binary should be here I've around 40 repos in several levels and it takes under 100ms, so something is clearly off above. |
Those commands work when run from iTerm.app, but hang when run from VSCode's terminal, and interestingly also hang when run from Terminal.app. I cannot paste the output as this is my work laptop and I may inadvertently publish confidential information (project names etc.), but iTerm.app does indeed print a list of git repos in my home directory.
|
Thanks for the info.
Those commands were for you to check the output if we are getting repos, so sharing is not needed at all. Looks like we have the issue in the binary itself. something platform or shell specific.
Guess it's time add debug mode in binary. I'll make sure it doesn't print any sensitive info. |
Oh yes, forgot to mention, I use It just hangs, nothing shown after waiting 30s or so (I just cancel it after that). Happy to help 🙂 Although I'm a JS/TS bod only, so unfortunately I can't help with any Rust code. |
I'll handle the rust 😁. Got some debug builds ready for you here. Let's start with Try this in iTerm, Terminal.app and VSCode Terminal. This should tell us where is it getting stuck. |
Published v0.4.1 of extension. It fixes a bug in binary which caused early exit on traversal. This was affecting macOS. I'm still not sure about root cause of your issue because I tested it in M1 and Intel Macs and it worked fine expect traversal bug. You may give this release a try though. |
Closing this as of now since I am unable to reproduce this and after several fixes, the extension seems to work fine for others on Intel and M1 Macs. Feel free to reopen when we have more info on this. |
Hi @mohitsinghs Sorry for not getting back to you sooner. Yes, that's working now! Thank you. |
Glad that it worked. This entire time, I forgot that I have an old Macbook 😄, or else I would have fixed it sooner. |
Let me know if there's any debug info I can send
The text was updated successfully, but these errors were encountered: