ARBS-23 opened a new issue, #42531:
URL: https://github.com/apache/superset/issues/42531

   ### Bug description
   
   When exporting a chart whose name is very long (for example, 250 
characters), the exported ZIP contains a YAML filename in the format 
`{chart_name}_{chart_id}.yaml` that becomes too long for Windows file 
extraction.
   
   As a result, the ZIP export is created successfully, but Windows users 
cannot unzip it.
   
   ### To Reproduce
   
   1. Log in to Superset.
   2. Go to **Charts**.
   3. Export a chart with a name around 250 characters long.
   4. Try to extract the exported ZIP on Windows.
   
   ### Expected behavior
   
   The exported chart package should use a safe filename length so it can be 
extracted on Windows without errors.
   
   ### Actual behavior
   
   The exported ZIP includes a filename like `{chart_name}_{chart_id}.yaml` 
that exceeds Windows path/filename limits, causing extraction to fail.
   
   ### Screenshots/recordings
   
   <img width="1920" height="911" alt="Image" 
src="https://github.com/user-attachments/assets/9c6621be-c90b-4f5b-852a-8300cf45f006";
 />
   <img width="1904" height="867" alt="Image" 
src="https://github.com/user-attachments/assets/0b882599-3c93-4625-bc85-c34215663588";
 />
   
   ### Superset version
   
   6.1.0
   
   ### Python version
   
   3.11
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   This appears to be caused by export filename generation using the full chart 
name plus chart ID, without truncation or sanitization for Windows-compatible 
limits.
   
   A possible fix would be to:
   - truncate exported filenames to a safe maximum length, or
   - use a shorter slug-based naming scheme for chart YAML files inside the ZIP.
   
   This is especially visible on Windows, where extraction fails for long 
filenames even though the export itself succeeds.
   
   ### Checklist
   
   - [x] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [x] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [x] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to