vimcolorschemes / vimcolorschemes/worker
add job phase timing logs
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 5
- Forks
- 0
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 4
Description
the worker currently logs only coarse markers and final elapsed time, which made it hard to identify where import and update were spending time.
- log phase durations for import: github search, data preparation, repository upsert, job event writes
- log phase durations for update: repository load, github fetches, database writes, deletes/errors
- keep logs concise enough for cloudwatch scanning
- include counts per phase where useful
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the worker entry points for import and update, then read the existing coarse-marker and final-elapsed-time logging. Add concise duration logs for each listed phase, including useful counts, and verify that the logs make time spent in GitHub, preparation, database, delete, and error work visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100