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]: Ballerina profiler fails to profile when there are mandatory configurable variable #41547

Closed
sameerajayasoma opened this issue Oct 19, 2023 · 2 comments · Fixed by #41538 or #41554
Assignees
Labels
Area/Profiler Issues related to Ballerina Profiler Priority/Blocker Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Team/jBallerina All the issues related to BIR, JVM backend code generation and runtime Type/Bug userCategory/Compilation

Comments

@sameerajayasoma
Copy link
Contributor

Description

I tried profiling the following service and got the following error in the console.
https://github.com/sameerajayasoma/ballerina-samples/tree/main/publish-hotel-reservations-to-kafka

error: value not provided for required configurable variable 'kafkaUrl'
        at sameera/publish_hotel_reservations_to_kafka:0.1.0(main.bal:6)
error: value not provided for required configurable variable 'kafkaTopic'
        at sameera/publish_hotel_reservations_to_kafka:0.1.0(main.bal:7)

Steps to Reproduce

No response

Affected Version(s)

No response

OS, DB, other environment details and versions

No response

Related area

-> Compilation

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

@sameerajayasoma sameerajayasoma added Type/Bug Priority/Blocker Area/Profiler Issues related to Ballerina Profiler labels Oct 19, 2023
@ballerina-bot ballerina-bot added needTriage The issue has to be inspected and labeled manually userCategory/Compilation labels Oct 19, 2023
@HindujaB HindujaB self-assigned this Oct 20, 2023
@HindujaB
Copy link
Contributor

This happens due to the current directory is set to /target/bin when running the profiler. Therefore, it doesn't read from the package directory as default.
As a workaround, we can use the BAL_CONFIG_FILES env variable with the Config.toml path.

I'll send a fix for this.

@warunalakshitha warunalakshitha added the Team/jBallerina All the issues related to BIR, JVM backend code generation and runtime label Oct 20, 2023
@HindujaB HindujaB removed the needTriage The issue has to be inspected and labeled manually label Oct 23, 2023
Copy link

github-actions bot commented Dec 5, 2023

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.

@HindujaB HindujaB added the Reason/EngineeringMistake The issue occurred due to a mistake made in the past. label Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area/Profiler Issues related to Ballerina Profiler Priority/Blocker Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Team/jBallerina All the issues related to BIR, JVM backend code generation and runtime Type/Bug userCategory/Compilation
Projects
None yet
4 participants