---
# System prepended metadata

title: AiiDA core coding days 06-07 Oct 2025
tags: [event]

---

# AiiDA core coding days 06-07 Oct 2025

###### tags: `event`

[toc]

## General Notes

### Topics

- Wrapping up open PRs, especially ones that can be sped-up by pair-review seems again like a useful task for all
- Discussion on standards:
    - https://github.com/aiidateam/aiida-core/issues/7028
    - gh tags, projects

### Wrap-up general notes

- v2.7.2 project: https://github.com/orgs/aiidateam/projects/24
- v2.8.0 project: https://github.com/orgs/aiidateam/projects/18
- v3.0.0 project: https://github.com/orgs/aiidateam/projects/21
- **Next core days on 3/4 Nov? -> raise your voice now or remain silent**
- Updates on 21 PRs and 13 issues :rocket: 
- 

## Notes people

### Miki

- PR [[# 7048]](https://github.com/aiidateam/aiida-core/pull/7048) on how to page for real-world workflows on aiida-core docs, should be ready (together with Natasha)
- Started working on [[# 1144]](https://github.com/aiidateam/aiida-quantumespresso/issues/1144) in aiida-quantumespresso about How-to on "customising inputs (together with Natasha)

### Julian

#### Release discussion

##### cherry-pick or auto-merge
- i'd say it's still reasonable to spend manual time cherry-picking the commits for a release
- avoids "acccidentally" releasing commits that were tagged to remain some time on `main` before being released -> should we add a tag for this??
- finding _forgotten_ commits can be achieved using `git` / `gh` cli tools, searching for commits that don't have any tags (I guess)

#### 2.7.2 patch release

* [[# 6993] Fix OperationalError on archive creation with PSQL backend by batching](https://github.com/aiidateam/aiida-core/pull/6993) -> reviews by DH and MBx. final touch on PR now
* [[# 6829] Improve information shown with `verdi storage info` (`--detailed`)](https://github.com/aiidateam/aiida-core/pull/6829) -> renamed "Show first and last node `ctime` for `verdi storage info --detailed`" and simplified scope. merged
* [#6978 `verdi storage info` CLI output unreadable with large `entities_starting_set`](https://github.com/aiidateam/aiida-core/issues/6978) -> not really a bug, but just ugly UI, and has been there for a long time. not sure if it's necessary for v2.7.2, but i'd say nice-to-have
* [#6926 Duplicated and poorly formatted information for `verdi code show`](https://github.com/aiidateam/aiida-core/issues/6926) -> didn't manage to work on this...
* Will have a look at [[# 6850] Improve tools for release](https://github.com/aiidateam/aiida-core/pull/6850) -> neither

#### Requires discussion

* [[# 6946] Add `--tmp-dir` option for archive creation](https://github.com/aiidateam/aiida-core/pull/6946) -> Pick up discussion again
* [[# 6659] Storage: Add `extend_json` Tag for Enhanced JSON Field Handling in `bulk_update` Operations](https://github.com/aiidateam/aiida-core/pull/6659) -> worth db migration

### Marnik

>[!Note]
>These are in order of priority. 

- [[#6376](https://github.com/aiidateam/aiida-core/issues/6376) | [#7037](https://github.com/aiidateam/aiida-core/issues/7037)]: `TrajectoryData` does not preserve periodicity information.

- [[#6994](https://github.com/aiidateam/aiida-core/issues/6994)]: Remove `stash`, `unstash` and `monitor` keys from the default inputs.
   → Even with an empty builder these are shown:

    ```
    Process class: ArithmeticAddCalculation
    Inputs:
    metadata:
      options:
        stash: {}
        unstash: {}
    monitors: {}
    ```
    
    which leads to added noise and distractions for the user. Considering these are somewhat niche use cases compared to e.g. the `resources`, I think we should remove them.

- [[#6196](https://github.com/aiidateam/aiida-core/pull/6196)]: copying between computers that have the same hostname.
    → Imagine you have run a DFT calculation on a `core.slurm` computer but want to run a post-processing script with `core.direct`. You have to set up two computers for this, but can't copy between them.
- [[#6185](https://github.com/aiidateam/aiida-core/pull/6185)]: Long-standing issue that (AFAIK) has never been resolved: Changing nested content of a stored `Dict` node does not raise [[#5970](https://github.com/aiidateam/aiida-core/issues/5970)]. Leads to some very nasty silent failures, e.g.:

   ```
    In [3]: d = Dict({'a': {'b': None, 'c': None}})
       ...: d['a']['b'] = 2
       ...: print(d.get_dict())
   {'a': {'b': 2, 'c': None}}

   In [4]: d.store()
       ...: d['a']['c'] = 3
       ...: print(d.get_dict())
   {'a': {'b': 2, 'c': None}}

* [[#7032](https://github.com/aiidateam/aiida-core/issues/7032)]:❓Should the options be hidden in the metadata?

### Daniel

- [[#7018]async_ssh: Use async semaphore instead of manual locking](https://github.com/aiidateam/aiida-core/pull/7018)
    - Write regression test
    - Benchmark for small files
    - Make it ready for patch release?

- [Fix OperationalError on archive creation with PSQL backend by batching #6993 ](https://github.com/aiidateam/aiida-core/pull/6993) -- Final review

- [Add dev dependency group #7040](https://github.com/aiidateam/aiida-core/pull/7040) -- Discussion of effective use of `uv`


### Xing

- investigate how to integrate `gui` cmd into `verdi`, [[CLI]: make top-level verdi pluginable via entry points](https://github.com/aiidateam/aiida-core/pull/7053)
- work on WorkGraph stable release

### Ali

- Documnetation discussion with Edan 
- [[# 6847] Use TextIOWrapper for opening file from repository in text mode](https://github.com/aiidateam/aiida-core/pull/6847)

### Edan

- Pydantic + REST API (I'll make my comments on the corresponding PRs)