🐛 extract relevant output from hatch env show --json

[valentinoli]

If result.stdout contains something more than the JSON output of all the environments, such as logs from Hatch plugins/hooks, this will result in JSONDecodeError. We must extract the relevant output to prevent such cases.

[Copilot]

Pull Request Overview

This PR fixes a bug where parsing the output of hatch env show --json could fail with a JSONDecodeError when the stdout contains additional content beyond the JSON output, such as logs from Hatch plugins or hooks. The fix extracts only the relevant JSON output by taking the last line of stdout.

• Adds robust JSON output extraction from hatch env show --json command
• Prevents JSONDecodeError when stdout contains plugin/hook logs before the JSON output

Comments suppressed due to low confidence (1)

hatch_pip_compile/cli.py:146

• [nitpick] The variable name 'envs_raw' is somewhat ambiguous. Consider renaming it to 'json_output' or 'last_line_output' to better reflect that it contains the extracted JSON data from the last line.

        envs_raw = result.stdout.strip().rsplit(b"\n", maxsplit=1)[-1]

[juftin]

lol, that was my first time requesting review from co-pilot. It wasn't actually that useful.

Thanks for the contribution, @valentinoli - give me a day or to get a closer look at this but everything looks good on first glance.

[valentinoli]

Perhaps consider parsing hatch.toml/pyproject.toml directly instead

[valentinoli]

@juftin

Consider #96 as an alternative

[valentinoli]

Hey @juftin, have you considered this yet?

I think it is the better alternative compared to #96 although not pretty

Let me know what you think