Last 7 days

• Dec 16, 2009

  issue 11 (Uploading large size file (60 MB) and giving me error.) reported by developer.api.test   -   What steps will reproduce the problem? 1. tried to upload 60 MB file. What is the expected output? What do you see instead? >> response = yt.post_file(feed, test_movie, mime_type, entry).to_xml Net::ProtocolError: execution expired from /usr/lib/ruby/1.8/timeout.rb:60:in `rbuf_fill' from /usr/lib/ruby/1.8/net/protocol.rb:140:in `rbuf_fill' from /usr/lib/ruby/1.8/net/protocol.rb:116:in `readuntil' from /usr/lib/ruby/1.8/net/protocol.rb:126:in `readline' from /usr/lib/ruby/1.8/net/http.rb:2020:in `read_status_line' from /usr/lib/ruby/1.8/net/http.rb:2009:in `read_new' from /usr/lib/ruby/1.8/net/http.rb:1050:in `request' from /usr/lib/ruby/1.8/net/http.rb:1037:in `request' from /usr/lib/ruby/1.8/net/http.rb:543:in `start' from /usr/lib/ruby/1.8/net/http.rb:1035:in `request' from /usr/lib/ruby/gems/1.8/gems/gdata-1.1.1/lib/gdata/http/default_service.rb:69:in `make_request' from /usr/lib/ruby/gems/1.8/gems/gdata-1.1.1/lib/gdata/client/base.rb:81:in `make_request' from /usr/lib/ruby/gems/1.8/gems/gdata-1.1.1/lib/gdata/client/base.rb:61:in `make_file_request' from /usr/lib/ruby/gems/1.8/gems/gdata-1.1.1/lib/gdata/client/base.rb:123:in `post_file' from (irb):44 What version of the product are you using? On what operating system? ruby 1.8.7 Ubuntu 9.10 gdata 1.1.1 Please provide any additional information below.

  What steps will reproduce the problem? 1. tried to upload 60 MB file. What is the expected output? What do you see instead? >> response = yt.post_file(feed, test_movie, mime_type, entry).to_xml Net::ProtocolError: execution expired from /usr/lib/ruby/1.8/timeout.rb:60:in `rbuf_fill' from /usr/lib/ruby/1.8/net/protocol.rb:140:in `rbuf_fill' from /usr/lib/ruby/1.8/net/protocol.rb:116:in `readuntil' from /usr/lib/ruby/1.8/net/protocol.rb:126:in `readline' from /usr/lib/ruby/1.8/net/http.rb:2020:in `read_status_line' from /usr/lib/ruby/1.8/net/http.rb:2009:in `read_new' from /usr/lib/ruby/1.8/net/http.rb:1050:in `request' from /usr/lib/ruby/1.8/net/http.rb:1037:in `request' from /usr/lib/ruby/1.8/net/http.rb:543:in `start' from /usr/lib/ruby/1.8/net/http.rb:1035:in `request' from /usr/lib/ruby/gems/1.8/gems/gdata-1.1.1/lib/gdata/http/default_service.rb:69:in `make_request' from /usr/lib/ruby/gems/1.8/gems/gdata-1.1.1/lib/gdata/client/base.rb:81:in `make_request' from /usr/lib/ruby/gems/1.8/gems/gdata-1.1.1/lib/gdata/client/base.rb:61:in `make_file_request' from /usr/lib/ruby/gems/1.8/gems/gdata-1.1.1/lib/gdata/client/base.rb:123:in `post_file' from (irb):44 What version of the product are you using? On what operating system? ruby 1.8.7 Ubuntu 9.10 gdata 1.1.1 Please provide any additional information below.

Last 30 days

• Dec 08, 2009

  issue 10 (request error 400: No file found in upload request. gdata ve...) reported by anders.back   -   What steps will reproduce the problem? 1.create authenticated client 2.@client.put_file(url, path, mime_type, entry) 3.No file found in upload request. What is the expected output? What do you see instead? I would like to be able to upload a video to youtube What version of the product are you using? On what operating system? Windows XP SP3, gdata version 1.1.1 Please provide any additional information below. in "class MimeBody" replace "wrap_entry" with this code to fix it. "def wrap_entry(entry, file_mime_type) wrapped_entry = "--#{@boundary}\r\n" wrapped_entry += "Content-Type: application/atom+xml; charset=UTF-8\r\n\r\n" wrapped_entry += entry wrapped_entry += "\r\n--#{@boundary}\r\n" wrapped_entry += "Content-Type: #{file_mime_type}\r\n" wrapped_entry += "Content-Transfer-Encoding: binary\r\n\r\n" return MimeBodyString.new(wrapped_entry) end"

  What steps will reproduce the problem? 1.create authenticated client 2.@client.put_file(url, path, mime_type, entry) 3.No file found in upload request. What is the expected output? What do you see instead? I would like to be able to upload a video to youtube What version of the product are you using? On what operating system? Windows XP SP3, gdata version 1.1.1 Please provide any additional information below. in "class MimeBody" replace "wrap_entry" with this code to fix it. "def wrap_entry(entry, file_mime_type) wrapped_entry = "--#{@boundary}\r\n" wrapped_entry += "Content-Type: application/atom+xml; charset=UTF-8\r\n\r\n" wrapped_entry += entry wrapped_entry += "\r\n--#{@boundary}\r\n" wrapped_entry += "Content-Type: #{file_mime_type}\r\n" wrapped_entry += "Content-Transfer-Encoding: binary\r\n\r\n" return MimeBodyString.new(wrapped_entry) end"
• Dec 06, 2009

  issue 9 (Unicode support issues with ruby 1.9) reported by kasula   -   What steps will reproduce the problem? 1. Include confi.gem "gdata", :version => '1.1.1' in environment.rb 2. Start the rails console. The console doesn't start. What version of the product are you using? On what operating system? I am using ruby 1.9, rails 2.3.3. From what I read on the web, it looks like the unicode support is built into ruby 1.9. So commenting out the following lines from gdata.rb seems to be working for me. require 'jcode' $KCODE = 'UTF8' I don't know if it causes any other issues? Please provide any additional information below. The error message: no such file to load -- jcode /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `require' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `block in require' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:521:in `new_constants_in' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `require' /Users/Chethan/courses/RoR/Project/shelves/vendor/gems/gdata-1.1.1/lib/gdata.rb:21:in `<top (required)>' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `require' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `block in require' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:521:in `new_constants_in' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `require' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/rails/gem_dependency.rb:208:in `load' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:307:in `block in load_gems' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:307:in `each' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:307:in `load_gems' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:164:in `process' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:113:in `run' /Users/Chethan/courses/RoR/Project/shelves/config/environment.rb:9:in `<top (required)>' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:262:in `require' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:262:in `block in load_modules' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:260:in `each' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:260:in `load_modules' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:20:in `setup' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb.rb:53:in `start' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/bin/irb:12:in `<main>' no such file to load -- jcode /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `require' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `block in require' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:521:in `new_constants_in' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `require' /Users/Chethan/courses/RoR/Project/shelves/vendor/gems/gdata-1.1.1/lib/gdata.rb:21:in `<top (required)>' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `require' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `block in require' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:521:in `new_constants_in' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `require' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/rails/gem_dependency.rb:208:in `load' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:307:in `block in load_gems' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:307:in `each' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:307:in `load_gems' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:169:in `process' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:113:in `run' /Users/Chethan/courses/RoR/Project/shelves/config/environment.rb:9:in `<top (required)>' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:262:in `require' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:262:in `block in load_modules' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:260:in `each' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:260:in `load_modules' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:20:in `setup' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb.rb:53:in `start' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/bin/irb:12:in `<main>' Missing these required gems: gdata = 1.1.1 You're running: ruby 1.9.1.243 at /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/bin/ruby rubygems 1.3.5 at /Users/Chethan/.gem/ruby/1.9.1

  What steps will reproduce the problem? 1. Include confi.gem "gdata", :version => '1.1.1' in environment.rb 2. Start the rails console. The console doesn't start. What version of the product are you using? On what operating system? I am using ruby 1.9, rails 2.3.3. From what I read on the web, it looks like the unicode support is built into ruby 1.9. So commenting out the following lines from gdata.rb seems to be working for me. require 'jcode' $KCODE = 'UTF8' I don't know if it causes any other issues? Please provide any additional information below. The error message: no such file to load -- jcode /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `require' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `block in require' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:521:in `new_constants_in' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `require' /Users/Chethan/courses/RoR/Project/shelves/vendor/gems/gdata-1.1.1/lib/gdata.rb:21:in `<top (required)>' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `require' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `block in require' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:521:in `new_constants_in' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `require' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/rails/gem_dependency.rb:208:in `load' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:307:in `block in load_gems' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:307:in `each' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:307:in `load_gems' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:164:in `process' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:113:in `run' /Users/Chethan/courses/RoR/Project/shelves/config/environment.rb:9:in `<top (required)>' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:262:in `require' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:262:in `block in load_modules' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:260:in `each' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:260:in `load_modules' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:20:in `setup' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb.rb:53:in `start' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/bin/irb:12:in `<main>' no such file to load -- jcode /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `require' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `block in require' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:521:in `new_constants_in' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `require' /Users/Chethan/courses/RoR/Project/shelves/vendor/gems/gdata-1.1.1/lib/gdata.rb:21:in `<top (required)>' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `require' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `block in require' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:521:in `new_constants_in' /Users/Chethan/.gem/ruby/1.9.1/gems/activesupport-2.3.3/lib/active_support/dependencies.rb:156:in `require' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/rails/gem_dependency.rb:208:in `load' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:307:in `block in load_gems' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:307:in `each' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:307:in `load_gems' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:169:in `process' /Users/Chethan/.gem/ruby/1.9.1/gems/rails-2.3.3/lib/initializer.rb:113:in `run' /Users/Chethan/courses/RoR/Project/shelves/config/environment.rb:9:in `<top (required)>' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:262:in `require' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:262:in `block in load_modules' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:260:in `each' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:260:in `load_modules' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb/init.rb:20:in `setup' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/lib/ruby/1.9.1/irb.rb:53:in `start' /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/bin/irb:12:in `<main>' Missing these required gems: gdata = 1.1.1 You're running: ruby 1.9.1.243 at /Users/Chethan/.ruby_versions/ruby-1.9.1-p243/bin/ruby rubygems 1.3.5 at /Users/Chethan/.gem/ruby/1.9.1

Earlier this year

• Nov 09, 2009

  gdata-1.1.1.gem (Version 1.1.1) file uploaded by tjohns@google.com   -  

  Labels: Featured

  Labels: Featured
• Nov 09, 2009

  2 new revisions pushed by tjohns@google.com   -   93890a03f9:Updated Rakefile to use hg instead of svn for prepdoc commands. 8f4907d5d6:Added tag 1.1.1 for changeset 93890a03f97a

  93890a03f9:Updated Rakefile to use hg instead of svn for prepdoc commands. 8f4907d5d6:Added tag 1.1.1 for changeset 93890a03f97a
• Nov 07, 2009

  issue 8 (request error 400: No file found in upload request.) reported by lanceJpollard   -   What steps will reproduce the problem? 1.create authenticated client 2.@client.put_file(url, path, mime_type, entry) 3.No file found in upload request. What is the expected output? What do you see instead? I would like to be able to upload a video to youtube What version of the product are you using? On what operating system? MacBook 10.5, gdata version 1.1.0 Please provide any additional information below. The example code I'm using is attached, it's very short and straight forward.

  What steps will reproduce the problem? 1.create authenticated client 2.@client.put_file(url, path, mime_type, entry) 3.No file found in upload request. What is the expected output? What do you see instead? I would like to be able to upload a video to youtube What version of the product are you using? On what operating system? MacBook 10.5, gdata version 1.1.0 Please provide any additional information below. The example code I'm using is attached, it's very short and straight forward.
• Oct 27, 2009

  issue 7 (Request error 400 Invalid request URI when creating document...) reported by jaffeweb   -   What steps will reproduce the problem? 1. Get list of folders = @client.get('http://docs.google.com/feeds/documents/private/full/-/folder') 2. inside loop create folder uri = entry.elements['id'].text + '/contents' 3. @client.post(uri,newdoc) What is the expected output? What do you see instead? Expect document to be created in folder, instead, receive "Invalid request URI" What version of the product are you using? On what operating system? gdata-1.1.0, ruby 1.8, Please provide any additional information below. I am able to create the document in the root: uri = 'http://docs.google.com/feeds/documents/private/full' @client.post(uri,newdoc)

  What steps will reproduce the problem? 1. Get list of folders = @client.get('http://docs.google.com/feeds/documents/private/full/-/folder') 2. inside loop create folder uri = entry.elements['id'].text + '/contents' 3. @client.post(uri,newdoc) What is the expected output? What do you see instead? Expect document to be created in folder, instead, receive "Invalid request URI" What version of the product are you using? On what operating system? gdata-1.1.0, ruby 1.8, Please provide any additional information below. I am able to create the document in the root: uri = 'http://docs.google.com/feeds/documents/private/full' @client.post(uri,newdoc)
• Oct 19, 2009

  Revision 2389b2a3db (Explicitly add an "\r\n" newline combination after the end o...) pushed by tjohns@google.com   -   Explicitly add an "\r\n" newline combination after the end of the Atom entry and before the MIME boundary string. This resolves an issue with YouTube API uploads.

  Explicitly add an "\r\n" newline combination after the end of the Atom entry and before the MIME boundary string. This resolves an issue with YouTube API uploads.
• Sep 24, 2009

  issue 6 (Need to be able to set proxy options in default service) reported by dsisnero   -   No way to set proxy

  No way to set proxy
• Sep 11, 2009

  issue 5 (Raising BadRequestError will itself cause error ...) commented on by chadro...@yahoo.com   -   This seemed to fix the problem for me sudo vi /Library/Ruby/Gems/1.8/gems/gdata-1.1.0/lib/gdata/client/base.rb change when 400 raise BadRequestError, response.body to when 400 raise BadRequestError.new(response)

  This seemed to fix the problem for me sudo vi /Library/Ruby/Gems/1.8/gems/gdata-1.1.0/lib/gdata/client/base.rb change when 400 raise BadRequestError, response.body to when 400 raise BadRequestError.new(response)
• Sep 11, 2009

  issue 5 (Raising BadRequestError will itself cause error ...) commented on by chadro...@yahoo.com   -   I'm seeing the same problem. This is really annoying b/c it hides the actual request error.

  I'm seeing the same problem. This is really annoying b/c it hides the actual request error.
• Jul 27, 2009

  23 new revisions pushed by tjohns@google.com   -   Revision 1829772318:Initial directory structure. Revision 03e6f1531d:initial commit Revision a4ebf62db5:committing the possible sin of committing the docs to the repository Revision 0147d30af5:fixing mime type of css Revision dc919b092f:added rubyforge project to Gem spec Revision f75b81f4dd:adding in additional client classes for each service. Revision c13db3a4bc:started treating hash objects as HTTP form data. Cleaned up the clientlogin code to use this. Revision 3d64f18fc7:Added file upload capability, refactored code to not use DEFAULT_OPTIONS hashes since it was causing all client classes to share memory. Also changed the return type of all service class operations which is a breaking change. Revision ce7b3e982b:Fixes from comments associated with r12. Revision be5e5a3685:Added MIME support. This enables YouTube video uploads. Revision 0cfdaa300a:changing movie example path to be more generic. Revision c36a3919b9:Doc update Revision 4359456026:Fix README Revision 322e5cdfd6:count a redirect as a success for now to help with Calendar. Revision 9b9b6a6ac5:making the calendar client smart enough to handle 302 redirects Revision 905ccdaa76:relocating the require line for REXML since that logic was moved into the response. Revision 0afdb4bae9:fixing some syntax nits. Revision 5ffd1ae8c2:adding in the ability to specify a clientlogin account type from the service class call. Revision e12689fd25:preparing for 1.0.1 gem launch to push calendar redirect support into the gem. Revision 89d6fae10f:Patch contributed by eric.hodel, which refactors the way exceptions are thrown to make them more useful to calling methods. Thanks Eric! Revision 2779e734e0:Getting ready to release 1.1.0 Revision afdf0497c4:Fixed small bug with new exception handling. Revision 9412ff569c:update tags

  Revision 1829772318:Initial directory structure. Revision 03e6f1531d:initial commit Revision a4ebf62db5:committing the possible sin of committing the docs to the repository Revision 0147d30af5:fixing mime type of css Revision dc919b092f:added rubyforge project to Gem spec Revision f75b81f4dd:adding in additional client classes for each service. Revision c13db3a4bc:started treating hash objects as HTTP form data. Cleaned up the clientlogin code to use this. Revision 3d64f18fc7:Added file upload capability, refactored code to not use DEFAULT_OPTIONS hashes since it was causing all client classes to share memory. Also changed the return type of all service class operations which is a breaking change. Revision ce7b3e982b:Fixes from comments associated with r12. Revision be5e5a3685:Added MIME support. This enables YouTube video uploads. Revision 0cfdaa300a:changing movie example path to be more generic. Revision c36a3919b9:Doc update Revision 4359456026:Fix README Revision 322e5cdfd6:count a redirect as a success for now to help with Calendar. Revision 9b9b6a6ac5:making the calendar client smart enough to handle 302 redirects Revision 905ccdaa76:relocating the require line for REXML since that logic was moved into the response. Revision 0afdb4bae9:fixing some syntax nits. Revision 5ffd1ae8c2:adding in the ability to specify a clientlogin account type from the service class call. Revision e12689fd25:preparing for 1.0.1 gem launch to push calendar redirect support into the gem. Revision 89d6fae10f:Patch contributed by eric.hodel, which refactors the way exceptions are thrown to make them more useful to calling methods. Thanks Eric! Revision 2779e734e0:Getting ready to release 1.1.0 Revision afdf0497c4:Fixed small bug with new exception handling. Revision 9412ff569c:update tags
• Jul 14, 2009

  issue 4 (Calendars still experience 302 errors ) commented on by rono.music   -   Just encountered this problem (feed request fails because of redirect to https) also, and managed to figure out the cause and a solution. This happens when the account belongs to a Google App, under a domain that has been declared SSL enabled (under the Domain Settings page, when managing the Google Apps). The fix that was used for the session cookin in GData 1.0.1 is not enough to handle redirects, since it disregards the returned url (the redirect_to). I wouldn't use parsing of the response body, like this.ryansmith, but instead use the 'location' header: url = response.headers['location'] I predict that this might occur for other Google services under the same circumstances (SSL domain), but I haven't checked for it (yet). I recommend this be fixed in the next GData version.

  Just encountered this problem (feed request fails because of redirect to https) also, and managed to figure out the cause and a solution. This happens when the account belongs to a Google App, under a domain that has been declared SSL enabled (under the Domain Settings page, when managing the Google Apps). The fix that was used for the session cookin in GData 1.0.1 is not enough to handle redirects, since it disregards the returned url (the redirect_to). I wouldn't use parsing of the response body, like this.ryansmith, but instead use the 'location' header: url = response.headers['location'] I predict that this might occur for other Google services under the same circumstances (SSL domain), but I haven't checked for it (yet). I recommend this be fixed in the next GData version.
• Jul 13, 2009

  issue 5 (Raising BadRequestError will itself cause error ...) reported by vincentchu   -   When responding to an error code 400 (line 88-89 in ./gdata-1.1.0/lib/gdata/client.rb) the code will throw an error. This is because code is passing response.body when it should be passing response Proposed fix: Original: raise BadRequestError, response.body Proposed: raise BadRequestError.new(response) Cheers, Vince

  When responding to an error code 400 (line 88-89 in ./gdata-1.1.0/lib/gdata/client.rb) the code will throw an error. This is because code is passing response.body when it should be passing response Proposed fix: Original: raise BadRequestError, response.body Proposed: raise BadRequestError.new(response) Cheers, Vince
• Jun 27, 2009

  issue 4 (Calendars still experience 302 errors ) commented on by this.ryansmith   -   I have a new update. I have been testing this plugin using a google apps account. I updated my credentials using my personal @gmail.com account and the tests passed with no issues. What could be causing the problems when using a google apps account?

  I have a new update. I have been testing this plugin using a google apps account. I updated my credentials using my personal @gmail.com account and the tests passed with no issues. What could be causing the problems when using a google apps account?
• Jun 23, 2009

  issue 4 (Calendars still experience 302 errors ) commented on by this.ryansmith   -   wow. sorry for the delayed response. I have tested the code on two different machines and each time that test fails. 1) ruby 1.8.6 (2008-08-11 patchlevel 287) [universal-darwin9.0] 2) ruby 1.8.7 (2008-08-11 patchlevel 72) [i486-linux] each machine returned the following test result: Loaded suite tc_gdata_client_calendar Started F Finished in 1.156392 seconds. 1) Failure: test_get_all_calendars(TC_GData_Client_Calendar) [tc_gdata_client_calendar.rb:29]: Must not be a redirect. <200> expected but was <302>.

  wow. sorry for the delayed response. I have tested the code on two different machines and each time that test fails. 1) ruby 1.8.6 (2008-08-11 patchlevel 287) [universal-darwin9.0] 2) ruby 1.8.7 (2008-08-11 patchlevel 72) [i486-linux] each machine returned the following test result: Loaded suite tc_gdata_client_calendar Started F Finished in 1.156392 seconds. 1) Failure: test_get_all_calendars(TC_GData_Client_Calendar) [tc_gdata_client_calendar.rb:29]: Must not be a redirect. <200> expected but was <302>.
• May 06, 2009

  r29 (Fixed small bug with new exception handling. ) committed by jfis...@youtube.com   -   Fixed small bug with new exception handling.

  Fixed small bug with new exception handling.
• May 06, 2009

  issue 4 (Calendars still experience 302 errors ) Status changed by jfis...@youtube.com   -  

  Status: WorksForMe

  Status: WorksForMe
• May 04, 2009

  issue 4 (Calendars still experience 302 errors ) commented on by jfis...@youtube.com   -   I am not able to reproduce your problem. I have a unit test that passes perfectly: http://code.google.com/p/gdata-ruby-util/source/browse/trunk/test/tc_gdata_client_calendar.rb Does this test fail for you? Also you shouldn't have to extract a link from the response if you use the session cookie. What version of Ruby are you using? I think Net::HTTP behaved strangely in some older versions. I'm on ruby 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]

  I am not able to reproduce your problem. I have a unit test that passes perfectly: http://code.google.com/p/gdata-ruby-util/source/browse/trunk/test/tc_gdata_client_calendar.rb Does this test fail for you? Also you shouldn't have to extract a link from the response if you use the session cookie. What version of Ruby are you using? I think Net::HTTP behaved strangely in some older versions. I'm on ruby 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
• May 03, 2009

  issue 4 (Calendars still experience 302 errors ) commented on by this.ryansmith   -   Again, I had to do add a line to GData::Client::Calendar.make_request. def make_request(method, url, body = '', retries = 4) response = super(method, url, body) if response.status_code == 302 and retries > 0 @session_cookie = response.headers['set-cookie'] # I added this guy here so that the library would work. url = response.body.match(/<a href=\"([^>]+)\">/i)[1] return self.make_request(method, url, body, retries - 1) else return response end end

  Again, I had to do add a line to GData::Client::Calendar.make_request. def make_request(method, url, body = '', retries = 4) response = super(method, url, body) if response.status_code == 302 and retries > 0 @session_cookie = response.headers['set-cookie'] # I added this guy here so that the library would work. url = response.body.match(/<a href=\"([^>]+)\">/i)[1] return self.make_request(method, url, body, retries - 1) else return response end end
• May 03, 2009

  issue 4 (Calendars still experience 302 errors ) reported by this.ryansmith   -   require 'gdata' >> client = GData::Client::Calendar.new >> client.clientlogin( username, password ) >> client.get( "http://www.google.com/calendar/feeds/default/allcalendars/full") #=> #<GData::HTTP::Response:0x25cdf80 @status_code=302, @headers={"cache- control"=>"private, max-age=0", "connection"=>"close", "expires"=>"Sun, 03 May 2009 18:53:53 GMT", "x-content-type-options"=>"nosniff", "date"=>"Sun, 03 May 2009 18:53:53 GMT", "content-type"=>"text/html; charset=UTF-8", "server"=>"GFE/2.0", "content- length"=>"240", "location"=>"https://www.google.com/calendar/feeds/default/allcalendars"}, 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="https://www.google.com/calendar/feeds/default/allcalendars">here</A>.\n</BODY>\n </HTML>\n" I am using the latest gem.

  require 'gdata' >> client = GData::Client::Calendar.new >> client.clientlogin( username, password ) >> client.get( "http://www.google.com/calendar/feeds/default/allcalendars/full") #=> #<GData::HTTP::Response:0x25cdf80 @status_code=302, @headers={"cache- control"=>"private, max-age=0", "connection"=>"close", "expires"=>"Sun, 03 May 2009 18:53:53 GMT", "x-content-type-options"=>"nosniff", "date"=>"Sun, 03 May 2009 18:53:53 GMT", "content-type"=>"text/html; charset=UTF-8", "server"=>"GFE/2.0", "content- length"=>"240", "location"=>"https://www.google.com/calendar/feeds/default/allcalendars"}, 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="https://www.google.com/calendar/feeds/default/allcalendars">here</A>.\n</BODY>\n </HTML>\n" I am using the latest gem.
• Apr 28, 2009

  gdata-1.1.0.gem (Version 1.1.0) file uploaded by jfis...@youtube.com   -  

  Labels: Featured

  Labels: Featured
• Apr 28, 2009

  r28 (creating 1.1.0 tag ) committed by jfis...@youtube.com   -   creating 1.1.0 tag

  creating 1.1.0 tag
• Apr 28, 2009

  r27 (Getting ready to release 1.1.0 ) committed by jfis...@youtube.com   -   Getting ready to release 1.1.0

  Getting ready to release 1.1.0
• Apr 22, 2009

  issue 3 (Errors are not programatically very usable) commented on by eric.hodel   -   Nothing I've come across, thanks for the quick apply!

  Nothing I've come across, thanks for the quick apply!
• Apr 22, 2009

  issue 3 (Errors are not programatically very usable) changed by jfis...@youtube.com   -   Committed this to trunk in r26. Any other changes you want to see in 1.1.0? :)

  Status: Fixed

  Labels: Type-Enhancement −Type-Defect

  Committed this to trunk in r26. Any other changes you want to see in 1.1.0? :)

  Status: Fixed

  Labels: Type-Enhancement −Type-Defect
• Apr 22, 2009

  r26 (Patch contributed by eric.hodel, which refactors the way exc...) committed by jfis...@youtube.com   -   Patch contributed by eric.hodel, which refactors the way exceptions are thrown to make them more useful to calling methods. Thanks Eric!

  Patch contributed by eric.hodel, which refactors the way exceptions are thrown to make them more useful to calling methods. Thanks Eric!
• Apr 22, 2009

  issue 3 (Errors are not programatically very usable) reported by eric.hodel   -   The attached patch makes the errors raised by gdata more useful. It provides a base gdata error class that can be used to rescue all errors that come from gdata. It captures the Net::HTTPResponse object when creating errors based on HTTP responses for better usability so I can distinguish between a 401 Unathourized and 403 Forbidden and provide my users with better behavior and messaging.

  The attached patch makes the errors raised by gdata more useful. It provides a base gdata error class that can be used to rescue all errors that come from gdata. It captures the Net::HTTPResponse object when creating errors based on HTTP responses for better usability so I can distinguish between a 401 Unathourized and 403 Forbidden and provide my users with better behavior and messaging.
• Apr 14, 2009

  issue 2 (uninitialized constant Cal::GData) commented on by fabri...@googlemail.com   -   Well, I think the article at http://code.google.com/intl/de-DE/apis/gdata/articles/gdata_on_rails.html is a very good explanation. Maybe it's just to well written and I switched my brain off to early. ;)

  Well, I think the article at http://code.google.com/intl/de-DE/apis/gdata/articles/gdata_on_rails.html is a very good explanation. Maybe it's just to well written and I switched my brain off to early. ;)
• Apr 14, 2009

  issue 2 (uninitialized constant Cal::GData) commented on by jfis...@youtube.com   -   No worries, glad you figured it out. I'm actually sort of a Rails n00b myself, not having designed the client for rails in particular but rather to be used in any Ruby environment. :) Perhaps a future goal is to have a zipped up example Rails project that demos the use of the API with a README documenting the important bits.

  No worries, glad you figured it out. I'm actually sort of a Rails n00b myself, not having designed the client for rails in particular but rather to be used in any Ruby environment. :) Perhaps a future goal is to have a zipped up example Rails project that demos the use of the API with a README documenting the important bits.
• Apr 14, 2009

  issue 2 (uninitialized constant Cal::GData) commented on by fabri...@googlemail.com   -   Hum... I got it! XD I looked through the source code of your demo app and I forgot to add the line config.gem 'gdata', :lib => 'gdata' to my config/enviroment.rb file. Maybe you want to mention this somewhere, for other rails newbies like me. Sorry for wasting your time, but thanks a lot for your patience!

  Hum... I got it! XD I looked through the source code of your demo app and I forgot to add the line config.gem 'gdata', :lib => 'gdata' to my config/enviroment.rb file. Maybe you want to mention this somewhere, for other rails newbies like me. Sorry for wasting your time, but thanks a lot for your patience!
• Apr 14, 2009

  issue 2 (uninitialized constant Cal::GData) commented on by jfis...@youtube.com   -   Hmm are you requiring the gem somewhere? :)

  Hmm are you requiring the gem somewhere? :)
• Apr 14, 2009

  issue 2 (uninitialized constant Cal::GData) commented on by fabri...@googlemail.com   -   oh sorry my fault. this was the first try, where I put the example in a method of a model (same method like above, but named fetch_gdata). Line 5 is: yt = GData::Client::YouTube.new I'm pretty new to Ruby on Rails, but it seems like Rails is thinking GData has to be a subclass of my Controller or Model?!

  oh sorry my fault. this was the first try, where I put the example in a method of a model (same method like above, but named fetch_gdata). Line 5 is: yt = GData::Client::YouTube.new I'm pretty new to Ruby on Rails, but it seems like Rails is thinking GData has to be a subclass of my Controller or Model?!
• Apr 14, 2009

  issue 2 (uninitialized constant Cal::GData) commented on by jfis...@youtube.com   -   I'm curious about this line of the trace: /Users/fabrik42/Dev/Rails/testGdata/app/models/cal.rb:5:in `fetch_gdata' How is a model being involved here? What's at line 5 of it? Where is the cosntant "Cal::GData" being referenced?

  I'm curious about this line of the trace: /Users/fabrik42/Dev/Rails/testGdata/app/models/cal.rb:5:in `fetch_gdata' How is a model being involved here? What's at line 5 of it? Where is the cosntant "Cal::GData" being referenced?
• Apr 14, 2009

  issue 2 (uninitialized constant Cal::GData) commented on by fabri...@googlemail.com   -   Cal is the name of my Controller class. I used the "Example readonly request to YouTube" within Cal def index yt = GData::Client::YouTube.new feed = yt.get('http://gdata.youtube.com/feeds/api/standardfeeds/top_rated') end Is there anything to require/include you haven't mentioned?

  Cal is the name of my Controller class. I used the "Example readonly request to YouTube" within Cal def index yt = GData::Client::YouTube.new feed = yt.get('http://gdata.youtube.com/feeds/api/standardfeeds/top_rated') end Is there anything to require/include you haven't mentioned?
• Apr 14, 2009

  issue 2 (uninitialized constant Cal::GData) Status changed by jfis...@youtube.com   -   What the heck is Cal::GData? There is nothing in the gem named that. Also what example code are you referencing?

  Status: Invalid

  What the heck is Cal::GData? There is nothing in the gem named that. Also what example code are you referencing?

  Status: Invalid
• Apr 14, 2009

  issue 2 (uninitialized constant Cal::GData) reported by fabrik42   -   What steps will reproduce the problem? 1. installed the gdata gem 2. tried out the example code in controller ("cal") 3. throws the following error: NameError in CalController#index uninitialized constant Cal::GData /Users/fabrik42/.gem/ruby/1.8/gems/activesupport-2.3.2/lib/active_support/dependencies.rb:105:in `const_missing' /Users/fabrik42/Dev/Rails/testGdata/app/models/cal.rb:5:in `fetch_gdata' /Users/fabrik42/Dev/Rails/testGdata/app/controllers/cal_controller.rb:5:in `index' using RoR 2.3.2 with Ruby 1.8.6 p114 on OS X Leopard

  What steps will reproduce the problem? 1. installed the gdata gem 2. tried out the example code in controller ("cal") 3. throws the following error: NameError in CalController#index uninitialized constant Cal::GData /Users/fabrik42/.gem/ruby/1.8/gems/activesupport-2.3.2/lib/active_support/dependencies.rb:105:in `const_missing' /Users/fabrik42/Dev/Rails/testGdata/app/models/cal.rb:5:in `fetch_gdata' /Users/fabrik42/Dev/Rails/testGdata/app/controllers/cal_controller.rb:5:in `index' using RoR 2.3.2 with Ruby 1.8.6 p114 on OS X Leopard
• Apr 06, 2009

  gdata-1.0.1.gem (Version 1.0.1) file uploaded by jfis...@youtube.com   -  

  Labels: Featured

  Labels: Featured
• Apr 06, 2009

  r25 (tagging 1.0.1 ) committed by jfis...@youtube.com   -   tagging 1.0.1

  tagging 1.0.1
• Apr 06, 2009

  r24 (preparing for 1.0.1 gem launch to push calendar redirect sup...) committed by jfis...@youtube.com   -   preparing for 1.0.1 gem launch to push calendar redirect support into the gem.

  preparing for 1.0.1 gem launch to push calendar redirect support into the gem.
• Mar 09, 2009

  r23 (adding in the ability to specify a clientlogin account type ...) committed by jfis...@youtube.com   -   adding in the ability to specify a clientlogin account type from the service class call.

  adding in the ability to specify a clientlogin account type from the service class call.
• Mar 05, 2009

  r22 (fixing some syntax nits. ) committed by jfis...@youtube.com   -   fixing some syntax nits.

  fixing some syntax nits.
• Mar 05, 2009

  r21 (relocating the require line for REXML since that logic was m...) committed by jfis...@youtube.com   -   relocating the require line for REXML since that logic was moved into the response.

  relocating the require line for REXML since that logic was moved into the response.
• Mar 05, 2009

  issue 1 (Handle Google Calendar 302 API responses gracefully) changed by jfis...@youtube.com   -   This issue (Calendar Redirects) has been resolved in trunk as of r20.

  Summary: Handle Google Calendar 302 API responses gracefully

  Status: Fixed

  This issue (Calendar Redirects) has been resolved in trunk as of r20.

  Summary: Handle Google Calendar 302 API responses gracefully

  Status: Fixed
• Mar 05, 2009

  r20 (making the calendar client smart enough to handle 302 redire...) committed by jfis...@youtube.com   -   making the calendar client smart enough to handle 302 redirects

  making the calendar client smart enough to handle 302 redirects
• Mar 05, 2009

  issue 1 (Ruby client raises exception on GET & does NOT return respon...) commented on by jfis...@youtube.com   -   For tracking purposes r19 made 302 a success.

  For tracking purposes r19 made 302 a success.
• Mar 05, 2009

  issue 1 (Ruby client raises exception on GET & does NOT return respon...) changed by jfis...@youtube.com   -   I'm debating about this. Giving control to the programmer is cool, but I imagine a lot of code is # try to do API operation # catch possible API failures and inform user / redo It seems annoying to make the developer check after each call if there was an authentication problem instead of just catching one exception. I'm open to ideas though. Since this is getting conversational you can just e-mail me directly.

  Status: Accepted

  Owner: jfis...@youtube.com

  I'm debating about this. Giving control to the programmer is cool, but I imagine a lot of code is # try to do API operation # catch possible API failures and inform user / redo It seems annoying to make the developer check after each call if there was an authentication problem instead of just catching one exception. I'm open to ideas though. Since this is getting conversational you can just e-mail me directly.

  Status: Accepted

  Owner: jfis...@youtube.com
• Mar 05, 2009

  issue 1 (Ruby client raises exception on GET & does NOT return respon...) commented on by this.ryansmith   -   Thanks for adding 302 as a success. But perhaps we could let the client program decide the outcome of a new request. Can I take a stab at working with this particular method?

  Thanks for adding 302 as a success. But perhaps we could let the client program decide the outcome of a new request. Can I take a stab at working with this particular method?
• Mar 05, 2009

  issue 1 (Ruby client raises exception on GET & does NOT return respon...) reported by this.ryansmith   -   Calendar Data API What steps will reproduce the problem? 1. client = GData::Client::Calendar.new 2. client.get("http://www.google.com/calendar/feeds/default/allcalendars/full").to_xml I expect to see some xml describing my calendars. However, the google Calendar API suggests that i may be redirected (302) and the redirect response will include a new url with a gsessionid parameter. Unfortunately, gdata/client/base.rb make_request method will raise an exception when 302 is returned. I was able to move around this by having the method return the response in stead of raising an exception. I think that this should be the default behavior. The programmer should be able to handle HTTP responses. Not the Library.

  Calendar Data API What steps will reproduce the problem? 1. client = GData::Client::Calendar.new 2. client.get("http://www.google.com/calendar/feeds/default/allcalendars/full").to_xml I expect to see some xml describing my calendars. However, the google Calendar API suggests that i may be redirected (302) and the redirect response will include a new url with a gsessionid parameter. Unfortunately, gdata/client/base.rb make_request method will raise an exception when 302 is returned. I was able to move around this by having the method return the response in stead of raising an exception. I think that this should be the default behavior. The programmer should be able to handle HTTP responses. Not the Library.
• Mar 05, 2009

  r19 (count a redirect as a success for now to help with Calendar....) committed by jfis...@youtube.com   -   count a redirect as a success for now to help with Calendar.

  count a redirect as a success for now to help with Calendar.