I am referring to an issue, which is very similar to backstage/backstage#5577. It is related to the scaffolder-backend plugin.

In our company, we are running a self-hosted Bitbucket repository. It can be accessed via https://code.mycompany.com/bitbucket/. Therefore the base path for APIs is at https://code.mycompany.com/bitbucket/rest/api/1.0/ (note the /bitbucket/ in

Opened from the Prefect Public Slack Community

elliot: Hey folks is anyone else getting a deprecation warning on marshmallow? Something like:

...
/home/rof/.pyenv/versions/3.9.1/lib/python3.9/site-packages/marshmallow/fields.py:198
/home/rof/.pyenv/versions/3.9.1/lib/python3.9/site-packages/marshmallow/fields.py:198: RemovedInMarshmallow4Warning: Passing fi

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

🚀 Feature Request

Let's add official support for all sklearn metrics to our Metric API.

Motivation

Sklearn

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