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.
309
-
//Hopefully one day they will be able to give us a working streaming implementation in lambda for everyone
310
-
//If you're lucky you have a working streaming implementation in your aws account and don't need this
311
-
//If not you can set the OPEN_NEXT_FORCE_NON_EMPTY_RESPONSE env variable to true
312
-
//BE CAREFUL: Aws keeps rolling out broken streaming implementations even on accounts that had working ones before
313
-
//This is not dependent on the node runtime used
314
-
//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
315
296
_flush(callback: TransformCallback): void{
297
+
if(!this.headersSent){
298
+
this.flushHeaders();
299
+
}
300
+
// In some cases we might not have a store i.e. for example in the image optimization function
301
+
// We may want to reconsider this in the future, it might be intersting to have access to this store everywhere
0 commit comments