Install the pylance extension in vscode or manually download it from the marketplace
The extension path should be similar to this: ~/.vscode/extensions/ms-python.vscode-pylance-2023.11.10
In init.vim, this will automatically detect the latest pylance version because after an upgrade the old plugin might linger for a while:
call coc#config('languageserver', { "pylance": { "module": expand("~/.vscode/extensions/ms-python.vscode-pylance-*/dist/server.bundle.js", 0, 1)[0] } })
| services: | |
| gitlab: | |
| image: 'gitlab/gitlab-ce:14.6.0-ce.0' | |
| restart: always | |
| hostname: 'localhost' | |
| ports: | |
| - "443:443" | |
| - "80:80" | |
| - "22:22" | |
| environment: |
Gist for https://youtu.be/N8AQTlHoBKc
This article show you the ultimate way to set up a transparent proxy on Linux using clash and iptables to bypass the GFW in China.
We use:
- clash as the proxy software
- online subconverter and crontab to periodically update config file.
- ACL4SSR to provide GFW rules.
You can go to github gist to download all files mentioned in this article.
Conformance test are a subset of the e2e test Kubernetes test.
The e2e tests are based on Ginkgo https://onsi.github.io/ginkgo/ and live in the Kubernetes repository https://github.com/kubernetes/kubernetes/tree/master/test/e2e.
There is no guarantee of compatibility for the e2e binaries, hence the e2e binary version MUST match your kubernetes cluster version.
| import json | |
| import os | |
| import time | |
| import webbrowser | |
| import sys | |
| import re | |
| def handleWindows(extra_seconds): | |
| print("OS : Windows") |
The set lines
- These lines deliberately cause your script to fail. Wait, what? Believe me, this is a good thing.
- With these settings, certain common errors will cause the script to immediately fail, explicitly and loudly. Otherwise, you can get hidden bugs that are discovered only when they blow up in production.
set -euxo pipefailis short for:
set -e
set -u