Trying to debug message undefined error
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- javascript, node.js
- Domain
- networking
Research direction
Start at defs.js:371 and trace the call chain through pdu.js lines 141 and 160 to smpp.js lines 97 and 130. Reproduce a Session.submit_sm call if possible, inspect the values reaching PDU.encode, and finish with a minimal reproducer or a documented explanation of the missing request context.
Written by the indexing model from the issue text.
Description
We've had a handful of uncaught exceptions in our application. The error stack is shown below. It's quite hard to pin it down using the node uncaughtException handler, as we only have access to the error and not the parameters of the request. Does this suggest anything to you guys?
TypeError: Cannot read properties of undefined (reading 'message')
at PDU.encode (.../node_modules/smpp/lib/defs.js:371:58)
at PDU._filter (.../node_modules/smpp/lib/pdu.js:141:40)
at PDU.toBuffer (.../node_modules/smpp/lib/pdu.js:160:7)
at Session.send (.../node_modules/smpp/lib/smpp.js:97:24)
at Session.submit_sm (.../node_modules/smpp/lib/smpp.js:130:15)
- Dominant language
- JavaScript
- Stars
- 434
- Forks
- 194
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 farhadi/node-smpp
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
MultiprocessingOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in farhadi/node-smpp
Similar issues
-
check:failed logos:add
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
iptv-org/database#38874 · 1 comment ·
Maintainers usually reply within 4 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
githubnext/gh-aw-workshop#5193 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
agent/quality stage/040-covered-by-pr testing
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
cncf/endusers#2031 · 2 comments ·
Maintainers usually reply within 1 day