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?

For context variables provided by an alert, to be used in action parameters, usually the values of the variables are strings or other primitive values. However, they can be objects as well. The metrics alert makes use of this for it's grouping (I believe).

When a customer uses these object-valued variables directly as a mustache "variable", mustache will render these values as the following,

Describe the bug
When a user signs in using Auth.signIn() the "signIn" event is registered multiple times in the Hub listener

To Reproduce

1. Add a log inside the "signIn" event in the Hub.listener callback
2. Open devtools
3. Sign in using Auth.signIn()
4. Notice there is at least 4 or more logs and the same amount of network calls

Expected behavior
The sign in event shou

The current version of the HANS dataset is missing the additional information provided for each example, including the sentence parses, heuristic and subcase.

I'd like to use a client certificate with sitespeed.io (with the Chrome backend). I've searched the documentation, but I could not find any explanation on how to do this.

Note that the Chrome browser does support the use the certificates installed in the host operating system (e.g. Windows or macOS).

Request: Please document how to use client certificates (e.g. P12) in the any browser (or at

🚀 Feature

What do you think to be able to terminate a run after a time of computation ? This would be useful for using ignite on runtime environments like Colab or Kaggle which limit the time of session.

An implementation of such handler is available here and can be reused : https://github.com/Minyus/pipelinex/blob/master/src/pipelinex/ops/ignite/handlers/time_limit.py

It misses documentatio

Hi

Im getting an error while comparing with a branch (using -b option) or running in CI mode (using -m option). Backtrace attached below.

Traceback (most recent call last):
	23: from /home/atrivedi/.rbenv/versions/2.5.5/bin/rubycritic:23:in `<main>'
	22: from /home/atrivedi/.rbe

This is a FEATURE REQUEST.

Please add support for kube_state_metrics_build_info as part of the metrics exposed on telemetry port 8081.
kube_state_metrics_build_info shall include the version of the kube-state-metrics.
Most Prometheus exporters are currently supporting such metric.

https://github.com/collectd/collectd/blob/0b2796dfa3b763ed10194ccd66b39b1e056da9b9/src/mysql.c#L772

Hi,
As I saw in the source for the mysql plugin, the collector specifically ignors the Prepared_stmt_count variable.
I would like to have that in the output for collectd as well.
Is it possible to enable this key in the collectd mysql collector?

Unfortunately my C skills are pretty near zer

Issue Description

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

Type: feature request

Describe what feature

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

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

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

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

---

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