---
# System prepended metadata

title: AiiDA Team Meeting 2021-11-17
tags: [team meetings]

---

# AiiDA Team Meeting 2021-11-17

###### tags: `team meetings`
###### time: 10am CET

[TOC]

### Present

* Giovanni
* Marnik
* Chris
* Simon
* Jason
* Francisco
* Louis


### Catch-up round

*Max. 3 minutes each*

Sebastiaan:
 * *Cannot join this time due to other meeting all morning*.
 * **Merged PRs**:
     * [Add support for Enum types to `aiida.orm.utils.serialize`](https://github.com/aiidateam/aiida-core/pull/5218): This now makes it possible to store `Enum` instances in the context of a `WorkChain` for example.
     * [`Node`: add the `is_valid_cache` property setter](https://github.com/aiidateam/aiida-core/pull/5207): Proposed official API to control caching on the node-level. This property allows to mark a single node as invalid for caching.
     * [`verdi code setup`: validate the uniqueness of label for local codes](https://github.com/aiidateam/aiida-core/pull/5215): Complement of #5205 to also support local codes. Uniqueness condition here has to be just on the code label, since local codes do not have an associated computer.
 * **Open PRs**:
     * [Add the `EnumData` data plugin to easily store Enum instances](https://github.com/aiidateam/aiida-core/pull/5225): New data plugin that makes it easy to store `Enum` members as nodes. Went through first round of review from GPizzi. Refined the interface and is ready for second round of review.
     * [`Code`: add `validate_remote_exec_path` method to check executable ](https://github.com/aiidateam/aiida-core/pull/5184): This could help prevent typos when setting up a code and subsequently the calculation failing. Went through a lot of back and forth on implementation and is now ready for final review.

Jason: 
  * Coding week: Add issue label `materials-science-related` and go through all `good first issue`. 
  * Question: there are some DOC issues should be fixed after switch the documentation theme to `sphinx-book-theme`, any progress on these?
  * AiiDA wechat official account: account orientation; do we really need it?
  
  
Simon:
  * AiiDA is (almost) ready to claim support for Python 3.10.
      * Pip installation with all extras succeeds.
      * Next step: Re-enable all tests.
      * Conda installation still fails (currently investigating why), but our installation instructions do not specify a specific Python version, so irrelevant in this context.

Francisco
  * CLI meeting summary:
      * Change `verdi database` command with `verdi storage` to unify there all commands related to the backend (database+repository). Commands:
          * `migrate`: moved to `verdi storage migrate`
          * `summary`: moved to `verdi storage info`
          * `version`: now reported on `verdi status`
          * `integrity`: database integrity checks were no longer necessary and have been removed
      * New command `verdi storage maintain`
          * Will perform maintainance operations on the repository and DB, that don't require to stop using the profile (warning it may be an "incomplete" optimization).
          * Flag `--full` / `--downtime` to perform a more complete maintainance that requires the user to stop using the profile (not enforced so far, see below). [`--full` is preferred]
          * Flag `--dry-run` (alternative?) to perform some heuristics that allows us to suggest to the user what kind of maintainance is needed.
      * New command `verdi storage info`
          * It returns some very basic summary information on the content of the database and repository (number of nodes, total size on disk, etc)
          * Flag `--statistics` to give a more detailed information.
          * Currently has the info of `verdi database summary` (and `--statistics` flag for `verdi database summary -v`)
  * DONE:
      * Replace `verdi database` with `verdi storage` - Merged ([PR#5228](https://github.com/aiidateam/aiida-core/pull/5228))
  * IN PROGRESS:
      * Apply requested modifications to the maintainance CLI - in progress ([PR#4965](https://github.com/aiidateam/aiida-core/pull/4965) is set as draft, will change when it is ready for review)
  * NEXT:
      * Retake the problem of blocking the profile (already started some time ago in [PR#5135](https://github.com/aiidateam/aiida-core/pull/5135))

Marnik:
  * Nothing to report on `aiida-core`

Giovanni:
  * Reminder on meeting with Sarus people on Dec 3rd, 11AM - please see docs/watch videos and prepare questions *beforehand*
  * FirecREST: Giovanni, Chris, Jason, Francisco got tokens to test it - we should try to test it before the coding week (I tried already, I can get the machines but I think the token does not allow yet to do much, e.g. listing files is not allowed)

Chris:
  * On holiday until next week 😎
  * Archive done but still tinkering
      * Added option not to create import group
      * Looking into updating group-nodes
  * 🧪 TESTS: SQLA Migrations -> pytest (#5192)
      * Held up because tests are hanging on GH Actions: how to properly reset database and release connection
      * If anyone want to have a look, or I'll re-look next week

### Specific Agenda Items
* Program for topics at the coding week