Broken build because of mismatched types

[Jasonvdb]

Maybe related to PR

error[E0308]: mismatched types
   --> src/cli/fungible.rs:302:27
    |
302 |                 blinding: blinding_factor,
    |                           ^^^^^^^^^^^^^^^ expected `u64`, found `u32`

warning: use of deprecated item 'std::vec::Vec::<T>::remove_item': Removing the first item equal to a needle is already easily possible with iterators and the current Vec methods. Furthermore, having a method for one particular case of removal (linear search, only the first item, no swap remove) but not for others is inconsistent. This method will be removed soon.
   --> src/contracts/fungible/data/asset.rs:171:21
    |
171 |         allocations.remove_item(&old_allocation).is_some()
    |                     ^^^^^^^^^^^
    |
    = note: `#[warn(deprecated)]` on by default

error[E0308]: mismatched types
  --> src/contracts/fungible/data/outcoins.rs:52:27
   |
52 |                 blinding: entropy,
   |                           ^^^^^^^ expected `u64`, found `u32`

error[E0308]: mismatched types
  --> src/contracts/fungible/data/outcoins.rs:58:27
   |
58 |                 blinding: entropy,
   |                           ^^^^^^^ expected `u64`, found `u32`

error[E0308]: mismatched types
  --> src/util/seal_spec.rs:42:27
   |
42 |                 blinding: entropy,
   |                           ^^^^^^^ expected `u64`, found `u32`

error[E0308]: mismatched types
  --> src/util/seal_spec.rs:48:27
   |
48 |                 blinding: entropy,
   |                           ^^^^^^^ expected `u64`, found `u32`

error: aborting due to 5 previous errors; 1 warning emitted

For more information about this error, try `rustc --explain E0308`.
error: could not compile `rgb_node`.

[rajarshimaitra]

Hi @Jasonvdb. The break is also present in Travis and I am working on the fix.
Maybe consider reopening?

Yes, indeed it's because of PR#24. Probably I missed some checks.

CC @dr-orlovsky

[Jasonvdb]

Hey @rajarshimaitra. I managed to get passed this after rebasing my branch so I just assumed the mistake was on my side and #24 was actually the fix?

[rajarshimaitra]

Hmm, this is not happening in the latest build. It suddenly appeared in my local and tricked me into thinking its an issue. I am still investigating.

[dr-orlovsky]

Sometimes it is required to delete Cargo.lock file and even target dir to get the updated upstream repo dependencies compiled properly