reimagined / hacker-news-resolve Goto Github PK

Importing only one HackerNews story affects invoking more than 30000 tcp + udp packets, which is very redundant. Performing import is necessary when event structure had been changed. It's not very frequent operation while development, but non rare too.

For example, only resolving IP-address of HackerNews website by DNS performs hundred and hundred times repeatably. import_hn.log.
In comparation, two minutes of 4K youtube video consumes only approximate 1900 tcp packets and works very well. youtube.log

Issue faced on Ubuntu 16.04.1 LTS on VirtualBox 5.2.0, virtual network adapter is:
82540EM Gigabit Ethernet Controller (pm pcix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation, autonegotiation=on broadcast=yes driver=e1000 driverversion=7.3.21-k8-NAPI duplex=full ip=10.0.2.15 latency=64 link=yes mingnt=255 multicast=yes port=twisted pair speed=1Gbit/s)

Most likely, that current importer implementation performs big traffic flood, which can be handled by physical adapter, but very much for virtual.

npm run import  ✓  11912  11:35:57

[email protected] import /Users//Documents/hacker-news-resolve
babel-node ./import
Import has been started. Press Crtl+C to stop import
Data importing from news.ycombinator.com [===-----------------] 142/989Fetch timeout (10000 ms)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] import: babel-node ./import
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] import script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users//.npm/_logs/2017-10-31T08_37_40_174Z-debug.log

Original resolve-scripts package supports ability for setup ROOT_DIR, which meant application can be run for specified subdirectory. But Hacker-news front-end part itself does not support this ability

Describe the bug
Read-model

To Reproduce
Steps to reproduce the behavior:

1. Read-model projection

await store.update('Users', { id: aggregateId }, { $set: changes })

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.