build error

[jkitchin]

After cloning the repo, the directions to build libsql say to run this:

cargo xtask build

It faile like this. I don't know why it is trying to use [email protected]:Nugine/s3s when the https version is listed

Updating crates.io index
Updating git repository `https://github.com/Nugine/s3s`

error: failed to get s3s as a dependency of package libsql-wal v0.1.0-alpha.1 (/Users/jkitchin/Desktop/libsql/libsql-wal)

Caused by:
failed to load source for dependency s3s

Caused by:
Unable to update https://github.com/Nugine/s3s#29bf39cb

Caused by:
failed to fetch into: /Users/jkitchin/.cargo/git/db/s3s-6bbd859ed1d66d8e

Caused by:
failed to authenticate when downloading repository: [email protected]:Nugine/s3s

• attempted ssh-agent authentication, but no usernames succeeded: git

if the git CLI succeeds then net.git-fetch-with-cli may help here
https://doc.rust-lang.org/cargo/reference/config.html#netgit-fetch-with-cli

Caused by:
no authentication methods succeeded

[mgs255]

I ran into this too. Presumably, if you try and do a git clone on the command line for that repo then your git client is going to prompt for a password? The trick here is to add the ssh key used to authenticate to github to the ssh-agent using ssh-add. I'm on a Mac, then also ran into issues with, neither cmake nor protoc being installed. These are the steps I ran:

$ ssh-add ~/.ssh/id_rsa_personal
$ brew install cmake
$ brew install protobuf
$ cargo xtask test
....
        PASS [   5.720s] libsql_replication::bootstrap bootstrap
        PASS [  20.687s] libsql-wal::flaky_fs flaky_fs
        PASS [  32.029s] libsql-server::tests cluster::large_proxy_query
        PASS [  31.930s] libsql-server::tests cluster::replication::apply_partial_snapshot
  TRY 1 SLOW [> 60.000s] libsql-wal::oracle test_oracle
        PASS [  66.762s] libsql-wal::oracle test_oracle
────────────
     Summary [  76.147s] 445 tests run: 445 passed (1 slow), 6 skipped

[jkitchin]

huh. Maybe it is because I cloned the https version earlier. I tried cloning the git/ssh version and it worked fine. Thanks for the tip. I guess this can be closed now.