Jerska

new Crawler({
  appId: "FIXME",
  apiKey: "FIXME",
  indexPrefix: "crawler_FIXME_",
  rateLimit: 4,
  maxUrls: 100,
  startUrls: ["FIXME"],
  ignoreQueryParams: ["utm_medium", "utm_source", "utm_campaign", "utm_term"],
  actions: [
    {

Jerska

// Make sure JSON keys are always in the same order, to allow for easy comparison
// This uses JSON.stringify's replacer twice:
// - once to get the list of keys, including of nested children
// - once in its lesser known form: as a array of keys
//     this filters keys to only ones in the list - (we don't use this feature)
//     but also sorts them, and this is why this is useful to us
export function stableJSONStringify(obj: any) {
  const allKeys: string[] = [];

  // Use the replacer function to get the keys

Jerska

/* eslint-disable no-console, import/no-extraneous-dependencies */

const micromatch = require('micromatch');

const NB_PAGES = 50 * 1000;
const NB_MATCHES = 2000;
const STAR_RATIO = 0.1;
const NEGATION_RATIO = 0.1;

const base = 'https://www.example.com';

Jerska

version: 2

jobs:
  build:
    environment:
      - TEST: true
    docker:
      - image: debian:stretch

    steps:

Jerska

Goals

The goal here was to solve our issues with Librato and Node.js only on a distributed system on Heroku. Here's the list of our issues / questions :

• we loved how easy the log drain was to use
• but we sent too much data to use the log drain w/ Heroku so some of it was skipped and the data was inconsistent
• we had multiple machines updating the same counters (e.g. # of concurrent jobs) and we wanted a rate (concurrent jobs / s accross all machines) : you can't do using counters
• librato-node uses counters internally when you call increment
• using librato-node in dev environment requires you to wrap it
• making a request to the API every 15s would induce performance issues

Jerska

diff --git a/public/shopify/assets/javascripts/algolia_autocomplete.js.liquid b/public/shopify/assets/javascripts/algolia_autocomplete.js.liquid
index 0130d68..be51693 100644
--- a/public/shopify/assets/javascripts/algolia_autocomplete.js.liquid
+++ b/public/shopify/assets/javascripts/algolia_autocomplete.js.liquid
@@ -19,7 +19,7 @@
         return algolia.render(params.templates.empty, props);
       },
       suggestion: function displaySuggestion (hit) {
-        return algolia.render(params.templates.hit, hit);
+        return algolia.render(params.templates.hit, Object.assign({ _distinct: params.distinct }, hit));

Jerska

[
  {
    "name": "DHgate Shopping - Buy Fashion Clothing, Electronic",
    "genres": [
      "Business",
      "Shopping"
    ],
    "price": 0,
    "rating": 4.5,
    "link": "http://itunes.apple.com/app/dhgate-shopping-buy-fashion-clothing-electronic/id905869418?uo=5&at=10l9yE",

Jerska

Technical Test

The goal of this test is to evaluate your ability to architecture a small full-stack app.

Instructions

The app you need to build is a small AppStore admin page. The initial import dataset can be found here: apps.json. The dataset being a bit old, don't be surprised by missing images.