A loop isn't needed here at all. Just tail call parseDeclarationFlags
as needed to replay the logic.
function parseDeclarationFlags(): StatementFlags {
switch (token) {
case SyntaxKind.VarKeyword:
[{"ts":210342517955,"pid":84888,"tid":84888,"ph":"I","name":"TracingStartedInPage","id":1,"cat":"disabled-by-default-devtools.timeline","args":{"data":{"sessionId":"-1","page":"0xfff","frames":[{"frame":"0xfff","url":"webpack","name":""}]}}}, | |
{"ts":210342518021,"pid":84888,"tid":84888,"ph":"I","name":"TracingStartedInBrowser","id":2,"cat":"disabled-by-default-devtools.timeline","args":{"data":{"sessionId":"-1"}}}, | |
{"ts":210342596877,"pid":84888,"tid":84888,"ph":"b","name":"EntryOptionPlugin","id":3,"cat":"blink.user_timing"}, | |
{"ts":210342597223,"pid":84888,"tid":84888,"ph":"e","name":"EntryOptionPlugin","id":3,"cat":"blink.user_timing"}, | |
{"ts":210342786095,"pid":84888,"tid":84888,"ph":"b","name":"NodeSourcePlugin","id":4,"cat":"blink.user_timing"}, | |
{"ts":210342786350,"pid":84888,"tid":84888,"ph":"e","name":"NodeSourcePlugin","id":4,"cat":"blink.user_timing"}, | |
{"ts":210342786357,"pid":84888,"tid":84888,"ph":"b","name":"AMDPlugin","id":5,"cat":"blink.user_timing"}, | |
{"ts":210342786418,"pid":84888,"tid":84888,"ph |
A loop isn't needed here at all. Just tail call parseDeclarationFlags
as needed to replay the logic.
function parseDeclarationFlags(): StatementFlags {
switch (token) {
case SyntaxKind.VarKeyword:
/* Execute this on https://{your-team}.slack.com/customize */ | |
Array.from(document.querySelectorAll('.emoji_row a[href^="/team"]')).reduce((counts, node) => {const name = node.getAttribute('href').slice(6);return (counts[name] = (counts[name] || 0) + 1), counts}, {}); |
Populating this as we dig further into the platform, hopefully it'll be as useful to you as it is to use.
Change the IPs to the cluster's master node (has a star next to the name in kibana.) Most of the suggestions below come from the official Elastic ingestion performance guidelines.
Disables throttling of segment merges in Lucene.
If you are doing a bulk import and don’t care about search at all, you can disable merge throttling entirely. This will allow indexing to run as fast as your disks will allow.
I hereby claim:
To claim this, I am signing this object:
/* | |
place this somewhere above where your test files are in a directory called __mocks__, e.g. | |
__mocks__/ | |
react-redux.js | |
src/ | |
myTestFile.spec.js | |
Requires an updated version of node with ES6 Proxy support. | |
*/ |
#!/bin/bash | |
# adapted from http://stackoverflow.com/questions/10909685/run-parallel-multiple-commands-at-once-in-the-same-terminal | |
# but this version works in Ubuntu + Windows Subsystem for Linux | |
PID_LIST="" | |
for cmd in "$@"; do { | |
echo "Process \"$cmd\" started"; | |
eval $cmd & pid=$! |
<style> | |
form { | |
display: flex; | |
} | |
label { | |
order: 1; | |
} | |
input { |
Notes:
All actions should go in /actions.js
and all constants should go in /constants.js
(this is the one place where we deviate from keeping things together, as having all actions in one place makes understanding the entire application's potential state changes very straightforward)
The /index.js
should mount the application, set up the store, and contain application routing
The /**/index.js
in each child folder should contain that part of the state tree's reducer, action constants, and export /**/component.js
wrapped by connect()
from react-redux
If using Stylus, /style.styl
can glob import all child /**/*.styl
files so explicit tracking of them is not necessary
Each child /**/*.styl
should only contain styles relevant to that view, without side effects
The child /**/component.js
should be as simple and "pure" as possible, preferring stateless syntax where possible
If the child does not need a reducer ("pure" subview), /**/component.js
can be skipped and si