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

[Bug]: Compilation failure occurs while using --cloud=docker flag in update 8 #7533

Closed
Thevakumar-Luheerathan opened this issue Jan 28, 2025 · 2 comments
Assignees
Labels
module/c2c Priority/High Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Status/Blocked Issues that are currently blocked. Type/Bug

Comments

@Thevakumar-Luheerathan
Copy link
Member

Description

The below code is giving error with --cloud=docker flag.

import ballerina/http;
import ballerina/log as _;

type CentralAPIConfig record {|
    string url;
    string certPath;
|};

configurable CentralAPIConfig centralConf = ?;

final http:Client centralApiClient = check new (centralConf.url, secureSocket = {cert: centralConf.certPath});

isolated service /repository/ballerina\-central on new http:Listener(9090) {

    isolated resource function get [string org]/[string package]/[string ver]/[string balafile]() returns http:Response|http:InternalServerError? {

    }

}

Steps to Reproduce

copy the above code and build it with --cloud=docker flag with update 8.8

Version

cloud-2.11.3, 2201.8.8

Environment Details (with versions)

No response

@anuruddhal
Copy link
Member

anuruddhal commented Feb 6, 2025

Fixed in https://central.ballerina.io/ballerina/cloud/2.11.4. The fix will be available with the next 2201.8.x release

@github-project-automation github-project-automation bot moved this from In Progress to Done in Ballerina Team Main Board Feb 6, 2025
Copy link

github-actions bot commented Feb 6, 2025

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.

@anuruddhal anuruddhal added the Reason/EngineeringMistake The issue occurred due to a mistake made in the past. label Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module/c2c Priority/High Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Status/Blocked Issues that are currently blocked. Type/Bug
Projects
Status: Done
Development

No branches or pull requests

2 participants