group.of.nepali.translators team mailing list archive

[Robie Basak <1877442@xxxxxxxxxxxxxxxxxx>]

(5.7.31 and 8.0.21 are not yet released)

** Changed in: mysql-5.7 (Ubuntu Eoan)
       Status: New => Invalid

** Changed in: mysql-5.7 (Ubuntu Focal)
       Status: New => Invalid

** Changed in: mysql-8.0 (Ubuntu Xenial)
       Status: New => Invalid

** Changed in: mysql-8.0 (Ubuntu Bionic)
       Status: New => Invalid

** Changed in: mysql-8.0 (Ubuntu Eoan)
       Status: New => Triaged

** Changed in: mysql-8.0 (Ubuntu Focal)
       Status: New => Triaged

** Changed in: mysql-5.7 (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: mysql-5.7 (Ubuntu Xenial)
       Status: New => Triaged

** Changed in: mysql-5.7 (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: mysql-5.7 (Ubuntu Bionic)
       Status: New => Triaged

** Changed in: mysql-8.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: mysql-8.0 (Ubuntu Eoan)
   Importance: Undecided => High

** Changed in: mysql-8.0 (Ubuntu Focal)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1877442

Title:
  Broken SQL CONCAT function behaviour in 5.7.30-0ubuntu0.18.04.1

Status in mysql-5.7 package in Ubuntu:
  Triaged
Status in mysql-8.0 package in Ubuntu:
  Triaged
Status in mysql-5.7 source package in Xenial:
  Triaged
Status in mysql-8.0 source package in Xenial:
  Invalid
Status in mysql-5.7 source package in Bionic:
  Triaged
Status in mysql-8.0 source package in Bionic:
  Invalid
Status in mysql-5.7 source package in Eoan:
  Invalid
Status in mysql-8.0 source package in Eoan:
  Triaged
Status in mysql-5.7 source package in Focal:
  Invalid
Status in mysql-8.0 source package in Focal:
  Triaged

Bug description:
  Hi,

  Yesterday we upgraded from 5.7.29-0ubuntu0.18.04.1 to
  5.7.30-0ubuntu0.18.04.1 (via unattended-upgrade) on Ubuntu 18.04 and
  slurmdbd (https://packages.ubuntu.com/bionic/admin/slurmdbd) started
  segfaulting.

  Upon inspection, the slurmdbd crash is caused by a change of behaviour
  of the SQL CONCAT function. The new behaviour seems wrong.

  Calling
  SELECT CONCAT('');
  will result in an empty string as expected however if the result is assigned to a variable with:
  SET @var = ""; SELECT @var := CONCAT('');
  the variable will be NULL instead of an empty string.

  It seems that when the output of CONCAT is assigned to a variable; if
  CONCAT should have returned an empty string, it will set the variable
  to NULL instead.

  SLURM itself crashes because it uses a stored procedure which relies
  on the output of CONCAT to be an empty string rather than a NULL
  variable and tries to dereference the pointer.

  I wasn’t able to get hold of 5.7.29-0ubuntu0.18.04.1 via APT so I
  tested on 5.7.21-1ubuntu1. On 5.7.21, the variable was correctly set
  to an empty string. I have also tried on 20.04 and the behaviour is
  correct as well. So the problem seems to be present only in the
  version 5.7.30-0ubuntu0.18.04.1.

  I think that the behaviour was introduced in the 5.7 branch by this commit:
  https://github.com/mysql/mysql-server/commit/addb2aab601d98e685eccae545f79d120561ad9b
  but I am not entirely sure.

  This bug is a bit annoying because it makes SLURM with accounting
  enabled completely unusable. However downgrading MySQL to
  5.7.29-0ubuntu0.18.04.1 temporarily fixed the problem.

  I have attached a log file with examples to reproduce the bug.

  Thank you very much.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1877442/+subscriptions