Swoole | 【Swoole 从入门到实战】学习笔记，从零开始学 Swoole，包括 Swoole Task，Swoole | HTTP library

pcntl_alarm(int $seconds) only has a resolution of seconds. Is there a way in PHP to signal a SIGALRM with a delay of, say, milliseconds? Maybe a posix_kill() with a delay argument?

PS.: I'm aware of Swoole\Process::alarm() from the PECL extension Swoole, but I'm looking for a more bare-bones PHP solution.

I'm having issues getting Laravel Sail to work on new laravel 8 project, I'm on Ubuntu 20.04 LTS , i followed the instructions as explained on Laravel Sails Documentation

What i did so far was :

First i created a new Laravel Project :

I'm very new to the docker technology.

What i'm trying to do, is install the PHP extensions sqlsrv and pdo_sqlsrv from PECL repo. Accordingly to this tutorial:

https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server?view=sql-server-ver15

Before i get data from this repo i install the following php additions:

I'm migrating from Laravel 8 to Laravel 8 + Octane / Swoole. All works fine, but php://input always are empty. Also, I check $_POST and $_SERVER values.

file_get_contents('php://input') is used by AWS SNS Message Validator.

Any alterantive to read php://input?

I installed docker and downloaded an ubuntu distro to run with laravel sail,planing to use swoole php,and made it default,also made wsl version to 2

with docker-compose.yml ready from laravel sail docker-compose.yml:

but every time I try to run the sail up cmd,it gives me this error " Unsupported operating system [MINGW64_NT-10.0]. Laravel Sail supports macOS, Linux, and Windows (WSL2)."

any ideas how to fix this ?

When Swoole is on heavy load and heavy requests I kept getting this Log:

[2021-01-24 16:07:22 *33833.2] NOTICE finish (ERRNO 1005): session#21022 does not exists
[2021-01-24 16:07:22 *33833.2] NOTICE finish (ERRNO 1005): session#21022 does not exists
[2021-01-24 16:07:22 *33833.2] NOTICE finish (ERRNO 1005): session#21022 does not exists
[2021-01-24 16:07:22 *33833.2] NOTICE finish (ERRNO 1005): session#21022 does not exists
[2021-01-24 16:07:39 *33835.4] NOTICE finish (ERRNO 1005): session#21025 does not exists
[2021-01-24 16:07:39 *33835.4] NOTICE finish (ERRNO 1005): session#21025 does not exists
[2021-01-24 16:07:39 *33835.4] NOTICE end (ERRNO 1005): session[21025] is closed

[2021-01-23 14:07:22 *5300.3] NOTICE php_swoole_http_onReceive (ERRNO 1005): session[10002] is closed
[2021-01-23 14:07:22 *5300.3] NOTICE php_swoole_http_onReceive (ERRNO 1005): session[10042] is closed
[2021-01-23 14:08:21 *5326.29] NOTICE php_swoole_http_onReceive (ERRNO 1005): session[10508] is closed
[2021-01-23 14:18:15 *5333.36] NOTICE finish (ERRNO 1005): session#12755 does not exists
[2021-01-23 14:18:15 *5333.36] NOTICE end (ERRNO 1005): session[12755] is closed

In example I send total 500k requests with 1k concurrent requests, it logs this errors and hangs ! And suddenly it hangs !
My server is Centos 7, 8 gigabytes of RAM and 4 cores of CPU.
Swoole is running with 40 workers, + 30 Master-Worker and 8 Reactor.
Even in production this happens too.
Can some one help me or explain me why this happens and maybe how can I solve it?
Thanks.

I have installed php/swoole on my server and configured it using Laravel swoole

Now The problem is everything works fine until total requests per second number increase more than 1000 requests.
Swoole will log an error and not responding to user !
I have set Operating system ulimit number to 50000
But still get same error ! Searching all over internet and find nothing !
Os Centos 7
Server is good enough to handle more than 1k requests per second

If you have any experience about this please share it with me

Note:
When swoole starts, it logs this error too:
set_max_connection: max_connection is exceed the maximum value, it's reset to 1024

I'm trying to understand how are we supposed to manage client in Swoole Websocket Server.

I've MyServer who extends from Swoole\WebSocket\Server, I store in a property the client list, but it seems every single client can only see his own list (with only him in it). So if the client 1 send a message who have to be resent to the client 2, the only I've found is to use the getClientList method and send the message to all clients.

But I want also to "bind" clients between themselves ... Like 1 with 2 only, 3 with 4 a,nd 5 etc.

I use APCu (forced to CLI mode) to communicate client list to all my client, but it seems I've some multi acces problems now.

Isnt a "native" way in Swoole Websocket Server to store information on my client, information who could by read from any client?