carboxyl_time-0.0.2 beta regression

[est31]

carboxyl_time version 0.0.2 regressed from stable to beta (full log):

 error: type `signal::FuncSignal<A>` is private
   --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/carboxyl-0.1.2/src/lift.rs:80:28
    |
 80 |             SignalFn::Func(_) => SignalFn::from_fn(move || f(sample_raw(&pclone))),
    |                            ^
 

[est31]

cc @aepsil0n

[petrochenkov]

This is a known regression (see #42125 (comment)).
The issue was actually in carboxyl, not carboxyl_time, and it was fixed in Feb 2016, but carboxyl_time still uses outdated version of carboxyl.

[milibopp]

Ah, this is actually fixed on master and the tagged 0.0.3 version, but I think it has not been published yet to crates.io. Let me do that right away.

[milibopp]

Uhm… okay, this is a bit unfortunate, but I am blocked on rust-lang/cargo#4264. Now I remember why I did not publish this in the first place: same issue, but I did not have time to look into it and forgot about later.

[alexcrichton]

@aepsil0n an issue like rust-lang/cargo#4264 is pretty unlikely to be indicative of a bug in Cargo, are you sure this happens persistently over time? If so would you able to help debug that issue?

[milibopp]

It does happen persistently at least on my machine. (Tried it for the third time now.) I am glad to help out with debugging, if you can tell me what to look for. Meanwhile I should probably try this on another machine.

[alexcrichton]

Hm could you try to attach a debugger when Cargo looks like it hanging and see what the backtrace is? Also, can you try setting RUST_LOG=debug and see if Cargo prints anything useful to know where it's publishing to?

[milibopp]

Uhm, that's weird… I just tried publishing at work and it went fine. I'm starting to suspect that my wifi network at home has an issue. Need to look into this further.

Anyway, the regression should be fixed now.

[alexcrichton]

Thanks @aepsil0n!