walkacross

hi there @Trinkle23897 , thanks for your quick and detail feedback. I see the advantage of using bazel, specially in saving a lot of time for CI. what I'm wondering...

google-cloud-cpp might be in the same situation, here is their thinking, just for reference. https://github.com/googleapis/google-cloud-cpp/blob/main/doc/contributor/working-with-bazel-and-cmake.md

In short, auto-reset in gym: ~~~ reset_obs = env.reset() action_result_in_done = poilicy(reset_obs) a_reset_obs, reward, done, info = env.step(action_result_in_done) ~~~ in envpool ~~~ reset_obs = envpool_env.reset() action_result_in_done = policy(reset_obs) not_a_reset_obs, reward1,...

In short, auto-reset in gym: ~~~ reset_obs = env.reset() action_result_in_done = poilicy(reset_obs) a_reset_obs, reward, done, info = env.step(action_result_in_done) ~~~ in envpool ~~~ reset_obs = envpool_env.reset() action_result_in_done = policy(reset_obs) not_a_reset_obs, reward1,...

> Hi 👋 Do you have a DB running locally in another container ? If so you need to make it accessible from inside the docker container see [here](https://stackoverflow.com/a/24326540) >...