Samvera Tech Call 2025-08-27

Meeting Logistics:

Time: 9:00am PDT / Noon EDT
Zoom Meeting URL: Join our Cloud HD Video Meeting
(link will launch Zoom client – if you do not have Zoom, expand the instructions below)

Agenda (meeting notes below)

The length it takes to run Dassie specs
A copy of Hyrax::Workflow::WorkflowFactory has been removed from the module tree but is still active · Issue #7166 · samvera/hyrax
Considering what to tee up for myself next sprint starting next week @Randall Floyd
- Need to start the Rails 8 push; roadmap doc calls for this work in Sep. - Dec.
- Ditto for Blacklight 8
Looming Bitnami changes.

Moderator: @Randall Floyd

Notetaker: @Shana Moore

Attendees:

@Tracy McCormick
@Mark Bussey
@Praneeth Byna
@Sarah Proctor
@Rob Kaufman
@Nic Don Stanton-Roark
@Bradley Watson
@Chris Colvard
you!

Meeting Process

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
Follow Agenda from above (facilitated by moderator) and record notes in Notes section below (note taker)
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)
  1. Recent Samvera PR list
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 XXXX-XX-XX"
  2. Click on ... in the top right corner, and select “Duplicate”.
  3. Popup will open for location. It should contain:
    1. Space: Samvera
    2. Parent page: (Verify value is current year)
  4. Select “Duplicate”. New page should be created.
  5. Modify the title to remove "Duplicate of", update it with the next date, add moderator, notetaker, and any carry-over agenda info. Click Publish.

Notes

Length of Dassie spec runs:
1. @Daniel Pierce responded in slack: “I'm out today for the tech call, but I wanted to say the dassie specs got slower during the big valkyrie specs effort. My guess is that was mainly from throwing away the special lightweight collection mock that was being used in favor of the real collection classes.”
2. @Randall Floyd to follow up. Will be considered for the next planned sprint.
3. Rob: We used to run 7 or 8 processes, and only run against Dassie. Now we have 4 runners x 3. Dassie specs take much longer than Koppie and Serenia - the fundamental problem may be because Fedora 4 is slow.
re: issue: A copy of Hyrax::Workflow::WorkflowFactory has been removed from the module tree but is still active · Issue #7166 · samvera/hyrax
1. @Randall Floyd will create a PR and include it in the next sprint.
Next Sprint: rails 8 push?
1. (Chris Colvard) - may have to deal with more core and view component issues in rails 8 based off his experience with Avalon and the upgrade to blacklight 8. They also had to move to bootstrap 5. They didn’t change the asset pipeline.
2. (Rob) - it’s probably time for hyrax and hyku to get rid of sprockets but we wouldn’t have to deal with that on day 1 when upgrading rails.
(Brad) - bitnami free images are being deprecated. Do we have a plan in place?
1. (Rob) - yes. He will put up a PR for Hyrax and Hyku helm charts today.
2. (Randall) - what is required beyond Rob’s PR?
  1. (Rob) - fundamental issue - short term they are renaming docker images. We can change this and we’ll be ok for the moment. But many of the free images we use won’t get updates in the future (solr, and zookeeper) so we will need to replace these in the stack and decide if we should keep using bitnami. This is the second time they’re “pulled the rug” - are they a trusted actor? Rob will open a set a tickets for what needs to happen in the long term.
Calls for help?
1. (Mark Bussey) - PR to update getting started documents for Hyku. Instructions for running the test suite are failing because they don’t have a test database. PR removes the testing instructions.
  1. Should he be able to run them?
    1. Yes - (Rob) something must be busted in the set up. He shouldn’t have to be able to run test prepare separately. It should be ready to go when you spin up. Try run db:test:prepare - if that fixes it, it should be added to the initialize step of docker-compose.yml. Rob thinks he knows what happened and will take a look.
2. Deploy problems for Hyku
  1. db-wait.sh not found will fail deploys. Rob says it should be fixed as of yesterday.
Next Meeting:
1. moderator: Rob Kaufman
2. note taker: Randal Floyd