Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rules_nodejs and rules_docker conflict #2265

Open
rengui-hs opened this issue Aug 4, 2023 · 1 comment
Open

rules_nodejs and rules_docker conflict #2265

rengui-hs opened this issue Aug 4, 2023 · 1 comment
Labels
Can Close? Will close in 30 days unless there is a comment indicating why not

Comments

@rengui-hs
Copy link

rengui-hs commented Aug 4, 2023

🐞 bug report

Affected Rule

The issue is caused by the rule:

WORKPSACE.bazel

oad("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

http_archive(
    name = "build_bazel_rules_nodejs",
    # Replace with a real SHA256 checksum
    sha256 = "{SHA256}"
    # Replace with a real release version
    urls = ["https://github.com/bazelbuild/rules_nodejs/releases/download/{VERSION}/rules_nodejs-{VERSION}.tar.gz"],
)


load("@build_bazel_rules_nodejs//:index.bzl", "npm_install")

# Install your declared Node.js dependencies
npm_install(
    name = "npm",
    package_json = "//:package.json",
    yarn_lock = "//:yarn.lock",
)

load(
    "@io_bazel_rules_docker//repositories:repositories.bzl",
    container_repositories = "repositories",
)

container_repositories()

load(
    "@io_bazel_rules_docker//nodejs:image.bzl",
    _nodejs_image_repos = "repositories",
)

_nodejs_image_repos()

Is this a regression?

Yes, the previous version in which this bug was not present was: ....

Description

🔬 Minimal Reproduction

bazel clean --expunge && bazel sync

🔥 Exception or Error

renguizhou@renguidembp backend % bazel clean --expunge && bazel sync
Starting local Bazel server and connecting to it...
INFO: Starting clean (this may take a while). Consider using --async if the clean takes more than several minutes.
Starting local Bazel server and connecting to it...
ERROR: ErrorInfo{exception=null, cycles=[[] -> [[/Users/renguizhou/Desktop/haystack/zaplink/backend]/[WORKSPACE.bazel], 2, KeyForWorkspace{label=@build_bazel_rules_nodejs//:index.bzl, isBuildPrelude=false}, KeyForWorkspace{label=@build_bazel_rules_nodejs//internal/pkg_web:pkg_web.bzl, isBuildPrelude=false}, KeyForWorkspace{label=@rules_nodejs//nodejs:providers.bzl, isBuildPrelude=false}, CONTAINING_PACKAGE_LOOKUP:@rules_nodejs//nodejs, PACKAGE_LOOKUP:@rules_nodejs//nodejs, REPOSITORY_DIRECTORY:@rules_nodejs]], isCatastrophic=false, isDirectlyTransient=false, isTransitivelyTransient=false}
 checking cached actions





🌍 Your Environment

Operating System:

  
 ProductName:		macOS
ProductVersion:		13.4.1
ProductVersionExtra:	(c)
BuildVersion:		22F770820d
  

Output of bazel version:

  
Build label: 6.3.1-homebrew
Build target: bazel-out/darwin_arm64-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Tue Jan 1 00:00:00 1980 (315532800)
Build timestamp: 315532800
Build timestamp as int: 315532800
  

Rules_docker version:

  
v0.25.0
  

Anything else relevant?

@rengui-hs rengui-hs reopened this Aug 4, 2023
Copy link

This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days.
Collaborators can add an assignee to keep this open indefinitely. Thanks for your contributions to rules_docker!

@github-actions github-actions bot added the Can Close? Will close in 30 days unless there is a comment indicating why not label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Can Close? Will close in 30 days unless there is a comment indicating why not
Projects
None yet
Development

No branches or pull requests

1 participant