GregoryCannon / GregoryCannon/StackRabbit
'skipping frame' errrors
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 462
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
when i run stackrabbit the output says: 'Skipping frame9
Skipping frame8
Skipping frame7
Skipping frame6
Skipping frame5
Skipping frame4
Skipping frame3
Skipping frame2
Skipping frame1
Skipping frame0
S
reqLines 0
reqLines2 0
http://localhost:3000/get-move-async?board=00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000¤tPiece=S&nextPiece=L&level=19&lines=0&inputFrameTimeline=X.' after that it stops and shows an error
also npm start doesnt work it says '
stackrabbit@1.0.0 start
node-gyp build && tsc && node built/src/server/app.js
gyp info it worked if it ends with ok
gyp info using node-gyp@11.2.0
gyp info using node@22.15.1 | win32 | x64
gyp ERR! build error
gyp ERR! stack Error: You must run node-gyp configure first!
gyp ERR! stack at loadConfigGypi (C:\Users\Lenovo\Downloads\StackRabbit-master\StackRabbit-master\node_modules\node-gyp\lib\build.js:49:15)
gyp ERR! stack at async build (C:\Users\Lenovo\Downloads\StackRabbit-master\StackRabbit-master\node_modules\node-gyp\lib\build.js:36:3)
gyp ERR! stack at async run (C:\Users\Lenovo\Downloads\StackRabbit-master\StackRabbit-master\node_modules\node-gyp\bin\node-gyp.js:81:18)
gyp ERR! System Windows_NT 10.0.26100
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\Lenovo\Downloads\StackRabbit-master\StackRabbit-master\node_modules\node-gyp\bin\node-gyp.js" "build"
gyp ERR! cwd C:\Users\Lenovo\Downloads\StackRabbit-master\StackRabbit-master
gyp ERR! node -v v22.15.1
gyp ERR! node-gyp -v v11.2.0
gyp ERR! not ok '
Contributor guide
No contributing guide indexed for this repository
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 reported Windows failure from the npm start script, which runs node-gyp build, tsc, and built/src/server/app.js, using the reported Node.js version. Then compare that build failure with the later “Skipping frame” output and HTTP request to determine whether they are separate problems. Done means the startup command completes and the stopping runtime error has a clear, reproducible diagnosis.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, node.js
- Domain
- backend, build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100