[TWiR] Call for Participation

nazmulidris · February 27, 2024, 2:25pm

Hi everyone

Here are some Ockam issues for community contributors:

ockam node create --identity X should fail if X doesn't exist
Output for ockam project ticket is improved and information is not opaque
Output for both ockam project ticket and ockam project enroll is improved, with support for --output json

Thank you

joshlf · February 27, 2024, 6:20pm

Hi all!

A zerocopy issue:

Thanks!

nazmulidris · March 5, 2024, 4:20pm

Hi everyone

Here are Ockam issues for community contributors:

Output for both ockam project ticket and ockam project enroll is improved, with support for --output json
Syntax highlighting for fenced code blocks, in command help output, on Linux works
Command - refactor to use typed interfaces to implement commands for kafka services

Thanks

joshlf · March 5, 2024, 5:33pm

Hi folks!

Some zerocopy issues:

github.com/google/zerocopy

Don't generate warning when deriving on deprecated type

opened 01:35PM - 27 Oct 23 UTC

joshlf

help wanted experience-medium

While working on [this PR](https://github.com/rust-lang/libc/pull/3407), I wrote… the following code: ```rust #[cfg_attr(feature = "zerocopy", derive(FromZeroes, FromBytes, AsBytes))] #[deprecated( since = "0.2.55", note = "Use the `mach2` crate instead", )] pub struct mach_timebase_info { pub numer: u32, pub denom: u32, } ``` Running `cargo check --features zerocopy` on `cargo 1.74.0-nightly (b4ddf95ad 2023-09-18)`, I get the following warning: ```text warning: use of deprecated struct `unix::bsd::apple::mach_timebase_info`: Use the `mach2` crate instead --> src/unix/bsd/apple/mod.rs:306:16 | 306 | pub struct mach_timebase_info { | ^^^^^^^^^^^^^^^^^^ | = note: `#[warn(deprecated)]` on by default ``` ## Mentoring instructions - [ ] Figure out the conditions under which this warning is emitted - [ ] Write a test that reproduces this behavior - [x] Modify our derives as needed to not generate this warning - Done: https://github.com/google/zerocopy/pull/556

github.com/google/zerocopy

Test the output of zerocopy-derive

opened 06:14PM - 10 Sep 23 UTC

joshlf

help wanted experience-hard

As zerocopy-derive gets more powerful, it becomes harder to test every edge case… just through compile-success and compile-fail tests. One way we could test at a higher fidelity would be to assert the exact token stream output as a result of deriving traits on various types. This would be in some ways easier to verify for a human reviewer, and would be more stable than compiler error messages (a problem that plagues our existing trybuild tests, and requires us to keep three separate copies of the .stderr files - one for each toolchain we use in CI). A few ways we could do this: - Use [`cargo expand`](https://crates.io/crates/cargo-expand) - Use synstructure's [test_derive!](https://docs.rs/synstructure/latest/synstructure/macro.test_derive.html) macro I'm currently leaning towards `test_derive!`, as it seems to do exactly what we want. ## Mentoring Steps: - [ ] Add `synstructure` dev-dependency to zerocopy-derive - [ ] Add a basic test and confirm that it works (this and the previous step could be their own PR) - [ ] Come up with as many test cases as you can think of! Consider using our existing tests (`zerocopy-derive/tests/*.rs`) and trybuild tests (`zerocopy-derive/tests/ui-*.rs`) to help give you ideas.

github.com/google/zerocopy

[CI] Check semver compatibility with all target platforms, not just the host platform

opened 10:29PM - 08 Sep 23 UTC

joshlf

help wanted experience-medium compatibility-nonbreaking

We use [`cargo-semver-checks-action`](https://github.com/obi1kenobi/cargo-semver…-checks-action) in CI to ensure we do not accidentally break semver compatibility: https://github.com/google/zerocopy/blob/0ff2dd15c958ab615b8094cf273f6b37d113c8fa/.github/workflows/ci.yml#L244-L264 This check occurs within our build matrix, so it's re-run for each `target`: https://github.com/google/zerocopy/blob/0ff2dd15c958ab615b8094cf273f6b37d113c8fa/.github/workflows/ci.yml#L41-L53 However, we aren't actually making use of `target`, meaning we are re-running the exact *same* check 11 times on the Github Actions host target (`x86_64-unknown-linux-gnu`). **We need to modify this CI job to respect the value of `target`.** To do this, see here: https://github.com/obi1kenobi/cargo-semver-checks-action/issues/54#issuecomment-1711833826

github.com/google/zerocopy

Inline many trait methods (in zerocopy and in derive-generated code)

opened 08:32PM - 19 Sep 22 UTC

joshlf

help wanted experience-easy compatibility-nonbreaking

## Status - [x] #341 - [ ] Deny `clippy::missing_inline_in_public_items` in …derive-generated code ## zerocopy-derive We don't care about inline attributes for zerocopy-derive itself, but we _do_ care for code _emitted_ by zerocopy-derive. We need to figure out a way to either modify zerocopy-derive's output or modify our zerocopy-derive tests so that, when running zerocopy-derive tests, missing `#[inline]` attributes generate warnings or errors. It might be possible to use the `clippy::missing_inline_in_public_items` lint for this, but I'm not sure. ## zerocopy ~~Many zerocopy trait methods contain very little logic or no logic at all, but are currently not marked with any `inline` attribute, and so cannot be inlined across a crate boundary. We should change this.~~ `#[inline]` attributes are now enforced by Clippy as of #341.

Thanks!

thomaseizinger · March 11, 2024, 4:31am

It isn't necessarily a beginner-friendly issue but we wanted to reach out to the community for people that have experience with testing native Android and iOS code in CI. quinn, a Rust implementation of QUIC has an open issue for that: Add CI for mobile platforms (iOS & Android) · Issue #1778 · quinn-rs/quinn · GitHub

joshlf · March 19, 2024, 5:12am

More zerocopy issues!

github.com/google/zerocopy

Audit uses of "C-like" and prefer "fieldless"

opened 05:23PM - 01 Mar 24 UTC

jswrenn

help wanted experience-easy

Much of our documentation refers to "C-like" enums, where *fieldless* would be a… more apt description. We should audit our documentation and replace "C like" for "fieldless" wherever applicable. A fieldless enum is one without fields; e.g.: ```rust enum Fieldless { Unit, Struct {}, Enum(), } ``` A C-like enum is a fieldless enum in which every constructor is unit-like. This is usually more restrictive than we need.

github.com/google/zerocopy

In zerocopy-derive UI tests, detect whether we're building with `RUSTFLAGS='-Wwarnings'`

opened 08:37PM - 26 Feb 24 UTC

joshlf

help wanted experience-easy

This is how we run zerocopy-derive's UI tests in CI, and so if a developer local…ly runs UI tests treating warnings as errors, they will generate the wrong `.stderr` files, and CI will fail. If `RUSTFLAGS='-Wwarnings'` is absent the test harness should eagerly fail with a single descriptive error, rather than proceed to run UI tests (which will produce lots of errors). For those interested in tackling this, the file to look in is: https://github.com/google/zerocopy/blob/main/zerocopy-derive/tests/trybuild.rs

weiznich · March 27, 2024, 1:37pm

The diesel project is looking for examples of bad error messages: Review Diesel compile time error message · diesel-rs/diesel · Discussion #3972 · GitHub

beryl678 · March 29, 2024, 10:35am

Hi community！

We have a good first issue for Rust starters to contribute at Greptime:

Thank you!

Anita-ihuman · April 2, 2024, 10:12am

Hey Community,

We have a few beginner-friendly Rust issues from the mirrord repository up for grabs.

Thanks

Anita-ihuman · April 8, 2024, 11:51am

Hi everyone
Here is an open issue for community contributors.

Fix all check-rust-docs warnings

Anita-ihuman · April 15, 2024, 11:05am

Hi everyone

Here are mirrord.dev issues for community contributors

medschool generated malformed JSON

dandyvica · April 23, 2024, 6:27pm

Hi all,

I'm the owner of the dqy project, a dig/dog/drill clone in pure Rust. Current version is 0.2.

If someone is interested in helping me moving to 1.0, it'll be great. No issues opened yet but spread the word. It has been asked to be a Rust replacement for dig (Add `dqy` alternative to `dig`. by XVilka · Pull Request #124 · TaKO8Ki/awesome-alternatives-in-rust · GitHub).

Project link: GitHub - dandyvica/dqy: A DNS query tool

drc-infinyon · April 24, 2024, 5:36pm

Hi Rustaceans,

Here are some issues to contribute to Fluvio Open Source Project.

Fluvio is a distributed event streaming system built from the ground up in Rust, and extended using the WASM component model.

Help appreciated on issues:

Cheers
Deb.

diokeles · April 25, 2024, 8:10pm

Hi all,
I am the developer of ricat a Rust based implementation of unix's cat command.
Current version is 0.4.2.
I have some issues that maybe interesting to newcomers, as i myself am a newcomer to Rust.
Ricat: Issues
Project Link: GitHub - adityanav123/ricat: Rust based implementation for the classic UNIX `cat` command
Crate Link: crates.io: Rust Package Registry
Thanks for reading.
-Aditya

beryl678 · May 6, 2024, 3:14am

Hi everyone,

Here are Greptime issues for community contributors:

Added TLS support for GreptimeDB's gRPC service

Thanks!

beryl678 · May 11, 2024, 3:47am

Hi everyone👋

Here are Greptime issues for community contributors:

Thanks!

joshlf · May 16, 2024, 11:51pm

Hey again!

Two zerocopy issues:

github.com/google/zerocopy

CI cache not including installed Cargo tools?

opened 05:22PM - 19 May 24 UTC

joshlf

help wanted experience-easy

Our `generate_cache` CI job, which is a dependency of the main `build_test` job,… runs [`cargo install cargo-nextest`](https://github.com/google/zerocopy/blob/889ac1bc2f38b1ccf338a1bf12f222102b338bc0/.github/workflows/ci.yml#L476). However, in [this run](https://github.com/google/zerocopy/actions/runs/9149280094/job/25152797173?pr=1311), we can see that it's getting re-installed in `build_test`. This likely means that binaries installed via `cargo install` are not getting cached.

Cheers,
Josh

rgiot · May 18, 2024, 10:19am

Hi; several months ago I open this thread for help request that attracted no help Help to compile a crate on windows that depends on a C library but compile properly on linux
So I try a second time with opening an issue to request help and guidance from someone else Make the code compiles on Windows · Issue #1 · cpcsdk/hxcfe_rs · GitHub

joshlf · May 23, 2024, 1:53pm

Bumping these for next week since they didn't go in this week

Also, one more:

bennyvasquez · May 27, 2024, 7:06pm

Hi all! I'm one of the editors for This Week in Rust and have been managing the CFP section for almost two years. It's been awesome to see y'all share your projects here and to hopefully send attention your way for newcomers.

The guidelines for the CFP section were set in place in 2016 (with the first post of this thread). We're updating them, and they will be adopted starting with edition 549, so I wanted to post them here. I've also added them to the README on the project.

Ensure your project has at least one Open Source Initiative-approved license.
Ensure that the issue tracker for your project is publicly accessible.
Create a new issue in your issue tracker, clearly describe the task, and include the difficulty level (easy/medium/hard/tedious) either as a tag/label or somewhere in the title/description.
Include a link to your contribution guidelines in the task, and call out any specific requirements for contributors (e.g., copyright waiver).

If you have questions or concerns, the best place for that conversation would be in the TWiR project. Feel free to open an issue and tag me!

Topic		Replies	Views
Call for Participation help	3	114	March 5, 2025
Rust open source project community	4	954	January 22, 2024
Rust Newcomer from Python	5	1607	September 18, 2020
Contributing to a Rust open-source project community	4	235	January 2, 2025
Find a open source project to contribute? community	2	857	July 20, 2023

Related topics