openresty / openresty/openresty.org
ngx.worker.id () is always 0 on windows
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 293
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 2
Description
openresty version 1.19.3.1
nginx.conf worker_processes 4;
init_worker_by_lua_file resty_test/init.lua;
init.lua
ngx.log(ngx.ERR, "init worker: ",ngx.worker.id()) -- It's ngx.worker.id() always zero here
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the report using the shown nginx.conf and resty_test/init.lua with OpenResty 1.19.3.1 on Windows, starting at the init_worker_by_lua_file entry point. Compare ngx.worker.id() behavior with worker_processes 4 and determine the expected result; the issue is complete when the Windows behavior is resolved or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, nginx
- Domain
- backend, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100