-
Notifications
You must be signed in to change notification settings - Fork 11
Conversation
PR Review ChecklistDo not edit the content of this comment. The PR reviewer should simply update this comment by ticking each review item below, as they get completed. Trivial Change
Code
Architecture
|
pub async fn cleanup_databases(&mut self) { | ||
try_join_all(self.databases.all().await.unwrap().into_iter().map(Database::delete)).await.ok(); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We ignore possible errors that could appear when database is still in all()
but is already deleted.
.factory/automation.yml
Outdated
source tools/start-cluster-servers.sh # use source to receive export vars | ||
bazel test //tests --test_env=ROOT_CA=$ROOT_CA --test_arg=-- --test_arg=behaviour::concept --test_arg=--test-threads=1 --test_output=streamed && export TEST_SUCCESS=0 || export TEST_SUCCESS=1 | ||
tools/stop-cluster-servers.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should make two sets of tests in automation.yml
: one for cluster (test-behaviour-concept-cluster
) and (test-behaviour-concept-core
)
Same pattern for behaviour-typeql
and the rest
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We decided that it's out of the scope now. https://github.com/vaticle/typedb-client-rust/issues/52
.factory/automation.yml
Outdated
source tools/start-cluster-servers.sh # use source to receive export vars | ||
bazel test //tests --test_env=ROOT_CA=$ROOT_CA --test_arg=-- --test_arg=behaviour::connection --test_arg=--test-threads=1 --test_output=streamed && export TEST_SUCCESS=0 || export TEST_SUCCESS=1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've made a comment on typedb/typedb-common#147 to implement root CA & TLS support in the TypeDB runner. I don't think it currently is able to do that.
.factory/automation.yml
Outdated
bazel test //tests --test_arg=-- --test_arg=behaviour::concept --test_arg=--test-threads=1 --test_output=streamed && export TEST_SUCCESS=0 || export TEST_SUCCESS=1 | ||
tools/stop-core-server.sh | ||
source tools/start-cluster-servers.sh # use source to receive export vars | ||
bazel test //tests --test_env=ROOT_CA=$ROOT_CA --test_arg=-- --test_arg=behaviour::concept --test_arg=--test-threads=1 --test_output=streamed && export TEST_SUCCESS=0 || export TEST_SUCCESS=1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
couple more extra --test-threads=1
here and below
What is the goal of this PR?
We implement
UserManager
.What are the changes implemented in this PR?
We implemented:
User
struct andUserManager
As
UserManager
BDD scenarios have to be run ontypedb-cluster
, we changed the default connection inContext
to cluster connection, and run all behaviour tests on cluster. We added waiting to some steps because of eventual consistency oftypedb-cluster
.