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

File system error on Windows #1

Closed
carstenhag opened this issue Sep 28, 2017 · 2 comments
Closed

File system error on Windows #1

carstenhag opened this issue Sep 28, 2017 · 2 comments

Comments

@carstenhag
Copy link

carstenhag commented Sep 28, 2017

Hello, I've tried to run pullkee --limit 20 facebook/react on Windows 10 x64 but sadly Pullkee is giving out many errors about not being able to find the path:

2017/09/28 21:49:04 File system error occurred while accessing the cache: open C:\Users\carstenh\AppData\Local\Temp/pullkee_cache/facebook/react/pr10019.json: Das System kann den angegebenen                                                      Pfad nicht finden.
2017/09/28 21:49:04 File system error occurred while accessing the cache: open C:\Users\carstenh\AppData\Local\Temp/pullkee_cache/facebook/react/pr10018.json: Das System kann den angegebenen                                                      Pfad nicht finden.
2017/09/28 21:49:04 File system error occurred while accessing the cache: open C:\Users\carstenh\AppData\Local\Temp/pullkee_cache/facebook/react/pr10025.json: Das System kann den angegebenen                                                      Pfad nicht finden.
2017/09/28 21:49:04 File system error occurred while accessing the cache: open C:\Users\carstenh\AppData\Local\Temp/pullkee_cache/facebook/react/pr10028.json: Das System kann den angegebenen                                                      Pfad nicht finden.

"Das System kann den angegebenen Pfad nicht finden" translates to "The system could not find the specified path".

It probably has something to do with forward slashes being used instead of backslashes?

@kirillrogovoy
Copy link
Owner

@carstenhag Thank you very much for bringing this up!

I believe, this issue has gotten fixed in #2.

I've made a new release - 1.2.1, where it is fixed.

Let me know if you have any further issues.
Please, close the issue if everything works well.

@kirillrogovoy
Copy link
Owner

Closing this issue for inactivity. Let me know if this problem persists for you in the newer releases.

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