🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Based on the Hypercube on the fly sample - I tried to select values within the different cubes using the selectValues(dimNo, values, toggleMode) function. Unfortunately this is not supported. Is there a way to select values in two or more different hypercubescubes?

Hi,

I got an error whenever I tried to export to Image of PDF the visualization with Qlik Sense 3.2.

Qlik Sense API are not supported for this export ?

Regards,
Thibaut

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Hi Stefan,

First of all, thank for the all content that you are creating for the community and developper !

I would like to know if you have encounter the same problem as me with the creation on the fly of hypercube in Qlik Sense Desktop.

I found recently that there is memory leak when you create hypercube with the method "app.createCube", not in QlikSense core because with the method destroySessionObject it release instantly the cpu of the hypercube. But in the browser the memory is never release.

For example in your extension (hypercubeonthefly)
I have create a new project with 10 000 row with this script
LOAD
RowNo() as field,
RowNo()*rand() *150032104 as field2
AutoGenerate(10000);

And after we configure the dimension with field and expression with sum(field2).
The result is a bit slow but that's not the problem here (the object is loading 5000 rows).
But when you change the dimension to field2 to field (repeatly) you can see the cpu of your computer increase but it's never collected by the GC.

I have see this problem with the google Tools by taking snapshot. Every action increase by 3-4 mo so after 10 action it become 40 mo leak and etc ...

Of course the leak occur only when you recreate the hypercube via the method createCube() (so when you modify the layout.props).

So my question are :

• Should we use this method in Qlik Sense desktop ?
• Is this a known problem for extension ?
• Is there a way to release the memory or a method to destroy the object/reference correctly ?

Thanks again !

Regards,
Thibaut