rapidsai / rapidsai/deployment
JIT compilation in cuDF on Kaggle Notebooks is broken
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 15
- Forks
- 41
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 6
Description
Kaggle Notebooks GPU environments have the same problem with JIT compilation as Snowflake does: #729
@ncclementi debugged the issue and came up with solutions for this in this comment: https://github.com/rapidsai/deployment/issues/729#issuecomment-5144897364
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 reading issue #729 and the linked comment from @ncclementi, then reproduce the JIT compilation failure in a Kaggle Notebook GPU environment. Identify which solution applies to Kaggle and verify that JIT compilation works there; the payload names no repository files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100