Yaroslav Dynnikov

Results 12 issues of Yaroslav Dynnikov

Tarantool version: I've checked * 1.10.7-3-g2eddcb432 * 2.3.3-2-g7eea3a6cb Steps to reproduce: ```lua s = require('socket').tcp_server('127.0.0.1', 3301, function() end) box.cfg({log = '| cat'}) s:close() os.execute('lsof -i :3301') box.cfg({listen = 3301}) ```...

bug

Tarantool version: 2.5.0-16-g9f2819785 (master) Bug description: Tarantool strips output if init script raises an error: ```console $ tarantool test.lua LuajitError: test.lua:1: module 'unknown' not found: no field package.preload['unknown'] no file...

bug

There is too little info about new luarocks-3 features in wiki. E.g. luarocks test (and it's rockspec format) isn't mentioned at all.

docs

CI was built on top of unofficial tarantool/cartridge docker image which we removed recently.

Since you redirect both stdout and stderr to a pipe and capture it together, both should be linebuffered to produce nice output. Here is a PoC: ```lua local ffi =...

Sleeps are nasty. Better use fair system waits instead. Here is an example of parent process waiting for his child to call exec. Parent can even detect if exec failed,...

It's essential and should be a part of public API.

Luatest produces a lot of garbage fds for pipes and unix sockets See https://github.com/tarantool/cartridge/issues/1069

bug

We lack the way to run tests in their personal sandboxes. Nowadays the flow sequence is approximately the following: ```lua require('test1') reqture('test2') test1.before_all() test1.test() test1.after_all() test2.before_all() test2.test() test2.after_all() ``` If...

A nice approach was developed in https://github.com/tarantool/cartridge/pull/1194 (and later used in https://github.com/tarantool/cartridge/pull/1202). Let's use it for the migrations.

feature