Skip to content

QA tests fail due to Unbound Error in VariableResistor #364

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

Closed
matthew-kapp opened this issue Mar 5, 2025 · 2 comments
Closed

QA tests fail due to Unbound Error in VariableResistor #364

matthew-kapp opened this issue Mar 5, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@matthew-kapp
Copy link
Contributor

Describe the bug 🐞

During test of main, one of the tests fail.

Expected behavior

All tests should pass.

Minimal Reproducible Example 👇

Pkg.activate(".")
Pkg.test()

Testing Running tests... Unbound type parameters detected: [1] var"#__VariableResistor__#18"(name, T_dep, enforce_bounds, R_ref::Union{Missing, Nothing, ModelingToolkit.NoValue, var"##608"}, T_ref::Union{Missing, Nothing, ModelingToolkit.NoValue, var"##609"}, R_const::Union{Missing, Nothing, ModelingToolkit.NoValue, var"##610"}, pos::Union{Missing, Nothing, ModelingToolkit.NoValue, Real}, R::Union{Missing, Nothing, ModelingToolkit.NoValue, var"##611"}, alpha::Union{Missing, Nothing, ModelingToolkit.NoValue, var"##612"}, ::typeof(ModelingToolkitStandardLibrary.Electrical.__VariableResistor__)) where {var"##608", var"##609", var"##610", var"##611", var"##612"} @ ModelingToolkitStandardLibrary.Electrical none:0 Aqua: Test Failed at C:\Users\matth\.julia\packages\Aqua\epbUr\src\unbound_args.jl:37

Additional context

Is this a known or unknown issue? If unknown, future PR's can't pass. If known, how to fix it?

@matthew-kapp matthew-kapp added the bug Something isn't working label Mar 5, 2025
@ChrisRackauckas
Copy link
Member

This is known, we should fix it. @ven-k is it the macro that generates code that Aqua doesn't like?

@matthew-kapp
Copy link
Contributor Author

@ChrisRackauckas @ven-k I solved this issue with PR #365 so I guess this issue can be closed now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants