NVIDIA / NVIDIA/cutlass

[BUG] Filenames too long trip up windows

Open
#3,368 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

? - Needs Triage bug CUTLASS C++ inactive-30d
Dominant language
C++
Stars
10.5k
Forks
2.1k
Avg merge
3d 11h
Merged PRs (30d)
7

Description

Which component has the problem?

Git repo

Bug Report

Describe the bug

The repo contains filenames that make it very easy to trip windows's path limit:

Cloning into 'D:/dev/score-dev/src/addons/score-addon-librediffusion/3rdparty/librediffusion/3rdparty/cutlass'...
error: unable to create file examples/68_hopper_fp8_warp_specialized_grouped_gemm_with_blockwise_scaling/68_hopper_fp8_warp_specialized_grouped_gemm_with_blockwise_scaling_with_sparse_groups.cu: Filename too long

in this case, I ran git clone in d:\dev - D:/dev/score-dev/src/addons/score-addon-librediffusion is a first submodule, and 3rdparty/librediffusion a second, and cutlass a third one so I don't have a lot of power

Steps/Code to reproduce bug

clone in a folder which has a path already ~50 characters long

Expected behavior

git cloning on the average folder on windows works

Environment details (please complete the following information):

  • windows, git bash

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.

Research direction

Reproduce the failure by cloning into a Windows path about 50 characters long, using the nested paths under src/addons/score-addon-librediffusion/3rdparty/librediffusion/3rdparty/cutlass. Inspect the listed CUTLASS example filename and the submodule layout first. Done means the repository can be cloned from an average Windows folder without a filename-too-long error.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, git
Domain
operating-systems, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.