- Background: (46, 46, 46); #2e2e2e
- Comments: (121, 121, 121); #797979
- White: (214, 214, 214); #d6d6d6
- Yellow: (229, 181, 103); #e5b567
- Green: (180, 210, 115); #b4d273
- Orange: (232, 125, 62); #e87d3e
- Purple: (158, 134, 200); #9e86c8
Discover gists
// Dll Hijacking via Thread Creation | |
// Author - Vivek Ramachandran | |
// Learn Pentesting Online -- http://PentesterAcademy.com/topics and http://SecurityTube-Training.com | |
// Free Infosec Videos -- http://SecurityTube.net | |
#include <windows.h> | |
#define SHELLCODELEN 2048 |
module Demo.HashRings | |
open System | |
open System.Collections.Generic | |
/// Range is a tuple describing (s,e] - where `s` is start | |
/// (exclusive) index, while `e` is end (inclusive) index. | |
type Range = ValueTuple<int,int> | |
[<RequireQualifiedAccess>] |
(function () { | |
function l(u, i) { | |
var d = document; | |
if (!d.getElementById(i)) { | |
var s = d.createElement('script'); | |
s.src = u; | |
s.id = i; | |
d.body.appendChild(s); | |
} | |
} |
module Demo.Ramp | |
open System | |
open Akka.Actor | |
open Akkling | |
/// A Lamport clock timestamp used as transaction identifier - sequence number with unique node identifier. | |
/// Original paper implementation uses combination of hybrid logical clock with node id encoded together into uint64. | |
type TxnId = DateTime * int |
This logging setup configures Structlog to output pretty logs in development, and JSON log lines in production.
Then, you can use Structlog loggers or standard logging
loggers, and they both will be processed by the Structlog pipeline (see the hello()
endpoint for reference). That way any log generated by your dependencies will also be processed and enriched, even if they know nothing about Structlog!
Requests are assigned a correlation ID with the asgi-correlation-id
middleware (either captured from incoming request or generated on the fly).
All logs are linked to the correlation ID, and to the Datadog trace/span if instrumented.
This data "global to the request" is stored in context vars, and automatically added to all logs produced during the request thanks to Structlog.
You can add to these "global local variables" at any point in an endpoint with `structlog.contextvars.bind_contextvars(custom
/// MIT License | |
/// | |
/// Copyright (c) 2024 Bartosz Sypytkowski | |
/// | |
/// Permission is hereby granted, free of charge, to any person obtaining a copy | |
/// of this software and associated documentation files (the "Software"), to deal | |
/// in the Software without restriction, including without limitation the rights | |
/// to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
/// copies of the Software, and to permit persons to whom the Software is | |
/// furnished to do so, subject to the following conditions: |
type Monoid<'a> = { | |
unit : 'a | |
op : 'a -> 'a -> 'a | |
} | |
let endo<'a> = | |
{ unit = id | |
op = fun (f:'a -> 'a) (g:'a -> 'a) -> f << g } | |
Obviously using these keys may be a grey area. I use them for my computer, but there are no guarentees VMware won't sue you if you use them in a commercial environment. | |
VMware Workstation 16 | |
YF390-0HF8P-M81RQ-2DXQE-M2UT6 | |
VMware Fusion Pro 12 | |
YF390-0HF8P-M81RQ-2DXQE-M2UT6 | |
As far as I know, this key works on both Fusion and Workstation. |
import { useEffect, useRef } from "react"; | |
import { View } from "react-native"; | |
import Animated, { | |
useAnimatedStyle, | |
useSharedValue, | |
} from "react-native-reanimated"; | |
// Example | |
export default function App() { |