Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Fix response routing and dedupe commands across transports

Open
  • Is something wrong?
#15 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
embedded-iot, networking

Research direction

Start with the design and open questions in the linked contracts issue 7, then trace route_responses_task and the shared TX queues in this firmware repository. Reproduce the BLE queue blocking MQTT responses and check how state updates and phone changes affect queued messages. Done means responses survive state updates, BLE disconnection does not block MQTT, messages stay with their intended phone, and duplicate pairs are suppressed across transports.

Written by the indexing model from the issue text.

Description

Part of https://github.com/OpenCarControls/contracts/issues/7, which has the design and open questions., where the audit details are.

  • Responses can be evicted from the shared TX queues by state updates.
  • route_responses_task can stay stuck on the BLE queue with no phone connected, blocking MQTT responses.
  • Messages queued for one BLE phone are delivered to the next one.
  • Dedupe recent (source, message_id) pairs across both transports (also covers MQTT QoS 1 redelivery).
Dominant language
Rust
Stars
1
Forks
0
Avg merge
10h 56m
Merged PRs (30d)
15

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenCarControls/firmware

All issues in OpenCarControls/firmware

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.