Avoid error if no log file exists
Open
bug
good first issue
- Dominant language
- Python
- Stars
- 180
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
There are no log files on a freshly provisioned GHE appliance. Consequently, Hubble cannot find any log file and experiences errors such as this one:
```
Started update of git-download.tsv
gzip: /var/log/github-audit.log.1*.gz: No such file or directory
```
Contributor guide
Research direction
Start by tracing the update of git-download.tsv and how Hubble handles /var/log/github-audit.log.1*.gz when no matching log exists. Reproduce the fresh-appliance case, then verify that the update completes without the gzip “No such file or directory” error when no log file is present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- analytics
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100