Andreas Stenius

@ptrhck > I am just wondering what a good debug strategy would be as I would need to rerun the debugger to attach again after every code change. What is...

Got it. +1 for having a production like environment for testing, however depending on the change/build/test cycle time for such a setup, being able to also develop under a less...

Ah, so docker doesn't remove the old container quick enough. Another option, going down this route, could be to write out the container id to a file mounted from the...

> In theory, is it possible to not use pants code reloading but mount the source code to the container and use it that way for within the PEX File?...

Ah, yes. That is interesting. So the image is used more as a side-effect/or means for debugging, rather than build me an image, and then I want to run it....

@thejcannon does any of the above fit with the `--debug-adapter` (or even `--run-adapter`) thingy.. ? (if we'd implement said adapter for such a purpose)

That aligns with my current understanding. My reference to the debug adapter here would be more of an implementation detail (and possibly UX) not functionality. I think we can work...

Oh, just realized this issue is not in the pants repo, so yes a feature request over in pantsbuild/pants would be great, thank you.

I'm stumped that `SCIE=inspect` fails where as `PANTS_BOOTSTRAP_VERSION=reports` doesn't? You could try running with `RUST_LOG=debug` might give some additional clues.

Could be that the later versions of `scie-pants` are unable to run pants 1.x. `scie-pants` are not tested against pants 1.x, and could be broken in that regard. If you...