Closed jkbpvsc closed 2 years ago
I just merged fixes to main which makes 0.5.5 work well. We can do git ref as well if you redo the PR with new serum dex
Ok, I changed it, I think this is still preferable, as the version tags are irrelevant for crates imported from git, and just confuse Cargo. Also when you eventually update serum_dex
again, we can avoid this situation.
@acamill Can you make it so UXD composability tests don't fail anymore?
@acamill Can you make it so UXD composability tests don't fail anymore?
Will look into it now
Secrets are not passed to workflows that are triggered by a pull request from a fork @dafyddd issue seems to be that secret won't work for fork PR.
End of may we will have another audit that will yield having the place_perp_order_v2 on mainnet (Still using some derported logic).
Once this is reached, the likelyness of breaking something will be very low, and changes to mangoMarketsV3 shouldn't be plentyfull either with V4 in the work.
I propose to remove the CI until we open source in the coming month, and in the meantime of update the program to use place_perp_order_v2, we can communicate on changes.
Opened #175
Problem
Recently the mango fork of
serum_dex
was merged with the upstream version 0.5.5. The main mango program is importing theserum_dex
package with version0.4.0
from a git repository.If you delete Cargo.lock, the build will fail with
because while Cargo.toml specifies version
0.4.0
, when importing from a git repo, the latest0.5.5
from upstream is used.Fix
Build with
serum_dex 0.5.5
is breakingso as a quick fix, I removed the version from the
serum_dex
and fixated it to the commit before the upstream merge.