Christopher Smith cbsmith
| From self[at]sungpae.com Mon Nov 8 16:59:48 2021 | |
| Date: Mon, 8 Nov 2021 16:59:48 -0600 | |
| From: Sung Pae <self[at]sungpae.com> | |
| To: [email protected] | |
| Subject: Permissive forwarding rule leads to unintentional exposure of | |
| containers to external hosts | |
| Message-ID: <YYmr4l1isfH9VQCn@SHANGRILA> | |
| MIME-Version: 1.0 | |
| Content-Type: multipart/signed; micalg=pgp-sha256; | |
| protocol="application/pgp-signature"; boundary="QR1yLfEBO/zgxYVA" |
I was talking to a coworker recently about general techniques that almost always form the core of any effort to write very fast, down-to-the-metal hot path code on the JVM, and they pointed out that there really isn't a particularly good place to go for this information. It occurred to me that, really, I had more or less picked up all of it by word of mouth and experience, and there just aren't any good reference sources on the topic. So… here's my word of mouth.
This is by no means a comprehensive gist. It's also important to understand that the techniques that I outline in here are not 100% absolute either. Performance on the JVM is an incredibly complicated subject, and while there are rules that almost always hold true, the "almost" remains very salient. Also, for many or even most applications, there will be other techniques that I'm not mentioning which will have a greater impact. JMH, Java Flight Recorder, and a good profiler are your very best friend! Mea
Based on D3.JS and Dimple, ChartFactory provide the ability to build quickly D3.JS charts without coding any lines of javascript. Just define your dashboard in a JSON and voila !
charts: [
{id:'chart1',
width:800,height:250,
xAxis:{type:'Category',field: "Month",orderRule:'Date'},
| # Author: Federico Mendez | |
| # _ _ _ _ _ _ | |
| # ___ _ _ <_> ___ | |__ ___ ._ _ _| | _| |<_> _ _ _| |_ _ _ | |
| # / . || | || |/ | '| / / <_> || ' |/ . | / . || || '_> | | | | | | |
| # \_ |`___||_|\_|_.|_\_\ <___||_|_|\___| \___||_||_| |_| `_. | | |
| # ___| _ _ _ _ <___' | |
| # | _>| |_ <_>| || | ___ ___ ._ _ _ ___ ___ _ _ ___ ___ ___ _ _ | |
| # | <__| . || || || | _ / | '/ . \| ' ' | <_-</ | '| '_><_> || . \/ ._>| '_> | |
| # `___/|_|_||_||_||_|<_>\_|_.\___/|_|_|_| /__/\_|_.|_| <___|| _/\___.|_| | |
| # |_| |
Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = [email protected]:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
| #!/usr/bin/python | |
| # Save this file as protoc-gen-depends, put it in your path (executable) and add "--depends-out=/whatever/path" to your protoc invocation | |
| from google.protobuf.compiler.plugin_pb2 import CodeGeneratorRequest,CodeGeneratorResponse | |
| from sys import stdin,stdout | |
| req = CodeGeneratorRequest() | |
| req.MergeFromString(''.join(stdin.readlines())) | |
| res = CodeGeneratorResponse() |
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real