| From 6765c58a27f9a9ef4a7820e10259e464d9fbbb33 Mon Sep 17 00:00:00 2001 | |
| From: isaacs <i@izs.me> | |
| Date: Mon, 2 Mar 2015 16:03:34 -0800 | |
| Subject: [PATCH] http: do not reuse socket on error responses | |
| Some servers (in this case, CouchDB) behave very oddly when you attempt | |
| to re-use a socket that returned an error response. | |
| --- | |
| lib/_http_client.js | 4 ++++ | |
| 1 file changed, 4 insertions(+) |
| - (void)viewDidLoad | |
| { | |
| [super viewDidLoad]; | |
| UITextView *textView = [[UITextView alloc] init]; | |
| textView.translatesAutoresizingMaskIntoConstraints = NO; | |
| [self.view addSubview:textView]; | |
| [self.view addConstraints:[NSLayoutConstraint constraintsWithVisualFormat:@"V:|-[textView]-|" options:0 metrics:nil views:NSDictionaryOfVariableBindings(textView)]]; | |
| [self.view addConstraints:[NSLayoutConstraint constraintsWithVisualFormat:@"H:|-[textView]-|" options:0 metrics:nil views:NSDictionaryOfVariableBindings(textView)]]; | |
| NSString *htmlString = @"<h1>Header</h1><h2>Subheader</h2><p>Some <em>text</em></p><img src='http://blogs.babble.com/famecrawler/files/2010/11/mickey_mouse-1097.jpg' width=70 height=100 />"; |
| # (create oauth2 tokens from Google Console) | |
| client_id = "" | |
| client_secret = "" | |
| # (paste the scope of the service you want here) | |
| # e.g.: https://www.googleapis.com/auth/gan | |
| scope = "" | |
Redis is a commonly used as a mini 'database' for caching, shared queues, and similar. It is generally fast & reliable for these tasks. Redis does not support nested data types, and misusing redis for this type of thing can end up with the situation described below.
Imagine that we want to store the following data in Redis:
set users '[{"user":"tim", "pages": ["aaa", "bbb"]}]'
| <% | |
| require 'cgi' | |
| require 'uri' | |
| def attribute(name, value, force_string = false) | |
| if value | |
| value_string = | |
| if force_string | |
| '"' + value + '"' | |
| else |
| // tokenize(str) | |
| // extracts semantically useful tokens from a string containing English-language sentences | |
| // @param {String} the string to tokenize | |
| // @returns {Array} contains extracted tokens | |
| function tokenize(str) { | |
| var punct='\\['+ '\\!'+ '\\"'+ '\\#'+ '\\$'+ // since javascript does not | |
| '\\%'+ '\\&'+ '\\\''+ '\\('+ '\\)'+ // support POSIX character | |
| '\\*'+ '\\+'+ '\\,'+ '\\\\'+ '\\-'+ // classes, we'll need our |
I want to be extremely clear about three things. First, this is my personal opinion – insert full standard disclaimer. Second, this is not a condemnation of everyone at RSA, present and past. I assume most of them are pretty okay, and that the problem is confined to a few specific points in the company. However, “unknown problem people making major decisions at RSA” is a bit unwieldy, so I will just say RSA. Third, I'm not calling for a total boycott on RSA. I work almost literally across the street from them and I don’t want to get beat up by roving gangs of cryptographers at the local Chipotle.
RSA's denial published last night is utter codswallop that denies pretty much everything in the world except the actual allegations put forth by Reuters and hinted at for months by [other sources](http://li
| require 'monitor' | |
| class IdWorker | |
| attr_reader :worker_id, :datacenter_id, :reporter, :logger, :sequence, :last_timestamp | |
| TWEPOCH = 1288834974657 | |
| WORKER_ID_BITS = 5 | |
| DATACENTER_ID_BITS = 5 | |
| MAX_WORKER_ID = (1 << WORKER_ID_BITS) - 1 |
I've recently shifted from a straight engineering job to a job with a "dev/ops" title. What I have discovered in operations land depresses me. The shoemaker's children are going unshod. Operations software is terrible.
What's driving me craziest right now is my monitoring system.
What I have right now is Nagios.
