-
Notifications
You must be signed in to change notification settings - Fork 11.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[cli] Remove indexer feature for sui
and remove the sui-pg
binary
#19436
[cli] Remove indexer feature for sui
and remove the sui-pg
binary
#19436
Conversation
…his indexer feature to build sui binary
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
|
85582d4
to
7dd4f2c
Compare
@@ -29,15 +29,19 @@ runs: | |||
- name: cargo build | |||
if: env.s3_file_exist == '' # if empty, we have not built and uploaded this binary to s3 yet | |||
run: | | |||
cargo build --bin sui --features indexer | |||
if [[ "${{ inputs.ref }}" == 'devnet' || "${{ inputs.ref }}" == 'testnet' ]]; then |
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.
Note that this is a workaround until we get this code into devnet/testnet branches. When that happens, we need to remove this (a.k.a the workflow will fail anyway).
…#19436) ## Description Recent improvements on GraphQL and Postgres code removed the dynamic linking to `libpq`. Due to this linking (GH actions was linking to postgres@14), we had to have a separate `sui-pg` binary that was built with the `indexer` feature such that one can have access to `sui start --with-indexer` and `--with-graphql` due to the required dependencies to Postgres. This PR removes the `indexer` feature, all the instances of building the binary with `--features indexer` in workflows, actions, etc, and updates the documentation (docs + sui-test-validator crate). This is possible because `libpq` is no longer a dependency that gets dynamically linked to the binary. Note that in order to use those flags, a running Postgres DB is still required just like before. ## Test plan Existing tests. --- ## Release notes Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required. For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates. - [ ] Protocol: - [ ] Nodes (Validators and Full nodes): - [ ] Indexer: - [ ] JSON-RPC: - [ ] GraphQL: - [x] CLI: the `indexer` feature was removed from the `sui` crate as the dynamic linking to `libpq` was removed. Therefore, the `sui-pg` binary will not be part of releases anymore. This `sui-pg` binary was used for starting a network with `--with-indexer` and `--with-graphql` flags. These commands will still work as before and it is still required to have installed a Postgres database. If you used `sui-pg` binary previously, you can simply use `sui` binary from this version on. - [ ] Rust SDK: - [ ] REST API:
Description
Recent improvements on GraphQL and Postgres code removed the dynamic linking to
libpq
. Due to this linking (GH actions was linking to postgres@14), we had to have a separatesui-pg
binary that was built with theindexer
feature such that one can have access tosui start --with-indexer
and--with-graphql
due to the required dependencies to Postgres.This PR removes the
indexer
feature, all the instances of building the binary with--features indexer
in workflows, actions, etc, and updates the documentation (docs + sui-test-validator crate). This is possible becauselibpq
is no longer a dependency that gets dynamically linked to the binary. Note that in order to use those flags, a running Postgres DB is still required just like before. If you used sui-pg binary previously, you can simply use sui binary from this version on.Test plan
Existing tests.
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.
indexer
feature was removed from thesui
crate as the dynamic linking tolibpq
was removed. Therefore, thesui-pg
binary will not be part of releases anymore. Thissui-pg
binary was used for starting a network with--with-indexer
and--with-graphql
flags. These commands will still work as before and it is still required to have installed a Postgres database.If you used
sui-pg
binary previously, you can simply usesui
binary from this version on.