Skip to content

Conversation

@jClugstor
Copy link
Member

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

Add any other context about the problem here.

@SebastianM-C
Copy link
Member

Would progress information also go through this?

@jClugstor
Copy link
Member Author

It definitely could, yeah.

@jClugstor jClugstor force-pushed the scimllogging branch 2 times, most recently from cf4d2c1 to 45e93b0 Compare January 28, 2026 19:36
@jClugstor jClugstor marked this pull request as ready for review January 29, 2026 18:41
@jClugstor
Copy link
Member Author

@SebastianM-C can you make sure this looks okay? Also, let me know if there are any other log messages you would like to add that I haven't yet. Thanks!

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.

2 participants