I probably updated the specific file instead of the whole directory structure (to avoid checking to see what else had been updated in between my code and the checked out revision).

`svn info app/models/log_bundle.rb` reveals:

Path: app/models/log_bundle.rb
Name: log_bundle.rb
URL: file:///home/subversion/sds/trunk/app/models/log_bundle.rb
Repository Root: file:///home/subversion/sds
Repository UUID: 4e27850c-0488-45a1-9bd4-87dd9910adcb
Revision: 382
Node Kind: file
Schedule: normal
Last Changed Author: aunger
Last Changed Rev: 382
Last Changed Date: 2008-05-13 15:31:45 -0400 (Tue, 13 May 2008)
Text Last Updated: 2008-05-13 15:32:20 -0400 (Tue, 13 May 2008)
Checksum: 7f702013b92b79d9c631fc814085639e


The not-checked-in code can be reverted -- it was simply debugging info for when I was fixing the LogBundles upload problem, and trying to fix the offering-wide XLS export problem on offering 2308.

-- Aaron


Stephen Bannasch wrote:
Hiroki,

Can you run a TELS activity from the dev SDS?

Learner data persistence works using the dev sds when running an activity from both the dev itsi and udl DIY sites.

At 11:07 AM -0400 5/16/08, Aaron Unger wrote:
  
The changes look ok to me. 380-382 are already live on saildataservice.
    

Arron,

I knew you had deployed them but was (and am) confused by this svn info result from the saildataservice which appears to indicate that the latest checkout is r380:

[EMAIL PROTECTED] saildataservice]$ svn info
Path: .
URL: file:///home/subversion/sds/trunk
Repository Root: file:///home/subversion/sds
Repository UUID: 4e27850c-0488-45a1-9bd4-87dd9910adcb
Revision: 380
Node Kind: directory
Schedule: normal
Last Changed Author: aunger
Last Changed Rev: 380
Last Changed Date: 2008-05-06 12:43:23 -0400 (Tue, 06 May 2008)

There also appear to be changes on the production site not checked in to svn:

[EMAIL PROTECTED] app]$ svn diff
Index: controllers/log_bundles_controller.rb
===================================================================
--- controllers/log_bundles_controller.rb	(revision 382)
+++ controllers/log_bundles_controller.rb	(working copy)
@@ -93,6 +93,7 @@
           render(:xml => @log_bundle.errors, :status => 400)
         end
       rescue Exception => e
+        logger.warn("Exception: #{e}\n\n#{e.backtrace.join("\n")}")
         render(:xml => "#{e}", :status => 404)
         # render(:text => "#{e}", :status => 400) # Bad Request
       end
Index: controllers/offering_controller.rb
===================================================================
--- controllers/offering_controller.rb	(revision 380)
+++ controllers/offering_controller.rb	(working copy)
@@ -291,6 +291,7 @@
     compact = params[:compact] ? true : false
     file = "#{RAILS_ROOT}/tmp/xls/[EMAIL PROTECTED]"
     pid = spawn {
+begin
     f = File.new(file, "w")
     f.write("")
     f.close
@@ -443,11 +444,18 @@
     row << []
     end
     exit(0)
+rescue Exception => e
+  f = File.open("/tmp/backtrace.log","w")
+  f.write("#{e}\n#{e.backtrace.join("\n")}")
+  f.flush
+  f.close
+  exit(14)
+end
     }
     wait(pid)
     # @workbook.close
     if $?.exitstatus != 0
-      raise "Error generating spreadsheet"
+      raise "Error generating spreadsheet. Exit status was: #{$?.exitstatus}"
     end
     send_data(File.open(file).read, :type => "application/vnd.ms.excel", :filename => "[EMAIL PROTECTED]" )  
   end



  
It seems like running a few sessions of both a TELS project and a UDL
activity would be sufficient to ensure the changes in bundle
upload/download aren't negatively affecting things. Plus checking an
offering-wide XLS report.

-- Aaron

Stephen Bannasch wrote:
    
I plan to apply r380..385 to the production SDS shortly.

Aaron and Scott,

Could you review these changes and help me think about what
additional testing we should do with the dev SDS before rolling out
these changes to production:

See changesets 380...385:

   http://trac.cosmos.concord.org/sds/changeset/380/trunk



      
 
      

    


  


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "SAIL-Dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to