Repurposing a script used to find unused test builder methods from tektoncd/pipeline#3178 (comment) to try to find exported method names that aren't invoked from outside their package.

$ git grep -o "^func [A-Z][^(]*" pkg/ | grep -v "pkg/client" | grep -v " Test" | cut -d' '  -f 2 | sort | uniq | xargs -n 1 -I{} sh -c "git grep -c '\.{}(' > /dev/null 

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.

Describe the bug

Even when reaching the end of the log, the request to /logs endpoint are reinvoked causing the UI to restream the logs.

To Reproduce

1. Create a job that logs to stdout
2. Let it run to finish
3. View pod log getting repeated unnecessarily

Expected behavior

Stops request once the end of the log is reached

Screenshots

![image](https://user-ima

Summary

jx create addon istio doesn't work
since v 1.5 istio moved to operator so no folder install/kubernetes/helm/istio

Steps to reproduce the behavior

jx create addon istio

Output

Istio package already downloaded: /Users/msirs/.jx/cache/istio-1.6.0-osx.tar.gz
error: Could not find folder install/kubernetes/helm/istio inside istio clone at /Users/msirs/.jx/cache/istio

Description & context

Users can specify names for their nodes to identify them more easily. When a name is not explicitly specified, Kedro auto-generates a default name. You can see this in the name property on Node.
The current auto-generated name for a node looks something like this: func_name(inputs) -> outputs. (see implementation of __str__ method on the Node class)

This is

Describe the bug
Using a data source with umlauts in the column names leads to the Jupyter Notebook with which the suite can be edited throw an error on startup. The Notebook then doesn't load.
This might be a Jupyter Notebook bug, not sure?!

To Reproduce
Steps to reproduce the behavior:

1. Initialize a suite with this xlsx file as a data source (nothing fancy: Just two columns, the

At Node.js, async function will not block the JavaScript thread, and sync does. So it's a best practice in somehow to use the async function instead of sync ones.

Feel free to open small PRs to help us to change the sync to async.

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

Analogous to how you can use basename to get only the filename of a path, like in:

p.SetOut("out1", "{i:in1|basename}.out.txt")

... it would be useful to also be able to extract only the directory, using dirname as a modifiers, so:

p.SetOut("out1", "{i:in1|dirname}/newfilename.txt")

This will also allow introducing another level of folders based on a previous

"We could also try and update the job naming for CWL jobs to include fewer UUIDs, because I'm not sure they really help anyone for debugging." DataBiosphere/toil#3226 (comment)

┆Issue is synchronized with this Jira Task
┆Issue Number: TOIL-666