-
Notifications
You must be signed in to change notification settings - Fork 3
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
Frank/metadata propagation #164
Merged
Merged
Conversation
This file contains 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
frankosterfeld
had a problem deploying
to
configure coverage
February 23, 2024 21:12
— with
GitHub Actions
Failure
frankosterfeld
had a problem deploying
to
configure coverage
February 23, 2024 21:12
— with
GitHub Actions
Failure
frankosterfeld
force-pushed
the
frank/metadata-propagation
branch
from
February 26, 2024 13:14
73ea6eb
to
750758a
Compare
frankosterfeld
temporarily deployed
to
configure coverage
February 26, 2024 13:14
— with
GitHub Actions
Inactive
frankosterfeld
had a problem deploying
to
configure coverage
February 26, 2024 13:14
— with
GitHub Actions
Failure
frankosterfeld
temporarily deployed
to
configure coverage
February 28, 2024 10:01
— with
GitHub Actions
Inactive
frankosterfeld
had a problem deploying
to
configure coverage
February 28, 2024 10:01
— with
GitHub Actions
Failure
3 tasks
frankosterfeld
force-pushed
the
frank/metadata-propagation
branch
from
February 29, 2024 14:12
112faec
to
1a96703
Compare
frankosterfeld
temporarily deployed
to
configure coverage
February 29, 2024 14:12
— with
GitHub Actions
Inactive
frankosterfeld
had a problem deploying
to
configure coverage
February 29, 2024 14:12
— with
GitHub Actions
Failure
frankosterfeld
temporarily deployed
to
configure coverage
February 29, 2024 14:12
— with
GitHub Actions
Inactive
frankosterfeld
had a problem deploying
to
configure coverage
February 29, 2024 14:12
— with
GitHub Actions
Failure
3 tasks
frankosterfeld
force-pushed
the
frank/metadata-propagation
branch
from
February 29, 2024 14:39
1a96703
to
320f8b0
Compare
frankosterfeld
had a problem deploying
to
configure coverage
February 29, 2024 14:39
— with
GitHub Actions
Failure
frankosterfeld
had a problem deploying
to
configure coverage
February 29, 2024 14:39
— with
GitHub Actions
Failure
frankosterfeld
had a problem deploying
to
configure coverage
February 29, 2024 14:39
— with
GitHub Actions
Failure
frankosterfeld
had a problem deploying
to
configure coverage
February 29, 2024 14:39
— with
GitHub Actions
Failure
frankosterfeld
force-pushed
the
frank/metadata-propagation
branch
from
February 29, 2024 15:02
320f8b0
to
a5fac21
Compare
frankosterfeld
had a problem deploying
to
configure coverage
February 29, 2024 15:02
— with
GitHub Actions
Failure
frankosterfeld
had a problem deploying
to
configure coverage
February 29, 2024 15:02
— with
GitHub Actions
Failure
frankosterfeld
had a problem deploying
to
configure coverage
February 29, 2024 15:02
— with
GitHub Actions
Failure
frankosterfeld
had a problem deploying
to
configure coverage
February 29, 2024 15:02
— with
GitHub Actions
Failure
frankosterfeld
force-pushed
the
frank/metadata-propagation
branch
from
February 29, 2024 15:38
a5fac21
to
7dee114
Compare
frankosterfeld
had a problem deploying
to
configure coverage
February 29, 2024 15:38
— with
GitHub Actions
Failure
frankosterfeld
had a problem deploying
to
configure coverage
February 29, 2024 15:38
— with
GitHub Actions
Failure
frankosterfeld
had a problem deploying
to
configure coverage
February 29, 2024 15:38
— with
GitHub Actions
Failure
frankosterfeld
had a problem deploying
to
configure coverage
February 29, 2024 15:38
— with
GitHub Actions
Failure
frankosterfeld
force-pushed
the
frank/metadata-propagation
branch
from
February 29, 2024 16:44
7dee114
to
5c80b72
Compare
frankosterfeld
had a problem deploying
to
configure coverage
February 29, 2024 16:44
— with
GitHub Actions
Failure
frankosterfeld
had a problem deploying
to
configure coverage
February 29, 2024 16:44
— with
GitHub Actions
Failure
frankosterfeld
had a problem deploying
to
configure coverage
February 29, 2024 16:44
— with
GitHub Actions
Failure
frankosterfeld
force-pushed
the
frank/metadata-propagation
branch
from
March 5, 2024 12:12
5c80b72
to
b698689
Compare
frankosterfeld
had a problem deploying
to
configure coverage
March 5, 2024 12:12
— with
GitHub Actions
Failure
frankosterfeld
had a problem deploying
to
configure coverage
March 5, 2024 12:12
— with
GitHub Actions
Failure
frankosterfeld
had a problem deploying
to
configure coverage
March 5, 2024 12:12
— with
GitHub Actions
Failure
frankosterfeld
had a problem deploying
to
configure coverage
March 5, 2024 12:12
— with
GitHub Actions
Failure
frankosterfeld
had a problem deploying
to
configure coverage
March 7, 2024 21:01
— with
GitHub Actions
Failure
frankosterfeld
had a problem deploying
to
configure coverage
March 7, 2024 21:01
— with
GitHub Actions
Failure
The automatic forwarding uses the shortKey (e.g. "signal_name") instead of they key ("key::signal_name").
This can now be achieved with gr::testing::Delay.
frankosterfeld
force-pushed
the
frank/metadata-propagation
branch
from
March 7, 2024 21:33
a9a6faa
to
fd8a26b
Compare
frankosterfeld
temporarily deployed
to
configure coverage
March 7, 2024 21:33
— with
GitHub Actions
Inactive
frankosterfeld
had a problem deploying
to
configure coverage
March 7, 2024 21:33
— with
GitHub Actions
Failure
frankosterfeld
temporarily deployed
to
configure coverage
March 7, 2024 21:33
— with
GitHub Actions
Inactive
frankosterfeld
had a problem deploying
to
configure coverage
March 7, 2024 21:33
— with
GitHub Actions
Failure
As the sinks now register themselves only when started, we need an initial delay in processing to get all data in the test listener. Use gr::testing::Delay for that. That also removes the need for the workaround for sinks being mixed up in simultaneously existing gr::Graphs. That's fine now, as long only one graph is executed by a scheduler, at a time. To force-stop the scheduler, use message ports instead of polling isProcessing.
frankosterfeld
force-pushed
the
frank/metadata-propagation
branch
from
March 8, 2024 07:58
fd8a26b
to
fa3cf4e
Compare
frankosterfeld
temporarily deployed
to
configure coverage
March 8, 2024 07:58
— with
GitHub Actions
Inactive
frankosterfeld
temporarily deployed
to
configure coverage
March 8, 2024 07:58
— with
GitHub Actions
Inactive
frankosterfeld
temporarily deployed
to
configure coverage
March 8, 2024 07:58
— with
GitHub Actions
Inactive
frankosterfeld
temporarily deployed
to
configure coverage
March 8, 2024 07:58
— with
GitHub Actions
Inactive
RalphSteinhagen
approved these changes
Mar 8, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adapt to latest graph-prototype:
Expand tests to ensure that metadata configured at the GR sources (in GRC) make it to the data sink and from there to the REST client.