2768:00d820d5241b | 27-Mar-2024 |
Ippolitov Igor |
Fix tag for 1.32.1-1. |
Revision tags: 1.32.1-1 |
|
2766:e1697591d345 | 26-Mar-2024 |
oxpa |
Merge tag '1.32.1' into packaging
Unit 1.32.1 release. |
2765:5e31d3ff500a | 27-Feb-2024 |
Dan Callahan |
Merge tag '1.32.0' into branches/packaging
Unit 1.32.0 release. |
2764:9918e21815bc | 15-Mar-2024 |
Andrei Zeliankou |
Added version 1.32.1 CHANGES |
2763:680f233bfe5d | 15-Mar-2024 |
Andrei Zeliankou |
Generated Dockerfiles for Unit 1.32.1 |
2762:4c50cc739e94 | 15-Mar-2024 |
Andrei Zeliankou |
Edited changes.xml for the 1.32.1 release |
2761:f51b9c5cc2dc | 07-Mar-2024 |
Andrew Clayton |
Wasm-wc: Fix application restarts
Liam reported a problem when trying to restart wasm-wasi-component based applications using the /control/applications/APPLICATION_NAME/restart endpoint.
The applic
Wasm-wc: Fix application restarts
Liam reported a problem when trying to restart wasm-wasi-component based applications using the /control/applications/APPLICATION_NAME/restart endpoint.
The application would become unresponsive.
What was happening was the old application process(es) weren't exit(3)ing and so while we were starting new application processes, the old ones were still hanging around in a non-functioning state.
When we are terminating an application it must call exit(3).
So that's what we do. We use the return value of nxt_unit_run() as the exit status.
Due to exit(3)ing we also need to now explicitly handle the return on error case.
Reported-by: Liam Crilly <liam@nginx.com> Fixes: 20ada4b5c ("Wasm-wc: Core of initial Wasm component model language module support") Closes: https://github.com/nginx/unit/issues/1179 Tested-by: Liam Crilly <liam@nginx.com> Tested-by: Danielle De Leo <d.deleo@f5.com> Co-developed-by: Dan Callahan <d.callahan@f5.com> Signed-off-by: Dan Callahan <d.callahan@f5.com> Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
show more ...
|
2760:d21b2f76865e | 11-Mar-2024 |
Andrei Zeliankou |
Tests: NJS cacheable variables with access log
Reproduces issue https://github.com/nginx/unit/issues/1169. |
2759:375cdded2f5f | 06-Mar-2024 |
Zhidao HONG |
Var: Fix cacheable issue for njs variable access
The variables accessed with JS template literal should not be cacheable. Since it is parsed by njs engine, Unit can't create indexes on these variabl
Var: Fix cacheable issue for njs variable access
The variables accessed with JS template literal should not be cacheable. Since it is parsed by njs engine, Unit can't create indexes on these variables for caching purpose. For example:
{ "format": "`{bodyLength:\"${vars.body_bytes_sent}\",status:\"${vars.status}\"}\n`" }
The variables like the above are not cacheable.
Closes: https://github.com/nginx/unit/issues/1169
show more ...
|
2758:e95731b7c811 | 15-Mar-2024 |
Andrei Zeliankou |
Version bump |
Revision tags: 1.32.0-1, 1.32.0 |
|
2707:1d63b0ce2394 | 15-Feb-2024 |
Andrei Zeliankou |
Added version 1.32.0 CHANGES |
2706:5f5001fcc15a | 15-Feb-2024 |
Andrei Zeliankou |
Generated Dockerfiles for Unit 1.32.0 |
2705:319bf153ef44 | 15-Feb-2024 |
Andrei Zeliankou |
Edited changes.xml for the 1.32.0 release |
2704:9c1f10db8375 | 23-Feb-2024 |
Dylan Arbour |
Update setup-go to v5
Removes deprecation notices on actions builds. v5 updates the version of node and `cache: false` disables the errors related to not finding a go.sum |
2703:1432b0266c01 | 22-Feb-2024 |
Dylan Arbour |
Add PHP 8.2 and 8.1 to test matrix
`setup-php` action was fixed to add embed SAPI for older versions of PHP |
2702:ae8b55fd206b | 22-Feb-2024 |
Konstantin Pavlov |
Packages: Pass CFLAGS to compile wasm modules on all packaging targets
This extends the approach used for debian-based packages in 3f805bc64e28 to rpm as well. Notable change for both deb and rpm p
Packages: Pass CFLAGS to compile wasm modules on all packaging targets
This extends the approach used for debian-based packages in 3f805bc64e28 to rpm as well. Notable change for both deb and rpm packaging is to use CFLAGS as defined in the build/Makefile, and not pass them from the environment which might not be there (as is the case for rpm).
While at it, stop passing CFLAGS in the install phase, as it should no longer invoke builds (see d54af163c46b).
The rpm part was overlooked in 7a6405566c0, since testing was not done on the platforms where problem manifested itself, notably Amazon Linux 2023 and Fedora 38+.
show more ...
|
2701:26b04fc757e4 | 22-Feb-2024 |
Dylan Arbour |
Remove debug from builds and tests
The info and above errors should be more than enough for debugging failures in GitHuB Actions CI. |
2700:859302d7f6a5 | 19-Feb-2024 |
Sergey A. Osokin |
Update third-party java components to their recent versions
Acked-by: Timo Stark <t.stark@nginx.com> [ Remove trailing '.' from subject line - Andrew ] Signed-off-by: Andrew Clayton <a.clayton@nginx
Update third-party java components to their recent versions
Acked-by: Timo Stark <t.stark@nginx.com> [ Remove trailing '.' from subject line - Andrew ] Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
show more ...
|
2699:a0f7b03b5ab6 | 22-Feb-2024 |
Andrew Clayton |
Wasm-wc: Use the cargo build output as the make target dependency
cargo build creates the language module under src/wasm-wasi-component/target/release/libwasm_wasi_component.so and not build/lib/uni
Wasm-wc: Use the cargo build output as the make target dependency
cargo build creates the language module under src/wasm-wasi-component/target/release/libwasm_wasi_component.so and not build/lib/unit/modules/wasm_wasi_component.unit.so which is what we were using as a target dependency in the Makefile which doesn't exist so this resulted in the following
$ make wasm-wasi-component-install cargo build --release --manifest-path src/wasm-wasi-component/Cargo.toml Finished release [optimized] target(s) in 0.17s install -d /opt/unit/modules install -p src/wasm-wasi-component/target/release/libwasm_wasi_component.so \ /opt/unit/modules/wasm_wasi_component.unit.so
I.e it wanted to rebuild the module, after this patch we get the more correct
$ make wasm-wasi-component-install install -d /opt/unit/modules install -p src/wasm-wasi-component/target/release/libwasm_wasi_component.so \ /opt/unit/modules/wasm_wasi_component.unit.so
This is all a little ugly because we're fighting against cargo wanting to do its own thing and this wasm-wasi-component language module build process is likely going to get some re-working anyway, so this will do for now.
Reported-by: Konstantin Pavlov <thresh@nginx.com> Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
show more ...
|
2698:a5d2b2aad2d5 | 22-Feb-2024 |
Andrew Clayton |
Wasm-wc: Add nxt_unit.o as a dependency in the auto script
Rather than calling make itself to build nxt_unit.o make nxt_unit.o a dependency of the main module build target.
Reported-by: Konstantin
Wasm-wc: Add nxt_unit.o as a dependency in the auto script
Rather than calling make itself to build nxt_unit.o make nxt_unit.o a dependency of the main module build target.
Reported-by: Konstantin Pavlov <thresh@nginx.com> Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
show more ...
|
2697:9ff760287fdc | 22-Feb-2024 |
Konstantin Pavlov |
Packages: added wasm-wasi-component module packaging for rpm-based distros |
2696:4110f0243b12 | 22-Feb-2024 |
Konstantin Pavlov |
Packages: added wasm-wasi-component module packaging for deb-based distros
We need to redefine CFLAGS to drop missing-prototypes as warning since third-party code such as wasmtime fails to build fro
Packages: added wasm-wasi-component module packaging for deb-based distros
We need to redefine CFLAGS to drop missing-prototypes as warning since third-party code such as wasmtime fails to build from source when building a debian package. This happens only for packages because we use DPKG_EXPORT_BUILDFLAGS=1 propagating build flags to the environment, so cargo build picks it up as well. Since we have no control over third-party code, the easiest solution is to disable this warning.
show more ...
|
2695:4c9ad19be663 | 07-Feb-2024 |
Andrei Zeliankou |
Tests: renamed test_python_procman.py since it's not Python-specific
Python applications are used only to generate responses here and can be replaced by applications written in any other language.
Tests: renamed test_python_procman.py since it's not Python-specific
Python applications are used only to generate responses here and can be replaced by applications written in any other language. While the "_python" prefix is used to indicate that the file contains tests specific to the Python module.
show more ...
|
2694:c11223916183 | 07-Feb-2024 |
Andrei Zeliankou |
Tests: skip some of TLS reconfiguration tests under AddressSanitizer
These tests cause router crash when run with AddressSanitizer:
=================================================================
Tests: skip some of TLS reconfiguration tests under AddressSanitizer
These tests cause router crash when run with AddressSanitizer:
================================================================= ==77196==ERROR: AddressSanitizer: heap-use-after-free on address 0x60c000079340 at pc 0x55d56b132d4b bp 0x7f8cc7f346b0 sp 0x7f8cc7f346a0 READ of size 1 at 0x60c000079340 thread T1 #0 0x55d56b132d4a in nxt_openssl_conn_io_shutdown src/nxt_openssl.c:1466 #1 0x55d56b0f6a25 in nxt_h1p_closing src/nxt_h1proto.c:2069 #2 0x55d56b1009a6 in nxt_h1p_shutdown src/nxt_h1proto.c:2038 #3 0x55d56b1014c3 in nxt_h1p_request_close src/nxt_h1proto.c:1718 #4 0x55d56b1045c0 in nxt_http_request_close_handler src/nxt_http_request.c:864 #5 0x55d56b104988 in nxt_http_request_done src/nxt_http_request.c:795 #6 0x55d56b0ba0c3 in nxt_event_engine_start src/nxt_event_engine.c:542 #7 0x55d56b0dcac2 in nxt_router_thread_start src/nxt_router.c:3645 #8 0x55d56b0b421b in nxt_thread_trampoline src/nxt_thread.c:126 #9 0x7f8ccab95ac2 (/lib/x86_64-linux-gnu/libc.so.6+0x94ac2) #10 0x7f8ccac2784f (/lib/x86_64-linux-gnu/libc.so.6+0x12684f)
show more ...
|
2693:0b7afe1ba8d8 | 07-Feb-2024 |
Andrei Zeliankou |
Tests: check for the AddressSanitizer flag during discovery
This flag is necessary to either run or skip certain tests that have specific behavior depending on whether AddressSanitizer is enabled.
Tests: check for the AddressSanitizer flag during discovery
This flag is necessary to either run or skip certain tests that have specific behavior depending on whether AddressSanitizer is enabled.
For instance, some tests may fail only when the binary is compiled with AddressSanitizer.
show more ...
|