theinvensi

class RepeatTableHeadersHandler extends Paged.Handler {
    constructor(chunker, polisher, caller) {
        super(chunker, polisher, caller)
        this.splitTablesRefs = []
    }

    afterPageLayout(pageElement, page, breakToken, chunker) {
        this.chunker = chunker
        this.splitTablesRefs = []

justincy

In addition to the Storybook for React setup, you'll also need to install these packages:

npm i -D @babel/core babel-loader css-loader style-loader

leonardofed

We built this thing to make coding interviews suck less

The traditional technical interview process is designed to ferret out a candidate's weaknesses whereas the process should be designed to find a candidate's strengths.

No one can possibly master all of the arcana of today's technology landscape, let alone bring that mastery to bear on a problem under pressure and with no tools other than a whiteboard.

Under those circumstances, everyone can make anyone look like an idiot.

The fundamental problem with the traditional technical interview process is that it is based on a chain of inference that seems reasonable but is in fact deeply flawed. That chain goes something like this:

therightstuff

using Org.BouncyCastle.Crypto;
using Org.BouncyCastle.Crypto.Parameters;
using Org.BouncyCastle.OpenSsl;
using Org.BouncyCastle.Security;
using System;
using System.IO;
using System.Security.Cryptography;

namespace MyProject.Data.Encryption
{

adeekshith

# <type>: (If applied, this commit will...) <subject> (Max 50 char)
# |<----  Using a Maximum Of 50 Characters  ---->|


# Explain why this change is being made
# |<----   Try To Limit Each Line to a Maximum Of 72 Characters   ---->|

# Provide links or keys to any relevant tickets, articles or other resources
# Example: Github issue #23

OlegIlyenko

In this gist I would like to describe an idea for GraphQL subscriptions. It was inspired by conversations about subscriptions in the GraphQL slack channel and different GH issues, like #89 and #411.

Conceptual Model

At the moment GraphQL allows 2 types of queries:

• query
• mutation

Reference implementation also adds the third type: subscription. It does not have any semantics yet, so here I would like to propose one possible semantics interpretation and the reasoning behind it.

albertbori

public class MyDB : IdentityDbContext<User>
{  
    //DBSet properties go here

	public MyDB()
	{
		((IObjectContextAdapter)this).ObjectContext.ObjectMaterialized += new ObjectMaterializedEventHandler(ObjectMaterialized);
	}

	#region Encryption

kwent

#!/bin/sh -       
#title           :backup_neo4j_to_s3.sh
#description     :This script is creating a NEO4J Backup through neo4j-backup tool,
#                compress the backup folder via LZMA2 algorithm compression, and upload it to AWS S3.
#author		 :Quentin Rousseau <[email protected]>
#date            :2014-07-28
#version         :1.1
#usage		 :sh backup_neo4j_to_s3.sh ip port destination | eg. sh backup_neo4j_to_s3.sh 127.0.0.1 6362 /mnt/datadisk/backup
#dependencies    :apt-get update && apt-get install p7zip-full && apt-get install awscli.
#==============================================================================

sangeeths

Go to Bitbucket and create a new repository (its better to have an empty repo)
    git clone [email protected]:abc/myforkedrepo.git
    cd myforkedrepo

Now add Github repo as a new remote in Bitbucket called "sync"
    git remote add sync [email protected]:def/originalrepo.git

Verify what are the remotes currently being setup for "myforkedrepo". This following command should show "fetch" and "push" for two remotes i.e. "origin" and "sync"
    git remote -v

stevenkuhn

#
# Assumptions
#
# 1. If you have a Octopus release deployed, say 1.0.0.73, there is a git
#    tag set for that commit in GitHub that is "v1.0.0.73".
#
# 2. You have TeamCity label each successful build in GitHub with the format
#    "v{build number}. Sidenote: it appears that TeamCity only labels the
#    default branch, but not feature branches.
#