Skip to content

Conversation

peterfpeterson
Copy link
Member

This pulls in a variety of things from main into ornl-next things that might fix starting the workbench

jclarkeSTFC and others added 2 commits April 15, 2025 11:44
…#38600)

* add pystack to workbench and developer environments

* Turn on core dumps on linux for the inner workbench process

Has to switch from multiprocessing to subprocess in order to do this (needed the preexec option).
Through some testing, this should preserve the desired spawn behaviour.
A new module 'workbench_process.py' has been created to use with subprocess.run (can't pass it a function)

* add module to get the compressed output from pystack on the latest worbench core file

* add tests for new run pystack module

* add cpp traces to the report sender

* base64 encode data to store as a string

* show pystack output in the show more details window

* add release note

* update existing tests

* fix pystack test

* add support for lz4 compressed core files, such as those on idaaas

* only import lz4 if on linux

* return Path type as intended

* use process id to identify core dump file

* move release note to 6.13

* pass missing parameter to errorreporter constructor

* only launch with preexec_func when not on windows to avoid crash

* add property to user properties default file

* Update comment in run_pystack

---------

Co-authored-by: thomashampson <thomas.hampson@stfc.ac.uk>
@peterfpeterson peterfpeterson added the ornl-next A copy of a branch into the ornl-next fork label Apr 15, 2025
@peterfpeterson peterfpeterson marked this pull request as ready for review April 15, 2025 16:43
@peterfpeterson peterfpeterson enabled auto-merge (squash) April 15, 2025 16:55
@peterfpeterson peterfpeterson merged commit f2748d4 into mantidproject:ornl-next Apr 15, 2025
8 of 10 checks passed
@peterfpeterson peterfpeterson deleted the ornlnext_packaging branch April 15, 2025 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ornl-next A copy of a branch into the ornl-next fork
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants