[atlas] Fetching results for ongoing measurements
- Previous message (by thread): [atlas] Fetching results for ongoing measurements
- Next message (by thread): [atlas] RRDs for pings with 25 probes.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sebastian Castro
sebastian at nzrs.net.nz
Thu Apr 25 22:41:27 CEST 2013
On 26/04/13 03:20, Robert Kisteleki wrote: > Hello, Hi Everyone, > >>>> The problem you're encountering exists because we are in the process of >>>> changing parts of the infrastructure and a backend component is refusing to >>>> comply. We're working on fixing this asap. >>>> >>> >>> I was wondering if there has been any resolution yet? I don't get an >>> error, https://atlas.ripe.net/atlas/udm.html simply comes up blank. > I was getting the same result (an empty page), so following the recommendation below (produce a firebug report), dusted off my Firefox and tried to generate one. The thing, it does work in Firefox, but it fails in Chrome! > It should work -- though it may take a second or two to load. If you can > reproduce it (after a page reload) then please drop us a mail to > atlas at ripe.net and tell us when this happened. (And if you're up to it, a > firebug report would be even more helpful!) The JavaScript console in Chrome reports two warnings, two errors: Error Viewport argument value "device-width;" for key "width" is invalid, and has been ignored. Note that ';' is not a separator in viewport values. The list should be comma-separated. udm.html:121 Warning Viewport argument value "0.6666;" for key "initial-scale" was truncated to its numeric prefix. Note that ';' is not a separator in viewport values. The list should be comma-separated. udm.html:121 Warning Viewport argument value "1.0;" for key "maximum-scale" was truncated to its numeric prefix. Note that ';' is not a separator in viewport values. The list should be comma-separated. udm.html:121 Error Uncaught TypeError: undefined is not a function ext-all.js:7 Hopefully it will help. > >> FWIW, I do not get a blank page, I can access My Measurements just >> fine, but I will get a "This section is temporarily disabled. We'll be >> fixing it soon though!" message when trying to see the latest msm >> results - which comes as no surprise given the recent announcements. > > The "last 100" page has been pretty under-used before, and will most likely > be superseded by the "probes" tab. This is already the case for ping type > measurements. Thanks for the feedback, Cheers, > > Regards, > Robert > > -- Sebastian Castro DNS Specialist .nz Registry Services (New Zealand Domain Name Registry Limited) desk: +64 4 495 2337 mobile: +64 21 400535
- Previous message (by thread): [atlas] Fetching results for ongoing measurements
- Next message (by thread): [atlas] RRDs for pings with 25 probes.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]