# AiiDA Team Meeting 2022-07-13 ###### tags: `team meetings` ###### time: 10am CET [TOC] ### Present * Sebastiaan * Marnik * Jason * Giovanni * Kristjan ### Catch-up round *Max. 3 minutes each* Sebastiaan: * **Pull requests** * REST API: make the profile configurable as request parameter [[#5054]](https://github.com/aiidateam/aiida-core/pull/5054): Benchmarked by Kristian with Materials Cloud. Original average request 0.30s. With new implementation (no profile switching) 0.34s. (with profile switching) 0.51s. So there is a performance hit when switching profiles, as expected, but this should not affect bulk requests that operate on the same profile in quick succession. Since it is an optional feature, I would suggest to merge this. * Deprecate `Profile.repository_path` [[#5516]](https://github.com/aiidateam/aiida-core/pull/5516): reviewed and adapted, will merge today. * **Issues** * Listing pseudopotential familes prints an entry for every pseudo in the family. [[#5535]](https://github.com/aiidateam/aiida-core/pull/5535): Tracked this down to an important bug in the `QueryBuilder` when appending a `Node` followed by a `Group`. This broke in v2.0 and should be fixed a.s.a.p. I suspect this might also be the root cause of the pseudo CLI of `aiida-vasp` breaking. Created [a PR](https://github.com/aiidateam/aiida-core/pull/5554) with a test demonstrating the problem. Not sure how to fix it yet. Jason: * The [containerized code PR](https://github.com/aiidateam/aiida-core/pull/5507) is ready to review. However, I find the `Singularity` on CSCS has a bit different behaviour than it installed in local machine. * The `nightly` CI test is failed. https://github.com/aiidateam/aiida-core/actions/workflows/nightly.yml * Some update about [computer/code registery](https://github.com/aiidateam/aiida-code-registry/issues/63) after brainstorm with Leopold. * Need a new CLI read jinja2 template and translate to what aiida-core can understand now? * Should be only one computer template and codes folder for per resource (cluster/computational center). Marnik: * Managed to get `aiida-hyperqueue` working again on Eiger, still have to release a new version of the plugin. Once this is done I'll also add a reference to this in the `aiida-core` documentation. I was thinking maybe a "How to"? Kristjan: * Is the process of creating a patch release (e.g. now, 2.0.2) documented? Giovanni: * Did anyone work on the news of the new AiiDA website and/or checked it? ### Specific Agenda Items