Ilya Chekalsky

Вам спасибо :smile:

Hey, I've decided to archive this action as there is a better alternative now available. I've created this action in the very early days of Github Actions and now it's...

Hey, I've decided to archive this action as there is a better alternative now available. I've created this action in the very early days of Github Actions and now it's...

Hey, backend of https://neural.love works with bref too. Our fastest handler is only 40ms in average.

@mnapoli any chance this will be finished soon? In the meantime, is there an option for single-arch builds for at least most popular extensions? (e.g. gd?)

I understand. With reasonable pricing we would love to contribute, but for now it is not that big of a difference for us in migrating to graviton to offset full-scale...

@hwchase17 Hey, any idea when you could approve this fix? Currently this bug affects get-started examples from the documentation. Thank you!

@slact Sorry for silence, problem still persists. I tried monitor redis and it is shows tha everything is OK, SETEX was processed: `"SETEX" "sockets:e5f7c3cca23251fb7394c060c18abbc1:5" "3600" "a:3:{s:4:\"type\";s:15:\"comment created\"....` nginx error log...

After adding the root-level `error_log` it's like only 1/10 requests to sockets are getting 503 with the same error in usual log `nchan: error publishing message (HTTP status code 503)`...

OK, I'll write you later when I will get up new server from scratch with that problem.