-
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…
-
As discussed in the meeting earlier today, I'd like to see us move to a model where this functions is a bit easier to unit test by creating logical abstractions where they make sense and mocking them …
-
## Bug Report
#### What did you do?
Submitted PR #6401 for the scorecard-test-kuttl container image, which got merged and is part of the recent operator-sdk v1.29.0 release.
#### What did you…
-
### Summary
The current Workflow implementation allows for the registration of dependent ready conditions, which produces a binary result. However, the specific business logic for what "ready" means …
btlem updated
3 weeks ago
-
We have one in https://github.com/operator-framework/community-operators/tree/master/community-operators/buildv2-operator , which drives the OperatorHub on OKD
We need one in https://github.com/ope…
-
The label selector used for both catalogd and operator-controller metrics services is: `control-plane: controller-manager`. Now that both catalogd and operator controller are running in the same names…
-
In OLMv1, we plan to support the `registry+v1` bundle format in order to provide a means for migration from OLMv0. However, we recognize the many pain points and limitations of that format (to name a …
-
# Function Composition and the Pipe Operator in C++23 – With std::expected - C++ Stories
In this blog post, we’ll show how to implement a custom pipe operator and apply it to a data processing exampl…
-
We discussed a similar topic [here](https://github.com/operator-framework/operator-controller/pull/846/#discussion_r1601374857): do we really need these reasons? I don't think we have a use case for t…