sandman

Hi there! 😊

I’m DeepSeek-R1 — your friendly AI assistant created by **DeepSeek**, designed to
help answer questions, explain concepts, brainstorm ideas, and more. You can think
of me as a helpful companion who’s always ready with information, support, or just
good conversation!

Whether you need help with homework, drafting an email, understanding code,
exploring science topics, planning a trip — I’m here for it all! Just let me know

sandman

Aviva Investors Sterling Liquidity Plus Fund 4 GBP Acc

ISIN	BLOOMBERG	ASSET CLASS	NAV	FUNDSIZE	AS AT
IE00B3KMX297	AVISPL4 ID	Liquidity	1301.81 GBP	GBP 1625.14m	30 Jun 2025

Fund overview

sandman

If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.

To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.

1. Clone some repo (you've probably already done this step).

   git clone [email protected]

sandman

sudo apt-get install python3.X python3.X-venv

sandman

Download binaries: https://github.com/TalalMash/ubond/releases/tag/v0.1.1
Disable encryption for 400Mbit+ , force DNS over HTTPS if needed.
Temporarily running as root. (tun bugfix TODO)
----------------------
VPS/crontab -e:
@reboot screen -d -m sh -c "/root/startubond.sh"
----------------------
/root/startubond.sh
----------------------
#!/bin/sh

sandman

[INFO] [launch]: All log files can be found below /home/cfroch/.ros/log/2023-03-10-15-14-57-895435-cfroch-legion-395383
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [rcvstream_exe-1]: process started with pid [395386]
[INFO] [rcvstream_exe-2]: process started with pid [395388]
[INFO] [rcvstream_exe-3]: process started with pid [395390]
[INFO] [rcvstream_exe-4]: process started with pid [395392]
[rcvstream_exe-4] [INFO] [1678461298.036990546] [niro_fn22lnt.rcvstream_exe_back_node]: save_bit_stream is NOT set
[rcvstream_exe-4] [INFO] [1678461298.037425994] [rcv_stream]: cam_index: 3
[rcvstream_exe-2] [INFO] [1678461298.038131770] [niro_fn22lnt.rcvstream_exe_right_node]: save_bit_stream is NOT set
[rcvstream_exe-3] [INFO] [1678461298.038280339] [niro_fn22lnt.rcvstream_exe_left_node]: save_bit_stream is NOT set

sandman

  name                : The name of the object
                        flags: readable, writable
                        String. Default: "nvv4l2h265enc0"
  parent              : The parent of the object
                        flags: readable, writable
                        Object of type "GstObject"
  qos                 : Handle Quality-of-Service events from downstream
                        flags: readable, writable
                        Boolean. Default: false
  device              : Device location

sandman

pip3 install pip-tools pipreqs
# pipreqs generates a requirements.in file and pip-compile generates the requirements.txt from it
pipreqs --savepath=requirements.in && pip-compile

sandman

# Install latest version nvidia-docker2 on PopOS 22.04
## PopOS does not take the latest upstream NVIDIA Container runtime which is needed to run the container
## Run the below steps

### Add a new preference entry in /etc/apt/preferences.d/pop-default-settings

Package: *
Pin: origin nvidia.github.io
Pin-Priority: 1002

sandman

Install NVDEC and NVENC as GStreamer plugins

Environment

• Ubuntu 18.04
• NVIDIA driver 430.40
• NVIDIA Video Codec SDK 9.0.20

Steps