Max mstaack

## TestCase.php
<?php

namespace Tests;

use Illuminate\Foundation\Testing\TestCase as BaseTestCase;
use JMac\Testing\Traits\HttpTestAssertions;
use Tests\Utils\CreateUploadedFileFromFilePath;
use Tests\Utils\IsRoutesAware;
use Tests\Utils\ResourceAsserts;

## GeneralModal.vue
<template>
    <modal @modal-close="handleClose">
        <form
            @submit.prevent="handleConfirm"
            slot-scope="props"
            class="bg-white rounded-lg shadow-lg overflow-hidden"
            style="width: 460px"
        >
            <slot :uppercaseMode="uppercaseMode" :mode="mode">
                <div class="p-8">

## js_optional_chaining_operator.markdown

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              1 star
            
          
                kimhogeling
                / js_optional_chaining_operator.markdown
            
            
              Last active
              February 26, 2018 22:31
            
              
                Why the optional chaining operator might be pretty damn useful for readable code
              
          
    Coming soon to JavaScript: Optional Chaining Operator
This example is inspired by mpjme's Fun Fun Function Video
Watch that! It's short fun and explained really well!
This gist, is for me and my colleagues as a reference.
Given: Optional properties in an object
const hero1 = { name: 'Superman', address: { city: 'Metropolis', zip: 12345 } }

  
## twitter.html
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <meta http-equiv="X-UA-Compatible" content="ie=edge">
    <title>Twitter</title>
    <link rel="stylesheet" type="text/css" href="./css/tailwind.css">
    <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css">
</head>

## Application.php
<?php namespace App;


class Application extends \Laravel\Lumen\Application
{
    use Concerns\RoutesRequests; // override with our new trait
}

## siege
# Changed to use content-type flag instead of header: -H 'Content-Type: application/json'
siege -c50 -t60S --content-type "application/json" 'http://domain.com/path/to/json.php POST {"ids": ["1","2","3"]}'

## github-issue-to-phab-task.py
import json
import os

import requests


GITHUB_TOKEN = os.environ.get('GITHUB_TOKEN')
if GITHUB_TOKEN is None:
    raise Exception('Missing GITHUB_TOKEN from os.environ')

## scan_del.sh
#!/bin/bash

if [ $# -ne 3 ]
then
  echo "Delete keys from Redis matching a pattern using SCAN & DEL"
  echo "Usage: $0 <host> <port> <pattern>"
  exit 1
fi

cursor=-1

## parse-imap.md

      
              1 file
            
          
              1 fork
            
          
              0 comments
            
          
              13 stars
            
          
                karanth
                / parse-imap.md
            
            
              Last active
              August 7, 2022 06:27
            
              
                Notes on parsing IMAP responses
              
          
    The IMAP protocol workflow consists of the following steps,

A network connection established between the client and the server.
A greeting message sent by the server indicating that the client has successfully connected.
A series of interactions between the client and server.

The interactions consists of strings of lines, i.e. string terminated by a carriage return and a line feed (CRLF or \r\n). Interactions can be both commands (sent by clients) and data (sent by clients and servers). Both the client and the server strictly interact using lines or known length octet streams (8-bit characters) followed by a line.
####Client
An IMAP client issues commands to the server in a CRLF terminated string. The syntax of a command includes a tag, followed by the command and parameters. A tag is an alphanumeric identifier and each client command has a different tag for that session. A tag could be something like but not limited to A1, A2 etc.

  
## ParensParser.php
<?php

// @rodneyrehm
// http://stackoverflow.com/a/7917979/99923
class ParensParser
{
    // something to keep track of parens nesting
    protected $stack = null;
    // current level
    protected $current = null;
	<?php

	namespace Tests;

	use Illuminate\Foundation\Testing\TestCase as BaseTestCase;
	use JMac\Testing\Traits\HttpTestAssertions;
	use Tests\Utils\CreateUploadedFileFromFilePath;
	use Tests\Utils\IsRoutesAware;
	use Tests\Utils\ResourceAsserts;
	<template>
	<modal @modal-close="handleClose">
	<form
	@submit.prevent="handleConfirm"
	slot-scope="props"
	class="bg-white rounded-lg shadow-lg overflow-hidden"
	style="width: 460px"
	>
	<slot :uppercaseMode="uppercaseMode" :mode="mode">
	<div class="p-8">
	<html lang="en">
	<head>
	<meta charset="UTF-8">
	<meta name="viewport" content="width=device-width, initial-scale=1.0">
	<meta http-equiv="X-UA-Compatible" content="ie=edge">
	<title>Twitter</title>
	<link rel="stylesheet" type="text/css" href="./css/tailwind.css">
	<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css">
	</head>
	<?php namespace App;


	class Application extends \Laravel\Lumen\Application
	{
	use Concerns\RoutesRequests; // override with our new trait
	}
	# Changed to use content-type flag instead of header: -H 'Content-Type: application/json'
	siege -c50 -t60S --content-type "application/json" 'http://domain.com/path/to/json.php POST {"ids": ["1","2","3"]}'
	import json
	import os

	import requests


	GITHUB_TOKEN = os.environ.get('GITHUB_TOKEN')
	if GITHUB_TOKEN is None:
	raise Exception('Missing GITHUB_TOKEN from os.environ')
	#!/bin/bash

	if [ $# -ne 3 ]
	then
	echo "Delete keys from Redis matching a pattern using SCAN & DEL"
	echo "Usage: $0 <host> <port> <pattern>"
	exit 1
	fi

	cursor=-1
	<?php

	// @rodneyrehm
	// http://stackoverflow.com/a/7917979/99923
	class ParensParser
	{
	// something to keep track of parens nesting
	protected $stack = null;
	// current level
	protected $current = null;