Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 9.0.2 Minor Release
-
Labels:
-
Story Points:1
-
Sprint:B - Summer 2018, Summer 2018 Part 2, Summer 2018 Part 3, Fall 2018 1, Fall 2018 Sprint 2
Description
IGB appears hard-coded to request resources from BioViz.org and a few other sites.
This makes testing and developing IGB challenging for developers because they need access to the access_logs of BioViz to add new features or fix bugs. It also makes updating URLs difficult and may slow down startup if IGB tries to access resources that no longer exist.
Task is:
Identify all places in IGB code base with URLs. Document these:
- Report name of file with hard-coded URL (.java or other resources)
- Report URL
Request BioViz.org access_log from Dr. Loraine. Do not attach here to respect users' privacy.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
IGB appears hard-coded to request resources from BioViz.org.
This makes testing and developing IGB challenging for developers because they need access to the access_logs of BioViz to add new features or fix bugs. * Identify all places in IGB code bas with hard-coded URLs. Document here. Ideas for how to fix/improve: * IGB installer Install4J uses codeBaseUrl setting in its configuration file to configure future updates. Use this to determine IGB code base URL. * Create a new IGB Service (new module) that provides URLs on demand for key IGB functions, e.g., IGB Help Page, IGB Code Base, etc. |
IGB appears hard-coded to request resources from BioViz.org and others.
This makes testing and developing IGB challenging for developers because they need access to the access_logs of BioViz to add new features or fix bugs. It also makes updating URLs difficult and may slow down startup if IGB tries to access resources that no longer exist. * Identify all places in IGB code base with hard-coded URLs. Document these here. * Develop a plan for how to improve the situation. Thought for how to fix/improve: * IGB installer Install4J uses codeBaseUrl setting in its configuration file to configure future updates. Use this to determine IGB BioViz code base URL. * Create a new IGB Service (new module) that provides URLs on demand for key IGB functions, e.g., IGB Help Page, IGB Code Base, etc. |
| Description |
IGB appears hard-coded to request resources from BioViz.org and others.
This makes testing and developing IGB challenging for developers because they need access to the access_logs of BioViz to add new features or fix bugs. It also makes updating URLs difficult and may slow down startup if IGB tries to access resources that no longer exist. * Identify all places in IGB code base with hard-coded URLs. Document these here. * Develop a plan for how to improve the situation. Thought for how to fix/improve: * IGB installer Install4J uses codeBaseUrl setting in its configuration file to configure future updates. Use this to determine IGB BioViz code base URL. * Create a new IGB Service (new module) that provides URLs on demand for key IGB functions, e.g., IGB Help Page, IGB Code Base, etc. |
IGB appears hard-coded to request resources from BioViz.org and others.
This makes testing and developing IGB challenging for developers because they need access to the access_logs of BioViz to add new features or fix bugs. It also makes updating URLs difficult and may slow down startup if IGB tries to access resources that no longer exist. * Identify all places in IGB code base with hard-coded URLs. Document these here. * Develop & implement solution. Thought for how to fix/improve: * IGB installer Install4J uses codeBaseUrl setting in its configuration file to configure future updates. Use this to determine IGB BioViz code base URL. * Create a new IGB Service (new module) that provides URLs on demand for key IGB functions, e.g., IGB Help Page, IGB Code Base, etc. |
| Description |
IGB appears hard-coded to request resources from BioViz.org and others.
This makes testing and developing IGB challenging for developers because they need access to the access_logs of BioViz to add new features or fix bugs. It also makes updating URLs difficult and may slow down startup if IGB tries to access resources that no longer exist. * Identify all places in IGB code base with hard-coded URLs. Document these here. * Develop & implement solution. Thought for how to fix/improve: * IGB installer Install4J uses codeBaseUrl setting in its configuration file to configure future updates. Use this to determine IGB BioViz code base URL. * Create a new IGB Service (new module) that provides URLs on demand for key IGB functions, e.g., IGB Help Page, IGB Code Base, etc. |
IGB appears hard-coded to request resources from BioViz.org and others.
This makes testing and developing IGB challenging for developers because they need access to the access_logs of BioViz to add new features or fix bugs. It also makes updating URLs difficult and may slow down startup if IGB tries to access resources that no longer exist. * Identify all places in IGB code base with hard-coded URLs. Document these here. * Develop & implement solution. Thought for how to fix/improve: * IGB installer Install4J uses codeBaseUrl setting in its configuration file to configure future updates. Use this to determine IGB BioViz code base URL. * Create a new IGB Service (new module) that provides URLs on demand for key IGB functions, e.g., IGB Help Page, IGB Code Base, etc. |
| Rank | Ranked higher |
| Sprint | B - Summer 2018 [ 48 ] | B - Summer 2018, Summer 2018 Part 2 [ 48, 49 ] |
| Rank | Ranked higher |
| Summary | identify and parameterize all references to BioViz.org in IGB code base | identify hard-coded URLs in IGB code base |
| Description |
IGB appears hard-coded to request resources from BioViz.org and others.
This makes testing and developing IGB challenging for developers because they need access to the access_logs of BioViz to add new features or fix bugs. It also makes updating URLs difficult and may slow down startup if IGB tries to access resources that no longer exist. * Identify all places in IGB code base with hard-coded URLs. Document these here. * Develop & implement solution. Thought for how to fix/improve: * IGB installer Install4J uses codeBaseUrl setting in its configuration file to configure future updates. Use this to determine IGB BioViz code base URL. * Create a new IGB Service (new module) that provides URLs on demand for key IGB functions, e.g., IGB Help Page, IGB Code Base, etc. |
IGB appears hard-coded to request resources from BioViz.org and a few other sites.
This makes testing and developing IGB challenging for developers because they need access to the access_logs of BioViz to add new features or fix bugs. It also makes updating URLs difficult and may slow down startup if IGB tries to access resources that no longer exist. Task is: Identify all places in IGB code base with URLs. Document these: * Report name of file with hard-coded URL (.java or other resources) * Report URL Request BioViz.org access_log from Dr. Loraine. Do not attach here to respect users' privacy. |
| Assignee | Ann Loraine [ aloraine ] | Sneha Ramesh Watharkar [ jdaly ] |
| Assignee | Sneha Ramesh Watharkar [ jdaly ] |
| Assignee | Sneha Ramesh Watharkar [ jdaly ] |
| Rank | Ranked higher |
| Summary | identify hard-coded URLs in IGB code base | Identify hard-coded URLs in IGB code base |
| Assignee | Sneha Ramesh Watharkar [ jdaly ] | Kiran Korey [ kkorey ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Attachment | hard_coded_urls_formatted.txt [ 14123 ] | |
| Attachment | hard_coded_urls_original.txt [ 14124 ] |
| Attachment | hard_coded_https_urls.txt [ 14125 ] |
| Assignee | Kiran Korey [ kkorey ] | Sneha Ramesh Watharkar [ jdaly ] |
| Status | In Progress [ 3 ] | Open [ 1 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Assignee | Sneha Ramesh Watharkar [ jdaly ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Sneha Ramesh Watharkar [ jdaly ] |
| Assignee | Sneha Ramesh Watharkar [ jdaly ] | Ann Loraine [ aloraine ] |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Sprint | B - Summer 2018, Summer 2018 Part 2 [ 48, 49 ] | B - Summer 2018, Summer 2018 Part 2, Summer 2018 Part 3 [ 48, 49, 50 ] |
| Rank | Ranked higher |
| Status | Needs 1st Level Review [ 10005 ] | Reviewing [ 10301 ] |
| Status | Reviewing [ 10301 ] | Open [ 1 ] |
| Assignee | Ann Loraine [ aloraine ] | Sneha Ramesh Watharkar [ jdaly ] |
| Assignee | Sneha Ramesh Watharkar [ jdaly ] | Ann Loraine [ aloraine ] |
| Status | Open [ 1 ] | Needs 1st Level Review [ 10005 ] |
| Status | Needs 1st Level Review [ 10005 ] | Ready for Pull Request [ 10304 ] |
| Assignee | Ann Loraine [ aloraine ] | Sneha Ramesh Watharkar [ jdaly ] |
| Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
| Assignee | Sneha Ramesh Watharkar [ jdaly ] | Ann Loraine [ aloraine ] |
| Status | Pull Request Submitted [ 10101 ] | Needs Testing [ 10002 ] |
| Assignee | Ann Loraine [ aloraine ] |
| Rank | Ranked higher |
| Sprint | B - Summer 2018, Summer 2018 Part 2, Summer 2018 Part 3 [ 48, 49, 50 ] | B - Summer 2018, Summer 2018 Part 2, Summer 2018 Part 3, Fall 2018 1 [ 48, 49, 50, 51 ] |
| Rank | Ranked lower |
| Rank | Ranked higher |
| Sprint | B - Summer 2018, Summer 2018 Part 2, Summer 2018 Part 3, Fall 2018 1 [ 48, 49, 50, 51 ] | B - Summer 2018, Summer 2018 Part 2, Summer 2018 Part 3, Fall 2018 1, Fall 2018 Sprint 2 [ 48, 49, 50, 51, 52 ] |
| Rank | Ranked lower |
| Resolution | Done [ 10000 ] | |
| Status | Needs Testing [ 10002 ] | Closed [ 6 ] |
| Assignee | Sneha Ramesh Watharkar [ jdaly ] |
| Workflow | Loraine Lab Workflow [ 18040 ] | Fall 2019 Workflow Update [ 19915 ] |
| Workflow | Fall 2019 Workflow Update [ 19915 ] | Revised Fall 2019 Workflow Update [ 22034 ] |