Erratic behavior as of 6 July

[Danny B]

In the post @ http://groups.google.com/group/google-visualization-api/browse_thread/thread/2153b62cdb4c54c6
Viz Kid said to let you guys know if problems persist. Just as NA
stated in that thread, mid afternoon yesterday the Visualization
implementations we are using started to just not display. The code
has not been changed at all in this time frame, and I have checked the
data being fed to the gadget and it is still completely accessible and
valid.

Last night when looking in the js console within Chrome I saw errors
coming from both locked-domain and idi. Shortly after that the gadget
started appearing just fine again. Now this morning it is back to not
displaying any visualization, and throwing no errors at all. Once
again the data being fed is still accessible and valid so it isn't
that.

Any ideas? We submitted a ticket with our Customer and Support PINs
however all we ever get as a response from that is to post here so I
figured I would go ahead and do that too!

[Viz Kid]

Seeing a live example which demonstrates the error would be really helpful.

Have you seen this behavior on a single browser or on several? Is it consistent (I mean, hitting refresh result every time in the same thing in the same time frame)?

Just to make sure, you are using version 1.0 and not the release candidate, right?

  Viz Kid

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To post to this group, send email to google-visua...@googlegroups.com.
To unsubscribe from this group, send email to google-visualizati...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.

[Danny B]

I am not sure how to let you see a live example given it is a private gadget utilizing a sdc within our App Domain.  If you have any suggestions I am all ears.  You would be correct about the version, we are using v1.0 not the RC.  It is consistent and happens across multiple browsers(I have tried in Chrome, Firefox, and IE - all of which are normal stable release clients).  I have tried refreshing and clearing cache with no luck on solving the problem.  All users with access are having this issue so it isn't just isolated to myself.  I have checked the logs of the sdc agent and as far as it knows all is fine, and is handling connections/sending out the responses without a problem.

In case I wasn't clear in my initial post, this gadget was working perfectly fine previously.  This issue just began occurring yesterday late afternoon EST.

[Viz Kid]

ok, let's try to narrow it down.

The charts are visible in our documentation pages so it is not a general charts problem. Can you share some information on which charts are failing for you? Also, from your mail it seems you are using gadgets. Can you specify which gadgets exactly are you using and how you are loading them? Since you say this is not a problem only related to you, it sound like it shouldn't be hard to create an example which doesn't use your private data that reproduces the errors.

  Viz Kid

On Thu, Jul 7, 2011 at 4:25 PM, Danny B <dbri...@qualitydistribution.com> wrote:

I am not sure how to let you see a live example given it is a private gadget utilizing a sdc within our App Domain.  If you have any suggestions I am all ears.  You would be correct about the version, we are using v1.0 not the RC.  It is consistent and happens across multiple browsers(I have tried in Chrome, Firefox, and IE - all of which are normal stable release clients).  I have tried refreshing and clearing cache with no luck on solving the problem.  All users with access are having this issue so it isn't just isolated to myself.  I have checked the logs of the sdc agent and as far as it knows all is fine, and is handling connections/sending out the responses without a problem.

In case I wasn't clear in my initial post, this gadget was working perfectly fine previously.  This issue just began occurring yesterday late afternoon EST.

--

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

To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/VObhwdH2U6IJ.

[Danny B]

Quick update - the error in the js console that is being thrown now is  Failed to load resource: the server responded with a status of 413 (Request Entity Too Large). I saw this same error once yesterday, but it just started showing up this morning. The gadget uses the gauge visualization.

As far as the error above, I am not sure if that is trying to say the data being sent to the gadget is too large or what. It has worked fine before, not to mention I have a hard time believing that a single number being sent to the gadget would be too large ;p

[Viz Kid]

The main question is which server returned this error - the data or the visualization itself.

I assume that the server of the data is your local server. Can you query it and see that indeed it does return the expected values in your browser?

Can you try to use the same gadget with a different server, for example Google Spreadsheets?

On Thu, Jul 7, 2011 at 4:53 PM, Danny B <dbri...@qualitydistribution.com> wrote:

Quick update - the error in the js console that is being thrown now is  Failed to load resource: the server responded with a status of 413 (Request Entity Too Large). I saw this same error once yesterday, but it just started showing up this morning. The gadget uses the gauge visualization.

As far as the error above, I am not sure if that is trying to say the data being sent to the gadget is too large or what. It has worked fine before, not to mention I have a hard time believing that a single number being sent to the gadget would be too large ;p

--

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

To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/zPO81cwOfnEJ.

[Danny B]

The data returns correctly if I call the link in a spreadsheet using =importData('url') it shows the small json string of { "name":1.23 }.  

Here is the full error thrown and it's source is "csi":

GET https://gg.google.com/csi?v=3&s=opensocial-gadgets&action=gm_default&srt=353&tran=15&gadget=https%253A%252F%252Ffeedserver-enterprise.googleusercontent.com%252Fa%252Fabcd.com%252Fg%252FPrivateGadgetSpec%252Fgadget_name.xml&container=gm&view=default&e=&rt=dl.487,ol.507,prt.507 413 (Request Entity Too Large)

I edited out the actual domain/gadget name, but you should be able to get what you need from that still right?

[Viz Kid]

Is this a gadget you wrote or are you using a Google written gadget? I think that the gadget itself might be useful in order to see what is the cause here.

As far as I see, the gauge gadget inside Google Spreadsheet still works as intended.

--

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

To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/d_zdW2ojd7UJ.

[Danny B]

It isn't the exactly the Google written one, but was based on it.  I had to change it to allow for an sdc connection, as well as updated it from the legacy gadget api like changing _IG_Prefs to gadgets.prefs and a couple other small things.

Attached is it scrubbed of any private info.

[Danny B]

Also something else of note is that error isn't even thrown in the console every time.  However even when it isn't thrown it still doesn't display.  For example right now no error is thrown at all, but nothing is displayed.

[Danny B]

So is the lack of response at this point because you are looking into it still?  

I feel the need to reiterate that nothing changed on our end for this to stop working.  It isn't a new gadget that we just can't get working...it is one that was working perfectly fine and now has stopped.  Our servers are still working the same as previously, and that was tested through calling the same url that the gadget calls through a spreadsheet and gets the correct results.  The error returned is what I posted in this thread yesterday, and it is coming from "csi" on your end, whatever that may be.

[ChartMan]

Hi

There are 4-5 technologies here so pin pointing the issue may be complicated.

We do know that gauge gadget in Google spreadsheet works and that your server is also working.
My suggestion is to try and eliminate the following one by one:

* remove oauth and use a spreadsheet URL
* use a fixed local Data Table
* try a different chart
* do not use a gadget just use the plain JavaScript directly in your page
* try embedding the standard gauge gadget from Google Spreadsheets in your page.

HTH
ChartMan 

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

> To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/gR_XnF1QKLQJ.