SSL_VERIFY=0 is a stopgap that will outlive its reason

Open Beginner friendly
#21 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
68/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
devops

Research direction

Read section 5 of vllm-fleet-design.md and inspect install_set.py to confirm how SSL_VERIFY is handled and whether :8443 is still in use. Done means the stopgap is removed once the port moves, or install_set.py logs a warning whenever SSL_VERIFY=0 is set.

Written by the indexing model from the issue text.

Description

vllm-fleet-design.md section 5 notes it is temporary while
llm.apache.org is on :8443. Stopgaps in provisioning scripts do not get
removed on their own.

Either remove it when the port moves, or have install_set.py log a warning
when it is set so it announces itself.

Dominant language
Python
Stars
2
Forks
3
Avg merge
1d 12h
Merged PRs (30d)
2

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 apache/tooling-llmao

All issues in apache/tooling-llmao

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.