Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assert on inserting into _priv tuple with wrong object id #6295

Closed
ImeevMA opened this issue Aug 6, 2021 · 0 comments
Closed

Assert on inserting into _priv tuple with wrong object id #6295

ImeevMA opened this issue Aug 6, 2021 · 0 comments
Assignees
Labels
bug Something isn't working crash
Milestone

Comments

@ImeevMA
Copy link
Collaborator

ImeevMA commented Aug 6, 2021

Function schema_find_name() throws an assert if a tuple with an invalid object identifier is received. This error is only available in debug mode.

Reproducer:

box.space._priv:replace{1, 2, 'function', 1000000, box.priv.X}

Result:

tarantool: /home/mergen/work/dev/src/box/schema.cc:720: const char* schema_find_name(schema_object_type, uint32_t): Assertion `false' failed.

Solution: remove assert assert(false); at the end of schema_find_name().

@ImeevMA ImeevMA added the bug Something isn't working label Aug 6, 2021
ImeevMA added a commit that referenced this issue Aug 7, 2021
Prior to this patch, an assertion was throwed if a tuple with an
incorrect id was inserted into the _priv system space. This bug
appeared only in the debug build.

Closes #6295
@kyukhin kyukhin added the crash label Aug 10, 2021
@kyukhin kyukhin added the teamL label Aug 13, 2021
ImeevMA added a commit that referenced this issue Aug 16, 2021
Prior to this patch, an assertion was throwed if a tuple with an
incorrect id was inserted into the _priv system space. This bug
appeared only in the debug build.

Closes #6295
@kyukhin kyukhin added this to the 2.8.3 milestone Aug 19, 2021
@igormunkin igormunkin added the 1sp label Aug 20, 2021
ImeevMA added a commit that referenced this issue Sep 3, 2021
Prior to this patch, an assertion was throwed if a tuple with an
incorrect id was inserted into the _priv system space. This bug
appeared only in the debug build.

Closes #6295
ImeevMA added a commit that referenced this issue Sep 29, 2021
Prior to this patch, an assertion was thrown if a tuple with an invalid
id was inserted into the _priv system space. This bug appeared only in
the debug build.

Closes #6295
ImeevMA added a commit that referenced this issue Oct 1, 2021
Prior to this patch, an assertion was thrown if a tuple with an invalid
id was inserted into the _priv system space. This bug appeared only in
the debug build.

Closes #6295
kyukhin pushed a commit that referenced this issue Oct 5, 2021
Prior to this patch, an assertion was thrown if a tuple with an invalid
id was inserted into the _priv system space. This bug appeared only in
the debug build.

Closes #6295

(cherry picked from commit 60f1681)
@kyukhin kyukhin closed this as completed in 60f1681 Oct 5, 2021
ImeevMA added a commit to ImeevMA/tarantool that referenced this issue Mar 11, 2022
Prior to this patch, an assertion was thrown if a tuple with an invalid
id was inserted into the _priv system space. This bug appeared only in
the debug build.

Closes tarantool#6295

NO_DOC=Fix for debug build only.

(cherry picked from commit 60f1681)
kyukhin pushed a commit that referenced this issue Mar 11, 2022
Prior to this patch, an assertion was thrown if a tuple with an invalid
id was inserted into the _priv system space. This bug appeared only in
the debug build.

Closes #6295

NO_DOC=Fix for debug build only.

(cherry picked from commit 60f1681)
@igormunkin igormunkin removed the teamL label Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working crash
Projects
None yet
Development

No branches or pull requests

3 participants