thanksshu

"""
Test cloudflare WARP endpoints
Select all the best WARP endpoints
Thanks to https://gitlab.com/Misaka-blog/warp-script#warp-endpoint-ip-优选脚本
"""

import asyncio
import csv
import ipaddress
import logging

r17x

/**
 * Example `FizzBuzz` with JavaScript (Pattern-Matching Like????????????) λ_(ツ)_/¯
 * I Love this tweet 
 * @see https://twitter.com/cajuinaoverflow/status/1395022027204005889
 * JavaScript will make You Crazy (Trust Me!)
 */
const FizzBuzz = n => ({
  true: n, 
  [ n % 5 === 0]: "Buzz",
  [ n % 3 === 0]: "Fizz",

wpscholar

function Loader(el) {

    el.loader = this;
    this.el = el;
    this.style = document.getElementById('js-loader-styles');
    this.init();

    if (!document.body.animate) {
        if (!this.style) {
            this.style = document.createElement('style');

ravibhure

In your local clone of your forked repository, you can add the original GitHub repository as a "remote". ("Remotes" are like nicknames for the URLs of repositories - origin is one, for example.) Then you can fetch all the branches from that upstream repository, and rebase your work to continue working on the upstream version. In terms of commands that might look like:

Add the remote, call it "upstream":

git remote add upstream https://github.com/whoever/whatever.git

Fetch all the branches of that remote into remote-tracking branches, such as upstream/master:

git fetch upstream