I highly recommend using python-semantic-release instead. It provides full control over the release creation and does not have roadblocks in place preventing you from using it on non-latest commits. Still, if using semantic-release is a must, above scripts provide the means to do so.
WSL2 uses a random network from the 172.16.0.0/12 RFC1918 private IP address block. And our VPN uses that address block, too, with a route metric of 1
(= most preferred.)
This breaks networking for WSL2. Meh!
While messing around with the interface/route metric of the VPN network may work around the problem, it also reduces the priority of the VPN. We do not really want this. Additionally, changing the interface metric does not seem to be permanent, so it requires more work when it breaks again.
1. # create new .py file with code found below | |
2. # install ollama | |
3. # install model you want “ollama run mistral” | |
4. conda create -n autogen python=3.11 | |
5. conda activate autogen | |
6. which python | |
7. python -m pip install pyautogen | |
7. ollama run mistral | |
8. ollama run codellama | |
9. # open new terminal |
Param | |
( | |
[string]$PAT, | |
[string]$Organization, | |
[string]$Connstr | |
) | |
$SQLQuery = "TRUNCATE TABLE PersonalAccessTokens" | |
Invoke-Sqlcmd -query $SQLQuery -ConnectionString $Connstr |
Internet connection and DNS routing are broken from WSL2 instances, when some VPNs are active.
The root cause seems to be that WSL2 and the VPN use the same IP address block, and the VPN routing clobbers WSL2's network routing.
This problem is tracked in multiple microsoft/WSL issues including, but not limited to:
#! /bin/bash | |
# Input file should be based on downloadable Excel sheets, but saved as CSV file (field_delimiter=; string_delimiter=<empty>) | |
INPUT_FILE=${1} | |
INPUT_FILE_CONTENT_START_LINE=${2:-2} | |
URL_COLUMN_IDX=${3:-19} | |
assemble_download_file_basename() { | |
input_file="${1}" | |
url="${2}" |
We can export a mermaid diagram to PNG very simply using the official Mermaid CLI Tool.
Installation via npm
npm i -g mermaid.cli
Usage:
-
Gets PAT - personal access token - from azure devops profile. See more on this page.
You can use username:password from 'Alternate credentials', which is also in your profile. -
Use curl with -s - silent, doesn't print statistics. Use
jq
tool for pritty print json content.
> curl -s -u username:PAT -H "Content-Type: application/json" https://dev.azure.com/<organization>/_apis/projects?api-version=2.0 | jq
You can use authorization header directly from the bash tasks from some build/release pipeline with System.AccessToken pipeline variable
> curl -H "Authorization: Bearer $(System.AccessToken)" -H "Content-Type: application/json" \
Sinks are for output, sources are for input. To stream source to sink a loopback must be created. More shall you find there.
Our output sink will be named recording
.
pacmd load-module module-null-sink sink_name=recording sink_properties=device.description=recording