For years, people have been using jemalloc with ruby. There were various benchmarks and discussions. Legend had it that Jemalloc 5 didn't work as well as Jemalloc 3.
Then, one day, hope appeared on the horizon. @wjordan offered a config for Jemalloc 5.
FROM ruby:3.1.2-bullseye
RUN apt-get update ; \
| linters-settings: # 設定のデフォルト値は、https://github.com/golangci/golangci-lint/blob/master/.golangci.example.yml で確認できる | |
| depguard: # packagesに宣言されているモジュールの取り扱いに関するルール。ブラックリスト形式で使っているので、列挙したものを使うとエラーになる。 | |
| list-type: blacklist | |
| packages: | |
| - golang.org/x/xerrors # go 1.13で必要な機能はすべてerrorsに取り込まれたので使わない | |
| - github.com/rs/zerolog # ログ出力用のライブラリはプロジェクト内部に作ったファクトリ関数経由で使うため | |
| packages-with-error-message: | |
| - golang.org/x/xerrors: "エラー処理は標準のerrorsを使って下さい。スタックトレースが必要な場合のみpkg/errorsを使って下さい" | |
| - github.com/rs/zerolog: "ログ出力は example.com/myproject/logger#Newから利用して下さい" | |
| dupl: # コードのコピペを検出するルール。 閾値のトークン数を越えるものをエラーにする |
| import 'dotenv/config'; | |
| import { NestFactory } from '@nestjs/core'; | |
| import * as repl from 'repl'; | |
| import * as Logger from 'purdy'; | |
| const LOGGER_OPTIONS = { | |
| indent: 2, | |
| depth: 1, | |
| }; |
| begin | |
| require "bundler/inline" | |
| rescue LoadError => e | |
| $stderr.puts "Bundler version 1.10 or later is required. Please update your Bundler" | |
| raise e | |
| end | |
| gemfile(true) do | |
| source "https://rubygems.org" |
| begin | |
| require "bundler/inline" | |
| rescue LoadError => e | |
| $stderr.puts "Bundler version 1.10 or later is required. Please update your Bundler" | |
| raise e | |
| end | |
| gemfile(true) do | |
| source "https://rubygems.org" |
To get a private GitHub repo to work on Heroku, you can leverage the netrc buildpack in conjunction with the Heroku Ruby buildpack.
When setting up the Gemfile, make sure to use the https GitHub URL. This mechanism does not work with git+ssh.
gem "some_private_gem", git: "https://github.com/org/some_private_gem.git"git-prebase improves on 'git rebase -i' by adding information per commit regarding which files it touched.
Add the executable to your path and git will automatically expose it as
I fell in love with CoffeeScript a couple of years ago. Javascript has always seemed something of an interesting curiosity to me and I was happy to see the meteoric rise of Node.js, but coming from a background of Python I really preferred a cleaner syntax.
In any fast moving community it is inevitable that things will change, and so today we see a big shift toward ES6, the new version of Javascript. It incorporates a handful of the nicer features from CoffeeScript and is usable today through tools like Babel. Here are some of my thoughts and issues on moving away from CoffeeScript in favor of ES6.
While reading I suggest keeping open a tab to Babel's learning ES6 page. The examples there are great.
Holy punctuation, Batman! Say goodbye to your whitespace and hello to parenthesis, curly braces, and semicolons again. Even with the advanced ES6 syntax you'll find yourself writing a lot more punctuatio
| require 'openssl' | |
| require 'base64' | |
| # ===== \/ sign ===== | |
| # generate keys | |
| key = OpenSSL::PKey::EC.new("secp256k1") | |
| key.generate_key | |
| public_key = key.public_key | |
| public_key_hex = public_key.to_bn.to_s(16).downcase # public key in hex format |
| #!/usr/bin/env ruby | |
| # | |
| # `git pr-get 37` => Fetch Pull Resuest #37 and create branch `pr-37` | |
| # | |
| # Requirements: | |
| # Ruby | |
| # | |
| # Install: | |
| # $ chmod +x git-pr-get | |
| # $ mv git-pr-get (somewhere listed in PATH) |
