Bienenvolk Sprint 189

Sprint Goal / Focus 

  • 15 Apr - target for Bugfest Release Deadline (Fri 19 Apr)
  • Grails 6 DB connection issue → rollback to Grails 5? 

Sprint Schedule

  • Sprint: 189
  • Release: 2024.2 Ramsons 
    • Sprint 3 of 15 since Release Development Cycle Starts (Sprint 187) to Feature Freeze (Sprint 200: 27 Sep 2024)
    • Sprint 201: Module Release Deadline (4 Oct 2024) [FOLREL-601]
    • Sprint 203: Bugfix Release Deadline (8 Nov 2024) [FOLREL-602 [TBC]]

Development Meetings

  • Wed 17 Apr - dev update
  • Mon 22 Mar - mid-sprint
  • Wed 24 Mar - dev update

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • Owen off Fri 19 / Mon 22 Apr

Lead Roles:

QA Environment: 

  • folio-snapshot, folio-snapshot-2

Present

Planning Questions

  • Does the issue meet the criteria for Definition of Ready?
  • What front and back end components are affected?
  • What changes need to be made? (additions, removals or modifications)
  • What development tests need to be written?  
  • What data does the developer need to verify their work?
  • What are the known unknowns? 
  • What is needed to QA? (environment, data, scripts)

Navigation

 Sprint Planning Agenda
  1. Sprint Goal / Focus
  2. Sprint Capacity
  3. Review sprint candidates 
  4. Agree technical approach / define key implementation tasks
  5. Finalise estimates / costings
  6. Confirm sprint scope
  7. Confirm first actions





Sprint Planning  

(error) - not in sprint

(tick) or @ - in sprint 

(warning) - not ready

(question) - pending triage / planning

Sprint Focus

Planning Notes Template

  • Triage

  • Approach
  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: 
  • Development Estimate



Serials

  • Ethan Freestone
    • Determine pattern for tests on react query hooks or useMutation,
    • async function in ky library chains a .then promise, which is not easily tested
  • Monireh Rasouli 
    • memory routing on index.js in /src and /settings
  • Jack Golding
    • Resolve code smells (tick)
    • Revise longstanding TODOs as Jira issues (tick)
    • Prioritise: 
      • UISER-88 - Getting issue details... STATUS
      • UISER-99 - Getting issue details... STATUS
      • UISER-13 - Getting issue details... STATUS
      • UISER-100 - Getting issue details... STATUS
        • needs test
      • UISER-113 - Getting issue details... STATUS
        • on hold


Open Access

  • Separate module and interface versions
  • Upgrade to Grails 6
  • Complete QA on UIOA-215
  • Release






ERM-3130 - Getting issue details... STATUS Monireh Rasouli
  • Currently investigating source of problem

ERM-3165 - Getting issue details... STATUS Claudia Malzer

Moved to future release

  • some strange behaviour with translating between date and datetime across days/moment

ERM-3138 - Getting issue details... STATUS

Ethan Freestone

Owen Stephens

Release branches prepped for 

  • mainline
  • GBV release
    • along with 

Waiting 


ERM-3190 - Getting issue details... STATUS Ethan Freestone

Fix replicates some issues, but not DB close connection issues, which we cannot replicate

  • cannot set schema (all 
  • jobrunner (mod-agreements)

Q: Does snapshot fall over with smaller harvests?

If it doesn't, then try tomorrow on longer ingests


ERM-3187 - Getting issue details... STATUS Ethan Freestone

TODO:

  • Separate call to do a count vs working query
  • Need to rewrite query and handle pagination
  • Decisions to made about how to handle pagination
    • only clue is that results is not max for page
    • for now, assume that 

Needed for (a) GBV Poppy and (b) Ramsons

Testing:

  • Performance expectation is 2s ... 
  • ... once Gokb is harvested 
  • would need to test remove as well as add
  • [ ] need to decide where and when to get a baseline

ERM-3194 - Getting issue details... STATUS Claudia Malzer
  • Triage

    • should fail if refdata value is in use
    • whether there is no response body is dependent on environment (can point to bugfest instead of snapshot)
    • example: trying to delete a local license type in licenses
  • Approach
  • Components and Changes

    • Frontend: 

    • Backend: none

  • Tests / Data / Dependencies / Known Unknowns: none

  • QA: bugfest 

  • Release Target: Quesnelia Bug Fix
  • Development Estimate: 


ERM-3195 - Getting issue details... STATUS Monireh Rasouli
  • Triage

  • Approach
    • one-liner
    • add batchParams and handle as object rather than through KiwtParams
    • apply toa ll places whtere ParallelBatchFetch introduced
  • Components and Changes: Frontend

  • Tests / Data / Dependencies / Known Unknowns: NA

  • QA: snapshot | bugfest

  • Release Target: Q Bug Fix

Grails Track

 

  • Success with compiling and running with Grails 6
  • However, JobRunner is not behaving as expected: 
    • unchanged between 5 and 6 
    • but jobs are not being picked up
    • probably an unnecessary transaction that has been added and is now scoped

 

  • JobRunner triage indicates some client level tasks need tenant scope
    • These can fail silently
  • TODO:
    • diagnose cause of JobRunner fail
    • review areas where this may similarly occur (is this a job issue or pattern issue)
  • UNKNOWN
    • whether this affects beyond mod-0agreements: unlikely as it is related to federation interface with database

 

  • Running out of resources when running harvest on local branch
  • Not reproduced on master, so using that with postgres to get some performance data to compare

 

  • mod-agreements
    • compiles, builds, run
    • harvest begins, but goes from 20% CPU usage to 30-90 before climbing to 1005%
  • could be a local laptop issue
  • dev note: set up new application.yaml for an isolated pg/kafka environment to test performance 

 

  • QA pending


  • ERM-3111 - Getting issue details... STATUS
  • ERM-3089 - Getting issue details... STATUS
  • SI-34 - Getting issue details... STATUS
  • SI-38 - Getting issue details... STATUS
  • ERM-3090 - Getting issue details... STATUS


Tests

(minus) Cypress test development stalled pending implementation of STCOR-484 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions





Release Tasks (
Non-Flower Release)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions




Release Tasks (Quesnalia)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA

Release Tasks (Poppy Bug Fix)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA



Maintenance

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA






Sprint Summary

ERM


key summary type assignee status components
Loading...
Refresh

Dashboard

key summary type assignee status components
Loading...
Refresh

Other

key summary type assignee status components labels
Loading...
Refresh

No Label

key summary type assignee status components
Loading...
Refresh