Skip to content
This repository has been archived by the owner on Sep 28, 2023. It is now read-only.

Cannot clone on Windows #210

Open
saranshkataria opened this issue Mar 28, 2018 · 4 comments
Open

Cannot clone on Windows #210

saranshkataria opened this issue Mar 28, 2018 · 4 comments
Labels
good first issue Issues that are suitable for first-time contributors. help wanted Issues that need help from contributors to move forward.

Comments

@saranshkataria
Copy link

git clone unable to create file server/mongorestore/data/_Join:mySchedule:_User.bson: Invalid argument

A colon is an invalid character for a Windows file name.

@saranshkataria
Copy link
Author

The : in join files can be replaced with _ according to my understanding or according to stack overflow: https://stackoverflow.com/questions/41430355/mongodump-the-filename-directory-name-or-volume-label-syntax-is-incorrect, archive option could be included to create the db dump. There's an issue at https://jira.mongodb.org/browse/SERVER-13313 which is closed as well that states this has been fixed but I cannot make changes and verify anything since I am unable to clone the repo itself.

@frantic frantic added good first issue Issues that are suitable for first-time contributors. help wanted Issues that need help from contributors to move forward. labels Apr 5, 2018
@frantic
Copy link
Contributor

frantic commented Apr 5, 2018

@saranshkataria would you mind sending a pull request? Or adding a more detailed description of what needs to be done so that someone else can pick it up?

@saranshkataria
Copy link
Author

Have changed the file name and refactored reference in the metadata. Not sure where in the dashboard I should verify if the restore for mySchedule and user have been successfully restored.

@caabernathy
Copy link
Contributor

The schedule data is empty initially. I think renaming the data in the files may cause an issue with the class names. However, you can test this by stopping the server (the one started by the yarn server) command. Then run the server again. This should pick up your new data, even if it's empty. Test by adding something to your schedule via the app.

If your current solution turns out to be an issue, the stackoverflow alternative of creating a file with the archive option sounds like a good alternative.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Issues that are suitable for first-time contributors. help wanted Issues that need help from contributors to move forward.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants