daniel lee khun84

ai-coding-assistant.md

🎯 Purpose

This prompt defines how an AI assistant should behave when collaborating with senior engineers. The assistant serves two key roles:

As a fast and accurate executor for tactical tasks
As a critical thinking partner for design, review, and sequencing

It promotes clean engineering habits, testability, sustainable delivery, and clear communication—without slowing down progress.

Basically we just need to do the following

# 1. Install v8 ourselves
$ brew install v8-315
# 2. Install libv8 using the v8 binary we just installed
$ gem install libv8 -v '3.16.14.19' -- --with-system-v8
# 3. Install therubyracer using the v8 binary we just installed
$ gem install therubyracer -- --with-v8-dir=/usr/local/opt/v8@315 # your path could be different, e.g. /usr/local/opt/[email protected]
# 4. Install the remaining dependencies

require 'kafka'
require 'avro_turf/messaging'

kaf_broker = "from-ur-credentials"
kaf_api_key = "from-ur-credentials"
kaf_api_secret = "from-ur-credentials"
schema_url = "from-ur-credentials"
schema_api_key = "from-ur-credentials"
schema_api_secret = "from-ur-credentials"

The main point is to save the SSL/TLS keys those used by the web browser (SSLKEYLOGFILE=/tmp/tmp-google/.ssl-key.log).
In the example below we run brand new instance of Google Chrome (--user-data-dir=/tmp/tmp-google do the trick):
SSLKEYLOGFILE=/tmp/tmp-google/.ssl-key.log /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --user-data-dir=/tmp/tmp-google
Then run the Wireshark and open the Preferences -> Protocols -> SSL, where we put the path to the SSL keys log file into the (Pre)-Master-Secret log filename field.
Now all SSL/TLS traffic from this browser instance will be decrypted.

Put tlskeylogger.plist at ~/Library/LaunchAgents/tlskeylogger.plist
launchctl load ~/Library/LaunchAgents/tlskeylogger.plist, so it will load on the next restart
launchctl start ~/Library/LaunchAgents/tlskeylogger.plist, so it will load the environment variable immediately
Restart your browser(s)
See how TLS keys are being written to ~/.tlskeyfile via tail -f ~/.tlskeyfile

Playbook to setup physical replication in Postgresql 13

Install the postgresql 13 for replica on another instance. sudo apt-get install postgresql-13. Install binary extension if theres any, ie sudo apt-get install postgresql-13-postgis-3
Create a user in master server for replication connection. create user replica with password <password>
Change the following postgres config in the master server

# in /etc/postgresql/13/main/postgres.conf

max_wal_senders = 5
synchronous_standby_names = 'pgslave001' # or any other you prefer

The reason of this issue is here => https://www.openssl.org/blog/blog/2021/09/13/LetsEncryptRootCertExpire/

So basically we can just remove the expired cert from the ssl cert file as suggested here => https://www.linuxadictos.com/en/ya-iniciaron-los-problemas-generados-por-el-certificado-dst-root-ca-x3.html

My ssl cert file is located in /etc/ssl/cert.pem. I just need to look for the expired cert and comment it out.

Since Im using ruby 2.3.1 which is using openssl 1.0.2t and I dont want to recompile it, I can use the env var SSL_CERT_FILE to tell which ssl cert i want to use in ruby runtime.

	require 'json'
	require 'csv'

	data = `pbpaste`
	data = JSON.parse(data);nil
	data = data.select{\|d\| d.dig('schedule', 'paused') == false && d['source_type'] == 'dbtable' };nil
	keys = [
	'title',
	'description',
	'src_db', # from_ds_name

	- sleep
	- pipeline
	- parallel task