michaellee8
michaellee8
Server log : ``` 1605358725.414072 cmd_unpack_argv: argv[0]=show-environment 1605358725.414075 cmd_unpack_argv: argv[1]=-g 1605358725.414085 cmd_unpack_argv: argv[2]=TMUX_PLUGIN_MANAGER_PATH 1605358725.414089 cmd_parse_from_arguments: argv[0]=show-environment 1605358725.414092 cmd_parse_from_arguments: argv[1]=-g 1605358725.414095 cmd_parse_from_arguments: argv[2]=TMUX_PLUGIN_MANAGER_PATH 1605358725.414099 cmd_parse_from_arguments: at 0: argv[0]=show-environment 1605358725.414102 cmd_parse_from_arguments: at...
[tmux-server-686.log](https://github.com/tmux-plugins/tpm/files/5540764/tmux-server-686.log)
Actually it breaks in the same way even for https://github.com/nelsonenzo/tmux-appimage
This is a successful log from my system installation of tmux 2.3. ``` 1605368065.946366 client 0x5591a030b640 IDENTIFY_ENVIRON _=/usr/bin/tmux 1605368065.946368 peer 0x5591a030fb50 message 105 1605368065.946373 client 0x5591a030b640 IDENTIFY_ENVIRON EVENT_NOEPOLL=1 1605368065.946376 peer...
Well it turns out it has nothing to do with AppImage, it breaks for all vesion >= 3.1, even for my non-appimage binary. I will look if there are some...
working server log at 3.0a [tmux-server-2162.log](https://github.com/tmux-plugins/tpm/files/5541609/tmux-server-2162.log) You may want to do a tmux split for both less `tmux-server-686.log` and then `less tmux-server-2162.log`, run `/show-environment` on both of them. I saw...
Full logs for both working 3.0a and broken 3.1: working 3.0a: [tmux-client-1287.log](https://github.com/tmux-plugins/tpm/files/5541796/tmux-client-1287.log) [tmux-server-1295.log](https://github.com/tmux-plugins/tpm/files/5541797/tmux-server-1295.log) [tmux-out-1295.log](https://github.com/tmux-plugins/tpm/files/5541798/tmux-out-1295.log) broken 3.1, which is killed with SIGTERM: [tmux-server-1638.log](https://github.com/tmux-plugins/tpm/files/5541799/tmux-server-1638.log) [tmux-client-1630.log](https://github.com/tmux-plugins/tpm/files/5541800/tmux-client-1630.log) (out is not avilable since it is...
After one Sunday of debug now I understand this problem now. When I start an AppImage instance of tmux (3.1b), it uses the newer file-based protocol that uses MSG_WRITE suite...
Some additional information: I have tried v1.22 on minikube and it works, but v1.21 on GKE Autopilot stable and v1.22 on GKE Autopilot regular both got the exact same MountVolume.SetUp...
Still got the problem after this patch, no idea why, investigating.