Mohanson

这是我目前在用的服务端和客户端的配置, 你可以试一下 **server** ``` daze server -e asheshadow -l 0.0.0.0:80 -m http://127.0.0.1:20001 ``` **client** ``` daze client -s $SERVER:80 -e asheshadow -r https://raw.githubusercontent.com/mohanson/rule.ls/master/rule.ls -f auto ``` systemd 我没有写过, 我是用 supervisor...

你配置 supervisor 的时候或者 systemd 的时候, 带上 HOME=/tmp 环境变量试试? 服务端混淆只在 asheshadow 协议下有效, 可以是域名或 ip:port 形式. 服务端你直接输入 "daze server -e asheshadow -l 0.0.0.0:80 -m http://httpbin.org", 然后浏览器访问 80 端口也不行吗?

1) 非混淆 (-e asheshadow) 情况可以正常跑么? 2) 确认你服务器的时间与 PC 的时间相差在 2 分钟之内. 为了避免重放攻击, 协议内加入了时间戳并强制要求请求的时间戳差值在 2 分钟之内 3) 可以 nginx 改为监听 8888 端口, daze server 监听 80 端口并配置 -m http://127.0.0.1:8888 4) "-k"...

In the end we adopted shift = 2, see [https://github.com/nervosnetwork/ckb-vm/commit/d6be30f410913e88d8a5890f636b0c4378931a52](https://github.com/nervosnetwork/ckb-vm/commit/d6be30f410913e88d8a5890f636b0c4378931a52)

`current_cycles` has been added at ckb2021. https://github.com/nervosnetwork/rfcs/blob/master/rfcs/0034-vm-syscalls-2/0034-vm-syscalls-2.md

I'm guessing there's a bug somewhere, but I don't know how to start right now. I'll try to analyze it, thanks for the report.

> There are some hard limits to the system, such as: > > * How many VMs can be instantiated at the same time? > * The maximum number of...

Is there an official testsuit currently available? Even very simple.

This is exactly what I want to express, there are many wasm vm implementations in the world, and they all have their own wasi test cases, which seems inconsistent. I...

这主要是一个演示项目, 其展示了如何在 golang 中调用 c++ 代码, 性能和速度的主要是由 setaface 这个 c++ 项目决定的, 你可以前往 setaface 项目查看详细的性能报告. 由于在 go 代码中使用的是 cgo 进行包装, 性能相比 c++ 会有略微损失. 不过总的来说性能还不错, 曾线上运行过一段时间.