Does not detect repos

Question

Does not detect repos

Closed this issue 2 years ago · 9 comments

Let me know if there's any debug info I can send

Answer 1 · 2022-08-11T14:35:08.000Z

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

repo cmp -f
repo cmp -t
repo cmp -j

This binary should be here

I've around 40 repos in several levels and it takes under 100ms, so something is clearly off above.

Answer 2 · 2022-08-12T08:21:30.000Z

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.

macOS: 12.5
CPU arch: intel

Answer 3 · 2022-08-12T08:59:34.000Z

Thanks for the info.

I cannot paste the output as this is my work laptop and I may inadvertently publish confidential information (project names etc.)

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.

Those commands work when run from iTerm.app, but hang when run from VSCode's terminal.
I guess something is wrong with the default terminal/shell.

Does iTerm and Terminal.app are having same shell ?
Is there any panic or it just hangs ?

Guess it's time add debug mode in binary. I'll make sure it doesn't print any sensitive info.

Answer 4 · 2022-08-12T09:30:00.000Z

Oh yes, forgot to mention, I use fish shell throughout.

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.

Answer 5 · 2022-08-12T15:09:57.000Z

I'll handle the rust 😁. Got some debug builds ready for you here. Let's start with repo cmp -f. In order to print info we require you'll need to run INFO=1 repo cmp -f

Try this in iTerm, Terminal.app and VSCode Terminal. This should tell us where is it getting stuck.

Answer 6 · 2022-08-17T13:12:14.000Z

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.

Answer 7 · 2022-08-23T04:02:54.000Z

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.

Answer 8 · 2022-08-24T08:12:40.000Z

Hi @mohitsinghs Sorry for not getting back to you sooner. Yes, that's working now! Thank you.

Answer 9 · 2022-08-24T09:39:25.000Z

Glad that it worked. This entire time, I forgot that I have an old Macbook 😄, or else I would have fixed it sooner.