dankarization

blueprint:
  name: Link On/Off State of Multiple Devices
  description: |
    ## Link On/Off State of Multiple Devices v1.3
    1) It triggers not only on a state change, but also every minute, to eliminate a problem with very fast changes on/off with last one not triggering anything and entities become unsincronized.
    2) It does not trigger when initial entity state is unavailable or unknown. It solves the problem with a ton of zigbee devices firstly sending this status after HA reboot, then sending their real one, trigerring all automations based on the v1 template.
    3) Fixed log errors

    ### Credits
    * [@luma](https://community.home-assistant.io/u/luma) for [v1 template](https://community.home-assistant.io/t/link-on-off-state-of-multiple-devices/460310)

dbrand666

blueprint:
  name: Link On/Off State of Multiple Devices
  description: "## Link On/Off State of Multiple Devices v1.0.3

    Select multiple entities to link their on/off state. If any selected
    entity is turned on or off, the other selected entities will be sent
    a matching on or off command.


    You can select any entity, but only entities supported by the

hartfordfive

Description

The goal of this hook is to allow you catch when you're committing with an email you shouldn't on a public repositories. In some cases, certain companies need to seperate their internal coporate email accounts from those that might be used for committing to public repositories.

Setting up.

The UNWANTED_EMAIL_SUFFIX should be the suffix (after the @ sign) of the email address you do not want to appear in the git logs. The DESIRED_AUTHOR_EMAIL and DESIRED_AUTHOR_NAME are the respective email and name you want to show up in the git logs.

christopherlai

FROM elixir:1.9.1-alpine as build

ENV MIX_ENV=prod

WORKDIR /build

RUN apk add --no-cache build-base nodejs yarn && \
    mix local.hex --force && \
    mix local.rebar --force

douglascayers

/**
 * Inspired by @MoOx original script: https://gist.github.com/MoOx/93c2853fee760f42d97f
 * Adds file download per @micalevisk https://gist.github.com/MoOx/93c2853fee760f42d97f#gistcomment-2660220
 * 
 * Changes include:
 *  - Get the description from the `title` attribute instead of `aria-label` (doesn't exist anymore)
 *  - Use style.backgroundColor and parse the rgb(...) to hex (rather than regex parsing of 'style' string)
 *  - Downloads labels to a JSON file named after the webpage to know which GitHub repo they came from.
 * 
 * Last tested 2019-July-27:

joepie91

You don't need a blockchain.

If you're reading this, you probably suggested to somebody that a particular technical problem could be solved with a blockchain.

Blockchains aren't a desirable thing; they're defined by having trustless consensus, which necessarily has to involve some form of costly signaling to work; that's what prevents attacks like sybil attacks.

In other words: blockchains must be expensive to operate, to work effectively. This makes it a last-resort solution, when you truly have no other options available for solving your problem; in almost every case you want a cheaper and less complex solution than a blockchain.

In particular, if your usecase is commercial, then you do not need or want trustless consensus. This especially includes usecases like supply chain tracking, ticketing, and so on. The whole *p

fasiha

Well, that was unexpected. In the following, I’m trying to follow Jon Evans’ advice from “The Terrible Technical Interview”.

---

To: [email protected]
From: Ahmed Fasih
Subject: Re: Programming Test Invitation

Hi there! Thanks for offering to let me take a HackerRank test for ABC, I appreciate the vote of confidence.

chrismccord

If you want a run-down of the 1.3 changes and the design decisions behidn those changes, check out the LonestarElixir Phoenix 1.3 keynote: https://www.youtube.com/watch?v=tMO28ar0lW8

To use the new phx.new project generator, you can install the archive with the following command:

$ mix archive.install https://github.com/phoenixframework/archives/raw/master/phx_new.ez

Bump your phoenix dep

Phoenix v1.3.0 is a backwards compatible release with v1.2.x. To upgrade your existing 1.2.x project, simply bump your phoenix dependency in mix.exs:

sheharyarn

/**
 * Axios Request Wrapper
 * ---------------------
 *
 * @author  Sheharyar Naseer (@sheharyarn)
 * @license MIT
 *
 */

import axios     from 'axios'

danielberkompas

defmodule MyApp.Scheduler do
  @moduledoc """
  Schedules a Mix task to be run at a given interval in milliseconds.

  ## Options

  - `:task`: The name of the Mix task to run.
  - `:args`: A list of arguments to pass to the Mix task's `run/1` function.
  - `:interval`: The time interval in millisconds to rerun the task.