Skip to content

Add separate AsyncReceiver type instead of implementing Future directly on the Receiver #67

Add separate AsyncReceiver type instead of implementing Future directly on the Receiver

Add separate AsyncReceiver type instead of implementing Future directly on the Receiver #67

Triggered via pull request February 21, 2025 22:52
Status Success
Total duration 20s
Artifacts

formatting.yml

on: pull_request
check-formatting
12s
check-formatting
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
check-formatting
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
check-formatting
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
check-formatting
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
check-formatting
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/