I am using Google Document AclFeed APi to get the list of users to whom the document is shared. This is the code I am using
AclFeed aclFeed = docsService.getFeed(new URL("https://docs.google.com/feeds/default/private/full/file%3A"+fileId+"/acl"), AclFeed.class);//No I18N
Until last week everything was working fine , but from past two days I am getting the SocketTimeOutException for many requests...Is anyone else facing this issue? Any help will be grateful..
TIA,
VijayRaj
It happens a lot. What is your timeout set to? As an example the default on AppEngine is 5s which is way to low.
Related
My problem is simple. The url below is for a linkedin page that contains 25 jobs. The code seems to be working but I'm surprised that it is returning some of the jobs but not all of the jobs displayed on the page. Why is it returning only half of the results? so can anyone provide some suggestions as I'm new to this? I've heard about requests but I want to do it using Selenium only. I'm grateful for any help! Thanks.
here's the url
url = "https://www.linkedin.com/jobs/search/?f_TP=1&keywords=forecast&location=Toronto%2C%20Canada%20Area&locationId=ca%3A4876&sortBy=DD&start=0"
Here's my code:
body_html = driver.find_element_by_xpath("/html/body")
print(body_html.text)
I am querying a subcollection in Firestore in an Angular6 Web App. On the first run, my function went through, but I was missing some information, so I had to delete it. I deleted the data in the subcollection manually in Firebase.
This is my query:
this.inviteSub = this.afs.collection('groups').doc(myGroup).collection<any>('invitations').valueChanges().subscribe(invites => {
console.log(invites);
});
When I execute my function on the client (Chrome) again, the valueChanges returns me the data that actually has been deleted.
I already tried a hard refresh by CTRL+F5 of the website. I also closed the browser. I also tried to unsubscribe when I at ngOnDestroy. But none of my efforts "cleared" up my 'invites'.
Can anyone help me how I "refresh" my browser / function / 'invites'?
UPDATE:
I still could not figure out what the issue causes, but I changed my App to Angular 6. So, I also changed this in my question.
I found a solution by myself. In my 'app.module.ts' I had the persistence enabled AngularFirestoreModule.enablePersistence() and changed it to AngularFirestoreModule
I am trying to fetch the contacts of the user who have an account in google apps marketplace. While fetching the contact i get the following error
com.google.gdata.util.ParseException: The prefix "atom" for element "atom:cc" is not bound.
at com.google.gdata.util.XmlParser.parse(XmlParser.java:695)|
at com.google.gdata.util.XmlParser.parse(XmlParser.java:568)|
at com.google.gdata.data.BaseFeed.parseAtom(BaseFeed.java:793)|
at com.google.gdata.wireformats.input.AtomDataParser.parse(AtomDataParser.java:68)|
at com.google.gdata.wireformats.input.AtomDataParser.parse(AtomDataParser.java:39)|
at com.google.gdata.wireformats.input.CharacterParser.parse(CharacterParser.java:)|
at com.google.gdata.wireformats.input.XmlInputParser.parse(XmlInputParser.java:52)|...
I am using Java client library to fetch the contacts. Can you please let me know is there an issue in the java client library? This issue is there for a long time and I badly need to find a solution for this...What should I do to make it work...Any help will be grateful..
Thanks,
VijayRaj
I got the same Problem, that you have with the Java Client, with the .NET client.
After contacting Google support, they told me that the Contacts arbitrary XML data which is in an Property element cannot be parsed within my version of GData .
However, there is a time intensive workaround, by deleting and recreating Contacts, but thats probably not what you are looking for, me either.
After switching to the Python implementation all works fine now.
Check out this Issue report Issue 361
I'm using this example to test geolocation API http://www.w3schools.com/html/tryit.asp?filename=tryhtml5_geolocation_error
But, I always get Location information is unavailable. message. I tested it on different browsers, same problem. I have geolocation enabled in browser.
Also, I tried uploading this to a local server (XAMPP), but problem remains (same error code).
What am I doing wrong here, its taking me hours now?...I appreciate any help on this, thank you.
EDIT: When I try to locate myself using this service http://www.hostip.info/index.html its giving me error message ... actually we haven't a clue.. When I type in some random IP address, works perfect. Whats going on here?
I've recently been asked to help support a system which uses the PHP Proxy provided by SWFJunkie. In following the proxy's install steps I get to Step 4 at which point I get no results. I've tried hosting on Apache and IIS, have confirmed that URL rewrites work correctly on both platforms and that CURL is correctly installed, and have ensured there are no firewalls blocking my requests.
In researching this issue I've seen that Twitter have been changing their API rules (with more changes set to take place in March next year). The last activity I can see on the Proxy project was back in 2010, after which it seems to have gone dead. Before I put in more effort trying to get this to work I thought I'd ask - is anyone else currently using this / do you have it working?
If you have it working I'd welcome any tips / advice you have also, but mainly I just want to know in advance whether this utility still works in order to justify spending time on it.
Thanks in advance.
the proxy does still work, but I had to tweak the code a little.
Thanks to #MikeHayes for the solution: Twitter OAUTH - returns response code of "0"
For anyone else having this issue, the quick fix is to update Tweetr.php. Find the code matching what's below & insert the additional (commented) line on the end.
$opt[CURLOPT_URL] = $twitterURL;
$opt[CURLOPT_USERAGENT] = $this->userAgent;
$opt[CURLOPT_RETURNTRANSFER] = true;
$opt[CURLOPT_TIMEOUT] = 60;
//BEGIN UPDATED CODE
$opt[CURLOPT_SSL_VERIFYPEER] = false;
//END UPDATED CODE
Thanks again to Mike & good luck to anyone else currently having this issue.