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

`reflex cloud apps delete <unknown id>` exits 0

Open Beginner friendly
#7,295 1 comment 0 reactions 0 assignees View on GitHub

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
cli, python
Domain
cli

Research direction

Look at the reflex-hosting-cli package, specifically the command for reflex cloud apps delete. The issue shows the command exits with code 0 when given a non-existent app ID, but should exit 1. Compare the implementation for the ID-based delete with the --app-name delete and the inspect command to see how they handle not-found errors. The fix is likely in the function that processes the delete command, ensuring it returns a non-zero exit code when the app is not found. Run the existing tests for the CLI to verify the behavior.

Written by the indexing model from the issue text.

Description

Package: reflex-hosting-cli (reproduced on main at ea035ea47 and on #7207 at 988718e78)

Deleting an app ID that does not exist prints a warning and exits 0:

$ reflex cloud apps delete 00000000-0000-0000-0000-000000000000 --no-interactive
Warning: No application found with ID '00000000-0000-0000-0000-000000000000'
[exit=0]

The same lookup failure exits 1 elsewhere:

$ reflex cloud apps delete --app-name no-such-app-xyz --no-interactive
Warning: App 'no-such-app-xyz' not found.
[exit=1]

$ reflex cloud apps inspect 00000000-0000-0000-0000-000000000000 --no-interactive
no app with given id found
[exit=1]

A script that runs apps delete $ID && echo deleted reports success when the ID is wrong (typo, wrong account or project).

Expected: an error, and a non-zero exit, when the app ID is not found. This matches --app-name and the other apps subcommands.

Dominant language
Python
Stars
28.9k
Forks
1.8k
Avg merge
1d 15h
Merged PRs (30d)
180

Contributor guide

Open the 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 reflex-dev/reflex

All issues in reflex-dev/reflex

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.