Callback never executed for certain URLs
See original GitHub issueSummary
By coincidence, I noticed a URL that leads to request
hanging.
Simplest Example to Reproduce
var x = request({uri: 'http://m.eet.com/content/images/ebnonline/superhero-534120_640_1499288028.jpg'}, function (error, response, body) {
console.log('Hello'); // Callback is never executed
});
Expected Behavior
The callback should be executed in any situation.
Current Behavior
The callback is not executed, ever. I’ve waited for several hours.
Context
I was trying to download the image above.
Your Environment
software | version |
---|---|
request | 2.88.0 |
node | 6.10.3 |
npm | 3.10.10 |
Operating System | Linux archlinux 4.18.9-arch1-1-ARCH, Debian 4.9.82-1 |
Issue Analytics
- State:
- Created 5 years ago
- Comments:12
Top Results From Across the Web
Ajax success callback never executed, parsererror
I'm making a simple AJAX call to a server side PHP script but the success callback is never executed. Instead, under the error...
Read more >Callback function not being executed - ServiceNow Community
I'm trying to use the g_modal.showFrame in a UI action to update a record then after being close run a callback function. Kb0743790...
Read more >Futures and Promises | Scala Documentation
Instead, the callback is executed by some thread, at some time after the future object is completed. We say that the callback is...
Read more >How to make a Promise out of a Callback function in JavaScript
I hear some of you, including my naïve past self, telling me wrap it in an async function then await the callback function....
Read more >Node.js v19.3.0 Documentation
Disable the callbacks for a given AsyncHook instance from the global pool of AsyncHook callbacks to be executed. Once a hook has been...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue does not occur in request version 2.87.0 for me, only 2.88.0. I’ve been able to avoid the issue this way.
The problem must be caused by whatever was changed for this specific update of v2.87.0->v2.88.0 then.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.