plesty-bench 0.4.0.dev1__tar.gz → 0.4.2__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (216) hide show
  1. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/.gitlab-ci.yml +54 -21
  2. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/CHANGELOG.md +109 -12
  3. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/PKG-INFO +5 -5
  4. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/gui/menus.md +5 -1
  5. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/gl-secret-detection-report.json +6 -6
  6. plesty_bench-0.4.2/packaging/versioning.py +72 -0
  7. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/packaging/windows/install.ps1 +47 -18
  8. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/packaging/windows/plesty-server.iss +19 -8
  9. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/bench/cli.py +8 -2
  10. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/bench/client.py +12 -1
  11. plesty_bench-0.4.2/plesty/bench/streams.py +45 -0
  12. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/cli/main.py +2 -32
  13. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/model/catalogue.py +34 -1
  14. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/presenter/bench.py +7 -0
  15. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/services/agent.py +76 -2
  16. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/services/installer.py +83 -5
  17. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/services/launch.py +30 -7
  18. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/view/dialogs.py +118 -26
  19. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/pyproject.toml +24 -29
  20. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/reports/check.json +12 -5
  21. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_agent.py +48 -0
  22. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_bench.py +13 -0
  23. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_catalogue.py +31 -0
  24. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_cli.py +20 -1
  25. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_installer.py +125 -0
  26. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_jobs.py +25 -0
  27. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_problem_report.py +3 -1
  28. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_view.py +79 -3
  29. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_view_experiment.py +65 -1
  30. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/uv.lock +26 -26
  31. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/.gitignore +0 -0
  32. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/LICENSE +0 -0
  33. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/LICENSES/LGPL-3.0-or-later.txt +0 -0
  34. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/README.md +0 -0
  35. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/REUSE.toml +0 -0
  36. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/api_reference.md +0 -0
  37. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/cli/files.md +0 -0
  38. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/cli/index.md +0 -0
  39. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/cli/plesty-bench.md +0 -0
  40. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/cli/plesty-server.md +0 -0
  41. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/cross_bench.md +0 -0
  42. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/design/agent.md +0 -0
  43. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/design/architecture.md +0 -0
  44. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/design/console.md +0 -0
  45. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/design/cross_platform.md +0 -0
  46. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/design/experiments.md +0 -0
  47. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/design/index.md +0 -0
  48. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/design/installer.md +0 -0
  49. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/design/packaging.md +0 -0
  50. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/design/ports.md +0 -0
  51. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/design/processes.md +0 -0
  52. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/gui/devices.md +0 -0
  53. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/gui/experiments.md +0 -0
  54. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/gui/index.md +0 -0
  55. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/bench_overview.svg +0 -0
  56. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/cross_bench.svg +0 -0
  57. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-data-collapse.png +0 -0
  58. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-data-expand.png +0 -0
  59. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-device-clear_log.png +0 -0
  60. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-device-control.png +0 -0
  61. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-device-edit.png +0 -0
  62. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-device-field_test.png +0 -0
  63. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-device-install.png +0 -0
  64. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-device-remove.png +0 -0
  65. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-device-restart.png +0 -0
  66. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-device-start.png +0 -0
  67. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-device-stop.png +0 -0
  68. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-device-uninstall.png +0 -0
  69. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-device-update.png +0 -0
  70. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-exp-create.png +0 -0
  71. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-exp-duplicate.png +0 -0
  72. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-exp-load.png +0 -0
  73. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-experiment-abort.png +0 -0
  74. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-experiment-configure.png +0 -0
  75. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-experiment-install.png +0 -0
  76. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-experiment-open.png +0 -0
  77. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-experiment-pause.png +0 -0
  78. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-experiment-remove.png +0 -0
  79. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-experiment-run.png +0 -0
  80. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-experiment-stop.png +0 -0
  81. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-experiment-update.png +0 -0
  82. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-fleet-control.png +0 -0
  83. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-fleet-declare.png +0 -0
  84. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-fleet-down.png +0 -0
  85. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-fleet-refresh.png +0 -0
  86. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/btn-fleet-up.png +0 -0
  87. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/capture.py +0 -0
  88. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/capture_cross_bench.py +0 -0
  89. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/control-window.png +0 -0
  90. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/detail-card.png +0 -0
  91. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/detail-jobs.png +0 -0
  92. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/detail-log.png +0 -0
  93. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/detail-reports.png +0 -0
  94. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/detail-terminal.png +0 -0
  95. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/detail-traffic.png +0 -0
  96. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/devices-card.png +0 -0
  97. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/dialog-add-experiment.png +0 -0
  98. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/dialog-agent.png +0 -0
  99. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/dialog-configure-tab2.png +0 -0
  100. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/dialog-configure.png +0 -0
  101. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/dialog-create-run.png +0 -0
  102. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/dialog-declare.png +0 -0
  103. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/dialog-device-config-tab2.png +0 -0
  104. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/dialog-device-config.png +0 -0
  105. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/dialog-field-test.png +0 -0
  106. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/dialog-fleet-file.png +0 -0
  107. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/dialog-load-from.png +0 -0
  108. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/dialog-problem.png +0 -0
  109. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/run-data.png +0 -0
  110. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/run-log.png +0 -0
  111. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/run-report.png +0 -0
  112. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/run-visualization.png +0 -0
  113. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/runs-card.png +0 -0
  114. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/start-device.gif +0 -0
  115. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/status-line.png +0 -0
  116. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/take-control.gif +0 -0
  117. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/window-devices.png +0 -0
  118. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/window-experiments.png +0 -0
  119. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/xbench-completed.png +0 -0
  120. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/xbench-devices-before.png +0 -0
  121. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/xbench-devices-during.png +0 -0
  122. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/xbench-dialog-agent.png +0 -0
  123. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/xbench-dialog-benches.png +0 -0
  124. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/xbench-dialog-configure-tab2.png +0 -0
  125. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/xbench-dialog-create-run.png +0 -0
  126. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/xbench-report-fss.png +0 -0
  127. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/xbench-report-setup.png +0 -0
  128. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/xbench-report.gif +0 -0
  129. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/xbench-run.gif +0 -0
  130. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/imgs/gui/xbench-visualization.png +0 -0
  131. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/index.md +0 -0
  132. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/install.md +0 -0
  133. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/toc.yaml +0 -0
  134. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/usage/experiment.md +0 -0
  135. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/usage/field_test.md +0 -0
  136. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/usage/first_bench.md +0 -0
  137. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/usage/headless.md +0 -0
  138. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/usage/index.md +0 -0
  139. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/usage/maintenance.md +0 -0
  140. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/usage/modules.md +0 -0
  141. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/docs/usage/remote.md +0 -0
  142. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/packaging/install.sh +0 -0
  143. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/packaging/plesty-mark.png +0 -0
  144. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/packaging/server_dist.py +0 -0
  145. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/packaging/windows/build-installer.ps1 +0 -0
  146. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/packaging/windows/probes/README.md +0 -0
  147. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/packaging/windows/probes/probe.iss +0 -0
  148. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/packaging/windows/probes/probe.ps1 +0 -0
  149. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/packaging/windows/probes/probe2.iss +0 -0
  150. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/packaging/windows/probes/probe2.ps1 +0 -0
  151. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/packaging/windows/uninstall.ps1 +0 -0
  152. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/bench/__init__.py +0 -0
  153. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/__init__.py +0 -0
  154. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/__main__.py +0 -0
  155. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/assets/console.qss +0 -0
  156. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/assets/env.example +0 -0
  157. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/assets/fleet.example.yaml +0 -0
  158. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/assets/plesty-mark.svg +0 -0
  159. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/assets/report.css +0 -0
  160. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/assets/report.html +0 -0
  161. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/cli/__init__.py +0 -0
  162. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/config.yaml +0 -0
  163. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/host.py +0 -0
  164. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/model/__init__.py +0 -0
  165. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/model/agent.py +0 -0
  166. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/model/device.py +0 -0
  167. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/model/device_manager.py +0 -0
  168. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/model/envfile.py +0 -0
  169. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/model/errors.py +0 -0
  170. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/model/experiment.py +0 -0
  171. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/model/field_test.py +0 -0
  172. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/model/fleet.py +0 -0
  173. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/model/home.py +0 -0
  174. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/model/job.py +0 -0
  175. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/model/peer.py +0 -0
  176. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/model/ports.py +0 -0
  177. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/model/process.py +0 -0
  178. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/model/purge.py +0 -0
  179. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/model/traffic.py +0 -0
  180. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/presenter/__init__.py +0 -0
  181. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/reexec.py +0 -0
  182. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/services/__init__.py +0 -0
  183. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/services/catalogue.py +0 -0
  184. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/services/control.py +0 -0
  185. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/services/experiments.py +0 -0
  186. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/services/gitbin.py +0 -0
  187. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/services/jobs.py +0 -0
  188. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/services/nodes.py +0 -0
  189. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/services/problem_report.py +0 -0
  190. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/services/run_report.py +0 -0
  191. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/services/supervisor.py +0 -0
  192. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/view/__init__.py +0 -0
  193. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/view/app.py +0 -0
  194. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/view/control.py +0 -0
  195. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/view/window.py +0 -0
  196. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/plesty/server/view/workers.py +0 -0
  197. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/__init__.py +0 -0
  198. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/conftest.py +0 -0
  199. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/fake_server.py +0 -0
  200. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_agent_settings.py +0 -0
  201. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_control.py +0 -0
  202. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_device_manager.py +0 -0
  203. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_experiments.py +0 -0
  204. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_field_test.py +0 -0
  205. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_fleet.py +0 -0
  206. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_gitbin.py +0 -0
  207. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_home.py +0 -0
  208. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_host.py +0 -0
  209. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_job.py +0 -0
  210. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_nodes.py +0 -0
  211. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_packaging.py +0 -0
  212. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_purge.py +0 -0
  213. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_run_report.py +0 -0
  214. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_server.py +0 -0
  215. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_supervisor.py +0 -0
  216. {plesty_bench-0.4.0.dev1 → plesty_bench-0.4.2}/tests/test_traffic.py +0 -0
@@ -7,6 +7,8 @@ stages:
7
7
  variables:
8
8
  # Required for versioningit: the runner must fetch full Git history and tags.
9
9
  GIT_DEPTH: "0"
10
+ # The runner tests:windows runs on; see that job.
11
+ WINDOWS_RUNNER_TAG: plesty-windows
10
12
 
11
13
  include:
12
14
  - component: $CI_SERVER_FQDN/plesty/plesty-ci/plesty-standard-ci@main
@@ -36,39 +38,69 @@ hub-release:
36
38
  # never happened, and a green pipeline says nothing about the platform the
37
39
  # benches run on.
38
40
  #
39
- # Runs where hub-check runs (merge requests, the default branch, exp) and on
40
- # tags. Coverage is measured on Linux, where the gate is; here the outcome is
41
- # the point, so pytest runs plain.
41
+ # Runs where hub-check runs (merge requests, the default branch, exp, every
42
+ # maintain/* line) and on tags. Coverage is measured on Linux, where the gate
43
+ # is; here the outcome is the point, so pytest runs plain.
44
+ #
45
+ # On the project's own Windows runner (tag plesty-windows: a lab PC, a
46
+ # dedicated non-admin account, shell executor). GitLab's hosted Windows runner
47
+ # spent 3 min starting a VM and 4 min on `uv sync` with nothing cached, of an
48
+ # 18-minute job; this one keeps its uv cache between jobs. While it is offline,
49
+ # set the project CI/CD variable WINDOWS_RUNNER_TAG=saas-windows-medium-amd64
50
+ # to run on the hosted runner again — no commit needed.
42
51
  # ---------------------------------------------------------------------------
43
52
  tests:windows:
44
53
  stage: check
45
54
  tags:
46
- - saas-windows-medium-amd64
55
+ - $WINDOWS_RUNNER_TAG
47
56
  rules:
48
57
  - if: $CI_PIPELINE_SOURCE == "merge_request_event"
49
58
  - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
50
59
  - if: $CI_COMMIT_BRANCH == "exp"
60
+ - if: $CI_COMMIT_BRANCH =~ /^maintain\//
51
61
  - if: $CI_COMMIT_TAG
52
- timeout: 30 minutes
62
+ timeout: 20 minutes
63
+ hooks:
64
+ # Before the checkout is cleaned: python an earlier, killed job of this
65
+ # account left running holds the .venv's DLLs open, and the clean then
66
+ # fails ("failed to remove … Qt6Core.dll") before any script line runs.
67
+ pre_get_sources_script:
68
+ # Ends on $true: with nothing to end, Get-Process still fails the line, and
69
+ # the runner stops the job on any line that failed.
70
+ - Get-Process python -ErrorAction SilentlyContinue | ForEach-Object { "stale python $($_.Id) started $($_.StartTime)"; Stop-Process -Id $_.Id -Force -ErrorAction SilentlyContinue }; $true
53
71
  variables:
72
+ # The .venv survives the clean, so `uv sync` updates it rather than
73
+ # rebuilding it; installs guard against a .venv left without pyvenv.cfg.
74
+ GIT_CLEAN_FLAGS: -ffdx -e .venv
54
75
  UV_LINK_MODE: copy
55
- # No cache, deliberately. Measured on this runner: restoring it took 4m03s
56
- # and saving it several minutes more, to speed a `uv sync` that takes 1m35s
57
- # even when the cache is warm. It cost about ten minutes of a twenty-two
58
- # minute job to save one and a half. Downloading the wheels afresh is the
59
- # cheaper half of that trade.
60
- UV_CACHE_DIR: .uv_cache
76
+ # No GitLab cache: on the hosted runner restoring it took 4 min to save 1½.
77
+ # And no UV_CACHE_DIR inside the checkout, which is cleaned before each job:
78
+ # uv keeps its cache in the runner account's own profile, so on the
79
+ # project's runner a `uv sync` downloads only what changed.
61
80
  # tests/test_view.py drives the Qt console and the runner has no desktop
62
81
  QT_QPA_PLATFORM: offscreen
63
82
  before_script:
64
- - powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
83
+ # One statement per line: the runner hands PowerShell this a line at a time.
84
+ # The job shell takes Ctrl+Break itself. PowerShell otherwise breaks into its
85
+ # debugger on one, and that debugger reads the rest of this script from the
86
+ # same stdin the runner feeds it on: the first job on the project's runner
87
+ # sat there 25 min after a test's stop signal reached this console.
88
+ - Add-Type -TypeDefinition 'using System; using System.Runtime.InteropServices; public static class CtrlBreakGuard { public delegate bool Handler(uint kind); static readonly Handler keep = kind => kind == 1; [DllImport("kernel32.dll")] static extern bool SetConsoleCtrlHandler(Handler h, bool add); public static bool Install() { return SetConsoleCtrlHandler(keep, true); } }'; [void][CtrlBreakGuard]::Install()
65
89
  - $env:Path = "$env:USERPROFILE\.local\bin;$env:Path"
90
+ # The project's runner keeps uv between jobs; the hosted one starts bare.
91
+ - if (-not (Get-Command uv -ErrorAction SilentlyContinue)) { powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex" }
66
92
  - uv --version
67
93
  script:
68
- # --all-extras: the Qt console is part of what a bench runs on Windows
69
- - uv sync --frozen --all-extras
94
+ # --all-extras: the Qt console is part of what a bench runs on Windows.
95
+ # Retried: an on-access scanner holding an .exe uv just wrote fails the sync
96
+ # with os error -2147024786, and the file is fine moments later.
97
+ # A .venv without pyvenv.cfg runs the base interpreter, and uv then installs
98
+ # into the account's own Python: a clean that a locked DLL interrupted left
99
+ # one behind, kept since .venv survives the clean. Removed, uv builds it anew.
100
+ - if ((Test-Path .venv) -and -not (Test-Path .venv\pyvenv.cfg)) { "removing a hollow .venv"; Remove-Item -Recurse -Force .venv }; $true
101
+ - for ($i = 1; $i -le 3; $i++) { uv sync --frozen --all-extras; if ($LASTEXITCODE -eq 0) { break }; Start-Sleep -Seconds (5 * $i) }; if ($LASTEXITCODE -ne 0) { exit $LASTEXITCODE }
70
102
  # -v so the log names the test that is running when something wedges, and a
71
- # per-test timeout so a wedge is a traceback rather than the job's 30
103
+ # per-test timeout so a wedge is a traceback rather than the job's 20
72
104
  # minutes: `-q` reports failures only in a summary a hang never reaches,
73
105
  # which is exactly how the first run of this job came back unreadable.
74
106
  - uv run pytest -v -rf --timeout=120 --timeout-method=thread
@@ -166,13 +198,14 @@ installer:windows:
166
198
  # built with one fails on every machine). On a tag it is the tag; an
167
199
  # installer/<name> branch proves a script change against the last release,
168
200
  # or against INSTALLER_VERSION when set.
201
+ #
202
+ # One statement per line: the runner hands PowerShell this block a line at
203
+ # a time, so an `elseif` opening a line of its own is an unknown command,
204
+ # and a `throw` does not end the job. Both happened on every installer/*
205
+ # branch -- the job built a setup.exe pinned to an empty version and passed.
169
206
  - |
170
- if ($env:CI_COMMIT_TAG) { $VERSION = $env:CI_COMMIT_TAG -replace '^v', '' }
171
- elseif ($env:INSTALLER_VERSION) { $VERSION = $env:INSTALLER_VERSION -replace '^v', '' }
172
- else { $VERSION = (git describe --tags --abbrev=0) -replace '^v', '' }
173
- if ($VERSION -notmatch '^[0-9]+\.[0-9]+\.[0-9]+$') {
174
- throw "not a released version: '$VERSION' -- set INSTALLER_VERSION to the release to pin"
175
- }
207
+ if ($env:CI_COMMIT_TAG) { $VERSION = $env:CI_COMMIT_TAG -replace '^v', '' } elseif ($env:INSTALLER_VERSION) { $VERSION = $env:INSTALLER_VERSION -replace '^v', '' } else { $VERSION = (git describe --tags --abbrev=0) -replace '^v', '' }
208
+ if ($VERSION -notmatch '^[0-9]+\.[0-9]+\.[0-9]+$') { Write-Error "not a released version: '$VERSION' -- set INSTALLER_VERSION to the release to pin"; exit 1 }
176
209
  "installer pins plesty-server[gui]==$VERSION"
177
210
  - uv sync --frozen --group build
178
211
  - uv run --group build python -c "from PIL import Image; Image.open('packaging/plesty-mark.png').save('packaging/plesty-mark.ico', sizes=[(256,256),(128,128),(64,64),(48,48),(32,32),(16,16)])"
@@ -2,7 +2,106 @@
2
2
 
3
3
  The format is based on [Keep a Changelog](https://keepachangelog.com).
4
4
 
5
- ## [Unreleased]
5
+ ## [0.4.2] - 2026-10-03
6
+
7
+ ### Fixed
8
+ - **An experiment's views load inside the console again.** The console runs on
9
+ Python 3.12, and a module asking for `>=3.12` was built on the newest Python
10
+ uv had — plesty-pol-pl on 3.14 — so its views could not be loaded in the
11
+ console and opened in a window of their own. Every module environment is now
12
+ built on the console's Python; one already installed moves onto it with its
13
+ next install or update. A module that requires a newer Python is still built
14
+ on what it asks for, and the install log says its views will open separately.
15
+ - **Installing while PLESTY Bench is open says so, instead of breaking the next
16
+ install.** The Windows installer could not remove the old environment while
17
+ the console held it open, failed to create the new one on top of it, and left
18
+ one on Python 3.12 without pip; the next run reused it and failed with "No
19
+ module named pip". The environment is now reused only when pip runs in it, and
20
+ one that cannot be removed stops the install with "PLESTY Bench is probably
21
+ still running — close it, then run this installer again".
22
+ - **`plesty-bench` keeps non-ASCII characters when its output is piped on
23
+ Windows.** The client wrote a pipe in the ANSI codepage, so a reply's `…`
24
+ arrived as one byte and was shown as `à` — the same for `°` or `µ` in a
25
+ relayed log. It now sets up its output as `plesty-server` does: UTF-8 into a
26
+ pipe or file, the console's own encoding (with `?` for what it cannot draw)
27
+ on a terminal.
28
+ - **Configure no longer saves a number outside the bounds the module declares.**
29
+ A spin box showed as many decimals as the value had and rounded its range to
30
+ them, so pol-pl's step (0.01–90°, default 2.0) accepted 0.0 and Save wrote
31
+ `hwp.step_deg: 0.0`, which the experiment refuses. The box now keeps enough
32
+ decimals for its bounds, and Save refuses a value outside them with the bound
33
+ it broke.
34
+ - **A build from the 0.4 maintenance line is numbered as a 0.4 build.** A
35
+ snapshot took its number from the last tag by bumping the minor, so a test
36
+ installer built from `maintain/0.4` called itself `0.5.0.dev35` — above the
37
+ 0.4.2 it was a candidate for, so installing that release over it read as a
38
+ downgrade. Snapshots now follow plesty-sdk's rule (`packaging/versioning.py`):
39
+ the next minor on `exp` and `main`, the next patch on a maintenance line.
40
+ - **Checking a device that is just stopping no longer fails on Windows.** A
41
+ device's exit code is written to a temporary file and moved into place, and
42
+ Windows refuses to open the file during that move: the supervisor raised
43
+ `PermissionError` instead of answering whether the device still ran. The read
44
+ is tried again briefly, and a file still refused counts as not written yet.
45
+ - **A started run's configuration can be read in full (#16).** Configure
46
+ disabled its whole form for a run that had started, which also stopped it
47
+ scrolling and took *Edit YAML…* with it, so a long configuration could not
48
+ be seen. The form now scrolls with every field read-only, and *View YAML…*
49
+ opens the run's file without letting it change.
50
+ - **Save in *Server ▸ Benches…* keeps an edit not confirmed with Enter (#17).**
51
+ A cell still being edited when Save was clicked kept its old text, on macOS
52
+ where a button takes no focus: the old address was written while the new one
53
+ showed, and the console went on dialling a bench that had moved. Every read of
54
+ the list now takes in the open edit first — in the Device Setup tab's benches
55
+ too, which share the list.
56
+ - **`plesty-bench -b HOST` reads the bench's replies right (#19).** The agent
57
+ captured what a command printed by swapping the whole process's output, and it
58
+ answers several requests at once, so commands running together wrote into each
59
+ other's replies: a `jobs cancel` printed the `[]` of a console's job poll, and
60
+ a followed `install` received an empty log and crashed although the install
61
+ ran. Each request now captures only its own output. The client also no longer
62
+ follows a job command asked for `--help`, and a log reply it cannot read says
63
+ the job is still running instead of raising.
64
+ - **The Marketplace offers only experiments that can be configured (#15).**
65
+ Configure builds its form from what an experiment answers to `--manifest`,
66
+ and no experiment on the hub answered it: each installed, then failed with
67
+ "unrecognized arguments: --manifest". An experiment is now listed once its
68
+ published check passed on plesty-sdk 0.5 or newer, whose Experiment Manifest
69
+ gate proves it answers; installing one that has not is refused with that
70
+ reason. *Hub ▸ Load from…* still runs any checkout.
71
+ - **Create offers every configuration of an experiment installed from the
72
+ Marketplace.** For an experiment not declared yet, the Config list held the
73
+ default file alone, so the demo's `config/demo.yaml` could not be chosen; it
74
+ now lists the checkout's `config/` folder, as it already did for one loaded
75
+ with *Hub ▸ Load from…*.
76
+ - **A module installed from a repository gets an environment of its own,
77
+ every time.** A `.venv` that an interrupted install left as its launcher
78
+ alone, without `pyvenv.cfg`, runs the shared uv Python instead, and the next
79
+ install put the module and all its dependencies there without a word: found
80
+ on a bench whose plesty-pol-pl, plesty-fss and plesty-lib sat in the shared
81
+ Python 3.14. Such a `.venv` is now rebuilt before the install, an install
82
+ that still leaves one fails and says so, and *Load from…* refuses a folder
83
+ whose `.venv` is in that state rather than touching it.
84
+
85
+ ## [0.4.1] - 2026-09-30
86
+
87
+ ### Fixed
88
+ - **The Windows installer builds the application on Python 3.12, whatever
89
+ other Python the machine has.** On a computer whose only Python managed by
90
+ uv was another version, it built the application's environment on that one —
91
+ 3.10 on the bench that reported it — where no plesty-server release installs,
92
+ and the wizard said the build or the network was at fault. It now fetches a
93
+ 3.12 when there is none, and rebuilds an environment an earlier installer
94
+ left on another version, so running the new installer is the whole repair.
95
+ Should the Python ever be wrong again, the wizard says so.
96
+ - **A failed install can be closed.** The wizard left a greyed Next and no
97
+ other button — Inno Setup hides Cancel once the files are copied — so the
98
+ window could only be closed from its title bar. Next now leads to a last
99
+ page that says the application was not installed and where the log is.
100
+
101
+ ## [0.4.0] - 2026-09-29
102
+
103
+ Opens the 0.4 line. Supported lines: 0.4 and 0.3 (`maintain/0.3`); 0.2 is
104
+ retired.
6
105
 
7
106
  ### Added
8
107
  - **A run keeps its own report.** When a run ends — completed, stopped,
@@ -234,13 +333,14 @@ The format is based on [Keep a Changelog](https://keepachangelog.com).
234
333
  one. The operator's notes, which the pane also called "reports", are now
235
334
  under **Notes**: two different things under one heading was what made the
236
335
  pane hard to read.
237
- - **Requires plesty-lib 0.5.0.dev6** (was 0.5.0.dev5), which retires
238
- `PLESTY_DATA_DIR` and `PLESTY_DATA_MOUNT` for the one shared root
239
- `PLESTY_DATA` and makes a manifest's `run_root` relative to the shared point.
240
- A run's environment is built from that contract, so a console on dev5 and a
241
- module on dev6 do not agree on where a run writes. Still a prerelease until
242
- the bound moves to 0.5.0, but the Windows installer needs no flag for it: it
243
- installs with pip, which takes a prerelease a requirement names.
336
+ - **Requires plesty-lib 0.5.0** (was 0.4.0), the released version, so a
337
+ bench installs stable versions only. It retires `PLESTY_DATA_DIR` and
338
+ `PLESTY_DATA_MOUNT` for the one shared root `PLESTY_DATA` and makes a
339
+ manifest's `run_root` relative to the shared point. A run's environment is
340
+ built from that contract, so a module still on plesty-lib 0.4 and this
341
+ console do not agree on where a run writes.
342
+ - **Developed and checked with plesty-sdk 0.5.0** (was 0.3.5), the SDK
343
+ released with the plesty-lib 0.5 line.
244
344
  - **The tables refresh every second**, not every three: the Progress column
245
345
  follows a run step by step instead of jumping several at a time.
246
346
  - **The report's raw data is one table per kind of step**, one short line per
@@ -249,10 +349,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com).
249
349
  day with its date said once. A step recorded once, such as the rig's
250
350
  identity, is a list of its fields.
251
351
  - **The window has two halves, Devices and Experiment**, and the menu bar reads
252
- File, Edit, Device, Experiment, Hub, Server, View, Help. The Experiment tab is
253
- empty and every item of the Experiment menu is disabled in this version: they
254
- are built now so that the window does not change shape when the work behind
255
- them lands.
352
+ File, Edit, Device, Experiment, Hub, Server, View, Help.
256
353
  - **The documentation is rewritten for the people who use a bench.** It is in
257
354
  three parts — *GUI*, the window element by element with its real buttons,
258
355
  dialogs and screenshots; *CLI*, every command, file and setting; *Usages*,
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: plesty-bench
3
- Version: 0.4.0.dev1
3
+ Version: 0.4.2
4
4
  Summary: Client for a PLESTY bench running plesty-server: run its commands and fetch its reports from another machine.
5
5
  Author-email: Yunshuang Yuan <yuanyunshuang@gmail.com>
6
6
  Maintainer-email: Plesty Development Team <plesty.dev@example.com>
@@ -11,14 +11,14 @@ Requires-Python: >=3.12
11
11
  Requires-Dist: click>=8.1
12
12
  Requires-Dist: pyzmq>=26
13
13
  Provides-Extra: control
14
- Requires-Dist: plesty-lib[gui]>=0.5.0.dev8; extra == 'control'
14
+ Requires-Dist: plesty-lib[gui]>=0.5.0; extra == 'control'
15
15
  Provides-Extra: gui
16
- Requires-Dist: plesty-lib[gui]>=0.5.0.dev8; extra == 'gui'
17
- Requires-Dist: plesty-lib[report]>=0.5.0.dev8; extra == 'gui'
16
+ Requires-Dist: plesty-lib[gui]>=0.5.0; extra == 'gui'
17
+ Requires-Dist: plesty-lib[report]>=0.5.0; extra == 'gui'
18
18
  Requires-Dist: pyside6==6.11.2; extra == 'gui'
19
19
  Requires-Dist: pyyaml>=6.0; extra == 'gui'
20
20
  Provides-Extra: server
21
- Requires-Dist: plesty-lib[report]>=0.5.0.dev8; extra == 'server'
21
+ Requires-Dist: plesty-lib[report]>=0.5.0; extra == 'server'
22
22
  Requires-Dist: pyyaml>=6.0; extra == 'server'
23
23
  Description-Content-Type: text/markdown
24
24
 
@@ -98,7 +98,11 @@ Installing a module declares nothing: afterwards,
98
98
 
99
99
  ### Marketplace…
100
100
 
101
- The hub's device and experiment modules at the quantum standard. Search by
101
+ The hub's device and experiment modules at the quantum standard. An
102
+ experiment is listed only once its published check passed on plesty-sdk 0.5
103
+ or newer, which shows it publishes the settings the **Configure** dialog is
104
+ built from; one that does not yet can still be run from a checkout with
105
+ [Load from…](#load-from). Search by
102
106
  name, vendor or description, and narrow by kind and vendor; the table shows
103
107
  each module's latest release, what this bench already has, and whether it
104
108
  passes its checks and field tests.
@@ -19,19 +19,19 @@
19
19
  "version": "8.30.1"
20
20
  },
21
21
  "type": "secret_detection",
22
- "start_time": "2026-09-25T15:49:00",
23
- "end_time": "2026-09-25T15:49:00",
22
+ "start_time": "2026-10-03T07:44:54",
23
+ "end_time": "2026-10-03T07:44:55",
24
24
  "status": "success",
25
25
  "observability": {
26
26
  "events": [
27
27
  {
28
28
  "event": "collect_secrets_analyzer_scan_metrics_from_pipeline",
29
- "time_s": 0.513604419,
29
+ "time_s": 0.28747632,
30
30
  "exit_code": 0,
31
31
  "git_strategy": "FetchShallow",
32
- "repo_size_kb": 11214,
33
- "commit_count": 1,
34
- "bytes_scanned": 563,
32
+ "repo_size_kb": 10617,
33
+ "commit_count": 26,
34
+ "bytes_scanned": 60822,
35
35
  "pipeline_type": "Tag"
36
36
  },
37
37
  {
@@ -0,0 +1,72 @@
1
+ # SPDX-FileCopyrightText: 2026 Plesty Development Team
2
+ # SPDX-FileContributor: Yunshuang Yuan
3
+ #
4
+ # SPDX-License-Identifier: LGPL-3.0-or-later
5
+
6
+ """What a build between two tags calls itself, decided by the line it is on.
7
+
8
+ A snapshot is named for the release it is working towards, and which release
9
+ that is depends on the branch:
10
+
11
+ =================== ================== ==========================
12
+ branch last tag snapshot
13
+ =================== ================== ==========================
14
+ ``exp`` / ``main`` ``v0.5.0.dev3`` ``0.5.0.devN``
15
+ ``exp`` / ``main`` ``v0.4.1`` ``0.5.0.devN``
16
+ ``maintain/0.4`` ``v0.4.1`` ``0.4.2.devN``
17
+ anything else either the release the tag precedes
18
+ =================== ================== ==========================
19
+
20
+ Neither of versioningit's own methods gets every row right:
21
+
22
+ - ``minor`` bumps past a prerelease, so ``exp`` sitting on ``v0.5.0.dev3``
23
+ builds ``0.6.0.devN`` — a whole minor it is not working towards.
24
+ - ``smallest-release`` is right on a maintenance line and wrong on ``exp`` the
25
+ moment a release is merged back into it: ``git describe`` then finds the
26
+ release's own tag rather than the line's, and ``exp`` builds ``0.4.2.devN``.
27
+
28
+ The rule reads the branch instead, so it says the same thing on every branch
29
+ and travels through a merge in either direction unchanged.
30
+
31
+ **Being wrong safely.** A branch that names no line takes the patch, which
32
+ understates: a snapshot that understates sorts below the release it precedes
33
+ and can never shadow it. Overstating is the failure this exists to prevent — a
34
+ ``0.5.0.devN`` built off ``maintain/0.4`` sorts *above* the ``0.4.1`` the line
35
+ exists to produce, so a bench given one is never upgraded by it.
36
+
37
+ Written by ``plesty init`` and ``plesty update --versioning``; versioningit
38
+ imports it at build time through ``[tool.hatch.version.next-version]``.
39
+ """
40
+
41
+ from __future__ import annotations
42
+
43
+ from typing import Any, Optional
44
+
45
+ from versioningit.next_version import (
46
+ next_minor_release_version,
47
+ next_smallest_release_version,
48
+ )
49
+
50
+ #: Branches whose next release is the next MINOR: the integration line, and the
51
+ #: release line that mirrors it.
52
+ MINOR_BRANCHES = frozenset({"exp", "main"})
53
+
54
+
55
+ def next_version(*, version: str, branch: Optional[str], params: dict[str, Any]) -> str:
56
+ """Return the version a snapshot of *branch* is working towards.
57
+
58
+ Args:
59
+ version: The last tag's version.
60
+ branch: The branch being built, or ``None`` on a detached HEAD.
61
+ params: versioningit's method parameters.
62
+
63
+ Returns:
64
+ The next minor on the integration line, else the release the last tag
65
+ precedes — which on a maintenance line is the next patch. A detached
66
+ HEAD, which is how CI checks out, takes the same safe answer as an
67
+ unnamed branch. A build *at* a tag never reaches here, having no
68
+ distance to name.
69
+ """
70
+ if branch in MINOR_BRANCHES:
71
+ return next_minor_release_version(version=version, branch=branch, params=params)
72
+ return next_smallest_release_version(version=version, branch=branch, params=params)
@@ -126,8 +126,11 @@ function LastLines($count) {
126
126
  return $lines[($lines.Count - $count)..($lines.Count - 1)]
127
127
  }
128
128
 
129
- # The newest interpreter uv has unpacked that is NOT a junction, preferring
130
- # $PythonSeries. A process descended from the wizard cannot traverse a
129
+ # The newest $PythonSeries interpreter uv has unpacked that is NOT a junction,
130
+ # or "" when there is none -- and then the caller fetches one. Never another
131
+ # series: a bench whose only uv Python was 3.10 got its environment built on
132
+ # 3.10, where no plesty-server release installs (Requires-Python >=3.12), and
133
+ # the wizard blamed the build. A process descended from the wizard cannot traverse a
131
134
  # junction at all -- every path through one answers "os error 448, untrusted
132
135
  # mount point", while the same junction is fine from a shell -- and uv keeps a
133
136
  # minor-version junction beside each real directory, which both its own
@@ -151,30 +154,53 @@ function Find-RealInterpreter {
151
154
  if ($_.Name -match "^cpython-(\d+\.\d+\.\d+)-") { [version]$Matches[1] }
152
155
  else { [version]"0.0.0" }
153
156
  } -Descending)
154
- if ($real.Count -eq 0) { return "" }
155
157
  $pinned = @($real | Where-Object { $_.Name -like "cpython-$PythonSeries.*" })
156
- if ($pinned.Count -gt 0) { return (Join-Path $pinned[0].FullName "python.exe") }
157
- return (Join-Path $real[0].FullName "python.exe")
158
+ if ($pinned.Count -eq 0) { return "" }
159
+ return (Join-Path $pinned[0].FullName "python.exe")
158
160
  }
159
161
 
160
162
  # A virtual environment of the bench's own, built by the interpreter itself so
161
- # that nothing uv writes launchers into it. Reused when it still runs: a
162
- # rebuild costs the whole Qt download again, and removing the directory fails
163
- # outright while the console is open.
163
+ # that nothing uv writes launchers into it. Reused when it still runs on
164
+ # $PythonSeries: a rebuild costs the whole Qt download again, and removing the
165
+ # directory fails outright while the console is open. One built on another
166
+ # series is rebuilt -- otherwise a bench an earlier installer left on the wrong
167
+ # Python would fail the same way on every run.
168
+ #
169
+ # It must also have pip, which is the last thing `python -m venv` puts in. A
170
+ # run that stopped part-way -- the old console still open, its pythonw.exe
171
+ # locked, so the old environment could not be removed and venv failed on it --
172
+ # left one on 3.12 with no pip, and the next run reused it and failed with
173
+ # "No module named pip". A removal that does not happen now stops the install
174
+ # and says why, rather than letting venv fail on what is left.
164
175
  function New-AppEnv($interpreter, $target) {
165
176
  $python = Join-Path $target "Scripts\python.exe"
166
177
  if (Test-Path $python) {
167
- if ((Run $python "-V") -eq 0) {
178
+ $runs = (Run $python "-V") -eq 0
179
+ $onSeries = $runs -and $script:LastOutput -match "Python $([regex]::Escape($PythonSeries))\."
180
+ if ($onSeries -and (Run $python "-m pip --version") -eq 0) {
168
181
  Say "reusing the environment at $target"
169
182
  return $python
170
183
  }
171
- Say "the environment at $target no longer runs -- rebuilding it"
184
+ if (-not $runs) {
185
+ Say "the environment at $target no longer runs -- rebuilding it"
186
+ } elseif (-not $onSeries) {
187
+ Say "the environment at $target is not on Python $PythonSeries -- rebuilding it"
188
+ } else {
189
+ Say "the environment at $target has no pip (an earlier install stopped part-way) -- rebuilding it"
190
+ }
172
191
  Remove-Item -Recurse -Force -ErrorAction SilentlyContinue $target
192
+ if (Test-Path $target) {
193
+ throw ("could not remove the old environment at $target -- PLESTY Bench is " +
194
+ "probably still running. Close it, then run this installer again.")
195
+ }
173
196
  }
174
197
  Say "creating the environment at $target"
175
198
  $rc = Run $interpreter "-m venv `"$target`""
176
199
  if ($rc -ne 0) { throw "could not create the environment at $target (exit $rc)" }
177
200
  if (-not (Test-Path $python)) { throw "expected $python after creating the environment" }
201
+ if ((Run $python "-m pip --version") -ne 0) {
202
+ throw "the environment at $target was created without pip; run this installer again"
203
+ }
178
204
  return $python
179
205
  }
180
206
 
@@ -233,6 +259,11 @@ function Diagnose($rc) {
233
259
  return "The application's metadata names a dependency by URL, which " +
234
260
  "the installer cannot resolve. This build cannot be installed; it has to be rebuilt."
235
261
  }
262
+ if ($script:LastOutput -match "require a different python version") {
263
+ return "The application does not install on the Python the environment was built " +
264
+ "on (see the log). Removing $EnvDir and running the installer again " +
265
+ "rebuilds it on Python $PythonSeries."
266
+ }
236
267
  if ($script:LastOutput -match ("No solution found|Failed to resolve dependencies|" +
237
268
  "ResolutionImpossible|No matching distribution found|" +
238
269
  "Could not find a version that satisfies")) {
@@ -308,14 +339,12 @@ try {
308
339
  Say "using the interpreter at $interpreter"
309
340
  $python = New-AppEnv $interpreter $EnvDir
310
341
 
311
- # No --prerelease flag, and none is needed -- but not because everything
312
- # resolves stable. The application asks for `plesty-lib>=0.5.0.dev6` and
313
- # PyPI carries no stable 0.5.0 at all, so that requirement can only be met
314
- # by a prerelease. It resolves because this installs with pip, below, and
315
- # pip enables prereleases for a requirement whose own specifier names one
316
- # -- which is exactly what `uv tool install` refused to do transitively,
317
- # and why the flag used to be here. Revisit when the bound moves to a
318
- # released 0.5.0 and the question goes away.
342
+ # No --prerelease flag: the application asks for `plesty-lib>=0.5.0`, a
343
+ # released version, so everything resolves stable. Should a bound ever
344
+ # name a prerelease again, this still installs with pip, below, which
345
+ # enables prereleases for a requirement whose own specifier names one --
346
+ # what `uv tool install` refused to do transitively, and why the flag
347
+ # used to be here.
319
348
  $spec = "plesty-server[gui]==$Version"
320
349
  $links = if ($WheelDir) { "--find-links `"$WheelDir`" " } else { "" }
321
350
  $from = if ($WheelDir) { "the wheels this installer carries" } else { "PyPI" }
@@ -237,20 +237,31 @@ begin
237
237
  'the cause above is addressed.',
238
238
  mbError, MB_OK);
239
239
  end;
240
- { Only a successful install gets a Next. The wizard reached this page with its
241
- files already copied and its uninstall entry already written -- Inno does
242
- both before a custom page runs -- so letting Next through would end the
243
- wizard on a Finish page for an application that is not there, which is how a
244
- bench came to have a Start Menu shortcut that launched nothing. Cancel is the
245
- way out of a failure, and the message above says what it leaves behind. }
246
- WizardForm.NextButton.Enabled := InstallSucceeded;
240
+ { Next is the way out, failed or not. Cancel cannot be: this page comes after
241
+ the files are copied, and Inno hides Cancel on every page past that point,
242
+ so a failed install used to leave a greyed Next and no button at all. After
243
+ a failure the Finish page says so instead of congratulating -- see
244
+ CurPageChanged -- and it offers no Launch, whose Check is InstallOk. }
245
+ WizardForm.NextButton.Enabled := True;
247
246
  WizardForm.CancelButton.Enabled := True;
247
+ if not InstallSucceeded then
248
+ LogStatus.Caption := LogStatus.Caption + ' Click Next to close.';
248
249
  end;
249
250
 
250
251
  procedure CurPageChanged(CurPageID: Integer);
251
252
  begin
252
253
  if CurPageID = LogPage.ID then
253
- RunInstallOnLogPage();
254
+ RunInstallOnLogPage()
255
+ else if (CurPageID = wpFinished) and (not InstallSucceeded) then
256
+ begin
257
+ WizardForm.FinishedHeadingLabel.Caption := '{#Label} was not installed';
258
+ WizardForm.FinishedLabel.Caption :=
259
+ 'The application could not be installed from {#Origin}. The log is at' + #13#10 +
260
+ LogFilePath() + '.' + #13#10 + #13#10 +
261
+ 'Its files and the entry in Add/Remove Programs are in place, but nothing' + #13#10 +
262
+ 'there runs until an install succeeds: run this installer again once the' + #13#10 +
263
+ 'cause is addressed, or remove it from Add/Remove Programs.';
264
+ end;
254
265
  end;
255
266
 
256
267
  { ---------------------------------------------------------------------------
@@ -34,6 +34,7 @@ from pathlib import Path
34
34
  import click
35
35
 
36
36
  from plesty.bench.client import ADDRESS_ENV, TOKEN_ENV, BenchClient, BenchClientError
37
+ from plesty.bench.streams import printable_output
37
38
 
38
39
  #: Remote commands that start a job; the client adds ``--no-wait`` and follows.
39
40
  JOB_COMMANDS = ("install", "update", "field-test")
@@ -71,14 +72,18 @@ def app(address: str | None, token: str | None, timeout: float, argv: tuple[str,
71
72
  def run_remote(client: BenchClient, args: Sequence[str]) -> int:
72
73
  """Run *args* on the bench; follow the job when it starts one. Returns the exit code."""
73
74
  argv = list(args)
74
- follow = argv[0] in JOB_COMMANDS and "--no-wait" not in argv
75
+ asks_help = "--help" in argv or "-h" in argv
76
+ follow = argv[0] in JOB_COMMANDS and "--no-wait" not in argv and not asks_help
75
77
  if follow:
76
78
  argv.append("--no-wait")
77
79
  result = client.exec(argv)
78
80
  if result.stderr:
79
81
  click.echo(result.stderr, err=True, nl=False)
80
82
  lines = result.stdout.strip().splitlines()
81
- if not follow or not result.ok or not lines:
83
+ # A started job prints its id, one word, last. Anything else — help text,
84
+ # a message — is printed as it came: following a line of help as a job id
85
+ # was answered "unknown job ' --help …'" (#19).
86
+ if not follow or not result.ok or not lines or len(lines[-1].split()) != 1:
82
87
  click.echo(result.stdout, nl=False)
83
88
  return result.code
84
89
  job_id = lines[-1]
@@ -145,6 +150,7 @@ def _control(client: BenchClient, args: Sequence[str]) -> None:
145
150
 
146
151
  def main() -> None:
147
152
  """Console-script entry point."""
153
+ printable_output()
148
154
  app(prog_name="plesty-bench")
149
155
 
150
156
 
@@ -249,7 +249,18 @@ class BenchClient:
249
249
  raise BenchClientError(
250
250
  result.stderr.strip() or result.stdout.strip() or "jobs log failed"
251
251
  )
252
- chunk = result.json()
252
+ try:
253
+ chunk = result.json()
254
+ except ValueError as exc:
255
+ # Said plainly: a traceback here read as a failed install, and
256
+ # an operator who retried it ran the install twice (#19).
257
+ raise BenchClientError(
258
+ f"{job_id}: the bench's log reply was not readable "
259
+ f"({result.stdout.strip()[:120]!r}); the job itself is still on "
260
+ f"the bench — see `jobs log {job_id}` before starting it again"
261
+ ) from exc
262
+ if not isinstance(chunk, dict):
263
+ raise BenchClientError(f"{job_id}: unexpected log reply {chunk!r}")
253
264
  text = str(chunk.get("text", ""))
254
265
  if text:
255
266
  sink(text)