Skip to content

Conversation

@slinkydeveloper
Copy link
Contributor

This is meant to propagate some configuration errors/warnings, such as when values are clamped or ignored.

@nikrooz can you review the error messages?

…me configuration errors/warnings, such as when values are clamped or ignored.
info.push(
Info::new_with_code(
&restate_errors::RT0021,
format!("The configured inactivity_timeout {} will not be applied because the handler is exposed in Request/Response mode.", FriendlyDuration::new(inactivity_timeout))
Copy link
Contributor Author

Choose a reason for hiding this comment

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

if got_journal_retention_clamped {
info.push(Info::new_with_code(
&restate_errors::RT0022,
"The configured journal_retention is clamped to the maximum cluster limit."
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor

@nikrooz nikrooz left a comment

Choose a reason for hiding this comment

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

thx, lgtm. Maybe "Restate Server" instead of "Cluster" might be more consistent with what we have in docs.

Make sure we return the info in deployment responses too
@slinkydeveloper slinkydeveloper merged commit 5079b7e into restatedev:main Oct 23, 2025
25 checks passed
@slinkydeveloper slinkydeveloper deleted the warning-request-response-inactivity-timeout branch October 23, 2025 12:26
@github-actions github-actions bot locked and limited conversation to collaborators Oct 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants