Bump max_frame_size (#3050)
We use the WebSocket connection to send binary data (in the form of shapefiles) from the engine to the client. These can very easily get larger than the default 16MB limit on the max_frame_size. I don't understand why it won't stich multiple frames together - but given what I can see when this crashes, the max_message_size isn't the LIMFAC, max_frame_size is. That's an issue for future-us. Signed-off-by: Paul Tagliamonte <paul@zoo.dev>
This commit is contained in:
		@ -137,7 +137,7 @@ After it runs you should just need the push the branch and open a PR.
 | 
			
		||||
 | 
			
		||||
The PR may then serve as a place to discuss the human-readable changelog and extra QA. The `make-release.sh` tool suggests a changelog for you too to be used as PR description, just make sure to delete lines that are not user facing.
 | 
			
		||||
 | 
			
		||||
#### 2. Smoke test artifacs from the Cut Release PR
 | 
			
		||||
#### 2. Smoke test artifacts from the Cut Release PR
 | 
			
		||||
 | 
			
		||||
The release builds can be find under the `artifact` zip, at the very bottom of the `ci` action page for each commit on this branch.
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
		Reference in New Issue
	
	Block a user