Skip to content
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

Do not an error if ingress update failed because the ingress is not found #163

Merged
merged 1 commit into from
Nov 21, 2023

Conversation

biglittlebigben
Copy link
Contributor

No description provided.

@biglittlebigben biglittlebigben merged commit f5a0576 into main Nov 21, 2023
2 checks passed
@biglittlebigben biglittlebigben deleted the benjamin/no_log_ingress_not_found branch November 21, 2023 04:22
biglittlebigben added a commit that referenced this pull request Nov 29, 2023
 ## Changelog

 ### Fixed
- Flush between each frame when copying data on the WHIP relay (#157)
- Fix CanAccept logic (#159)
- Avoid panic when querying the stats monitor before service start (#161)
- Allow reconnections when the output fails (#164)
- Do not an error if ingress update failed because the ingress is not found (#163)
- Make sure that we resize layers to even dimensions (#172)
@biglittlebigben biglittlebigben mentioned this pull request Nov 29, 2023
biglittlebigben added a commit that referenced this pull request Nov 29, 2023
 ## Changelog

  ### Fixed
- Flush between each frame when copying data on the WHIP relay (#157)
- Fix CanAccept logic (#159)
- Avoid panic when querying the stats monitor before service start (#161)
- Allow reconnections when the output fails (#164)
- Do not an error if ingress update failed because the ingress is not found (#163)
- Make sure that we resize layers to even dimensions (#172)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants