[Bug]: The cannot complete future twice error does not have any information such as stack trace

[TharmiganK]

Description

Related to this issue: https://github.com/wso2-enterprise/internal-support-ballerina/issues/837

An error: cannot complete the same future twice. is thrown from the lang without any logs where the error is originated. Since it is a panic behaviour, we expects more information.

Steps to Reproduce

Could not able to reproduce the issue

Affected Version(s)

Ballerina Swan Lake Update 7

OS, DB, other environment details and versions

No response

Related area

-> Runtime

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

[warunalakshitha]

Runtime actually throw a ballerina error if same future called twice, but it seems http or any other package seems not catch properly. Since future complete happens in many places, it might be hard to track too. We have fixed this issue in update 11 with new concurrency model (Now API user cant complete same future twice via API), but there are some implementation implications to fix in previous versions.

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