SagerNet / SagerNet/sing-vmess
The library sing with sing-vemss incompatible
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29
- Forks
- 74
- PR merge metrics
- No merged PRs in 30d
Description
I am working in clash.meta and xray with same go work project
xray require https://github.com/SagerNet/sing at v0.0.0-20220801112236-1bb95f9661fc
clash.meta require https://github.com/SagerNet/sing at v0.0.0-20220627234642-a817f7084d9c
When I ues go work sync，It changed clash.meta go.mod :
github.com/sagernet/sing v0.0.0-20220801112236-1bb95f9661fc
github.com/sagernet/sing-shadowsocks v0.0.0-20220801112336-a91eacdd01e1
github.com/sagernet/sing-vmess v0.0.0-20220616051646-3d3fc5d01eec
Then I got this error：
Is the library sing with sing-vemss incompatible?
need help
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 reproducing the reported Go workspace with clash.meta and xray, then inspect the go.work sync changes in clash.meta's go.mod. Compare the required versions of sing, sing-shadowsocks, and sing-vmess and use the linked error image to identify the incompatibility; done means the workspace dependencies work together without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100