StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHandling chunked request in Sinatra
primarykey
Id
14207553
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
7
CommunityOwnedDate
CreationDate
2013-01-08T02:57:05.737
FavoriteCount
0
LastActivityDate
2013-01-08T20:10:58.170
LastEditDate
LastEditorUserId
0
OwnerUserId
1443338
ParentId
0
PostTypeId
1
Score
1
ViewCount
332
LastEditorDisplayName
text
Body
In Sinatra I have a route setup similar to the following: <pre><code>put '/test' do begin logger.info 'In put begin block' write_to_file(request.body.read) [200, ''] rescue RuntimeError => e [500, 'some error'] end end def write_to_file(data) logger.info "writing data with size #{data.size}" # Code to save file... end </code></pre> When I send data that is < ~500 MBytes it everything seems to work correctly but when I attempt to send data that is >= 500 MBytes I get some weird log output and then the client eventually errors out with the following error: Excon::Errors::SocketError: EOFError (EOFError) The logs from the server (Sinatra) look like the following: For data < 500 MBytes: <pre><code>I, [2013-01-07T21:33:59.386768 #17380] INFO -- : In put begin block I, [2013-01-07T21:34:01.279922 #17380] INFO -- : writing data with size 209715200 xxx.xxx.xxx.xxx - - [07/Jan/2013 21:34:22] "PUT /test " 200 - 22.7917 </code></pre> For data > 500 MBytes: <pre><code>I, [2013-01-07T21:47:37.434022 #17386] INFO -- : In put begin block I, [2013-01-07T21:47:41.152932 #17386] INFO -- : writing data with size 524288000 I, [2013-01-07T21:48:16.093683 #17380] INFO -- : In put begin block I, [2013-01-07T21:48:20.300391 #17380] INFO -- : writing data with size 524288000 xxx.xxx.xxx.xxx - - [07/Jan/2013 21:48:39] "PUT /test " 200 - 62.4515 I, [2013-01-07T21:48:54.718971 #17386] INFO -- : In put begin block I, [2013-01-07T21:49:00.381725 #17386] INFO -- : writing data with size 524288000 I, [2013-01-07T21:49:33.980043 #17267] INFO -- : In put begin block I, [2013-01-07T21:49:41.990671 #17267] INFO -- : writing data with size 524288000 xxx.xxx.xxx.xxx - - [07/Jan/2013 21:50:06] "PUT /test " 200 - 110.2076 xxx.xxx.xxx.xxx - - [07/Jan/2013 21:51:22] "PUT /test " 200 - 108.5339 </code></pre> Not entirely sure whats going on here so I guess my question is two fold, A. What is fundamentally different between these two cases that would cause them to behave this way? B. Is there a better way to handle data to mitigate against this?
Tags
<ruby><http><nginx><sinatra><passenger>
Title
Handling chunked request in Sinatra
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USajorgensen
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POHandling chunked request in Sinatra
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.