-
## Type of question
General operator-related help
## Question
#### What did you do?
There used to be an `ansible-operator` binary that could be run on a Mac till version …
-
https://github.com/microsoft/reverse-proxy/tree/main/src/OperatorFramework includes 5 new packages that we don't anticipate owning long term. For preview11 and 1.0 we need to decide if we should direc…
-
In `internal/controllers/suite_test.go`:
Nit: move the mocks to a separate package and/or file to make them easier to find?
_Originally posted by @joelanford in https://github.com/operator-framewo…
-
The production ansible operator base image is up to 4.15 - we need to move to it. Do what we did last time when we moved to 4.13: https://github.com/kiali/kiali/issues/6220
* Downstream v4.15: http…
-
Lots of times when people get down into the nitty gritty of using a parsing framework, it's because their ad-hoc attempts at using a regex or whatever for a complicated grammar becomes unwieldy. One …
-
Related to #453. One recommendation of that issue is:
> * Remove model-specific instructions like `LSTM` and `gru`
## Current support across backends
| Operator | [DirectML](https://learn.mic…
-
Recently we've done some work related to TLS support that has uncovered some difficulty in navigating the existing layout of manifests and utilization of kustomize to compose the V1 components and ins…
-
This is a placeholder issue for communicate state regarding JOSDK and Operator Framework membership.
-
See #4 and #6 for specific use cases (but mainly #4).
For example, what happens if another framework defines `infix operator |> {}`, but with conflicting associativity or precedence, and then I impor…
-
### bug描述 Describe the Bug
[Hint: Expected desc.ParseFromArray(buf.get(), size) == true, but received desc.ParseFromArray(buf.get(), size):0 != true:1.] (at /paddle/paddle/fluid/framework/tensor_uti…