msgbyte / msgbyte/tailchat

插件wxpusher的问题 || Problem with plug-in wxpusher

Open
#256 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
3.6k
Forks
398
Avg merge
1h 14m
Merged PRs (30d)
2

Description

我在本地docker部署了安装插件 wxpusher后,根据文档打开wxpusher的选项,直接提示
Service 'plugin:com.msgbyte.wxpusher.getWXPusherUserId' is not found .(图1)
也重启了 docker 后,查看了wxpusher 是started的。(图1)

wp1

wp2

请问这个问题如何解决


After I deployed the installation plug-in wxpusher in local docker, I opened the wxpusher option according to the documentation and was prompted directly.
Service 'plugin:com.msgbyte.wxpusher.getWXPusherUserId' is not found. (Figure 1)
After restarting docker, I checked that wxpusher was started. (Figure 1)

wp1

wp2

How to solve this problem

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the wxpusher plug-in setup in the local Docker deployment described in the issue, following the referenced documentation. Start from the reported service name, plugin:com.msgbyte.wxpusher.getWXPusherUserId, and inspect why it is not found despite wxpusher showing as started. Done means the wxpusher option resolves the service without this error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, typescript
Domain
backend, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.