Requesting to export issue tags as a CSV file fails due to large size
Open
Nobody has claimed this yet.
GitHub Team: issue-workflow
Product Area: Issues
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
A user received the message below after trying to export data from the Issues page, I was also able to reproduce this.
For additional details, please see the internal issue.
Expected Result
Data is exported correctly.
Actual Result
Data export wailed with an internal error
Product Area
Issues
Link
No response
DSN
No response
Version
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue-tag CSV export from the Issues page with a dataset large enough to trigger the reported internal error. Trace the export path and the size-related failure, then verify that the same export completes successfully and produces a usable CSV.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100