data flow and cmage conf#1112
Draft
dlyr wants to merge 82 commits intoSTORM-IRIT:release-candidatefrom
Draft
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## release-candidate #1112 +/- ##
=====================================================
+ Coverage 41.59% 50.19% +8.60%
=====================================================
Files 387 347 -40
Lines 30074 26625 -3449
=====================================================
+ Hits 12508 13365 +857
+ Misses 17566 13260 -4306
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Ease the use of make_shared.
Maybe too much ? will see when with usage.
Found by set and check...
This fixes dataflow components that are not lib, install path not consistent. Also try to better handle component and "_FOUND".
Hence if the function is not called, no need to find qt packages.
lcov mess up when same name.
Prevent race condition (when same dir is used).
rename parameters, data member, and add using for compound types.
Since Sphinx config failed on my setup.
for more information, see https://pre-commit.ci
Works with clone in workspace, if not, filename resolution is not working on codecov. Hence external and build are outside of workspace, and cache must be copied, because could not cache using ".." in path
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Desription
Check if you branch history is PR compatible
git fetch originif origin is this remotescripts/is-history-pr-compatible.shThese checks are enforced by github workflow actions
Please refer to the corresponding log in case of failure
UPDATE the form below to describe your PR
Please check if the PR fulfills these requirements
Be aware that the PR request cannot be accepted if it doesn't pass the Continuous Integration tests.
What kind of change does this PR introduce?
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: