Pavel Sergeev

Selections are also affected by this issue: unable to retrieve a tuple from the `lua` space with the specified key: ```lua tarantool> box.space.users.index.pk:select(nil, {limit=1})[1][1] --- - 0 ... tarantool> box.space.users.index.pk:select({0},...

Since the configuration discovery process is somewhat complex, it would be helpful to have a log message (debug-level) detailing the location of the found configuration file.

Why do we need to chdir to the application directory and create one more env there? Why is this a popular scenario?

> let's forbid to work like this in documentation Cannot be forbidden due to `cartridge-cli` compatibility. > Do we have any statistics or independent research on non-tt developers which scenarios...

Add a diagnostic message in verbose mode (`-V` option) about invocation of other `tt` executable.

This issue is due to post-build script invocation. It must be invoked in the `pack` command after building an app and use temporary app directory as a working dir for...

This functionality shoudl be supported additionally to `.gitignore` for the scenarios if the application is not a git repo. My suggestion is to support `.packignore` file with list of files/dirs...

> @psergee is it duplicate of #843 or another problem? It looks like other issue. `tt` must take base dir base as an app name. Anyway, don't understand the purpose...

> Хотелось бы чтоб промпт команды connect был красным на проде и все Как программно отличить прод от не-прода?

> This command, unexpectedly for me, erased the replicaset config for me, and for a long time I could not understand what was happening. I assumed that it read etcd...