This is an automated email from the ASF dual-hosted git repository.
hanahmily pushed a change to branch v0.2.0
in repository
https://gitbox.apache.org/repos/asf/skywalking-banyandb-java-client.git
discard 074e163 Add more UTs
discard 36e5c96 Update banyand image
discard c3ff352 Bump up proto files
add f950804 Remove powermock and update mockito (#19)
add f46410c Bump up proto files
add 97b9e0c Update banyand image
add 62200d6 Add more UTs
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 (074e163)
\
N -- N -- N refs/heads/v0.2.0 (62200d6)
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.
No new revisions were added by this update.
Summary of changes:
.github/workflows/ci.yaml | 23 ++++++++++++++++++----
pom.xml | 14 +------------
.../v1/client/AbstractBanyanDBClientTest.java | 2 +-
.../v1/client/BanyanDBClientMeasureQueryTest.java | 7 +------
.../v1/client/BanyanDBClientStreamQueryTest.java | 7 +------
.../v1/client/BanyanDBClientStreamWriteTest.java | 2 +-
.../banyandb/v1/client/grpc/ExceptionTest.java | 2 +-
.../v1/client/grpc/channel/ChannelManagerTest.java | 10 +++++-----
.../IndexRuleBindingMetadataRegistryTest.java | 5 -----
.../metadata/IndexRuleMetadataRegistryTest.java | 5 -----
.../metadata/MeasureMetadataRegistryTest.java | 5 -----
.../v1/client/metadata/PropertyStoreTest.java | 7 +------
.../metadata/StreamMetadataRegistryTest.java | 5 -----
13 files changed, 31 insertions(+), 63 deletions(-)
