safe_name collision: different environment names sanitize to same filename
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 73/100
Research direction
Start with safe_name and save_request in git_api/cli.py, then trace where environment names are entered in the REPL. Check how existing collision warnings work and decide how name collisions should be reported when a name is created. Done when colliding sanitized names are rejected or warned about at creation time.
Written by the indexing model from the issue text.
Description
The safe_name function in git_api/cli.py strips all non-alphanumeric characters (except dash and underscore) and replaces them with underscore. This means different environment names like 'prod east' and 'prod/east' both sanitize to 'prod_east'. While save_request detects this collision and warns the user, the REPL does not prevent the ambiguity at the point of command entry. A user can set base_url in an environment named 'prod east', then accidentally reference 'prod/east' in a later command, and the silently-colliding name makes debugging confusing. Expected: Either reject names that collide with existing environment names after sanitization, or warn at creation time.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
ChatBedrockConverse changes the keys of JSON tool results to camelCase (`order_id` becomes `orderId`)Possibly taken @geyazheng claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
langchain-ai/langchain-aws#1469 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
b4b usability
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
fix(schedule): align list_tasks since cursor filter boundary from strict > to >=Possibly taken @bfs2021 claimed this today. Openagent-ready bug p2 schedule
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
allenporter/supernote#540 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
frazane/scoringrules#164 ·
Maintainers usually reply within 1 day