plugin:com.msgbyte.agora设置404 || plugin:com.msgbyte.agora to set 404
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.6k
- Forks
- 398
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 2
Description
agora用不了，而且agora官网后台
NCS 健康检查结果: 失败
{ "success": false, "httpCode": 404, "error": "", "response": "{"name":"ServiceNotFoundError","message":"Service 'plugin:com.msgbyte.agora.webhook' is not found.","code":404,"type":"SERVICE_NOT_FOUND","data":{"action":"plugin:com.msgbyte.agora.webhook"}}" }
但livekit插件能用
agora cannot be used, and agora official website backend
NCS health check result: failed
{ "success": false, "httpCode": 404, "error": "", "response": "{"name":"ServiceNotFoundError","message":"Service 'plugin: com.msgbyte.agora.webhook' is not found.","code":404,"type":"SERVICE_NOT_FOUND","data":{"action":" plugin:com.msgbyte.agora.webhook"}}" }
But the livekit plug-in can use
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 with the plugin:com.msgbyte.agora.webhook service named in the 404 and compare it with the working livekit plugin. Reproduce the NCS health check against the Agora integration; done means the webhook is found and the health check no longer returns HTTP 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100