Maciej

Did you manage to work this one out? Sounds a bit like a race condition

Ok. I'm away all week so can't test this myself, but could you try two things: 1. Change the storage to memcache and cookie and see if the same problem...

That's probably the best thing to do for now. I'll see if I can play with it over the next week to try and track it down.

You guys get `symlink` problems, I get `rename` issues :frowning: ``` [==============================] 100.00%C:\Users\\Roaming\npm\node_modules\ied\bin\cmd.js:57 throw err ^ Error: EPERM: operation not permitted, rename 'D:\Projects\\node_modules\.tmp\c1510493-3b61-4eaf-b5a7-743438e26d4a' -> 'D:\Projects\node_modules\f7b6cee64aabea6944b2a679023d533e40aebfdc' at Error (native) ```

It's a really simple fix. In the database layout template, the last loop that iterates through options. Just needs a check if_array.... Print_r instead of echo or something.

I tried to test @michalskalski's solution, but it still caused the freeze me. ~However, my Rust knowledge is close to zero, so could someone check if the following change is...

Spreading the `input` prop instead of manually assigning `value` and `onChange` did the trick for me. ```javascript // BAD const { value, onChange } = input ``` ```javascript // GOOD...

Switching directly to `zip-stream` resolves all the issues for _very large_ archives when using streams. Thanks @raghuchahar007 for a great example!

@raghuchahar007 I only took the "zipping & file adding parts" out of your code and modified it to our needs. It seems to work great on lambdas creating +1GB zips....

Is there an easy way to get all the registered routes now? Like a map of url -> handlers or something.