<!-- -- != := === >= >- >=> |-> -> <$>
</> #[ |||> |= ~@
// The five boxing wizards jump
#include // <= quickly.
int main(int argc, char **argv) {
float il1[]={1-2/3.4,5+6==7/8};
int 0xFaced=0xBAD||”[{(CQUINE";
<!-- -- != := === >= >- >=> |-> -> <$>
</> #[ |||> |= ~@
// The five boxing wizards jump
#include // <= quickly.
int main(int argc, char **argv) {
float il1[]={1-2/3.4,5+6==7/8};
int 0xFaced=0xBAD||”[{(CQUINE";
#!/bin/bash | |
# by d4rk3r | |
# A smart way to search for a code | |
# inside your git history whatever the branch you're | |
# -- Setup : | |
# -- After getting the bash script | |
# chmod +x /path/to/gf.sh |
The instructions in this gist have some subtle problems and this gist will not be updated.
this is a rough draft and may be updated with more examples
GitHub was kind enough to grant me swift access to the Copilot test phase despite me @'ing them several hundred times about ICE. I would like to examine it not in terms of productivity, but security. How risky is it to allow an AI to write some or all of your code?
Ultimately, a human being must take responsibility for every line of code that is committed. AI should not be used for "responsibility washing." However, Copilot is a tool, and workers need their tools to be reliable. A carpenter doesn't have to
MIT License | |
Copyright (c) 2021 Daniel Ethridge | |
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: |
-ea | |
-server | |
-Xss256k | |
-Xms4G | |
-Xmx4G | |
-XX:+IgnoreUnrecognizedVMOptions | |
-XX:+UnlockExperimentalVMOptions | |
-XX:+HeapDumpOnOutOfMemoryError | |
-XX:-OmitStackTraceInFastThrow | |
-XX:-UseSerialGC |
package main; | |
import com.google.common.truth.Truth; | |
import net.starlark.java.eval.EvalException; | |
import net.starlark.java.eval.Module; | |
import net.starlark.java.eval.Mutability; | |
import net.starlark.java.eval.Starlark; | |
import net.starlark.java.eval.StarlarkInt; | |
import net.starlark.java.eval.StarlarkList; |
// system resources physical memory map VM detection trick | |
// written by Graham Sutherland (@gsuberland) for Nettitude | |
// based on prior work done as part of the al-khaser project | |
// https://github.com/LordNoteworthy/al-khaser/ | |
// ref: https://blog.xpnsec.com/total-meltdown-cve-2018-1038/ | |
// ref: https://gist.github.com/xpn/3792ec34d712425a5c47caf5677de5fe | |
// compile: |
""" | |
Github Issue Thread: https://github.com/samuelcolvin/pydantic/issues/2152#issuecomment-786713976 | |
License : MIT | |
Copyright 2021 Shashank Sharma | |
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, |
This is a cheat sheet for how to perform various actions to ZSH, which can be tricky to find on the web as the syntax is not intuitive and it is generally not very well-documented.
Description | Syntax |
---|---|
Get the length of a string | ${#VARNAME} |
Get a single character | ${VARNAME[index]} |