Google Charts works sometimes and sometimes it does not work! Please notice that I am using the same data in both cases ,no difference at all, when it does not work it throws a message error in the console.
I am sure that the problem is not happening from my side, it is happening from google side. Did this problem happen to anyone before and does it happen often?
There are many duplicate reports on this issue. There seems to have been a bit of a problem with the loader system with caching browsers and caching proxies keeping redirects from the 'current' version during the latest release.
Switching to a fixed version (43 for before this update, or 44 for the new version) has been an effective workaround for most people.
This the Google Visualization team assures us this is a temporary issue, will solve itself as caches expire, and they'll look into solving the underlying problem before the next release.
the solution is to explicitly specify previous version of the API to load instead of using current:
- google.charts.load('current', {'packages':['bar']});
+ google.charts.load('43', {'packages':['bar']});
Here is a link to a discussion about the new version v44 from Google Charts team.
From: https://stackoverflow.com/a/35648674/1857295
Related
Been trying to setup a simple Hoodie app and its been a very troublesome days for me.
To get more eyes on my issues, I'm submitting the issues that I'd submitted in Hoodie server issues but couldn't get any replies yet.
So here are the issues I want someone to look into:
https://github.com/hoodiehq/hoodie-server/issues/510
https://github.com/hoodiehq/hoodie-server/issues/511
https://github.com/hoodiehq/hoodie-server/issues/512
But the one that will take me forward is this one:
https://github.com/hoodiehq/hoodie-server/issues/513
I’m very sorry for the trouble you run into. I’m one of Hoodie’s core contributors, I’m happy to help you out.
First, your node version is very out of date. Can you please install the latest node from https://nodejs.org/en/?
Also you are using the old hoodie version. I’m very sorry for the confusion, we are currently transitioning to a new Hoodie, and the old version is still referenced a lot on our website and the docs.
After you installed the new Node version, follow the setup instructions at https://github.com/hoodiehq/hoodie. Here is a simple example app that you can check out to see Hoodie works https://github.com/hoodiehq/hoodie-app-tracker. And the work-in-progress docs are here: http://docs.hood.ie/camp/ (note the /camp path)
Anyone please let me know what is this all about? I am stuck since a week on this and no help from searching. I posted my query to the developer of Alamofire but still no response. Please help! I am totally confused what is wrong in the integration of Alamofire. I have followed every step and this issue is coming with XCode 6.3 as before it was running properly.
When I am adding the Framework under "Copy Frameworks", it is adding the Framework twice showing different paths but when I am Going to there location, it is taking me to the same location. Here is the screen shot.
I have also created the video for that issue. May be that can help in a better way. Please see HERE
Moreover, latest SDK contains framework for MAC OS as well but I didn't add that. I hope all the above information will help you in helping me. Thanks!
This is going to be incredibly difficult to debug without a sample project that is set up in the same manner as your actual one. If you had imported Alamofire project into your project, you wouldn't see two versions of Alamofire appear when you add it to the Copy Frameworks build phase. If you truly want to resolve this quickly, you have two options.
Option 1
Push up a sample project to Github and link it here. We can then take a look at the project and pretty quickly access what the issue is. The main reason it's so difficult here is that there are roughly 10 different things that could be the cause of the issue. Therefore, it's much faster for you to create a sample project than for us to go round-and-round (which we've already started with #Masterfego).
Option 2
Take the leap and try out CocoaPods. It is a fantastic dependency management system that will forever alleviate these annoying types of project management issues. CocoaPods itself has fantastic documentation. Also, the Alamofire README breaks down in detail how to add Alamofire to your project using CocoaPods.
Recommendation
I would highly encourage you to choose Option 2. That is definitely the fastest way forward and you won't regret moving to a more robust dependency management system. It makes managing library updates and new installations extremely simple.
If you do end up going with Option 1, then I'll take a look at your sample project and revise my answer.
I upgraded our JIRA from version 6 to version 6.1. Suddenly the Activity Streams are always empty. It is very annoying for the users who were very dependent on them. So I need to get the activity streams back.
What I have tried so far:
1. Reindexing
2. Creating a new widget for activity stream
What log can I look into to see what is broken? Do I need to create a new filter or something?
Please do not create activitystream-gadget.xml. Instead, remove the gadgets you have now and install the latest versions of each--including the Activity Stream gadget itself.
Please look at your atlassian-jira.log file.
Mostly this is caused by outdated plugins using deprecated (and now removed) classes. Similar thing happened to me when OSUser class was removed due to deprecation and an older plugin still used it.
If you are not able to view the log, try disabling user installed plugins.
I am using iTextSharp to read pdf file. I am using pdfreader.GetPageContent() and PdfTextExtractor.GetTextFromPage() methods using simple text extraction strategy.
Both the methods not reading all the pdf's.
For one pdf if I use GetTextFromPage it's throwing Index was outside the bounds of the array exception(that page having bullet marks and special chars).
How to solve this problem ?
Recently a few bugs were fixed, so you have two options:
Wait for 5.1.4 to be released
Download and build the latest SVN yourself.
If you still have issues after building the latest SVN, either submit a bug report at sourceforge or subscribe to the mailing list and post there.
The recent bug fixes may or may not fix your specific problem. People keep complaining about the parsers, but many are unwilling to submit sample PDF(s) that reproduce the issue.
In other words, if the fixes don't solve your problem and you're unwilling to submit a bug report and sample PDF(s) you're out of luck.
I have been looking to switch to OAuth for my Twitter integration code and now that there is a deadline in less than 7 weeks (see countdown link) it is even more important to make the jump to OAuth. I have been doing Basic Authentication which is extremely easy. Unfortunately OAuth does not appear to be something that I would whip together in a couple of hours.
http://www.countdowntooauth.com/
So I am looking to use a library. I have put together the following list.
MPOAuth
MGTwitterEngine
OAuthConsumer
I see that MPOAuth has some great features with a good deal of testing code in place but there is one big problem. It does not work. The sample iPhone project that is supposed to authenticate with Twitter causes an error which others have identified and logged as a bug.
http://code.google.com/p/mpoauthconnection/issues/detail?id=29
The last code change was March 11 and this bug was filed on March 30. It has been over a month and this critical bug has not been fixed yet. So I have moved on to MGTwitterEngine.
I pulled down the source code and loaded it up in Xcode. Immediately I find that there are a few dependencies and the README file does not have a clear list of steps to fetch those dependencies and integrate them with the project so that it builds successfully. I see this as a sign that the project is not mature enough for prime time. I see also that the project references 2 libraries for JSON when one should be enough. One is TouchJSON which has worked well for me so I am again discouraged from relying on this project for my applications.
I did find that MGTwitterEngine makes use of OAuthConsumer which is one of many OAuth projects hosted by an OAuth project on Google Code.
http://code.google.com/p/oauth/
http://code.google.com/p/oauthconsumer/wiki/UsingOAuthConsumer
It looks like OAuthConsumer is a good choice at first glance. It is hosted with other OAuth libraries and has some nice documentation with it. I pulled down the code and it builds without errors but it does have many warnings. And when I run the new Build and Analyze feature in Xcode 3.2 I see 50 analyzer results. Many are marked as potential memory leaks which would likely lead to instability in any app which uses this library.
It seems there is no clear winner and I have to go with something before the big Twitter OAuth deadline.
Any suggestions?
I've used bengottlieb's Twitter-OAuth without issues.
Build+Analyse finds only one issue (in SA_OAuthTwitterController.m) and that's just a variable that has a value stored during initialization that is never read. I've not seen any leaks in my use of it. It was simple to implement and so far (two apps in the store using it, a third in development) no problems at all.
A new single-file solution is TDOAuth: http://github.com/tweetdeck/TDOAuth.
It's well-tested in that it is used in the TweetDeck iOS clients.
I recently had to implement "post to Twitter".
What I found was that none of the various projects would work out-of-the-box. They're all close, but not quite there.
Eventually I settled on OAuthConsumer, Stig Brautaset's SBJSon, with some ideas more than code borrowed from Ben Gottlieb's Twitter-OAuth-iPhone for pin processing.
I probably would have looked at MGTwitterEngine, but I didn't need to hit that much of the API - just status updates.
I seem to recall having to hack OAuthConsumer to set a few parameters correctly - that was the biggest stumbling block.
Try this Framework out for size: https://github.com/materik/meauth-ios, works well for BitBucket's API and am in progress of testing it with more sites. Please give feedback and contribute.