Client_payload weight issue
See original GitHub issueHey Lukas, thanks for maintaining this plugin!
I have been making requests to a github repo, and it has been working fine, until I tried exporting tokens from a large file (well, not so large, but lots of typography styles). The token object in the request, even minified, weights 142ko (so not that big…) Still Github throws me a 422 and justifies it by the payload being too large.
Is it possible for you to increase (or specifiy at least) a limit for your payload when the plugin makes the request?
Thanks a lot for your help!
{
"message": "client_payload is too large.",
"documentation_url": "https://docs.github.com/rest/reference/repos#create-a-repository-dispatch-event"
}
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
MSFS SimConnect client not setting payload weight - Reddit
When I start a flight on MSFS in the SimConnect client, it sets the aircraft tail number and fuel weight, but not the...
Read more >Want to Increase Payload Capacity? You Might Be Asking the ...
Curb weight refers to how much the truck itself weighs. ... The problem here is a combination of payload capacity and towing capacity....
Read more >Load Balancing Algorithms, Types and Techniques - Kemp
Weighted round robin is similar to the round-robin load balancing algorithm, adding the ability to spread the incoming client requests across the server...
Read more >Understanding Weight and Balance | Safety First
The next story is based on a real event with a wide body cargo aircraft. ... Among the accidents related to a weight...
Read more >Compilation of Existing State Truck Size and Weight Limit Laws
Federal law prevents States from enforcing vehicle weight limits on Interstate ... The Department of Transportation may issue super-load permits for ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Unfortunately - I’ve got the same error on my side. At some point even the compressed payload became just too bit for GitHub to handle (it’s 69.2 kB with maximum of 50kB for GitHub actions).
As an quick solution I would propose to add the toggle to “send Design Tokens to url” which would remove things like
extensions
field (and maybe others likedescription
as well if they’re not necessarily needed). The toggle could be named like “Include Design Tokens-specific data” and be toggled on by default, so it won’t be a breaking change.For me removal of the
extensions
field alon cut done the compressed JSON filesize by roughly 50%.Would you accept PR for that?
Unfortunately for the dispatches there isn’t any 😄 I was talking about the GitHub’s upload-artifact action repo. For the dispatch I think we can raise the issue only via feedback page.