Right now we're working on a bulk edit, but you know the client is expecting a bulk download as well.We can't wrap the same search results partial in multiple forms.(Argument Error) from C:/Program Files/Ruby200-x64/lib/ruby/gems/2.0.0/gems/nexpose-0.8.1/lib/nexpose/vuln_excep tion.rb:143:in `save' from C:/Remediation/TEST-Nexpose Bulk Exclude-Specific Instance Asset.rb:52:in `block in ' from C:/Program Files/Ruby200-x64/lib/ruby/2.0.0/csv.rb:1717:in `each' from C:/Program Files/Ruby200-x64/lib/ruby/2.0.0/csv.rb:1120:in `block in foreach' from C:/Program Files/Ruby200-x64/lib/ruby/2.0.0/csv.rb:1266:in `open' from C:/Program Files/Ruby200-x64/lib/ruby/2.0.0/csv.rb:1119:in `foreach' from C:/Remediation/TEST-Nexpose Bulk Exclude-Specific Instance Asset.rb:34:in `' The vuln does not create or get approved or anything.If I take out the vuln_line and just have the approve line: vuln_exception.approve(nsc, comment = nil) I get the following: C:/Program Files/Ruby200-x64/lib/ruby/gems/2.0.0/gems/nexpose-0.8.1/lib/nexpose/api_reques t.rb:128:in `execute': Nexpose API: Action failed: cvc-complex-type.4: Attribute 'exception-id' must appear on element 'Vulnerability Exception Approve Request'.Not only is it an awful user experience to wait that long for a page to load, we’re also blocking that entire process from serving other requests during that time (which would be a significant problem in our high-throughput app).Looking at our other use case with notification preferences, doing this 1.4 million times means it could take over an hour to turn these notifications on, and other migrations we may need to run will be blocked on that process. One of the reasons this takes so long is that Active Record is running validations on each one of these records individually.'' vuln_exception.save(nsc, exception['SComment']) vuln_exception.submitter = exception['submitter'] vuln_exception.update_expiration_date(nsc, exception['expiration']); vuln_exception.approve(nsc, exception['RComment']) But that code will now only run if i comment out the expiration date line - and it still does not submit the SComment or RComment (Submitter or 'Reporter' comment) or the RComment (Reviewer Comment) C:/Program Files/Ruby200-x64/lib/ruby/gems/2.0.0/gems/nexpose-0.8.1/lib/nexpose/api_reques t.rb:128:in `execute': Nexpose API: Action failed: cvc-complex-type.4: Attribute 'expiration-date' must appear on element 'Vulnerability Exception Update Expiration Date Request'.This will be the first article in a series, outlining how to implement a bulk edit in Rails 3.1.1 (although most any version of Rails will do). Well, there are a couple of gotcha's to be worked out along the way.If you don't see an adapter you're using listed let us know.I’d like to use the latest branch of development of redmine under bitnami, but it requires rails 2.1.0 (the very new version).
This works great when processing data in a onesie-twosie fashion, but what about large batches of data?