christopherdro

/**
 * @providesModule PatientList
 */
import NavigationBar from 'react-native-navbar';
import NavigationButtons from 'NavigationButtons';
import React, { ListView, Navigator, StyleSheet, Text, TextInput, TouchableHighlight, View } from 'react-native';
import { connect } from 'react-redux/native'

@connect(state => ({
  patients: state.patients

Willmo36

import most from 'most';

const load$ = most.fromEvent('DOMContentLoaded', document);
const tick$ = load$.flatMap(() => {
    return most.iterate((f) => f + 1, 0).take(5).flatMap(v => most.of(v).delay(v * 1000));
});

load$.observe(() => console.log('timer start'));
tick$.observe(x => console.log('timer tick', x));

lenaten

- create s3 bucket, for example: react.
- create cloudfront distributions	with these settings:
  - Default Root Object: index.html
  - Origin Domain Name: s3 bucket url, for example: react.s3.amazonaws.com
- add custom error page with these settings:
  - HTTP Error Code: 403: Forbidden
  - Customize Error Response: Yes
  - Response Page Path: /index.html
  - HTTP Response Code: 200: OK
  

briancavalier

This is an explanation of the extremely subtle problem in this most.js issue. This solution described isn't necessarily the best, or most rigorous solution. We're investigating other potential solutions, but wanted to record this information in case it's interesting to someone.

Background

One of the fastest ways to schedule a task in ES6 is to use a promise. They tend to use the fastest micro-tick scheduling option the platform provides. So, when a task is scheduled with scheduler.asap it doesn’t use setTimeout 0, it uses a promise to schedule itself, because that’s basically as close to zero-time as you can get in a platform independent way

given this:

jarretmoses

RN < 0.50 - watchman watch-del-all && rm -rf $TMPDIR/react-* && rm -rf node_modules/ && npm cache clean && npm install && npm start -- --reset-cache
RN >= 0.50 -  watchman watch-del-all && rm -rf $TMPDIR/react-native-packager-cache-* && rm -rf $TMPDIR/metro-bundler-cache-* && rm -rf node_modules/ && npm cache clean && npm install && npm start -- --reset-cache
RN >= 0.63 - watchman watch-del-all && rm -rf node_modules && npm install && rm -rf /tmp/metro-* && npm run start --reset-cache

npm >= 5 - watchman watch-del-all && rm -rf $TMPDIR/react-* && rm -rf node_modules/ && npm cache verify && npm install && npm start -- --reset-cache

Windows - del %appdata%\Temp\react-native-* & cd android & gradlew clean & cd .. & del node_modules/ & npm cache clean --force & npm install & npm start -- --reset-cache

TooTallNate

#!/usr/bin/env sh
#
# Usage:
#   USERNAME=abcd12345 PASSWORD=ghij67890 HOST=n8.io TARGET=alias.zeit.co ./updater.sh

URL="https://domains.google.com/nic/update"

HOST_IP=$(dig @8.8.8.8 +short A "$HOST" | sort | tail -1)
TARGET_IP=$(dig @8.8.8.8 +short A "$TARGET" | sort | tail -1)

jatins

This was built and written in 2016. While the project didn't gain much traction, the intro post is kept here for posterity.

---

Building realtime applications is hard.

A scalable solution to this problem involves many cumbersome steps:

• Hooking into replication logs of the database servers, or writing custom data invalidating logic for realtime UI components.
• Adding messaging infrastructure (e.g. RabbitMQ) to your project.
• Writing sophisticated routing logic to avoid broadcasting every message to every web server.
• Reimplementing database functionality in the backend if your app requires realtime computation (e.g. realtime leaderboards).

i-tu

  componentWillReceiveProps(nextProps) {
    if (nextProps.lastRequestedUserLocationAt > this.props.lastRequestedUserLocationAt) {
      this.centerMapToUser(nextProps.currentLocation);
    }

    if (nextProps.lastUpdated > this.props.lastUpdated) {
      const markers = this.createMarkersForLocations(nextProps);

      if (markers && Object.keys(markers)) {
        const clusters = {};

ahmdrz

package main

import (
	"fmt"
	"reflect"
)

type Test struct {
	Name string
}

kevin-smets

Requirements

Minikube requires that VT-x/AMD-v virtualization is enabled in BIOS. To check that this is enabled on OSX / macOS run:

sysctl -a | grep machdep.cpu.features | grep VMX

If there's output, you're good!

Prerequisites