Meteor-Community-Packages / Meteor-Community-Packages/raix-push
apn/node_modules/q/q.js
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 505
- Forks
- 191
- PR merge metrics
- No merged PRs in 30d
Description
raix:push@3.1.0-pre.1
when I build a app with the development environment, And send a notification(Meteor.call('serverNotification', 'xx', 'xx') from browser console). But the terminal give me a exception.
```
W20170405-16:32:10.133(8)? (STDERR) /Users/ioobot/.meteor/packages/raix_push/.3.0.2.zh81jy++os+web.browser+web.cordova/npm/node_modules/apn/node_modules/q/q.js:155
W20170405-16:32:10.134(8)? (STDERR) throw e;
W20170405-16:32:10.134(8)? (STDERR) ^
W20170405-16:32:10.134(8)? (STDERR)
W20170405-16:32:10.135(8)? (STDERR) Error: Connect timed out
W20170405-16:32:10.135(8)? (STDERR) at Connection. (/Users/ioobot/.meteor/packages/raix_push/.3.0.2.zh81jy++os+web.browser+web.cordova/npm/node_modules/apn/lib/connection.js:193:36)
W20170405-16:32:10.136(8)? (STDERR) at Timer.listOnTimeout (timers.js:92:15)
=> Exited with code: 1
W20170405-16:32:18.537(8)? (STDERR) WARNING: Push APN is using development key and certificate
```
what's wrong with q.js ?
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 stack trace at npm/node_modules/apn/node_modules/q/q.js:155 and compare it with apn/lib/connection.js:193. Reproduce the failure through Meteor.call('serverNotification', 'xx', 'xx') in the development environment, then determine what change or additional diagnosis is needed for the APN connection timeout; the issue is done when the cause and a concrete fix or clarified scope are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100