Summary

It would be great to add some screenshots of the current PagerDuty plugin to its README here:

https://github.com/backstage/backstage/blob/master/plugins/pagerduty/RE

Current behavior

Right now, the connection string to Azure can be passed as a string at initialization or read AZURE_STORAGE_CONNECTION_STRING from the environment.

The connection string property is not serialized with the storage object. The only way to get this to work is to have AZURE_STORAGE_CONNECTION_STRING available when the flow is retrieved from storage. For most agent types, t

What is the problem this feature would solve? Please describe.

In CI and/or scripting it is often useful for commands that create resources to block until they become ready. For example, both doctl compute droplet create and doctl kubernetes cluster create have --wait flags that block until the resource has been successfully created. Recently, the doctl apps create-deployment comman

🐛 Bug Report

AdditiveValueMetric assumes that the metric value can be converted to float / NumPy array. But in reality, there are many cases when it is much faster and easier to calculate metrics on GPU us

A number of modules, and scripts in the test suite start with

#!/usr/bin/env python

In general it is better to use

#!/usr/bin/env python

because that allows execution inside a virtualenv, or when python is installed elsewhere, e.g. /usr/loca/bin/python.

There may be cases in which we really do want to hard code the path - for instance testing detection/selection of `

https://www.usenix.org/conference/opml19/program

Prepare to read papers