oracle / oracle/nosql-node-sdk
TypeError: Cannot destructure property 'proxy' of 'this' as it is undefined.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 14
- Forks
- 6
- Avg merge
- 20m
- Merged PRs (30d)
- 1
Description
I am facing this error while initializing my APP
version : 5.3.3
TypeError: Cannot destructure property 'proxy' of 'this' as it is undefined.
at /root/Desktop/orchestrator-SIT/alinma-orchestrator-sprint6/node_modules/https-proxy-agent/dist/agent.js:86:21
at Generator.next ()
at /root/Desktop/orchestrator-SIT/alinma-orchestrator-sprint6/node_modules/https-proxy-agent/dist/agent.js:8:71
at new Promise ()
at __awaiter (/root/Desktop/orchestrator-SIT/alinma-orchestrator-sprint6/node_modules/https-proxy-agent/dist/agent.js:4:12)
at callback (/root/Desktop/orchestrator-SIT/alinma-orchestrator-sprint6/node_modules/https-proxy-agent/dist/agent.js:85:16)
at Function.writeFieldValue (/root/Desktop/orchestrator-SIT/alinma-orchestrator-sprint6/node_modules/oracle-nosqldb/lib/binary_protocol/protocol.js:165:19)
at Function._writeMapEntries (/root/Desktop/orchestrator-SIT/alinma-orchestrator-sprint6/node_modules/oracle-nosqldb/lib/binary_protocol/protocol.js💯18)
at Function.writeObject (/root/Desktop/orchestrator-SIT/alinma-orchestrator-sprint6/node_modules/oracle-nosqldb/lib/binary_protocol/protocol.js:112:14)
at Function.writeFieldValue (/root/Desktop/orchestrator-SIT/alinma-orchestrator-sprint6/node_modules/oracle-nosqldb/lib/binary_protocol/protocol.js:223:26)
Contributor 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.
Research direction
Start with the reported stack trace in node_modules/https-proxy-agent/dist/agent.js and the serialization calls in node_modules/oracle-nosqldb/lib/binary_protocol/protocol.js, using version 5.3.3 as the reproduction context. Confirm the initialization scenario that triggers the error and determine whether it belongs to this SDK or its dependency; done should include a reproducible case and a verified resolution or clear compatibility guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100