ilake

#config/initializers/sorcery_async_email.rb 
module Sorcery
    module InstanceMethods
      def generic_send_email(method, mailer)
        config = sorcery_config
        config.send(mailer).delay.send(config.send(method),self)
      end
    end
  end
end 

xpepermint

'use strict';

/**
* Webpack Configuration File
*
* This is a configuration file for Webpack module bundler. You should customize
* it to fit your project.
*
* To start the development server run:
*

fbaiodias

Circular dependencies on GraphQL schemas

Problem

Whenever I uncomment the lines on author.js I get the following error:

/Users/xicombd/Code/taskq/taskq-api/node_modules/graphql/jsutils/invariant.js:20
    throw new Error(message);
    ^

xpepermint

var path = require('path');
var webpack = require('webpack');
var isProduction = process.env.NODE_ENV === 'production';

/*
* Compile for usage in a browser-like environmen or for the server.
*/

exports.target = 'web';

xpepermint

```
#!/bin/sh

branch=$(git branch | sed -n -e 's/^\* \(.*\)/\1/p')

if [ "master" != "$branch" ]; then
  exit;
fi

git checkout production

xpepermint

const { Model } = require("rawmodel");
const express = require("express");

/** Application context *******************************************************/

class Context {
  constructor() {
    this.db; // imaginary database
  }
  connect() {

xpepermint

Commands

Install dependencies:

npm install -g @microsoft/rush

Initialize the project:

xpepermint

const { Cert } = require('@0xcert/cert');
const { HttpProvider } = require('@0xcert/ethereum-http-provider');
const { AssetLedger } = require('@0xcert/ethereum-asset-ledger');

(async () => {

  const schema = {
    "$schema": "http://json-schema.org/draft-07/schema",
    "description": "A digital assets that have a unique combination of different properties.",
    "properties": {

Phaiax

How does async work in async-std?

(Phaiax - 2019/12/1 - CC_BY_SA 4.0)

Lately I was porting a software from tokio/futures-1.0 to async-await. I somehow thought async-std was the successor of tokio and ported everything to async-std. 80% in, I noticed that my hyper dependency requires tokio and that it's not possible to replace tokio with async-std without also replacing hyper. Also, tokio and async-std try to solve the same problem. So I started a journey into the inners of the rust async story to find out if it is possible to use both tokio and async-std at the same time. (tl;dr: it is). I had heard of reactors and executors before, but there was much new stuff to discover.

jbr

[package]
name = "surf-tide-proxy-example"
version = "0.1.0"
authors = ["Jacob Rothstein <[email protected]>"]
edition = "2018"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
surf = { git = "https://github.com/http-rs/surf", branch = "master" }