Xiaochen Wang

We provide docker images only for ghcr.io (github image stores) currently. You can check it [here](https://github.com/orgs/alibaba/packages?repo_name=tengine). Note that these images had been used for our CI/CD workflow, it had almost...

yeah they were generated by github dockerhub automatically. You can modify our script and create ur own image from these scripts: ``` 1 build and test tengine on ubuntu https://github.com/alibaba/tengine/blob/master/.github/workflows/ci.yml...

Could you provide us with a minimal reproducible example? For instance, utilize the curl command to replicate the unsuccessful request, along with specific nginx configuration details. From the tcpdump package...

Another potentially valuable suggestion could involve referencing the [debug log](http://nginx.org/en/docs/debugging_log.html) for nginx/tengine. This would significantly enhance our ability to address the issue effectively. This would greatly speed up the problem...

HINT: By setting the SameSite attribute to None, you are essentially telling the browser that the cookie can be sent with any request, regardless of the origin. This means that...

> 添加串行更新指令，让nginx的每个进程串行更新upstream。具体为设置flag原子变量，当且仅当进程ngx_worker==flag时，该进程才有权加锁更新。 这个行为和nginx的mutex try lock行为一致。内部实现也是将pid存在lock上，如果被其他进程枷锁后则本进程无法强到锁。dyups有个指令可以开启这个功能。你可以试一下，看看是否满足你的需求：https://github.com/alibaba/tengine/blob/master/docs/modules/ngx_http_upstream_dyups_module.md#dyups_trylock This behavior is consistent with the mutex locking behavior used by nginx. The internal implementation stores the process ID (PID) of the process that currently...

> > 这个行为和nginx的mutex try lock行为一致。内部实现也是将pid存在lock上，如果被其他进程枷锁后则本进程无法强到锁。dyups有个指令可以开启这个功能。 > > @chobits 只是有个问题，极端场景下，某个或者某几个进程可能一直ngx_shmtx_trylock失败，这样不能保证在规定时间内100%的进程得到更新，甚至最坏情况下，某些进程ngx_shmtx_trylock从来没有成功过。 > > 而串行更新能够保证在规定的时间内所有进程完成更新，所有进程更新完毕时间为worker_processes*dyups_read_msg_timeout。 > > There is just one problem. In extreme cases, one or more processes may fail `ngx_shmtx_trylock` all...

You can check that debug log to help debug, and there is no step to reproduce, otherwise developers could not give deep advice. 你可以开启debug log来帮助排查，并且最好附上复现步骤，否则开发者无法给出深度建议

I convert this PR to draft. There are some compilation error found by test cases. If your pr is ready to review, click `ready to review` in this page.

TODO: also need to create documentation for this feature