print active channels on redis trigger #2232
Merged
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.
This PR prints active channels once the Redis trigger starts to improve the Ux slightly. In cases where the wasm modules take a while to prepare, it can look like Spin has hanged if there is no feedback to the user until they decide to send the first request and if it does not have any print statements, it will continue looking like that.
(e.g.)
$ spin up Logging component stdio to ".spin/logs/" Preparing Wasm modules is taking a few seconds...
after the pr it looks like
$ spin up Logging component stdio to "examples/redis-rust/.spin/logs/" Active Channels on redis://localhost:6379: messages: echo-message