viperproject / viperproject/VerifiedSCION
Introduce obligations to enforce closing locks
Open
Nobody has claimed this yet.
deadlock-freedom
termination
- Dominant language
- Go
- Stars
- 12
- Forks
- 5
- Avg merge
- 13h 2m
- Merged PRs (30d)
- 4
Description
This issue has no description.
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
The issue body names no files, tests, or entry points. Start by inspecting the repository's Gobra verification code and existing lock-handling conventions; the issue does not define the required behavior or a concrete completion check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100