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

Hide class loading warnings during batch execution #3513

Open
anitvam opened this issue Jun 6, 2024 · 1 comment
Open

Hide class loading warnings during batch execution #3513

anitvam opened this issue Jun 6, 2024 · 1 comment

Comments

@anitvam
Copy link
Contributor

anitvam commented Jun 6, 2024

When alchemist search for suitable constructors given the provided arguments, it gives back an error each time a constructor does not fit. For example:

10:09:52.342 [main] WARN it.unibo.alchemist.boundary.loader.util.JVMConstructor --   - InstancingImpossibleException: Could not create an instance with public it.unibo.alchemist.boundary.launchers.DefaultLauncher(java.util.List,boolean,boolean,int,int,kotlin.jvm.internal.DefaultConstructorMarker): discarded because incompatible with provided parameters [ArrayList, Boolean, Boolean, Integer]
[...]
10:10:02.110 [Alchemist Pool 0 worker 3] WARN it.unibo.alchemist.boundary.loader.util.JVMConstructor --   - InstancingImpossibleException: Could not create an instance with public it.unibo.alchemist.model.timedistributions.ExponentialTime(double,it.unibo.alchemist.model.Time,org.apache.commons.math3.random.RandomGenerator): discarded because incompatible with provided parameters [Double]

It is possible to hide them if it is not a blocking error?

@DanySK
Copy link
Member

DanySK commented Jun 6, 2024

There should be a --verbosity error level, the default is warning. I would still hide them by default, they are de-facto info loggings. In general the explainability of the loading process should be improved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants