[MDEV-8756] MariaDB 10.0.21 crashes during PREPARE - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 5.5(EOL), 10.0(EOL), 10.1(EOL)
Fix Version/s: 5.5.47, 10.0.22, 10.1.9
Component/s: Data Manipulation - Subquery, Data Manipulation - Update, Platform Debian, Prepared Statements
Labels:
None
Environment:
MariaDB 10.0.21 Docker Container running on Ubuntu 15.04.

Sprint:
10.0.22

Description

MariaDB 10.0.21 crashes during preparation of an UPDATE statement with a SELECT subquery in combination with ONLY_FULL_GROUP_BY.

One can reproduce the issue using docker as follows:

First start the MariaDB database container:

docker run -it --rm --name crasher -e MYSQL_ROOT_PASSWORD=root mariadb:10.0.21

Afterwards connect with the MariaDB command line client:

docker run -ti --rm --link crasher:mariadb mariadb mysql --host=mariadb -proot

Inside the command line client perform the following querys:

-- create test database

CREATE DATABASE IF NOT EXISTS db; use db;

-- drop test tables

DROP TABLE IF EXISTS t1; DROP TABLE IF EXISTS t2;

-- create test tables

CREATE TABLE t1 ( id INT(10), value INT(10) ); CREATE TABLE t2 ( id INT(10) );

-- enable full group by

SET SESSION sql_mode = 'ONLY_FULL_GROUP_BY';

-- try to prepare query

PREPARE stmt FROM 'UPDATE t1 t1 SET value = (SELECT 1 FROM t2 WHERE id = t1.id)';

The last query will return:

ERROR 2013 (HY000): Lost connection to MySQL server during query

And the server crashes because of signal 11. The stack trace is a follows:

Thread pointer: 0x0x7fa1d3641008

Attempting backtrace. You can use the following information to find out

where mysqld died. If you see no messages after this, something went

terribly wrong...

stack_bottom = 0x7fa1f779ce70 thread_stack 0x48000

mysqld(my_print_stacktrace+0x3d)[0x7fa1f7195a2d]

mysqld(handle_fatal_signal+0x31a)[0x7fa1f6cd375a]

/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7fa1f633d8d0]

mysqld(_ZN10Item_field15fix_outer_fieldEP3THDPP5FieldPP4Item+0x14c)[0x7fa1f6cf8a1c]

mysqld(_ZN10Item_field10fix_fieldsEP3THDPP4Item+0x4f2)[0x7fa1f6cf9742]

mysqld(_ZN9Item_func10fix_fieldsEP3THDPP4Item+0x1b3)[0x7fa1f6d2f3a3]

mysqld(_Z11setup_condsP3THDP10TABLE_LISTR4ListIS1_EPP4Item+0x1c3)[0x7fa1f6b09573]

mysqld(+0x42f111)[0x7fa1f6b9d111]

mysqld(_ZN30subselect_single_select_engine7prepareEv+0x688)[0x7fa1f6d62788]

mysqld(_ZN14Item_subselect10fix_fieldsEP3THDPP4Item+0xed)[0x7fa1f6d60aed]

mysqld(_Z12setup_fieldsP3THDPP4ItemR4ListIS1_E17enum_mark_columnsPS5_b+0x184)[0x7fa1f6b07594]

mysqld(+0x3f7f7a)[0x7fa1f6b65f7a]

mysqld(_ZN18Prepared_statement7prepareEPKcj+0x6dd)[0x7fa1f6b6771d]

mysqld(_Z22mysql_sql_stmt_prepareP3THD+0x39f)[0x7fa1f6b67caf]

mysqld(_Z21mysql_execute_commandP3THD+0x90e)[0x7fa1f6b4edfe]

mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x1e2)[0x7fa1f6b551d2]

mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1787)[0x7fa1f6b56f87]

mysqld(_Z24do_handle_one_connectionP3THD+0x28b)[0x7fa1f6c2da5b]

mysqld(handle_one_connection+0x40)[0x7fa1f6c2dac0]

/lib/x86_64-linux-gnu/libpthread.so.0(+0x80a4)[0x7fa1f63360a4]

/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fa1f493e04d]

Trying to get some variables.

Some pointers may be invalid and cause the dump to abort.

Query (0x7fa1be042408): is an invalid pointer

Connection ID (thread ID): 2

Status: NOT_KILLED

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

log.txt
5 kB
2015-09-05 21:19

Activity

Ascending order - Click to sort in descending order

Tim Düsterhus created issue - 2015-09-05 21:19

Tim Düsterhus made changes - 2015-09-05 21:19

Field	Original Value	New Value
Attachment		log.txt [ 39425 ]

Tim Düsterhus made changes - 2015-09-05 21:20

Description

MariaDB 10.0.21 crashes during preparation of an UPDATE statement with a SELECT subquery in combination with ONLY_FULL_GROUP_BY.

One can reproduce the issue using docker as follows:

First start the [MariaDB database container|https://github.com/docker-library/mariadb/blob/eb767c72883d3a79d07e27614233e73988f6fad3/10.0/Dockerfile]:
{noformat}
docker run -it --rm --name crasher -e MYSQL_ROOT_PASSWORD=root mariadb:10.0.21
{noformat}

Afterwards connect with the MariaDB command line client:
{noformat}
docker run -ti --rm --link crasher:mysql mysql mysql --host=mysql -proot
{noformat}

Inside the command line client perform the following querys:
{code:sql}
-- create test database
CREATE DATABASE IF NOT EXISTS db; use db;
-- drop test tables
DROP TABLE IF EXISTS t1; DROP TABLE IF EXISTS t2;
-- create test tables
CREATE TABLE t1 ( id INT(10), value INT(10) ); CREATE TABLE t2 ( id INT(10) );
-- enable full group by
SET SESSION sql_mode = 'ONLY_FULL_GROUP_BY';
-- try to prepare query
PREPARE stmt FROM 'UPDATE t1 t1 SET value = (SELECT 1 FROM t2 WHERE id = t1.id)';
{code}

The last query will return:
{noformat}
ERROR 2013 (HY000): Lost connection to MySQL server during query
{noformat}

And the server crashes because of signal 11. The stack trace is a follows:

{code}
Thread pointer: 0x0x7fa1d3641008
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x7fa1f779ce70 thread_stack 0x48000
mysqld(my_print_stacktrace+0x3d)[0x7fa1f7195a2d]
mysqld(handle_fatal_signal+0x31a)[0x7fa1f6cd375a]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7fa1f633d8d0]
mysqld(_ZN10Item_field15fix_outer_fieldEP3THDPP5FieldPP4Item+0x14c)[0x7fa1f6cf8a1c]
mysqld(_ZN10Item_field10fix_fieldsEP3THDPP4Item+0x4f2)[0x7fa1f6cf9742]
mysqld(_ZN9Item_func10fix_fieldsEP3THDPP4Item+0x1b3)[0x7fa1f6d2f3a3]
mysqld(_Z11setup_condsP3THDP10TABLE_LISTR4ListIS1_EPP4Item+0x1c3)[0x7fa1f6b09573]
mysqld(+0x42f111)[0x7fa1f6b9d111]
mysqld(_ZN30subselect_single_select_engine7prepareEv+0x688)[0x7fa1f6d62788]
mysqld(_ZN14Item_subselect10fix_fieldsEP3THDPP4Item+0xed)[0x7fa1f6d60aed]
mysqld(_Z12setup_fieldsP3THDPP4ItemR4ListIS1_E17enum_mark_columnsPS5_b+0x184)[0x7fa1f6b07594]
mysqld(+0x3f7f7a)[0x7fa1f6b65f7a]
mysqld(_ZN18Prepared_statement7prepareEPKcj+0x6dd)[0x7fa1f6b6771d]
mysqld(_Z22mysql_sql_stmt_prepareP3THD+0x39f)[0x7fa1f6b67caf]
mysqld(_Z21mysql_execute_commandP3THD+0x90e)[0x7fa1f6b4edfe]
mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x1e2)[0x7fa1f6b551d2]
mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1787)[0x7fa1f6b56f87]
mysqld(_Z24do_handle_one_connectionP3THD+0x28b)[0x7fa1f6c2da5b]
mysqld(handle_one_connection+0x40)[0x7fa1f6c2dac0]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x80a4)[0x7fa1f63360a4]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fa1f493e04d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fa1be042408): is an invalid pointer
Connection ID (thread ID): 2
Status: NOT_KILLED
{code}

MariaDB 10.0.21 crashes during preparation of an UPDATE statement with a SELECT subquery in combination with ONLY_FULL_GROUP_BY.

One can reproduce the issue using docker as follows:

First start the [MariaDB database container|https://github.com/docker-library/mariadb/blob/eb767c72883d3a79d07e27614233e73988f6fad3/10.0/Dockerfile]:
{noformat}
docker run -it --rm --name crasher -e MYSQL_ROOT_PASSWORD=root mariadb:10.0.21
{noformat}

Afterwards connect with the MariaDB command line client:
{noformat}
docker run -ti --rm --link crasher:mysql mysql mysql --host=mysql -proot
{noformat}

Inside the command line client perform the following querys:
{code:sql}-- create test database
CREATE DATABASE IF NOT EXISTS db; use db;
-- drop test tables
DROP TABLE IF EXISTS t1; DROP TABLE IF EXISTS t2;
-- create test tables
CREATE TABLE t1 ( id INT(10), value INT(10) ); CREATE TABLE t2 ( id INT(10) );
-- enable full group by
SET SESSION sql_mode = 'ONLY_FULL_GROUP_BY';
-- try to prepare query
PREPARE stmt FROM 'UPDATE t1 t1 SET value = (SELECT 1 FROM t2 WHERE id = t1.id)';
{code}

The last query will return:
{noformat}
ERROR 2013 (HY000): Lost connection to MySQL server during query
{noformat}

And the server crashes because of signal 11. The stack trace is a follows:

{code}
Thread pointer: 0x0x7fa1d3641008
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x7fa1f779ce70 thread_stack 0x48000
mysqld(my_print_stacktrace+0x3d)[0x7fa1f7195a2d]
mysqld(handle_fatal_signal+0x31a)[0x7fa1f6cd375a]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7fa1f633d8d0]
mysqld(_ZN10Item_field15fix_outer_fieldEP3THDPP5FieldPP4Item+0x14c)[0x7fa1f6cf8a1c]
mysqld(_ZN10Item_field10fix_fieldsEP3THDPP4Item+0x4f2)[0x7fa1f6cf9742]
mysqld(_ZN9Item_func10fix_fieldsEP3THDPP4Item+0x1b3)[0x7fa1f6d2f3a3]
mysqld(_Z11setup_condsP3THDP10TABLE_LISTR4ListIS1_EPP4Item+0x1c3)[0x7fa1f6b09573]
mysqld(+0x42f111)[0x7fa1f6b9d111]
mysqld(_ZN30subselect_single_select_engine7prepareEv+0x688)[0x7fa1f6d62788]
mysqld(_ZN14Item_subselect10fix_fieldsEP3THDPP4Item+0xed)[0x7fa1f6d60aed]
mysqld(_Z12setup_fieldsP3THDPP4ItemR4ListIS1_E17enum_mark_columnsPS5_b+0x184)[0x7fa1f6b07594]
mysqld(+0x3f7f7a)[0x7fa1f6b65f7a]
mysqld(_ZN18Prepared_statement7prepareEPKcj+0x6dd)[0x7fa1f6b6771d]
mysqld(_Z22mysql_sql_stmt_prepareP3THD+0x39f)[0x7fa1f6b67caf]
mysqld(_Z21mysql_execute_commandP3THD+0x90e)[0x7fa1f6b4edfe]
mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x1e2)[0x7fa1f6b551d2]
mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1787)[0x7fa1f6b56f87]
mysqld(_Z24do_handle_one_connectionP3THD+0x28b)[0x7fa1f6c2da5b]
mysqld(handle_one_connection+0x40)[0x7fa1f6c2dac0]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x80a4)[0x7fa1f63360a4]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fa1f493e04d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fa1be042408): is an invalid pointer
Connection ID (thread ID): 2
Status: NOT_KILLED
{code}

Tim Düsterhus made changes - 2015-09-05 21:23

Description

MariaDB 10.0.21 crashes during preparation of an UPDATE statement with a SELECT subquery in combination with ONLY_FULL_GROUP_BY.

One can reproduce the issue using docker as follows:

First start the [MariaDB database container|https://github.com/docker-library/mariadb/blob/eb767c72883d3a79d07e27614233e73988f6fad3/10.0/Dockerfile]:
{noformat}
docker run -it --rm --name crasher -e MYSQL_ROOT_PASSWORD=root mariadb:10.0.21
{noformat}

Afterwards connect with the MariaDB command line client:
{noformat}
docker run -ti --rm --link crasher:mysql mysql mysql --host=mysql -proot
{noformat}

Inside the command line client perform the following querys:
{code:sql}-- create test database
CREATE DATABASE IF NOT EXISTS db; use db;
-- drop test tables
DROP TABLE IF EXISTS t1; DROP TABLE IF EXISTS t2;
-- create test tables
CREATE TABLE t1 ( id INT(10), value INT(10) ); CREATE TABLE t2 ( id INT(10) );
-- enable full group by
SET SESSION sql_mode = 'ONLY_FULL_GROUP_BY';
-- try to prepare query
PREPARE stmt FROM 'UPDATE t1 t1 SET value = (SELECT 1 FROM t2 WHERE id = t1.id)';
{code}

The last query will return:
{noformat}
ERROR 2013 (HY000): Lost connection to MySQL server during query
{noformat}

And the server crashes because of signal 11. The stack trace is a follows:

{code}
Thread pointer: 0x0x7fa1d3641008
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x7fa1f779ce70 thread_stack 0x48000
mysqld(my_print_stacktrace+0x3d)[0x7fa1f7195a2d]
mysqld(handle_fatal_signal+0x31a)[0x7fa1f6cd375a]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7fa1f633d8d0]
mysqld(_ZN10Item_field15fix_outer_fieldEP3THDPP5FieldPP4Item+0x14c)[0x7fa1f6cf8a1c]
mysqld(_ZN10Item_field10fix_fieldsEP3THDPP4Item+0x4f2)[0x7fa1f6cf9742]
mysqld(_ZN9Item_func10fix_fieldsEP3THDPP4Item+0x1b3)[0x7fa1f6d2f3a3]
mysqld(_Z11setup_condsP3THDP10TABLE_LISTR4ListIS1_EPP4Item+0x1c3)[0x7fa1f6b09573]
mysqld(+0x42f111)[0x7fa1f6b9d111]
mysqld(_ZN30subselect_single_select_engine7prepareEv+0x688)[0x7fa1f6d62788]
mysqld(_ZN14Item_subselect10fix_fieldsEP3THDPP4Item+0xed)[0x7fa1f6d60aed]
mysqld(_Z12setup_fieldsP3THDPP4ItemR4ListIS1_E17enum_mark_columnsPS5_b+0x184)[0x7fa1f6b07594]
mysqld(+0x3f7f7a)[0x7fa1f6b65f7a]
mysqld(_ZN18Prepared_statement7prepareEPKcj+0x6dd)[0x7fa1f6b6771d]
mysqld(_Z22mysql_sql_stmt_prepareP3THD+0x39f)[0x7fa1f6b67caf]
mysqld(_Z21mysql_execute_commandP3THD+0x90e)[0x7fa1f6b4edfe]
mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x1e2)[0x7fa1f6b551d2]
mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1787)[0x7fa1f6b56f87]
mysqld(_Z24do_handle_one_connectionP3THD+0x28b)[0x7fa1f6c2da5b]
mysqld(handle_one_connection+0x40)[0x7fa1f6c2dac0]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x80a4)[0x7fa1f63360a4]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fa1f493e04d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fa1be042408): is an invalid pointer
Connection ID (thread ID): 2
Status: NOT_KILLED
{code}

MariaDB 10.0.21 crashes during preparation of an UPDATE statement with a SELECT subquery in combination with ONLY_FULL_GROUP_BY.

One can reproduce the issue using docker as follows:

First start the [MariaDB database container|https://github.com/docker-library/mariadb/blob/eb767c72883d3a79d07e27614233e73988f6fad3/10.0/Dockerfile]:
{noformat}
docker run -it --rm --name crasher -e MYSQL_ROOT_PASSWORD=root mariadb:10.0.21
{noformat}

Afterwards connect with the MariaDB command line client:
{noformat}
docker run -ti --rm --link crasher:mariadb mariadb mysql --host=mariadb -proot
{noformat}

Inside the command line client perform the following querys:
{code:sql}-- create test database
CREATE DATABASE IF NOT EXISTS db; use db;
-- drop test tables
DROP TABLE IF EXISTS t1; DROP TABLE IF EXISTS t2;
-- create test tables
CREATE TABLE t1 ( id INT(10), value INT(10) ); CREATE TABLE t2 ( id INT(10) );
-- enable full group by
SET SESSION sql_mode = 'ONLY_FULL_GROUP_BY';
-- try to prepare query
PREPARE stmt FROM 'UPDATE t1 t1 SET value = (SELECT 1 FROM t2 WHERE id = t1.id)';
{code}

The last query will return:
{noformat}
ERROR 2013 (HY000): Lost connection to MySQL server during query
{noformat}

And the server crashes because of signal 11. The stack trace is a follows:

{code}
Thread pointer: 0x0x7fa1d3641008
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x7fa1f779ce70 thread_stack 0x48000
mysqld(my_print_stacktrace+0x3d)[0x7fa1f7195a2d]
mysqld(handle_fatal_signal+0x31a)[0x7fa1f6cd375a]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7fa1f633d8d0]
mysqld(_ZN10Item_field15fix_outer_fieldEP3THDPP5FieldPP4Item+0x14c)[0x7fa1f6cf8a1c]
mysqld(_ZN10Item_field10fix_fieldsEP3THDPP4Item+0x4f2)[0x7fa1f6cf9742]
mysqld(_ZN9Item_func10fix_fieldsEP3THDPP4Item+0x1b3)[0x7fa1f6d2f3a3]
mysqld(_Z11setup_condsP3THDP10TABLE_LISTR4ListIS1_EPP4Item+0x1c3)[0x7fa1f6b09573]
mysqld(+0x42f111)[0x7fa1f6b9d111]
mysqld(_ZN30subselect_single_select_engine7prepareEv+0x688)[0x7fa1f6d62788]
mysqld(_ZN14Item_subselect10fix_fieldsEP3THDPP4Item+0xed)[0x7fa1f6d60aed]
mysqld(_Z12setup_fieldsP3THDPP4ItemR4ListIS1_E17enum_mark_columnsPS5_b+0x184)[0x7fa1f6b07594]
mysqld(+0x3f7f7a)[0x7fa1f6b65f7a]
mysqld(_ZN18Prepared_statement7prepareEPKcj+0x6dd)[0x7fa1f6b6771d]
mysqld(_Z22mysql_sql_stmt_prepareP3THD+0x39f)[0x7fa1f6b67caf]
mysqld(_Z21mysql_execute_commandP3THD+0x90e)[0x7fa1f6b4edfe]
mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x1e2)[0x7fa1f6b551d2]
mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1787)[0x7fa1f6b56f87]
mysqld(_Z24do_handle_one_connectionP3THD+0x28b)[0x7fa1f6c2da5b]
mysqld(handle_one_connection+0x40)[0x7fa1f6c2dac0]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x80a4)[0x7fa1f63360a4]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fa1f493e04d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fa1be042408): is an invalid pointer
Connection ID (thread ID): 2
Status: NOT_KILLED
{code}

Elena Stepanova made changes - 2015-09-06 01:53

Fix Version/s		10.1 [ 16100 ]
Fix Version/s		10.0 [ 16000 ]
Fix Version/s		5.5 [ 15800 ]
Affects Version/s		10.1 [ 16100 ]
Affects Version/s		10.0 [ 16000 ]
Affects Version/s		5.5 [ 15800 ]
Affects Version/s	10.0.21 [ 19406 ]

Elena Stepanova made changes - 2015-09-06 01:54

Status

Open [ 1 ]

Confirmed [ 10101 ]

Elena Stepanova made changes - 2015-09-06 01:54

Assignee

Oleksandr Byelkin [ sanja ]

Oleksandr Byelkin made changes - 2015-10-22 16:32

Status

Confirmed [ 10101 ]

In Progress [ 3 ]

Oleksandr Byelkin made changes - 2015-10-22 17:10

Assignee	Oleksandr Byelkin [ sanja ]	Sergei Petrunia [ psergey ]
Status	In Progress [ 3 ]	In Review [ 10002 ]

Rasmus Johansson (Inactive) made changes - 2015-10-22 17:16

Sprint

10.0.22 [ 17 ]

Rasmus Johansson (Inactive) made changes - 2015-10-22 17:16

Rank

Ranked higher

Sergei Petrunia made changes - 2015-10-27 23:32

Assignee	Sergei Petrunia [ psergey ]	Oleksandr Byelkin [ sanja ]
Status	In Review [ 10002 ]	Stalled [ 10000 ]

Oleksandr Byelkin made changes - 2015-10-28 11:19

Fix Version/s		10.0.22 [ 19700 ]
Fix Version/s		10.1.9 [ 20301 ]
Fix Version/s	10.0 [ 16000 ]
Fix Version/s	5.5 [ 15800 ]
Fix Version/s	10.1 [ 16100 ]
Resolution		Fixed [ 1 ]
Status	Stalled [ 10000 ]	Closed [ 6 ]

Oleksandr Byelkin made changes - 2015-11-20 15:52

Fix Version/s

5.3.13 [ 12602 ]

Oleksandr Byelkin made changes - 2015-11-20 16:04

Fix Version/s		5.5.47 [ 20300 ]
Fix Version/s	5.3.13 [ 12602 ]

Sergei Golubchik made changes - 2021-12-06 21:41

Workflow

MariaDB v3 [ 71366 ]

MariaDB v4 [ 149578 ]

People

Assignee:: Oleksandr Byelkin

Reporter:: Tim Düsterhus

Votes:: 4 Vote for this issue

Watchers:: 10 Start watching this issue

Dates

Created:: 2015-09-05 21:19

Updated:: 2015-11-20 16:04

Resolved:: 2015-10-28 11:19

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server

Details

Description

Attachments

Attachments

Activity

People

Dates

Git Integration