statik

Collection of Bazel open source python rules / forks from BazelCon 2019 python BOF

https://github.com/dropbox/dbx_build_tools

• Supports shipping python in the package
• Linking pip deps with cc_library
• Build all pip deps from source with the bazel cc toolchains
• building python from source
• support python2/3 on each binary, library, test

https://github.com/ali5h/rules_pip

statik

_video_file="${1}"
ffmpeg -i $_video_file -vf palettegen pal.png
ffmpeg -i $_video_file -i pal.png -lavfi paletteuse=bayer_scale=4:dither=bayer -r 18 video.gif

statik

  LambdaSortGDFindings:
    Type: 'AWS::Lambda::Function'
    Condition: AuditAccountPrimary # only in primary audit region, next to S3 bucket
    Properties:
      Code:
        ZipFile: |
          import boto3, csv, os, json
          s3_resource = boto3.resource('s3')
          s3_client = boto3.client('s3')
          

statik

import Html exposing (Html, Attribute)
import Html
import Html.Attributes
import Html.Events exposing (..)
import List
import String
------------------
--- HELPER CODE --
------------------

statik

## GistList: TODO for coders

statik

This note explains how to build Postgres from source and setup to debug it using LLDB on a Mac. I used this technique to research this article:
http://patshaughnessy.net/2014/10/13/following-a-select-statement-through-postgres-internals

1. Shut down existing postgres if necessary - you don’t want to mess up your existing DB or work :)

$ ps aux | grep postgres
pat               456   0.0  0.0  2503812    828   ??  Ss   Sun10AM   0:11.59 postgres: stats collector process       
pat               455   0.0  0.0  2649692   2536   ??  Ss   Sun10AM   0:05.00 postgres: autovacuum launcher process       
pat               454   0.0  0.0  2640476    304   ??  Ss   Sun10AM   0:00.74 postgres: wal writer process       
pat               453   0.0  0.0  2640476    336   ??  Ss   Sun10AM   0:00.76 postgres: writer process       

statik

buildscript {
    repositories {
        mavenCentral()
        maven { url 'https://oss.sonatype.org/content/repositories/snapshots' }
        maven { url 'http://clojars.org/repo' }
        maven { url 'http://dl.bintray.com/literalice/maven' }
    }
    dependencies {
        classpath 'org.robovm:robovm-gradle-plugin:1.0.1-SNAPSHOT'
        classpath 'clojuresque:clojuresque-base:1.6.0'

statik

# !/bin/bash

# Copyright (c) 2011 Float Mobile Learning
# http://www.floatlearning.com/
#
# Permission is hereby granted, free of charge, to any person obtaining 
# a copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation 
# the rights to use, copy, modify, merge, publish, distribute, sublicense, 
# and/or sell copies of the Software, and to permit persons to whom the 

statik

Description

Dashing widget to display the next and some subsequent Google Calendar events using the Google Calendar API v3.

I use this widget to display my shift calendar - see the screenshot below

Set up

This widget works with API v3 and requires a service account to be set up via the Google Developer's Console. Once a project is set up, enable the Calendar API. On the Credentials page create a new OpenID and download the p12 key file - set up the path to this file in the job file and grant the email address access to the relevant calendar.

statik

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style