Ethan Wessel ejwessel

Dynamically generating `where` parameters to the `dbt_utils.union_relations` macro

-!  🚨                                          WARNING                                          🚨  !-
There is basically no reason for you to do this - written just to show that it's possible.

Let's assume for a second, we have a few incremental models that we want to union with dbt_utils.union_relations().

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

Clarify and agree on the scope of the system

User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?

A Typical directory structure for running tests using `unittest`

Ref : stackoverflow

The best solution in my opinion is to use the unittest [command line interface][1] which will add the directory to the sys.path so you don't have to (done in the TestLoader class).

For example for a directory structure like this:

new_project

├── antigravity.py

via (https://www.linux.com/learn/tutorials/442438-vim-tips-folding-fun)

zf#j creates a fold from the cursor down # lines.
zf/string creates a fold from the cursor to string .
zj moves the cursor to the next fold.
zk moves the cursor to the previous fold.
zo opens a fold at the cursor.
zO opens all folds at the cursor.
zm increases the foldlevel by one.
zM closes all open folds.

	// SPDX-License-Identifier: CC0
	pragma solidity ^0.8.0;

	// author @koeppelmann
	// Detector Factory allows to deploy new CensorshipDetector
	// Each CensorshipDetector monitors wether a specific address is being cencored on Ethereum
	// Each CensorshipDetector must be funded with ETH (anyone can send ETH to the CensorshipDetector)
	// Once funded anyone can call the "withdrawal" in the "CensorshipDetector" every 1h and it will pay a small bounty to tx.origin (100k * basefee)
	// During this transaction the "CensorshipDetector" will send 1 wei to the address that is endangered of being cencored.
	// CensorshipDetector will log the coinbase (validator address) (those are NOT censoring) and the number of blocks that has passed.

	const setupAddress = 'YOUR_SETUP_ADDRESS';
	const wethAddress = 'YOUR_WETH_ADDRESS';
	const web3 = new Web3(web3Provider);

	(async () => {
	console.log('Running exploit.....');

	try {
	// Script Setup
	console.log('Starting script setup....')

	# Assume we are in your home directory
	cd ~/

	# Clone the repo from GitLab using the `--mirror` option
	$ git clone --mirror [email protected]:mario/my-repo.git

	# Change into newly created repo directory
	$ cd ~/my-repo.git

	# Push to GitHub using the `--mirror` option. The `--no-verify` option skips any hooks.

	So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear!

	Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy.

	* Off the top of my head *

	1. Fork their repo on Github
	2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it

	git remote add my-fork [email protected]

Ethan Wessel ejwessel

Dynamically generating where parameters to the dbt_utils.union_relations macro

System Design Cheatsheet

Basic Steps

A Typical directory structure for running tests using unittest

Dynamically generating `where` parameters to the `dbt_utils.union_relations` macro

A Typical directory structure for running tests using `unittest`