Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:
-
Story Points:0.25
-
Epic Link:
-
Sprint:Sprint 33
Description
This task was created to serve as a reminder for a user requested task. It seems there may be 2 issues involved in this story.
The whole conversation with the user can be found in HELP-100, but the specific user question about this issue can be seen below:
"I wanted also to point a minor bug. When you select a local source for the plugin repository and also for the data sources IGB gives the following problem:
if the address is "C:\Documents", it automatically turns it into "file:\C:\Documents" and it gives an error. The user has to manually delete "C:\" to get "file:\Documents" .
The same thing happens with the "SOURCE" attribute of regions belonging to a local .gtf file. The "SOURCE" attribute value is "file:\C:\Documents\etc" and it can gives problem if someone wants to use directly that attribute to do something.
Obviously this is not a big problem, but I thought you wanted to know about it."
Attachments
![MSEdge - Win10TH2 [Running] - Oracle VM VirtualBox_025.png](/secure/attachment/13462/MSEdge%20-%20Win10TH2%20%5BRunning%5D%20-%20Oracle%20VM%20VirtualBox_025.png)
Activity
I have tested adding local app repositories on Windows and it works as expected. The "file:" prefix is expected, and is a valid file path in java on Windows. See attached screenshot for confirmation.
See attached screenshot to see the URL that gets populated into the URL field when adding a local repo on Windows. Notice, that the version used for testing was IGB 9.0.0.
It seems that this issue is still occurring. When a user attempts to add a local app repo, IGB prefixes the URL with "file:\C:\". The user mentioned that deleting the "C:\" from the URL allows the app repo to be added to IGB properly, but a user should not have to do this.
Moving this to the backlog since this has been verified as not yet fixed and it still needs to be fixed.
This is an older issue that we need to test to ensure that this is no longer a problem, however, I may need some assistance in looking at this story so that I can make sure to fully test the behavior described in this story.
Adding to the Testing Blocked column until I gather more information on this story.
Since this does not seem to be an outstanding issue, I will now close this story.