Describe the bug I get a access violation whenever I use khiva python lib

To Reproduce Run a simple program like:

from khiva.library import *
set_backend(KHIVABackend.KHIVA_BACKEND_OPENCL)
set_device(0)

from khiva.array import *
a = Array([1, 2, 3, 4, 5, 6, 7, 8])
a.display()

Expected behavior Application should run without exceptions

Screenshots

(base) C:\Progetti\Lab\Khiva\MyPythonSamples\HelloKhiva>python main.py
array
[8 1 1 1]
    1.0000
    2.0000
    3.0000
    4.0000
    5.0000
    6.0000
    7.0000
    8.0000

Traceback (most recent call last):
  File "main.py", line 7, in <module>
    a.display()
  File "C:\Anaconda3\lib\site-packages\khiva\array.py", line 323, in display
    KhivaLibrary().c_khiva_library.display(ctypes.pointer(self.arr_reference))
OSError: exception: access violation writing 0x00007FFE94CB180A

Environment information:

• OS: Windows 10
• Version 0.3.0

Make sure you have checked all steps below.

Description

• [ ] Here are some details about my PR, including screenshots of any UI changes:

Tests

• [ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

• [ ] My commits have been squashed if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

License

• [ ] Add a Mozilla Public License 2.0 license header to all the new files.

Documentation

• [ ] In case of new functionality, my PR adds documentation that describes how to use it.

Make sure you have checked all steps below.

Description

• [ ] Here are some details about my PR, including screenshots of any UI changes:

Tests

• [ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

• [ ] My commits have been squashed if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

License

• [ ] Add a Mozilla Public License 2.0 license header to all the new files.

Documentation

• [ ] In case of new functionality, my PR adds documentation that describes how to use it.

Describe the bug Khiva Python Bindings not passing all unit tests. Problems include seg fault or is not able to find required library in khiva function call.

To Reproduce Build khiva from source, install. Run install script to generate python bindings. Run unit tests from this repo.

Expected behavior All tests should pass.

Environment information: Ubuntu 18.04.4 LTS Python 3.6.9 Conan version 1.23.0 ArrayFire-v3.6.2

Additional context I joined the Gitter, it may be easier to continue the conversation there. Saw no errors during installation of both khiva and the python bindings. Prerequisites were installed prior to installing khiva.

Make sure you have checked all steps below.

Description

• [ ] Here are some details about my PR, including screenshots of any UI changes:

Tests

• [ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

• [ ] My commits have been squashed if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

License

• [ ] Add a Mozilla Public License 2.0 license header to all the new files.

Documentation

• [ ] In case of new functionality, my PR adds documentation that describes how to use it.

Make sure you have checked all steps below.

Description

• [ ] Here are some details about my PR, including screenshots of any UI changes:

Tests

• [ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

• [ ] My commits have been squashed if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

License

• [ ] Add a Mozilla Public License 2.0 license header to all the new files.

Documentation

• [ ] In case of new functionality, my PR adds documentation that describes how to use it.

• Add scamp algorithm
• Add get_chains function

Description

• [ ] Here are some details about my PR, including screenshots of any UI changes:

Tests

• [ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

• [ ] My commits have been squashed if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

License

• [ ] Add a Mozilla Public License 2.0 license header to all the new files.

Documentation

• [ ] In case of new functionality, my PR adds documentation that describes how to use it.

Make sure you have checked all steps below.

Description

• [ ] Here are some details about my PR, including screenshots of any UI changes:

Tests

• [ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

• [ ] My commits have been squashed if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

License

• [ ] Add a Mozilla Public License 2.0 license header to all the new files.

Documentation

• [ ] In case of new functionality, my PR adds documentation that describes how to use it.

Make sure you have checked all steps below.

Description

• [ ] Here are some details about my PR, including screenshots of any UI changes:

Tests

• [ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

• [ ] My commits have been squashed if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

License

• [ ] Add a Mozilla Public License 2.0 license header to all the new files.

Documentation

• [ ] In case of new functionality, my PR adds documentation that describes how to use it.

Reading from an Array:

• When an Array of real or complex numbers with more than two dimensions was benig converted to numpy this conversion didn't return an np.array with a proper shape.

Creating an Array:

• When an Array of real numbers with more than two dimensions was built. The shape in the device (arrayfire) was not correct.
• For complex numbers it occurrs with more than one dimension.

Make sure you have checked all steps below.

Description

• [ ] Here are some details about my PR, including screenshots of any UI changes:

Tests

• [ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

• [ ] My commits have been squashed if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

License

• [ ] Add a Mozilla Public License 2.0 license header to all the new files.

Documentation

• [ ] In case of new functionality, my PR adds documentation that describes how to use it.

This PR solves one issue when doing get_data().tolist() on a Khiva.Array with one element.

Description

• [ ] Here are some details about my PR, including screenshots of any UI changes:

Tests

• [ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

• [ ] My commits have been squashed if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

License

• [ ] Add a Mozilla Public License 2.0 license header to all the new files.

Documentation

• [ ] In case of new functionality, my PR adds documentation that describes how to use it.

Bumps numpy from 1.18.1 to 1.22.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Use of Khiva Python requires a lot of previous installation of Arrayfire and other dependencies. We could try to bundle most of the dependencies (Arrayfire at least) in order to make life easier to our users.