[bug]: Unable to read empty (= never used) meta directory (readDirAsync): not exists

[klein0r]

No existing issues.

• There is no existing issue for my problem.

Description

I'm not able to read an empty and never used meta object. Expected an empty array instead.

Reproduction instruction

1. Use the instance configuration to create a new meta object in io-package

  "instanceObjects": [
    {
      "_id": "",
      "type": "meta",
      "common": {
        "name": {
          "en": "Meta storage for user files",
          "de": "Meta-Speicher für Benutzerdateien",
          "ru": "Meta Storage для файлов пользователей",
          "pt": "Meta de armazenamento para arquivos de usuário",
          "nl": "Meta opslag voor gebruikersbestanden",
          "fr": "Stockage Meta pour les fichiers utilisateur",
          "it": "Meta storage per i file utente",
          "es": "Meta almacenamiento para archivos de usuario",
          "pl": "Meta storage for user files",
          "uk": "Зберігання мета для файлів користувачів",
          "zh-cn": "用户档案的储存"
        },
        "type": "meta.user"
      },
      "native": {}
    }
]

2. Start the instance and ensure the object has been created
3. Use the files tab in admin and access the meta object
4. Use const files = await this.readDirAsync(this.adapter.namespace, '/');

The last 2 steps will fail (Error: Not exists) until a file has been created.

JS-controller version

7.0.6

Node version

v20.18.1

[klein0r]

The new meta object should check and create an empty directory here:

Or the handling of the missing directory must be changed:

ioBroker.js-controller/packages/db-objects-file/src/lib/objects/objectsInMemFileDB.js

Line 641 in f005b73

throw new Error(utils.ERRORS.ERROR_NOT_FOUND);

[foxriver76]

From my Point of view Admin should create this directory, Meta does not imply that there is a Directory. It seems something has changed for frontend Adapters recently, see also #2992

[klein0r]

Directories are a core feature and not related to admin. Why should the admin adapter create a directory for other instances?

The admin ui was just an additional example to confirm the issue. I've the same problem with the adapter utils.

[foxriver76]

Ah it is trashschedule dir, so you would expect that creating a meta object creates a directory in your scenario? I mean that was never the case so this would be a feature request not a bug report imo

[klein0r]

I would expect that readDir returns an empty array (because I've created a meta object). Not exists sounds like something is wrong.

[Apollon77]

Thats a good question ... On one side dirs are automatically created as soon as first file is placed there ... so with this is would be (even if it never was that way) consequent to also return each non existing dir as empty ...