Issue with Sankey package earlier today / how to protect my site from this?

[Wouter]

Hi all,

Is it correct that there was an issue with the Sankey package earlier today? I experienced it but cannot find any info about it. None of the charts on my pages like this one were loading until I disabled the loading of the Sankey chart. I noticed that the Sankeys were also not showing up at the Google charts example page.

All seems to be fine now. How can I harness my pages from issues like this?

- I could use a frozen version rather than current but I am not sure whether this was related to a release? Was the latest release indeed done on February 23, 2016  as I see on this page?

- would it be better to do the content delivery from my own site rather than using the https://www.gstatic.com/charts/loader.js ? The loader loads packages and I have no idea how I could do that :)

- Can I make sure that other charts are loaded if there is an issue with one (type of) chart? In this case my page has 7 core charts, 1 table and 1 Sankey and nothing loaded due to the issue with the Sankey.

Many thanks in advance, Wouter (I use Google charts a lot and really like it!!!)

[Daniel LaLiberte]

Hi Wouter,

Nothing has changed with the current release of Google Charts for a few months.  The current release is actually 45.2, with a few refactoring changes relative to version 45.  

So i don't know what might have caused the sankey chart to fail for you earlier, but perhaps you were actually experiencing a more general outage, but other (non-sankey) charts were still working because of caching.  Just a wild speculation.  Glad it is working for you again.

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/22f4f7ed-b5ec-4334-b7d7-d660858cc396%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Daniel LaLiberte

dlaliberte@Google.com   5CC, Cambridge MA

[Daniel LaLiberte]

One more thing.  The frozen versions might work more reliably for you, but perhaps not, depending on the precise nature of the failure you were seeing.  At least the code should not be changing, but whether you get the code could still change.

On Mon, Nov 20, 2017 at 1:07 PM, Daniel LaLiberte <dlali...@google.com> wrote:

Hi Wouter,

Nothing has changed with the current release of Google Charts for a few months.  The current release is actually 45.2, with a few refactoring changes relative to version 45.  

So i don't know what might have caused the sankey chart to fail for you earlier, but perhaps you were actually experiencing a more general outage, but other (non-sankey) charts were still working because of caching.  Just a wild speculation.  Glad it is working for you again.

On Mon, Nov 20, 2017 at 11:42 AM, Wouter <woutervanbijsterveld@gmail.com> wrote:

Hi all,

Is it correct that there was an issue with the Sankey package earlier today? I experienced it but cannot find any info about it. None of the charts on my pages like this one were loading until I disabled the loading of the Sankey chart. I noticed that the Sankeys were also not showing up at the Google charts example page.

All seems to be fine now. How can I harness my pages from issues like this?

- I could use a frozen version rather than current but I am not sure whether this was related to a release? Was the latest release indeed done on February 23, 2016  as I see on this page?

- would it be better to do the content delivery from my own site rather than using the https://www.gstatic.com/charts/loader.js ? The loader loads packages and I have no idea how I could do that :)

- Can I make sure that other charts are loaded if there is an issue with one (type of) chart? In this case my page has 7 core charts, 1 table and 1 Sankey and nothing loaded due to the issue with the Sankey.

Many thanks in advance, Wouter (I use Google charts a lot and really like it!!!)

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsubscr...@googlegroups.com.

To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/22f4f7ed-b5ec-4334-b7d7-d660858cc396%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Daniel LaLiberte

dlaliberte@Google.com   5CC, Cambridge MA

[Wouter]

Hello Daniel,

Thanks for your response. FYI some more info on the error below (and page printscreen attached).

I am not sure about caching. All my pages loaded normally, except the one with Sankey if I enabled it. Why would that package be cached shorter? Where can I see which JS is cached and for how long? 

And what I find strange: my page cache in Chrome made me think that the error re-occured: the Sankey here did not load and gave the errors below but when I cleared it the page loads fine. (I use the PC that I used 15 hours ago when I experienced the error, I used a different PC in between). I copied the (old) error info:

"Failed to load https://play.google.com/log?format=json&authuser=0: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://developers.google.com' is therefore not allowed access. The response had HTTP status code 503." (more below)

loader.js:226 GET https://www.gstatic.com/charts/45.2/third_party/d3_sankey/v4/d3.sankey.js net::ERR_CONTENT_DECODING_FAILED

U.H.I.Tc @ loader.js:226

(anonymous) @ loader.js:230

U.h.forEach.U.Ha.e @ loader.js:67

google.l.m.la.ee @ loader.js:230

(anonymous) @ loader.js:234

Promise resolved (async)

google.l.m.s.Fl @ loader.js:234

google.l.m.s.Dl @ loader.js:241

google.l.m.s.load @ loader.js:243

google.G.H.T.yh @ loader.js:224

(anonymous) @ loader.js:225

Promise resolved (async)

google.G.H.T.yk @ loader.js:225

google.G.load @ loader.js:226

(anonymous) @ (index):109

loader.js:226 GET https://www.gstatic.com/charts/45.2/i18n/jsapi_compiled_i18n_sankey_module__nl.js net::ERR_CONTENT_DECODING_FAILED

U.H.I.Tc @ loader.js:226

(anonymous) @ loader.js:230

U.h.forEach.U.Ha.e @ loader.js:67

google.l.m.la.ee @ loader.js:230

(anonymous) @ loader.js:234

Promise resolved (async)

google.l.m.s.Fl @ loader.js:234

google.l.m.s.Dl @ loader.js:241

google.l.m.s.load @ loader.js:243

google.G.H.T.yh @ loader.js:224

(anonymous) @ loader.js:225

Promise resolved (async)

google.G.H.T.yk @ loader.js:225

google.G.load @ loader.js:226

(anonymous) @ (index):109

Failed to load resource: the server responded with a status of 503 ()

sankey:1 Failed to load https://play.google.com/log?format=json&authuser=0: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://developers.google.com' is therefore not allowed access. The response had HTTP status code 503.

9www.gstatic.com/charts/45.2/third_party/d3_sankey/v4/d3.sankey.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED

[Daniel LaLiberte]

My thinking is that the sankey chart code, being less frequently used, might have gotten expired sooner from either your local cache, or some intermediate cache.  You may be able to find out more about which files are cached and for how long in your browser's developer tools or debugger.  Otherwise, caches are mostly black boxes that are just supposed to work.

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.

To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/2c274340-2b20-43fd-bbbb-f7b23f99089d%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Wouter]

Ok, thank you. Is there a way to remove the dependency of loading from the gstatic / Google CDN? Or is this not done? Or should I ask this as a seperate question? Kind regards, Wouter

[Daniel LaLiberte]

The code currently must be loaded from gstatic, so there is no choice there, except that caches will hold on to copies of the code for some period of time, possibly indefinitely if they so choose.

On Wed, Nov 22, 2017 at 6:06 AM, Wouter <woutervanb...@gmail.com> wrote:

Ok, thank you. Is there a way to remove the dependency of loading from the gstatic / Google CDN? Or is this not done? Or should I ask this as a seperate question? Kind regards, Wouter

--

You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/cd6db7b1-be65-4488-8c4e-7f7b6a437dfe%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Wouter]

Ok, clear, thank you for your help!