prayagverma / gdata-python-client

Automatically exported from code.google.com/p/gdata-python-client
1 stars 0 forks source link

InsertRow occasionally fails with: gdata.service.RequestError: {'status': 409, 'body': '', 'reason': 'Conflict'} #669

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Since it's an occasional error, I don't have any exact steps to reproduce the 
problem. I'm hoping someone reading this bug report can provide me with some 
clues that can help me lay out the exact steps to reproduce the issue.

I have a script that runs continually (as a daemon), inserting rows into a 
Google Spreadsheet using the Python gdata.spreadsheet.service class. The script 
logs in with ProgrammaticLogin() when the script is started, and then 
continually inserts rows whenever it receives a message that tells it to insert 
a row.

It works fine almost all of the time. Up until the most recent error, the 
script had been running for 5 days straight, and had inserted 166 rows into two 
different spreadsheets.

But then, running the same code that has always been running, this exception 
occurs when trying to insert a row:

      File "/home/ubuntu/ASICMiner/gspread.py", line 34, in insert_row
        entry = self.spr_client.InsertRow(data_dict, self.spreadsheet_key, worksheet_id)
      File "/usr/local/lib/python2.7/dist-packages/gdata/spreadsheet/service.py", line 339, in InsertRow
        converter=gdata.spreadsheet.SpreadsheetsListFromString)
      File "/usr/local/lib/python2.7/dist-packages/gdata/service.py", line 1236, in Post
        media_source=media_source, converter=converter)
      File "/usr/local/lib/python2.7/dist-packages/gdata/service.py", line 1358, in PostOrPut
        'reason': server_response.reason, 'body': result_body}
    gdata.service.RequestError: {'status': 409, 'body': '', 'reason': 'Conflict'}

The line 34 in /home/ubuntu/ASICMiner/gspread.py is the same line that has been 
used to successfully insert 166 rows in the same spreadsheet, but now it fails 
with this error.

Original issue reported on code.google.com by runesv...@gmail.com on 18 Jun 2013 at 11:42