Samvera Tech Call 2020-12-16

Owned by Jeremy Friesen
Dec 18, 2020

Meeting Logistics:

Agenda

(meeting notes below)

Moderator: Jeremy Friesen

Notetaker: Jeremy Friesen

Attendees:

Meeting Process

 Moderator and Note Taker - click to see meeting process...
  1. Standing pre-agenda items (moderator)

    1. Welcome

      • "Welcome everyone, please add your name to the Attendees list.  If you are unable to do so, please let us know, and someone will add you. To any newcomers, Welcome, and please feel free to ask questions. Likewise for all attendees. We strive for an open and accessible conversation around Samvera technology."

    2. Call for new agenda items
  2. Follow Agenda from above (facilitated by moderator) and record notes in Notes section below (note taker)
  3. Standing post-agenda items (moderator)
    1. call for next moderator and note taker (moderator)
      1. Moderator:
      2. Notetaker:
    2. Samvera help follow-up (moderator)
    3. Pull request review (moderator)
  4. Post-meeting action (note taker)
    1. After call, this week's notetaker should create the agenda for the next call:
      1. Open template agenda titled "Samvera Tech Call 2020-xx-xx"
      2. Click on ... in the top right corner, and select copy.
      3. Popup will open for location. It should contain:
        1. Space: Samvera
        2. Parent page: 2020
      4. Select copy. New page should be created.
      5. Modify the title to remove "copy of", update it with the next date, add moderator, notetaker, and any carry-over agenda info. Click Publish. 


Notes

Help follow-up: https://github.com/samvera/hyrax/issues/4674; Tamsin is unable to duplicate this.

A possible help point: https://github.com/uclibs/uc_drc/pull/94

Jeremy Friesen Commits to working on this today.
Chris Colvard (Deactivated) Encountered this, in the build for Hyku container, they feed it a Gemfile.lock that helps it along the way.
Maybe remove Gemfile.lock?

Check-in on release candidates

Where is Hyrax at for v3.0.0; Juliet Hardesty has hopes that this will be rolling out in the early part of 2021.

Investigating https://github.com/samvera/hyrax/issues/4647, which appears to be a blocker for v3.0.0; This is an issue only in background async jobs.
Planning to ship v3.0.0.rc3 by end of 2020; These may not need to go through the full testing scripts.

Hyku has a release candidate for v3.0, which will point at Hyrax v2.9.2 (which includes the latest security fix).

We’ll be releasing v2.9.2 of Hyrax to address a IIIF viewer.

We need to get Rails 6 figured out in 2021, which is addressing bootstrap.

Email to respond about Nurax (and Dassy)

Brief situation: For a long-stretch in September until this week, Nurax was not deploying. We fixed that situation. Which also involves a manifest URL fix. In some install setups, SSL termination happens outside of the Ruby environment. This appears to be related to some installations/configurations. @tamsin rolled back some of this, which is now a bit hacky.

Aspirational state given options: Make Nurax good enough for the next 3 months; We’d a plan to pursue a more stable CI/CD

DCE wants to know if they should be at the wheel regarding Nurax.

There may be technical problems for keeping Nurax synchronized with Hyrax repository.

Nurax’s faltering is related to Travis CI’s fragility.

Nurax has been prone to fall out of date regarding effort.

There could be a lot of effort to bringing Nurax up to date versus pushing the Helm charts over the edge.

- @tamsinj is anxious about the fragmentation of effort regarding our reference implementation and testing/QA infrastructure.
- @tamsinj estimates that the effort to move towards Helm charts and Hyrax CI/CD infrastructure and moving forward on the DCE are approximately equal.
- @tamsinj is asking for a collaborator on these Helm charts

Question: Should we move towards the Helm chart for of Dassy? If our reference infrastructure would be updating at PR time, we would improve our feedback loop. We’re identifying that the feedback loop is unpredictable, we are spending effort in the QA process (e.g. someone goes to review, but Nurax is out of date, so they test and can’t resolve the issue)

PR https://github.com/samvera/hyrax/pulls/4675; This reproduces the error identified in #4647

@chrisc has recollection of a background jobs of rescue; @chrisc will be sending out this information (https://github.com/resque/resque/pull/1597)
@thomass noted that UC’s having problems with sidekiq jobs

Scheduling Next Tech Call: January 6th. tamsin woo will facilitate and Chris Colvard (Deactivated) will note take