This is an automated email from the ASF dual-hosted git repository.
zstan pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/ignite-nodejs-thin-client.git
discard fa2a0ba Merge pull request #10 from JohnSColeman/master
omit 85ff8ca Reject in-flight request when detached finalize throws; drop
Promise.finally in specs
omit ac6092a Drop the version bump from this bug-fix PR
omit bfcf03d Return an empty array from Cursor._getValues() on exhaustion
omit 0fd725b Dispatch _finalizeResponse off the processing queue to avoid
deadlock
omit 92a22d6 Fail fast on response stream desync instead of discarding the
frame
omit 54c6032 Clarify per-message buffer comment: copy happens in
MessageBuffer.from
omit 28b76f3 Build per-message buffer only on the matched-request path
omit b5e735e Warn (not silently discard) on response frame with unmatched
request id
omit bd33cba Use MessageBuffer.getSlice() helper when carving per-message
buffer
omit 952ce79 Fix BaseCursor _id typing and hasMore() on empty results
omit 86a7ed1 fix defects bump version to 1.1.1
omit 2031e68 IGNITE-18520 Await cluster start by logs in tests
omit dc5fd9f IGNITE-18520 Await cluster start by logs
omit bfd0be0 IGNITE-19421 Added extended debug logging of client
connections
omit 341bb01 IGNITE-19421 Added extended debug logging of client
connections
omit 8e8c376 Merge pull request #7 from apache/ignite-15759
omit 8701f16 IGNITE-15759 Replace local affinity function with the custom
one
omit 618d032 IGNITE-17389 Increase test node startup timeout
omit a664d1b IGNITE-17389 Increase test node startup timeout
omit 4669930 IGNITE-16651 Use ignite-log4j2 logger instead of deprecated
ignite-log4j
new 0c7c3c7 IGNITE-17389 Increase test node startup timeout
new fb71360 IGNITE-15759 Replace local affinity function with the custom
one
new fce3c8a IGNITE-19421 Added extended debug logging of client
connections
new a538d74 IGNITE-18520 Await cluster start by logs
new df0fe4c IGNITE-14550 Fix four bugs in ClientSocket, Cursor and Errors
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (fa2a0ba)
\
N -- N -- N refs/heads/master (df0fe4c)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 5 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
