telefonicaid / telefonicaid/iotagent-node-lib
if context broker cannot be reached device is not provisioned
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 90
- Avg merge
- 2h 35m
- Merged PRs (30d)
- 1
Description
i have done only basic tests, but basically, the process of device provisioning freezes until timeout is reached, and the device is not registered.
response should be faster probably. options could be:
- reduce time out so to immediately return error message to user.
- insert contextBroker provisioning in a queue, that when connectivity is restored is actually emptied
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 tracing the device provisioning entry point and the request made when the Context Broker cannot be reached. Reproduce the timeout and determine whether the intended done condition is an immediate error or queued provisioning after connectivity returns; the issue does not identify files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100