-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
While SUSHI runs inside the Devcontainer quite well, HAPI seems to fail:
[INFO] Extension started
[INFO] Checking FHIR Packages Dependencies...
[INFO] Found Workspacefolder in '/workspaces/basprofiler-r4'
[INFO] Found sushiConfigPath: /workspaces/basprofiler-r4/sushi-config.yaml
[INFO] Found resourceFolder: /workspaces/basprofiler-r4/
[INFO] Executing: 'fhir cache'
[INFO] All FHIR Packages Dependencies checked.
[INFO] Started Sushi...
[INFO] Found Workspacefolder in '/workspaces/basprofiler-r4'
[INFO] Found sushiConfigPath: /workspaces/basprofiler-r4/sushi-config.yaml
[INFO] Found resourceFolder: /workspaces/basprofiler-r4/
[INFO] Executing: 'sushi "/workspaces/basprofiler-r4/"'
[INFO] Sushi completed.
[INFO] Found Workspacefolder in '/workspaces/basprofiler-r4'
[INFO] Found sushiConfigPath: /workspaces/basprofiler-r4/sushi-config.yaml
[INFO] Found resourceFolder: /workspaces/basprofiler-r4/
[ERROR] Error: ENOENT: no such file or directory, open 'extension-output-gematikde.codfsh-#3-codfsh: Sushi'
[INFO] Found Workspacefolder in '/workspaces/basprofiler-r4'
[INFO] Found sushiConfigPath: /workspaces/basprofiler-r4/sushi-config.yaml
[INFO] Found resourceFolder: /workspaces/basprofiler-r4/
[ERROR] Error: ENOENT: no such file or directory, open 'extension-output-gematikde.codfsh-#1-codfsh: Info'
This is using codfsh v1.0.9.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels