rapina-rs/rapina

Summary This issue is marked as a good first issue — it's a great starting point if you're new to contributing to Rapina. Before picking this up, please read the Contributing Guide. Comment /take to claim this issue. Task The validator crate in the Cargo.toml generated by the rapina new command and in some examples are still in 0.20.0, the most recent one is 0.21.0, bump them Why This Matters If the versions are incompatible, the code wont compile when Validator is used: there are multiple different versions of crate `validator` in the dependency graph Relevant Files rapina-cli/src/commands/templates/mod.rs rapina/examples/todo-app/Cargo.toml and rapina/examples/url-shortner/Cargo.toml Acceptance Criteria Feature/fix is implemented cargo fmt and cargo clippy pass Estimated Effort XS — < 30 minutes Hints & Resources Look at how similar functionality is implemented as a reference Follow existing patterns in the codebase Maintainer Checklist Issue is self-contained and scope

Summary We added needs: review, needs: author, needs: direction and stale so the PR queue reads at a glance. Those three are derivable from data GitHub already gives us. needs: direction is a judgement call, so the job should never touch it. Why This Matters Three of those four are set by hand right now, which means they'll be wrong within a week, and a label people can't trust is worse than no label at all. Relevant Files No response Acceptance Criteria No response Estimated Effort XS — < 30 minutes Hints & Resources The labels already exist, so this is just the workflow file. gh api graphql covers it, no third-party action needed. Maintainer Checklist Issue is self-contained and scoped for a first-time contributor Relevant files and context are provided above Acceptance criteria are clear and verifiable

Problem The first cut of the Redis relay backend opens one Redis pub/sub connection per active subscription. fn subscribe(&self, topic: &str) -> ... { let client = self.client.clone(); Box::pin(async move { let mut pubsub = client.get_async_pubsub().await?; // ← new socket, every call pubsub.subscribe(&topic).await?; let (_sink, stream) = pubsub.split(); // sink discarded ... }) } Connection != subscription is conflated: every subscription = a fresh socket. No sharing even for identical topics, 10k clients all on the same topic is still 10k connections, not 1. Goal Before: 1 (publish) connection + one pub/sub conn per subscription After: 2 total connections, flat: 1 publish + 1 shared pub/sub, regardless of sub count The "10k" moves from sockets to cheap in-process state (channel-subscriptions + local broadcast receivers). One shared pub/sub connection can SUBSCRIBE to any number of channels natively; a

Part of #740. derive_config_impl moves to config.rs, the #[proc_macro_derive] entry stays in lib.rs. Note the entry point and the impl currently sit ~70 lines apart with the schema entry between them, which is exactly the kind of thing this split fixes. Tests go along.

Part of #740. JobAttr, its Parse impl, and job_macro_impl move to job.rs, entry point stays in lib.rs. Tests go along. Independent of everything else in the file.