text:
[HUDI-7617] Fix issues for bulk insert user defined partitioner in StreamSync

Change Logs
NOTE: This PR handles only AVRO code paths, there will be follow-up patch for RowWriter code paths as well.
There are two problems with BULK_INSERT and partitioners.

Passing user defined partitioner using hoodie.bulkinsert.user.defined.partitioner.class is not honoured in the StreamSync code path and the data is written in a non-sort mode and can lead to OOM errors because of too many open writeHandles.
There is another problem with RDDCustomColumnsSortPartitioner where data is globally sorted but too many files are written because data is actually not pre-pending the partition keys in the sort columns. The unit test fails with this error for existing code.

org.opentest4j.AssertionFailedError:
Expected :654
Actual   :3
<Click to see difference>

// Verify each partition has one base file because parallelism is 1.
assertEquals(baseFiles.size(), partitions.size());

https://github.com/onehouseinc/hudi-internal/blob/master/hudi-client/hudi-spark-client/src/main/java/org/apache/hudi/execution/bulkinsert/RDDCustomColumnsSortPartitioner.java#L60
 @Override
  public JavaRDD<HoodieRecord<T>> repartitionRecords(JavaRDD<HoodieRecord<T>> records,
                                                     int outputSparkPartitions) {
    final String[] sortColumns = this.sortColumnNames;
    final SerializableSchema schema = this.serializableSchema;
    final boolean consistentLogicalTimestampEnabled = this.consistentLogicalTimestampEnabled;
    return records.sortBy(
        record -> {
          Object[] columnValues = record.getColumnValues(schema.get(), sortColumns, consistentLogicalTimestampEnabled);
          return FlatLists.ofComparableArray(columnValues);
        },
        true, outputSparkPartitions);
  }

But _hoodie_partition_path is returned as null here using record.getColumnValues, added the screenshots from debugger because these fields are actually added as part of HoodieAvroParquetWriter.
https://github.com/onehouseinc/hudi-internal/blob/master/hudi-common/src/main/java/org/apache/hudi/io/storage/HoodieAvroParquetWriter.java#L64
  @Override
  public void writeAvroWithMetadata(HoodieKey key, IndexedRecord avroRecord) throws IOException {
    if (populateMetaFields) {
      prepRecordWithMetadata(key, avroRecord, instantTime,
          taskContextSupplier.getPartitionIdSupplier().get(), getWrittenRecordCount(), fileName);
      super.write(avroRecord);
      writeSupport.add(key.getRecordKey());
    } else {
      super.write(avroRecord);
    }
  }

  default void prepRecordWithMetadata(HoodieKey key, IndexedRecord avroRecord, String instantTime, Integer partitionId, long recordIndex, String fileName) {
    String seqId = HoodieRecord.generateSequenceId(instantTime, partitionId, recordIndex);
    HoodieAvroUtils.addHoodieKeyToRecord((GenericRecord) avroRecord, key.getRecordKey(), key.getPartitionPath(), fileName);
    HoodieAvroUtils.addCommitMetadataToRecord((GenericRecord) avroRecord, instantTime, seqId);
  }

Attaching the screenshots below where _hoodie_partition_path column is null.

Impact
No impact, fixing the bugs related to BULK_INSERT user defined partitioners to ensure it sorts the data correctly.
Risk level (write none, low medium or high below)
Medium.
Documentation Update
None.
Contributor's checklist

[x] Read through contributor's guide
[x] Change Logs and Impact were stated clearly
[x] Adequate tests were added if applicable
[x] CI passed

Azure CI is green.

source: gharchive/pull-request


text:
[HUDI-1129]: AvroConversionUtils unable to handle avro to row transformation when passing evolved schema

What is the purpose of the pull request
Specific fix this error: https://issues.apache.org/jira/browse/HUDI-1129
This is needed to partially fix https://github.com/apache/hudi/issues/1845
Brief change log

Use avro field names and not indices to convert from avro to GenericRow of catalyst at AvroConversionHelper

Verify this pull request
Run maven test suite
Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Hi @bvaradar the test currently fails because of the EOFException from https://issues.apache.org/jira/browse/HUDI-1128

I found the issue after some debugging. But need your thoughts on whether it is a bug or how to go about fixing it.
@bvaradar @n3nash @vinothchandar
As per the test case linked to reproduce, here is what we are doing.
Generate records with SCHEMA_1 and ingest to Hudi with SCHEMA_1
Generate records with SCHEMA_2 and ingest to Hudi with SCHEMA_2
Generate records with SCHEMA_1 and ingest to Hudi with SCHEMA_2(both source and target schema)// this is where the exception is thrown.
Here is the gist of the issue.
Lets say we have an avro record with SCHEMA_1
byte[] recordBytes = HoodieAvroUtils.avroToBytes(genericRecord);
Converting this back to GenRec with SCHEMA_1 succeeds. HoodieAvroUtils.bytesToAvro(recordBytes, SCHEMA_1)
But converting this back to GenRec with SCHEMA_2 (which has one additional field compared to SCHEMA_1) fails.

This is not required anymore. https://github.com/apache/hudi/pull/2927 handles the schema evol.

authors: nsivabalan sbernauer

repo: apache/hudi

license_type: permissive

license_source: github-api


text:
[MINOR] clean up and add comments to flink client

What is the purpose of the pull request
Minor code clean up and added some comments.
Brief change log
rename HudiFlinkStreamer to HoodieFlinkStreamer
Verify this pull request
This pull request is a trivial rework / code cleanup without any test coverage.
Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@wangxianghu did some clean up while reading the code. Please take a look when you are free.

Codecov Report

Merging #2261 (f9e2b0f) into master (4d05680) will decrease coverage by 43.13%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master    #2261       +/-   ##
=============================================
- Coverage     53.53%   10.39%   -43.14%
+ Complexity     2770       48     -2722
=============================================
  Files           348       50      -298
  Lines         16109     1779    -14330
  Branches       1643      211     -1432
=============================================
- Hits           8624      185     -8439
+ Misses         6786     1581     -5205
+ Partials        699       13      -686

Flag
Coverage Δ
Complexity Δ

hudicli
?
?

hudiclient
?
?

hudicommon
?
?

hudihadoopmr
?
?

hudispark
?
?

huditimelineservice
?
?

hudiutilities
10.39% <ø> (-59.70%)
0.00 <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ
Complexity Δ

...va/org/apache/hudi/utilities/IdentitySplitter.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-2.00%)

...va/org/apache/hudi/utilities/schema/SchemaSet.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-3.00%)

...a/org/apache/hudi/utilities/sources/RowSource.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-4.00%)

.../org/apache/hudi/utilities/sources/AvroSource.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-1.00%)

.../org/apache/hudi/utilities/sources/JsonSource.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-1.00%)

...rg/apache/hudi/utilities/sources/CsvDFSSource.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-10.00%)

...g/apache/hudi/utilities/sources/JsonDFSSource.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-4.00%)

...apache/hudi/utilities/sources/JsonKafkaSource.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-6.00%)

...pache/hudi/utilities/sources/ParquetDFSSource.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-5.00%)

...lities/schema/SchemaProviderWithPostProcessor.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-3.00%)

... and 325 more


text:
[HUDI-4284] Implement bloom lookup tree as red-black tree

What is the purpose of the pull request
The existing KeyRangeLookupTree implementation is Binary Sorting Tree.
Although it is shuffled before insertion, it may still cause uneven distribution. This PR implement it as a Red Black Tree.
Brief change log
Added abstract implementation of red-black tree RedBlackTree and implement the KeyRangeLookupTree as red-black tree.
Verify this pull request
Added new unit test org.apache.hudi.common.util.rbtree.TestRedBlackTree
Committer checklist

[x] Has a corresponding JIRA in PR title & commit

[x] Commit message is descriptive of the change

[x] CI is green

[x] Necessary doc changes done or have another open PR

[x] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@codope Please take a look~

@vinothchandar Can you help review this PR, thanks.

@yabola Thanks for putting up this PR. Sorry for the delay as I was occupied with Hudi release work. I am going to review it towards the end of week. Expect feedback by Monday.

@yihua Hi, if you have time, can you help review my PR, thanks~

authors: codope yabola


text:
[HUDI-5477] Optimize timeline loading in Hudi sync client

Change Logs
Before this change, the Hudi archived timeline is always loaded during the metastore sync process if the last sync time is given. Besides, the archived timeline is not cached inside the meta client if the start instant time is given. These cause performance issues and read timeout on cloud storage due to rate limiting on requests because of loading archived timeline from the storage, when the archived timeline is huge, e.g., hundreds of log files in .hoodie/archived folder.
This PR improves the timeline loading by
(1) only reading active timeline if the last sync time is the same as or after the start of the active timeline;
(2) caching the archived timeline based on the start instant time in the meta client, to avoid unnecessary repeated loading of the same archived timeline.
Impact
This PR improves the performance of metastore sync.
Risk level
low
Documentation Update
N/A
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

CI passes.  Merging this PR


text:
parquet_path_to_id_mapping generates incorrect path for List types

Apache Iceberg version
main (development)
Please describe the bug 🐞
When using the add_files table api, the parquet metadata needs to be read and a mapping of Dict[str, int] is used by data_file_statistics_from_parquet_metadata in order to link the field ID to the name in the parquet file for statistics collection. However during the mapping lookup I was receiving an error that a key was not present.
My schema contains one of the following (its a subfield of a Details struct which is important for the full name later):
extras: large_list<item: struct<key: string not null, value: string>> not null
  child 0, item: struct<key: string not null, value: string>
      child 0, key: string not null
      child 1, value: string

Which based on the parquet schema path definition has a path of:
Details.extras.list.item.key
Details.extras.list.item.value

The issue is that the parquet_path_to_id_mapping returns a mapping for these two fields as follows:
Details.extras.list.element.key -> 189
Details.extras.list.element.value -> 190

So, the issue appears to be that the visitor for constructing the schema paths is incorrectly using element instead of item as expected in the parquet schema paths. I am not sure how this manifests yet, as I have not dug into it too closely.

@cgbur Thanks for raising this. Could you share the stack trace that you're seeing?
I tried to reproduce it, but it works on my end:
def test_data_file_statistics_from_parquet_metadata_list(tmp_path_factory: pytest.TempPathFactory) -> None:
    pyarrow_list = pa.schema([
        pa.field("extras", pa.list_(pa.field("element", pa.struct([pa.field("key", pa.string()), pa.field("value", pa.string())]))))
    ])
    tbl = pa.Table.from_pylist([{'some_list': [{"key": "a", "value": "b"}]}], schema=pyarrow_list)
    file_path = tmp_path_factory.mktemp('test_statistics') / "test.parquet"
    pq.write_table(tbl, file_path)

    parquet_metadata = pq.read_metadata(file_path)

    iceberg_schema = Schema(
        NestedField(
            1,
            "extras",
            ListType(
                10,
                StructType(
                    NestedField(10, "key", StringType()),
                    NestedField(11, "value", StringType()),
                ),
                element_required=False,
            ),
        )
    )

    statistics = data_file_statistics_from_parquet_metadata(
        parquet_metadata=parquet_metadata,
        stats_columns=compute_statistics_plan(iceberg_schema, EMPTY_DICT),
        parquet_column_mapping=parquet_path_to_id_mapping(iceberg_schema),
    )

    assert statistics == DataFileStatistics(
        record_count=1,
        column_sizes={10: 51, 11: 51},
        value_counts={10: 1, 11: 1},
        null_value_counts={10: 1, 11: 1},
        nan_value_counts={},
        column_aggregates={},
        split_offsets=[4],
    )

Here is a complete example recreating the error. Here I am using polars to make the table which results in the same schema that I am producing with pyarrow.
import polars as pl
from pyiceberg.catalog.sql import SqlCatalog
import pyarrow.parquet as pq
import os
import shutil

pl.DataFrame(
    {
        "a": [[{"a": 1}, {"a": 2}], [{"a": 3}]],
    }
).write_parquet("example.parquet")

warehouse_path = "/tmp/warehouse"

# wipe the warehouse
if os.path.exists(warehouse_path):
    shutil.rmtree(warehouse_path)

os.makedirs(warehouse_path)

catalog = SqlCatalog(
    "default",
    **{
        "uri": f"sqlite:///{warehouse_path}/pyiceberg_catalog.db",
        "warehouse": f"file://{warehouse_path}",
    },
)
df = pq.read_table("example.parquet")
catalog.create_namespace("default")
table = catalog.create_table(
    "default.webserver",
    schema=df.schema,
)
table.add_files(["example.parquet"])

And here is the error. The top two lines were debug statements showing how the mapping file has the incorrect path.
    print(f"column mappings {len(parquet_column_mapping)}")
    print(parquet_column_mapping)

column mappings 1
{'a.list.element.a': 3}
Traceback (most recent call last):
  File "/home/cgbur/pyice-test/failure.py", line 36, in <module>
    table.add_files(["example.parquet"])
  File "/local/home/cgbur/pyice-test/iceberg-python/pyiceberg/table/__init__.py", line 1355, in add_files
    tx.add_files(file_paths=file_paths, snapshot_properties=snapshot_properties)
  File "/local/home/cgbur/pyice-test/iceberg-python/pyiceberg/table/__init__.py", line 462, in add_files
    for data_file in data_files:
  File "/local/home/cgbur/pyice-test/iceberg-python/pyiceberg/table/__init__.py", line 2737, in _parquet_files_to_data_files
    yield from parquet_files_to_data_files(io=io, table_metadata=table_metadata, file_paths=iter(file_paths))
  File "/local/home/cgbur/pyice-test/iceberg-python/pyiceberg/io/pyarrow.py", line 1869, in parquet_files_to_data_files
    statistics = data_file_statistics_from_parquet_metadata(
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/local/home/cgbur/pyice-test/iceberg-python/pyiceberg/io/pyarrow.py", line 1734, in data_file_statistics_from_parquet_metadata
    field_id = parquet_column_mapping[column.path_in_schema]
               ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
KeyError: 'a.list.item.a'

You can see how the parquet path_in_schema using the item instead of element.

Ah, confusingly there appears to be writer differences that cause the issue. My Rust pyarrow implementation matches when polars has pyarrow=True.
import polars as pl
import pyarrow.parquet as pq

df = pl.DataFrame(
    {
        "a": [[{"a": 1}, {"a": 2}], [{"a": 3}]],
    }
)

def print_schema_path(path, col_name):
    metadata = pq.read_metadata(path)
    for group_number in range(metadata.num_row_groups):
        row_group = metadata.row_group(group_number)
        for column_number in range(row_group.num_columns):
            column = row_group.column(column_number)
            if column.path_in_schema.startswith(col_name):
                print(f"path_in_schema: {column.path_in_schema}")

df.write_parquet("example.parquet", use_pyarrow=False)
print("with polars")
print(pq.read_schema("example.parquet"))
print_schema_path("example.parquet", "a")
df.write_parquet("example.parquet", use_pyarrow=True)
print("with pyarrow")
print(pq.read_schema("example.parquet"))
print_schema_path("example.parquet", "a")

with polars
a: large_list<item: struct<a: int64>>
  child 0, item: struct<a: int64>
      child 0, a: int64
path_in_schema: a.list.item.a
with pyarrow
a: large_list<element: struct<a: int64>>
  child 0, element: struct<a: int64>
      child 0, a: int64
path_in_schema: a.list.element.a

Perhaps the visitor is not respecting the name used in the schema? Or there is a mismatch in the method used to acquire between the iceberg and parquet change?

Hi, I investigated this a bit further and it seems to be related to the way the visitor works as @cgbur suggested. Here is what I tried:
def test_parquet_path_to_id_mapping():
    # set field name to "item"
    pyarrow_list = pa.schema([
            pa.field("extras", pa.list_(pa.field("item", pa.struct([pa.field("key", pa.string()), pa.field("value", pa.string())]))))
        ])

    # this is called during table creation
    schema = Catalog._convert_schema_if_needed(pyarrow_list)

    mapping = parquet_path_to_id_mapping(schema)
    assert "extras.list.item.key" in mapping

The mapping that Catalog._convert_schema_if_needed creates looks like this:
{'extras.list.element.key': -1, 'extras.list.element.value': -1}

Looking into the visitor I found the method dealing with list types sets a default field name of "elements".
https://github.com/apache/iceberg-python/blob/20c273104257f0a1ccd74a09f6d4601643115ffd/pyiceberg/io/pyarrow.py#L865-L870
https://github.com/apache/iceberg-python/blob/20c273104257f0a1ccd74a09f6d4601643115ffd/pyiceberg/io/pyarrow.py#L172
So we lose the information on the field name of the value field, setting it to "elements".
Unfortunately I haven't found a way to access the field name as both pyarrow.lib.ListType and pyarrow.lib.DataType don't seem to make that available.

Hi @cgbur and @felixscherz thank you for raising this and taking this investigation further. I'm not a polars user myself, but the difference in the behavior is quite interesting, and I think there would be value in trying to fix this issue.
I just read the write_table API documentation in pyarrow.parquet and found something rather interesting:
https://arrow.apache.org/docs/python/generated/pyarrow.parquet.write_table.html#pyarrow.parquet.write_table
If you check the documentation for use_compliant_nested_type flag, it mentions that having element as the single item field name is the parquet compliant format as specified here on the Parquet Spec for Nested Types. PyArrow defaults to using this flag and writes the list element field name as element.
For some reason it looks like polars has decided to use item - the non-parquet compliant list element name instead. While I'm curious about why the polars community has decided to go this route, I also think supporting both element or item name in the visitor may not be the worst thing, just to increase our scope of support.

Here is the code in Polars where the "item" name crops up.
https://github.com/pola-rs/polars/blob/main/crates/polars-core/src/datatypes/dtype.rs#L575
I believe this is because they are not converting to parquet, but to arrow, then parquet. A subtle difference in their internal logic. However, perhaps the confusion arises because in arrow, the List single element name is often item not element.
https://arrow.apache.org/docs/format/Columnar.html#recordbatch-message
import pyarrow as pa

py_list = pa.array([[1, 2, 3], [1, 2]])
print(py_list.type)

list<item: int64>

I'll go ahead and open an issue on the Polars repo and see if they have anything to say, there are multiple ways to fix this in their package and agree they should likely be producing parquet files according to the spec.

source: gharchive/issue

authors: Fokko cgbur felixscherz syun64

repo: apache/iceberg-python


text:
Airflow improperly shows task status as 'up for retry' for a task that failed on re-run

Dear Airflow Maintainers,
Environment
Before I tell you about my issue, let me describe my Airflow environment:

Airflow version: 1.7.0
Airflow components: webserver, mysql, scheduler with celery executor
Python Version: 2.7.6
Operating System: Linux Ubuntu 3.19.0-26-generic

Description of Issue
Now that you know a little about me, let me tell you about the issue I am having:
What I expect:
If I do a re-run and it fails - The task should be either re-tried again (resetting retry count) and marked accordingly in GUI OR not retried - and marked in GUI as 'failed'

What happened instead?
The task in the GUI was presented as 'up_for_retry' however it was not retried, even after retry_delay has passed

Reproducing the Issue
DAG does not have some strange settings:
concurrency= 3,
max_active_runs = 2,
start_date = datetime(2016,04,03,01),
default_args={
'depends_on_past': False,
'retries': 2,
'retry_delay': timedelta(minutes=3) }

@kretes Can you create a Jira issue for this and provide a reproducible case with it plus screenshots? Thanks

migrated to https://issues.apache.org/jira/browse/AIRFLOW-138

authors: bolkedebruin kretes

repo: apache/incubator-airflow

license_source: bigquery


text:
[AIRFLOW-219] Unix user impersonation based on new BaseOperator.run_as_user

[Work in Progress]
https://issues.apache.org/jira/browse/AIRFLOW-219
I'm looking for guidance around:

the bash magic sudo su {ti.run_as_user}; ...
the consideration & requirements I started highlighting in the Security docs in the PR

The sudo principle is quite easy to implement. What I am more worried about is how to manage it correctly. For example you might want to guard against tasks becoming root or have an admin be able the configure a list of acceptable userids.
In case of versioning we probably get some issues that are not foreseen yet, but as versioning is slowly being addressed should not be too much of a thing. Improvements will happen overtime.

Might also want to have a look at Hadoop's container-executor:

http://www.cloudera.com/documentation/archive/cdh/4-x/4-2-0/CDH4-Security-Guide/cdh4sg_topic_18_3.html
https://github.com/apache/hadoop/blob/master/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/container-executor.c

[Current coverage][cc-pull] is 64.38%

Merging [#1578][cc-pull] into [master][cc-base-branch] will decrease coverage by <.01%

@@             master      #1578   diff @@
==========================================
  Files           123        124     +1
  Lines          8683       8748    +65
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           5591       5632    +41
- Misses         3092       3116    +24
  Partials          0          0

Powered by Codecov. Last updated by [348f25f...dacf41f][cc-compare]
[cc-base-branch]: https://codecov.io/gh/apache/incubator-airflow/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/apache/incubator-airflow/compare/348f25f08af2c02627cec04453564edd2fb69fa3...dacf41f387e994a6c23f99d701207be5334983a2?src=pr
[cc-pull]: https://codecov.io/gh/apache/incubator-airflow/pull/1578?src=pr

For the BashOperator, only the subprocess needs to be run as the specified user, not the entire airflow command. If the specified user doesn't have permissions to airflow.cfg, we should be set.

@mistercrunch you can close this as it lives here now: https://github.com/apache/incubator-airflow/pull/1934

authors: aoen bolkedebruin codecov-io criccomini mistercrunch plypaul


text:
[AIRFLOW-2186] Change the way logging is carried out in few ops

Make sure you have checked all steps below.
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-2186

Description

[x] Here are some details about my PR, including screenshots of any UI changes:
Changed the way logging is implemented in PostgresToGoogleCloudStorageOperator and HiveToDynamoDBTransferOperator.  Changed logging.info to self.log.info

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
Minor change. Doesn't require testing

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

[x] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

cc @Fokko PTAL. The Travis CI fails as apache-beam[gcp] is not available for Python 3.

@kaxil The apache-beam issue has been fixed in master.

@Fokko haha yes, I fixed that in a PR  😉  💃

authors: Fokko kaxil


text:
[AIRFLOW-3355] Fix BigQueryCursor.execute to work with Python3

Make sure you have checked all steps below.
Jira

[x] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-3355
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

BigQueryCursor.execute uses dict.iteritems internally,
so it fails with Python3 if binding parameters are
provided. This PR fixes this problem.
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

tests.contrib.hooks.test_bigquery_hook:TestBigQueryCursor
Commits

[x] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[x] Passes flake8

CI failures occur at test_scheduler_sla_miss_callback_exception and test_scheduler_sla_miss_email_exception and are irrelevant to this fix.

Codecov Report

Merging #4198 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #4198      +/-   ##
=========================================
+ Coverage   77.69%   77.7%   +<.01%
=========================================
  Files         199     199
  Lines       16309   16309
=========================================
+ Hits        12672   12673       +1
+ Misses       3637    3636       -1

Impacted Files
Coverage Δ

airflow/models.py
92.37% <0%> (+0.04%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8668ef8...eab19b0. Read the comment docs.

authors: codecov-io sekikn


text:
APEX-22 #commit adding the port object only when it doesn't already e…

…xist

@davidyan74 Please review and merge

repo: apache/incubator-apex-core


text:
[BEAM-551] Add TextIO.Write support for ValueProvider

R: @dhalperi

Some issues deferred, but can be resolved orthogonally.

And merged. Thanks.

authors: dhalperi sammcveety

repo: apache/incubator-beam


text:
What is external:ssl in BUILD.bazel

Describe the bug (描述bug)
com_github_brpc/BUILD.bazel:324:11: no such target '//external:ssl': target 'ssl' not declared in package 'external' defined by

To Reproduce (复现方法)
bazel build brpc
Expected behavior (期望行为)
Versions (各种版本)
OS: Ubuntu 20.04.2 LTS
Compiler: bazel 3.7.0
brpc: commit b3a948c9dca29632b3367529488e070852e31f11
protobuf: v3.15.6
Additional context/screenshots (更多上下文/截图)

butil depends on "//conditions:default": ["//external:ssl"],

repo: apache/incubator-brpc


text:
brpc log performance

我有个问题，关于log的：
1：目前我看到brpc的log中，使用了localtime_s/localtime_r，这两个函数应该调用了__tz_convert， __tz_convert，有tzset_lock全局锁，每次获取时间都会使用到kernel级别的futex锁，不知道我分析的对不对，这块getimeofday会不会好点
#if _MSC_VER >= 1400
    localtime_s(&local_tm, &t);
#else
    localtime_r(&t, &local_tm);
#endif

2：关于log打印的问题，目前多线程下，log打印是有锁的，当打印的内容比较多的时候，这个锁就会有一定的问题，是否有种无锁的设计方式？

这个log主要是提供接口，实现作为参考，性能是没有任何优化的，在生产环境中建议适配使用公司内或第三方日志库

@jamesge 好的，谢谢戈神，目前我实现的方法是继承了LogSink，但没看到类似于glog那种AddLogSink()，如何调用我这个logsink呢，还是得改brpc源码

找到了

authors: gxkevin jamesge


text:
[fix-4273][UI] The submission time of task instance is empty

What is the purpose of the pull request
#4273
Fix the submission time of task instance is empty
Verify this pull request
This change added tests and can be verified as follows:

Manually verified the change by testing locally.

Codecov Report

Merging #4274 (3bebbec) into dev (64dd9db) will decrease coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #4274      +/-   ##
============================================
- Coverage     43.14%   43.09%   -0.05%
+ Complexity     3153     3149       -4
============================================
  Files           466      466
  Lines         21632    21603      -29
  Branches       2611     2610       -1
============================================
- Hits           9333     9310      -23
+ Misses        11401    11393       -8
- Partials        898      900       +2

Impacted Files
Coverage Δ
Complexity Δ

...che/dolphinscheduler/common/utils/LoggerUtils.java
62.50% <0.00%> (-8.34%)
5.00% <0.00%> (-1.00%)

...e/dolphinscheduler/common/shell/AbstractShell.java
44.53% <0.00%> (-5.89%)
5.00% <0.00%> (-1.00%)

...e/dolphinscheduler/remote/NettyRemotingClient.java
50.00% <0.00%> (-2.78%)
9.00% <0.00%> (-2.00%)

...eduler/server/worker/runner/TaskExecuteThread.java
54.33% <0.00%> (-2.70%)
13.00% <0.00%> (ø%)

.../apache/dolphinscheduler/common/utils/OSUtils.java
44.57% <0.00%> (-2.41%)
23.00% <0.00%> (ø%)

...inscheduler/server/log/LoggerRequestProcessor.java
56.41% <0.00%> (-1.70%)
8.00% <0.00%> (ø%)

...pache/dolphinscheduler/common/utils/FileUtils.java
48.14% <0.00%> (-0.62%)
13.00% <0.00%> (ø%)

.../server/worker/processor/TaskExecuteProcessor.java
69.11% <0.00%> (ø)
7.00% <0.00%> (ø%)

...phinscheduler/server/worker/task/AbstractTask.java
16.66% <0.00%> (+5.41%)
4.00% <0.00%> (ø%)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 64dd9db...3bebbec. Read the comment docs.

+1

authors: chengshiwen codecov-io zhuangchong

repo: apache/incubator-dolphinscheduler


text:
[Improvement-4550][ui]Fix the problem of Uncaught (in promise) NavigationDuplicated: Avoided redundant navigation when clicking on the same route

issue #4550

Codecov Report

Merging #4551 (2289ba4) into dev (829fdb5) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev    #4551   +/-   ##
=========================================
  Coverage     44.73%   44.73%
+ Complexity     3340     3339    -1
=========================================
  Files           528      528
  Lines         22832    22832
  Branches       2669     2669
=========================================
  Hits          10214    10214
+ Misses        11698    11696    -2
- Partials        920      922    +2

Impacted Files
Coverage Δ
Complexity Δ

...er/master/dispatch/host/assign/RandomSelector.java
77.77% <0.00%> (-5.56%)
3.00% <0.00%> (-1.00%)

...dolphinscheduler/remote/future/ResponseFuture.java
81.35% <0.00%> (-1.70%)
18.00% <0.00%> (-1.00%)

...inscheduler/service/zk/CuratorZookeeperClient.java
65.85% <0.00%> (+4.87%)
8.00% <0.00%> (+1.00%)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 829fdb5...2289ba4. Read the comment docs.

Codecov Report

Merging #4551 (2289ba4) into dev (829fdb5) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev    #4551   +/-   ##
=========================================
  Coverage     44.73%   44.73%
+ Complexity     3340     3339    -1
=========================================
  Files           528      528
  Lines         22832    22832
  Branches       2669     2669
=========================================
  Hits          10214    10214
+ Misses        11698    11696    -2
- Partials        920      922    +2

Impacted Files
Coverage Δ
Complexity Δ

...er/master/dispatch/host/assign/RandomSelector.java
77.77% <0.00%> (-5.56%)
3.00% <0.00%> (-1.00%)

...dolphinscheduler/remote/future/ResponseFuture.java
81.35% <0.00%> (-1.70%)
18.00% <0.00%> (-1.00%)

...inscheduler/service/zk/CuratorZookeeperClient.java
65.85% <0.00%> (+4.87%)
8.00% <0.00%> (+1.00%)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 829fdb5...2289ba4. Read the comment docs.

LGTM.

LGTM.

authors: break60 codecov-io zhuangchong


text:
Analytic function issue

Describe the bug
palo在使用分析函数时必须有partition分组字段，但如果只是针对某一列排序，不想分组但话，就会被限制，所以我在表中加了一个常量作为分组partition使用，但是报错
测试sql如下：
select row_number() over(partition by dim order by id) rn,id from
(
select id,'test' dim from
(
select 1 id
union all
select 2 id
union all
select 3 id
) t
)t

返回 ERROR 1064 (HY000): Internal Error, maybe this is a bug, please contact with Palo RD.
但如果我将常量写在 union里面  ，可以通过执行，改写如下：
select row_number() over(partition by dim order by id) rn,id from
(

select 1 id ,'test' dim
union all
select 2 id  ,'test' dim
union all
select 3 id ,'test' dim

)t

可以得到正常返回
分析函数应该是不能支持常量分组。。
希望改进～

分析函数已经支持不带分组列的了~

repo: apache/incubator-doris


text:
Custom encoding when exporting query results

Is it possible to specify the encoding format when importing query results? Because the default UTF-8 format will appear Chinese garbled when it is opened by Excel, I need to perform a GBK operation by myself, thank you~

importing query results

Did you mean exporting the query result to file by using "SELECT INTO OUTFILE"?

authors: F-SLoong morningman


text:
[Optimize] Improve LRU cache's performance

Proposed changes
When LRUCache insert and evict a large number of entries, there are
frequently calls of HandleTable::remove(e->key, e->hash), it will
lookup the entry in the hash table. Now that we know the entry to
remove 'e', we can remove it directly from hash table's collision list
if it's a double linked list.
This patch refactor the collision list to double linked list, the simple
benchmark CacheTest.SimpleBenchmark shows that time cost reduced about
18% in my test environment.
Types of changes
What types of changes does your code introduce to Doris?
Put an x in the boxes that apply

[] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[] Documentation Update (if none of the other choices apply)
[] Code refactor (Modify the code structure, format the code, etc...)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[] I have create an issue on (Fix #ISSUE), and have described the bug/feature there in detail
[x] Compiling and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[] If this change need a document change, I have updated the document
[] Any dependent changes have been merged

Could you rebase the master code to see if unit test can run normally?

Could you rebase the master code to see if unit test can run normally?

Done


text:
Springboot1.5.10.RELEASE yml配置文件cunsumer配置无法自动注入问题

spring1.5.x版本，配置cunsumer yml资源文件，dubbo无法解析？
举例
dubbo配置
dubbo:
consumer:
check: false
上述配置，在springboot1.5.x版本无效。
换成springboot2.0.4和dubbo-spring-boot-starter 0.2.0得以解决，或手动注入ConsumerConfig Bean解决

You also can update Dubbo latest version

You also can update Dubbo latest version

是的，升级到springboot2.x和dubbo-spring-boot-starter0.2.0是可以解决的。
经过我们排查，怀疑可能是dubbo-spring-boot-starter0.1.0内引用的dubbo版本可能与springboot1.5.x版本兼容存在bug。

authors: mercyblitz uzdz


text:
树形结构，多个中间节点能否汇聚到同一个节点，在这个汇总节点又分散成多个节点？

Version
4.7.0
Steps to reproduce
"name": "flare",
    "children": [
        {
            "name": "data",
            "children": [
                {
                    "name": "b",
                    "children": [
                        {"name": "a", "value": 721}
                    ]
                },
                {
                    "name": "c",
                    "children": [
                        {"name": "a", "value": 721}
                    ]
                }
            ]
        }
    ]
};
var option = {
    tooltip: {
        trigger: 'item',
        triggerOn: 'mousemove'
    },
    series:[
        {
            type: 'tree',
            id: 0,
            name: 'tree1',
            data: [data],

            top: '10%',
            left: '8%',
            bottom: '22%',
            right: '20%',

            symbolSize: 7,

            edgeShape: 'curve',
            edgeForkPosition: '10%',
            initialTreeDepth: 3,

            lineStyle: {
                width: 2,
                curveness: 1
            },

            label: {
                backgroundColor: '#fff',
                position: 'left',
                verticalAlign: 'middle',
                align: 'right',
                borderColor: 'red',
                borderWidth: 1,
                borderRadius: 10,
                padding: 10
            },

            leaves: {
                label: {
                    position: 'right',
                    verticalAlign: 'middle',
                    align: 'left'
                }
            },

            expandAndCollapse: true,
            animationDuration: 550,
            animationDurationUpdate: 750
        }
    ]
};

What is expected?
a节点成为b,c节点的汇总节点
What is actually happening?
b,c节点各自生成了a节点

Could you provide a demo for the issue either with https://gallery.echartsjs.com/editor.html or https://jsfiddle.net/ovilia/n6xc4df3/.

https://gallery.echartsjs.com/editor.html?c=xygd9KCt9o&v=1

如果「汇聚」，从数据结构上来说，这个就不是「树」了，所以建议使用 graph 实现。

authors: Ovilia yufeng04 zhuanghongbin

repo: apache/incubator-echarts


text:
realtimeSort switch not in time

Version
5.0.0
Steps to reproduce
Example:
incubator-echarts-examples the next branch:
http://127.0.0.1:3002/en/editor.html?c=covid-america
Need to set the animationDurationUpdate as a long time.
Like:
var _timelineDuration = 5500;
var _barDurationUpdate = 5490;
var _axisDurationUpdate = 5000;

And drag the timeline to about 10/7/20. We will see that the bar of Massachusetts growth very fast and does not switch on time.

It depends on the setting on axis:
                    yAxis: [{
                        inverse: true,
                        type: 'category',
                        max: 9,
                        // Should be a small value:
                        animationDurationUpdate: 200,
                        animationEasingUpdate: 'linear'
                    }],

It depends on the setting on axis:
                    yAxis: [{
                        inverse: true,
                        type: 'category',
                        max: 9,
                        // Should be a small value:
                        animationDurationUpdate: 200,
                        animationEasingUpdate: 'linear'
                    }],


text:
[GOBBLIN-465] Add support for couchbase client cert auth

The requisite version bump eliminates support for couchbase v3.
Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[/] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-465] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-465

Description

[/] Here are some details about my PR, including screenshots (if applicable):
Bump API to 2.5.4. Exposes configuration values for performing cert auth. Skips SASL password auth if password is not provided.

Tests

[/] My PR adds the following unit tests OR does not need testing for this extremely good reason: this change is mostly exposing new config values - coverage & flow doesn't really change here, but I'm happy to add tests if they are needed to pass. I have smoke tested the new and old functionality with this build against CB5.

Commits

[/] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

@wwest4 looks ok. let me know when you have fixed the test cases.

@abti passing now after an update of CouchbaseMock

Thanks. Merged the changes.

repo: apache/incubator-gobblin


text:
HAWQ-344. When resource queue capacity is shrunk, deadlock detection …

When resource queue capacity is shrunk, deadlock detection maybe not triggered.

The fix looks good. +1

+1

authors: huor jiny2 linwen

repo: apache/incubator-hawq


text:
[HUDI-285] Implement HoodieStorageWriter based on actual file type

see jira: https://jira.apache.org/jira/projects/HUDI/issues/HUDI-285
CC @vinothchandar

LGTM/ merging!

authors: leesf vinothchandar

repo: apache/incubator-hudi


text:
[Bug][Manager] The method of batchSaveAll occurred error as the sink_name was null

What happened
The batchSaveAll() method submits the form interface exception, and there is no sink_name to fill in the form. But the database sets the field to be non-null

What you expected to happen
No Errors
How to reproduce
Create a hive sink
Environment
centos
InLong version
master
InLong Component
InLong Manager, InLong Dashboard
Are you willing to submit PR?

[ ] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Already resolved.

authors: Greedyu healchow

repo: apache/incubator-inlong


text:
[IOTDB-234] Refactor TsFile storage on HDFS

Refactor TsFile storage on HDFS codes:

Extract HDFS related files (HDFSFile, HDFSInput, HDFSOutput) into Hadoop module from TSFile module, so that TSFile module will not depend on Hadoop libs.
Use Java Reflection to get HDFS related files for factories used in TSFile module.

I think using reflection every time is too heavy and slow when all you want to do is to get a new Object. To put it simply, reflections should be used as less frequently as possible.
Here is my suggestion: use two factories (the LocalFactory and the HDFSFactory) instead of one, and initialize one of them using reflection according to the configuration at the system start-up. Thus the occurrence of reflections can be reduced to only 1.

Hi, many thanks for your useful suggestion!
In the new commit, I tried to reduce the occurrence of reflections to only 1 by initializing private static Class<?> clazz when constructing TSFileFactory. I think this also reached your main purpose, so I didn't use two factories... Do you think it is acceptable? > <

If you insist on this design, at least you should save the constructor.
And this test will show you that this is still slower compared with a direct call to new().
ReflectionTest.txt

If you insist on this design, at least you should save the constructor.
And this test will show you that this is still slower compared with a direct call to new().
ReflectionTest.txt

Thanks for the suggested design  @jt2594838 ! I have accepted it by using two factories (LocalFSFactory and HDFSFactory) with FSFactoryProducer to produce either one of them according to user config. I think this design is so much better for being less heavy and slow and being more scalable for future design.

repo: apache/incubator-iotdb


text:
[new-parser] Class literal not supported by expression parser

Parent issue

#5678

Failing tests

org.drools.traits.compiler.factmodel.traits.TraitTest#testIsAEvaluatorOnClassification

Notes
Rule code snippet
$t : org.drools.base.factmodel.traits.Thing( $c : core, this not isA t.x.E.class, this isA t.x.D.class )

Error output
20:22:51.158 [main] WARN  o.d.c.k.builder.impl.KieBuilderImpl.packageNameForFile:396 - File 'file0.drl' is in folder '' but declares package 't.x'. It is advised to have a correspondance between package and folder names.
### parse : ANTLR4_PARSER_ENABLED = true
line 1:19 no viable alternative at input '.class'
20:22:51.189 [main] ERROR o.d.c.k.b.impl.AbstractKieProject.buildKnowledgePackages:280 - Unable to build KieBaseModel:defaultKieBase
Unable to parse pattern expression:
[ERR 101] Line 1:19 no viable alternative at input '.class' : [Rule name='Rule 0 >> http://t/x#D']

java.lang.RuntimeException: [Message [id=1, kieBase=defaultKieBase, level=ERROR, path=file0.drl, line=27, column=0
   text=Unable to parse pattern expression:
[ERR 101] Line 1:19 no viable alternative at input '.class']]

	at org.kie.internal.utils.KieHelper.getKieContainer(KieHelper.java:127)
	at org.kie.internal.utils.KieHelper.build(KieHelper.java:89)
	at org.kie.internal.utils.KieHelper.build(KieHelper.java:84)
	at org.drools.traits.compiler.factmodel.traits.TraitTest.getSessionFromString(TraitTest.java:145)
	at org.drools.traits.compiler.factmodel.traits.TraitTest.testIsAEvaluatorOnClassification(TraitTest.java:2699)

/take

repo: apache/incubator-kie-drools


text:
[kie-issues#963] Remove all references to kogito-task-console and kogito-management-console

Closes https://github.com/apache/incubator-kie-issues/issues/963
This PR removes all references to kogito-task-console and kogito-management-console images, as they are being migrated to kie-tools [1].
It also fixes a small bug in the Makefile that prevented the make command from building all images.
[1] https://github.com/apache/incubator-kie-tools/pull/2226

Are you going to still use the same architecture (Cekit) when moving those to kie-tools?

No, we are using kie-tools tooling (image-builder [1]) to build the image now. Also, it's not a Java-based image anymore, we figured out it's enough to have Apache httpd serve the static webapp files and provide a way to change environment variables (to set the data index endpoint, for example).
If we're missing something or not meeting a requirement, let us know.
[1] https://github.com/apache/incubator-kie-tools/tree/main/packages/image-builder

PR job #137 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/137/display/redirect
See console log:

Console Logs
[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jit-runner: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-runtime-native: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-runtime-nativeBuild KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-s2i-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/137/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

@tiagobento count on me

@ricardozanini I'm not sure why ShellCheck is failing, do you have any ideas?

Try looking for this openBinaryFile method. Maybe it was a script used in the modules you're removing.

PR job #143 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/143/display/redirect
See console log:

Console Logs
[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-data-index-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-data-index-ephemeral seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jit-runner: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-jobs-service-allinone seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-builder seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-devmode seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/143/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

@ricardozanini Apparently, ShellCheck never worked (or I'm missing something), because Bash didn't work well with globstar. After I enabled it ShellCheck started printing a bunch of warnings and infos regarding the scripts.
I could add a -S error to the ShellCheck command so it only alerts for Error cases, but I can't fix the warnings and infos as I don't have the proper context of these scripts.

PR job #144 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/144/display/redirect
See console log:

Console Logs
[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-data-index-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-data-index-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jit-runner: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-builder seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-devmode seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/144/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

PR job #145 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/145/display/redirect
See console log:

Console Logs
[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-data-index-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-data-index-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jit-runner: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-builder seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-swf-devmode[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/145/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

@thiagoelg please remove the globstar, this action has been working on all the other PRs. I'll take a look after you revert it.

@thiagoelg I think I've found the problem, I'll send a PR later to solve this.

Fixed here: https://github.com/apache/incubator-kie-kogito-images/pull/1756
Once I get green, we can merge, rebase here and we should be good to go.

Awesome! Thanks @ricardozanini

PR job #147 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/147/display/redirect
See console log:

Console Logs
[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-data-index-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jit-runner: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-jobs-service-ephemeral seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-jobs-service-allinone seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-builder seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-devmode seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/147/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

PR job #153 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/153/display/redirect
See console log:

Console Logs
[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jit-runner: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-data-index-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-data-index-ephemeral seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-builder seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-devmode seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/153/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

The images build are broken, please see: https://github.com/apache/incubator-kie-kogito-runtimes/issues/3473

PR job #154 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/154/display/redirect
See console log:

Console Logs
[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-data-index-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-data-index-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-builder seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-swf-devmode[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/154/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

PR job #155 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/155/display/redirect
See console log:

Console Logs
[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jit-runner: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-data-index-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-data-index-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-data-index-ephemeral seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-jobs-service-allinone seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1753 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1753 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/155/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

PR job #159 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/159/display/redirect
See console log:

Console Logs
From https://github.com/thiagoelg/incubator-kie-kogito-images * branch              kie-issues-963 -> FETCH_HEADhint: You have divergent branches and need to specify how to reconcile them.hint: You can do so by running one of the following commands sometime beforehint: your next pull:hint: hint:   git config pull.rebase false  # merge (the default strategy)hint:   git config pull.rebase true   # rebasehint:   git config pull.ff only       # fast-forward onlyhint: hint: You can replace "git config" with "git config --global" to set a defaulthint: preference for all repositories. You can also pass --rebase, --no-rebase,hint: or --ff-only on the command line to override the configured default perhint: invocation.fatal: Need to specify how to reconcile divergent branches.[Pipeline] }[Pipeline] // withCredentials[Pipeline] echo        -------------------------------------------------------------        [ERROR] Can't merge source into Target. Please rebase PR branch.        -------------------------------------------------------------        Source: git://github.com/thiagoelg/incubator-kie-kogito-images kie-issues-963        Target: af98d962 Temporary removal of kogito-swf-{builder-,devmode} images from release pipelines (#1752)        ------------------------------------------------------------- [Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Validate CeKit Image and Modules descriptors)Stage "Validate CeKit Image and Modules descriptors" skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Build & Test Images)Stage "Build & Test Images" skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/159/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

authors: kie-ci3 ricardozanini thiagoelg

repo: apache/incubator-kie-kogito-images


text:
[incubator-kie-issues-1485] Reenable event test in ProcessTestEvents in kogito-apps

Closes: https://github.com/apache/incubator-kie-issues/issues/1485

PR job #2 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
build-chain build full_downstream  -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-runtimes -u https://github.com/apache/incubator-kie-kogito-runtimes/pull/3722 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3722/2/display/redirect
Test results:

PASSED: 3362
FAILED: 6

Those are the test failures:

org.jbpm.bpmn2.IntermediateEventTest.testTimerBoundaryEventInterrupting
expected: 2 but was: 1

org.jbpm.bpmn2.IntermediateEventTest.testIntermediateCatchEventTimerDuration
expected: 2 but was: 1

org.jbpm.bpmn2.IntermediateEventTest.testEventBasedSplit2
expected: 2 but was: 1

org.kie.kogito.quarkus.it.openapi.client.ApiWithSecurityContextIT.verifyAuthHeadersOpenApi3_0NoAuth
java.util.concurrent.CompletionException: java.lang.RuntimeException: Unable to start Quarkus test resource class org.kie.kogito.quarkus.it.openapi.client.mocks.AuthSecurityMockService

org.kie.kogito.integrationtests.quarkus.TaskIT.testUpdateTaskInfo
1 expectation failed.Expected status code <200> but was <404>.

org.kie.kogito.integrationtests.springboot.TaskTest.testUpdateTaskInfo
1 expectation failed.Expected status code <200> but was <404>.

PR job #3 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
build-chain build full_downstream  -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-runtimes -u https://github.com/apache/incubator-kie-kogito-runtimes/pull/3722 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3722/3/display/redirect
Test results:

PASSED: 3376
FAILED: 5

Those are the test failures:

org.jbpm.bpmn2.IntermediateEventTest.testTimerBoundaryEventInterrupting
expected: 2 but was: 1

org.jbpm.bpmn2.IntermediateEventTest.testIntermediateCatchEventTimerDuration
expected: 2 but was: 1

org.jbpm.bpmn2.IntermediateEventTest.testEventBasedSplit2
expected: 2 but was: 1

org.kie.kogito.integrationtests.quarkus.TaskIT.testUpdateTaskInfo
1 expectation failed.Expected status code <200> but was <404>.

org.kie.kogito.integrationtests.springboot.TaskTest.testUpdateTaskInfo
1 expectation failed.Expected status code <200> but was <404>.

PR job #4 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
build-chain build full_downstream  -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-runtimes -u https://github.com/apache/incubator-kie-kogito-runtimes/pull/3722 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3722/4/display/redirect
Test results:

PASSED: 3378
FAILED: 3

Those are the test failures:

org.jbpm.bpmn2.IntermediateEventTest.testTimerBoundaryEventInterrupting
expected: 2 but was: 1

org.jbpm.bpmn2.IntermediateEventTest.testIntermediateCatchEventTimerDuration
expected: 2 but was: 1

org.jbpm.bpmn2.IntermediateEventTest.testEventBasedSplit2
expected: 2 but was: 1

PR job #5 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
build-chain build full_downstream  -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-runtimes -u https://github.com/apache/incubator-kie-kogito-runtimes/pull/3722 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3722/5/display/redirect
Test results:

PASSED: 2664
FAILED: 3

Those are the test failures:

org.jbpm.bpmn2.IntermediateEventTest.testTimerBoundaryEventInterrupting
expected: 2 but was: 1

org.jbpm.bpmn2.IntermediateEventTest.testIntermediateCatchEventTimerDuration
expected: 2 but was: 1

org.jbpm.bpmn2.IntermediateEventTest.testEventBasedSplit2
expected: 2 but was: 1

PR job #6 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
build-chain build full_downstream  -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-runtimes -u https://github.com/apache/incubator-kie-kogito-runtimes/pull/3722 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3722/6/display/redirect
Test results:

PASSED: 2155
FAILED: 3

Those are the test failures:

org.jbpm.bpmn2.IntermediateEventTest.testTimerBoundaryEventInterrupting
expected: 2 but was: 1

org.jbpm.bpmn2.IntermediateEventTest.testIntermediateCatchEventTimerDuration
expected: 2 but was: 1

org.jbpm.bpmn2.IntermediateEventTest.testEventBasedSplit2
expected: 2 but was: 1

PR job #7 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
build-chain build full_downstream  -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-runtimes -u https://github.com/apache/incubator-kie-kogito-runtimes/pull/3722 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3722/7/display/redirect
Test results:

PASSED: 3380
FAILED: 3

Those are the test failures:

org.jbpm.bpmn2.IntermediateEventTest.testTimerBoundaryEventInterrupting
expected: 2 but was: 1

org.jbpm.bpmn2.IntermediateEventTest.testIntermediateCatchEventTimerDuration
expected: 2 but was: 1

org.jbpm.bpmn2.IntermediateEventTest.testEventBasedSplit2
expected: 2 but was: 1

repo: apache/incubator-kie-kogito-runtimes


text:
Add an issue translator to the website repository

This PR is to solve the issue #381

repo: apache/incubator-linkis-website


text:
About DSS and linkis, in addition to supporting deployment user login, can you configure other user login?

Search before asking

[X] I searched the issues and found no similar issues.

Linkis Component
linkis-commons
What happened + What you expected to happen
About DSS and linkis, in addition to supporting deployment user login, can you configure other user login?
Relevent platform
。
Reproduction script
。
Anything else
This question comes from the QA documentation of the Linkis community
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Solution:
Certainly. Users are deployed for convenience only. Linkis gateway supports access by configuring LDAP service and SSO service. There is no user verification system. For example, to enable LDAP service access, you only need to configure linkis in the configuration file of linkis gateway Properties your LDAP server is configured as follows:
wds.linkis.ldap.proxy.url=ldap://127.0.0.1:389/#您的LDAP服务URL
wds.linkis.ldap.proxy.baseDN=dc=webank，dc=com#您的LDAP服务的配置
If the user needs to perform tasks, he / she also needs to establish a user with the corresponding user name on the LIX server. If it is a standard version, the user needs to be able to perform spark and hive tasks, and needs to establish a corresponding user name directory in the local workspace and HDFS directory / TMP / links.

repo: apache/incubator-linkis


text:
All the tests in tools/coreml package are failing

Note: Providing complete information in the most concise form is the best way to get help. This issue template serves as the checklist for essential information to most of the technical issues and bug reports. For non-technical issues and feature requests, feel free to present the information in what you believe is the best form.
For Q & A and discussion, please start a discussion thread at https://discuss.mxnet.io
Description
Currently all the tests for mxnet-to-coreml converter under the tools/coreml package are failing due to lack of maintenance. We need to update them to keep up with the latest release
Environment info (Required)
----------Python Info----------
('Version      :', '2.7.15')
('Compiler     :', 'GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.39.2)')
('Build        :', ('default', 'May  1 2018 16:44:37'))
('Arch         :', ('64bit', ''))
------------Pip Info-----------
('Version      :', '10.0.1')
('Directory    :', '/Users/lnyuan/.virtualenvs/mxnet2/lib/python2.7/site-packages/pip')
----------MXNet Info-----------
('Version      :', '1.3.0')
('Directory    :', '/Users/lnyuan/work/incubator-mxnet/python/mxnet')
Hashtag not found. Not installed from pre-built package.
----------System Info----------
('Platform     :', 'Darwin-16.7.0-x86_64-i386-64bit')
('system       :', 'Darwin')
('node         :', '88e9fe759c49.ant.amazon.com')
('release      :', '16.7.0')
('version      :', 'Darwin Kernel Version 16.7.0: Thu Jun 21 20:07:39 PDT 2018; root:xnu-3789.73.14~1/RELEASE_X86_64')
----------Hardware Info----------
('machine      :', 'x86_64')
('processor    :', 'i386')
machdep.cpu.extfeatures: SYSCALL XD 1GBPAGE EM64T LAHF LZCNT PREFETCHW RDTSCP TSCI
machdep.cpu.leaf7_features: SMEP ERMS RDWRFSGS TSC_THREAD_OFFSET BMI1 AVX2 BMI2 INVPCID SMAP RDSEED ADX IPT SGX FPU_CSDS MPX CLFSOPT
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX EST TM2 SSSE3 FMA CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES PCID XSAVE OSXSAVE SEGLIM64 TSCTMR AVX1.0 RDRAND F16C
machdep.cpu.brand_string: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
----------Network Test----------
Setting timeout: 10
Timing for MXNet: https://github.com/apache/incubator-mxnet, DNS: 0.0121 sec, LOAD: 0.6747 sec.
Timing for PYPI: https://pypi.python.org/pypi/pip, DNS: 0.0117 sec, LOAD: 0.4044 sec.
Timing for FashionMNIST: https://apache-mxnet.s3-accelerate.dualstack.amazonaws.com/gluon/dataset/fashion-mnist/train-labels-idx1-ubyte.gz, DNS: 0.0217 sec, LOAD: 0.1044 sec.
Timing for Conda: https://repo.continuum.io/pkgs/free/, DNS: 0.0195 sec, LOAD: 0.0761 sec.
Timing for Gluon Tutorial(en): http://gluon.mxnet.io, DNS: 0.0173 sec, LOAD: 0.2269 sec.
Timing for Gluon Tutorial(cn): https://zh.gluon.ai, DNS: 0.0216 sec, LOAD: 0.1687 sec.

Package used (Python/R/Scala/Julia):
Python
Build info (Required if built from source)
Compiler (gcc/clang/mingw/visual studio):
g++
MXNet commit hash:
e4134c8270c1b944278b1e0331313074b1d97cc0
Error Message:
======================================================================
ERROR: test_pred_vgg16 (test_mxnet_models.ModelsTest)
Traceback (most recent call last):
File "/Users/lnyuan/work/mxnet-master/tools/coreml/test/test_mxnet_models.py", line 141, in test_pred_vgg16
"http://data.mxnet.io/models/imagenet/vgg/vgg16-0000.params"])
File "/Users/lnyuan/work/mxnet-master/tools/coreml/test/test_mxnet_models.py", line 116, in _test_model
coreml_pred = coreml_model.predict(_mxnet_remove_batch(input_data)).values()[0].flatten()
File "/Users/lnyuan/.virtualenvs/mxnet2/lib/python2.7/site-packages/coremltools/models/model.py", line 267, in predict
raise Exception('Model prediction is only supported on macOS version 10.13 or later.')
Exception: Model prediction is only supported on macOS version 10.13 or later.
Minimum reproducible example
All the tests under tools/coreml/test
Steps to reproduce

cd tools/coreml/test
nosetests -v .

What have you tried to solve it?

@sandeep-krishnamurthy Please help to label this issue Test

Created a JIRA ticket to track this issue. I will work on it.

As displayed in the error message "Exception: Model prediction is only supported on macOS version 10.13 or later.", the tests convert MXNet models into CoreML models and use CoreML to predict. This prediction is not supported on Mac OS 10.12.
I have disabled the prediction and tests will pass.

@apeforest any update?

@lupesko I have created a simple test that can run on Mac OS 10.12. The PR is https://github.com/apache/incubator-mxnet/pull/11952
Since our CI does not include Mac OS platform, I am working with @marcoabreu to add this to the manual test suite.

@sandeep-krishnamurthy @nswamy Please close this issue.

authors: apeforest lupesko

repo: apache/incubator-mxnet


text:
MXNet for Scala 2.12 and 2.13

The Scala language binding is badly needed for high performance training/inference around Apache Spark. The current Scala language binding is for 2.11 and the MXNet version is 1.5.1.
Please add 2.12 and 2.13 packages for 1.6.0 and up. TF has eaplatanios/tensorflow_scala, which while being a non-official release, has a lot of traction and builds for both 2.12 and 2.13.

I would like to contribute if anyone can give me a few pointers of what is needed to have this happen.

@cosmincatalin have you tried building from source https://github.com/apache/incubator-mxnet/tree/v1.x/scala-package#build-from-source?
Are you interested in the CPU or GPU packages? There are some licensing issues with the binaries at org.apache.mxnet (GPU packages may be subject to CUDA EULA and thus incompatible with Apache 2 License; CPU packages redistribute libquadmath.so which is GPL and thus incompatible with Apache 2 License). The latter can be easily fixed by not putting libquadmath.so into the jar. So if you are interested in having the CPU packages for 1.6 (and 1.7 release) and Scala 2.12 and 2.13, we can discuss more about how to make it happen. The first step is to verify the build-from-source works locally for 2.12 and 2.13.
For the GPU packages, it depends on NVidia. They have internal discussions considering if they'd be able to make their EULA compatible with Apache License 2.
You can also refer to https://issues.apache.org/jira/browse/INFRA-20442 for more information.

I've tinkered a little with building from source, but wasn't very successful, I guess I need to focus on it more. To answer your second question, yes, I am interested specifically in the CPU packages.

hey, I'm interested on this, count me in if you want help @cosmincatalin

hey @leezu , I got to compile the project using make. But when run mvn compile on the Scala folder I get this error:
[INFO] Compiling 2 source files to /home/gustavo/git/apache-mxnet-src-1.6.0-incubating/scala-package/init/target/classes at 1597332091507
[INFO] compiler plugin: BasicArtifact(org.scalamacros,paradise_2.11.8,2.1.0,null)
[ERROR] error: scala.reflect.internal.MissingRequirementError: object java.lang.Object in compiler mirror not found.

then I realized that the pom.xml is configured like this:
<java.version>1.7</java.version>
I have Java 11 installed and that may be the source of the error above, would that be correct?
Also, is there any reason to set the java.version to 1.7?

@tavoaqp I think that's right. cc @lanking520 who's helping with a build instruction on this.

I have some instruction in this repository https://github.com/cosmincatalin/mxnet-compiler. I use a custom made Docker image to compile a linux based MXNet library and then I compile the Scala 2.11 binding. The image has Java 8 baked in.
Roughly the same procedure can be used to generate 2.12 bindings, by modifying some Maven configs and libraries. But I don't know how to generate both 2.11, 2.12 and 2.13 bindings.

instead of build from source, you can get the pip wheel for mxnet and put the so in the lib folder.
I would suggest start with mvn verify to see if it can run successfully. I have been trying to upgrade to 2.12 last year but failed due to some dependencies mismatch issue. If you can get over them it could be ok.
Another beast in the code is the code generation system. I am not sure if 2.12 or 2.13 would have consistent support on quasiquote to get it work, but worth for a try. Finally is the Spark support, you may need to change some code to get Spark fully support there.

thanks @lanking520 ! seems like a lot of work :smile: , @cosmincatalin I will try your setup!

@lanking520 Yeah, that works too. I tried with so's from the wheel, and that worked. That being said, 2.12 and 2.13 are a must since a lot Scala code is now on 2.12 at least. Spark is now on 2.12. It would have been nice if the whole setup was based on sbt rather than maven

hey @lanking520 I got some progress: I switched to Scala 2.12.12 and fixed the dependencies. Everything compiles (with some warnings though) but when it comes to compile the examples project I get this:
[INFO] --- scala-maven-plugin:3.4.4:doc-jar (compile) @ mxnet-examples ---
/home/gustavo/git/incubator-mxnet/scala-package/examples/src/main/java/org/apache/mxnetexamples/javaapi/benchmark/ObjectDetectionBenchmark.java:35: error: not found: type NDArray$
    private NDArray$ NDArray = NDArray$.MODULE$;
            ^
/home/gustavo/git/incubator-mxnet/scala-package/examples/src/main/java/org/apache/mxnetexamples/javaapi/infer/bert/BertQA.java:52: error: not found: type NDArray$
    private static NDArray$ NDArray = NDArray$.MODULE$;
                   ^
/home/gustavo/git/incubator-mxnet/scala-package/examples/src/main/java/org/apache/mxnetexamples/javaapi/infer/predictor/PredictorExample.java:48: error: not found: type NDArray$
    private static NDArray$ NDArray = NDArray$.MODULE$;

Any pointers?
Thanks!

Yeah, I've stumbled on this one as well. Come to think of it, maybe I haven't actually been able to generate bindings for 2.12 🤔

hey @lanking520 I got some progress: I switched to Scala 2.12.12 and fixed the dependencies. Everything compiles (with some warnings though) but when it comes to compile the examples project I get this:
[INFO] --- scala-maven-plugin:3.4.4:doc-jar (compile) @ mxnet-examples ---
/home/gustavo/git/incubator-mxnet/scala-package/examples/src/main/java/org/apache/mxnetexamples/javaapi/benchmark/ObjectDetectionBenchmark.java:35: error: not found: type NDArray$
    private NDArray$ NDArray = NDArray$.MODULE$;
            ^
/home/gustavo/git/incubator-mxnet/scala-package/examples/src/main/java/org/apache/mxnetexamples/javaapi/infer/bert/BertQA.java:52: error: not found: type NDArray$
    private static NDArray$ NDArray = NDArray$.MODULE$;
                   ^
/home/gustavo/git/incubator-mxnet/scala-package/examples/src/main/java/org/apache/mxnetexamples/javaapi/infer/predictor/PredictorExample.java:48: error: not found: type NDArray$
    private static NDArray$ NDArray = NDArray$.MODULE$;

Any pointers?
Thanks!

Acutally this is used for Java to access the NDArray class.

So, is there a way to get pass the issue with the NDArray?

I haven't had spare time to see this! Still not sure why is this happening, I believe that the POM project is not generating the Java byte code in the correct path.

October 2021 - is this project release stuck at Scala 2.11 (anno 2014)? I didn't expect it to work with Scala 3, but not even 2.13, come on? Any pointers to othe machine learning frameworks that work with contemporary Scala versions?

Does anyone know if mxnet still has any scala or java bindings update on the roadmap? Or is it only python at this point?

authors: Sciss cosmincatalin lanking520 leezu markthor szha tavoaqp


text:
[Discussion] FP16 Support

Ideally, we have everything to support FP16,
While trying to train Inception-7, I find out it is necessary to support FP16 now, as it is so memory consuming.
Let's set a milestone.

The question is do we want it as a global constant or a per tensor variable. The former requires rebuilding to switch and the later requires major refactor of frontend code, since it's currently const there.

we want a per tensor type aware thing, so fp16 can be part of the graph

Then we need to discuss how to handle this in python and cudnn. Currently mx_float is a const.
Also do we want to alway convert or let mshadow support different source/target type?

mshadow is typed, and mshadow accept DataType as flag, we can use mshadow's cast operator to cast between types. There is a type flag in TBlob already, need a patch to support dtype in NDArray

Does cudnn support mixed type operations?

Unlikely, but we can do explicit cast op
On Sat, Dec 5, 2015 at 2:03 PM Eric Junyuan Xie notifications@github.com
wrote:

Does cudnn support mixed type operations?
—
Reply to this email directly or view it on GitHub
https://github.com/dmlc/mxnet/issues/833#issuecomment-162251184.

Should data type be the property of symbol?

Hmm, I guess we can support some kinda of inference, and make datatype one loose property like device

The quickest way is to first make low level operator type aware, and support cast, so things can be added gradually, as opposed to need to support everything

I think we can make mshadow primitives support different input/output type. Then later we can add type inference to minimize casting.

mshadow primitive already support mixed type, like
Tensor<xpu,float> a;
Tensor<xpu, fp16> b, out;
out = cast<fp16>(a) + b;

The last line generate one kernel that takes fp16 and float input and add to

can we make the cast implicit
On Dec 5, 2015 4:15 PM, "Tianqi Chen" notifications@github.com wrote:

mshadow primitive already support mixed type, like
Tensor<xpu,float> a;
Tensor<xpu, fp16> b, out;
out = cast(a) + b;
The last line generate one kernel that takes fp16 and float input and add
to
—
Reply to this email directly or view it on GitHub
https://github.com/dmlc/mxnet/issues/833#issuecomment-162258823.

currently no due to type inference cost, but I guess it works for most of case we need

What do you mean by type inference cost? Can it be resolved at compile time?

Yes, it can be, except we need to cost some engineering to write the type inference code, we can do it gradually, first by explicit cast, then add implicit inference

Ok. Let's try to do this properly so we can easily support all types. I think TF also supports int. should be useful for softmax and nlp models.

https://github.com/dmlc/mxnet/pull/1675

@tqchen How can I use cast<> in my code? I cannot find a definition of cast in mshadow.

authors: KiddoZhu antinucleon futurely piiswrong tqchen


text:
[Clojure] Add resource scope to clojure package

Description
Ports ResourceScope from the Scala package and introduces using macro to automatically close any resource in the enclosing forms.
https://github.com/apache/incubator-mxnet/issues/13442
and see https://cwiki.apache.org/confluence/display/MXNET/JVM+Memory+Management for more context
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[X] Changes are complete (i.e. I finished coding on this PR)
[X] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[X] Code is well-documented:
[X] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes
Also added the resource scope to the imclassification example.
New runs to the example do not show any warnings of memory leaks of this nature:
WARN  org.apache.mxnet.WarnIfNotDisposed: LEAK: [one-time warning] ...

I think all the feedback is addressed. Feel free to take another look. If there are no more changes needed, I will merge 😸


text:
Fixed Install page history broken

Description
Fixed issue https://github.com/apache/incubator-mxnet/issues/14583. On get started page when navigating back in session history through browser back button, the "Installing MXNet" options block does not update while the url was cut shorter.
After the fix, when navigating back session history, the install options selection will be updated to previous state.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)

Changes

[x] Update install options section when navigating back history
[x] Avoid install options section buttons' default css style, the blue outline, when losing focus during selection update

Comments
Preview: http://ec2-52-38-4-82.us-west-2.compute.amazonaws.com/

@mxnet-label-bot add [Website]

@mxnet-label-bot add [pr-awaiting-review]

Thanks @ys2843 for your contributions! Welcome to MXNet community :-)

Congratulations on your first PR @ys2843! Excellent work :)

All test cases passed, it should be all good to merge. Thanks @zachgk


text:
Add param 'num_filter' for 'BaseConvRNNCell'.

Description
I think it is improper to use the 'num_hidden' as 'num_filter'. So I add the parameter 'num_filter' for  'BaseConvRNNCell' and its derived classes in rnn_cell.py.
Changes

Add the parameter 'num_filter'.
Change the 'num_filter' in 'Convolution' from 'self._num_hiddenself._num_gates' to 'self._num_filterself._num_gates'.

@dsqx71

I think num_hidden is fine. Also this breaks backward compatibility

authors: ceiba-w piiswrong szha


text:
[NETBEANS-54] adding schema2beans test data to Rat exceptions

[NETBEANS-54] adding and simplifying Rat exclusions

OK, these updates are modifications to the existing Rat exclusions, and a simplification of part of it, only the build.xml is impacted by this commit, and only the Rat exclusion section in there. These changes should bring the problematic files down to about 500. Merging this now.

repo: apache/incubator-netbeans


text:
arch/xtensa: Replace the xcp context with stack context to improve context switching

Summary
Apply the same ideas from:

https://github.com/apache/incubator-nuttx/pull/5645
https://github.com/apache/incubator-nuttx/pull/5731

Impact
Xtensa chips.
Testing
ESP32, ESP32-S2 and ESP32-S3.

@zhuyanlin111 could you review the change?

repo: apache/incubator-nuttx


text:
feat(services/redb): support redb service

introduce new redb service  https://github.com/apache/incubator-opendal/issues/2524

Sorry for the CI failure, fixed in https://github.com/apache/incubator-opendal/pull/2534

@Xuanwo https://github.com/apache/incubator-opendal/actions/runs/5370716502/jobs/9743000170?pr=2526 and this error, it seems we are using old MSRV version.

@Xuanwo https://github.com/apache/incubator-opendal/actions/runs/5370716502/jobs/9743000170?pr=2526 and this error, it seems we are using old MSRV version.

Please remove redb from default feature. It's required that opendal eith default feature must work on MSRV.

waiting for https://github.com/apache/incubator-opendal/pull/2534 merged and rebase for fix CI failed.

authors: Xuanwo oowl

repo: apache/incubator-opendal