-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
Requiring multiple non-interface namespaces from another component throws java.lang.ClassCastException #504
Comments
|
Seems like it may not be reproducible on some systems (see this message in Slack). I've added a nix flake to the repo. This flake creates a devenv shell that reproduces the issue for me. |
Will have a look. |
I can't reproduce the error:
The other two should do |
Maybe you could clone the polylith repo and then point to it in an alias, which is described here. |
I haven't repo'ed the error, just looking at the code
deps on line 52 is a sequence of maps, interface-deps (line 53) is a sequence of whatever :to-brick-id is (presumably not a map), same for base-deps(line 56), but illegal-deps (line 58) remains a sequence of maps. so interface-deps sorts fine, base-deps sorts fine, but illegal-deps throws an error when trying to sort it (when it is non-empty). |
Okay, thanks, now I get it! Will fix! |
Bug fix. Make sure we don't try to sort the vector of illegal dependencies (each dependency is a map). Issue #504
Confirming that 2fca38b fixes the issue in both of my repos. |
Thanks for setting up that extra repo! |
Describe the bug
Requiring multiple non-interface namespaces from another component throws java.lang.ClassCastException.
To Reproduce
This example repository shows a minimal example workspace that reproduces the error with instructions.
Expected behavior
Instead of a stacktrace, I expect
poly
to give me multiple illegal dependency errors or otherwise not throw an error.Additional context
Found while trying to reproduce the error described in this Slack thread. This error does not seem to appear on version 0.2.19.
The text was updated successfully, but these errors were encountered: