In [1]: from ceresdb_client import Client
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
Input In [1], in <cell line: 1>()
----> 1 from ceresdb_client import Client

File ~/.pyenv/versions/3.10.4/envs/brm-api/lib/python3.10/site-packages/ceresdb_client/__init__.py:1, in <module>
----> 1 from .ceresdb_client import *
      3 __doc__ = ceresdb_client.__doc__
      4 if hasattr(ceresdb_client, "__all__"):

ImportError: dlopen(/Users/messense/.pyenv/versions/3.10.4/envs/test/lib/python3.10/site-packages/ceresdb_client/ceresdb_client.abi3.so, 0x0002): symbol not found in flat namespace (_aes_hw_cbc_encrypt)

symbol not found in flat namespace (_aes_hw_cbc_encrypt) looks like the same kind of issue as https://github.com/ray-project/ray/issues/14697, I think it might be caused by misconfiguration of grpc or boringssl when cross compiling from x86_64 macOS to arm64 macOS.

To deliver the sdk to users, We have to upload the package to pypi. What we should do:

• Do the necessary application to pypi.
• Build an automatic upload procedure.

Maybe we should refer to some other famous python project.

Thie project needs CI based on Github Actions to ensure the quality of development. And now about the CI what I can come up with is these jobs:

• python style check
• rust style check: (refer to actions in ceresdb)
  • rustfmt
  • clippy

And as for unit tests, now no unit test in this project has been provided and the test framework of the python project has not been decided yet so I suggest skipping the UT part in the CI for now.

Some users only have a python3.6 environment to run their application, but currently our client doesn't support python3.6 yet.

Let's support python3.6 on a specific branch.

Currently, the installation of protoc has blocked the compiling the python client on windows. After https://github.com/CeresDB/ceresdbproto/pull/32, the installation has been made automatically, that is to say, we don't need to do manual installation of protoc for windows.

After #28, a new version of ceresdbproto has been adopted. However, a new dependency called protobuf has been introduced, leading to the failure of release. Let this pr fix it.

Rationale for this change

Bump to 0.1.3, mainly update the rust-client dependency.

What changes are included in this PR?

• update rust-client dependency.
• bump version to 0.1.3.

Are there any user-facing changes?

None.

How does this change test

CI itself.

Rationale for this change

Now, the rust client can only be used for ceresdb of standalone mode. We should modify it for serving ceresdb of cluster mode.

What changes are included in this PR?

• Update rust client dependency.
• Update python client's correspoding part.

Are there any user-facing changes?

Users can now use client to access ceresdb of cluster mode.

How does this change test

CI itself.

Rationale for this change

The toolchain's version is too old.

What changes are included in this PR?

update toolchain version.

Are there any user-facing changes?

None.

How does this change test

None.

The example link now is a relative path which leads to confuse when it is rendered on the pypi ceresdb-client page.

And this PR change the link of it to absolute path so that the example file can be opened everywhere.