Skip to content

Handle empty wakeup responses without false server error#1226

Open
gilderman wants to merge 1 commit into
tonesto7:masterfrom
gilderman:fix/wakeup-empty-response
Open

Handle empty wakeup responses without false server error#1226
gilderman wants to merge 1 commit into
tonesto7:masterfrom
gilderman:fix/wakeup-empty-response

Conversation

@gilderman

Copy link
Copy Markdown

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Description of Changes

Reason for Change

How Has This Been Tested?

Screenshots (if appropriate):

@mrbrito mrbrito left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This definitely helps get rid of the errors. I still get a warning, but it cleans up the errors. My log now looks like this:
2026-07-03 12:13:16.851 am warn EchoApp (v4.3.0.1) | wakeupServerResp: 404
without the extra 3 errors

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