TypeError: Nil is not a valid JSON source. (TypeError)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- backend-api-design
Research direction
Start with exercism/tooling_job.rb:37 and trace how Exercism::ToolingJob.find gets its JSON input from app/commands/tooling_job/process.rb and app/controllers/spi/tooling_jobs_controller.rb. Reproduce the request that supplies nil, then check the existing tests for tooling job processing and controller updates. Done means the nil input is handled without raising this TypeError, with a regression test covering the case.
Written by the indexing model from the issue text.
Description
Error
Nil is not a valid JSON source. (TypeError)
new(id, JSON.parse(json))
^^^^
Stack trace
exercism/tooling_job.rb:37 in JSON.parse
exercism/tooling_job.rb:37 in Exercism::ToolingJob.find
app/commands/tooling_job/process.rb:31 in job
mandate/memoize.rb:47 in block (2 levels) in __mandate_memoize
app/commands/tooling_job/process.rb:10 in call
mandate/call_injector.rb:10 in ToolingJob::Process.call
app/controllers/spi/tooling_jobs_controller.rb:4 in update
action_controller/metal/basic_implicit_render.rb:8 in send_action
abstract_controller/base.rb:215 in process_action
action_controller/metal/rendering.rb:193 in process_action
Tracking Details
- Project: exercism-rails
- Sentry: TypeError: Nil is not a valid JSON source. (TypeError)
- Culprit: SPI::ToolingJobsController#update
- First seen: Nov 18, 2026
- Dominant language
- Ruby
- Stars
- 554
- Forks
- 172
- Avg merge
- 20h 23m
- Merged PRs (30d)
- 73
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from exercism/website
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
All issues in exercism/website
Similar issues
-
開発用DockerイメージにPlaywrightのシステム依存を追加するPossibly taken @momocus claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
sakazuki-org/sakazuki#1453 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
jenkins-infra/jenkins.io#9615 · 1 comment ·
Maintainers usually reply within 1 day
-
fix(ocr): compile the Tesseract-free pipeline with Tokio runtimePossibly taken @Goldziher claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Metric tooltips that contradict how the metric is calculatedPossibly taken @aniadeadu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
WikiEducationFoundation/WikiEduDashboard#7303 · 1 comment ·
Maintainers usually reply within 1 day
-
WhatsApp Cloud template sync saves a partial template list when one page of the Graph API response failsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days