Details
-
Type:
Story
-
Status: Won't Fix
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Epic Link:
-
Team:Science User Interface
Description
Here is the user (Joe Mazzarella) description of the issue. Essentially the first attempt to load/display FF content
in a browser session fails. We have seen cases where the browser has cached an older copy of the Firefly startup JavaScript file, and references that, after finding that the expiration date (HEAD) on the server is unchanged, and
uses the cached copy. This is the reference to the "caching problem" I believe.
[[Note: The rc.ned (release candidate) and ned.ipac (operations/public) systems use the same IRSA ops instance of Firefly, and the same NED backend in this case.]]
In Chrome, when I try to compare results from RC with Ops, the infamous JavaScript caching problem appears.
Details: On the homepage, a search on 'M82' returns a message "SED Plot Loading..." with no plot. Likewise the Phot & SED tab contains no Firefly content (all three divs are empty.)
https://rc.ned.ipac.caltech.edu/?q=byname&of=pre_text&list_limit=5&img_stamp=YES&hconst=73&omegav=0.73&obj_sort=RA%20or%20Longitude&omegam=0.27&extend=no&out_csys=Equatorial&objname=M82&corr_z=1&out_equinox=J2000.0
Interestingly, the same query on Ops at the same time does return FF content:
https://ned.ipac.caltech.edu/?q=byname&out_equinox=J2000.0&omegav=0.73&corr_z=1&hconst=73&objname=m82&out_csys=Equatorial&img_stamp=YES&of=pre_text&list_limit=5&obj_sort=RA%20or%20Longitude&omegam=0.27&extend=no
When I run the same query on RC.ned in a separate browser, it works fine.
About 10:00-10:30 AM (20180804), Loy and Jeff looked at this on MY computer. They looked at the debugger/Inspector in Chrome. WE simply clicked the RELOAD button and the Firefly content did load.
NED ENG-1072
Attachments
Issue Links
- relates to
-
DM-16689 Firefly results missing from Cone Search and ByName queries (sometimes)
- Won't Fix
Activity
Rick Ebert Try this:
In JS, open console browser. In console, enter > window.firefly.util.getVersion()
window.firefly.util.getVersion() 3/12/2019 the NED public facing UI:
- {BuildTime: "Tue Dec 18 14:03:21 PST 2018", BuildCommit: "615d048", BuildMajor: "1", BuildDate: "2018-12-18", BuildRev: "0", …}
- BuildCommit: "615d048"
- BuildDate: "2018-12-18"
- BuildMajor: "1"
- BuildMinor: "0"
- BuildNumber: "0"
- BuildRev: "0"
- BuildTag: "firefly_1.0.0_Final-0"
- BuildTime: "Tue Dec 18 14:03:21 PST 2018"
- BuildType: "Final"
- _proto_: Object
Just FYI-
I have noticed a caching issue with chrome under the following circumstances:
- Firefly is loaded in tab 1
- Firefly is loaded in tab 2
- New Firefly is built
- Tab 2 reloads but does not get the new firefly
In the case where there are multiple tabs with firefly they will opt for the cached version unless they are all deleted first or the cached is clear before the reload.
We do encounter with this when testing but is probably rare for end-users.
The issue will be addressed in IPAC Firefly project ticket: https://jira.ipac.caltech.edu/browse/FIREFLY-34
Being handled off-project.
To respond to Trey's question about version number: NED is using the API, and we don't know of a way to access (and have opened a ticket to provide an API to query) the version number.
At this point we believe it is the version we otherwise see on IRSA Ops:
v3.1.0_Final-3099 Built On:Wed Aug 15 16:24:59 PDT 2018