1 files changed, 42 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/118/socket/1612908 b/results/classifier/zero-shot/118/socket/1612908
new file mode 100644
index 00000000..262d73d0
--- /dev/null
+++ b/results/classifier/zero-shot/118/socket/1612908
@@ -0,0 +1,42 @@
+socket: 0.854
+network: 0.686
+mistranslation: 0.622
+device: 0.614
+graphic: 0.547
+semantic: 0.481
+user-level: 0.441
+architecture: 0.395
+performance: 0.358
+ppc: 0.285
+x86: 0.241
+hypervisor: 0.197
+kernel: 0.194
+register: 0.194
+peripherals: 0.194
+i386: 0.191
+vnc: 0.187
+debug: 0.177
+boot: 0.149
+VMM: 0.143
+arm: 0.135
+risc-v: 0.132
+permissions: 0.131
+virtual: 0.119
+TCG: 0.104
+assembly: 0.098
+files: 0.092
+PID: 0.074
+KVM: 0.054
+
+qom-[list,tree,get,set] don't accept tcp endpoint arg
+
+Hi, 
+
+I'm using origin/master [6bbbb0ac13...]. When I run any of the commands in 'qemu/scripts/qmp/qom-[list,tree,get,set]', the help text says that it can connect to a QEMU instance by passing either a path to a unix socket or a tcp endpoint in the format "host:port". The unix socket variant works but the tcp endpoint variant does not. QEMUMonitorProtocol accepts either a string (unix socket) or a tuple (host,port). None of the qom-* scripts actually massage the '-s' argument into a tuple. 
+
+I have a patch to fix this issue that I can submit to the developer list.
+
+Hi! Triaging old bug tickets ... is this still an issue with the latest version of QEMU? If you've got a patch for this ready, please send it to the qemu-devel mailing list!
+
+[Expired for QEMU because there has been no activity for 60 days.]
+