[Bug]: Getting non-accessible symbol error for error intersections with details

[TharmiganK]

Description

I am getting the following error when I try to use error types from a external ballerina package. The error types are intersections with detail records:

ERROR [main.bal:(8:16,8:171)] attempt to refer to non-accessible symbol '$anonIntersectionErrorType$_2'
ERROR [main.bal:(10:16,10:170)] attempt to refer to non-accessible symbol '$anonIntersectionErrorType$_3'
error: compilation contains errors

Please note that this compiler errors are only shown at the very first build, after that the compilation is successful.

Steps to Reproduce

1. Create a ballerina library package:

$ bal new -t lib status-code-errors

2. Add the following errors.bal file to the package:

public type Detail record {
    int statusCode;
    map<string[]> headers;
    anydata body;
};

public type StatusCodeBindingErrorDetail record {
    *Detail;
    boolean fromDefaultStatusCodeMapping;
};

public type Error distinct error;

public type ClientError distinct Error;

public type ApplicationResponseError distinct (ClientError & error<Detail>);

public type ClientRequestError distinct (ApplicationResponseError & error<Detail>);

public type RemoteServerError distinct (ApplicationResponseError & error<Detail>);

public type StatusCodeResponseBindingError distinct ClientError & error<StatusCodeBindingErrorDetail>;

public type StatusCodeBindingClientRequestError distinct StatusCodeResponseBindingError & ClientRequestError;

public type StatusCodeBindingRemoteServerError distinct StatusCodeResponseBindingError & RemoteServerError;

3. Pack and push it to Ballerina local central:

$ bal pack; bal push --repository=local

4. Create a new Ballerina package:

$ bal new sample

5. Add the following local dependency to Ballerina.toml:

[[dependency]]
org = "tharmigan" # Change the org to your org
name = "status_code_errors"
version = "0.1.0"
repository = "local"

6. Replace the main.bal file content with the following:

// Replace the package organization with your organization
import tharmigan/status_code_errors as http;

isolated function createStatusCodeResponseBindingError(int statusCode, map<string[]> headers, anydata body = ()) returns http:StatusCodeResponseBindingError {
    string reasonPhrase = string `incompatible type found for the response with non-default status code: ${statusCode}`;
    if 100 <= statusCode && statusCode <= 399 {
        return error http:StatusCodeResponseBindingError(reasonPhrase, statusCode = statusCode, headers = headers, body = body, fromDefaultStatusCodeMapping = false);
    } else if 400 <= statusCode && statusCode <= 499 {
        return error http:StatusCodeBindingClientRequestError(reasonPhrase, statusCode = statusCode, headers = headers, body = body, fromDefaultStatusCodeMapping = false);
    } else {
        return error http:StatusCodeBindingRemoteServerError(reasonPhrase, statusCode = statusCode, headers = headers, body = body, fromDefaultStatusCodeMapping = false);
    }
}

7. Run the build for the first time:

$ bal build

Compiling source
        tharmigan/sample:0.1.0
ERROR [main.bal:(8:16,8:171)] attempt to refer to non-accessible symbol '$anonIntersectionErrorType$_4'
ERROR [main.bal:(10:16,10:170)] attempt to refer to non-accessible symbol '$anonIntersectionErrorType$_5'
error: compilation contains errors

8. Run the build for the second time:

$ bal build

Compiling source
        tharmigan/sample:0.1.0

Generating executable
        target/bin/sample.jar

Affected Version(s)

Ballerina SwanLake Update 9(2201.9.0)

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

[dulajdilshan]

We are not getting the error in the 2nd run of bal build because we get the error symbol accessible via the BIR correctly.

[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.