Leopold Talirz

Thanks for reporting @janssenhenning, I [noticed this](https://github.com/aiidateam/aiida-plugin-cutter/commit/62d0fd7fa91a73ec041fe443fde373a9389002fd) in the AiiDA plugin cutter as well. Do we know what changed here? @sphuber

From the commit message > Then, to overcome the fact that we would still like to refer to the top-level module paths > (e.g. `aiida.orm.Computer` rather than `aiida.orm.computers.Computer`), > some...

I've run into this issue again. I will open a PR to move the `AutodocAliases` class inside aiida-core such that plugins can import them as well in their documentation.

+1 for adding parsing to the SLURM plugin to detect this error and return a corresponding exit code with instructions to provide a `metadata.options.queue_name` to fix this

+1 Just ran into this again

The error in the PR seems to indicate that `self._get_and_count('input_plugin', used)` can return an entry point or a string, depending on circumstances. A proper fix will need to take both...

I would second some flexibility here as well. In terms of usability, there is a precursor to this, which is to allow `verdi computer delete` - with a user prompt...

Hi @jbweston , just came across this issue. Process-level control on caching has actually been available in AiiDA pretty much since the introduction of caching, see [the docs](https://aiida.readthedocs.io/projects/aiida-core/en/develop/howto/run_codes.html#instance-level). It would...

Following a brief discussion with @giovannipizzi and @sphuber , here follows some inspection of one of the failed calculation nodes: ``` $ verdi process report 896549 *** 896549 [CELL_OPT]: None...

From our discussion, possible explanations include: 1) for whatever reason, the output of squeue is too long for the ssh buffer (~4 MB according to @giovannipizzi ) This is possible...