Files
dev/bazel/rules/testing/foreign_platform_binary.bzl
T
zeekayandHanzo Dev 6cbbea2d03 merge: just-every/code v0.6.169 (e4fe007150) — keep Hanzo identity
Our history is just-every's with author emails rewritten, so the graphs are
disjoint and git finds no merge base. Supplied one by hand: d1f1f51a41, the
just-every commit matching our Oct-2025 fork point (22 files apart). 9618
upstream commits, 7004 files, +1.81M/-159k, 37 conflicts.

Resolution:
- Upstream code where our side was the Oct-2025 prototype of a feature they
  have since reimplemented 3-5x larger (agent_runs, browser_sessions,
  history_cell/{agent,browser}, the vt100 harness and its snapshots).
- Upstream's config.rs module split (builder/defaults/sources/validation)
  kept; zen5-coder and the provider-follows-model rule re-applied on top.
- Ours where the file IS the identity: README, package.json, postinstall,
  release notes pipeline, integration-zed.
- Hybrid where upstream improved a file we had branded: updates.rs (their
  release-repo migration, our hanzoai/dev), release.yml (their fail-fast npm
  auth check, our package name), chatwidget.rs (their turn handling, our
  HANZO_USER_KEY hint), exec human output (their 237 lines, our banner).

Superseded and dropped deliberately: our resume_command_name() coder-alias
hack — upstream's derive_resume_command_name() reads the invocation basename
generically, which yields "dev" for us.

LLM.md now records the real topology and the sync point; AGENTS.md and
CLAUDE.md are symlinks to it again. Single parent on purpose: adopting
jecode/main as a second parent would re-import 13,742 commits carrying the
upstream author emails a prior rewrite deliberately removed.

Version 0.2.188 -> 0.2.189.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-05 23:09:12 -07:00

54 lines
1.9 KiB
Python

"""Makes a binary built for a foreign platform available as test data."""
_EXTRA_RUSTC_FLAGS = "@rules_rust//rust/settings:extra_rustc_flags"
def _foreign_platform_transition_impl(settings, attr):
# A transition cannot rewrite a dependency's rule attributes. Use the
# rules_rust build setting when every Rust target in the foreign
# configuration needs additional compiler or linker flags.
return {
"//command_line_option:platforms": [attr.platform],
_EXTRA_RUSTC_FLAGS: settings[_EXTRA_RUSTC_FLAGS] + attr.extra_rustc_flags,
}
_foreign_platform_transition = transition(
implementation = _foreign_platform_transition_impl,
inputs = [_EXTRA_RUSTC_FLAGS],
outputs = [
"//command_line_option:platforms",
_EXTRA_RUSTC_FLAGS,
],
)
def _foreign_platform_binary_impl(ctx):
if len(ctx.attr.binary) != 1:
fail("expected exactly one transitioned binary")
binary = ctx.attr.binary[0][DefaultInfo]
runfiles = ctx.runfiles(transitive_files = binary.files)
runfiles = runfiles.merge(binary.default_runfiles)
return [
DefaultInfo(
files = binary.files,
runfiles = runfiles,
),
]
foreign_platform_binary = rule(
implementation = _foreign_platform_binary_impl,
attrs = {
"binary": attr.label(
cfg = _foreign_platform_transition,
executable = True,
mandatory = True,
),
"extra_rustc_flags": attr.string_list(
doc = "Additional flags applied to every Rust target in the foreign configuration.",
),
"platform": attr.string(mandatory = True),
"_allowlist_function_transition": attr.label(
default = "@bazel_tools//tools/allowlists/function_transition_allowlist",
),
},
doc = "Builds `binary` for `platform` and exposes its files and runfiles.",
)