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

Git cloning into a mapped directory fails #75

Closed
DustinBrett opened this issue Mar 1, 2022 · 9 comments
Closed

Git cloning into a mapped directory fails #75

DustinBrett opened this issue Mar 1, 2022 · 9 comments

Comments

@DustinBrett
Copy link
Owner

Seems like write and possibly large reads from mapped drives are having issues. If I open a mapped drive in terminal and run git, the folder is made but files are not written.

Repository owner deleted a comment from hello-smile6 Mar 1, 2022
@hello-smile6
Copy link

May be an issue with API support in BrowserFS, I encountered the same issue while attempting to clone a repository using isogit.

@DustinBrett
Copy link
Owner Author

Been digging more into this and starting to think it has something to do with symlinks. It does seem to be partly related to the way isogit wants to use fs which may not be supported with the File System Access API currently.

@hello-smile6
Copy link

Been digging more into this and starting to think it has something to do with symlinks. It does seem to be partly related to the way isogit wants to use fs which may not be supported with the File System Access API currently.

Can you implement symlinks by creating a .symlinks file and reading from it, then creating a Nodejs script to create actual symlinks or update the file?

@DustinBrett
Copy link
Owner Author

I don't think it's possible to make real symlinks via the File System Access API but that is how IsoGit works on most GitHub repos it seems.

@hello-smile6
Copy link

I don't think it's possible to make real symlinks via the File System Access API but that is how IsoGit works on most GitHub repos it seems.

Why not fake it, by creating a file with the locations of would-be symlinks and creating placeholder files where symlinks would be?

@DustinBrett
Copy link
Owner Author

Feel free to give it a go. I think it will be easier said than done that approach. And I also prefer not to fake those kinds of things.

@hello-smile6
Copy link

Feel free to give it a go. I think it will be easier said than done that approach. And I also prefer not to fake those kinds of things.

I have no idea how to.

@hello-smile6
Copy link

Maybe discourse.wicg.io is necessary. Unfortunately, some environments will never support symlinks, so faking it may be the only option.

@DustinBrett DustinBrett modified the milestones: Functional - P1, Functional - P2 Mar 28, 2023
@DustinBrett DustinBrett modified the milestones: P2, P1 May 24, 2023
@DustinBrett DustinBrett modified the milestones: P1, P2 Oct 13, 2023
@DustinBrett
Copy link
Owner Author

I tested this recently and it worked, although it did oddly make my computer slow which was a worry, but it was able to write so progress has been made and I am going to close this for now.

@DustinBrett DustinBrett removed this from the P2 milestone Dec 19, 2023
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

2 participants