---
# System prepended metadata

title: AiiDA Team Meeting 2025-05-01
tags: [team meetings]

---

# AiiDA Team Meeting 2025-05-01

###### tags: `team meetings`
###### time: 14:00 CET

[TOC]

### Present

- Ali
- Alex
- Julian
- Miki
- Giovanni
- Marnik
    
### Catch-up round

*Max. 3 minutes each*


Ali:

- Discuss with the team, get rid of unsed functions in Transport interface: [#6832](https://github.com/aiidateam/aiida-core/issues/6832)
  - Remove with deprecation

- Closing the historical issues as stale(?) to have a cleaner repo?:smiling_face_with_tear: 
    - Alex: I think this does not help. I marked the issues with topics, and priorities and this did no help. We have too many issues and not enough dev.
    - Ali: the help will come afterwards, that we'll focus on new issues, and track closely to see what's actually happening.  
- Is anybody using [dev branch](https://github.com/aiidateam/aiida-core/tree/dev) ? No PRs is open from it.
   - Alex: I think it is there historically, sphuber mentioned to reduce CI time when CI time was expensive. I would keep it.
   - Ali: I don't know how that works maybe we can discuss?
- [`CI`: remove matrix redundancy between `test-install` and `ci`](https://github.com/aiidateam/aiida-core/pull/6780)
Alex: We have markers for each python version, so the dependencies are different for each python version, check uv.lock. There is no redundancy. That is why danielhollas does not agree with the change
- [`verdi smart cli`, AiiDA users benefit from LLM; a proof of concept.](https://github.com/aiidateam/aiida-core/pull/6834):
  - Fetch relevant info via RAG from verdi --help  -> pass that to an free LLM which is not learned by aiida database -> recieve prime results
  - E.g. 
  `$ verdi smart cli 'list my latest process that finished, show only one result'`
Generated command: `verdi process list -O id -D desc -S finished -l 1 `

- aiida-firecrst could be part of aiida-core (?)

Alex:
- Note that mypy checks were disabled (see PR [aiida-core/6827](https://github.com/aiidateam/aiida-core/pull/6827) for details), if you rebase now your PR you might get type checking errors
- aiida-core v2.7.0pre0 [aiida-core/6849](https://github.com/aiidateam/aiida-core/pull/6849):
    - @ali issue [aiida-core/6839](https://github.com/aiidateam/aiida-core/issues/6839) anything in the doc you want to change before the minore release? I think we can also change the doc in patch releases @jusongyu? --> Yes we can do this in patch release so we can do this later
    - `force kill` just requires PR [aiida-core/6793](https://github.com/aiidateam/aiida-core/pull/6793) final approval from @jusongyu but we already discussed so should be merged today/tomorrow
    - @julian are you okay if we squash and commit the PR into the prelease branch while continuing the review on the PR for the release? Tests seem fine (only new tests fail), we just need a rebase on main --> Julian is okay

Julian:

- Dumping:
    - Release feature as beta/experimental? Is this something we want to do in AiiDA? -> Check how it's done in pydantic PR
        - User API most likely stable (`verdi <process|group|profile dump` and `[Process|Group|Profile]Dumper.dump()`)
        - Config options (CLI & YAML) and log JSON might change -> Could add AiiDA version to files and verify.
        - Don't have to always be at 100% before putting anything out there (80/20 rule)
        - Don't shoot ourselves in the foot always having to be fully backwards compatible. We can still work on the implementation while people can already start using features, discovering bugs, edge cases, or additional feature requests.
    - [PR 6732](https://github.com/aiidateam/aiida-core/pull/6723) got quite messy over time (~170 commits), thinking of squashing all commits. Keeping history not important here.
    - @Alex: Yes, fine with the general approach of merging into pre-release (not very familiar with the procedure, so I trust you there). Will already squash all commits before.
    - Tests with PSQL fail via CI through GHA (sqlite works and PSQL also locally):
    ![image](https://hackmd.io/_uploads/Hk2iGCxelg.png)
    Anybody ever seen anything like that?
    --> Check past issues related to flaky tests



Xing:
- Recent improvements of WorkGraph web UI
    - Use [datagrid](https://www.datagrid.com/) for the WorkGraph table, same used in AiiDAlab QEapp.
    - Generalize the table to support multiple node types (WorkGraph, Process, Group etc), use server-side paging for the table to improve performance.
    - [PR 20](https://github.com/aiidateam/aiida-workgraph-web-ui/pull/20): Add graph view for WorkChain in the WorkGraph web UI, similar to WorkGraph.


Marnik:
* Nothing to report on the AiiDA-core front.

Miki
* Nothing to report, but next week we have the MSD meeting about StructureData 
