| /** | |
| * Represents an axix-aligned bounding box. | |
| * | |
| * @author Kristian | |
| */ | |
| public class AABB { | |
| public static class Vec3D { | |
| /** | |
| * Point with the coordinate (1, 1, 1). | |
| */ |
| nnoremap yy "+yy | |
| vnoremap y "+y | |
| nnoremap p "+p | |
| vnoremap p "+p | |
| nnoremap P "+P | |
| vnoremap P "+P |
| /** | |
| * K.jpg's OpenSimplex 2, smooth variant ("SuperSimplex") | |
| * | |
| * More language ports, as well as legacy 2014 OpenSimplex, can be found here: | |
| * https://github.com/KdotJPG/OpenSimplex2 | |
| */ | |
| public class OpenSimplex2S { | |
| private static final long PRIME_X = 0x5205402B9270C86FL; |
To remove a submodule you need to:
While building a React Chrome extension using the create-react-app utility (v2.x), I came across the following error on loading my unpacked extension:
Refused to execute inline script because it violates the following Content Security Policy directive: “script-src ‘self’
blob: filesystem: chrome-extension-resource:”. Either the ‘unsafe-inline’ keyword, a hash (‘sha256-
GgRxrVOKNdB4LrRsVPDSbzvfdV4UqglmviH9GoBJ5jk=’), or a nonce (‘nonce-…’) is required to enable inline execution.
Basically, this error arises as Chrome (or almost any modern browser) will not allow inline scripts to get executed. This CSP restriction resulted in the above error as the build script in create-react-app bundles the .js files in <script> tags in the <body> of index.html.
I've been deceiving you all. I had you believe that Svelte was a UI framework — unlike React and Vue etc, because it shifts work out of the client and into the compiler, but a framework nonetheless.
But that's not exactly accurate. In my defense, I didn't realise it myself until very recently. But with Svelte 3 around the corner, it's time to come clean about what Svelte really is.
Svelte is a language.
Specifically, Svelte is an attempt to answer a question that many people have asked, and a few have answered: what would it look like if we had a language for describing reactive user interfaces?
A few projects that have answered this question:
Discord timestamps can be useful for specifying a date/time across multiple users time zones. They work with the Unix Timestamp format and can be posted by regular users as well as bots and applications.
The Epoch Unix Time Stamp Converter is a good way to quickly generate a timestamp. For the examples below I will be using the Time Stamp of 1543392060, which represents November 28th, 2018 at 09:01:00 hours for my local time zone (GMT+0100 Central European Standard Time).
| Style | Input | Output (12-hour clock) | Output (24-hour clock) |
|---|---|---|---|
| Default | <t:1543392060> |
November 28, 2018 9:01 AM | 28 November 2018 09:01 |
DO NOT RUN THIS , it will attempt to recursively overwrite files.
What follows is very simple deobufscation & explanation of what the code is doing. I have changed the library imports to make it more clear
The original code: https://github.com/RIAEvangelist/node-ipc/blob/847047cf7f81ab08352038b2204f0e7633449580/dao/ssl-geospec.js
import path from "path";
| export async function runConcurrentAsync<T, A extends IterableIterator<unknown>>(tasks: Task<T>[], argsList: A[] = [], concurrency = 5): Promise<T[]> { | |
| const semaphore = new Semaphore(concurrency); | |
| const promises = tasks.map(async (task, index) => { | |
| await semaphore.acquire(); | |
| try { | |
| const args = argsList[index] || []; | |
| return await task(...args); | |
| } finally { | |
| semaphore.release(); | |
| } |
| interface Logger { | |
| void error(String message, Throwable t); | |
| } | |
| class ConsoleLogger implements Logger { | |
| private final String className; | |
| ConsoleLogger(String className) { | |
| this.className = className; | |
| } |