chore(deps): bump libc from 0.2.146 to 0.2.155

[znley]

Description

Motivation and Context

How Has This Been Tested?

Screenshots / Logs (if applicable)

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation (no code change)
• Refactor (refactoring production code)
• Other

Checklist:

• My code follows the code style of this project.
• I have updated the documentation accordingly.
• I have formatted the code with rustfmt.
• I checked the lints with clippy.
• I have added tests to cover my changes.
• All new and existing tests passed.

[orhun]

I'd rather have this more explicit by updating the versions in Cargo.toml as well. Did you just run cargo update?

[znley]

@orhun Yes, I just run cargo update to upgrade Cargo.lock. My main purpose is upgrade libc to 0.2.155 to build and run systeroid on loongarch64-alpine-linux-musl.

[orhun]

I see, then can you make the necessary changes in Cargo.toml (e.g. env_logger) or make this PR only scoped to update libc?

[znley]

@orhun Ok, I upgrade libc only, I think edit Cargo.lock is enough.