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.

Sign up for GitHub

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

Jump to bottom

Assets with long paths fails to build on linux. #17834

Open
pijaro opened this issue Apr 25, 2024 · 3 comments
Open

Assets with long paths fails to build on linux. #17834

pijaro opened this issue Apr 25, 2024 · 3 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/major Major priority. Work that should be handled after all blocking and critical work is done. sig/content Categorizes an issue or PR as relevant to SIG Content. sig/core Categorizes an issue or PR as relevant to SIG Core

Comments

@pijaro
Copy link
Contributor

pijaro commented Apr 25, 2024

Describe the bug
AssetProcessor on Linux (Ubuntu) returns an error when building an asset with a path longer than 260 chars.

Assets required
Any asset that has a path length > 260.

Steps to reproduce
Steps to reproduce the behavior:

  1. Create a project with a very long path.
  2. Run an asset processor for an asset that lives in the project.

Expected behavior
All assets are built correctly.

Actual behavior
Assets with long paths fail to build. The example error is:

AssetProcessor: JOB LOG: 25 Apr 2024 08:26:34 | ERROR | Cannot copy file: Product '/ver/long/path/to/asset/materialgraphname_mainpipeline_forwardpass_baselighting.azsl' path length (265) exceeds the max path length (260) allowed on disk from Error

Found in Branch
point-release/23103

Desktop/Device (please complete the following information):

  • Device: PC
  • OS: Ubuntu 22.04
  • CPU Intel 13th gen
  • GPU RTX 3070
  • Memory 32GB

Additional context
The asset processor max path length is set to 260 (source), even for OSes that should be able to handle longer paths. Maybe the limit should only exist for Windows OSes?
@pijaro pijaro added kind/bug Categorizes issue or PR as related to a bug. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 25, 2024
@kh-huawei
Copy link
Contributor

There is a preliminary fix here: #17719

@michalpelka michalpelka added sig/content Categorizes an issue or PR as relevant to SIG Content. sig/core Categorizes an issue or PR as relevant to SIG Core priority/major Major priority. Work that should be handled after all blocking and critical work is done. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 25, 2024
@spham-amzn
Copy link
Contributor

This should be fixed with #17719

@spham-amzn
Copy link
Contributor

@pijaro Can you verify this is fixed with the latest from the development branch?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/major Major priority. Work that should be handled after all blocking and critical work is done. sig/content Categorizes an issue or PR as relevant to SIG Content. sig/core Categorizes an issue or PR as relevant to SIG Core
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@michalpelka @pijaro @spham-amzn @kh-huawei