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

Application killed due to a panic has the exit code 0 #3796

Closed
azinneera opened this issue Dec 6, 2022 · 1 comment · Fixed by ballerina-platform/module-ballerina-http#1361
Assignees
Labels
module/http Points/0.5 Points/1 Priority/Low Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Team/PCM Protocol connector packages related issues Type/Bug
Milestone

Comments

@azinneera
Copy link

Description:
$subject. The exit code should be non-zero since it is an error state.
Introduced by #2714

Steps to reproduce:
Execute bal run on the below code:

import ballerina/http;
service / on new http:Listener(9090) {

    resource function get greeting() returns string {
        panic error("test panic");
    }
}

Output

$ bal run
Compiling source
        user/foo:0.1.0

Running executable

error: test panic
        at user.foo.0.$anonType$_0:$get$greeting(service.bal:5)
$ echo $?
0

Affected Versions:
At least 2201.4.0-SNAPSHOT

@azinneera azinneera changed the title Application killed due to panic has the exit code as 0 Application killed due to a panic has the exit code 0 Dec 6, 2022
@TharmiganK TharmiganK added module/http Team/PCM Protocol connector packages related issues labels Dec 6, 2022
@chamil321 chamil321 self-assigned this Dec 12, 2022
@chamil321 chamil321 moved this from BackLog to In Progress in Ballerina Team Main Board Dec 12, 2022
@chamil321 chamil321 moved this from In Progress to PR Sent in Ballerina Team Main Board Dec 12, 2022
@github-actions
Copy link

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.

@chamil321 chamil321 added the Reason/EngineeringMistake The issue occurred due to a mistake made in the past. label Dec 14, 2022
@chamil321 chamil321 reopened this Dec 14, 2022
@chamil321 chamil321 moved this from PR Sent to In Progress in Ballerina Team Main Board Dec 14, 2022
@chamil321 chamil321 moved this from In Progress to Done in Ballerina Team Main Board Dec 14, 2022
@TharmiganK TharmiganK added this to the 2201.3.1 milestone Dec 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module/http Points/0.5 Points/1 Priority/Low Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Team/PCM Protocol connector packages related issues Type/Bug
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants