https://bugs.kde.org/show_bug.cgi?id=428078
--- Comment #1 from Jan Kundrát <j...@kde.org> --- I do not understand how the proposed patch is supposed to fix the reported issue. Inclusion of <QDebug> looks like a leftover from some debugging. Instead of specifying type of that local variable as `auto`, it's now `QByteArray`. However, looking at the docs, `username` is a QString, then it calls toUtf8() which returns a QByteArray, then toBase64() which remains a QByteArray, and there's an operator+(QByteArray, const char*) which once again yields QByteArray. Unlike with QString, there's no QStringBuilder involved in there as far as I can tell. Are you sure you're *really* comparing results with the recent master, and then recent master with this particular patch applied? Can you share what's in `buf` before and after this patch? -- You are receiving this mail because: You are watching all bug changes.
