Arvados

Status update¶

Updates at 0ebe4a09a3d12f1415d2c119e716a2788ff889ec - branch 14988-wb-rails5-upgrade

• I've been eliminating the deprecation warnings after doing the rake app:update call.
• Forked a couple of gems because they aren't being maintained:
  • activerecord-nulldb-adapter
  • wiselinks: This one is not yet clear that it works, I was able to make it stop complaining about deprecated functions but it's from rails 3.x and it hasn't being updated since then. I've tried to submit a PR to the original maintainer but their travis pipeline fail because it's set up to test against ruby 1.9 & 2.0, and some of the updated dependencies aren't compatible with those ruby environments.
• I'm now trying to make the unit test pass, but our fake ActiveRecord::Column loading is not working properly, I think in part it's because the ActiveRecord::Column API changed again (we had issues when upgrading from 4.1 to 4.2) and I'm not getting much documentation about how to work with it, so what I'm trying is the new ActiveRecord::Attributes API (https://api.rubyonrails.org/classes/ActiveRecord/Attributes/ClassMethods.html) that seems to be the correct way to go about adding attributes not backed by a database.

It's possible that we don't even benefit from wiselinks and removing it would have no effect. Worth trying, if it causes any further trouble.

As for the fake-activerecord stuff, all I can think to offer is that IIRC it has always been a hack, written in "whatever seems to work" style, so it's not too surprising to hear Rails upgrades keep breaking it.

Updates at 28ca19d77 - branch 14988-wb-rails5-upgrade
Test run: https://ci.curoverse.com/job/developer-run-tests/1234/

All tests finally passing. Pending items:

• Update bootstrap-sass gem to version 3.4.1 to address CVE-2019-8331
• Fix test runner call to be able to run individual test files.

Updated bootstrap-sass at 2e1f0679f
Test run: https://ci.curoverse.com/job/developer-run-tests-apps-workbench-integration/1277/console

I'm not sure whether anything will care, but this (in arvados_base.rb) seems like it would accidentally match new records:

  def destroyed?
    !(etag || uuid)
  end

This (arvados_base.rb) seems like it silently returns nil for nonexistent columns, and foo['bar'] where bar happens to be a method that raises. It looks like this is replacing Rails.logger.debug "BUG: access non-loaded attribute #{k}" -- did you happen to find out what's relying on this?

  def [](attr_name)
    begin
      send(attr_name)
    rescue
      nil
    end
  end

Tom Clegg wrote:

I'm not sure whether anything will care, but this (in arvados_base.rb) seems like it would accidentally match new records:

Fixed, thanks!

This (arvados_base.rb) seems like it silently returns nil for nonexistent columns, and foo['bar'] where bar happens to be a method that raises. It looks like this is replacing Rails.logger.debug "BUG: access non-loaded attribute #{k}" -- did you happen to find out what's relying on this?

Restored the debug message. One of the parts relying on this is apps/workbench/app/views/containers/_show_log.html.erb, not sure why it is calling object[:name] but since this is a rails migration story, I didn't want to go into that rabbit hole :)

Updates at 17cde5d13
Test run: https://ci.curoverse.com/job/developer-run-tests/1241/

Thanks, LGTM