Stream: git-wasmtime

Topic: wasmtime / issue #5902 Include git submodule source in re...

view this post on Zulip Wasmtime GitHub notifications bot (Mar 01 2023 at 15:51):

kriswuollett opened issue #5902:

Feature

Include submodules source in release source artifacts.

Benefit

Can compile wasmtime from release source artifact, otherwise one currently encounters this issue:

$ cargo build --release --manifest-path crates/c-api/Cargo.toml
error: failed to load manifest for workspace member `/home/kris/code/wasmtime-6.0.0/crates/bench-api`

Caused by:
  failed to load manifest for dependency `wasi-cap-std-sync`

Caused by:
  failed to load manifest for dependency `wasi-common`

Caused by:
  failed to load manifest for dependency `wasmtime`

Caused by:
  failed to load manifest for dependency `wasmtime-wasi`

Caused by:
  failed to load manifest for dependency `wasi-tokio`

Caused by:
  failed to load manifest for dependency `wiggle`

Caused by:
  failed to load manifest for dependency `wiggle-macro`

Caused by:
  failed to load manifest for dependency `wiggle-generate`

Caused by:
  failed to load manifest for dependency `witx`

Caused by:
  failed to read `/home/kris/code/wasmtime-6.0.0/crates/wasi-common/WASI/tools/witx/Cargo.toml`

Caused by:
  No such file or directory (os error 2)

My use case is to use http_archive instead of git_repository in a Bazel workspace for faster build initialization, e.g.,:

_ALL_CONTENT = """\
filegroup(
    name = "all_srcs",
    srcs = glob(["**"]),
    visibility = ["//visibility:public"],
)

http_archive(
    name = "wasmtime",
    build_file_content = _ALL_CONTENT,
    strip_prefix = "wasmtime-6.0.0",
    urls = [
        "https://github.com/bytecodealliance/wasmtime/archive/refs/tags/v6.0.0.tar.gz",
    ],
    sha256 = "02af6132501ec5aff6993925a23efda0cbaab16e509787d3649cfc1bf8a33978",
)

Implementation

It is possible to reuse a script created for another project with the same issue to include submodules in the release source archive, see https://github.com/AcademySoftwareFoundation/MaterialX/issues/317#issuecomment-560131043.

view this post on Zulip Wasmtime GitHub notifications bot (Mar 01 2023 at 15:55):

kriswuollett edited issue #5902:

Feature

Include submodules source in release source artifacts.

Benefit

Can compile wasmtime from release source artifact, which can be mirrored on an internal archive, otherwise one currently encounters this issue:

$ cargo build --release --manifest-path crates/c-api/Cargo.toml
error: failed to load manifest for workspace member `/home/kris/code/wasmtime-6.0.0/crates/bench-api`

Caused by:
  failed to load manifest for dependency `wasi-cap-std-sync`

Caused by:
  failed to load manifest for dependency `wasi-common`

Caused by:
  failed to load manifest for dependency `wasmtime`

Caused by:
  failed to load manifest for dependency `wasmtime-wasi`

Caused by:
  failed to load manifest for dependency `wasi-tokio`

Caused by:
  failed to load manifest for dependency `wiggle`

Caused by:
  failed to load manifest for dependency `wiggle-macro`

Caused by:
  failed to load manifest for dependency `wiggle-generate`

Caused by:
  failed to load manifest for dependency `witx`

Caused by:
  failed to read `/home/kris/code/wasmtime-6.0.0/crates/wasi-common/WASI/tools/witx/Cargo.toml`

Caused by:
  No such file or directory (os error 2)

My use case is to use http_archive instead of git_repository in a Bazel workspace for faster build initialization, e.g.,:

_ALL_CONTENT = """\
filegroup(
    name = "all_srcs",
    srcs = glob(["**"]),
    visibility = ["//visibility:public"],
)

http_archive(
    name = "wasmtime",
    build_file_content = _ALL_CONTENT,
    strip_prefix = "wasmtime-6.0.0",
    urls = [
        "https://github.com/bytecodealliance/wasmtime/archive/refs/tags/v6.0.0.tar.gz",
    ],
    sha256 = "02af6132501ec5aff6993925a23efda0cbaab16e509787d3649cfc1bf8a33978",
)

Implementation

It is possible to reuse a script created for another project with the same issue to include submodules in the release source archive, see https://github.com/AcademySoftwareFoundation/MaterialX/issues/317#issuecomment-560131043.

view this post on Zulip Wasmtime GitHub notifications bot (Mar 01 2023 at 15:56):

kriswuollett edited issue #5902:

Feature

Include submodules source in release source artifacts.

Benefit

Can compile wasmtime from release source artifact, which can be mirrored on an internal archive, otherwise one currently encounters this issue:

$ cargo build --release --manifest-path crates/c-api/Cargo.toml
error: failed to load manifest for workspace member `/home/kris/code/wasmtime-6.0.0/crates/bench-api`

Caused by:
  failed to load manifest for dependency `wasi-cap-std-sync`

Caused by:
  failed to load manifest for dependency `wasi-common`

Caused by:
  failed to load manifest for dependency `wasmtime`

Caused by:
  failed to load manifest for dependency `wasmtime-wasi`

Caused by:
  failed to load manifest for dependency `wasi-tokio`

Caused by:
  failed to load manifest for dependency `wiggle`

Caused by:
  failed to load manifest for dependency `wiggle-macro`

Caused by:
  failed to load manifest for dependency `wiggle-generate`

Caused by:
  failed to load manifest for dependency `witx`

Caused by:
  failed to read `/home/kris/code/wasmtime-6.0.0/crates/wasi-common/WASI/tools/witx/Cargo.toml`

Caused by:
  No such file or directory (os error 2)

My use case is to use http_archive instead of git_repository in a Bazel workspace for faster build initialization, e.g.,:

_ALL_CONTENT = """\
filegroup(
    name = "all_srcs",
    srcs = glob(["**"]),
    visibility = ["//visibility:public"],
)

http_archive(
    name = "wasmtime",
    build_file_content = _ALL_CONTENT,
    strip_prefix = "wasmtime-6.0.0",
    urls = [
        "https://archive.corp.mycompany.com/bytecodealliance/wasmtime/v6.0.0.tar.gz",
        "https://github.com/bytecodealliance/wasmtime/archive/refs/tags/v6.0.0.tar.gz",
    ],
    sha256 = "02af6132501ec5aff6993925a23efda0cbaab16e509787d3649cfc1bf8a33978",
)

Implementation

It is possible to reuse a script created for another project with the same issue to include submodules in the release source archive, see https://github.com/AcademySoftwareFoundation/MaterialX/issues/317#issuecomment-560131043.

view this post on Zulip Wasmtime GitHub notifications bot (Mar 01 2023 at 15:56):

kriswuollett edited issue #5902:

Feature

Include submodules source in release source artifacts.

Benefit

Can compile wasmtime from release source artifact, which can be mirrored on an internal archive, otherwise one currently encounters this issue:

$ cargo build --release --manifest-path crates/c-api/Cargo.toml
error: failed to load manifest for workspace member `/home/kris/code/wasmtime-6.0.0/crates/bench-api`

Caused by:
  failed to load manifest for dependency `wasi-cap-std-sync`

Caused by:
  failed to load manifest for dependency `wasi-common`

Caused by:
  failed to load manifest for dependency `wasmtime`

Caused by:
  failed to load manifest for dependency `wasmtime-wasi`

Caused by:
  failed to load manifest for dependency `wasi-tokio`

Caused by:
  failed to load manifest for dependency `wiggle`

Caused by:
  failed to load manifest for dependency `wiggle-macro`

Caused by:
  failed to load manifest for dependency `wiggle-generate`

Caused by:
  failed to load manifest for dependency `witx`

Caused by:
  failed to read `/home/kris/code/wasmtime-6.0.0/crates/wasi-common/WASI/tools/witx/Cargo.toml`

Caused by:
  No such file or directory (os error 2)

My use case is to use http_archive instead of git_repository in a Bazel workspace for faster build initialization, e.g.,:

_ALL_CONTENT = """\
filegroup(
    name = "all_srcs",
    srcs = glob(["**"]),
    visibility = ["//visibility:public"],
)

http_archive(
    name = "wasmtime",
    build_file_content = _ALL_CONTENT,
    strip_prefix = "wasmtime-6.0.0",
    urls = [
        "https://archive.corp.example.com/bytecodealliance/wasmtime/v6.0.0.tar.gz",
        "https://github.com/bytecodealliance/wasmtime/archive/refs/tags/v6.0.0.tar.gz",
    ],
    sha256 = "02af6132501ec5aff6993925a23efda0cbaab16e509787d3649cfc1bf8a33978",
)

Implementation

It is possible to reuse a script created for another project with the same issue to include submodules in the release source archive, see https://github.com/AcademySoftwareFoundation/MaterialX/issues/317#issuecomment-560131043.

view this post on Zulip Wasmtime GitHub notifications bot (Mar 01 2023 at 16:11):

kriswuollett commented on issue #5902:

Current workaround:

git_repository(
    name = "wasmtime",
    build_file_content = _ALL_CONTENT,
    remote = "https://github.com/bytecodealliance/wasmtime.git",
    commit = "c00d3f0542855a13adffffd5f4ff0177dfbdcb34", # v6.0.0
    recursive_init_submodules = True,
)

$ bazel query 'deps(@wasmtime//:all_srcs)' 2>/dev/null | grep 'tools/witx' | head
@wasmtime//:crates/wasi-common/WASI/tools/witx-cli/Cargo.toml
@wasmtime//:crates/wasi-common/WASI/tools/witx-cli/src/main.rs
@wasmtime//:crates/wasi-common/WASI/tools/witx/.gitignore
@wasmtime//:crates/wasi-common/WASI/tools/witx/Cargo.toml
@wasmtime//:crates/wasi-common/WASI/tools/witx/LICENSE
@wasmtime//:crates/wasi-common/WASI/tools/witx/src/abi.rs
@wasmtime//:crates/wasi-common/WASI/tools/witx/src/ast.rs
@wasmtime//:crates/wasi-common/WASI/tools/witx/src/docs/ast.rs
@wasmtime//:crates/wasi-common/WASI/tools/witx/src/docs/md.rs
@wasmtime//:crates/wasi-common/WASI/tools/witx/src/docs/mod.rs

view this post on Zulip Wasmtime GitHub notifications bot (Mar 01 2023 at 16:13):

alexcrichton commented on issue #5902:

Could you try using the dedicated source tarball? We have no control over the github-generated tarballs to include submodules or not.

view this post on Zulip Wasmtime GitHub notifications bot (Mar 02 2023 at 15:21):

kriswuollett commented on issue #5902:

Yes, thanks, that works! I seem to have been in the habit of always skipping down to the src link at the bottom of GitHub releases for a repo.

view this post on Zulip Wasmtime GitHub notifications bot (Mar 02 2023 at 15:21):

kriswuollett closed issue #5902:

Feature

Include submodules source in release source artifacts.

Benefit

Can compile wasmtime from release source artifact, which can be mirrored on an internal archive, otherwise one currently encounters this issue:

$ cargo build --release --manifest-path crates/c-api/Cargo.toml
error: failed to load manifest for workspace member `/home/kris/code/wasmtime-6.0.0/crates/bench-api`

Caused by:
  failed to load manifest for dependency `wasi-cap-std-sync`

Caused by:
  failed to load manifest for dependency `wasi-common`

Caused by:
  failed to load manifest for dependency `wasmtime`

Caused by:
  failed to load manifest for dependency `wasmtime-wasi`

Caused by:
  failed to load manifest for dependency `wasi-tokio`

Caused by:
  failed to load manifest for dependency `wiggle`

Caused by:
  failed to load manifest for dependency `wiggle-macro`

Caused by:
  failed to load manifest for dependency `wiggle-generate`

Caused by:
  failed to load manifest for dependency `witx`

Caused by:
  failed to read `/home/kris/code/wasmtime-6.0.0/crates/wasi-common/WASI/tools/witx/Cargo.toml`

Caused by:
  No such file or directory (os error 2)

My use case is to use http_archive instead of git_repository in a Bazel workspace for faster build initialization, e.g.,:

_ALL_CONTENT = """\
filegroup(
    name = "all_srcs",
    srcs = glob(["**"]),
    visibility = ["//visibility:public"],
)

http_archive(
    name = "wasmtime",
    build_file_content = _ALL_CONTENT,
    strip_prefix = "wasmtime-6.0.0",
    urls = [
        "https://archive.corp.example.com/bytecodealliance/wasmtime/v6.0.0.tar.gz",
        "https://github.com/bytecodealliance/wasmtime/archive/refs/tags/v6.0.0.tar.gz",
    ],
    sha256 = "02af6132501ec5aff6993925a23efda0cbaab16e509787d3649cfc1bf8a33978",
)

Implementation

It is possible to reuse a script created for another project with the same issue to include submodules in the release source archive, see https://github.com/AcademySoftwareFoundation/MaterialX/issues/317#issuecomment-560131043.

Last updated: Dec 23 2024 at 12:05 UTC