Skip to content

Conversation

@GwendalRaoul
Copy link
Contributor

No description provided.

* wp_UploadScratchpadResp_size
*/
#define WPC_PROTO_MAX_RESPONSE_SIZE (415 + WPC_PROTO_GENERIC_MESSAGE_OVERHEAD)
#define WPC_PROTO_MAX_RESPONSE_SIZE (450 + WPC_PROTO_GENERIC_MESSAGE_OVERHEAD)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

We should find a way to size it.
I added some bytes to take into account flags support.

Copy link
Contributor

Choose a reason for hiding this comment

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

Might be good to have a comment telling where this number comes from

char * gateway_version,
char * sink_id)
{
_Static_assert(WPC_PROTO_MAX_RESPONSE_SIZE >= (wp_GetConfigsResp_size + WPC_PROTO_GENERIC_MESSAGE_OVERHEAD),
Copy link
Contributor Author

Choose a reason for hiding this comment

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

It is removed on purpose as now wp_GetConfigsResp_size is not available in generated code

It will avoid dynamic size
@GwendalRaoul GwendalRaoul force-pushed the update_proto/support_virtual_node_flag branch from 3a4295a to eb26798 Compare January 19, 2026 17:04
@GwendalRaoul
Copy link
Contributor Author

Initially I forget the options we use to generate "static" c code rather than runtime dynamic code.
So I forced push the branch to remove first attempt

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.

4 participants