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

XOD fails to load if Google Drive sync is in progress #1597

Closed
Cesar-S opened this issue Dec 22, 2018 · 1 comment · Fixed by #1600
Closed

XOD fails to load if Google Drive sync is in progress #1597

Cesar-S opened this issue Dec 22, 2018 · 1 comment · Fixed by #1600

Comments

@Cesar-S
Copy link
Contributor

Cesar-S commented Dec 22, 2018

Error EPERM

If a synchronization is in progress, a temporary file is created that XOD does not recognize, this prevents a normal start. Topic in forum

eperm

Environment

  • Scope: desktop IDE
  • Version: 0.25.3
  • OS: Windows 10

Steps to reproduce

  1. Install Google Drive
  2. Make new synchronization, folder XOD (workspace)
  3. Open XOD
@Cesar-S Cesar-S changed the title error EPERM(GDrive) no load XOD error EPERM(Google Drive) no load XOD Dec 22, 2018
@nkrkv nkrkv changed the title error EPERM(Google Drive) no load XOD XOD fails to load if Google Drive sync is in progress Dec 24, 2018
@nkrkv
Copy link
Member

nkrkv commented Dec 24, 2018

Thanks for creating the issue. Will fix it in the nearest bug hunting session.

To the developers: a possible solution is skipping special names when enumerating files/directories in xod-fs. The special names coming into my mind are:

  • .* — hidden files on Posix (will fix GDrive)
  • *~ — backups
  • thumbs.db — Windows image index

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants