Skip to content

Conversation

@ranocha
Copy link
Member

@ranocha ranocha commented Feb 4, 2025

We need this to get the latest bugfix SciML/RecursiveArrayTools.jl#420 - thanks, @jlchan!

@github-actions
Copy link
Contributor

github-actions bot commented Feb 4, 2025

Review checklist

This checklist is meant to assist creators of PRs (to let them know what reviewers will typically look for) and reviewers (to guide them in a structured review process). Items do not need to be checked explicitly for a PR to be eligible for merging.

Purpose and scope

  • The PR has a single goal that is clear from the PR title and/or description.
  • All code changes represent a single set of modifications that logically belong together.
  • No more than 500 lines of code are changed or there is no obvious way to split the PR into multiple PRs.

Code quality

  • The code can be understood easily.
  • Newly introduced names for variables etc. are self-descriptive and consistent with existing naming conventions.
  • There are no redundancies that can be removed by simple modularization/refactoring.
  • There are no leftover debug statements or commented code sections.
  • The code adheres to our conventions and style guide, and to the Julia guidelines.

Documentation

  • New functions and types are documented with a docstring or top-level comment.
  • Relevant publications are referenced in docstrings (see example for formatting).
  • Inline comments are used to document longer or unusual code sections.
  • Comments describe intent ("why?") and not just functionality ("what?").
  • If the PR introduces a significant change or new feature, it is documented in NEWS.md with its PR number.

Testing

  • The PR passes all tests.
  • New or modified lines of code are covered by tests.
  • New or modified tests run in less then 10 seconds.

Performance

  • There are no type instabilities or memory allocations in performance-critical parts.
  • If the PR intent is to improve performance, before/after time measurements are posted in the PR.

Verification

  • The correctness of the code was verified using appropriate tests.
  • If new equations/methods are added, a convergence test has been run and the results
    are posted in the PR.

Created with ❤️ by the Trixi.jl community.

@ranocha ranocha closed this Feb 4, 2025
@ranocha ranocha reopened this Feb 4, 2025
@ranocha ranocha requested a review from JoshuaLampert February 4, 2025 15:44
@jlchan
Copy link
Contributor

jlchan commented Feb 4, 2025

We need this to get the latest bugfix SciML/RecursiveArrayTools.jl#420 - thanks, @jlchan!

You bet! Thanks for making this PR.

@codecov
Copy link

codecov bot commented Feb 4, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.42%. Comparing base (24107f4) to head (5feb77f).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2260   +/-   ##
=======================================
  Coverage   96.42%   96.42%           
=======================================
  Files         490      490           
  Lines       39426    39426           
=======================================
  Hits        38015    38015           
  Misses       1411     1411           
Flag Coverage Δ
unittests 96.42% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@JoshuaLampert JoshuaLampert merged commit 81d8e47 into main Feb 4, 2025
43 of 76 checks passed
@JoshuaLampert JoshuaLampert deleted the ranocha-patch-2 branch February 4, 2025 17:01
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.

4 participants