What would you like to be added:

Currently Grafana has ability to provision Data Sources, Dashboards and other stuff. But unfortunately, it's not possible (or I haven't found?!) how to provision Data Links for ElasticSearch data source. I mean this part which I'm trying to migrate to provisioned setup and I just can't

@kezhenxu94 I think with using graceful shutting down, we need a simple e2e to verify whether OAP and UI could be shut down successfully. Because, once we have one unexpected thread, the shutdown wouldn't work.

Originally posted by @wu-sheng in apache/skywalking#7020 (comment)

As per elastic/kibana#99462 (reply in thread), IIndexPattern is deprecated (and possibly IFieldType too?).

If an @deprecated flag is added into the description with an @removeBy we can start getting folks off of it and a path for removal. Usage would also show up in the deprecated API list [here](https://elasticdocstest.netlify.app/kibana-dev-docs/dep

If I set all the prefixes (globalPrefix, prfixTimer, etc.) to "", what kind of ramifications will that have on the server side if any? Will all the timers, gauges, counters be calculated as normal or will see if any side effects?

Hi
Wikiann dataset needs to have "spans" columns, which is necessary to be able to use this dataset, but this column is missing from huggingface datasets, could you please have a look? thank you @lhoestq

Before opening, please confirm:

• I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
• I have searched for duplicate or closed issues.
• I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/master/CONTR

For the moment there is no ability to use IAM instance profile for access to s3 bucket as it is not described in documentation
Could yo

🚀 Feature

Related to the discussion from here: pytorch/ignite#1476 (comment)

We would like to ensure that all our supported experiment tracking loggers handle metric types in the same way as here:

For Neptune (correct):
https://github.com/pytorch/ignite/blob/9230a7319047b37ce19d956e024fa1b86030c30a/ignite/contrib/handlers/neptune_logger.py#L344-L

Describe the bug
When joining to tables on the same column name SQL error happens

To Reproduce

create table l as
( select x from long_sequence(100) )

create table r as
( select x + 50 from long_sequence(100) )

select x
from l join r on l.x = r.x

and got back
Invalid column: r.x

Expected behavior
Tables should be joined, no SQL syntax error

**Enviro

提问题？
请把问题现象、相关日志、初步排查结果写清楚，即提供尽量多的线索，这样方便我们定位问题。

提建议？
请写明白建议原因，即为何有此建议。

提修复PR？
请说明为何做此修改，需要做好测试。

提Feature？
建议先将想法提出，不着急写代码，与社区同道沟通，大家觉得OK再做代码实现

---

另外，我们是在做开源软件，不是服务于您的企业，做您的乙方，您一分钱没付，就不要颐指气使了，认同我们这个社区，则参与进来，不认同，就不参与，谢谢理解

Issue Description

是否有计划用actions 完全取代 TravisCI
感觉actions 速度上比 TravisCI更好点 ，另外也是github原生的。

Type: feature request

Describe what feature