Skip to content

Instantly share code, notes, and snippets.

Keybase proof

I hereby claim:

  • I am markstory on github.
  • I am markstory (https://keybase.io/markstory) on keybase.
  • I have a public key whose fingerprint is 4417 F052 3EC6 ECB5 B7C7 3622 3C07 0F5E 55B3 AEA0

To claim this, I am signing this object:

$ curl -k "https://cake.localhost.com/tasks/aaa%27;%3Cimg%20src=%27a%27%20onerror=%27alert%28%22XSS%22%29%27/"
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>
CakePHP: the rapid development php framework:
Errors </title>
<link href="/favicon.ico" type="image/x-icon" rel="icon" /><link href="/favicon.ico" type="image/x-icon" rel="shortcut icon" /><link rel="stylesheet" type="text/css" href="/css/cake.generic.css" /></head>
<body>
<div id="container">
diff --git a/Cake/ORM/BehaviorRegistry.php b/Cake/ORM/BehaviorRegistry.php
index db1aa77..06d2d63 100644
--- a/Cake/ORM/BehaviorRegistry.php
+++ b/Cake/ORM/BehaviorRegistry.php
@@ -14,6 +14,7 @@
*/
namespace Cake\ORM;
+use Cake\Cache\Cache;
use Cake\Core\App;
TL;DR Based on the assumptions below, the current cron strategy will be viable for a very very long time. In a worst case scenario, until we have 125,000 users paying through iOS.
At our last sprint demo, Mike and Warren asked about the scaling limits of the re-verification cron.
Assumptions:
* Reverifying each receipt will have a mean transaction time of 2seconds. This is higher than our initial estimates to allow some additional buffer room.
* Our IOS subscription patterns will have a similar histogram as our Payflow signups.
* We are ok with cron running for 18hrs consecutively. I chose 18hrs as I can only assume it will take several months to schedule a team to fix the issue in the future.
diff --git a/src/xmpp.coffee b/src/xmpp.coffee
index 69d4931..6c325ca 100644
--- a/src/xmpp.coffee
+++ b/src/xmpp.coffee
@@ -13,6 +13,7 @@ class XmppBot extends Adapter
rooms: @parseRooms process.env.HUBOT_XMPP_ROOMS.split(',')
keepaliveInterval: 30000 # ms interval to send whitespace to xmpp server
legacySSL: process.env.HUBOT_XMPP_LEGACYSSL
+ preferredSaslMechanism: process.env.HUBOT_XMPP_PREFERRED_SASL_MECHANISM
I have my model here:
// transactionmodel.js
function TransactionModel() {
var pg = require('pg');
var connectionString = "pg://chartjes:******@localhost:5432/ibl_stats";
this.client = new pg.Client(connectionString);
this.client.connect();
this.getCurrent = function(callback) {
// Front controller for our API
var application_root = __dirname;
var express = require("express");
var path = require("path");
var pg = require('pg');
var app = express.createServer();
var model = require('transactionmodel);
var tm = new model.TransactionModel(pg);
@markstory
markstory / gist:1935774
Created February 28, 2012 22:39
hash benchmarks
public function test() {
$this->autoRender = false;
$data = array(
array(
'Article' => array(
'id' => '1',
'user_id' => '1',
'title' => 'First Article',
'body' => 'First Article Body'
@markstory
markstory / gist:1770613
Created February 8, 2012 15:55
jenkins json url for getting people who broke the build.
http://jenkins/view/Radiator/api/json?tree=jobs[name,color,buildable,healthReport[description,score,iconUrl],builds[culprits[fullName],changeSet[items[msg]]]]
@markstory
markstory / gist:1711119
Created January 31, 2012 15:38 — forked from chartjes/gist:1711104
Hands On Node File System Exercise #3
var fs = require('fs');
function readFiveBytes(filePosition) {
var readFile = function (err, fd) {
if (err) {
console.log(err.message);
return;
}