Notes about how to use ripgrep to search hidden files and configuration related to Neovim.

We have a Python project where there are several developers, and we have a mature CI pipeline to do code linting, formatting check for python, yaml, json, and testing etc. The problem with CI pipeline is that you can only get feedback after you commit your code and push to the remote repo. The feedback is not instant and may be delayed for several minutes. If there are some linting issues, you then need to fix the issue and make another commit. This is also making the PR history messy.

A major Neovim release (version 0.12) has been released a few days ago, after more than one year from the last major release (version 0.11). The following is a list of feature I am interested. For a complete set of features, check full changelog and news.

builtin package manager vim.pack

#

Now you can use the builtin vim.pack API to manage your plugins. Check this detailed post if you want to migrate to vim.pack.

When unit-testing a function that make multiple external calls/requests, we want to mock the actual call and return the mock results. For each call, we might want to return different results.

Previously, our projects are still using the old Python 3.10, which will be deprecated soon this year. We are also using the good old pip and venv for the project/package management. This is already posing some issues for us:

• venv is a pure virtual env tool without the ability to manage python versions (it just picks your local python), so it is hard to enforce the local env of each developer
• pip’s requirements.txt is not a lockfile and thus does not ensure a fully reproducible python environment
• pip as a package management tool is not performant enough in resolving and installing packages

In order to solve these problems, I took the effort to migrate our project management to uv. Here are some of the things that I learned in the process as a first-time uv user.

When I am working on a Python project, I am using black to format the code, so that we have a unified format across the code base.

One pain point, however, is the super annoying trailing white spaces:

1. black can remove trailing spaces for doc string, code and comment, but it will not touch trailing spaces in, e.g., multi-line strings.

In this post, I compare the object vs nested type used in data mapping in Elasticsearch.

When you do code testing using pytest, pytest can do sophisticated changes to your logging. This is a very powerful feature, but carries some subtlety.

In Elasticsearch, when we index documents to an index, by default the source of the document is stored in meta field _source. When you search your index, you see a special field _source for each matched/hit product.

本文总结如何制作中式家常版本的“葱花饼”。

今天总结一下在德国超市里常见的蔬菜苤(piě)蓝（德语叫kohlrabi，在中国东北叫“卜留克”) 凉拌的做法。

和众多网友一样，我也有高考 PTSD。

In Elasticsearch, you can use wildcard in a lot of the index operations. This is very handy, but can be dangerous sometimes, e.g., when you use wildcards when deleting indexes. You may delete unintended indexes accidentally and cause serious interruptions to your business/work.

This post will give a quick summary on how to import GPX route into Garmin watch.

When I try to run pytest locally for a Python project, I noticed that the import in those test scripts may fail if I run pytest in different directories. The import error usually means that your actual code modules is not in the python path, so they can not be imported successfully by your test scripts.

This has something to do with how pytest set up the python path when you run it.