Abel Feng

Hi, I also did some benchmark test, to compare the performance of tonic and grpc-go, the service code is very easy, just return an empty struct ``` async fn read_file(&self,...

你好，我看到你提供的demo例子和你现在的代码差别很大，现在的代码里面已经没有xml标签解析的内容了，请问有没有一个针对当前代码的例子可以看下？

0.2.0-alpha这个版本我跑起来的时候发现一个bug，远程的子事务中如果抛了异常，它不会执行回滚导致数据库的事务没有释放，表一直被锁住。后面最外层事务再去做回滚操作的时候，因为表被锁了，一直不能回滚成功。也就是说这个版本对嵌套事务的z > 也就是说只能最外层事务抛异常了，整个事务的回滚是可以的，如果涉及到远程调用，里面抛了异常出来会回滚失败。不知道新版本有没有解决这个问题。

@liuyangming 我把demo-client包里面的TestServiceImpl里面的 `throw new IllegalStateException();` 注释掉，然后把这句加到demo-server包里面的AccountServiceImpl.incrementAmount方法的`stmt.executeUpdate();`后面，这样就是远程子事务调用失败了。这种情况下数据库的事务没有释放(可以通过`select * from information_schema.innodb_trx`查询到事务还在)。然后执行回滚的时候，因为数据库表被上一个事务锁住，导致事务一直回滚失败。

@BusyJay thank you very much, is making a spawn call in the method the only workaround? If it is that way, I have to write spawn call in every methods...

I have some idea about the design of Sandbox API, it follows the basic idea of the design currently, but it decouples the notion of sandbox and shim or container...

I merged the codes to the recent main branch and summit a PR, it is still a demo codes so the CI checking is still not passed, but you can...

needs rebase after #9736 #9853 #9882 #9883 #9884 #9903 #9904


It is just the podsandbox controller is a little bit special because it manage sandbox by Task plugin. and in https://github.com/containerd/containerd/pull/9884 the sandboxed Task may have dependency on the sandbox...