question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

END Event is not called

See original GitHub issue

Hi,

The end event is not called on my side.

My option is :

  var ProxyLists = require('proxy-lists');
  var options = {
    sourcesBlackList:["coolproxy","proxy-list-org","freeproxylist","new-net-time","blackhatworld","kingproxies","bitproxies","sockslist","proxydb"]
  };
  gettingProxies.on('data', function(proxies) {
   });

  gettingProxies.on('error', function(error) {
  	// Some error has occurred.
  	console.error("ERROR",error);
  });
  gettingProxies.once('end', function() {
  	// Done getting proxies.
    	console.log("END");
  });

Moreover; I have that issue that is showing up

ERROR { Error: unable to verify the first certificate
    at TLSSocket.onConnectSecure (_tls_wrap.js:1032:34)
    at emitNone (events.js:115:13)
    at TLSSocket.emit (events.js:218:7)
    at TLSSocket._finishInit (_tls_wrap.js:633:8) code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE' }

Thank you for your support,

Looking forward to provide you more info if necessary

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:9 (7 by maintainers)

github_iconTop GitHub Comments

2reactions
chill117commented, Jul 25, 2019

Closing this issue as the end event is now sending properly. I’ve created a separate issue for cleaning up the browser tabs in the data-sourcer module: https://github.com/chill117/data-sourcer/issues/17

1reaction
chill117commented, Jul 24, 2019

@stylesuxx

I’ve made significant improvements to the under-lying data-sourcer module - in particular the list-crawler abstract. I have not yet created a new release for proxy-lists module, but I will in the coming days.

Can you please checkout and test the latest proxy-lists master branch and let me know if the situation has improved for you?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Node js file system: end event not called for readable stream
Listen for finish event for writable streams. This is fired when end() has been called and processing of the entry is finished.
Read more >
http request 'end' event not fired #21398 - nodejs/node - GitHub
Hi,. I am using the http request and breakdown the response times using events emitted at different stages of the request/response process.
Read more >
Element: transitionend event - Web APIs - MDN Web Docs
If there is no transition delay or duration, if both are 0s or neither is declared, there is no transition, and none of...
Read more >
Node.js Readable Stream close Event - GeeksforGeeks
The 'close' Event in a Readable Stream is emitted when the stream and any of its hidden resources are being closed This event...
Read more >
Handling and Raising Events | Microsoft Learn
The object that raises the event is called the event sender. The event sender doesn't know which object or method will receive (handle)...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found