Thanks to visit codestin.com
Credit goes to github.com

Skip to content

A couple small changes for subvectors #3896

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

Merged
merged 3 commits into from
Jul 12, 2024

Conversation

lindsayad
Copy link
Member

@lindsayad lindsayad commented Jul 1, 2024

  • Take a unique_ptr by value when restoring instead of an rvalue of the object. I think this makes the get and restore APIs pair better. I know that this is changing a publicly available API but as @roystgnr pointed out in Static condensation #3883 it's only been around for a couple months so I'm 🤞 that he and @jwpeterson will allow it. If not, nbd, I'll go through the deprecation process
  • Make sure when restoring the subvector to communicate ghost data. I ran into the bad effects of not doing this when working on Static condensation #3883

@lindsayad lindsayad marked this pull request as ready for review July 1, 2024 20:27
@lindsayad lindsayad force-pushed the subvector-api-changes branch from 5d9d8d8 to 89d70d3 Compare July 1, 2024 20:32
@moosebuild
Copy link

moosebuild commented Jul 1, 2024

Job Coverage on eaa757f wanted to post the following:

Coverage

Inconsistent report tags were found between the head and base reports.
This can happen when reports are missing from either the head or the base.

Inconsistent tags:
32bit-np2_threads2
Full coverage report

This comment will be updated on new commits.

This ensures the move constructor is invoked and the caller releases
ownership per https://stackoverflow.com/a/71930927
@lindsayad lindsayad requested a review from roystgnr July 11, 2024 00:59
@lindsayad lindsayad self-assigned this Jul 11, 2024
@lindsayad
Copy link
Member Author

If you're ok with the API changes @roystgnr, this would be a PR that I'd like included in a libmesh update since I have multiple in-flight MOOSE PRs waiting on the libmesh update for other reasons that use these APIs

@lindsayad
Copy link
Member Author

So if we were to put an update in without this and then the MOOSE PRs got merged, this could no longer pass CI

@lindsayad
Copy link
Member Author

well ironically this is failing all the MOOSE targets, but for unrelated reasons

@roystgnr
Copy link
Member

If we can get this in ASAP then we should definitely update the current submodule update PR. I'm chomping at the bit to get multiple features into MOOSE, though; if those failures are unrelated then let's merge anyway and if they're related then let me know if there's anything I can do to help fix them.

@moosebuild
Copy link

Job Test MOOSE on eaa757f : invalidated by @lindsayad

@moosebuild
Copy link

Job Test MOOSE mac on eaa757f : invalidated by @lindsayad

@lindsayad
Copy link
Member Author

I'm 99% sure they are unrelated but let's ensure the remaining 1%

@moosebuild
Copy link

Job Test MOOSE ARM mac on eaa757f : invalidated by @lindsayad

@lindsayad lindsayad merged commit 10d830f into libMesh:devel Jul 12, 2024
20 checks passed
@lindsayad lindsayad deleted the subvector-api-changes branch July 12, 2024 06:08
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