Your charts look good to me now. Let us know if you see otherwise.
Jon
On Tue, Jun 10, 2014 at 8:09 PM, AM <apmil...@gmail.com> wrote:
> Thank you for the feedback on this. I was worried my code became
> incompatible in some way.
>
> Let me know if I can help.
>
>
>
>
> On Tuesday, June 10, 2014 4:17:39 PM UTC-7, George Madrid wrote:
>>
>> Isn't it fun watching the rollout as stuff begins to break all over the
>> world? :-)
>>
>> There are two possibilities here:
>>
>> 1. The rollout is in some kind of inconsistent state that is causing
>> weird failures, or
>> 2. Something is broken with the new release, itself.
>>
>> I think the first problem is less likely now that more people are
>> beginning to see the issue, but we did test the release before shipping it,
>> and we have been using it internal for a few weeks now. Having a specific
>> example that breaks would help us test this. I'll try AM's charts with the
>> new release tomorrow when I'm in a better position to run some tests.
>>
>> In the meantime, I have rolled back the release. It will probably take a
>> few hours to percolate around the world. My apologies for the
>> inconvenience, and I appreciate your patience as we push the files out to
>> all of our datacenters.
>>
>> George
>>
>>
>>
>> On Tuesday, June 10, 2014 6:57:06 PM UTC-4, Andrew Gallant wrote:
>>>
>>> Nevermind, I take that back. All of my example charts are down in
>>> Chrome, and they just stopped working in Firefox within the past minute or
>>> so as well.
>>>
>>> On Tuesday, June 10, 2014 6:55:46 PM UTC-4, Andrew Gallant wrote:
>>>>
>>>> Jon, I'm not convinced that this is a rollout issue. Is there
>>>> something I can check in the API that will let you know whether I'm pulling
>>>> the old or the new version from here? It's working in Firefox and not
>>>> Chrome, and there are a bunch of security issues that could be causing all
>>>> kinds of problems in Chrome.
>>>>
>>>> On Tuesday, June 10, 2014 6:50:56 PM UTC-4, orw...@google.com wrote:
>>>>>
>>>>> On the assumption that this is affecting more than just you, we'll
>>>>> roll back the new release worldwide so that we have time to debug. We
>>>>> don't
>>>>> have any reports of problems other than yours, so we''ll use your charts
>>>>> to
>>>>> identify what went wrong.
>>>>>
>>>>> Rolling back may take a few hours, so we appreciate your patience!
>>>>>
>>>>> Jon
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Jun 10, 2014 at 6:42 PM, Jon Orwant <orw...@google.com> wrote:
>>>>>
>>>>>> The new release of Google Charts just went live, so this may be
>>>>>> related. Your charts load fine for me, but I may be hitting a datacenter
>>>>>> that still has the old version. We'll investigate.
>>>>>>
>>>>>> Jon
>>>>>>
>>>>>>
>>>>>> On Tue, Jun 10, 2014 at 6:34 PM, AM <apmi...@gmail.com> wrote:
>>>>>>
>>>>>>> Really strange. I just get errors on my side for every page with
>>>>>>> charts on them.
>>>>>>>
>>>>>>> I'm getting b.I is not a function
>>>>>>> One or more participants failed to draw()
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tuesday, June 10, 2014 3:25:14 PM UTC-7, orw...@google.com wrote:
>>>>>>>
>>>>>>>> Google Charts is up, has experienced no downtime in recent memory,
>>>>>>>> and your charts load fine. If there's a problem, it's on your end...
>>>>>>>>
>>>>>>>> Jon
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jun 10, 2014 at 6:21 PM, AM <apmi...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I'm now using what I think is the correct version of the charts
>>>>>>>>> package:
>>>>>>>>>
>>>>>>>>> google.load('visualization', '1.0', {packages: ['controls']});
>>>>>>>>>
>>>>>>>>> But I'm getting errors for charts. This all worked earlier. Is this
>>>>>>>>> my issue or is something down?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Errors:
>>>>>>>>>
>>>>>>>>> http://www.towncharts.com/Alabama/Housing/Birmingham-city-
>>>>>>>>> AL-Housing-data.html
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> 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
>>>>>>>>> scr...@googlegroups.com.
>>>>>>>>> To post to this group, send email to google-visua...@googlegroups.
>>>>>>>>> com.
>>>>>>>>>
>>>>>>>>> Visit this group at http://groups.google.com/group
>>>>>>>>> /google-visualization-api.
>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>> 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-visua...@googlegroups.
>>>>>>> com.
>>>>>>> Visit this group at http://groups.google.com/
>>>>>>> group/google-visualization-api.
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>
>>>>>>
>>>>>>
>>>>> --
> 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
> http://groups.google.com/group/google-visualization-api.
> For more options, visit https://groups.google.com/d/optout.
>
--
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 http://groups.google.com/group/google-visualization-api.
For more options, visit https://groups.google.com/d/optout.
