Janko Marohnić janko

Endpoints for uploading large files in multiple chunks. Also has the ability to resume if the upload is interrupted.

Typical usage:

Send a POST request to /files with the first chunk of the file and receive an upload id in return.
Repeatedly PATCH subsequent chunks using the upload id to identify the upload in progress and an offset representing the number of bytes transferred so far.
After each chunk has been uploaded, the server returns a new offset representing the total amount transferred.
After the last chunk commit the upload by passing its id to another endpoint such as POST /videos, POST /audio, etc.

Example:

Finding a Ruby memory leak using a time analysis

When developing a program in Ruby, you may sometimes encounter a memory leak. For a while now, Ruby has a facility to gather information about what objects are laying around: ObjectSpace.

There are several approaches one can take to debug a leak. This discusses a time-based approach, where a full memory dump is generated every, say, 5 minutes, during a time that the memory leak is showing up. Afterwards, one can look at all the objects, and find out which ones are staying around, causing the

Uploads large files in multiple chunks. Also has the ability to resume if the upload is interrupted.

Typical usage:

Send a POST request to /upload with the first chunk of the file and receive an upload id in return.
Repeatedly PATCH subsequent chunks using the upload id to identify the upload in progress and an offset representing the number of bytes transferred so far.
After each chunk has been uploaded, the server returns a new offset representing the total amount transferred.
After the last chunk commit the upload by passing its id to another endpoint such as POST /upload/commit/:id:

Last night, Brian Shirai unilaterally "ended" the RubySpec project, a sub-project of Rubinius (the alternative Ruby implementation which Brian was paid to work on full-time from 2007 to 2013). The blog post describing his reasons for "ending" the project led to a big discussion on Hacker News.

When a single, competing Ruby implementation tells that you its test suite is the One True Way, you should be skeptical. Charles Nutter, Ruby core committer and JRuby head honcho, spent a lot of time last night on Twitter talking to people about what this decision means. He's probably too busy and certainly too nice of a guy to write about what is a political issue in the Ruby community, so I'm going to do it on behalf of all the new or intermediate Rubyists out there that are confused by Brian's decision and what it me

To remove a submodule you need to:

Delete the relevant section from the .gitmodules file.
Stage the .gitmodules changes git add .gitmodules
Delete the relevant section from .git/config.
Run git rm --cached path_to_submodule (no trailing slash).
Run rm -rf .git/modules/path_to_submodule (no trailing slash).
Commit git commit -m "Removed submodule "
Delete the now untracked submodule files rm -rf path_to_submodule

What I actually did

/etc/security/limits.conf

elasticsearch hard memlock 100000

/etc/default/elasticsearch

	# you must also upload the public key as signing key to https://github.com/settings/keys
	git config --global user.signingkey '~/.ssh/id_rsa'
	git config --global commit.gpgsign true
	git config --global gpg.format ssh
	# (optional) this file enables `git log --show-signature` and contains email addresses associated with public keys
	git config --global gpg.ssh.allowedsignersfile '~/.ssh/git-signers'

	filter {
	if [type] == "elasticsearch" {
	grok {
	match => [ "message", "\[%{TIMESTAMP_ISO8601:timestamp}\]\[%{DATA:severity}%{SPACE}\]\[%{DATA:source}%{SPACE}\]%{SPACE}(?<message>(.\|\r\|\n)*)" ]
	overwrite => [ "message" ]
	}

	if "_grokparsefailure" not in [tags] {
	grok { # regular logs
	match => [

	#!/bin/bash
	set -e

	droplet=netflix
	interface=Wi-Fi
	us_regions=( nyc1 nyc2 nyc3 )

	random_region() {
	echo ${us_regions[RANDOM % ${#us_regions[@]}]}
	}