What challenge are you facing?

The help text for fly order-pipelines:

Usage:
  fly [OPTIONS] order-pipelines [order-pipelines-OPTIONS]

Application Options:
  -t, --target=              Concourse target name
  -v, --version              Print the version of Fly and exit
      --verbose              Print API requests and responses
      --print-table-headers  Print table heade

Feature motivation

Azure storage client is backward incompatible, there's an issue #757 for upgrading the azure connection to the latest client. The new version has an async interface that can be leveraged for the streams module, at least for downloads.

N.B. This is likely a 3~4h work and not a pressing need, so just putting this in the backlog.

Feature implementation

There's a

Problem
Some of our transformers & estimators are not thoroughly tested or not tested at all.

Solution
Use OpTransformerSpec and OpEstimatorSpec base test specs to provide tests for all existing transformers & estimators.

From alan-turing-institute/MLJBase.jl#68:

This doesn't work:

@mlj_model mutable struct Bar
    a::Int = -1::(_ > -2)
end

But this does:

@mlj_model mutable struct Bar
    a::Int = (-)(1)::(_ > -2)
end

This needs to be documented in MLJ/docs/src/adding_models_for_general_use and MLJ/docs/src/quick_start_guide_to_adding_models

Describe the bug
Github Gateway pod unable to create webhook because of trailing whitespace that gets appended to the webhook token in the header
Is this a bug? YES
Is there a deployment method to prevent it?

Environment (please complete the following information):

OS: macOS Mojave 10.14.4
minikube: v1.0.1
Helm: v2.14.0
argo workflow: v2.2.1
Argo-events: v0.9.2

In each of the top level commands - az boards, az pipelines, az repos, az artifacts and az devops, we include the line indicating that this command is a part of azure-devops extension. In addition to this, we need to include the link out to the documentation - https://docs.microsoft.com/en-us/azure/devops/cli/?view=azure-devops as well.

Azure/azure-cli-extensions#1454

Besides splice(2) and tee(2), Linux also offers copy_file_range(2), opening the door for potential file-to-file copying optimizations, at the file system level. Perhaps we should look into supporting this. It doesn't look very difficult, at first sight.

Custom styles can be added in Monaco Editor already.
It would be nice to be able to set custom style as query parameter, like rawConfig.

There should be an option to have drone cli provide machine parsable output, especially for commands like 'drone secret ls'. Ideally this should be a json/yaml output.

Issue

Wrong description in CLI

$ hs model  --help
Usage: hs model [OPTIONS] COMMAND [ARGS]...
  Working with data profiles

$ hs --help
...
Commands:
  app      Working with data profiles <-----
  apply    Apply resources from files or directory.
  cluster  Utilities to manage hs clusters
  model    Working with data profiles <-----
  profile  Working with data profile

• Add cos_secure to kfp schema
• Validate usage (e.g. cos_secure with http endpoint)
• Add tests around cos_secure usage

In this iteration of improving our examples, I'd like to make our examples more like the ones in pipelines i.e. self contained files that a user can kubectl apply and then get something useful to happen e.g. something like the cron example we currently have.

Couple of conventions:

• Each file should contain all of the components needed e.g. the EventListener, TriggerBinding, TriggerTemplates

Make it tab separated too.

[stats] \t contigs \t 141
[stats] \t totalbp \t 4235451
[stats] \t n50 \t 23444

etc

So it can be grepped and parsed.
Beats having yet another small file output.

From the specs: "The value of the match option must be an XSLTMatchPattern. ... If the expression matches any other kind of node, the entire node (and not just its contents) is replaced by the hash."

Please see the test here: xproc/1.0-test-suite#34

Current save/load methods focus on dumping and loading the pipeline definition in its JSON form, but provide no means to save a fitted pipeline and load it later to make predictions, being the usage of pickle outside of the pipeline the only way to go.

Let's re-implement the save/load methods to save the whole pipeline instance, and move the current save functionality to a to_json method.