René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"QueueTimer keeps Node process from terminating gracefully","articleBody":"``` js\nvar client = require('exceptionless').ExceptionlessClient.default;\nclient.config.apiKey = \"***\";\nclient.config.useDebugLogger();\n```\n\nThis program will run and exit as expected. No events are submitted. Console output:\n\n```\n[info] Exceptionless: Processing queue...\nfranks-macbook:Exceptionless.JavaScript Frank$ \n```\n\nWhereas, if we modify the code to submit an event:\n\n``` js\nvar client = require('exceptionless').ExceptionlessClient.default;\nclient.config.apiKey = \"***\";\nclient.config.useDebugLogger();\nclient.submitLog('Test');\n```\n\nThis program will run forever, unless you terminate it by sending SIGINT:\n\n```\n[info] Exceptionless: Enqueuing event: 1456470547394 type=log \n[info] Exceptionless: Processing queue...\n[info] Exceptionless: Sending 1 events to https://collector.exceptionless.io.\n[info] Exceptionless: Sent 1 events.\n[info] Exceptionless: Finished processing queue.\n[info] Exceptionless: Processing queue...\n[info] Exceptionless: Processing queue...\n[info] Exceptionless: Processing queue...\n```\n\nIf we `npm install wtfnode` and call `.dump()`, it clearly shows what's going on: \n\n```\n[WTF Node?] open handles:\n- Sockets:\n  - undefined:undefined -\u003e undefined:undefined\n    - Listeners:\n  - undefined:undefined -\u003e undefined:undefined\n    - Listeners:\n- Timers:\n  - (10000 ~ 10 s) wrapper @ /Users/Frank/Entw..../exceptionless.node.js:242\n```\n\nFrom [Node docs](http://nodejs.org/en/about/): \n\n\u003e In Node there is no such start-the-event-loop call. Node simply enters the event loop after executing the input script. Node exits the event loop when there are no more callbacks to perform. \n\nSo, our timer is the last single callback in Node's event loop and therefore blocks it from exiting. This is probably not an issue for service-like applications, but it sucks for console tools or anything that should just exit when the work is finished.\n\nThoughts:\n- Can we use a shorter timespan for the timer in combination with a `lastEventTimestamp` field?\n- Can we leverage the same private API that `wtfnode` uses to figure out if we are the single reason that the process is still running?\n- How long do we want to wait for events to be submitted if the program has no work to do otherwise, before exiting? Should it wait forever if events cannot be submitted due to network problems? Should it make a difference between InMemory and LocalStorage?\n","author":{"url":"https://github.com/frankebersoll","@type":"Person","name":"frankebersoll"},"datePublished":"2016-02-26T07:23:17.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/42/Exceptionless.JavaScript/issues/42"}