Matt Simerson
Matt Simerson
Since #67 is closed / resolved, shouldn't this be closed?
The obvious workaround is to enable `mod_unique_id`. Can you test and see if this patch resolves it? ```diff diff --git a/server/lib/NicToolServer/Session.pm b/server/lib/NicToolServer/Session.pm index 4b12047..706886a 100644 @@ -316,7 +316,7 @@ sub...
What version of node, and more importantly, node-gyp? I bet if you install newer versions of both, the problem goes away. It works on my M1 MBP. ``` ❯ node...
> A quick fix may be to convert everything to ascii before saving the report Sounds like the right choice, based on my read of RFC 8616. > but this...
Because the data column that stored domains and author info were explicitly declared as ASCII, I think (limited testing) that mysql would have converted any unicode characters to a `?`...
Aware. I'm unlikely to "fix" it. PRs are welcome.
Yes, that is the likely fix. It's needs to be tested.
I'm thinking: 1. make port detection explicit and default to 993. The only way to get a port 143 connection is to ask for it. 2. add a `SSL_verify_mode` setting...
You really don't want to shutdown immediately, else you'll be spawning new node.js processes in a furious tail-chasing exercise. I solve this problem by making the ES cluster redundant so...
If you're installing on an old Elasticsearch 4 cluster, and running node.js 6 (no longer supported by node.js), it should require very little to get working besides applying the included...