Skip to content
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.

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

Received message larger than max (5406604 vs. 4194304) #1815

Open
JaPyR opened this issue Feb 28, 2022 · 6 comments
Open

Received message larger than max (5406604 vs. 4194304) #1815

JaPyR opened this issue Feb 28, 2022 · 6 comments
Assignees
Labels
bug Something isn't working help wanted Extra attention is needed priority: high
Milestone

Comments

@JaPyR
Copy link

JaPyR commented Feb 28, 2022

Describe the bug
I have a test case where I need to wait for request end before further interacting with page so my code look like:

${promise}    Promise To    Wait For Response    matcher
....
<Some Actions>
....
Wait For    ${promise}

If I understand correctly size of the response (big json, around 5 megabytes and I am not interested in it's content) is the reason why keyword Wait For fails with message "Received message larger than max (5406604 vs. 4194304)".

@aaltat
Copy link
Member

aaltat commented Mar 4, 2022

We use gRPC to communicate between Python and Node lands. Messages have max limit and if that exceeded, keyword will fail. Unfortunately there is not way to increase the max limit of the message.

I guess we could cut the json and make it fit to the maximum message size. But in that case, we would not return valid json and are in dancer to loose something important information.

But I agree that how keyword works now, is not correct either and it should be fixed, in one way or another.

@aaltat aaltat added bug Something isn't working priority: high labels Mar 4, 2022
@aaltat
Copy link
Member

aaltat commented Mar 4, 2022

@allcontributors please add @JaPyR for bugs.

@allcontributors
Copy link
Contributor

@aaltat

@JaPyR already contributed before to bug

@Sathish787
Copy link

Any updates on this guys? Is there any alternative approach for this

@aaltat
Copy link
Member

aaltat commented Aug 26, 2022

Currently there is not, I tried once to solve the problem, but could not get the node side working.

@Snooz82 Snooz82 modified the milestones: v15.3.0, v16.0.0, v16.1.0 Feb 1, 2023
@aaltat aaltat modified the milestones: v16.0.4, v16.1.0 Apr 30, 2023
@aaltat aaltat modified the milestones: v16.1.0, v16.2.0 May 8, 2023
@aaltat aaltat modified the milestones: v16.2.0, v16.3.0 May 26, 2023
@aaltat aaltat modified the milestones: v16.3.0, v16.4.0 Jul 2, 2023
@aaltat aaltat added this to the v18.0.0 milestone Nov 12, 2023
@Snooz82 Snooz82 added the help wanted Extra attention is needed label Nov 15, 2023
@aaltat aaltat removed their assignment Nov 17, 2023
@Snooz82 Snooz82 modified the milestones: v18.0.0, Some Next Issues Nov 18, 2023
@lgaitan
Copy link

lgaitan commented Feb 29, 2024

I'm facing the same issue

@aaltat aaltat modified the milestones: Some Next Issues, v19.0.0 Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed priority: high
Projects
None yet
Development

No branches or pull requests

6 participants