• Attendees / Apologies
• Upcoming Availability 

ERM-2956 - Getting issue details... STATUS

• no key exception
• • is that the liquibase issue?
  • or are there multiple causes? it has been observed on EPAM multi-tenant installs
• Inappropriate use of metaspace parameter by EPAM team
  • no action possible by ERM
• Liquibase bug
  
  • changes affect G5 only
  • requires liquibase dependency update - which cannot be backported to Orchid or prior
• "No key ...." exception 
• Locks being applied but then not released in
  • table tenant_changelog_lock (caused either by liquibase bug or app stopping while lock in place)
  • would need devops attention rather than work from Bienenvolk
• New unknowns
  • can the no key" 

WIP 

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

Pending

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

• 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

• ERM-2939 - Getting issue details... STATUS
  
  • Progress/Impediments:
    • required bubbling hierarchy update, which is tricky with Grails save handling of save
    • identified what appeared to be a non-standard double-saving code block that has been moved to event listener - appeared to work, but broke ingest when merged
    • currently only bubbles 1 step up or down, rather than full tree
    • last updated increasingly proving to be the wrong field for this
  • TODO:
    • merge frontend changes for ERM-2923
    • revert changes in listener from ERM-2939
    • then review what the goal for coverage and last updated and re-engineer an appropriate solution as part of UXPROD-4272 & UXPROD-4271 (Owen) and review with team+Steve
  • New unknowns / help or input needed: NA
  • ETA for review: today
• ERM-2641 - Getting issue details... STATUS
  • Essentially blocked by ERM-2956, as that may precipitate further changes that will cause repeat regression testing 

Needs Elaboration / Triage

• ERM-2940 - Getting issue details... STATUS
  • attempt to move to testImplementation

Sprint Backlog - Next Up

• NA

Allocations

• Claudia: NA
• Ethan: 
  • ERM-2940 - Getting issue details... STATUS
  • ERM-2630 - Getting issue details... STATUS
    • TODO
      • refactor upsert routine in package ingest service
      • remoteKB is assumed to be in place, so this needs to be made explicit to avoid harvest failures
      • unentangle handling of secondary title enrichment 
    • Dev Estimate: 1-2 sprints
    • Known Unknowns: 
      • ERM-2631
        • scaling / parallelisation
        • run where
        • how and what kind of access to service info to tenant/client users (eg, status)
• Jack: 
  • ERM-1110 - Getting issue details... STATUS
  • ERM-2812 - Getting issue details... STATUS

Sprint Backlog - to follow

• NA 

Sprint Backlog -  At Risk

• NA

Removed

• ERM-2937 - Getting issue details... STATUS
  • BLOCKED and moved to Sprint 169 
  • Progress / Impediments: 
    • cannot extract data.results from query: resolved
    • reached out to John Coburn for steer: https://folio-project.slack.com/archives/CAYCU07SN/p1687184002973369
      • suggested approach does not provide any performance benefit over infinite scroll, and worsens it in some pagination cases, so doesn't meet user needs
    • raised to stripes team, and they are aware of an issue they need to deal with
    • STCOM-1115
  • TODO: 
    • need to double check our implementation and see if we can get this working without the labelling
    • then revert to JC / #stripes 
    • need to reconcile inconsistency of pagination across FOLIO apps, and anti-pattern of importing from acquisitions
  • New unknowns / Help or input needed:  NA
  • ETA for review: NA

Code Review:

• NA

QA / UAT 

• ERM-2934 - Getting issue details... STATUS
  • not yet appearing on snapshot, although merged 2 days ago
  • date-time rejected as invalid after making enum label changes
  • returned to dev
• ERM-2641 - Getting issue details... STATUS
• ERM-2421 - Getting issue details... STATUS
  • looking good 
  • more extensive tests set up to check against additional high volume use cases 
• SI-23 - Getting issue details... STATUS

Pending Testrails

• ERM-2923 - Getting issue details... STATUS

• NA

• NA

New Issues

• ERM-2941 - Getting issue details... STATUS / ERM-2942 - Getting issue details... STATUS
  • undergoing triage by k-int
    • partially addressed by not using metaspace params
    • timeout issue persists when activating agreements - cannot currently replicate
  • Slack conversation group
  • Closing as Won't Do
  • Raising new issue to track timeout

Added to sprint

• ERM-2812 - Getting issue details... STATUS

Not added to sprint

• NA

Other

• NA

Component Updates

• NA

Release Planning

• NA

Testing

• Sporadic non-blocking issues with snapshot builds referencing mod-agreements and mod-service-interaction
  • Ian investigating, and added additional grails-okapi logging to diagnose

Security