Description

Move the main documentation to the info repo to reflect the structure we have in our documentation.
Add links to the info, and some general info about this repo.

Description

Get an Error when loading "hello-data".

Steps to Reproduce

Just followed the Guide on the Qlikcore Getting Started Website
https://core.qlik.com/tutorials/hello-data/

Expected behavior

The output from the "hello-data" guide

$ npm run hello-data
Creating table data representation.
Creating and opening session using mixin.
Creating session object with movie titles.
Listing the 10 first movies:
2012
Armageddon
Avatar
Battleship
Cars 2
Cleopatra
Evan Almighty
Green Lantern
Harry Potter and the Half-Blood Prince
Indiana Jones and the Kingdom of the Crystal Skull
Session closed.

Actual behavior

node ./src/hello-data/hello-data.js

Creating session app on engine.
Creating data connection to local files.
Whoops! An error occurred. { Error: Invalid path
at Intercept.errorInterceptor (C:\Project\QlikCore_data\core-get-started-master\node_modules\enigma.js\enigma.js:2549:19)
at process.internalTickCallback (internal/process/next_tick.js:77:7) code: 4, parameter: 'Invalid path' }
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] hello-data: node ./src/hello-data/hello-data.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] hello-data 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! C:\Users\abs\AppData\Roaming\npm-cache_logs\2019-03-20T07_46_41_306Z-debug.log

Environment

Library

[x] Node.js
[ ] Browser

Operating system

[x] Windows
[ ] OSX
[ ] Linux

Versions

• Node.js: v11.6.0
• Browser: Google Chrome 72.0.3626.121
• Operating system: Windows 10

I am looking for someone that can help me since always getting this error in the Getting Started guide from Qlik Core. I try to run the "hello-data.js" but always get the Error Message above.

Description

Get an Error while the "Getting Started" guide. At the moment i load "hello-engine"

Steps to Reproduce

Just followed the Guide on the Qlikcore Getting Started Website
https://qlikcore.com/tutorials/hello-engine/

Expected behavior

The output from the "hello-engine" guide

npm run hello-engine
Creating and opening session.
Engine version retrieved: 12.91.0
Session closed.

Actual behavior

> node ./src/hello-engine/hello-engine.js

Creating and opening session.
Whoops! An error occurred. ErrorEvent {
  target:
   WebSocket {
     _events:
      { open: [Function],
        close: [Function],
        error: [Function],
        message: [Function] },
     _eventsCount: 4,
     _maxListeners: undefined,
     readyState: 3,
     protocol: '',
     _binaryType: 'nodebuffer',
     _closeFrameReceived: false,
     _closeFrameSent: false,
     _closeMessage: '',
     _closeTimer: null,
     _closeCode: 1006,
     _extensions: {},
     _isServer: false,
     _receiver: null,
     _sender: null,
     _socket: null,
     url: 'ws://localhost:19076/app',
     _req: null },
  type: 'error',
  message: 'connect ECONNREFUSED 127.0.0.1:19076',
  error:
   { Error: connect ECONNREFUSED 127.0.0.1:19076
       at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1113:14)
     errno: 'ECONNREFUSED',
     code: 'ECONNREFUSED',
     syscall: 'connect',
     address: '127.0.0.1',
     port: 19076 } }
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] hello-engine: `node ./src/hello-engine/hello-engine.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] hello-engine script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Library

[x ] Node.js
[ ] Browser

Operating system

[x ] Windows
[ ] OSX
[ ] Linux

Versions

• Node.js:
• Browser: Google Chrome 68.0.3440.106
• Operating system: Windows 10

Maybe someone can help me. Im always getting this error in the Getting Started guide from Qlik Core. The Server is started in Docker and then i try to run the "hello-engine.js" but always get the Error Message above.

A BlackDuck Protex scan failed on this repository.

Number of files needing identification: 5

If you are unsure how this process works, please contact trunk team on Slack.

No more automated issues will be created on this repository until this issue
is closed.

Please prioritize and solve this as soon as possible. If the files
has been identified already, you may ignore and close this issue.

Description

This is a setup issue (support?) and may not be related to a problem with the code. When I run npm start hello-engine I get the error below. I have started the Qlik Core engine on the machine in a background docker container using: docker-compose up -d. I have also run the npm install before issuing npm start. I may have missed a step or didn't get one of the dependencies correct.

Description

Throws an error type: "Loading Error", message: "Cannot open file: 'lib://f2f6d-8ba3e-b439f-bab28cce1db1/movies.csv'" while accessing hello-visualization application on browser after running npm run hello-visualization command.

Steps to Reproduce

1. ACCEPT_EULA=yes docker-compose up -d
2. npm install
3. npm run hello-visualization

Expected behavior

It should render visualization graph along with movies CSV data.

Actual behavior

Instead of rendering visualization graph, Throws an error Oops! Something went wrong

Environment

Library

[ ] Node.js
[ ] Browser(Chrome)

Operating system

[ ] Windows

Versions

• Node.js: 9.10.1
• Browser: 62.0
• Operating system: Windows 10(64Bit)

Provide the intermediate step, hello-data that will precede the full visualization example.

Since we are changing this example to be a Qlik Web platform recipie, we will remove the angular example

We should move this repo to a new repository with a better name since we are changing this to a web platform recipe.

1. Decide new repo name.
2. Move the code there.
3. Ask Andrée to change the cronjob to update this repo instead

Description

qlik-styles.css & require.js file is missing in the qlikcore/engine:12.171.0 container, which is required for qdt-components.

http://localhost:9076/resources/autogenerated/qlik-styles.css
http://localhost:9076/resources/assets/external/requirejs/require.js

Steps to Reproduce

1. Install qdt-components
2. Render visualization ie. qdtComponents.render('QdtViz', {id: 'eRSdp', height:'200px'}, element);

Expected behavior

qlik-styles.css & require.js file should be loaded into browser.

Actual behavior

qlik-styles.css & require.js file path was not found.

Environment

Library

[ ] Node.js
[ ] Browser

Operating system

[ ] Windows

Versions

• Node.js: 9.10.1
• Browser: 62.0
• Operating system: Windows 10(64Bit)

Description

During install of dependencies 14 vulnerabilities (3 moderate, 11 high) are reported.

Steps to Reproduce

1. run npm install

Expected behavior

If possible use versions of dependencies with fixes to security problems

Description

localhost appears to be hard coded in the getting started samples, which is fine if you are running on a server (or desktop OS) with a GUI and are just testing. However, if you want to access the development server remotely (i.e. from a host OS using a VirtualBox image) this does not work as the webpack configuration does not support anything but localhost.

Can I get the instructions on how to modify the host to 0.0.0.0 (open) or to a specific domain mask (a little more secure) for testing purposes?

Thanks,
Steve

• Hello Engine (current Hello World)
• Hello Data
• Hello Visualization

This issue contains a checklist of tasks that are needed before repo can be open sourced.

Checklist

• LICENSE file added to repo with a MIT license.
• Update package.json with the right info for author, description, license and name.
• Linting of code e.g. airbnb for node.js repo.
• Circle CI build to secure quality e.g. linting, tests, docker image.
• Update README.md to contain relevant info for the repo e.g. Contributions
• Add .editorconfig, .gitignore and .gitattributes

We should use picasso to generate our graphs and not d3.

We need to make sure that our "hello" examples work as supposed to. We don't want broken examples and confused end-users.

I was able to get this to work last week, but this week when I try to run "npm run hello-visualization" I get the following message:

npm run hello-visualization

[email protected] hello-visualization /vagrant/shared-content/files/qc-challenge/getting-started-with-web-platform
webpack-dev-server

sh: webpack-dev-server: command not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] hello-visualization: webpack-dev-server
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] hello-visualization 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! /home/vagrant/.npm/_logs/2018-02-18T16_51_36_721Z-debug.log

Attached is the referenced log file.
2018-02-18T16_51_36_721Z-debug.log

Any idea what is going on?

Description

We found potential security vulnerabilities in your dependencies

Following packages:
lodash / lodash

joyent / node-sshpk sshpk

unshiftio / url-parse

Without thinking much of it, I upgraded npm to 5.8.0 before doing a "sudo npm install" (I am on Mac).
That installation returns a "write after end" error though.

Downgrading npm to 5.6.0, then trying "sudo npm install" again, all works well.
Downgrading can be done using "npm install -g [email protected]"

Many of the packages have pretty old versions. Update to later versions.

We want to introduce users early on to understand and be able to write load scripts. By using halyard.js we hide that complexity and it makes it harder for users to learn and understand the power and usefulness of load scripts. halyard.js is convenient so we should still make references to it and encourage usage, but let users later decide on whether they want to use it or not.

To avoid conflicts with existing installations (e.g. Sense Desktop)

To reduce the number of software needed on the users machine to get started. We could increase the success rate for newcomers this way, and just declare the Node.js version needed in the README if they want to run it locally.

If we want to use Docker images, we need to ensure that it mounts in the volume properly so changes are picked up (e.g. by docker-compose up --build).

running "npm run hello-data" I'm getting the below error:

Creating table data representation.
Creating and opening session using mixin.
Woops! An error occurred. { type: 'Loading Error',
message: 'Cannot open file: 'lib://8e48b-8e86c-918d0-be267cf54fd8/movies1.csv'',
item: undefined,
qixError:
{ qErrorString: 'Cannot open file: 'lib://8e48b-8e86c-918d0-be267cf54fd8/movies1.csv'',
qLineEnd: '\r\n',
qLine: '"Movies":\nLOAD\n "Movie" AS "Movie",\n "Year" AS "Year",\n "Adjusted Costs" AS "Adjusted Costs",\n "Description" AS "Description",\n "Image" AS "Image"\nFROM [lib://8e48b-8e86c-918d0-be267cf54fd8/movies1.csv]\n(txt, delimiter is ',')',
qErrorDataCode: 'EDC_ERROR',
qMessage: { qMessageCode: 11020, qMessageParameters: [Array] } } }

it seems that it can't find the file "movies.csv" located in core-get-started-master\data folder.

Description

Npm run Visualization is erroring out

Steps to Reproduce

1. npm run hello-visualization

Expected behavior

[What you expected to happen]
Expecting to get localhost URL of weback dev server, to view the visualization

Actual behavior

[What actually happened]

[email protected] hello-visualization C:\Users\Santosh Chavan\Downloads\core-get-started-master
webpack-dev-server --config ./src/hello-visualization/webpack.config.js

events.js:183
throw er; // Unhandled 'error' event
^

Error: listen EACCES 0.0.0.0:8080
at Object._errnoException (util.js:1024:11)
at _exceptionWithHostPort (util.js:1046:20)
at Server.setupListenHandle [as _listen2] (net.js:1334:19)
at listenInCluster (net.js:1392:12)
at doListen (net.js:1501:7)
at _combinedTickCallback (internal/process/next_tick.js:141:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
at Function.Module.runMain (module.js:678:11)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] hello-visualization: webpack-dev-server --config ./src/hello-visualization/webpack.config.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] hello-visualization 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:

Environment

Library

[ ] Node.js

Operating system

[ ] Windows


### Versions

* Node.js: 
* Browser: 
* Operating system: 
* [Other relevant versions]

Webpack configurations, font files, HTML, etc. The two examples are so similar that it feels weird to not have them on a combined page instead and share resources. Would be easier for the end-users getting started to as it's way less code to read/learn.

If the build step before "Test of hello-visualization" fails (background), this build step will hang forever. There should be an upper timeout limit on this step to ensure non-hanging builds.

Update to latest versions of the web platforms we use (Enigma, Halyard) since Halyard now suports Enigma 2+