When git reports a branch whose name itself contains the substring ... (e.g. feat...v2) with a tracking upstream, the porcelain output looks like ## feat...v2...origin/feat...v2. The line branch, upstream_branch = normalized_branch.split("...") in packages/python-sdk/e2b/sandbox/_git/parse.py splits on every occurrence of ..., producing more than two parts, and the two-variable unpacking immediately raises ValueError: too many values to unpack (expected 2).
Traceback:
File "parse.py", line 135, in parse_git_status
branch, upstream_branch = normalized_branch.split("...")
ValueError: too many values to unpack (expected 2)
To reproduce, run: python3 -c "from e2b.sandbox._git.parse import parse_git_status; parse_git_status('## feat...v2...origin/feat...v2\n')"
When git reports a branch whose name itself contains the substring
...(e.g.feat...v2) with a tracking upstream, the porcelain output looks like## feat...v2...origin/feat...v2. The linebranch, upstream_branch = normalized_branch.split("...")inpackages/python-sdk/e2b/sandbox/_git/parse.pysplits on every occurrence of..., producing more than two parts, and the two-variable unpacking immediately raisesValueError: too many values to unpack (expected 2).Traceback:
To reproduce, run:
python3 -c "from e2b.sandbox._git.parse import parse_git_status; parse_git_status('## feat...v2...origin/feat...v2\n')"