Respect Cargo.lock for dependencies version#4028
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
We'd still somehow need to handle the locked version being significantly different from the swss-common version/hash being used in the pipeline (as build artifacts). |
|
with locked, we lose the ability to automatically upgrade dependencies to pick up fixes. Are we going to manually upgrade? |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@qiluo-msft , How about using Cargo.lock in swss, dash-ha repo for UT. When UT passed, PR can be merged into swss repo. |
…1124) This reverts commit 7682785. Following the proper fix sonic-swss (sonic-net/sonic-swss#4028). Now we could bring back the commit. What I did in the PR: Fix several potential crash issues: unwrap() function may crash in runtime. Drop should not crash. Clone should not crash, so remove it. Protect casting Duration
|
Cherry-pick PR to 202511: #4051 |
|
hi @qiluo-msft , I wonder if you could help pick this PR to 202412 as well? |
Why I did it Currently cargo update will update dependencies in the Cargo.lock file to the latest version on the specified branch. The sonic-swss-common Rust code is possibly not aligned with libswsscommon package, which will make sonic-buildimage build fail. How I verified it Verify local sonic-buildimage build passing, even there is sonic-swss-common changes on c-api.
ack |
…onic-net#1118) Following the proper fix sonic-swss (sonic-net/sonic-swss#4028). Now we could bring back the commit. What I did in the PR: Fix several potential crash issues: 1. unwrap() function may crash in runtime. 2. Drop should not crash. 3. Clone should not crash, so remove it. 4. Protect casting Duration
…1136) Following the proper fix sonic-swss (sonic-net/sonic-swss#4028). Now we could bring back the commit. What I did in the PR: Fix several potential crash issues: 1. unwrap() function may crash in runtime. 2. Drop should not crash. 3. Clone should not crash, so remove it. 4. Protect casting Duration Co-authored-by: Vineet Mittal <46945843+vmittal-msft@users.noreply.github.com>
Why I did it Currently cargo update will update dependencies in the Cargo.lock file to the latest version on the specified branch. The sonic-swss-common Rust code is possibly not aligned with libswsscommon package, which will make sonic-buildimage build fail. How I verified it Verify local sonic-buildimage build passing, even there is sonic-swss-common changes on c-api.
Why I did it Currently cargo update will update dependencies in the Cargo.lock file to the latest version on the specified branch. The sonic-swss-common Rust code is possibly not aligned with libswsscommon package, which will make sonic-buildimage build fail. How I verified it Verify local sonic-buildimage build passing, even there is sonic-swss-common changes on c-api. Signed-off-by: Kalash Nainwal <kalash@nexthop.ai>
|
Cherry pick here: Azure/sonic-swss.msft#184 |
Why I did it Currently cargo update will update dependencies in the Cargo.lock file to the latest version on the specified branch. The sonic-swss-common Rust code is possibly not aligned with libswsscommon package, which will make sonic-buildimage build fail. How I verified it Verify local sonic-buildimage build passing, even there is sonic-swss-common changes on c-api.
Why I did it Currently cargo update will update dependencies in the Cargo.lock file to the latest version on the specified branch. The sonic-swss-common Rust code is possibly not aligned with libswsscommon package, which will make sonic-buildimage build fail. How I verified it Verify local sonic-buildimage build passing, even there is sonic-swss-common changes on c-api. Signed-off-by: Baorong Liu <96146196+baorliu@users.noreply.github.com>
What I did
Why I did it
Currently
cargo updatewill update dependencies in the Cargo.lock file to the latest version on the specified branch. The sonic-swss-common Rust code is possibly not aligned with libswsscommon package, which will make sonic-buildimage build fail.How I verified it
Verify local sonic-buildimage build passing, even there is sonic-swss-common changes on c-api.
Details if related