problems.rst 1.7 KB

  1. Common problems and solutions
  2. =============================
  3. List set of common problems and their solution.
  4. Most functions are however rather safe and should return an exception in the wrapper, instead of crashing the kernel.
  5. Note that even if the MvK crashes with such an error as mentioned below, this only breaks the violating task and all other tasks are left unharmed.
  6. As such, it is possible for a user to log in again on a different task, although there is no continuation.
  7. body_id is None
  8. ---------------------
  9. This error likely means that a function is called that was never defined: the declaration was found, but the definition is empty.
  10. None has no length
  11. ------------------------
  12. Operations done on an error value, such as a dictionary read on a non-existing element
  13. pickle.PicklingError: Can't pickle <function X>
  14. -----------------------------------------------
  15. The wrapper for manual activities relies on the multiprocessing library to spawn the various user-side interactions.
  16. As such, the different functions are spawned in different Python processes, to allow for multiple such functions to execute simultaneously, as needed for process enactment.
  17. While this allows for multiple such functions to execute simultaneously, as needed for process enactment, `this is not 100% supported in Python for Windows<>`_.
  18. Your error is therefore likely caused by the multiprocessing library wanting to pass a function (or something else...), which it could not.
  19. For example, it is not possible on Windows to give a local (nested) function as parameter to *transformation_execute_MANUAL*, as local functions cannot be pickled.
  20. On Linux, that would work perfectly fine.