bigdata

In https://github.com/taosdata/TDengine/blob/develop/src/client/src/tscPrepare.c, Local variable loopCont is assigned only once, to a constant value, making it effectively constant throughout its scope. If this is not the intent, examine the logic to see if there is a missing assignment that would make loopCont not remain constant.

So the 1567th line should be removed.
![image](https://user-im

The current RDL integrate test engine and cases are in-corrected.

I just removed the cases on #16004.

The problem of current RDL cases:

1. The SQL of case should be RDL, not RQL;
2. Should not change current rules, which are used to RAL and RQL, it is better to CREATE/ALTER/DROP new rule for assertion.

Please Redesign the RDL test engine and rewrite the related test cases.

vaex.from_arrays(s=['a,b']).s.str.replace(r'(\w+)',r'--\g<1>==',regex=True)

when using capture group in str, it fails, while str_pandas.replace() is correct

Name: vaex
Version: 4.6.0
Summary: Out-of-Core DataFrames to visualize and explore big tabular datasets
Home-page:

What would you like to be added:

can we add an extender framework such as kube-scheduler's extender. maybe we can send a RPC request or http request on each plugin functions, such as predicateFns.

Why is this needed:

we can add some logic of scheduling out of source code. such as an Operator specific requirements of scheduling

Describe the bug
When the finalizer is called for CLR JvmObjectId objects, it calls the rm DotnetBackend method and this calls goes through the JvmBridge class. Because the rm call goes through [JvmBridge.CallJavaMethod](https://github.com/do

especially for less obvious but lengthy code snippets!

Follow the implementation example of ingestion/tests/integration/ometa/test_ometa_database_service_api.py to implement the testing of the Python client for PipelineService.