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

Incorporate compiler-plugin code-generators to unique service path generation logic #2487

Closed
ayeshLK opened this issue Dec 13, 2021 · 2 comments · Fixed by ballerina-platform/module-ballerina-websub#510
Assignees
Labels
module/websub Points/2 Reason/Complex Issue occurred due to complex scenario. Team/PCM Protocol connector packages related issues Type/Bug
Milestone

Comments

@ayeshLK
Copy link
Member

ayeshLK commented Dec 13, 2021

Description:

$subject

This is an improvement to #1813

Related to ballerina-lang change #33987

@ayeshLK ayeshLK self-assigned this Dec 13, 2021
@ayeshLK ayeshLK added Points/1.5 Team/PCM Protocol connector packages related issues labels Dec 13, 2021
@ayeshLK
Copy link
Member Author

ayeshLK commented Jan 30, 2022

Currently when using bal run command with automatic service-path generation enabled will give a runtime error.

error: Error retrieving Service Information: service path not found
	at ballerina.websub.2.Listener:retrieveGeneratedServicePath(sub_listener.bal:114)
	   ballerina.websub.2.Listener:executeAttach(sub_listener.bal:104)
	   ballerina.websub.2.Listener:attach(sub_listener.bal:72)

This happens due a limitation in our current approach. This could be resolved by using compile-time code-generators.

Hence marking this issue as a bug.

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

@ayeshLK ayeshLK added the Reason/Complex Issue occurred due to complex scenario. label May 6, 2022
@ayeshLK ayeshLK added this to the 2201.1.0 milestone May 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module/websub Points/2 Reason/Complex Issue occurred due to complex scenario. Team/PCM Protocol connector packages related issues Type/Bug
Projects
None yet
1 participant