Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make other connect timeout test more reliable too #2448

Merged
merged 1 commit into from Nov 15, 2016

Conversation

mscdex
Copy link
Contributor

@mscdex mscdex commented Nov 3, 2016

This is basically #2414 except applied to a recently added test that was merged before #2414.

@mscdex mscdex force-pushed the improve-new-test-reliability branch from 7a272cc to e5c45b7 Compare November 3, 2016 12:40
@mscdex mscdex force-pushed the improve-new-test-reliability branch from e5c45b7 to 4cb1487 Compare November 3, 2016 12:44
@mscdex
Copy link
Contributor Author

mscdex commented Nov 15, 2016

@simov ping

@simov simov merged commit 8c6fd17 into request:master Nov 15, 2016
@simov
Copy link
Member

simov commented Nov 15, 2016

👍

@mscdex mscdex deleted the improve-new-test-reliability branch November 15, 2016 17:55
pulkitsinghal added a commit to ShoppinPal/vend-nodejs-sdk that referenced this pull request Sep 15, 2017
## Motivation
- Some upstream projects that use `vend-nodejs-sdk` were facing strange
issues where long-running use (after 47 minutes or so) led so a situation
where nodejs would just hang after a POST request.
- There weren't any clear CPU or Memory consumption red flags.
- It seemed more like a bad promise chain or failing to invoke a callback
that often leads nodejs into a forever running state and there's nothing
really going on.

## Solution
Look at the [CHANGELOG](https://github.com/request/request/blob/master/CHANGELOG.md)
for `request` and see if any plausible reasons for trying a module update.

1. request/request#2431
2. request/request#2414
3. request/request#2447
4. request/request#2448

This wasn't an exact science but their descriptions seemed to merit
the dependency upgrade as "at least worth a try"

## Consequences
Dropped support for Node 0.10
request/request#2381
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants