Skip to content

[bzlmod bug/regression] entry_point no longer working with blzmod  #958

Closed

Description

@xinbinhuang

🐞 bug report

Affected Rule

The issue is caused by the rule:

entry_point when using with blzmod

Is this a regression?

Yes

Description

entry_point rule no longer working when used with blzmod

🔬 Minimal Reproduction

You can find a reproducible example at this repo: https://github.com/xinbinhuang/rules_python_bug

🔥 Exception or Error

~ $ bazel run "//:flake8"    
ERROR: /workspace/BUILD.bazel:3:6: no such package '@[unknown repo 'pip_flake8' requested from @]//': The repository '@[unknown repo 'pip_flake8' requested from @]' could not be resolved: No repository visible as '@pip_flake8' from main repository and referenced by '//:flake8'
ERROR: Analysis of target '//:flake8' failed; build aborted: Analysis failed
INFO: Elapsed time: 4.436s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (1 packages loaded, 0 targets configured)
ERROR: Build failed. Not running target

🌍 Your Environment

Operating System:

  
mac/linux
  

Output of bazel version:

  
6.0.0
  

Rules_python version:

  
0.16.1
  

Anything else relevant?

Activity

  1. changed the title [-][bzlmod] `entry_point` no longer working with blzmod [/-] [+][bzlmod bug/regression] `entry_point` no longer working with blzmod [/+] on Jan 1, 2023
  2. keith commented on Jan 4, 2023

    @keith
    Member

    Same here, our case is even just registering pre-commit as a dep seems to get dropped

  3. keith commented on Jan 18, 2023

    @keith
    Member

    my case was fixed at head with 2c29f40, but based on that commit it's because my case had a - and yours doesn't, so maybe it's different. have you tried with HEAD?

  4. xinbinhuang commented on Jan 18, 2023

    @xinbinhuang
    Author

    my case was fixed at head with 2c29f40, but based on that commit it's because my case had a - and yours doesn't, so maybe it's different. have you tried with HEAD?

    Yeah, I've encountered that with another package and fixed it with the commit. But this's a different issue I think.

  5. added 2 commits that reference this issue on Apr 30, 2023
    21c2f1e
    3eb5b7d
  6. chrislovecnm commented on May 17, 2023

    @chrislovecnm
    Contributor

    @aignas is this fixed?

  7. aignas commented on May 17, 2023

    @aignas
    Collaborator

    Fixed by #1220.

  8. added a commit that references this issue on May 18, 2023
    693a158
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions