search

weakish / google-docs-fs

Automatically exported from code.google.com/p/google-docs-fs
GNU General Public License v2.0
0 stars 0 forks source link

Invalid Argument with Gdata 2.0.12 and google-docs-fs-1.0rc1 #37

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
First of all, thank you very much for your work :-)

What steps will reproduce the problem?
1.gmount on any directory
2.on nautilus, right click on a file and open with oo2.4

What is the expected output? What do you see instead?
I should be able to see the file in oo, instead it gives me an error saying 
"Invalid Argument"

What version of the product are you using? On what operating system?
OS: Suse 11.0
Python-Gdata: 2.0.12
google-docs-fs-1.0rc1
Python 2.5

Please provide any additional information below.
Debug information. As you see, the problem aparently is with that 301 error 
code returned

======================================
LOOKUP /asdfasdf.doc
   NODEID: 2
   unique: 777, error: 0 (Success), outsize: 136
unique: 778, opcode: LOOKUP (1), nodeid: 1, insize: 53
LOOKUP /asdfasdf.doc
   NODEID: 2
   unique: 778, error: 0 (Success), outsize: 136
unique: 779, opcode: OPEN (14), nodeid: 2, insize: 48
Traceback (most recent call last):
  File "/usr/lib64/python2.5/site-packages/fuse.py", line 361, in __call__
    return apply(self.func, args, kw)
  File "/usr/lib64/python2.5/site-packages/fuse.py", line 775, in wrap
    res = fun(*a, **kw)
  File "/usr/local/lib64/python2.5/site-packages/googledocsfs/gFile.py", line 276, in open
    file = self.gn.get_file(path, tmp_path, f)
  File "/usr/local/lib64/python2.5/site-packages/googledocsfs/gNet.py", line 195, in get_file
    self.gd_client.DownloadDocument(file.resourceId.text, tmp_path.encode(self.codec))
  File "/usr/local/lib64/python2.5/site-packages/atom/__init__.py", line 1475, in deprecated_function
    return f(*args, **kwargs)
  File "/usr/local/lib64/python2.5/site-packages/gdata/docs/service.py", line 361, in Export
    self.Download(entry_or_id_or_url, file_path, ext, gid, extra_params)
  File "/usr/local/lib64/python2.5/site-packages/gdata/docs/service.py", line 340, in Download
    self._DownloadFile(url, file_path)
  File "/usr/local/lib64/python2.5/site-packages/gdata/docs/service.py", line 178, in _DownloadFile
    'body': response_body}
gdata.service.RequestError: {'status': 302, 'body': 
'<HTML>\n<HEAD>\n<TITLE>Moved Temporarily</TITLE>\n</HEAD>\n<BODY 
BGCOLOR="#FFFFFF" TEXT="#000000">\n<H1>Moved Temporarily</H1>\nThe document has 
moved <A 
HREF="http://docs.google.com/feeds/download/documents/Export?exportFormat=doc&am
p;id=1y7IOiwAJOc_kjUa1JQe2xDoYs7GHrN7JgXfcAZfgYZ8">here</A>.\n</BODY>\n</HTML>\n
', 'reason': 'Moved Temporarily'}
   unique: 779, error: -22 (Invalid argument), outsize: 16
======================================

Original issue reported on code.google.com by ldillo...@gmail.com on 22 Sep 2010 at 10:51

GoogleCodeExporter commented 8 years ago 
Important UPDATE: I do can open xls(5) and ppt(2) files. The problem is only 
with all the .doc(25)

Also, it can be infered from my words that I can see the full list of files, no 
problem about that. Just when I try to open them.

Thanks!

Original comment by ldillo...@gmail.com on 22 Sep 2010 at 10:58

GoogleCodeExporter commented 8 years ago 
Hi, is this document a "new" document by any chance? I know Google updated Docs 
in the past couple of months with a newer UI and other things and I suspect 
this may be the problem. I think the fix will just be to change the calls in 
Google Docs FS to use Export().

Original comment by d38dm8nw81k1ng@gmail.com on 23 Sep 2010 at 4:55

GoogleCodeExporter commented 8 years ago 
Yes, that would be correct. I can confirm that old documents opens just fine 
and new documents don't.

Original comment by henrik.gorlin on 23 Sep 2010 at 5:05

GoogleCodeExporter commented 8 years ago 
I've posted this issue on GData Python Client and I'll see what they come back 
with:

http://code.google.com/p/gdata-python-client/issues/detail?id=451

A similar issue was supposed to be fixed, but it would appear to not be the 
case.

Original comment by d38dm8nw81k1ng@gmail.com on 24 Sep 2010 at 9:57

GoogleCodeExporter commented 8 years ago 
Merging into Issue 32

Original comment by d38dm8nw81k1ng@gmail.com on 7 Nov 2010 at 2:14