Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interrupt at "Executing: 'fhir cache'" #27

Open
ThimoHoelter opened this issue Oct 1, 2023 · 3 comments
Open

Interrupt at "Executing: 'fhir cache'" #27

ThimoHoelter opened this issue Oct 1, 2023 · 3 comments

Comments

@ThimoHoelter
Copy link

Checked all requirments and sushi runs without an error.
Tried to run the extension on my repo and this happens.

Output:
codfsh: Info
[INFO] Extension started
[INFO] Checking FHIR Packages Dependencies...
[INFO] Found Workspacefolder in 'c:\Users...'
[INFO] Found sushiConfigPath: c:\Users...\sushi-config.yaml
[INFO] Found resourceFolder: c:\Users...
[INFO] Executing: 'fhir cache'

codfsh: Firely Terminal
fhir chache

@SvenSommer
Copy link
Contributor

Hey @ThimoHoelter,

  1. I assume you are using the Windows OS.
  2. Which version of the extension do you have installed?
  3. Can you provide me with a screenshot of your extension settings? For example, here is mine:
    image

@ThimoHoelter
Copy link
Author

Hey @SvenSommer,
thank you for your help.

  1. Yes, Windows 11.
  2. v1.0.9

Screenshot 2023-10-04 094434

The validator version i used is 6.1.9.

@SvenSommer
Copy link
Contributor

Hello @ThimoHoelter,

I apologize for the late response; I've been quite busy. However, I've now found a potential game-changer that should help resolve the setup problems you're experiencing with the codfsh extension.

What is a Devcontainer?

A devcontainer, or Development Container, is a concept used in Visual Studio Code that allows you to define and use a Docker container as a full-featured development environment. It encapsulates the development environment's configuration, dependencies, and tooling in a container, ensuring that all developers working on a project have a consistent environment.

This approach has several benefits:

  • Consistency: Every developer works in an environment with the same configuration, tooling, and dependencies, regardless of their local machine setup.
  • Isolation: The development environment is isolated from the local machine, reducing the "works on my machine" problem.
  • Portability: The environment can be easily shared and replicated across different machines and teams.

For more detailed information, you can refer to the official VSCode documentation on devcontainers.

How to Use the Devcontainer for codfsh

In the spec-TemplateForSimplifierProjects repository, we have a preconfigured devcontainer that is tailored for FHIR development with the codfsh extension. This devcontainer includes all necessary dependencies and configurations, including the correct setup for the fhir command.

To use this in your repository, you can add the .devcontainer folder from the spec-TemplateForSimplifierProjects repository to your project. Here's the link to the folder in the feature branch: spec-TemplateForSimplifierProjects/.devcontainer.

Once you've added this folder to your project, you can reopen your project in VSCode in the devcontainer environment. VSCode will build the Docker container based on the configuration and use it as your development environment.

Steps to Follow

  1. Copy the .devcontainer folder: Clone or download the .devcontainer folder from the provided link and add it to the root of your project.

  2. Reopen in Container: Open your project in VSCode, and you'll be prompted to reopen it in a container. If not, you can use the command palette (Ctrl+Shift+P) and select "Remote-Containers: Reopen in Container".

  3. Test the codfsh Extension: Once your project is open in the devcontainer, try running the codfsh extension again.

I hope this solution helps resolve the issues you're facing. Please let me know if you encounter any problems or have any questions about setting up or using the devcontainer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants