Skip to content

Conversation

prbzrg
Copy link
Member

@prbzrg prbzrg commented Oct 14, 2025

Checklist

  • Appropriate tests were added
  • Any code changes were done in a way that does not break public API
  • All documentation related to code changes were updated
  • The new code follows the
    contributor guidelines, in particular the SciML Style Guide and
    COLPRAC.
  • Any new documentation only uses public API

Additional context

Fixes #1059

Comment on lines +137 to +138
@info ProgressLogging.Progress(progress_id, iterations / maxiters;
name = "loss: $(round(first(first(x)); digits=3))")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think @info is needed here, as you can use a log level that does not print, but it's picked up by ProgressLogging integrations, such as the VS Code native progress bar. I think that LogLevel(-1) could be enough.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And then final needs to manual there as well. At least for now I hotfixed a removal of the ProgressLogging setup

module OptimizationOptimisers

using Reexport, Printf, ProgressLogging
using Reexport, ProgressLogging, UUIDs
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We shouldn't depend on ProgressLogging

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

Successfully merging this pull request may close these issues.

[ERROR] @logprogress must be used inside @withprogress or with _id keyword argument

3 participants