René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Recursive call: RangeError: Maximum call stack size exceeded when deleteOnExpire:false","articleBody":"Hi\r\n\r\nThis is a specific case when deleteOnExpire:false and try to use has/get function in  .on(\"expired\", (key,value) =\u003e callback)\r\n\r\nHere is a small sample code to test the behaviour\r\n\r\n```\r\nimport NodeCache from 'node-cache';\r\n\r\nconst myCache = new NodeCache({checkperiod:10,deleteOnExpire:false});\r\nmyCache.on( \"set\", ( key, value ) =\u003e console.log(\"On SET \"+ key + '=' + value));\r\nmyCache.on( \"del\", ( key, value ) =\u003e console.log(\"On DEL: \"+ key + '=' + value));\r\nmyCache.on( \"expired\", ( key, value ) =\u003e {\r\n        console.log(\"On EXPIRED \"+ key + '=' + value);\r\n        //myCache.set(key, value+'_',10); // \u003c-- Uncommenting will work, commenting this line will crash process due to either of below lines causing recursion \r\n        let test1 = myCache.has(key); //\u003c--\r\n        let test2 =myCache.get(key); // \u003c-- \r\n});\r\n\r\nmyCache.set(\"MyKey\",\"MyValue\",5);\r\n\r\n//Below code is dummy/sample long running code.... \r\nlet done =1;\r\n(function wait () {\r\n   if (done) setTimeout(wait, 1000);\r\n})();\r\n\r\n```\r\n\r\n─$ node test.mjs\r\nOn EXPIRED MyKey=MyValue\r\nOn EXPIRED MyKey=MyValue\r\nOn EXPIRED MyKey=MyValue\r\n.... \r\nOn EXPIRED MyKey=MyValue\r\nnode:internal/console/constructor:309\r\n        if (isStackOverflowError(e))\r\n            ^\r\n\r\nRangeError: Maximum call stack size exceeded\r\n    at console.value (node:internal/console/constructor:309:13)\r\n    at console.log (node:internal/console/constructor:380:26)\r\n    at NodeCache.\u003canonymous\u003e (file:///Users/raxitsmacbook/MyNodeRnd/test.mjs:7:10)\r\n    at NodeCache.emit (node:events:514:28)\r\n    at NodeCache._check (/Users/raxitsmacbook/MyNodeRnd/node_modules/node-cache/lib/node_cache.js:659:16)\r\n    at NodeCache.has (/Users/raxitsmacbook/MyNodeRnd/node_modules/node-cache/lib/node_cache.js:575:52)\r\n    at NodeCache.\u003canonymous\u003e (file:///Users/raxitsmacbook/MyNodeRnd/test.mjs:9:22)\r\n    at NodeCache.emit (node:events:514:28)\r\n    at NodeCache._check (/Users/raxitsmacbook/MyNodeRnd/node_modules/node-cache/lib/node_cache.js:659:16)\r\n    at NodeCache.has (/Users/raxitsmacbook/MyNodeRnd/node_modules/node-cache/lib/node_cache.js:575:52)\r\n\r\nNode.js v18.17.1 (However it looks like this behaviour is independent of Node version, Just in case if version can be of any help.)\r\n\r\nPossible bug also in: mget when  deleteOnExpire:false\r\n\r\nAlso when deleteOnExpire:false it constantly emits \"expired\" event on every 'checkperiod' times. (But it does not crash, But nice to have non-periodic expire event unless the object/key/value/expiry etc has been modified.","author":{"url":"https://github.com/raxitsheth","@type":"Person","name":"raxitsheth"},"datePublished":"2023-09-06T18:50:29.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/313/node-cache/issues/313"}