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

Desktop not compiling if directory path contains a space #9396

Closed
ruggi99 opened this issue Mar 28, 2020 · 7 comments · Fixed by #9861
Closed

Desktop not compiling if directory path contains a space #9396

ruggi99 opened this issue Mar 28, 2020 · 7 comments · Fixed by #9861
Assignees
Labels
bug Confirmed bugs or reports that are very likely to be bugs electron Issues related to our use of Electron that may need updates to Electron or upstream fixes priority-3 Bugs that affect small number of users and/or relatively cosmetic in nature

Comments

@ruggi99
Copy link
Contributor

ruggi99 commented Mar 28, 2020

Describe the bug

If path of Desktop repo contains a space, then Desktop is not compiled, returning an error.

Version & OS

Github Desktop: development branch, OS: Windows 10

Steps to reproduce the behavior

  1. Compile Desktop with yarn build:dev

Expected behavior

Compiling without error.

Actual behavior

Generates an error (image below) during compile.

Screenshots

Cattura

Additional context

If path doesn't contain spaces (in my case) it compiles correctly.
If the error isn't repairable, I suggest to add a note in "docs/contributing/setup.md".
Or add the same note into troubleshooting section.

@rafeca rafeca added bug Confirmed bugs or reports that are very likely to be bugs priority-3 Bugs that affect small number of users and/or relatively cosmetic in nature labels Mar 30, 2020
@rafeca rafeca self-assigned this Mar 30, 2020
@rafeca
Copy link
Contributor

rafeca commented Mar 30, 2020

Thanks for the report! I've been able to reproduce the issue on my Window 10 VM

@ruggi99
Copy link
Contributor Author

ruggi99 commented Mar 30, 2020

How will this issue be fixed?

@rafeca
Copy link
Contributor

rafeca commented Mar 30, 2020

@ruggi99 I'm doing some quick investigation since the error comes from electron-packager: I'm checking whether this is something that we can fix in Desktop or it's a bug on electron-packager. I'll give more details soon.

@rafeca
Copy link
Contributor

rafeca commented Mar 30, 2020

@ruggi99 looks like this is a known problem with electron-packager (see electron/packager#1120).

The issue got fixed a few days ago by electron/packager#1139, once a new version gets published with the fix we'll upgrade to it.

@ruggi99
Copy link
Contributor Author

ruggi99 commented Mar 30, 2020

@rafeca thank you for investigating this issue.

@billygriffin billygriffin added the electron Issues related to our use of Electron that may need updates to Electron or upstream fixes label Mar 30, 2020
@ruggi99
Copy link
Contributor Author

ruggi99 commented May 22, 2020

@rafeca how about opening a PR to update only the cross-zip dependency and close this issue? I know it's not the best practice to edit manually the yarn.lock file, but I think it won't break anything.

@rafeca
Copy link
Contributor

rafeca commented May 25, 2020

Sounds good to me as a temporary fix, so feel free to send the PR!

Note that electron-packager is moving away from cross-zip to extract-zip (see electron/packager#1139), but either way upgrading cross-zip to v3.1.0 should be fine now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs electron Issues related to our use of Electron that may need updates to Electron or upstream fixes priority-3 Bugs that affect small number of users and/or relatively cosmetic in nature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants