Skip to content

Send ACK even if not all parameters in push request are recognised#79

Open
troelsjessen wants to merge 1 commit into
masterfrom
always_push_ack
Open

Send ACK even if not all parameters in push request are recognised#79
troelsjessen wants to merge 1 commit into
masterfrom
always_push_ack

Conversation

@troelsjessen
Copy link
Copy Markdown
Contributor

When typing switch X in CSH, the client throws a push queue error after the configured timeout and the module is leaving a Param serve push error, result = -1 in stdbuf due to the client also setting parameters boot_img2/3 in case they exist.

Since ack_with_pull was introduced, the user will see the parameters actually set in the ACK, so I see not reason why the server simply shall hold back the ACK in case not all values can be handled.

@troelsjessen troelsjessen requested a review from johandc May 20, 2026 05:35
@johandc
Copy link
Copy Markdown
Contributor

johandc commented May 20, 2026

Why dont we make it an option on the client side, wether they would like full ack of all set params, ack if only a partial was set, or simply just a return of all the set parameters?

@troelsjessen
Copy link
Copy Markdown
Contributor Author

Why dont we make it an option on the client side, wether they would like full ack of all set params, ack if only a partial was set, or simply just a return of all the set parameters?

You want another flag in the push request, selecting whether to send an ACK if only some parameters were recognised? Currently, Recent releases of CSH is always setting ack with pull.

Currently we have the following flags defined
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants