apache

The Mixed Time-Series chart type allows for configuring the title of the primary and the secondary y-axis.
However, while only the title of the primary axis is shown next to the axis, the title of the secondary one is placed at the upper end of the axis where it gets hidden by bar values and zoom controls.

How to reproduce the bug

1. Create a mixed time-series chart
2. Configure axi

Description

As an engineer when I am deleting multiple variables in the Airflow UI I wish to be sure about which variables I am deleting. currently the UI only asks Are you sure you want to delete selected records?, if I have a lot of records it is impossible to see the "selected records" when deleting them.

Use case/motivation

Prevent deletion of important / unintended Airflow Varia

As discussed on CZO, there are currently several ways to mute a topic. We should remove this redundant option from the message three-dot menu.

Reasons to do so:

• It's a topic action, not a message action.
• There are lots of other, more natural ways to do it.
• The message three-dot menu is g

The typescript runtime was recently added to openwhisk but we do not yet have docs for the runtime and it is missing from runtimes.json.

We need a doc like https://github.com/apache/incubator-openwhisk/blob/master/docs/actions-nodejs.md for typescript functions.

Adding the runtime to the runtime manifest can be done per https://github.com/apache/openwhisk/blob/master/docs/actions-new.md#the-

Proposed changes

Doris's Routine Load realizes the import of data from Kafka to Doris, and make a feature of real-time synchronization of data from Pulsar to Doris based on Pulsar IO.

1. The custom abstract class DorisAbstractSink implements the interface org.apache.pulsar.io.core.Sink.

2. The DorisGenericRecordSink class inherits the abstract class DorisAbstractSink, and the speci

Search before asking

• I had searched in the feature and found no similar feature requirement.

Description

I found out we do not have a search component for our documents. I think we should add this component to our document for better search

Usage Scenario

No response

Related is

based on apache/iceberg#3104 (comment)

I did not have a good way to distinguish what exception to use for what case, the definition provided by Ryan was clear. I think we should add that in the javadoc of ValidationException class about when to use it and when to use Preconditions to throw illegal argument exception.

This will give more clarity to both

We should have a metric that increments when a proxy loop is detected. Likely here:

https://github.com/apache/trafficserver/blob/f36cf6a6e5b1372916170541bec681a80b34c46f/proxy/http/HttpTransact.cc#L6577