-
Steps to reproduce:
- create anomaly
- find it in `data/anomalies/all_anomalies.json`
- restart server
- create new anomaly
Now there is only new anomaly in `all_anomalies.json`
It happens bec…
-
Based on conversation with @petrk94
https://github.com/hastic/hastic-server/issues/90#issuecomment-407084240
-
Deleting any analytic units only deletes the first analytic unit in column.
Steps to reproduce:
- Create 2 or more analytic units
- Click delete button on any analytic unit except for the first one…
-
When 2 or more anomalies are using the same name the color choice starts to work wierd.
It only changes color for the last created anomaly with the same name. And it is not possible to change color…
-
I think we should rethink this part: https://github.com/hastic/hastic-server#known-bugs--issues
Let's check what is actual and make issues here on github if we have bugs.
-
You get this error when you've just created anomaly and there are no segments yet
![image](https://user-images.githubusercontent.com/1989898/41902714-ce2d6716-793c-11e8-940a-2010f9c5fda5.png)
-
Just run server and it will not start analytics
-
Now anomaly name is case-sensitive
If you create anomaly with capital letter(s) in name - you get "Not found" or "Internal error" alert
We should change all names to lower-case
-
Nodejs version 6.11.2 is LTS.So I need to use this nodejs version to run koa2.I followed tutorial and code is:
```js
require('babel-register');
const Koa = require('koa');
const app = new Koa();
…