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

Code after return

Open
#167 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Search the templates for the shown return True and messages["set"] block, then trace the surrounding message-handling entry point. Confirm whether the assignments and write call can execute, and verify that the corrected control flow preserves successful message handling without leaving the block unreachable.

Written by the indexing model from the issue text.

Description

No wonder it was wrong -- this paragraph-to-code relationship is quite demanding to follow.

btw, I'm not used to reading templates, but are these lines after the return True even reachable?

        return True  # success{% for field in messages["set"][msg].payload %}
        m.{{field.name}} = {{field.name}}
{% endfor %}
        m.pack_msg_data()
        self.write(m.msg_data)

Originally posted by @joaoantoniocardoso in https://github.com/bluerobotics/ping-python/pull/165#pullrequestreview-3673411725

Dominant language
Python
Stars
60
Forks
39
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 bluerobotics/ping-python

All issues in bluerobotics/ping-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.