Badestrand

Ok not sure if this is 100% proper but seems to work: ```js const {AsyncLocalStorage, AsyncResource} = require('async_hooks') ... class DBQuery extends AsyncResource { constructor() { super('DBQuery') } query(db, sql,...

Okay, I have it down to this now: ```js // helper things const {AsyncLocalStorage, AsyncResource} = require('async_hooks') const asyncLocalStorage = new AsyncLocalStorage() class AsRes extends AsyncResource { constructor() { super('AsRes')...

Node v14.15 and pg 8.6.0

For anyone reading this and waiting, you can use the mostly compatible mysql2 library in the meantime: https://github.com/sidorares/node-mysql2/blob/master/documentation/Extras.md#receiving-rows-as-array-of-columns-instead-of-hash-with-column-name-as-key

Is there any chance this gets solved soon? As I understand this, I have to switch to another library to support logging in with the default root user? The linked...

Seems it would be fixed with the little pull request (1 line added): https://github.com/spite/THREE.MeshLine/pull/134 @spite Could we merge that one to fix this here?

Happy holidays to you too and we will certainly consider this! On Wed, 23 Dec 2020, 19:45 kindaTall wrote: > > 1. > > Appreciate the work you have put...

same and from #172 it seems to be a really prevalent issue.

I now also get the error ``` @notionhq/client warn: request fail { code: 'service_unavailable', message: 'Request timed out waiting to connect to a database. Please try again later.' } ```...

Instinctively I would agree but according to the algorithm description itself at https://super-memory.com/english/ol/sm2.htm it is clear that the interval for an incorrect response is 1. I(1):=1