You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
//This is only here because of aws broken streaming implementation.
288
+
//Hopefully one day they will be able to give us a working streaming implementation in lambda for everyone
289
+
//If you're lucky you have a working streaming implementation in your aws account and don't need this
290
+
//If not you can set the OPEN_NEXT_FORCE_NON_EMPTY_RESPONSE env variable to true
291
+
//BE CAREFUL: Aws keeps rolling out broken streaming implementations even on accounts that had working ones before
292
+
//This is not dependent on the node runtime used
293
+
//There is another known issue with aws lambda streaming where the request reach the lambda only way after the request has been sent by the client. For this there is absolutely nothing we can do, contact aws support if that's your case
294
+
_flush(callback: TransformCallback): void{
295
+
if(
296
+
this.body.length<1&&
297
+
// We use an env variable here because not all aws account have the same behavior
298
+
// On some aws accounts the response will hang if the body is empty
299
+
// We are modifying the response body here, this is not a good practice
0 commit comments