GregoryCannon / GregoryCannon/StackRabbit

Got response: Cannot read properties of undefined (reading 'split')

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

Nobody has claimed this yet.

Dominant language
C++
Stars
462
Forks
50
PR merge metrics
No merged PRs in 30d

Description

I'm running the server using npm run start and the program appears to build and run fine however when I try running the httpTest.lua script I get the error

Got response: Cannot read properties of undefined (reading 'split')

It appears to be coming from the following stack trace.

localhost:3000/precompute/00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000001101110000110/L/J/18/0/0/0/0/0/0/X..../false
TypeError: Cannot read properties of undefined (reading 'split')
    at parseUrlArguments (/home/user/projects/StackRabbit/built/src/server/request_parser.js:62:27)
    at RequestHandler.routeRequest (/home/user/projects/StackRabbit/built/src/server/request_handler.js:109:52)
    at /home/user/projects/StackRabbit/built/src/server/app.js:48:40
    at Layer.handle [as handle_request] (/home/user/projects/StackRabbit/node_modules/express/lib/router/layer.js:95:5)
    at next (/home/user/projects/StackRabbit/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/home/user/projects/StackRabbit/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/home/user/projects/StackRabbit/node_modules/express/lib/router/layer.js:95:5)
    at /home/user/projects/StackRabbit/node_modules/express/lib/router/index.js:281:22
    at param (/home/user/projects/StackRabbit/node_modules/express/lib/router/index.js:354:14)
    at param (/home/user/projects/StackRabbit/node_modules/express/lib/router/index.js:365:14)
Full request: 1.81ms

I'm not sure what might be causing this

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

The failure is reported in built/src/server/request_parser.js at line 62, reached through RequestHandler.routeRequest in built/src/server/request_handler.js. Run npm run start and httpTest.lua to reproduce, then inspect the request-parsing inputs used by the split call. Done means the script request is handled without the TypeError.

Written by the indexing model from the issue text.

Assessment

Tech stack
express, javascript, lua, node.js
Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.