quarto-dev / quarto-dev/quarto-cli
Test suite robustness: don't run `seaborn` code
Open
@cscheid is already working on this.
Since Apr 29, 2025.
testing
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Unfortunately, seaborn apparently hits https://raw.githubusercontent.com/mwaskom/seaborn-data/master at every execution. This sometimes makes github angry, and we get 429 too many requests:
- https://github.com/mwaskom/seaborn/blob/master/seaborn/utils.py#L24
- https://github.com/quarto-dev/quarto-cli/actions/runs/14734145448/job/41355843999#step:26:1043
We should remove all seaborn execution from our test suite.
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.
Assessment
This issue has not been assessed yet.