Conversation
There was a problem hiding this comment.
I'm Bonk, and I've done a quick review of your PR.
This PR adds a deps_wabt entry to build_deps.jsonc to fix a dependency issue from PR #6154. However, there are several problems that need to be addressed:
-
[HIGH] Missing
BUILD.wabtfile — The entry references"build_file": "//:build/BUILD.wabt"but this file does not exist anywhere in the repository. Runningupdate-deps.pywill fail or produce a broken dependency. -
[HIGH]
deps_wabtis not referenced anywhere — No BUILD.bazel, .bzl, or MODULE.bazel file in the repo referencesdeps_wabtor@deps_wabt. This dependency will be fetched but never used. -
[HIGH]
wasm-toolssource entries still missing frombuild_deps.jsonc— The actual problem from PR #6154 is thatwasm-toolsentries were hand-edited into the generatedgen/build_deps.MODULE.bazelwithout corresponding entries inbuild_deps.jsonc. Thesewasm-toolsentries ARE actively used bytools/BUILD.bazelandbuild/wasm_tools_parse.bzl. Runningupdate-deps.pyafter this PR will remove the wasm-tools entries from the generated file (since they have no source in the jsonc) and break the build. -
[MEDIUM] Generated file not regenerated —
build_deps.MODULE.bazelis not updated in this PR. You'll need to runupdate-deps.pyto regenerate it after fixing the jsonc source entries.
It looks like this PR adds the wrong dependency (wabt instead of wasm-tools) and is missing the BUILD.wabt file it references. The real fix likely needs to add wasm-tools source entries to build_deps.jsonc (one per platform, matching what's currently hand-edited in gen/build_deps.MODULE.bazel), and then regenerate the generated file.
This review was written by an AI assistant and may contain errors. Please verify the findings independently.
| { | ||
| "name": "deps_wabt", | ||
| "type": "github_release", | ||
| "owner": "WebAssembly", | ||
| "repo": "wabt", | ||
| "file_regex": "wabt-.*-ubuntu-20.04\\.tar\\.gz$", | ||
| "build_file": "//:build/BUILD.wabt", | ||
| "freeze_version": "1.0.37" // 1.0.38 doesn't have ubuntu tar.gz, 1.0.39 has a Linux binary but requires glibc 2.38 (will need to update to Trixie for that) |
There was a problem hiding this comment.
Several issues with this entry:
-
build_filereferences a non-existent file://:build/BUILD.wabtdoes not exist in the repo. This was not added in this PR or in PR Signal handling for non-Python WASM modules #6154. -
deps_wabtis unused: No BUILD file or .bzl rule in the repo references@deps_wabt. The dependency that IS actively used iswasm-tools(referenced bytools/BUILD.bazelandbuild/wasm_tools_parse.bzl). -
The
wasm-toolsentries ingen/build_deps.MODULE.bazelare still orphaned: They were hand-edited into the generated file by PR Signal handling for non-Python WASM modules #6154 without corresponding source entries here. Runningupdate-deps.pyafter this PR will delete them and break the build.
I believe the fix should instead add source entries for wasm-tools (one per platform: wasm_tools_linux_x64, wasm_tools_linux_arm64, wasm_tools_macos_x64, wasm_tools_macos_arm64, wasm_tools_windows_x64) to match what's currently in gen/build_deps.MODULE.bazel, and then regenerate the generated file. If wabt is also needed, you'll need to create the BUILD.wabt file and add a reference to @deps_wabt in the appropriate BUILD file.
|
I'm Bonk, and I've done a quick review of your PR. This PR adds a
The review has been posted to the PR. |
Merging this PR will improve performance by 12.81%
Performance Changes
Comparing Footnotes
|
|
Misunderstood what the actual issue was |
My last PR messed up the WABT dependency and added a dependency to wasm-tools incorrectly. This reverts that mistake