2023-10-04 ERM Weekly Delivery Update

Owned by Jag Goraya
Oct 04, 2023

Meeting Details

Date
 
Time

11:30am UK, 12:30pm Germany

Location

Video Call in

Previously2023-09-27 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities
  • ERM-2056 - Getting issue details... STATUS
  • ERM-3020 - Getting issue details... STATUS
    • needs toolkit release?
    • what knock-on impacts?
      • mod-agreements and mod-licenses already updated
      • no change needed at the moment for mod-service-interaction
  • Issues explicitly for backend modules and libraries
  • ERM-3043
    • will need some missing comparators added also

WIP 

 In Progress
  • 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

  • ERM-2056 - Getting issue details... STATUS
    • resolving merge conflicts
  • ERM-2055 - Getting issue details... STATUS
    • refactored to functional
    • started pagination
    • stalled for ERM-2056
  • ERM-2836 - Getting issue details... STATUS
    • 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

 Blocked
  • ISSUE
    • Blocking conditions
    • Action needed
  • Are the blocking conditions still relevant? 
  • What action is needed to unblock, and by whom?


 Needs Elaboration
  • 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?


 Sprint Backlog


  • 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

  • ERM-2052 - Getting issue details... STATUS
  • ERM-2054 - Getting issue details... STATUS
  • ERM-3043 - Getting issue details... STATUS
  • ERM-3018 - Getting issue details... STATUS
  • ERM-3044 - Getting issue details... STATUS
  • ERM-3045 - Getting issue details... STATUS
    • needs some kind of state tracking
  • ERM-3046 - Getting issue details... STATUS

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 

  • ERM-3016 - Getting issue details... STATUS
  • ERM-2641 - Getting issue details... STATUS
  • ERM-2934 - Getting issue details... STATUS
  • ERM-2937 - Getting issue details... STATUS / ERM-2053 - Getting issue details... STATUS
    • minor issue (non-blocking)
    • MCL doesn't scroll to top on first load
  • ERM-2630 - Getting issue details... STATUS
  • ERM-2815 - Getting issue details... STATUS
  • ERM-2841 - Getting issue details... STATUS
  • ERM-2967 - Getting issue details... STATUS
  • ERM-2973 - Getting issue details... STATUS
  • ERM-3020 - Getting issue details... STATUS
  • ERM-3045 - Getting issue details... STATUS

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