Jinjing Zhou

And also starship package, it used github domain to host packages, which is hard to install when network issue exists when we don't have cache

Generally, this means function can share information across different function. Solution 1: Use global variable-like mechanism For example, using `provide` and `inject` (idea from vue3) ``` def cuda(version="11.6.2"): provide("cuda/version", "11.6.2")...

@kemingy Arbitrary global variable doesn't seem good. At least a global dictionary needed I think. such as we have a global variable such as `global_info` and user can do anything...

From what I understood here, podman has the same implementation as docker. And we are adding a new context name for podman, right?

We had some discussions here https://github.com/tensorchord/envd/issues/1132#issuecomment-1308433521 about the interface. I think it's better to make it as a key-value interface instead of methods.

@kemingy So that every function can provide such information. For example envdlib can provide `torch` as function. Contributor can also provide torch version in the function. Other packages relying on...

Yes. Something like `env.get("os/version", "20.04")`, `env.get("os/name", "ubuntu")` or `env["package/torch"]="1.12.0"` `env.get(key, default_value)`. The same syntax as python dict

@cutecutecat Actually I think it's fine for the users to write into the key-value graph. For example, some library will depends on tensorrt version, and tensorrt is only provided in...

Some thoughts: - Override can be a feature instead of a bug. Just like dynamic language as Python, you can monkey patch any methods on your own. For now, I...

Support envd run on envd server and design support for distributed job