Commit activity
Last 12 weeks · 0 commits
Community health
1 of 6 standards met
28
✓README○License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 7 discussions · Last activity 14y ago
See all on GitHub →
doing 100,000 SETs even with a 1ms timeout produces random results.. the parser could be slightly off, however even when DBSIZE reports back with a large number the AOF contains farrrr less, which is not good :) node's fs.WriteStream seems to be failing
Just realized my favorite redis client needs multi support. Any tips on how to implement it myself?
I discovered a problem, where in out testsuite I'm sending a QUIT (in a test-teardown function) to close the client's connection. If there are outstanding responses from other requests to nedis, you'll see: The problem is, that in connection.js (e.g. https://github.com/visionmedia/nedis/blob/master/lib/connection.js#L152) it is not checked, if the stream is writable or not. I'd like to supply a patch for this problem, but I'd also like to know how you would like it to be solved. Is it correct to just call a wrapper function that will first check before actually doing ? Are there any bad tradeoffs I'm not seeing yet? Best Sebastian
Recent fixes
If you pass as port to , the kernel will choose a random and free unprivileged port. You can select the selected port with .
One-liner to have TTL return seconds instead of milliseconds.
Structured data for AI agents
Repository: tj/nedis. Description: Redis server implementation written with nodejs Stars: 132, Forks: 20. Primary language: JavaScript. Languages: JavaScript (100%). Open PRs: 0, open issues: 7. Last activity: 14y ago. Community health: 28%. Top contributors: tj, aheckmann, grumdrig, janpieper.