Christopher Harrison

PR exists (https://github.com/tweag/rules_haskell/pull/1594); needs amendment and re-review

Potentially similar to #1360; if so, see https://github.com/tweag/rules_haskell/issues/1360#issuecomment-912786715 for possible diagnosis

Update: I can still reproduce this with bazel 4.1.0 and `rules_haskell` 0.14. Presumably the expectation is by virtue of [this code](https://github.com/facundominguez/bug-reports/blob/53c6e1d7eae9c0f03a035ee4d628e62d8445a7f0/BUILD.bazel#L16-L18). It would be worth checking whether this just happens...

This feels more like a limitation of Bazel, that can be worked around, rather than a property of `rules_haskell`. @aherrmann suggests some directions for implementation, but I agree with the...

This is a more focused proposal than #1428. If implemented, best to start here before generalising.

n.b., Still reproducible as of a464b7e with Bazel 4.2.1 (not surprising, given the above comment)

Same for me in: * Firefox 123.0.1, on NixOS 23.11, with Bitwarden 2024.3.1 * Firefox 124.0.2, on macOS 11.7.10, with Bitwarden 2024.3.1

FWIW, it doesn't appear to have anything to do with other addons. I tried disabling all those I have, except Bitwarden, and the problem persists.

I had the same problem, but I was able to sort-of solve it by lifting the branch that admits options into its own struct. Something like this: ```rust use clap::{ArgGroup,...

Similar to @dbivolaru, I "solved" this by using: ``` [options.entry_points] console_scripts = my_script = my.module.name.__main__:main ``` i.e., Explicitly addressing the `main` function in my `__main__.py`, whereas it could have simply...