Summary

This is minor, but also really annoying when trying to run a bunch of workflows from the UI.

1. Go to /workflows
2. Click 'Submit new workflow'
3. Click in the 'select a workflow template' text area
4. Start typing

Issue: Your typing isn't refining the search.

I have to click again in the text dropdown for my typing to be effective.

Diagnostics

What Kubernetes

使用以下命令部署模型是，输入的thread参数不起作用，cpu使用率不超过400%：

python -m paddle_serving_server.serve --model my_model --thread 10 --port 9292 --name my_model

原因是文件：
https://github.com/PaddlePaddle/Serving/blob/develop/python/paddle_serving_server/serve.py
中第433行中processes=4，并没有更新为用户的输入参数；

In #2299 we patched the API to return the current (tip) layer rather than statically returning the first layer of the third epoch as the current layer. But this still isn't really accurate. What we really want is for the API to instead return the latest synced layer. This information is currently not exposed to the API, but it could be, and it definitely lives in the sync code somewhere, since s

To improve the security, it's good to start eliminating dependencies. Domains are a good start point.

We need to add a new CI job under lint: within the .github/workflows/testing.yml to validate commit message formatting.

Add a new CMD class in dffml/service/dev.py (along with tests in tests/service/test_dev.py) to check that commit message titles match the format specified in https://intel.github.io/dffml/master/contributing/git.html#issue-and-pull-request-title-formatting

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  

Ideally, we'd take a page from the https://github.com/multiformats/js-multiformats book and support cjs, esm, etc builds via rollup and friends to support multiple platforms/use-cases. Since this is designed to be a light-weight alternative to other ipds-based libraries, it should have a really low barrier to usage out of the box. In fact, moving forward, this should be a pretty critical require

What is the expected enhancement?

As retworkx continues to grow the number of algorithm functions we offer has grown substantially. Right now we have been putting standalone functions just in lib.rs except where th