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

[Unix(Ubuntu/MacOS)] bal dist pull command gives unexpected error text when the current update tool version is not the latest #196

Closed
NipunaMadhushan opened this issue Jan 13, 2022 · 2 comments
Labels

Comments

@NipunaMadhushan
Copy link
Contributor

NipunaMadhushan commented Jan 13, 2022

Label: High Priority

Description:
When we run the bal dist pull <distribution> command in Ubuntu or MacOS, it gives unexpected error text as follows. But the bal command runs without any issue after that. (Tested Version of Update Tool - 1.3.7-rc1, Latest version - 1.3.6)

Checking for newer versions of the update tool...
Downloading ballerina-command-1.3.6 100% [==========] 1/1 MB (0:00:00 / 0:00:0
Updating environment variables
The ‘ballerina’ command was changed to ‘bal’. Please use ‘bal’ command from now onwards.
Ie : $ bal build
     $ bal dist list
     $ bal dist update
Update tool version updated to the latest version: 1.3.6
Cleaning old files...

Update successfully completed

Fetching the 'slbeta5' distribution from the remote server...
Downloading slbeta5 100% [===================] 179/179 MB (0:01:10 / 0:00:00) 

Fetching the dependencies for 'slbeta5' from the remote server...
Dependency 'jdk-11.0.8+10-jre' is already available locally
'slbeta5' successfully set as the active distribution
/Library/Ballerina/bin/bal: line 131: unexpected EOF while looking for matching `"'
/Library/Ballerina/bin/bal: line 136: syntax error: unexpected end of file

Steps to reproduce:
Run the following command as a given distribution version exists or not exists.
bal dist pull <distribution>

Affected Versions:
Update Tool Version - 1.3.7-rc1

@udda1996
Copy link
Contributor

udda1996 commented Jan 9, 2024

Closing since this is fixed with #266

@udda1996 udda1996 closed this as completed Jan 9, 2024
Copy link

github-actions bot commented Jan 9, 2024

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.

@udda1996 udda1996 added the Reason/Invalid Issue is invalid. label Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants