/
2023-10-04 ERM Weekly Delivery Update

2023-10-04 ERM Weekly Delivery Update

Oct 04, 2023

Meeting Details

Date

Oct 4, 2023 

Time

11:30am UK, 12:30pm Germany

Location

Video Call in

Previously

2023-09-27 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya

  • @Monireh Rasouli 

  • @Owen Stephens 

  • @Ethan Freestone 

  • @Claudia Malzer 

  • @Jack Golding 

Apologies

Discussion items

Time

Item

Notes

Time

Item

Notes

<5 mins

Introductions

 

Call Priorities

 

WIP 

  • ISSUE: 

    • Progress / Impediments: 

    • TODO: 

    • New unknowns: 

    • Help or input needed: 

    • ETA for review: 

  • What progress or impediment on previously stated actions?

  • What's left to do?

  • Any new unknowns?

  • What help or input is needed?

  • When expected to be ready for review?

In Progress

  • https://folio-org.atlassian.net/browse/ERM-2056

    • resolving merge conflicts

  • https://folio-org.atlassian.net/browse/ERM-2055

    • refactored to functional

    • started pagination

    • stalled for ERM-2056

  • https://folio-org.atlassian.net/browse/ERM-2836

    • Progress / Impediments: 

      • looking to extend ERM-2841 tests, which needs to do an import

      • intermittent failures still on ERM-2841

    • TODO: 

      • need to temporarily set tenant timezone to UTC to avoid mistimed record creation/check

        • Claudia to update cypress tests for timezone check and persistentJobStatus (as with for agreementStatus: candidate for generalising so it can be used with other refdata)

      • Ethan to attempt to reproduce and triage 

    • New unknowns: 

      • inconsistent failures across clients against shared environments

    • Help or input needed: 

      • test doesn't pass fully for Monireh

      • if cypress test needs to import, job queue must be clear, so will fail if ingest/harvest is in progress

    • ETA for review: 

 

Pending

  • ISSUE

    • Blocking conditions

    • Action needed

  • Are the blocking conditions still relevant? 

  • What action is needed to unblock, and by whom?

 

  • ISSUE: 

    • Who / When: 

    • ETA Ready for Dev: 

  • Who needs to be involved in the elaboration process? 

  • What is the timeframe for getting input?

  • When is the issue expected to be ready for development?

 

 

  • Who is picking up what next?

  • When is next issue expected to start / complete?

  • Anything needed to start next issue (dependencies or clarifications)?

Blocked

  • NA

Needs Elaboration / Triage

  • NA

Sprint Backlog - Next Up

Allocations

  • Claudia:

  • Ethan: NA

  • Jack: NA

  • Monireh: NA

 

 

At Risk

  • What is now at risk of not being started this sprint?

  • Do any of these take priority over other sprint backlog items?

Sprint Backlog - to follow

  • NA 

Sprint Backlog -  At Risk

Removed

 

In Review

  • Any impediments to review or QA?

  • Any useful context, implementation choices or limitations for the reviewer/tester to know ?

 

Code Review:

QA / UAT 

 

Release Candidates

  • What has passed QA since last dev call?

  • What has been closed since last dev call?

For Release / Awaiting Deployment

  • NA

Pending Testrails

 

Closed: Poppy R2023.2

Stories / Bugs

  • NA

Maintenance / Tasks

Release Tasks

Closed (No ERM Release)

Testing Tasks

  • NA

  • <10 mins

AOB

 

New Issues

Added to sprint

Not added to sprint

Other

  • Snapshot issue:

    • GOKb harvest is causing an OOM error which stops agreements from working, resulting in stalling and then a 500 error.

    • follows implementation of ERM-3018 (title matching)

    • PR to change memory settings for agreements on snapshot

      • not guaranteed

      • pending acceptance and merge

    • alternatively, we revert to previous title ingest process

    • on snapshot-2 over the weekend, harvest was interrupted by a 504 response at GOKb, and successfully recovered and completed. 

      • suggests that memory use is building over the course of a job or new resources are being cached

      • could we exploit this to force a restart after a period on long-running processes?  NOT A LONG-TERM FIX

    • Options

      • TODO: Increase memory (as per PR)

      • TODO: limit harvest job batch to (1hr) chunks, determined end of each package

      • update library to get responses

      • update library to parse responses

      • better garbage collection to release memory during job

Component Updates

  • NA

Release Planning

  • NA

Testing

Security