This is a guide for aligning images.
See the full Advanced Markdown doc for more tips and tricks
// add this code to your StartupModule() function of your EDITOR module | |
// if it doesnt work, try setting loading phase to "postdefault" -- no idea if this will produce side effects though. | |
// basically idea is looping all CDOs (i.e. UClasses) and their properties, getting their "category" meta value and registering them to | |
// property sections | |
FPropertyEditorModule& PropertyModule = FModuleManager::LoadModuleChecked<FPropertyEditorModule>("PropertyEditor"); | |
static constexpr bool bAddSubcategories = false; // you probably want this to be false | |
auto ProcessCategory = [&PropertyModule](const FName ClassName, const FString& Category) |
#Resizes an image and keeps aspect ratio. Set mywidth to the desired with in pixels. | |
import PIL | |
from PIL import Image | |
mywidth = 300 | |
img = Image.open('someimage.jpg') | |
wpercent = (mywidth/float(img.size[0])) | |
hsize = int((float(img.size[1])*float(wpercent))) |
# update & upgrade | |
sudo apt update && apt upgrade | |
# create user | |
adduser <username> | |
# install packages | |
apt install tilix maltego metasploit-framework burpsuite wireshark aircrack-ng hydra nmap beef-xss nikto | |
# install tor |
This is a guide for aligning images.
See the full Advanced Markdown doc for more tips and tricks
#!/usr/bin/nft -f | |
flush ruleset | |
# home, office | |
# define admin = { 10.10.10.10. 172.10.10.10 } | |
table nat { | |
chain prerouting { | |
type nat hook prerouting priority 0 |
These are notes written up about the XG Mobile connector which is found on the Asus ROG Ally as well as some ROG Flow models. The goal is to build a custom eGPU enclosure that is compatible with the XG Mobile connector.
The XG Mobile Cable comes with ROG XG Mobile and can be purchased from a [parts store][2] for $129 USD. It has a male XG Mobile Connector on one end and three cables on the other end: two 40-pin FPC cables and a 8-pin connector. The cable carries a USB-C connection, PCIe x8 signal pairs, PCIe clock, an SMBus/I2C connection, and some sideband signals for power detection and hot-plug support.
The pinout can be obtained from the [GV301QC schematic][1] (page 69).
Pin | Name | Pin | Name |
---|---|---|---|
C1 | PCIENB_TXP0_C | D1 | PCIENB_TXP5_C |
# pip install webdriver_manager | |
# pip install selenium | |
from selenium import webdriver | |
from selenium.webdriver.common.keys import Keys | |
from time import sleep | |
from selenium.webdriver.common.by import By | |
from selenium.webdriver.chrome.service import Service | |
from selenium.webdriver.chrome.options import Options | |
from webdriver_manager.chrome import ChromeDriverManager |
UTC: 2024-04-25 06:08 chocolatey-community/chocolatey-packages
This file is automatically generated by the update_all.ps1 script using the Chocolatey-AU module.
Ignored | History | [Force Test](https://gist.github.com/ee5
https://stackoverflow.com/questions/48993286/is-it-possible-to-route-traffic-to-a-specific-pod?rq=1
You can guarantee session affinity with services, but not as you are describing. So, your customers 1-1000 won't use pod-1, but they will use all the pods (as a service makes a simple load balancing), but each customer, when gets back to hit your service, will be redirected to the same pod.
Note: always within time specified in (default 10800):