get_job_logs silently returns empty iterator when no pod is found
- Dominant language
- Python
- Stars
- 148
- Forks
- 262
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 1
Description
When no pod is found for the requested step, the generator silently returns. The caller gets an empty iterator with no way to distinguish "job produced no logs" from "pod was never found."
```python
if pod_name is None:
return
```
| File affected | Line |
|--|--|
| `kubernetes/backend.py` | `line: 443` |
| `optimizer/backends/kubernetes/backend.py` | `line: 245` |
Same behavior appears in both files above
### Was this behavior intended or should it raise an error?
Contributor guide
Research direction
Read kubernetes/backend.py around line 443 and optimizer/backends/kubernetes/backend.py around line 245, starting at the pod_name check in get_job_logs. Confirm how both generators behave when no pod is found and resolve whether the missing pod should be distinguishable from an empty log result. Done means both implementations follow the decided behavior consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- backend, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100