[Bug]:CCE when sync-send-action used with check expression

[prakanth97]

Description

function testAsyncSendAsExpressionWithCheckExpr() {
    worker w1 {
        () a = check (5 ->> w2);
    }

    worker w2 returns error? {
        int x = <- w1;
    }

    map<error?> mapResult = wait {w1, w2};
}

Got error: error while generating method '$lambda$_0' in class 'prakanth/test/0/main' for above example.

Steps to Reproduce

No response

Affected Version(s)

2201.6.0 and master

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

[prakanth97]

#38245 In this fix we are making async-send an action node. With that fix below code is valid. For that also we are getting the same error as above.

function testAsyncSendAsExpressionWithCheckExpr() {
    worker w1 {
        () a = check 5 -> w2;
    }

    worker w2 returns error? {
        int x = <- w1;
    }

    map<error?> mapResult = wait {w1, w2};
}

[prakanth97]

function testAsyncSendAsExpressionWithMatchStmt() {
    worker w1 {
        match (5 ->> w2) {
            () => {
                return;
            }

            _ => {
                panic error("This is an error");
            }
        }
    }

    worker w2 {
        int x = <- w1;
    }

    _ = wait {w1, w2};
}

sync-send-action or async-send-action with match statement results in exception from code-gen error while generating method '$lambda$_2' in class 'prakanth/test/0/main'

[github-actions]

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.