raft-rs in github is out of sync with the same version in crates.io

[whfuyn]

Hi, I was recently using raft-rs in my project. I added raft-rs = "0.6.0-alpha" in my Cargo.toml, and followed the examples to write my own server. But it turned out some field and methods were missing, like

        s.mut_metadata().mut_conf_state().voters = vec![1]; // no voters
        store.wl().set_conf_state(cs); // no wl

After some painful investigations, I found that the raft-rs in .Cargo/registry/src/github.com.../raft-0.6.0-alpha were different from the one I saw in github, which didn't use voters in the example, and the proto file weren't the same too.

Maybe it needs an update? It really confuses an inexperience user like me since it has the same version.

[Fullstop000]

@whfuyn You can get rid of it by adding things below in your Cargo.toml

[dependencies]
raft = "0.6.0-alpha"

[patch.crates-io]
raft = { git = "https://github.com/tikv/raft-rs", branch = "master", default-features = false }
raft-proto = { git = "https://github.com/tikv/raft-rs", branch = "master", default-features = false }

Though this is just a tmp solution.

[BusyJay]

We are planning release 0.6.0 this month. The current release blocker is #378.

[whfuyn]

@Fullstop000 Thanks! I am using that solution.
Another problem I encountered is the #![rustfmt::skip] in the generated eraftpb.rs that requires #![feature(custom_inner_attributes)], I just manually remove it. Maybe fix it in the next release?

[BusyJay]

@nrc Do you have any idea how to address the problem?

[nrc]

I actually don't know where that rustfmt::skip is coming from? The solution is to not emit it and if necessary use the outer attribute equivalent on the protos module.

[BusyJay]

It's generated by rust-protobuf to avoid formatting generated code.

[nrc]

Fixed in tikv/grpc-rs#479, we'll need to release a new version and to fix things here.

[chen-zhuohan]

Now it's December, where is my release 0.6.0?

[BusyJay]

There is still a known bug in master, we will fix it before releasing. Sorry for the delay, we have been put a lot of effort in the new design of joint consensus and async ready.

[BusyJay]

0.6.0 was just released.