Take the engine forty three commits forward by tamnd · Pull Request #41 · tamnd/zu-python

tamnd · 2026-08-25T05:29:17Z

The pin had not moved since 230581c and engine main is at 9dcb7b4, which is forty three commits behind. This moves it.

Two of the commits in that range are why this is worth doing rather than tidy. a92d9c1 lays a column of equal length byte rows out end to end and 5aee3d5 builds a string vector straight from the bytes it decoded to, so BYTES is now a type the engine has values for. The tests in this repository that read one were written ahead of the engine and fail against the old pin with nothing may follow RETURN, found string literal. They should pass here.

Nothing in the binding changed. The diff is three revisions in Cargo.toml and the lock lines that follow from them.

Part of DX4 (tamnd/zu#170), whose second box asks for the differential suite green across all five clients, which cannot be read while three of the five are pinned to different engines.

The pin had not moved since 230581c and main is at 9dcb7b4, which is forty three commits and about a month of engine work. Two of them are why this is worth doing rather than tidy: a92d9c1 lays a column of equal length byte rows out end to end and 5aee3d5 builds a string vector straight from the bytes it decoded to, so BYTES is a type the engine has values for and the tests in this repository that read one stop being tests written ahead of the engine. Nothing in the binding changed. The pin is three lines in Cargo.toml and the lock lines that follow from them.

tamnd · 2026-08-25T05:29:17Z

The pin had not moved since 230581c and engine main is at 9dcb7b4, which is forty three commits behind. This moves it.

Two of the commits in that range are why this is worth doing rather than tidy. a92d9c1 lays a column of equal length byte rows out end to end and 5aee3d5 builds a string vector straight from the bytes it decoded to, so BYTES is now a type the engine has values for. The tests in this repository that read one were written ahead of the engine and fail against the old pin with nothing may follow RETURN, found string literal. They should pass here.

Nothing in the binding changed. The diff is three revisions in Cargo.toml and the lock lines that follow from them.

Part of DX4 (tamnd/zu#170), whose second box asks for the differential suite green across all five clients, which cannot be read while three of the five are pinned to different engines.

The pin had not moved since 230581c and main is at 9dcb7b4, which is forty three commits and about a month of engine work. Two of them are why this is worth doing rather than tidy: a92d9c1 lays a column of equal length byte rows out end to end and 5aee3d5 builds a string vector straight from the bytes it decoded to, so BYTES is a type the engine has values for and the tests in this repository that read one stop being tests written ahead of the engine. Nothing in the binding changed. The pin is three lines in Cargo.toml and the lock lines that follow from them.

tamnd · 2026-08-25T05:29:17Z

The pin had not moved since 230581c and engine main is at 9dcb7b4, which is forty three commits behind. This moves it.

Two of the commits in that range are why this is worth doing rather than tidy. a92d9c1 lays a column of equal length byte rows out end to end and 5aee3d5 builds a string vector straight from the bytes it decoded to, so BYTES is now a type the engine has values for. The tests in this repository that read one were written ahead of the engine and fail against the old pin with nothing may follow RETURN, found string literal. They should pass here.

Nothing in the binding changed. The diff is three revisions in Cargo.toml and the lock lines that follow from them.

Part of DX4 (tamnd/zu#170), whose second box asks for the differential suite green across all five clients, which cannot be read while three of the five are pinned to different engines.

The pin had not moved since 230581c and main is at 9dcb7b4, which is forty three commits and about a month of engine work. Two of them are why this is worth doing rather than tidy: a92d9c1 lays a column of equal length byte rows out end to end and 5aee3d5 builds a string vector straight from the bytes it decoded to, so BYTES is a type the engine has values for and the tests in this repository that read one stop being tests written ahead of the engine. Nothing in the binding changed. The pin is three lines in Cargo.toml and the lock lines that follow from them.

tamnd · 2026-08-25T05:29:17Z

The pin had not moved since 230581c and engine main is at 9dcb7b4, which is forty three commits behind. This moves it.

Two of the commits in that range are why this is worth doing rather than tidy. a92d9c1 lays a column of equal length byte rows out end to end and 5aee3d5 builds a string vector straight from the bytes it decoded to, so BYTES is now a type the engine has values for. The tests in this repository that read one were written ahead of the engine and fail against the old pin with nothing may follow RETURN, found string literal. They should pass here.

Nothing in the binding changed. The diff is three revisions in Cargo.toml and the lock lines that follow from them.

Part of DX4 (tamnd/zu#170), whose second box asks for the differential suite green across all five clients, which cannot be read while three of the five are pinned to different engines.

The pin had not moved since 230581c and main is at 9dcb7b4, which is forty three commits and about a month of engine work. Two of them are why this is worth doing rather than tidy: a92d9c1 lays a column of equal length byte rows out end to end and 5aee3d5 builds a string vector straight from the bytes it decoded to, so BYTES is a type the engine has values for and the tests in this repository that read one stop being tests written ahead of the engine. Nothing in the binding changed. The pin is three lines in Cargo.toml and the lock lines that follow from them.

tamnd · 2026-08-25T05:29:17Z

The pin had not moved since 230581c and engine main is at 9dcb7b4, which is forty three commits behind. This moves it.

Two of the commits in that range are why this is worth doing rather than tidy. a92d9c1 lays a column of equal length byte rows out end to end and 5aee3d5 builds a string vector straight from the bytes it decoded to, so BYTES is now a type the engine has values for. The tests in this repository that read one were written ahead of the engine and fail against the old pin with nothing may follow RETURN, found string literal. They should pass here.

Nothing in the binding changed. The diff is three revisions in Cargo.toml and the lock lines that follow from them.

Part of DX4 (tamnd/zu#170), whose second box asks for the differential suite green across all five clients, which cannot be read while three of the five are pinned to different engines.

The pin had not moved since 230581c and main is at 9dcb7b4, which is forty three commits and about a month of engine work. Two of them are why this is worth doing rather than tidy: a92d9c1 lays a column of equal length byte rows out end to end and 5aee3d5 builds a string vector straight from the bytes it decoded to, so BYTES is a type the engine has values for and the tests in this repository that read one stop being tests written ahead of the engine. Nothing in the binding changed. The pin is three lines in Cargo.toml and the lock lines that follow from them.

tamnd · 2026-08-25T05:29:17Z

The pin had not moved since 230581c and engine main is at 9dcb7b4, which is forty three commits behind. This moves it.

Two of the commits in that range are why this is worth doing rather than tidy. a92d9c1 lays a column of equal length byte rows out end to end and 5aee3d5 builds a string vector straight from the bytes it decoded to, so BYTES is now a type the engine has values for. The tests in this repository that read one were written ahead of the engine and fail against the old pin with nothing may follow RETURN, found string literal. They should pass here.

Nothing in the binding changed. The diff is three revisions in Cargo.toml and the lock lines that follow from them.

Part of DX4 (tamnd/zu#170), whose second box asks for the differential suite green across all five clients, which cannot be read while three of the five are pinned to different engines.

The pin had not moved since 230581c and main is at 9dcb7b4, which is forty three commits and about a month of engine work. Two of them are why this is worth doing rather than tidy: a92d9c1 lays a column of equal length byte rows out end to end and 5aee3d5 builds a string vector straight from the bytes it decoded to, so BYTES is a type the engine has values for and the tests in this repository that read one stop being tests written ahead of the engine. Nothing in the binding changed. The pin is three lines in Cargo.toml and the lock lines that follow from them.

tamnd · 2026-08-25T05:29:17Z

The pin had not moved since 230581c and engine main is at 9dcb7b4, which is forty three commits behind. This moves it.

Two of the commits in that range are why this is worth doing rather than tidy. a92d9c1 lays a column of equal length byte rows out end to end and 5aee3d5 builds a string vector straight from the bytes it decoded to, so BYTES is now a type the engine has values for. The tests in this repository that read one were written ahead of the engine and fail against the old pin with nothing may follow RETURN, found string literal. They should pass here.

Nothing in the binding changed. The diff is three revisions in Cargo.toml and the lock lines that follow from them.

Part of DX4 (tamnd/zu#170), whose second box asks for the differential suite green across all five clients, which cannot be read while three of the five are pinned to different engines.

The pin had not moved since 230581c and main is at 9dcb7b4, which is forty three commits and about a month of engine work. Two of them are why this is worth doing rather than tidy: a92d9c1 lays a column of equal length byte rows out end to end and 5aee3d5 builds a string vector straight from the bytes it decoded to, so BYTES is a type the engine has values for and the tests in this repository that read one stop being tests written ahead of the engine. Nothing in the binding changed. The pin is three lines in Cargo.toml and the lock lines that follow from them.

tamnd · 2026-08-25T05:29:17Z

The pin had not moved since 230581c and engine main is at 9dcb7b4, which is forty three commits behind. This moves it.

Two of the commits in that range are why this is worth doing rather than tidy. a92d9c1 lays a column of equal length byte rows out end to end and 5aee3d5 builds a string vector straight from the bytes it decoded to, so BYTES is now a type the engine has values for. The tests in this repository that read one were written ahead of the engine and fail against the old pin with nothing may follow RETURN, found string literal. They should pass here.

Nothing in the binding changed. The diff is three revisions in Cargo.toml and the lock lines that follow from them.

Part of DX4 (tamnd/zu#170), whose second box asks for the differential suite green across all five clients, which cannot be read while three of the five are pinned to different engines.

The pin had not moved since 230581c and main is at 9dcb7b4, which is forty three commits and about a month of engine work. Two of them are why this is worth doing rather than tidy: a92d9c1 lays a column of equal length byte rows out end to end and 5aee3d5 builds a string vector straight from the bytes it decoded to, so BYTES is a type the engine has values for and the tests in this repository that read one stop being tests written ahead of the engine. Nothing in the binding changed. The pin is three lines in Cargo.toml and the lock lines that follow from them.