[Archivesspace_Users_Group] Reports broken in 2.2.0 ??

[Noah Huffman]

Hi Steve,

I’m seeing the same error you note with some reports in v2.2.0. Other reports are generating different errors. None of the reports seem to work.
-Noah

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven (sdm7g)
Sent: Friday, November 3, 2017 3:35 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Reports broken in 2.2.0 ??


Since upgrading to 2.2.0, most Reports have been broken for us.
We also had some problems with a database migration to a new server, where initially the MySQL functions used in the reports module were missing. We have since restored those functions, but reports are still broken, but for a different reason.

Is anyone else seeing a problem ?

None of the current errors seem to be related to MySQL, so I don’t believe those earlier issues are involved.

Some reports, like Location Report complete successfully, but all Accessions Reports seem to fail.


Generating report undefined method `orientation=' for #<UnprocessedAccessionsReport:0x7f80f16> Did you

mean? orientation (erb):6:in `<eval>' org/jruby/RubyKernel.java:1000:in `eval' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/erb.rb:864:in `result' /projects/Archivespace/dcs-archivesspace/backend/app/lib/reports/report_response.rb:50:in `render' /projects/Archivespace/dcs-archivesspace/backend/app/lib/reports/report_response.rb:21:in

`block in generate' /projects/Archivespace/dcs-archivesspace/backend/app/lib/reports/json_response.rb:5:in `initialize' /projects/Archivespace/dcs-archivesspace/backend/app/lib/reports/report_response.rb:27:in `generate' /projects/Archivespace/dcs-archivesspace/backend/app/lib/job_runners/reports_runner.rb:37:in

`block in run' /projects/Archivespace/dcs-archivesspace/backend/app/model/db.rb:111:in `block in open' /projects/Archivespace/dcs-archivesspace/backend/app/model/db.rb:75:in `block in transaction' /projects/Archivespace/dcs-archivesspace/build/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in

`_transaction' /projects/Archivespace/dcs-archivesspace/build/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `block in transaction' /projects/Archivespace/dcs-archivesspace/build/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in

`hold' /projects/Archivespace/dcs-archivesspace/build/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize' /projects/Archivespace/dcs-archivesspace/build/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction'

/projects/Archivespace/dcs-archivesspace/backend/app/model/db.rb:74:in `transaction' /projects/Archivespace/dcs-archivesspace/backend/app/model/db.rb:110:in `block in open' org/jruby/RubyFixnum.java:305:in `times' /projects/Archivespace/dcs-archivesspace/backend/app/model/db.rb:107:in

`open' /projects/Archivespace/dcs-archivesspace/backend/app/model/db.rb:432:in `block in DB' /projects/Archivespace/dcs-archivesspace/backend/app/lib/job_runners/reports_runner.rb:36:in `run' /projects/Archivespace/dcs-archivesspace/backend/app/lib/background_job_queue.rb:126:in

`run_pending_job' /projects/Archivespace/dcs-archivesspace/backend/app/lib/background_job_queue.rb:169:in `block in start_background_thread' Done.


I have gotten them to run successfully by commenting out this line:



#

@report.orientation

=

'landscape'







in:  https://github.com/archivesspace/archivesspace/blob/master/backend/app/views/reports/report.erb#L6<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_archivesspace_archivesspace_blob_master_backend_app_views_reports_report.erb-23L6&d=DwMGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=ExG84eHqP2HuPVCgV2FwCyxFXY3PDMpzSACflyGvTeE&s=Cl-QtUH0xb1BxEExd4N3uyrlYUqJoQep76RTDAaOr90&e=>

But this is not a new addition and was not (I believe) broken earlier.
This seems like it may be related to the assessment module addition, but I’m not sure exactly how.

— Steve.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171103/b3a7000a/attachment.html>