see: wechaty/puppet-service#43
see: https://github.com/wechaty/wechaty/blob/30c446b2b78c92166a1d613952e77d3e3fdbbe1f/src/wechaty.ts#L584

源码：
// ToImage extract the Image File from the Message, so that we can use different image sizes.
func (m *Message) ToImage() (_interface.IImage, error) {
if m.Type() != schemas.MessageTypeImage {
return nil, errors.New("not a image type message")
}
return m.GetWechaty().Image().Create(m.id), nil
}

测试。。。。。。

方式一
img,_:=message.ToImage()
fmt.Println(img.HD())
获取不到任何图片信息

方式二
img,_:=message.ToFileBox()
fmt.Println(img.ToDataURL())

无法获取到图片信息

https://github.com/robertkrimen/otto

It seems very interesting...

Run JavaScript inside Go!

vm := otto.New()
vm.Run(`
    abc = 2 + 2;
    console.log("The value of abc is " + abc); // 4
`)

Run Go inside JavaScript!

vm.Set("sayHello", func(call otto.FunctionCall) otto.Value {
    fmt.Printf("Hello, %s.\n", call.Argument(0).String())
    return otto.Value{}
})

vm.Set("twoPlus", func(call otto.FunctionCall) otto.Value {
    right, _ := call.Argument(0).ToInteger()
    result, _ := vm.ToValue(2 + right)
    return result
})

result, _ = vm.Run(`
    sayHello("Xyzzy");      // Hello, Xyzzy.
    sayHello();             // Hello, undefined

    result = twoPlus(2.0); // 4
`)

Let's fix the listing problems.

Current state: make lint

$ make lint
~/go/bin/golint wechaty
wechaty/accessory.go:7:6: exported type Accessory should have comment or be unexported
wechaty/type.go:7:6: exported type Sayable should have comment or be unexported
wechaty/wechaty.go:1:1: package comment should be of the form "Package wechaty ..."
~/go/bin/golint wechaty-puppet
wechaty-puppet/file_box.go:1:1: don't use an underscore in package name
wechaty-puppet/file_box.go:3:6: exported type FileBox should have comment or be unexported
wechaty-puppet/file_box.go:7:19: method ToJson should be ToJSON
wechaty-puppet/file_box.go:16:1: comment on exported method FileBox.FromQrCode should be of the form "FromQrCode ..."
wechaty-puppet/puppet.go:1:1: don't use an underscore in package name
wechaty-puppet/puppet.go:9:6: exported type PuppetInterface should have comment or be unexported
wechaty-puppet/puppet.go:10:15: interface method parameter messageId should be messageID
wechaty-puppet/puppet.go:13:6: exported type Puppet should have comment or be unexported
wechaty-puppet/puppet.go:19:1: comment on exported method Puppet.MessageList should be of the form "MessageList ..."
wechaty-puppet/puppet.go:30:1: exported method Puppet.MessageSearch should have comment or be unexported
wechaty-puppet/puppet.go:31:2: var allMessageIdList should be allMessageIDList
wechaty-puppet/puppet.go:42:6: var messageIdList should be messageIDList
wechaty-puppet/puppet.go:57:1: comment on exported method Puppet.MessagePayload should be of the form "MessagePayload ..."
wechaty-puppet/puppet.go:58:33: method parameter messageId should be messageID

Questions from WIP: add user/message.go #4

Q1

Q1: Go does not allow const of the same name and different types in the same package; so I changed the name of the constant, which may differ from the community specification, I wonder if it is appropriate?

I understand the naming style is different between the language specifications.

From TypeScript to Go means, we have to change some of our naming specifications so that the code can fit the Go styles.

My opinion is: we should follow the style from TS Wechaty as our default, and only change it when there's a must.

For the Go Lang, I believe we can follow another official style which will be a perfect match: @chatie/grpc (Wechaty has dependency to this module)

You can find the Image definition here:

https://github.com/Chatie/grpc/blob/ab85b7345b90c167a031710b9a819f9220c09002/proto/wechaty/puppet/message.proto#L25-L30

enum ImageType {
  IMAGE_TYPE_UNSPECIFIED = 0;
  IMAGE_TYPE_THUMBNAIL   = 1;
  IMAGE_TYPE_HD          = 2;
  IMAGE_TYPE_ARTWORK     = 3;
}

Which means in Go, we can align to:

  ImageTypeUnspecified ImageType = 0
  ImageTypeThumbnail = 1
  ImageTypeHd = 2
  ImageTypeArtwork = 3

Describe the bug
服务端重启后，这边的gprc客户端就会断连，需要重新启动

@https://github.com/wechaty/puppet-xp
@https://github.com/wechaty/go-wechaty
@zhangchunsheng
@atorber

Docs.Api.Message. Example

if (await message.mentionSelf()) {
 console.log('this message were mentioned me! [You were mentioned] tip ([有人@我]的提示)')
}

golang

func Chat(context *wechaty.Context, message *user.Message) {
	log.Printf("%sGroup Chat:%s %s \n", viper.GetString("info"), message.From().Name(), message.Text())
	if message.MentionSelf() {
		log.Printf("有人@我了 %s: %s", message.From().Name(), message.Text())
		return
	}
}

Log

[xrsec] 10:02:52 botAPI.go:69: [✓]  已设置钉钉提醒
[xrsec] 10:02:52 puppet_service.go:96: PuppetService Start()
[xrsec] 10:02:53 puppet_service.go:232: PuppetService onGrpcStreamEvent({type:EVENT_TYPE_LOGIN payload:{"contactId":"wxid"}})
[xrsec] 10:02:53 puppet_service.go:384: PuppetService ContactRawPayload(wxid)
[xrsec] 10:02:53 puppet_service.go:232: PuppetService onGrpcStreamEvent({type:EVENT_TYPE_HEARTBEAT payload:{"data":"Wechaty Puppet gRPC stream connect successfully"}})
[xrsec] 10:02:53 main.go:76: [✓] 机器人 Bot 上线
[xrsec] 10:03:01 puppet_service.go:232: PuppetService onGrpcStreamEvent({type:EVENT_TYPE_MESSAGE payload:{"messageId":"cl1lhyi3p000j4olc4n0j5pfz"}})
[xrsec] 10:03:01 puppet_service.go:504: PuppetService MessagePayload(cl1lhyi3p000j4olc4n0j5pfz)
[xrsec] 10:03:01 puppet_service.go:671: PuppetService RoomRawPayload(11111111chatroom)
[xrsec] 10:03:01 puppet_service.go:384: PuppetService ContactRawPayload(wxid)
[xrsec] 10:03:01 chat.go:11: [➜] Group Chat:星冉 #XRSec @Bot 
[xrsec] 10:03:01 puppet_service.go:802: PuppetService RoomMemberList(11111111chatroom)
[xrsec] 10:03:01 puppet_service.go:814: PuppetService RoomMemberRawPayload(11111111chatroom, wxid)
[xrsec] 10:03:01 puppet_service.go:802: PuppetService RoomMemberList(11111111chatroom)
[xrsec] 10:03:01 chat.go:13: 星冉 #XRSec: @Bot
[xrsec] 10:03:01 chat.go:14: 有人@我了
[xrsec] 10:03:04 puppet_service.go:232: PuppetService onGrpcStreamEvent({type:EVENT_TYPE_MESSAGE payload:{"messageId":"cl1lhyjzh000k4olc9f4l8hos"}})
[xrsec] 10:03:04 puppet_service.go:504: PuppetService MessagePayload(cl1lhyjzh000k4olc9f4l8hos)
[xrsec] 10:03:04 chat.go:11: [➜] Group Chat:星冉 #XRSec @Bot 1 
[xrsec] 10:03:04 puppet_service.go:802: PuppetService RoomMemberList(11111111chatroom)
[xrsec] 10:03:27 puppet_service.go:232: PuppetService onGrpcStreamEvent({type:EVENT_TYPE_MESSAGE payload:{"messageId":"cl1lhz1m4000l4olc5fvsekpx"}})
[xrsec] 10:03:27 puppet_service.go:504: PuppetService MessagePayload(cl1lhz1m4000l4olc5fvsekpx)
[xrsec] 10:03:27 puppet_service.go:802: PuppetService RoomMemberList(11111111chatroom)
[xrsec] 10:03:27 puppet_service.go:384: PuppetService ContactRawPayload(wxid)

According to our Wechaty Specification https://wechaty.js.org/docs/specs/wechaty:

The WECHATY_LOG should support the values of silly, verbose, info, warn, silent

All Polyglot Wechaty should at least support the above names as an alias.

Link to wechaty/wechaty#2167

使用wechaty-padlocal的时候，在OnMessage回调函数里面取收信人信息会抛出空指针，比如message.To.Name()，不会返回预期的空字符串，而是抛出一个空指针异常，但是go-wechaty做了处理，会导致后续步骤无法执行。

docker wecahty:latest
go-wecahty v0.31 or v0.35

docker wecahty 不管是true还是false，均正常运行
export WECHATY_PUPPET_SERVICE_NO_TLS_INSECURE_CLIENT="true"
export WECHATY_PUPPET_SERVICE_NO_TLS_INSECURE_CLIENT="false"

环境变量

export WECHATY_LOG="verbose"
export WECHATY_PUPPET="wechaty-puppet-padlocal"
export WECHATY_PUPPET_PADLOCAL_TOKEN="puppet_padlocal_xxxxxxxxxxxxxxxxxxxxxx"
export WECHATY_PUPPET_SERVICE_NO_TLS_INSECURE_CLIENT="true"
export WECHATY_PUPPET_SERVER_PORT="8788"
export WECHATY_TOKEN=$(curl -s https://www.uuidgenerator.net/api/version4)
echo "WECHATY_TOKEN=$WECHATY_TOKEN"
```

启动参数
```docker
docker run -ti \
  -d \
  --name wxservice \
  --restart=always \
  --privileged \
  --network=host \
  -e WECHATY_LOG \
  -e WECHATY_PUPPET \
  -e WECHATY_PUPPET_SERVER_PORT \
  -e WECHATY_PUPPET_PADLOCAL_TOKEN \
  -e WECHATY_PUPPET_SERVICE_NO_TLS_INSECURE_SERVER \
  -p "$WECHATY_PUPPET_SERVER_PORT:$WECHATY_PUPPET_SERVER_PORT" \
  -e WECHATY_TOKEN \
  wechaty/wechaty:latest
```

但是要么是这个报错的信息，要么是0.0.0.0的JSON数据，即使有正确的IP地址和端口JSON返回，也无法让go-wechaty连接上去。

```html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Error</title>
</head>
<body>
<pre>Cannot GET /v0/hosties/</pre>
</body>
</html>
root@userroot:/home/userroot#
```

```go
bot := wechaty.NewWechaty(wechaty.WithPuppetOption(wp.Option{
		Endpoint: "113.74.111.111:8788",
		//Token:token,
		// 超时控制
		Timeout: time.Duration(2 * time.Minute),
	}), wechaty.WithName("IpadLocalWechat"))
```

但 go-wechaty始终连接不上去，报如下的问题。

2021/10/07 16:12:56 PuppetService Start()
2021/10/07 16:12:56 puppet start err:  PuppetService Start() rejection: startGrpcStream err:rpc error: code = Unavailable desc = connection closed
panic: PuppetService Start() rejection: startGrpcStream err:rpc error: code = Unavailable desc = connection closed

RT。看源码没看明白，太菜了！

请教，使用的是最新版代码，本地docker 部署的padlocal服务已登录运行正常。
本地运行ding-dong-bot， 报错无法连接上服务，请大佬帮看下

错误输出：

docker启动配置：

本地环境变量配置：

请大佬指点。

It seems from README that wechaty-puppet used by go-wechaty are all outdated, and as per commit logs and #74, no attempts had been made to incorporated the current/new wechaty-puppets. I.e., it seems the project died after the wechaty-puppet-padplus had died, which is what I really don't want to see.

Describe the solution you'd like
A clear and concise description of what you want to happen.

看一下这个
https://github.com/wechaty/summer-of-wechaty/issues

这个是目前其他的mentor已经发出来的project，在我看来，go wechaty的功能迫切需要完善，这同一个项目里面不要说放一两个学生，我觉得就是放上十几个也没问题，他们都是在做同一个项目，只不过分别到具体的方面不一样
具体到这个特别的项目，分工如何，看什么做了，什么还没做，指导我都不行，不过我可以在具体的某一些点上做一些帮助。比如，只是说比如，我可以帮着做基于go 的 unit test 框架，不过还是那点，让我做框架设计肯定不行，我能帮到的就是在大的框架结构下面做一些具体的工作

We need to find a way to avoid the circle dependencies problem.

Current state: make bot

$ make bot
go run examples/ding-dong-bot.go
import cycle not allowed
package main
	imports github.com/wechaty/go-wechaty/wechaty
	imports github.com/wechaty/go-wechaty/wechaty/user
	imports github.com/wechaty/go-wechaty/wechaty
make: *** [Makefile:40: bot] Error 1

1MentionText 不生效问题 （怀疑是特殊字符串导致）

快速定位

2022/04/16 23:06:31 MentionText:[@可馨 add @Chumo(初墨)六号技师 ]

完整日志

2022/04/16 23:06:21 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_HEARTBEAT payload:{"data":"heartbeat@padlocal"}})
2022/04/16 23:06:31 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_MESSAGE payload:{"messageId":"xxxxxxxxxxxxxxx"}})
2022/04/16 23:06:31 PuppetService MessagePayload(xxxxxxxx))
2022/04/16 23:06:31 PuppetService RoomMemberList(xxxxxxxxxxxxx@chatroom)
2022/04/16 23:06:31 PuppetService ContactRawPayload(wxid_xxxxxxxxxx)
2022/04/16 23:06:31 PuppetService RoomMemberList(xxxxxxxxxxxxx@chatroom)
2022/04/16 23:06:31 PuppetService RoomMemberRawPayload(xxxxxxxxxxxxx@chatroom, wxid_xxxxxxxxxx)
2022/04/16 23:06:31 PuppetService RoomMemberList(xxxxxxxxxxxxx@chatroom)
2022/04/16 23:06:31 PuppetService ContactRawPayload(wxid_xxxxxxxxxx)
2022/04/16 23:06:31 PuppetService RoomMemberList(xxxxxxxxxxxxx@chatroom)
2022/04/16 23:06:31 MentionText:[@可馨 add @Chumo(初墨)六号技师 ]

代码

log.Printf("MentionText:[%s]", message.MentionText())

亲爱的大佬，请问一下，就现在为止，该怎么搭配 purper
wecahty4u 好几年没维护了，wechaty4u 搭配的是 docker 0.65版本

最新版的 docker 镜像登录web版微信没有问题，但是 客户端提示连接失败，是否需要添加其他的参数呢？

Python 库 试用过了，还有提示，go 库 直接丢出报错，让我这个不怎么读代码的 菜鸟来说有点难受

请问能不能提供一个Stop方法用于正常关闭bot ，现在通过Puppet().Stop() 关闭的话，因为autoReconnectGrpcConn()的存在，会导致程序panic
panic: runtime error: invalid memory address or nil pointer dereference
goroutine 275 [running]:
google.golang.org/grpc.(*ClientConn).GetState(0x0, 0x0)
github.com/wechaty/go-wechaty/wechaty-puppet-service.(*PuppetService).autoReconnectGrpcConn(0xc002501b30)
created by github.com/wechaty/go-wechaty/wechaty-puppet-service.(*PuppetService).startGrpcClient

See: https://github.com/avelino/awesome-go

这几天运行发现隔个二三天左右微信账号就会自动退出，这种自动退出后，是否可以设置自动登录或者怎么不自动退出登录？在手机微信端无任何操作
docker日志
21:48:07 VERB EventStreamManager grpcEmit(EVENT_TYPE_HEARTBEAT[1], {"data":"heartbeat@browserbridge ding"})
21:48:22 VERB EventStreamManager grpcEmit(EVENT_TYPE_HEARTBEAT[1], {"data":"heartbeat@browserbridge ding"})
21:48:32 VERB PuppetWeChatBridge onLoad() page.url=https://wx2.qq.com/?&lang=en
21:48:32 VERB PuppetWeChatBridge readyAngular()
21:48:32 VERB PuppetWeChatBridge inject()
21:48:32 VERB EventStreamManager grpcEmit(EVENT_TYPE_HEARTBEAT[1], {"data":"heartbeat@browserbridge ding"})
21:48:32 VERB PuppetWeChatBridge ding(ding() OK!)
21:48:32 VERB EventStreamManager grpcEmit(EVENT_TYPE_DONG[3], {"data":"ding() OK!"})
21:48:32 VERB PuppetWeChatBridge clickSwitchAccount()
21:48:33 VERB PuppetWeChatEvent onScan({code: 0, url: https://login.weixin.qq.com/qrcode/QaUgZVng2g==})
21:48:33 VERB MemoryCard set(PUPPET_WECHAT, [object Object],[object Object],[object Object],[object Object],[object Object],[object Object])
21:48:33 VERB MemoryCard save() to StorageFile</wechaty/e4604ef1-f823-bd1f-3e6d-cebd84842d9d.memory-card.json>
21:48:33 VERB StorageFile save() to /wechaty/e4604ef1-f823-bd1f-3e6d-cebd84842d9d.memory-card.json
21:48:33 VERB PuppetWeChatEvent onScan() there has user when got a scan event. emit logout and set it to null
21:48:33 VERB PuppetWeChat logout()
21:48:33 VERB Puppet selfId()
21:48:33 VERB PuppetWeChatBridge logout()
21:48:33 VERB EventStreamManager grpcEmit(EVENT_TYPE_LOGOUT[26], {"contactId":"@0bac3b4fe04e292c879bf1013577feb27b98c3dd8aaad177d4c7cf7173842a56","data":"logout()"})
21:48:33 VERB ContactSelf name()
21:48:33 INFO IoClient 哈 logged out
21:48:33 VERB EventStreamManager grpcEmit(EVENT_TYPE_HEARTBEAT[1], {"data":{"code":0,"url":"https://login.weixin.qq.com/qrcode/QaUgZVng2g=="},"type":"scan"})
21:48:33 INFO IoClient [2] https://login.weixin.qq.com/l/QaUgZVng2g==
Online QR Code Image: https://wechaty.js.org/qrcode/https%3A%2F%2Flogin.weixin.qq.com%2Fl%2FQaUgZVng2g%3D%3D
21:48:33 VERB EventStreamManager grpcEmit(EVENT_TYPE_SCAN[22], {"qrcode":"https://login.weixin.qq.com/l/QaUgZVng2g==","status":2})
21:48:34 VERB PuppetWeChatBridge onLoad() page.url=https://wx2.qq.com/?&lang=en
21:48:34 VERB PuppetWeChatBridge readyAngular()
21:48:34 VERB PuppetWeChatBridge inject()
21:48:34 VERB EventStreamManager grpcEmit(EVENT_TYPE_HEARTBEAT[1], {"data":"heartbeat@browserbridge ding"})
21:48:34 VERB PuppetWeChatBridge ding(ding() OK!)
21:48:34 VERB EventStreamManager grpcEmit(EVENT_TYPE_DONG[3], {"data":"ding() OK!"})
21:48:34 VERB PuppetWeChatBridge clickSwitchAccount()

ding-dong 机器人日志：
2021/06/23 05:48:32 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_HEARTBEAT payload:{"data":"heartbeat@browserbridge ding"}})
2021/06/23 05:48:32 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_DONG payload:{"data":"ding() OK!"}})
2021/06/23 05:48:33 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_LOGOUT payload:{"contactId":"@0bac3b4fe04e292c879bf1013577feb27b98c3dd8aaad177d4c7cf7173842a56","data":"logout()"}})
User Contact<哈> logouted: logout()
2021/06/23 05:48:33 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_SCAN payload:{"qrcode":"https://login.weixin.qq.com/l/QaUgZVng2g==","status":2}})
Scan QR Code to login: ScanStatusWaiting
https://wechaty.js.org/qrcode/https://login.weixin.qq.com/l/QaUgZVng2g==
2021/06/23 05:48:33 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_HEARTBEAT payload:{"data":{"code":0,"url":"https://login.weixin.qq.com/qrcode/QaUgZVng2g=="},"type":"scan"}})
2021/06/23 05:48:33 PuppetService unMarshal err: json: cannot unmarshal object into Go struct field BaseEventPayload.Data of type string
2021/06/23 05:48:34 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_HEARTBEAT payload:{"data":"heartbeat@browserbridge ding"}})
2021/06/23 05:48:34 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_DONG payload:{"data":"ding() OK!"}})
2021/06/23 05:48:35 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_SCAN payload:{"qrcode":"https://login.weixin.qq.com/l/AdN2-vpRtQ==","status":2}})
Scan QR Code to login: ScanStatusWaiting
https://wechaty.js.org/qrcode/https://login.weixin.qq.com/l/AdN2-vpRtQ==
2021/06/23 05:48:35 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_HEARTBEAT payload:{"data":{"code":0,"url":"https://login.weixin.qq.com/qrcode/AdN2-vpRtQ=="},"type":"scan"}})
2021/06/23 05:48:35 PuppetService unMarshal err: json: cannot unmarshal object into Go struct field BaseEventPayload.Data of type string
2021/06/23 05:48:49 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_HEARTBEAT payload:{"data":"heartbeat@browserbridge ding"}})

We continue to discuss whether go.sum is submitted to the repository.

I suggest to submit this file.

As @eslizn quoted Go official discussion on this issue:
https://github.com/golang/go/wiki/Modules#releasing-modules-all-versions

Related documents:

• php composer.lock
• npm package-lock.json
• pip requirements.txt

submit go.sum the reason:

• reliance on version unification.
• Provide package management dependent content verification in a distributed environment

Many open source projects are like this.

See: wechaty/wechaty#1927

提供微信协议API接口，支持最新的视频号接口，公司合法业务可以提供支持
http://www.bbaos.com/docs/index
wx：damibtc

我不知道该如何实现如下的问题
当我获取到群好友中的关键信息后，如何私聊答复，但我不希望在群里面@好友.

系统默认方式：message.Say("txtMsg")

但我期待的是
message.Say("txtMsg",frind_ID)

请问如何实现。

message.Text() is

....

The Go Wechaty will be installed from github.com/wechaty/go-wechaty, so the wechaty/go-wechaty is our deploy repo for the Go Lang.

The Problem

However, currently, we are developing based on this repo too, which makes it complicated to maintain and not very clean.

The Solution

Shall we use this wechaty/go-wechaty for our publish-only repo, and we deploy the code from our developing repo to this publish-only repo by DevOps & CI/CD? That would help us make sure the published code is with high quality as we expected.

RFC

For the simplest way to archive this goal, we can just rename wechaty/go-wechaty to another name which can stands for the developing, like wechaty/go-wechaty-src (good suggestions are welcome!), and then create a new repo named wechaty/go-wechaty for the deployment.

If we think it's necessary to continue this discussion, please feel free to share your thoughts by commenting on this issue, thank you very much!

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Please rate Feature
Please consider the scope of application and the difficulty of development.

Additional context
Add any other context or screenshots about the feature request here.

使用的是web协议，DIY Puppet Service：
export WECHATY_LOG="verbose"
export WECHATY_PUPPET="wechaty-puppet-wechat"
export WECHATY_PUPPET_SERVER_PORT="9999"
export WECHATY_TOKEN=“My token”
docker run
-d
-ti
--name wechaty_puppet_service_token_gateway
--rm
--privileged
--network=host
-e WECHATY_LOG
-e WECHATY_PUPPET
-e WECHATY_PUPPET_SERVER_PORT
-e WECHATY_TOKEN
wechaty/wechaty

在使用message.Forward(room.ID())和message.ToFileBox()时，消息类型是text没问题，消息类型是image和video时都报：“json: cannot unmarshal string into Go struct field FileBoxOptions.headers of type []string”这个错误，其他类型没测试，有解决办法吗，谢谢。
go version:1.17

Describe the bug
在使用wechaty-puppet-wechat 同步通讯录时报错
使用参考文章：https://wechaty.js.org/2021/04/16/go-wechaty-use-web/

To Reproduce
Steps to reproduce the behavior:
1.其他微信号主动添加微信机器人

bot.OnFriendship(func(context *wechaty.Context, friendship *user.Friendship) { fmt.Printf("received friend event from " + friendship.Contact().Name()) if friendship.Type() == schemas.FriendshipTypeReceive { fmt.Printf("Have Friend " + friendship.Contact().Name()) err := friendship.Accept() } })

发现Docker容器循环提示错误

07:22:33 VERB PuppetCacheMixin dirtyPayload(Room<3>, @@819dc5a932922d0XXXXX1237552f59973f173c11904dca2312d7509936a8b)
07:22:33 VERB PuppetRoomMemberMixin roomMemberPayloadDirty(@@819dc5a932922d0XXXXX1237552f59973f173c11904dca2312d7509936a8b)
07:22:33 VERB PuppetCacheMixin __dirtyPayloadAwait(RoomMember<4>, @@819dc5a932922d0XXXXX1237552f59973f173c11904dca2312d7509936a8b)
07:22:33 VERB PuppetCacheMixin dirtyPayload(RoomMember<4>, @@819dc5a932922d0XXXXX1237552f59973f173c11904dca2312d7509936a8b)
07:22:33 VERB PuppetCacheMixin onDirty(RoomMember<4>, @@819dc5a932922d0XXXXX1237552f59973f173c11904dca2312d7509936a8b)
07:22:33 VERB EventStreamManager grpcEmit(EVENT_TYPE_DIRTY[27], {"payloadId":"@@819dc5a932922d0XXXXX1237552f59973f173c11904dca2312d7509936a8b","payloadType":4})
07:22:33 VERB PuppetContactMixin contactPayloadDirty(@@819dc5a932922d0XXXXX1237552f59973f173c11904dca2312d7509936a8b)
07:22:33 VERB PuppetCacheMixin __dirtyPayloadAwait(Contact<2>, @@819dc5a932922d0XXXXX1237552f59973f173c11904dca2312d7509936a8b)
07:22:33 VERB PuppetCacheMixin dirtyPayload(Contact<2>, @@819dc5a932922d0XXXXX1237552f59973f173c11904dca2312d7509936a8b)
07:22:33 VERB PuppetCacheMixin onDirty(Contact<2>, @@819dc5a932922d0XXXXX1237552f59973f173c11904dca2312d7509936a8b)

2021/11/18 15:23:40 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_DIRTY payload:{"payloadId":"@@819dc5a932922d0XXXXX1237552f59973f173c11904dca2312d7509936a8b","payloadType":2}})
2021/11/18 15:23:40 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_DIRTY payload:{"payloadId":"@@819dc5a932922d0XXXXX1237552f59973f173c11904dca2312d7509936a8b","payloadType":2}})
2021/11/18 15:23:40 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_DIRTY payload:{"payloadId":"@@819dc5a932922d0XXXXX1237552f59973f173c11904dca2312d7509936a8b","payloadType":2}})
2021/11/18 15:23:40 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_DIRTY payload:{"payloadId":"@@819dc5a932922d0XXXXX1237552f59973f173c11904dca2312d7509936a8b","payloadType":2}})

As mentioned by @suntong from #11 (comment):

"Convert TypeScript types to GO" right? -- https://app.quicktype.io/#l=Go
Meaning that we should make TypeScript type definitions as individual files, separate their implementations from them. So whenever the types get changed, the Go/Java/Python type definition files can be changed semi-automatically as well.

I believe it will be great if we can have a good design to use the automatic generation from this tool because the wechaty-puppet will be changed in the future frequently, and it will be great if we can be prepared and leave all the work to the machine.

Link to Python: wechaty/python-wechaty#10

之前我在终端设置过了环境变量，以为 在程序里面设置也可以，但是我刚刚退出程序重新进入才发现，程序里面设置的环境变量压根没有用，我不理解，你们这也太。。。
人都麻了，我不理解，连os.Setenv 都不能读取到吗？

统计小帮手（statistic genie）

• 群里谁经常踊跃发言，大家一般都会有个直觉。但真要定性定量的出一张排行榜，一般人还做不到。
• 再者，更重要的问题是，一方面群人满为患，很多人想进进不来，而另一方面，群里却存在着很多自从进群以后就从来没有参与交流过的僵尸用户。

用发言排行榜鼓励积极参与者，用沉睡鞭策榜提醒不参与交流的用户，统计小帮手（statistic genie）能帮助群主更加有效的调动群成员的积极参与意识。

名词简介

每一个群成员都有以下（在统计区间内的）重要指数：

Plan

I plan to implement this once the go-wechaty project is usable.

This is just a blue-print for now, if anyone has any more interesting idea, please chip in. Feature planned in design phase would much easier than adding them later on when design is done.

Thanks

Planned commands

Syntax

sg-period days-top [days-warn]

E.g.,

• sg-period 7 30 means to give statistics of active users for the past week, and least active users for the past 30 days.

On second thought, I might not need this.

sg-top [number [period]]

E.g.,

• sg-top, or sg-top 10 will give top 10 active users for the past week.
• sg-top 20 10 will give top 20 active user for the past 10 days.

sg-warn [number [period]]

E.g.,

• sg-warn or sg-warn 10, will warn the least 10 active users of the past 30 days.

sg-kick reason person [person...]

• kick the person(s) given on the command line.
• explain the reason and @ them before kicking.

E.g., sg-kick "group rule violation" @him @her ...

Question(s)

• I remember it was difficult to get the "group alias" (named used within this group) from weixin API. That will affect the listing of all the lists, as not using the group alias might confuse some people. I don't know what's the situation now.

Design considerations

• The "贡献指数" is named "word" total in DB, instead of "char" total, is manly for clarification purpose:
  • Each Chinese character will be counted as 1, yet
  • Each English word will be counted as 1, if they show up in the message

Is your feature request related to a problem? Please describe.
Some gRPC server use token to identify the current user in the same service port.

Describe the solution you'd like
add grpc.default_authority option to grpc channel

see:
wechaty/puppet-service#78

Questions from WIP: add user/message.go #4

Q2

Q2: I also have some doubts about the definition of Accessory, I am not completely sure.

What's your question about the Accessory design?

There are two related discussions from the Python Wechaty at wechaty/python-wechaty#18 and wechaty/python-wechaty#15

1. Add WECHATY_PUPPET_SERVICE_TOKEN support for all our Polyglot Wechaty projects.
2. Make WECHATY_PUPPET_HOSTIE_TOKEN an alias for WECHATY_PUPPET_SERVICE_TOKEN, and print a warning message to let the user know it was deprecated with it has been set.

Learn more from wechaty/wechaty#2123

客户端运行错误信息：
puppet start err: PuppetService Start() rejection: rpc error: code = Unknown desc = TypeError [ERR_INVALID_ARG_TYPE]: The "listener" argument must be of type function. Received undefined

客户端 golang 代码

服务端运行错误信息：

docker 使用的 lastest 和 next 版本都均会报错

支持大文件

已经在群聊中找到用户ID 但是无法加好友（怀疑是特殊字符串导致）

快速定位

2022/04/16 23:06:32 添加好友失败, 用户名: [Chumo(初墨)]用户ID:[wxid_xxxxxxxxxx], Error: [rpc error: code = Internal desc = [tid:57221f39] request has been cancelled for reason: SERVER_ERROR: 2 UNKNOWN: [tid:57221f39] wechat bad request error]

完整日志

2022/04/16 23:06:21 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_HEARTBEAT payload:{"data":"heartbeat@padlocal"}})
2022/04/16 23:06:31 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_MESSAGE payload:{"messageId":"xxxxxxxxxxxxxxx"}})
2022/04/16 23:06:31 PuppetService MessagePayload(xxxxxxxx))
2022/04/16 23:06:31 PuppetService RoomMemberList(xxxxxxxxxxxxx@chatroom)
2022/04/16 23:06:31 PuppetService ContactRawPayload(wxid_xxxxxxxxxx)
2022/04/16 23:06:31 PuppetService RoomMemberList(xxxxxxxxxxxxx@chatroom)
2022/04/16 23:06:31 PuppetService RoomMemberRawPayload(xxxxxxxxxxxxx@chatroom, wxid_xxxxxxxxxx)
2022/04/16 23:06:31 PuppetService RoomMemberList(xxxxxxxxxxxxx@chatroom)
2022/04/16 23:06:31 PuppetService ContactRawPayload(wxid_xxxxxxxxxx)
2022/04/16 23:06:31 PuppetService RoomMemberList(xxxxxxxxxxxxx@chatroom)
2022/04/16 23:06:31 MentionText:[@可馨 add @Chumo(初墨)六号技师 ]
2022/04/16 23:06:31 PuppetService RoomMemberList(xxxxxxxxxxxxx@chatroom)
2022/04/16 23:06:31 搜索用户名ID成功!
2022/04/16 23:06:31 您与对方不是好友, 正在尝试添加!
2022/04/16 23:06:31 PuppetService FriendshipAdd(wxid_xxxxxxxxxx, 你好,我是可馨,以后请多多关照!)
2022/04/16 23:06:32 添加好友失败, 用户名: [Chumo(初墨)]用户ID:[wxid_xxxxxxxxxx], Error: [rpc error: code = Internal desc = [tid:57221f39] request has been cancelled for reason: SERVER_ERROR: 2 UNKNOWN: [tid:57221f39] wechat bad request error]
2022/04/16 23:06:32 PuppetService messageSendText(xxxxxxxxxxxxx@chatroom, 好友申请失败!)
2022/04/16 23:06:32 PuppetService MessagePayload(xxxxxxxx))
2022/04/16 23:06:32 好友申请失败 通知成功!
2022/04/16 23:06:36 PuppetService onGrpcStreamEvent({type:EVENT_TYPE_HEARTBEAT payload:{"data":"heartbeat@padlocal"}})

代码

log.Printf("MentionText:[%s]", message.MentionText())

if strings.Contains(message.MentionText(), "add") { 			// 添加好友 匹配关键字
	addUserName := strings.Replace(strings.Replace(message.Text(), "\u2005", "", -1), "@可馨add @", "", 1) 	// 去掉特殊符号 再 过滤用户名
	if member, err := message.Room().Member(addUserName); err != nil && member == nil { 										//查找用户的 ID
		log.Printf("搜索用户名ID成功!")
		if message.GetWechaty().Friendship().Load(member.ID()).IsReady() { 				// 判断是否是好友
			log.Printf("已经是好友啦!")
		} else { 			// 不是好友
			log.Printf("您与对方不是好友, 正在尝试添加!")
			if err = message.GetWechaty().Friendship().Add(member, "你好,我是可馨,以后请多多关照!"); err != nil {
				log.Printf("添加好友失败, 用户名: [%s]用户ID:[%s], Error: [%s]", member.Name(), member.ID(), err)
			} else {
					log.Printf("成功发送好友申请!")
				}
			}
		}
	}

这篇文章仅授权 wecahty

关于 wechaty 使用一周的感受与教程

你被骗了！！只有标题和这一句话使用中文，其他的都是英文，请手动点击翻译

Type: Individual user
usage mode: Store messages and manage messages

How to Use

What are you going to do

1. Make for the company

   1. Recommend to use

      Polyglot： TypeScript，JavaScript，Java，Python，Go
      Puppet-providers: Service, PadLocal, Xp, Wechat, Wechat4u

2. Make it for yourself

   1. Recommend to use

      Polyglot： JavaScript，Php，Python，Go
      Puppet-providers: Service, Xp, Wechat, Wechat4u

3. Eazy to use

   ## Gateway
   cnpm install -g wechaty wechaty-puppet-xp
   wechaty gateway --puppet {WECHATY_PUPPET} --port {WECHATY_PUPPET_SERVER_PORT} --token {WECHATY_PUPPET_SERVICE_TOKEN} --puppet-token {WECHATY_TOKEN}
   
   ## Server
   .......

How to find Problems

1. Check the issues
2. Chat with everyone

example：

Network error: https://github.com/wechaty/wechaty/issues?q=network+error
Rpc error: https://github.com/wechaty/go-wechaty/search?q=err%3Arpc+error%3A+code+%3D+Unavailable+desc+%3D+connection&type=issues

How to find Document

Api : Message, Room, Friendship

Polyglot : Go, Java, Python

Puppet Providers : WeChat, XP, WeChat4U

Puppet Services : PadLocal, WXWork

Specifications : Wechaty, Plugin, Puppet, Service, Token, Gateway

Quick start

@gateway

## windows puppet-xp port 30000

cnpm install -g [email protected] wechaty-puppet-xp
@wechaty gateway --puppet wechaty-puppet-xp --port 30000 --token insecure_559c97f1-c6a9-39b0-8f98-288b05f315cd --puppet-token f5c70044-42ea-12ca-ae78-b5ece72dde59

## save to bat

@server

// 1. Viper Get config
// 2. viper.Getstring set Arg (wechaty-puppet-xp)
// 3. Third party robot corpus（tuling123）
// 4. WebHook（Dingding，Telegram）

// >>> config.yaml <<<
BOT:
  CHAT: off
Wechaty:
  WECHATY_PUPPET: wechaty-puppet-xp
...

// >>> main.go <<<
package main
import (
	"github.com/spf13/viper"
	"github.com/wechaty/go-wechaty/wechaty"
  // ...
)
func init() {
	log.SetPrefix("[WechatyBot] ") // 设置日志前缀
	log.SetFlags(log.Ltime | log.Lshortfile)

	success := "[\033[01;32m✓\033[0m] "
	faild := "[\033[01;31m✗\033[0m] "
	info := "[\033[01;33m➜\033[0m] "
	rootPath, _ := os.Getwd()

	viper.Set("rootPath", rootPath)
	//...
	if err = viper.ReadInConfig(); err != nil {
		log.Printf("%v读取配置文件失败%v", os.Getenv("faild"), err)
	} else {
		viper.Set("success", success)
		viper.Set("rootPath", rootPath)
		//...
	}
}

func main() {
	Api.DingBot() // Check the dingding configuration
		var bot = wechaty.NewWechaty(wechaty.WithPuppetOption(wp.Option{
		Token:    viper.GetString("Wechaty.WECHATY_PUPPET_SERVICE_TOKEN"),
		Endpoint: viper.GetString("Wechaty.URL"),
	}))
	// 根据观察，这里不要设置 TOKEN 了，全部用Option吧，少年
        // Token 要填写 WECHATY_PUPPET_SERVICE_TOKEN
	bot.OnScan(onScan).
		OnLogin(onLogin).
		OnLogout(onLogout).
		OnError(onError).
		OnMessage(onMessage).
		OnFriendship(onFriendShip)
	bot.DaemonStart()
}

func onMessage(context *wechaty.Context, message *user.Message) {
	if message.Self() {
		log.Printf("%sBot Chat:%s %s \n", viper.GetString("info"), message.From().Name(), message.Text())
	} else if message.From().ID() == viper.GetString("AdminID") {
		if message.Text() == "chat.off" {
			setEnv("CHAT", "off")
		} else if message.Text() == "chat.on" {
			setEnv("CHAT", "on")
		} else {
			Admin.Admin(context, message)
		}
	} else if message.Room() != nil {
    	if viper.GetString("CHAT") !="off"{
				// Private.Chat(context, message)
				message.Say(TulingBot(message.Text())) // TulingBot use tuling123 api
        log.Printf("%s%s @我了 ta 说: %s, 回复了: %s", viper.GetString("info"), message.From().Name(), message.Text(), reply)
		}
	} else {
		//	如果不是群消息，那就是联系人消息
		if viper.GetString("CHAT") !="off"{
      if string(message.Text())=="在吗？" {
        message.Say("来了老弟！")
      }
		}
	}
}
...............
Auth WrchatID == XRSec_MSG

Debug

1. I am using the xp protocol and go language, so I need a gateway as support. It seems that the new version of wechaty will automatically determine whether the IP of the gateway and the server is equal to the IP of the same exit. If they are equal, there is no need to open the port, and no public IP is required
2. The new version requires TLS encryption, if you need to cancel encryption, please set WECHATY_PUPPET_SERVICE_NO_TLS_INSECURE_SERVER=true parameter @environment

XRSec has the right to modify and interpret this article. If you want to reprint or disseminate this article, you must ensure the integrity of this article, including all contents such as copyright notice. Without the permission of the author, the content of this article shall not be modified or increased or decreased arbitrarily, and it shall not be used for commercial purposes in any way

在 ts 版本中:

• alias() 代表 get
• alias(newAlias) 代表 set
• alias(null) 代表 delete

但是在 go 语言里边参数是必传的，所以我准备把 alias 拆分为两个方法。

• GetAlias() 代表 get
• SetAlias("newAlias") 代表 set
• SetAlias("") 代表 delete

这样做是否可以? @huan

设计一个go-wechaty插件，提供HTTP API服务以管理Wechaty的各种功能。有了完善的基础API服务后，后面可根据API做可视化界面、cli、第三方服务等。

Questions from WIP: add user/message.go #4

Q3

Q3: In my understanding, Puppet should be an interface definition, different protocols to implement different classes, but some methods of Puppet have logic, and they cannot have logic in Go's interface definition. I don't know what to do.

Sorry, maybe my understanding of wechaty and wechat-puppet is too simple, and I may need to read and understand them as a whole.

If I'm understanding correctly, our problem is the Go Lang does not permit an abstract class to have any implementation in it?

Please feel free to correct me if I'm wrong.

To be updated... I'm going to study Go now...

Updated Links

• Go Playground - Abstract Class Implementation
• Abstract Class in GO: Complete Guide
• Abstract Class reinvented

help ~

Currently, we are doing a code rewrite and commit automatically in every PR:

github-actions bot commented 24 minutes ago
🚀 Your go files have been formatted successfully

I'd like to change this behavior from rewrite automatically to throw a failure via CI if the code has not been formatted as expected, which can leave the responsibility of the code formatting to the PR author.

Another benefit after this change is that we can also keep our contributor record clean because it can prevent lots of unnecessary commits.

从低版本升级到 v0.4.x 的注意事项

• go-wecahty v0.4.x 可以搭配镜像 wechaty/wechaty:0.78 或 wechaty/wechaty:1.19+ 使用
• 优化了 filebox 设计，修改了 filebox 一些方法的签名，如果升级后编译不通过，不要惊慌，根据编译器提示更改即可(0.x版本非最终确定版本，所以随着使用会重构掉之前不合理的设计)

Please Notice: the port may be other numbers than the default 8788

API Endpoint: https://api.chatie.io/v0/hosties/xxx_token

Return JSON Object:

{"ip":"13.76.3.2","port":8788}

Related to: wechaty/wechaty#1984

Question 1: Is wechaty-puppet-hostie acting as a client? Wechaty-puppet- * can be connected via wechaty-puppet-hostie?

Today I found golang网页版微信Api, 突破网页版登陆限制 and it will be great if we can encapsulate it with our Go Wechaty, so that Go lang users will be able to use Go Wechaty without token for free.

问题：
room.MemberAll 获得所有人列表， 发消息at时没有效果

代码：

日志：