Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

path-trace 1 cell did not pass its check

Open
#874 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
compilers, web-dev

Research direction

The error is a WGSL parsing error in a generated shader, specifically an unexpected '--' operator. Look at the path-trace workload in the test suite, likely under test/ or benchmarks/. Examine the GPU.js kernel generation code that produces WGSL, focusing on how unary minus or subtraction is emitted. Run the specific test to reproduce, then debug the code generation to avoid producing '--' in the output.

Written by the indexing model from the issue text.

Description

A cell reading WRONG or error is a gpu.js bug, not a property of your machine — the same kernel produced the right answer on the other backends. These are worth reporting, and a report with the workload name and your adapter in it is worth several without:
path-trace · webgpu · error

Shader '' parsing error: expected `)`, found "--"
   ┌─ wgsl:57:31
   │
57 │ var user_u_ut : f32 = (user_Ve--0.949999988079071);var user_dt : f32 = (user_et-0.8999999761581421);var user_Qe : f32 = (user_st--0.15000000596046448);var user_Xe : f32 = (((user_u_ut*user_Re)+(user_dt*user_Ie))+(user_Qe*user_Fe));var user_It : f32 = ((((user_u_ut*user_u_ut)+(user_dt*user_dt))+(user_Qe*user_Qe))-0.809999942779541);var user_ot : f32 = ((user_Xe*user_Xe)-user_It);if ((user_ot>0.0)){
   │                               ^^ expected `)`
Image
Dominant language
JavaScript
Stars
15.5k
Forks
663
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gpujs/gpu.js

All issues in gpujs/gpu.js

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.