2025-06-30

  • confirmed with paul proposal for end date on 21st
  • morning spent on simplifying cluster_diffs command, spoke to Ashish about principles rather than impl:
    • Ok, so summary of what we said:
      • define method to explain purpose (reduces cognitive load of long function). In this case maybe apply_group_exemption or something
      • separate GH resource reading to permit testing by injecting cluster resource so maybe method becomes apply_group_exemption(chart_resources, unexpected_resources)
      • whenever you lots of generic typing (eg SUPPORTED_RESOURCES: Dict[str, Dict[str, str]]) see if a pydantic class would make it easier to reason about. I don’t want to say these are essential, but I believe they would help tame methods like cluster_diffs execute
  • worked ibuild coverage up to 79%

2025-06-19

  • 1-2-1
    • no list, failed to say see you thursday then
    • accessibility tests: readme not impl

2025-06-17-18

AFK, emailed Paul and Irfan

2025-06-13

  • reasonably long investigation of yesterday’s release (7:30-11) but actually looking good.
  • at stand-up learned:
    • image pull error on 0.16.9. That release was never released, remains in draft yet somehow inspector ui terraform has been applied? TODO need to examine this. Could be one of the other workflows, say on PR ran it?
  • AFK in afternoon after 7:30 start

2025-06-12

  • release latest Inspector?
  • sonarqube session
    • clean as you code
    • define what is new code (last 30 days)
  • 1-2-1
    • good days and bad days
    • see you thursday
    • give me a list
    • you’ve made some good progress with grooming and refinement - thanks
  • python dev
    • set up monorepo support in vscode
    • poetry plugins
      • test
      • plantuml
      • Structurizr
      • xray
      • docker
  • AFK from 3pm

2025-06-11

  • hands on review of Ashish’s SBOM command
    • impl external reference behaviour
  • NR support case

2025-06-10

c4 diags as code (using Structurizr)

  • Wellington Gesteira, Scopus

  • Issues: manual layout, keeping up to date, splitting into sub-systems, hard to get others to engage in maintenance

  • Solution: automation, track changes, smaller portions, shared maintenance

  • DSL (diag as code)

  • different views of single model

  • track C4 impact and ADR in PR

  • version history

others

  • new relic support case

    • response sounds like AI

  • told the team I’m leaving

  • initial review of Ashish’s SBOM command

  • fix tests (this was the biggest part of the day)

  • PR to handle fatal NewRelic error

2025-06-09

  • Paired with Thomas to get the right NRQL fix

  • planning

  • fix tests

  • Failure to build: https://github.com/elsevier-centraltechnology/cortex-inspector/actions/runs/15531425887

    Run docker/login-action@74a5d142397b4f367a81961eba4e8cd7edddf772 
Logging into docker-tiocoreeng-common-local.bts.artifactory.tio.systems... 
Error: Error response from daemon: login attempt to https://docker-tiocoreeng-common-local.bts.artifactory.tio.systems/v2/ failed with status: 504 Gateway Timeout