Martin Adámek

I am not 100% sure if/how this is related, but there is one flaky test that is doing upserts without explicit transaction (which is in general bad idea, but should...

It looks like I discovered another problem when debugging this. I turned that flaky test into a heavy load test - doing ~1 million requests totally, using 50 entities via...

@wasd171 also, have you verified what I was asking for above? Whether the issue is coming from `em.populate()`, or if the property was undefined before you call it? As I...

> those are also undefined :( _also_ or _always_? i dont see how `em.populate` could wipe anything, i would expect it to be coming from the factory all the time,...

> Error on the field resolver level (em.populate) My point is that to me this all sounds like the problem is not in `em.populate` as you say. You just try...

I will need complete reproduction for this. Edit: i guess this is only about the array, right? If you put object inside it works?

Maybe we could replace `ow` with something faster, I see @vladfrangu just used https://github.com/sapphiredev/shapeshift in the new memory storage, it claims to be blazing fast :P @vladfrangu how does it...

Let's measure, I am not against it, especially if we would migrate away from `ow` so we would have to touch all the places anyway. Btw are we sure its...

Dockerfiles are in the templates, crawlee has its own templates just like apify-cli has, it would be better to have this handled in both. But looking at the logs, I...

> It seems that some functions are reported as methods and some as properties? This will be resolved by #1550, it depends on the signature, e.g. `foo(): any` vs `foo:...