Can we rename file path to avoid error on Windows (which does not support colon in file paths)?

Open
#47 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Domain
operating-systems

Research direction

Start by inspecting the example path under vm-noise-data and search the repository for filenames containing colons. Rename the affected paths to Windows-compatible names, then retry cloning and checkout on Windows to confirm the repository can be checked out successfully.

Written by the indexing model from the issue text.

Description

Error cloning the repository to a Windows machine:

$ git clone https://github.com/Azure/AzurePublicDataset.git
Cloning into 'AzurePublicDataset'...
remote: Enumerating objects: 3801, done.
remote: Counting objects: 100% (113/113), done.
remote: Compressing objects: 100% (41/41), done.
remote: Total 3801 (delta 88), reused 80 (delta 71), pack-reused 3688 (from 1)
Receiving objects: 100% (3801/3801), 97.22 MiB | 29.37 MiB/s, done.
Resolving deltas: 100% (297/297), done.
error: invalid path 'vm-noise-data/test_suite=Flexible_IO_Tester/test_name=Type:_Random_Read_-_IO_Engine:_Linux_AIO_-_Buffered:_No_-_Direct:_Yes_-_Block_Size:_64KB_-_Remote_Disk/vm_lifespan=long/vm_region=eastus/vm_sku=B8ms/unit=IOPS.csv'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

Renaming the files that contain : would resolve the issue.

For example, vm-noise-data/test_suite=Flexible_IO_Tester/test_name=Type:_Random_Read_-_IO_Engine:_Linux_AIO_-_Buffered:_No_-_Direct:_Yes_-_Block_Size:_64KB_-_Remote_Disk/vm_lifespan=long/vm_region=eastus/vm_sku=B8ms/unit=IOPS.csv

@jsfreischuetz

Dominant language
Jupyter Notebook
Stars
1.2k
Forks
186
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/AzurePublicDataset

All issues in Azure/AzurePublicDataset

Similar issues

More Operating Systems issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.