Skip to content

fix: stop flow manager after calling revoke handlers #598

fix: stop flow manager after calling revoke handlers

fix: stop flow manager after calling revoke handlers #598

Triggered via pull request July 20, 2024 22:53
Status Success
Total duration 4m 22s
Artifacts

test-deploy-website.yml

on: pull_request
Test deployment
4m 14s
Test deployment
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
Test deployment
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-dotnet@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test deployment
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
Test deployment: src/KafkaFlow.Abstractions/Configuration/TopicPartitions.cs#L5
Missing XML comment for publicly visible type or member 'TopicPartitions'
Test deployment: src/KafkaFlow.Abstractions/Configuration/TopicPartitions.cs#L7
Missing XML comment for publicly visible type or member 'TopicPartitions.TopicPartitions(string, IEnumerable<int>)'
Test deployment: src/KafkaFlow.Abstractions/Configuration/TopicPartitions.cs#L13
Missing XML comment for publicly visible type or member 'TopicPartitions.Name'
Test deployment: src/KafkaFlow.Abstractions/Configuration/TopicPartitions.cs#L15
Missing XML comment for publicly visible type or member 'TopicPartitions.Partitions'