Suggestion / Problem
After enabling KafkaConnectors CRD through the annotation as described on the documentation
we lost all the configuration from the existing connectors configured through the REST API

Our expectation was that both could live together

Documentation Link

• https://strimzi.io/docs/master/#kafkaconnector_resources
• https://strimzi.io/docs/master/#con-creating-

The hyperloglog unit tests depend on the presence of /usr/share/dict/words (see https://github.com/tylertreat/BoomFilters/blob/611b3dbe80e85df3a0a10a43997d4d5784e86245/hyperloglog_test.go#L34). It would be helpful to include the test data in the repo to ensure the tests work without modification on systems that don't follow that dictionary path convention or don't load a dictionary package.

Description of Problem:CMake Warning (dev) at C:/devel/vcpkg/scripts/buildsystems/vcpkg.cmake:195 (_add_library):

Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target. Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.

OpenSCAP Version:1.4.0

Operating Sys

Maybe it should be just or only and should be used to signal a consumer that synchronous MoveNext should return true. There are cases when we do not want to evaluate every CurrentValue, e.g. to take Nth value. With IObservable the only way to do so is to not send values inside OnNext.

sbt experiment command in root should execute all experiments (c.f. flex.experiment package). However, for now, only one experiment is executed (with arg0). Therefore, the experiment command that does not have an argument must perform all the experiment codes. See Tasks.

Post v2.3 release (where we apply the custom headers and accept a URL that can have a prefix in its path), we should update the following docs:

• Readme (which is visible on github and npm),
• Official API reference doc over here.

If we union two conditional branches right after the branching, during the optimization, the conditional branch vertex should have two edges toward the union operator.
However, this cannot be represented as a DAG that our system supports.
Fortunately, this situation is very weird and minor corner case.
Anyway, we have to deal with this (at least throw an exception).

• when constructing logic

Need to make this configurable and be sure it's setup to happen every so often (~once/week)!