/
2023-06-28 ERM Weekly Delivery Update

2023-06-28 ERM Weekly Delivery Update

Jun 28, 2023

Meeting Details

Date

Jun 28, 2023 

Time

11:30am UK, 12:30pm Germany

Location

Video Call in

Previously

2023-06-21 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya

  • @Owen Stephens 

  • @Jack Golding 

  • @Gill Osguthorpe 

  • @Claudia Malzer 

  • @Ethan Freestone 

Apologies

Discussion items

Time

Item

Notes

Time

Item

Notes

<5 mins

Introductions

 

Call Priorities

https://folio-org.atlassian.net/browse/ERM-2956

  • 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 

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

    • Progress / Impediments: 

      • state change is redrawing

    • TODO: 

      • review how to redesign hook to emulate mod-inventory

      • discuss with stripes on qindex changes 

    • New unknowns: 

      • what is causing redraw of SaS?

        • change in qindex

    • Help or input needed: 

      • Ethan and Claudia to collaborate on resoltuions

    • ETA for review: 

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

    • Progress / Impediments: 

    • TODO: 

    • New unknowns: 

    • Help or input needed: 

    • ETA for review:  Wed/Fri

 

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

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

    • 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

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

    • Essentially blocked by ERM-2956, as that may precipitate further changes that will cause repeat regression testing 

Needs Elaboration / Triage

Sprint Backlog - Next Up

  • NA

Allocations

 

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

  • NA

Removed

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

    • 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

 

In Review

  • Any impediments to review or QA?

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

 

Code Review:

  • NA

QA / UAT 

 

Release Candidates

  • What has passed QA since last dev call?

  • What has been closed since last dev call?

For Release / Awaiting Deployment

Pending Testrails

 

Closed: Nolana CSP

  • NA

 

Closed: Orchid CSP

  • NA

 

Closed: Poppy R2023.2

Stories / Bugs

Maintenance / Tasks

  • NA

Release Tasks

Closed (No ERM Release)

  • <10 mins

AOB

 

New Issues

Added to sprint

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