5 Pull requests merged by 2 people

• [5.1]Fix bug #5635

  #5643 merged Jan 1, 2025

• Optimize runtime thread safe

  #5647 merged Dec 31, 2024

• When the process restarts, send a 500 status code to the clients waiting in the queue

  #5644 merged Dec 31, 2024

• [6.0]Fix bug #5635

  #5640 merged Dec 31, 2024

• Refactor co lock

  #5646 merged Dec 30, 2024

9 Issues closed by 2 people

• Swoole 4.6.1、Swoole 5.1.6、Swoole 6.0.0 验证协程客户端PgSql 无异步效果（Swoole 4.6.1, Swoole 5.1.6, Swoole 6.0.0 verify that the coroutine client PgSql has no asynchronous effect）

  #5635 closed Jan 2, 2025

• swoole-6.0.0 and php-8.4 compile error

  #5634 closed Dec 31, 2024

• cURL error 2: Failed initialization

  #5631 closed Dec 30, 2024

• 5.1.6,使用RedisPool高并发出错 ERROR php_swoole_server_rshutdown() (ERRNO 503)

  #5630 closed Dec 30, 2024

• real_escape_string not accept numbers

  #5639 closed Dec 30, 2024

• Add partitioned cookie support

  #5645 closed Dec 30, 2024

• php $start = microtime(true); //set 2s timeout $service = (yield service_center("User")); $service->setTimeout(2); $callId1 = $service->addCall("User::getUsersCache", ['ids' => [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]]); $callId2 = $service->addCall("User::getUser", ['id' => 1]); $res = (yield $service->multiCall()); dump($res[$callId1]); dump($res[$callId2]); dump(microtime(true) - $start);

  #5642 closed Dec 30, 2024

• Please answer these questions before submitting your issue. Thanks! 1. What did you do? If possible, provide a simple script for reproducing the error. 2. What did you expect to see? 3. What did you see instead? 4. What version of Swoole are you using (`php --ri swoole`)? 5. What is your machine environment used (including the version of kernel & php & gcc)?

  #5641 closed Dec 30, 2024

• WARNING ProcessPool::wait(): worker#4 abnormal exit, status=0, signal=11

  #5636 closed Dec 29, 2024

3 Issues opened by 2 people

• $server->setting is NULL in onWorkerStart and onTask callback

  #5651 opened Jan 2, 2025

• Server script starts many times when using Swoole 6

  #5649 opened Dec 31, 2024

• 无法打印协程的bt

  #5648 opened Dec 31, 2024

2 Unresolved conversations

Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.

• Suggestion: Better core logging

  #5278 commented on Dec 27, 2024 • 0 new comments

• Coroutines are leaking

  #5618 commented on Dec 30, 2024 • 0 new comments