A full unit-test run is currently around the mine (63.786s). This is not that bad but unit tests should be really quick, a go test shouldn't spend more than a second or two to run all the unit tests of a package. This is not the case now, some packages are quite the offender 😅.

• cmd/entrypoint (4.12s)
• pkg/reconciler/events/cloudevent (3.147s)
• pkg/reconciler/events (6

Found that if all pods end up on the same node (just happened to me) nothing works well at least on our cluster due to hairpin issues. Any chance the yaml could have anti-affinity set for the pods so they don't end up on the same node by accident?

We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome

Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.

This is blocked until #114 is merged which comes with first initial integration.

Summary

When creating docker images for Java applications in the current setup in Jenkins-X the application and all dependencies are all placed in one jar file, meaning it will be in one layer in the docker image.

This means that when new versions of the application are created the unchanged dependencies can't be reused.

It would be a great enhancement if the application code where p

Describe the bug
bare decimals in arithmetic in evaluation parameters cause a parsing error

To Reproduce
Steps to reproduce the behavior:

1. Write an expectation with an evaluation parameter that...
2. has a urn and some simple arithmetic with...
3. a bare decimal value
4. execute the expectation and note the parsing failure

downstream_batch.expect_column_mean_to_b

Description

Adding a new extra dataset to handle Delta parquet format (delta.io)

Context

When using Spark, we use more and more the Delta parquet format which is not only a parquet file but also gives ability to time travel or to change schema .

async def sub(a, b):
  return a - b

See fridgerator/PyNode#25 for details.

While testing another PR, I found that mu pipeline logs command displays information from the pipelines, but also shows this error:

$ mu pipeline logs
[... normal, expected output ...]
func1 ▶ ERROR  ResourceNotFoundException: The specified log group does not exist.
	status code: 400, request id: f7260741-7f69-4772-b4cc-7c6a9c22d264

This error does not occur with the `-f

The PR JuliaData/CategoricalArrays.jl#310 means that an array with elements of type Symbol can no longer be wrapped as a CategoricalArray.

This means all MLJ documentation and test code that uses symbols in categorical data must be refactored to use strings instead.

These repos, at least, need checking/refactoring, in order of priority:

• MLJ

• [x]