Error messages are imprecise
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.7k
- Forks
- 336
- PR merge metrics
- No merged PRs in 30d
Description
See for instance https://github.com/docker/for-mac/issues/2954. The logs report
2018-05-29 09:30:06.602437-0600 localhost com.docker.driver.amd64-linux[23875]: ^MCould not lock backing file: Resource temporarily unavailable
It would be helpful to know what this is about.
Contributor 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.
Research direction
Start by searching the codebase for the log text "Could not lock backing file" and inspect the path that reports the locking failure. Use the Docker for Mac example as a reference; done means the error identifies what backing file or locking context is involved, with appropriate coverage if existing tests cover this message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100