Severity

High

What release version, tag or commit-hash did you use?

main

Current Behavior

"Check licenses" and "ensure lifecycle management" fails for main

Steps to Reproduce

Trigger the workflows

Expected Behavior

They shall not fail

Possible Solution

No response

Additional Information

No response

Code of Conduct

• I agree to follow this project's "Code of Conduct".

Question

As of today it is not that well described how to cross-compile. Do we need to improve that?

Example 1: Doing a docker build

Using --platform seems to work

docker build -f app/Dockerfile --progress=plain --platform=linux/arm64 -t ex5:latest .

Example 2: Using build script

We also have a build script, but not really well described how to actively use it (in a devcontainer)

apt-get install g++-aarch64-linux-gnu
./install_dependencies.sh -x aarch64
./build.sh -x aarch64

When deploying the vehicle app from the C++ template in the k3d cluster the app is not starting properly. It fail with a MQTT communication related error.

Description

We remove support for K3D runtime and Dapr middleware

• Both technologies are too heavy weight for in-vehicle applications
• Flexibility offered is not applicable in in-vehicle hardware architectures
• Increase development effort in the Velocitas OSS team

Suggested Solution

No response

Alternatives

No response

Additional Context

No response

Hi,

The task "Local Runtime - Up" seems ok. But When I try to Debug with F5 errors happen :

I have few errors in C++ include path.

I have also warning :

[6/16/2023, 9:15:36 AM] For C++ source files, IntelliSenseMode was changed from "linux-clang-x64" to "linux-gcc-x64" based on compiler args and querying compilerPath: "/usr/bin/gcc"
[6/16/2023, 9:15:36 AM] For C source files, IntelliSenseMode was changed from "linux-clang-x64" to "linux-gcc-x64" based on compiler args and querying compilerPath: "/usr/bin/gcc"

Could you help me to resolve the issue ?

Regards,
Pat

Hi,

There is a mistake in the tutorial for the dummy payload, the datatype for the requestId is a string and an int is expected in the sample.

It should be:

{ "position": 300, "requestId": 123}

Regards,
Pat

Question

Is the template code built a binary, rather than a container based on different CPU arch, such arm64v8? If like that, could you provide some ways or scripts for building?

Severity

Critical

What release version, tag or commit-hash did you use?

f5aff07

Current Behavior

Sample App is not working on Kanto

Steps to Reproduce

1. Kanto Deploy Applicatoin
2. sudo kantui

Expected Behavior

Sample App is working fine on Kanto

Possible Solution

No response

Additional Information

No response

Code of Conduct

• I agree to follow this project's "Code of Conduct".

The job "Generate release documentation" of release workflow is failing, because the CI workflow isn't providing any documentation related artefacts.

Severity

Medium

What release version, tag or commit-hash did you use?

30029a9

Current Behavior

Due to unupdated version of devenv-runtimes in .velocitas.json
I can just use app name as sampleapp.
Please refer this issue devenv-runtimes

Steps to Reproduce

1. Change name of application in Template from sampleapp
2. Due to the preset of name in devenv-runtimes, we cannot use any other name

Expected Behavior

We need to use other application name

Possible Solution

Change
From
"name": "devenv-runtimes",
"version": "v2.2.1"
to
"name": "devenv-runtimes",
"version": "v2.2.2"

Additional Information

No response

Code of Conduct

• I agree to follow this project's "Code of Conduct".

Severity

Trivial

What release version, tag or commit-hash did you use?

main

Current Behavior

In the quick start referenced from the README it is described how to create a release which triggers the release workflow.

It does not state anything about that you might need to change job rights. When running release after using the template errors were reported, upload fails, see https://github.com/erikbosch/vehicle-example-app3/actions/runs/9466300965

This seems to be the same problem (and solution) as in the Python template, see:

• eclipse-velocitas/vehicle-app-python-template#240
• eclipse-velocitas/vehicle-app-python-template#242
• eclipse-velocitas/vehicle-app-python-template#246

Steps to Reproduce

As above

Expected Behavior

No errors

Possible Solution

It appears that my GITHUB_TOKEN for the created repo does not have write rights.
After adding rights like below the job could be run successfully.

I see two possible improvements:

• Either add the lines below to https://github.com/eclipse-velocitas/vehicle-app-python-template/blob/main/.github/workflows/release.yml
• Or describe in documentation that you may need to change your permissions for GITHUB_TOKEN

Additional Information

None

Code of Conduct

• I agree to follow this project's "Code of Conduct".

Env:

• Windows 10
• MS Visual Studio 1.73.1
• DevContainers Ext 0.262.3
• Docker Desktop 4.9.1
• Behind corporate proxy

Steps to reproduce:

1. Clone repo locally
2. Open in MS VSCODE
3. Reopen in container -> Container opened without error (time ~35 minutes)
4. Run Task: Local - Start VehicleApp runtime
5. Press F5

Observation: