Description
We have to continuously push for quality, thus we always need to improve our testing and test coverage. Any improvement of testing is a great contribution to jina.

If you have no idea how to get started on this, here there are some ideas that could be good to have.

• Increase coverage
  Checking the reports on `https://codecov.io/gh/jina-ai/jin

Is your feature request related to a problem? Please describe.
Problem: I'd like to dynamically import scripts as <script> tags.

Describe the solution you'd like
Proposal:

const useScript = ({ url, id, type = 'text/javascript', async = true }) => {
    const [ready, setReady] = React.useState(false);
    const [failed, setFailed] = React.useState(false);

    R

Steps to reproduce:

1. Visit the Actions tab.
2. Create an action with some comment
3. Try modifying the action comment

Errors:
126. new Intl.NumberFormat is not supposed to get passed a single object as param. The first param must be a string and the second param can be an object.
135. Spelling error ('tis' should be 'this').

Suggestion:
86. Needs to be more explicit by calling the function in the example. Calling getName() with any falsy value would not set hasName to true with your correct answer.

Python wheels we build in the CI, such as PyZMQ or LIEF, do not get cached, and are rebuilt every CI run. This wastes time/CPU (LIEF can take some time to build). The versions of these packages rarely change, so we should be caching and reusing build output.

It looks like Cirrus even has a pip_cache key, that we may be able to ta

If I run trim

echo [[Column1]; ["  Value1   a lot of spaces  "] [Value3]] | str trim

it trims only "wrong" withe spaced at the beginning and at the end

───┬──────────────────────────
 # │         Column1
───┼──────────────────────────
 0 │ Value1   a lot of spaces
 1 │ Value3
───┴──────────────────────────

It it would be great a complete white spaces cleaning

• nvim --version:

NVIM v0.5.0-dev+1339-g5d9c56012
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/VC/T
ools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe /DWIN32 /D_WINDOWS /W3 /MD /Zi /O2
/Ob1 /DNDEBUG /W3 -D_CRT_SECURE_NO_WARNINGS -D_CRT_NONSTDC

Kibana version: master (~7.14)
Describe the bug:

Human-readable duration field formatter outputs a few seconds for 0 value

Steps to reproduce:

1. Create a duration human-readable field formatter on index pattern
2. Check-in discover how a 0 value shown as a few seconds

Expected behavior:

I think we should output 0 following other formatting options. e.g

Is your proposal related to a problem?

Moving from Prometheus to Thanos and I am now noticing that Ruler does not show alert rule duration in the UI like Prometheus would show. I think it is important to show this