Kaum ein halbes Jahr später und der Bug wurde von Major auf Critical hochgestuft: https://jira.mariadb.org/plugins/servle…ssue/MDEV-22923
Jetzt geht sicherlich alles ganz schnell
Bitte. Gerne. Es hilft bisweilen, derartige Einträge bei öffentlichen Veranstaltungen nochmal zu thematisieren. ![]()
Zitat von Freenode IRC channel #fosdem-mariadb-standAlles anzeigen[07.02.21 10:49:49] <uebera||> I'd love to see a short feedback regarding the prioritization/targeting of reported defects (like https://jira.mariadb.org/browse/MDEV-22923). Personally, I find anything related to "truncation of data" *really* scary.
[07.02.21 10:51:53] <KajArn|MariaDBFo> uebera||: Truncation of data **is** scary. Agree. And the fact you highlighted it helps catching our attention.
[07.02.21 11:01:52] <KajArn|MariaDBFo> <uebera|| "I'd love to see a short feedback"> Priorities and scheduling also depend on the availability of the original developer of the code around the bug. This particular bug I believe has been procrastinated out of such reasons. We may need to look at reallocating the bug.
[07.02.21 11:06:41] <AnnaWideniusMari> uebera||: When it comes to bug fixing, we always prioritise bugs that can cause data loss or wrong result. The bug MDEV-22923 seams to have fallen between cracks and I will investigate why this has not been fixed.
[07.02.21 11:09:02] <uebera||> AnnaWideniusMari: Thanks a lot!
[07.02.21 11:11:14] <AnnaWideniusMari> uebera||: If you can create some example queries + data that shows the issues you are having, please file an MDEV about this so that the MariaDB optimizer team can take a look and fix it or comment about what could be the problem and how to go around it.
[07.02.21 11:16:23] <uebera||> AnnaWideniusMari: For the MDEV mentioned, the original reporter already did this; I verified it back then with a different example (but saw no need to attach it as well). Also, said MDEV contains a reference to an older report which had been confirmed by one of your colleagues.