| import java.lang.ProcessBuilder.Redirect | |
| import java.util.concurrent.TimeUnit | |
| fun String.runCommand(workingDir: File? = null) { | |
| val process = ProcessBuilder(*split(" ").toTypedArray()) | |
| .directory(workingDir) | |
| .redirectOutput(Redirect.INHERIT) | |
| .redirectError(Redirect.INHERIT) | |
| .start() | |
| if (!process.waitFor(10, TimeUnit.SECONDS)) { |
I screwed up using git ("git checkout --" on the wrong file) and managed to delete the code I had just written... but it was still running in a process in a docker container. Here's how I got it back, using https://pypi.python.org/pypi/pyrasite/ and https://pypi.python.org/pypi/uncompyle6
apt-get update && apt-get install gdb
The documentation for how to deploy a pipeline with extra, non-PyPi, pure Python packages on GCP is missing some detail. This gist shows how to package and deploy an external pure-Python, non-PyPi dependency to a managed dataflow pipeline on GCP.
TL;DR: You external package needs to be a python (source/binary) distro properly packaged and shipped alongside your pipeline. It is not enough to only specify a tar file with a setup.py.
Your external package must have a proper setup.py. What follow is an example setup.py for our ETL package. This is used to package version 1.1.1 of the etl library. The library requires 3 native PyPi packages to run. These are specified in the install_requires field. This package also ships with custom external JSON data, declared in the package_data section. Last, the setuptools.find_packages function searches for all available packages and returns that
| #!/usr/bin/env python | |
| """ | |
| mocking requests calls | |
| """ | |
| import mock | |
| import unittest | |
| import requests | |
| from requests.exceptions import HTTPError |
Using py.test is great and the support for test fixtures is pretty awesome. However, in order to share your fixtures across your entire module, py.test suggests you define all your fixtures within one single conftest.py file. This is impractical if you have a large quantity of fixtures -- for better organization and readibility, you would much rather define your fixtures across multiple, well-named files. But how do you do that? ...No one on the internet seemed to know.
Turns out, however, you can define fixtures in individual files like this:
tests/fixtures/add.py
import pytest
@pytest.fixture
| //: # Swift 3: CGD and URLSessionDataTask | |
| import Foundation | |
| import PlaygroundSupport | |
| //: ### Create background queue | |
| let queue = DispatchQueue.global(qos: .background) | |
| //: ### Computed variable | |
| var time:DispatchTime! { |
| import asyncio | |
| from aiohttp import web | |
| import subprocess | |
| async def uptime_handler(request): | |
| # http://HOST:PORT/?interval=90 | |
| interval = int(request.GET.get('interval', 1)) | |
| # Without the Content-Type, most (all?) browsers will not render |
Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.
Translations: (No guarantee that the translations are up-to-date)
#SwitchResX Settings for LG 21:9 UltraWide
SwitchResX is a utility that allows users to override the default resolution settings in OSX. For more information, including download links, vist http://www.madrau.com/ .
##Disabling System Integrity Protection (SIP)
If you are running OSX 10.11 or higher, SIP must be disabled. To disable SIP do the following:
Table of Contents generated with DocToc