num-bigint dependency versions causing issues

[andygolay]

🐛 Bug

Reported on X:

"@movementlabsxyz @MovementLabs Heads up - found a num-bigint version conflict in the CLI build. You've got v0.4.4 and v0.2.6 causing type mismatches in Diesel's PG numeric handling. Quick fix would be pinning to 0.4.4 in the deps 🔧"

https://x.com/ateet7tiwari/status/1884317199873237338?s=12&t=tmz-jeomsRJElwoiMA8B5Q

Opening this issue with intent to investigate and will fill out the issue in more detail.

To reproduce

Code snippet to reproduce

# Your code goes here
# Please make sure it does not require any external dependencies

Stack trace/error message

// Paste the output here

Expected Behavior

A clear and concise description of what you expected to happen.

System information

Please complete the following information:

• Aptos Core Version
• Rust Version
• Computer OS

Additional context

Add any other context about the problem here.

[sweatpotato13]

Downgrade bigdecimal to version 0.3.0 by modifying your Cargo.toml:

bigdecimal = { version = "0.3.0", features = ["serde"] }

This should resolve the issue.

[mzabaluev]

Reproduced, it's the movement CLI build that is failing.

Downgrade bigdecimal to version 0.3.0

@sweatpotato13 is this preferred to just updating the diesel dependency (#139)?

[sweatpotato13]

Reproduced, it's the movement CLI build that is failing.

Downgrade bigdecimal to version 0.3.0

@sweatpotato13 is this preferred to just updating the diesel dependency (#139)?

It would be better if you could solve it by updating the diesel dependency

The method I suggested is a temporary solution.

[mzabaluev]

I wish dependencies of the diesel crate weren't so messed up. It should not depend on loose version ranges of num-bigint and bigdecimal when the latter has a more rigid dependency on num-bigint.

[mzabaluev]

The bigint dependencies are optional for diesel; any opinions on whether the CLI really needs these features?