Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🔥🔥🔥 Introducing new puppet-service: wechaty-puppet-workpro #2462

Closed
hcfw007 opened this issue Dec 23, 2022 · 5 comments
Closed

🔥🔥🔥 Introducing new puppet-service: wechaty-puppet-workpro #2462

hcfw007 opened this issue Dec 23, 2022 · 5 comments

Comments

@hcfw007
Copy link
Member

hcfw007 commented Dec 23, 2022

Hello Wechaty community!

We are RPAChat, from Silcon Valley, developer of wechaty-puppet-wxwork(hereinafter called 'WxWork'). We focused on creating Robots from IM based on RPA technique. RPAChat is providing marketing cloud solution for well-known brands e.g. P&G, L’ORÉAL Paris, Swisse and POPMART.

RPAChat

Now we are proud to announce our next-generation wecom puppet: wechaty-puppet-workpro(hereinafter called 'WorkPro').

It's been over two years since we published our first WxWork version. It has been well received, however there are some unsolvable problems due to basic structure:

  • huge memory and cpu consumption
  • react slowly when receiving wecom official broadcast
  • takes a long time to sync messages when login

And WorkPro solves all above problems with a complete new design. It is absolutely incredible with great efficiency improvement. It also contains many great new features which are not completely supported by community version of wechaty currently. We are working on pushing these features now. Such as:

  • Moment posting
  • Quote messages
  • Channel messages
  • System messages
  • Contact tagging
  • Room announcement event*
  • ...and much more

Please note that room announce events will cause break down in current wechaty-puppet-service. See: wechaty/puppet-service#216.
Please use the latest version of wechaty-puppet-service (>1.19.9) to prevent above issue.

Besides the above room announcement event issue, workpro is compatible with current community wechaty version. Some of the latest features may be unusable, but you can still benefit from great efficiency improvement.

You can use Wechaty getting-started project to try WorkPro. (You'll need a token first.)

  • Run via Github Codespace

    1. Click Github Codespace and then click Create Codespace. Then wait for a while for the configuration service to install dependencies automatically.

    2. Set up environment variables. Currently we do not support TLS, see : Enable TLS for all Puppet Service Clients of Wechaty Ecosystem puppet-service#160

      export WECHATY_PUPPET_SERVICE_NO_TLS_INSECURE_CLIENT=true
    3. Edit examples/ding-dong-bot.ts which should be opended in editor already, replace line 73-76 to

      puppet: 'wechaty-puppet-service', // WorkPro is a puppet service, so you should put 'wechaty-puppet-service' instead of 'wechaty-puppet-workpro'
      puppetOptions: {
        token: 'xxx', // Put your token here, it should be something like 'puppet_workpro_xxxxxx'
      }
    4. Start the bot with npm start. You should see the QRCode in the terminal.

  • Run locally with git clone

    1. Install dependencies. Make sure you have node 16 or above installed. Then run

      npm install cross-env -g
      npm install
    2. Set up environment variables. Currently we do not support TLS, see : Enable TLS for all Puppet Service Clients of Wechaty Ecosystem puppet-service#160

      export WECHATY_PUPPET_SERVICE_NO_TLS_INSECURE_CLIENT=true
    3. Edit examples/ding-dong-bot.ts which should be opended in editor already, replace line 73-76 to

      puppet: 'wechaty-puppet-service', // WorkPro is a puppet service, so you should put 'wechaty-puppet-service' instead of 'wechaty-puppet-workpro'
      puppetOptions: {
        token: 'xxx', // Put your token here, it should be something like 'puppet_workpro_xxxxxx'
      }
    4. Start the bot with npm start. You should see the QRCode in the terminal.

For further information and 7-day free trial token application, please scan the following QRCode with wechat or wecom:
Wechaty-GitHub-issue

Wish to talk to you soon.

RPAChat

@lijiarui lijiarui pinned this issue Dec 23, 2022
@lijiarui lijiarui changed the title Introducing new puppet-service: wechaty-puppet-workpro 🔥🔥🔥 Introducing new puppet-service: wechaty-puppet-workpro Dec 23, 2022
@lijiarui lijiarui transferred this issue from wechaty/puppet-service Dec 23, 2022
@lijiarui lijiarui pinned this issue Dec 23, 2022
@huan
Copy link
Member

huan commented Dec 23, 2022

That's a fantastic new puppet; good job!

@JAi-Li
Copy link

JAi-Li commented Jun 19, 2023

image
If a user enters or exits the group chat, an error will be reported. How can I solve this problem

@zhongyufan
Copy link

使用onError监听错误

@yalongwan
Copy link

客服没人答复啊

Copy link

dosubot bot commented Nov 20, 2023

Hi, @hcfw007. I'm Dosu, and I'm helping the wechaty team manage their backlog. I wanted to let you know that we are marking this issue as stale.

From what I understand, the RPAChat project has introduced a new puppet called wechaty-puppet-workpro, which has addressed issues related to memory and CPU consumption, slow reaction to wecom official broadcasts, and slow message syncing. Additionally, the new puppet includes new features such as moment posting, quote messages, channel messages, and more.

You reported an error when a user enters or exits a group chat. However, it seems that this issue has been resolved.

If this issue is still relevant to the latest version of the wechaty repository, please let us know by commenting on this issue. Otherwise, feel free to close the issue yourself, or the issue will be automatically closed in 7 days.

Thank you for your contribution to the wechaty community!

@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Nov 20, 2023
@dosubot dosubot bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 27, 2023
@dosubot dosubot bot removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants