Support IPROTO_PUSH #133
Milestone
Comments
Totktonada
added a commit
that referenced
this issue
Mar 16, 2020
tarantool-3.ini configuration fails and it seems the reason is gh-133 ('Receiving trash from persistent connect when there was timeout before'). Disabled both tarantool-2.ini and tarantool-3.ini configurations, where persistent connections are used, until the problem will be resolved. Related to #113.
Totktonada
added a commit
that referenced
this issue
Mar 18, 2020
tarantool-3.ini configuration fails and it seems the reason is gh-133 ('Receiving trash from persistent connect when there was timeout before'). Disabled both tarantool-2.ini and tarantool-3.ini configurations, where persistent connections are used, until the problem will be resolved. Related to #113.
Totktonada
added a commit
that referenced
this issue
Mar 19, 2020
tarantool-3.ini configuration fails and it seems the reason is gh-133 ('Receiving trash from persistent connect when there was timeout before'). Disabled both tarantool-2.ini and tarantool-3.ini configurations, where persistent connections are used, until the problem will be resolved. Related to #113.
Totktonada
added a commit
that referenced
this issue
Mar 20, 2020
tarantool-3.ini configuration fails and it seems the reason is gh-133 ('Receiving trash from persistent connect when there was timeout before'). Disabled both tarantool-2.ini and tarantool-3.ini configurations, where persistent connections are used, until the problem will be resolved. Related to #113.
|
Wrongly linked the commit here, it is unrelated. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
box.session.push() in 1.10 impements a new iproto command, IPROTO_PUSH. Please add support for it.
The text was updated successfully, but these errors were encountered: