Closed
Conversation
- add Bark delivery + notification channel with retry and timeout handling - wire Bark settings into hub configuration and startup logs - add unit tests for Bark delivery/channel and channel-failure isolation in notification hub
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
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.
Summary
Detailed Operations
BARK_DEVICE_KEY,BARK_SERVER_URL) and propagated them throughConfiguration.BarkDeliveryfor HTTP POST/pushwith timeout and retry behavior.BarkNotificationChannel+ factory, including session URL building frompublicUrl.NotificationHub.Verification
bunis not installed (/usr/bin/bash: bun: command not found).Notes
feat-bark-notifications1e1d681