Constantine Peresypkin
Constantine Peresypkin
OK, looks like it works as expected finally, all features we discussed here are implemented Will add tests soon
@kitaisreal @alexey-milovidov Done. Tests added, should be ready for review.
I would suspect it all comes from inability to use negative enum ranges. Thus setting `#define MAGIC_ENUM_RANGE_MIN 0` should solve it in CH code...
Will not work for EKS contexts as they have a '/' inside the name ``` current-context: arn:aws:eks:us-east-1:11111111111:cluster/cluster-1 ``` Supporting double-quoted identifiers will help here. Have no idea how it's done...
It just misses even in the middle of log streams too, pretty unreliable.
@JerrySievert @hmarzooq unfortunately the last tests may hard crash v8 or leave it in an unusable state (if it has these vulnerabilities). Which means that the following tests may crash...
@hmarzooq I do have an idea though, make sure that you are really running `make installcheck` using the newly compiled `plv8` extension. Knowing how, err... screwed the usual paths on...
plv8 has no event loop. therefore any `await` will be executed in a sync manner although because plv8 is a trusted environment with no access to outside the postgres it...
hmm, dunno await and async work for me out-of-the-box with new v8 in 3.0alpha but they are not async in any sense what's obviously doesn't work is `setTimeout` and friends,...
it is pretty easy to create some sort of event loop through a postgres background worker process I have even done something like it, but using closed source facilities, so...