net.box: fix `on_disconnect` inconsistency with documentation
According to the documentation [1]: > If the trigger function causes an error, the error is logged but otherwise is ignored. However, currently, the `on_disconnect` trigger behaves the same way as the `on_connect` trigger, i.e., the connection is terminated and its state changes to 'error'. Let's fix this inconsistency and log errors from the `on_disconnect` trigger, but otherwise ignore them. Closes #9677 Closes #9797 NO_DOC=<bugfix> 1. https://www.tarantool.io/en/doc/latest/reference/reference_lua/net_box/#lua-function.conn.on_disconnect
Showing
- changelogs/unreleased/gh-9677-netbox-on_disconnect-error-behaviour.md 5 additions, 0 deletions...nreleased/gh-9677-netbox-on_disconnect-error-behaviour.md
- changelogs/unreleased/gh-9797-netbox-on_disconnect-error-hangs-server.md 5 additions, 0 deletions...leased/gh-9797-netbox-on_disconnect-error-hangs-server.md
- src/box/lua/net_box.lua 5 additions, 1 deletionsrc/box/lua/net_box.lua
- test/box-luatest/gh_9309_errors_in_triggers_test.lua 7 additions, 2 deletionstest/box-luatest/gh_9309_errors_in_triggers_test.lua
- test/box-luatest/gh_9677_netbox_on_disconnect_error_behaviour_test.lua 31 additions, 0 deletions...est/gh_9677_netbox_on_disconnect_error_behaviour_test.lua
- test/box-luatest/gh_9797_netbox_on_disconnect_error_hangs_server_test.lua 32 additions, 0 deletions.../gh_9797_netbox_on_disconnect_error_hangs_server_test.lua
Loading
Please register or sign in to comment