phpfatalerror

No, no one else really uses them, but I upgraded my two composer packages to PHP 8.0, loving the transition from doc block annotations to attributes.

https://packagist.org/packages/thewunder/corma

https://packagist.org/packages/thewunder/croute

PRs welcome!

So right now I'm seeing some odd delays (like 15 minute!) when installing plugins via the supplied elasticsearch-plugin binary. It says it is 100% downloaded then like a crazy amount of time later it says "Continue with installation? [y/N]"

This is on a brand new ec2 instance running Ubuntu 20.04, locally that same prompt is nearly instant.

Anyone else experience slowness?

Github, Twitter, slack, a whole bunch of things aren't working for us right now on Google Fiber in KC.

Anyone know of anybody who isn't out of stock for a behmor drum?

I have the original basket weave drum and it's really getting a ton of holes and needs to be replaced.

So coming from java and PHP, I am used to much more useful stack traces that not only tell you what line of what file something occurred on, but also the calling context of your code.

For example

GraphQLError Cannot read property 'geoPoint' of null 
    src/datasources/BusinessSource.js:206:41 BusinessSource.<anonymous>
    src/datasources/BusinessSource.js:16:58 fulfilled
    internal/process/next_tick.js:228:7 process._tickDomainCallback

So basically the first line of the stack trace is the only one with real value, it's my code with the error.

The second line is transpiled async / await promise machinery (coming from Typescript), and the third line is internal