Update metadata for LoongArch64 (api is empty, should be python3)
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- developer-experience
Research direction
Find the LoongArch64 entry in the community-plugins metadata and compare it with the release 0.3.0 plugin.json at the linked repository. Update its api to python3, and align platforms and the short description with that plugin.json. Done when the extension metadata matches the release metadata and the plugin no longer reports an empty API.
Written by the indexing model from the issue text.
Description
Plugin: LoongArch64 by Noah1
Repository: https://github.com/noah0x1/LoongArch64
The extension was originally submitted as a native plugin, so its metadata on extensions.binary.ninja has an empty api. Since release 0.3.0 it is a Python plugin (a Python loader for prebuilt native binaries), and the plugin.json of that release contains "api": ["python3"] and "platforms": ["Linux"].
The extension manager still uses the old metadata. Installing shows “Plugin doesn’t support any of (python3, debugger, target)”, and after a forced install Binary Ninja 6.0.10601 logs:
ValueError: Plugin 'LoongArch64' API name '[]' is not Python
Could you update the extension’s api to python3, and the platforms and short description to match plugin.json? Thanks :-)
- Dominant language
- Python
- Stars
- 593
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
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 Vector35/community-plugins
-
invalid new plugin
Difficulty 3/5 1-2 days Newbie friendliness 42/100
Vector35/community-plugins#339 · 6 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Vector35/community-plugins#313 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Vector35/community-plugins#308 · 2 comments ·
All issues in Vector35/community-plugins
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pyjanitor-devs/pyjanitor#1758 ·
Maintainers usually reply within 1 day
-
bug ready for review
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
odysseus-dev/odysseus#6641 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
happypawspillaro/happypaws#78 ·
Maintainers usually reply within 4 days
-
pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pydantic/pydantic-ai#10020 ·
Maintainers usually reply within 1 day
-
stdlib type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
python/cpython#159044 · 4 comments ·
Maintainers usually reply within 1 day