maddy

#### Problem `coverage run` does not capture coverage for subprocess calls and Dockerized scripts in `llm_transform.py`. #### Approaches Tested 1. **Manual Coverage Wrapping** - Wrapped subprocess calls with `coverage run...

For dockerized scripts I'm unable to get coverage as the container exits before coverage files are collected and I'm unsure of how to proceed for this. I tried including `STOPSIGNAL...

I will revise my approach with this in mind and make it align better with the dev system.

@gpsaggese I leveraged pytest-cov’s subprocess hook (`coverage.process_startup()`) exactly as in the docs i.e creating a `coverage.pth` to track every process. By installing `coverage` in the Docker image and mounting the...

Yes, this is what we have found so far and is all correct. The built-in 'subprocess' support will work even when we are spawning a second docker container. We just...

1. We can detect docker run by watching tmp.system_cmd.sh so whenever a docker run is invoked we can use that. 2. The base image is generated and the dockerfile is...

1. I will start writing the design doc that explains everything we have discussed. 2. For the MVP I just want to clarify some things: Just to clarify: if caller...

@gpsaggese @heanhsok I have made a draft PR with the respective design doc and the MVP where its currently working for docker run commands running in any script and reporting...

@gpsaggese As per our Markdown style guide, any code (such as imports, file paths, function or class names) must be wrapped in backticks (e.g., "`import foo/bar`"). If code isn’t backticked,...

I’ve made a few small improvements to the documentation and drafted a PR. To help everyone get up and running more quickly, I’m thinking of adding a quickstart section to...