[Bug] 腾讯 XNet 不属于腾讯云物联网
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- tooling
Research direction
Start with the libXNet.so rule referenced by #642 and inspect how the library is currently classified under Tencent Cloud IoT. Update that rule so XNet is treated as a separate package, then verify the repository's rule data remains valid.
Written by the indexing model from the issue text.
Description
Current library filename / 现有库文件名
libXNet.so
Library relative URL / 相关链接
#642
Comment / 备注
对 #642 规则提出异议。腾讯 XNet 是单独的包名,不属于腾讯云 IoT 下属
- Dominant language
- Python
- Stars
- 201
- Forks
- 85
- Avg merge
- 1m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from LibChecker/LibChecker-Rules
-
[New Rule] InMobiOpen
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
LibChecker/LibChecker-Rules#1489 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
LibChecker/LibChecker-Rules#1488 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
LibChecker/LibChecker-Rules#1481 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
LibChecker/LibChecker-Rules#1479 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
LibChecker/LibChecker-Rules#1478 ·
All issues in LibChecker/LibChecker-Rules
Similar issues
-
Implement parse_url and accept http URLs for CPAN backendPossibly taken @patelshivani2283-lab claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
fedora-infra/anitya#2203 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Kaggle/kaggle-cli#1254 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jingyaogong/minimind#947 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
berntpopp/litvar-link#173 ·
Maintainers usually reply within 1 day