Leonid Vasilev

Tests `v24_features.py` and `v26_features.py` fail on Ubuntu 16.04

1

I tried to run the tests `v24_features.py` and `v26_features.py`, but my attempt failed. ``` ┌─[✗]─[leonid@vasya-L460]─[~/work/mail/nginx_upstream_module] └──╼ ./test/v24_features.py [+] Post/Put body [+] Post body - error [+] Body sould not pass...

Supports the ability to connect to a shared session on a replica

3

Now in case of a master switching, we must to re-identify on the new master. Seems like it would be convenient to connect to every instance in a replicaset, identify,...

Refactoring of the queue drivers tests structure

3

Now: Many tests of queue drivers have duplicated code Wish: Have some common tests for drivers (remove duplicate code) Add full testing of a driver API for limfifottl

Add automatic `rockspec` update in https://rocks.tarantool.org on push to master by using https://github.com/tarantool/rocks.tarantool.org

Now `queue.identify()` (https://github.com/tarantool/queue#session-identify) takes `uuid` only in binary format, which is inconvenient in some cases. My suggestions: * Make `identify` capable of getting uuid in any format (binary, string, uuid_obj)...

Right now the README queue is overloaded and difficult to read. I propose to put examples of queue usage in a separate document (which should be expanded later).

Right now the README of queue is overloaded and hard to read. I propose to move the description of the default drivers to a separate document.

Right now the README queue is overloaded and difficult to read. I suggest the following steps to make the situation better: - [ ] tarantool/queue#172 - [ ] tarantool/queue#173 -...

Move the information about `underlying spaces` from the README to a separate document

1

I think the information about `underlying spaces` is technical and can only be of interest to developers, and can be moved to some additional document in the `doc` directory.

Implement lifo and lifottl drivers by analogy with fifo and fifottl drivers. When implementing new drivers, don't need to use the "copy-paste" methodology (WET), the common code must be moved...