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

Unknown --os or --arch still fetches the releases before failing

Open Beginner friendly
  • Is something wrong?
#68 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
php
Domain
cli

Research direction

Start with the rr get command and the existing --location validation, which already rejects bad input before any request; the unknown --os/--arch path currently only logs a warning and then fetches releases. Reproduce with rr get --os=plan9 and check that the release request happens before the failure. Done when an unknown OS or architecture fails before any GitHub API call, and FailureTest::rejectsUnknownPlatformWithoutRequests from #66 passes. Check whether #49 (DLoad) changes the release lookup first.

Written by the indexing model from the issue text.

Description

bug

Description

An unknown --os or --arch value is only a warning (Possibly invalid operating system (--os=plan9) option). rr get then fetches the whole release list from the GitHub API and fails only afterwards with Could not find any available RoadRunner binary version which meets criterion. Each such call spends GitHub API requests (the anonymous limit is 60 per hour) on a request that can never succeed.

Expected: an unknown OS or architecture is rejected before any request, like an invalid --location already is.

Steps to reproduce

  1. Run rr get --os=plan9 (or --arch=sparc).
  2. The releases are requested before the command fails.

Additional context

Found by the acceptance tests in #66 (FailureTest::rejectsUnknownPlatformWithoutRequests). The release lookup may be replaced by DLoad in #49.

Dominant language
PHP
Stars
30
Forks
15
Avg merge
45m
Merged PRs (30d)
11

Getting set up

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 roadrunner-php/cli

All issues in roadrunner-php/cli

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.