Alex Villarreal

~~@anthony-murphy in your POC you gave no default to the new constructor parameter for `FluidDataStoreRuntime`, and that required that a bunch of places be updated immediately with their own functions....

> I'd love to see IFluidDataStoreFactory changes as part of this change, and ideally - at least one example that demonstrates full end-to-end usage. This feels like where I'd start,...

> I'd love to see IFluidDataStoreFactory changes as part of this change, @vladsud are you thinking of literal changes to the interface, or changes to its implementations so they leverage...

I'll add and push some of the local work on expanding the scope of this change to make it more "tangible" without making it breaking yet.

Oh, @tyler-cai-microsoft , I had forgotten to tag you in this one. PR is still kind of in flux, but feel free to explore and comment.

I'm not a fan of the approach on this commit, with a static `Container.loader`, just putting it out there as a possible approach as part of the experiments. Want to...

> Is this going to make repo-policy-check or fluid-build or whatever complain that your package.json scripts are not complying to the expected standard? Good point, I'll check. > What exactly...

The latest commit updates fluidPackageCheck in fluid-build so it supports several possible expected versions for a given script (e.g. `test:build` can be `tsc --project ./src/test/tsconfig.json` or `tsc --build ./src/test/tsconfig.json`). That...

Waiting for https://github.com/microsoft/FluidFramework/pull/11299 to be merged, that should take care of the "client packages" failed check about different versions between the new dependency on @fluid-tools/benchmark in the sequence package, and...

I'm experiencing something similar with uwsgi 2.0.17 behind nginx 1.10.3 (communicating with a socket file, uwsgi protocol), running in a Debian 9 Docker container, with Python 3.6.5. In my case...