Skip to content

handle Keep-Alive timeout log as DEBUG, not WARNING #463

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.

Sign up for GitHub

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

Merged
kanarus merged 2 commits into from
May 31, 2025
Merged

handle Keep-Alive timeout log as DEBUG, not WARNING #463

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0403534
handle session timeout log as `DEBUG`, not `WARNING`
kanarus May 31, 2025
8ce2222
WebSocket timeout as WARNING, Keep-Alive timeout as DEBUG
kanarus May 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ohkami/src/session/mod.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ impl<C: Connection> Session<C> {

match read_result {
None => {
crate::WARNING!("\
crate::DEBUG!("\
Session timeouted. In Ohkami, Keep-Alive timeout \
is set to 42 seconds by default and is configurable \
by `OHKAMI_KEEPALIVE_TIMEOUT` environment variable.\
Expand Down Expand Up @@ -139,7 +139,7 @@ impl<C: Connection> Session<C> {
tcp_stream
).await;
if aborted {
crate::WARNING!("\
crate::DEBUG!("\
WebSocket session aborted by timeout. In Ohkami, \
WebSocket timeout is set to 3600 seconds (1 hour) \
by default and is configurable by `OHKAMI_WEBSOCKET_TIMEOUT` \
Expand Down