Biweekly Triaging module meeting for planning and coordination.
Folks on the payroll should attend if possible, others are invited as well.
In these meetings, we can keep us up-to-date on everything triaging, discuss recent important issues and see if we can bring the module forward.
I believe it is also good to see human faces once in a while :), so there is always room for some personal stuff if appropriate.
The meeting will be on 2025-04-03T11:00:00Z. It is open for everybody interested to join the video call (link below).
Links
- Video call google meet for now, we can try jitsi as well if people prefer
- #module-triaging matrix chat room on chat.blender.org
- #module-triaging matrix chat room link for other matrix clients
- live meeting notes
Attendees
- @mano-wii
- @Alaska
- @ChengduLittleA
- @PratikPB2125
- Tariq Sully
Topics
- Announcements
- Startup Crash on legacy AMD GPUs has been fixed: Fix #132968: OpenGL: Strip line directives on legacy AMD · 5fb01b8392 - blender - Blender Projects
- Alaska and Philipp received NDOF devices
- Any bad regressions in 4.4?
- Updates on issues with Cycles HIP from previous meeting
- Enter key to choose label still doesn’t work on gitea
- Open PR list growing, can Triagers help in that?
"Pending TODOs/followups (wont get an active topic if no news have to be announced)"
- talk about Proposal - Label Changes
- Alaska has made a tool to automatically notify people of old
Needs information from user
reports: Issues - needs-information-reports - Blender Projects - Feedback regarding our triaging infrastructure
- We use a script to help write our weekly reports. There have been a few issues with it’s output recently (E.g. Duplicate data, missing data from PRs merged by others)
- Yimming was planning to look into this
- We use a script to help write our weekly reports. There have been a few issues with it’s output recently (E.g. Duplicate data, missing data from PRs merged by others)
- Wizard
- Gather a list of two or three examples from “out there” that work similar to what we want to achieve (add that to #78 - Gitea: Triaging Wizard - blender-projects-platform - Blender Projects) is still pending, some more discussion in #121260 - Issue template design discussion - blender - Blender Projects though regarding Richards experiments
- Could we add a feature that lets users know the location of crash logs after Blender crashes so they can more easily provide it in a bug report?
- There has been progress on the crash window pull request
- Discussion about exposing dependency cycles to the end user (an idea we have discussed in previous meetings)
- Discussion about Tests:
- reply in devtalk
- Usage of LLMs
Meeting Notes
-
Announcements
- Since the last meeting:
- Philipp and Alaska now have access to the 3DConnexion space mice for triaging (And have checked out some reports)
- The major regressions in Blender 4.4 have been fixed (E.g. Crash on startup with older AMD GPUs, rendering artifacts in Cycles with HIP on RDNA2, crashes with UV editor and material preview)
- Since the last meeting:
-
TODOs/followups
- The list of pull requests is quite long (1000+ open pull requests)
- Could we do something to help modules here?
- If we have the knowledge in the relevant area then we may be able to help. (need more discussion on this topic)
- Dependency cycles warning in UI task.
- While Yiming was looking into, they noticed that there could be dependency cycles that aren’t harmful (E.g. The render visibility of a object dependant on it’s own viewport visibility).
- Because these are harmless, Yiming wants to add a “ignore” button to the UI to avoid the clutter from that.
- Yiming will add a comment about this to the design task.
- While Yiming was looking into, they noticed that there could be dependency cycles that aren’t harmful (E.g. The render visibility of a object dependant on it’s own viewport visibility).
- LLM for triaging
- Germano is looking at fine tuning a LLM specifically for triaging. They’ve run some tests in the past, but they weren’t too successful. They plan to give it another go, but it requires some further adjustments and possibly data gathering.
- Germano, Philipp, Pratik, and Alaska have been working with Bart and Arnd to try and get a LLM server setup at the Blender HQ.
- Currently there is a (probably temporary) server setup for testing at the HQ.
- Another meeting about LLMs for triaging will occur after this meeting.
- We have been asked to provide information about this project to the head of development, so Germano went over what they’ve currently written in the meeting.
- In a previous meeting we talked with Thomas about gathering information about how developers use Gitea to help make a decision on Proposal - Label Changes
- Thomas wasn’t at the meeting and none of us have information to share about this.
- Alaska’s script to notify people of old
Needs information from user
seems very useful. We’re down to ~77 reports (earlier it’s mostly 200+) - Adding a window that informs users when Blender crashed.
- It’s still under development.
- The list of pull requests is quite long (1000+ open pull requests)
Following meeting
The following meeting will be on 2025-04-17T11:00:00Z. Again it will be open for everybody who’s interested.