You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both of the callbacks in the `print` wrapper are expected to be called, but
`print` may throw errors, e.g.,
`print(setmetatable({}, {__tostring = error})`, so we need to call it in a
protected environment and execute the 'after' callback even if `print`
throws.
Closestarantool#8136
NO_DOC=bugfix
Both of the callbacks in the `print` wrapper are expected to be called, but
`print` may throw errors, e.g.,
`print(setmetatable({}, {__tostring = error})`, so we need to call it in a
protected environment and execute the 'after' callback even if `print`
throws.
Closestarantool#8136
NO_CHANGELOG=<tarantoolgh-7186 was not released yet>
NO_DOC=bugfix
Both of the callbacks in the `print` wrapper are expected to be called, but
`print` may throw errors, e.g.,
`print(setmetatable({}, {__tostring = error})`, so we need to call it in a
protected environment and execute the 'after' callback even if `print`
throws.
Closes#8136
NO_CHANGELOG=<gh-7186 was not released yet>
NO_DOC=bugfix
Lord-KA
pushed a commit
to Lord-KA/tarantool
that referenced
this issue
Feb 27, 2023
Both of the callbacks in the `print` wrapper are expected to be called, but
`print` may throw errors, e.g.,
`print(setmetatable({}, {__tostring = error})`, so we need to call it in a
protected environment and execute the 'after' callback even if `print`
throws.
Closestarantool#8136
NO_CHANGELOG=<tarantoolgh-7186 was not released yet>
NO_DOC=bugfix
Consider the following snippet:
This code constantly erases the prompt and, AFAIC, the memory allocated in
console_hide_prompt
is also leaked, sinceafter_cb
never gets called:tarantool/src/lua/print.lua
Lines 8 to 14 in a82c246
tarantool/src/box/lua/console.c
Lines 340 to 366 in a82c246
The text was updated successfully, but these errors were encountered: