wildart

module Logging
    abstract Logger
    type DefaultLogger <: Logger
        stream::IO
        color::Symbol
        DefaultLogger() = new(STDERR, :blue)
        DefaultLogger(color::Symbol) = new(STDERR, color)
    end

    fatal(l::Logger, msg) = print_with_color(l.color, l.stream, "FATAL:", chomp(string(msg)), "\n")

wildart

module ParHelperFuncs

using LMDB

export getSamplesFromDb, miniBatchSum

# we pull samples from the database
function getSamplesFromDb(env, idxs::Array{Int})
    txn = start(env)
    dbi = open(txn)

wildart

module Log

export AbstractLogger, call, logging
import Base: call, getindex

@enum Level OFF=0 FATAL=100 ERROR=200 WARN=300 INFO=400 DEBUG=500 TRACE=600 ALL=1000

abstract AbstractLogger
type LogWrapper{T <: AbstractLogger}
    logger::T

wildart

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

wildart

HTTP/2 protocol implementation

Abstract

This project aims to provide native implementation of HTTP/2, the second major version of the HTTP network protocol, for Julia language. This project will provide a RFC compliant implementation, which will consist of a multiple modules related to framing and application layers, as well as tests, examples of using in server and client modes, ALPN support and documentation.

Problem description

The Julia language has a family of packages, JuliaWebStack, that provide support of modern web technologies. Currently, the Julia language provides a support for HTTP protocol which is implemented as a wrapper around popular HTTP parser library implementation in C language, http-parser. In order to keep up with new trends in web technologies, we propose to implement newly approved version of HTTP protocol, HTTP/2.

wildart

Git server framework in libgit2

Abstract

Libgit2 has support for the client side of the negotiation, but it’s missing server-side capabilities. We propose a framework that will support smart exchange protocol which attributes to the client state and needs and provide event triggering mechanism for customizable actions on the server side.

wildart

# Requires to install pandas & pywin32, and of course MS Word installed.
import sys
import os
import win32com.client
import pandas as pd
import re
import numpy as np

JUNK_SYMBOLS = r'[\x07|\t|\x0b|\r|\x0c]'

wildart

#!/bin/sh

# This script must be executed in the repo where
# the *.ts files are.
# It will concatenate the segments into one temp
# file which ffmpeg will reencode the audio track.
# By default the ouptup filename is output.mp4
# but can be changed by providing the name as parameter.
#
# ffmpeg is required

wildart

Computer Information:
    Manufacturer:  Unknown
    Model:  Unknown
    Form Factor: Desktop
    No Touch Input Detected

Processor Information:
    CPU Vendor:  GenuineIntel
    CPU Brand:  Intel(R) Xeon(R) CPU           W3690  @ 3.47GHz
    CPU Family:  0x6

wildart

// Copyright (c) Microsoft Corporation.  All Rights Reserved.  See License.txt in the project root for license information.

// namespace FSI

open System
open System.Text
open System.Collections.Generic

/// System.Console.ReadKey appears to return an ANSI character (not the expected the unicode character).
/// When this fix flag is true, this byte is converted to a char using the System.Console.InputEncoding.