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

Exception upon traverse #430

Closed
jchapuis opened this issue Apr 2, 2024 · 3 comments · Fixed by #441
Closed

Exception upon traverse #430

jchapuis opened this issue Apr 2, 2024 · 3 comments · Fixed by #441
Assignees
Labels
awaiting-upstream Cannot progress until upstream issue is solved blocked Something is blocking this issue form progressing kind/bug Some behavior is incorrect or out of spec P2 Bugs of moderate severity to be assigned to an engineer in the next iteration

Comments

@jchapuis
Copy link

jchapuis commented Apr 2, 2024

When running the example , prior removal of type information in the val uploads = declaration leads to a runtime exception

class scala.collection.immutable.$colon$colon cannot be cast to class scala.collection.View
[error] 	at scala.collection.BuildFrom$$anon$8.newBuilder(BuildFrom.scala:85)
[error] 	at besom.internal.Output$.sequence$$anonfun$1$$anonfun$1(Output.scala:123)
@pawelprazak pawelprazak added kind/bug Some behavior is incorrect or out of spec needs-repro Needs repro steps before it can be triaged or fixed labels Apr 2, 2024
@pawelprazak pawelprazak self-assigned this Apr 2, 2024
@pawelprazak pawelprazak added P2 Bugs of moderate severity to be assigned to an engineer in the next iteration and removed needs-repro Needs repro steps before it can be triaged or fixed labels Apr 2, 2024
@pawelprazak
Copy link
Collaborator

pawelprazak commented Apr 2, 2024

Thank you for finding this, I was able to reproduce on 0.2.2. As you've said, removing the explicit type from val uploads leads to compiler type inference confusion. Notable factor is the toList method is being called on a Java array.
We need to further investigate the root cause.

@lbialy
Copy link
Collaborator

lbialy commented Apr 3, 2024

Wow, this is actually a mind blowing issue in the compiler itself. This is, in my humble opinion, an exports-related bug. I have replicated this on this repro repo:
https://github.com/lbialy/besom-issue-430

@lbialy
Copy link
Collaborator

lbialy commented Apr 3, 2024

Reported to scala/scala3: scala/scala3#20079

@lbialy lbialy added blocked Something is blocking this issue form progressing awaiting-upstream Cannot progress until upstream issue is solved labels Apr 3, 2024
lbialy added a commit that referenced this issue Apr 8, 2024
lbialy added a commit that referenced this issue Apr 8, 2024
* fix traverse problem from #430
* fix component function with proxies, also change component so that Output[A] is no longer a valid return value to ameliorate the dry run plan short-circuiting problem
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-upstream Cannot progress until upstream issue is solved blocked Something is blocking this issue form progressing kind/bug Some behavior is incorrect or out of spec P2 Bugs of moderate severity to be assigned to an engineer in the next iteration
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants