sudo apt install zsh-autosuggestions zsh-syntax-highlighting zsh
wget https://www.python.org/ftp/python/2.7.18/Python-2.7.18.tgz | |
tar xzf Python-2.7.18.tgz | |
cd Python-2.7.18 | |
sudo ./configure --enable-optimizations | |
sudo make altinstall | |
sudo ln -s "/usr/local/bin/python2.7" "/usr/bin/python" |
Чеклист для собеседования | |
Общее | |
[] SOLID, расшифровка каждой буквы + примеры из го | |
[] Паттерны из Gang of Four, мочь сказать какие виды + 3-4 запомнить и как их использовать | |
[] Что такое хеш таблица, сет, стек, очередь и для чего нужны | |
[] Что такое TPC/IP, в чем отличия с UDP? | |
[] Как работает http запрос? Коды ошибок, http методы. | |
[] Отличия http и https. Как работает https? | |
[] http/1 и http/2 в чем отличия? |
INCOMPLETE, I ENCOURAGE CONTRIBUTING
This gist serves as a non-exhaustive, high-level overview of implementing MultiLoader-Template, which was created by jaredlll08 and contributors in 2021 for Hacktoberfest.
Trivia: Specifically, the first commit to MultiLoader-Template was a Markdown file simply reading "FabricForgeTogether", which was committed by jaredlll08 on Jul 23, 2021!
Only official mojang mappings are used in this gist. We are targetting 1.20.1 as the root/source-of-truth for our mod, and porting up to 1.21.1.
/* GTM : use the following code inside a customTask, hitCallback oder a cleanup tag | |
GA.JS : modify your existing tracking code with a customTask or hitCallback and execute the following code | |
GTAG.JS : modify your existing tracking code with a manual page_view event | |
including an event_callback (gtag.js) and execute the following code | |
customTask ga.js - see: https://developers.google.com/analytics/devguides/collection/analyticsjs/tasks#adding_to_a_task | |
hitCallback ga.js - see: https://developers.google.com/analytics/devguides/collection/analyticsjs/sending-hits#hitcallback | |
event_callback gtag.js - see: https://developers.google.com/analytics/devguides/collection/gtagjs/sending-data#implement_event_callback_functions | |
*/ |
<script> | |
function addEvent(obj, evt, fn) { | |
if (obj.addEventListener) { | |
obj.addEventListener(evt, fn, false); | |
} else if (obj.attachEvent) { | |
obj.attachEvent("on" + evt, fn); | |
} | |
} | |
// Exit intent trigger |
<script type="text/javascript"> | |
/* gms.scrolltracking.js | v0.2 | |
www.gandke.de | |
Copyright (c) 2015 Markus Baersch (@mbaersch) | |
Licensed under MIT license. | |
*/ | |
var trackBottomScroll = 0; | |
var trackScrollStep = 20 ; | |
var useDataLayer = true ; | |
window.onscroll = function () { |
function leak_hole() { | |
let x; | |
delete x?.[y]?.a; | |
return y; | |
let y; | |
} | |
function pwn() { | |
let hole = leak_hole(); | |
%DebugPrint(hole); | |
} |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j