-
Notifications
You must be signed in to change notification settings - Fork 15
Unclear error if no leader #331
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
Labels
Comments
GRISHNOV
added a commit
that referenced
this issue
Dec 28, 2022
Added validation of the connection to the `utils.get_space` method before receiving the space through the connection. Closes #331
GRISHNOV
added a commit
that referenced
this issue
Dec 28, 2022
Added validation of the connection to the `utils.get_space` method before receiving the space through the connection. Closes #331
It was also reported as #95. |
GRISHNOV
added a commit
that referenced
this issue
Jan 18, 2023
Added validation of the master connection to the `utils.get_space` method before receiving the space through the connection. Closes #331
GRISHNOV
added a commit
that referenced
this issue
Jan 18, 2023
Fixed a typo of the fiber status call when processing `RELOAD_SCHEMA_TIMEOUT` in `call_reload_schema`. Before that, an error occurred in this case with description: `calling 'status' on bad self (fiber expected, got table)`. To reproduce the error before this fix, it is enough to checkout to the one commit back and perform the action described in #331.
GRISHNOV
added a commit
that referenced
this issue
Jan 18, 2023
Added validation of the master connection to the `utils.get_space` method before receiving the space from the connection. Closes #331
GRISHNOV
added a commit
that referenced
this issue
Jan 18, 2023
Fixed a typo of the fiber status call when processing `RELOAD_SCHEMA_TIMEOUT` in `call_reload_schema`. Before that, an error occurred in this case with description: `calling 'status' on bad self (fiber expected, got table)`. To reproduce the error before this fix, it is enough to checkout to the one commit back and perform the action described in #331.
GRISHNOV
added a commit
that referenced
this issue
Jan 19, 2023
Added validation of the master connection to the `utils.get_space` method before receiving the space from the connection. Closes #331
GRISHNOV
added a commit
that referenced
this issue
Jan 19, 2023
Fixed a typo of the fiber status call when processing `RELOAD_SCHEMA_TIMEOUT` in `call_reload_schema`. Before that, an error occurred in this case with description: `calling 'status' on bad self (fiber expected, got table)`. To reproduce the error before this fix, it is enough to checkout to the one commit back and perform the action described in #331.
GRISHNOV
added a commit
that referenced
this issue
Jan 19, 2023
Added validation of the master presence in replicaset and the master connection to the `utils.get_space` method before receiving the space from the connection. Closes #331
GRISHNOV
added a commit
that referenced
this issue
Jan 19, 2023
Fixed a typo of the fiber status call when processing `RELOAD_SCHEMA_TIMEOUT` in `call_reload_schema`. Before that, an error occurred in this case with description: `calling 'status' on bad self (fiber expected, got table)`. To reproduce the error before this fix, it is enough to checkout to the one commit back and perform the action described in #331.
GRISHNOV
added a commit
that referenced
this issue
Jan 19, 2023
Fixed a bug of the fiber status call when processing `RELOAD_SCHEMA_TIMEOUT` in `call_reload_schema`. Before that, an error occurred in this case with description: `calling 'status' on bad self (fiber expected, got table)`. To reproduce the error before this fix, it is enough to checkout to the one commit back and perform the action described in #331. Now the fibers for schema reloading are correctly canceled if the timeout on schema reloading is reached.
GRISHNOV
added a commit
that referenced
this issue
Jan 19, 2023
Fixed fiber cancel on schema reload timeout. Before that, an error occurred in timeout case with description: `calling 'status' on bad self (fiber expected, got table)`. To reproduce the error before this fix, it is enough to checkout to the one commit back and perform the action described in #331.
GRISHNOV
added a commit
that referenced
this issue
Jan 19, 2023
Added validation of the master presence in replicaset and the master connection to the `utils.get_space` method before receiving the space from the connection. Closes #331
GRISHNOV
added a commit
that referenced
this issue
Jan 19, 2023
Fixed fiber cancel on schema reload timeout. Before that, an error occurred in timeout case with description: `calling 'status' on bad self (fiber expected, got table)`. To reproduce the error before this fix, it is enough to checkout to the one commit back and perform the action described in #331.
DifferentialOrange
pushed a commit
that referenced
this issue
Jan 20, 2023
Added validation of the master presence in replicaset and the master connection to the `utils.get_space` method before receiving the space from the connection. Closes #331
DifferentialOrange
pushed a commit
that referenced
this issue
Jan 20, 2023
Fixed fiber cancel on schema reload timeout. Before that, an error occurred in timeout case with description: `calling 'status' on bad self (fiber expected, got table)`. To reproduce the error before this fix, it is enough to checkout to the one commit back and perform the action described in #331.
DifferentialOrange
added a commit
that referenced
this issue
Feb 2, 2023
Overview This release introduces a breaking change with removing a deprecated feature: `crud.len(space_id)`. This release also introduces a Cartridge clusterwide config to setup `crud.cfg`. Breaking changes You cannot use space id as a space identifier in `crud.len` anymore. Use space name instead. New features * Timeout condition for the validation of master presence in replicaset and for the master connection (#95). * Cartridge clusterwide configuration for `crud.cfg` (#332). Changes * Forbid using space id in `crud.len` (#255). Fixes * Add validation of the master presence in replicaset and the master connection to the `utils.get_space` method before receiving the space from the connection (#331). * Fix fiber cancel on schema reload timeout in `call_reload_schema` (PR #337).
DifferentialOrange
added a commit
that referenced
this issue
Feb 2, 2023
Overview This release introduces a breaking change with removing a deprecated feature: `crud.len(space_id)`. This release also introduces a Cartridge clusterwide config to setup `crud.cfg`. Breaking changes You cannot use space id as a space identifier in `crud.len` anymore. Use space name instead. New features * Timeout condition for the validation of master presence in replicaset and for the master connection (#95). * Cartridge clusterwide configuration for `crud.cfg` (#332). Changes * Forbid using space id in `crud.len` (#255). Fixes * Add validation of the master presence in replicaset and the master connection to the `utils.get_space` method before receiving the space from the connection (#331). * Fix fiber cancel on schema reload timeout in `call_reload_schema` (PR #336).
DifferentialOrange
added a commit
that referenced
this issue
Feb 2, 2023
Overview This release introduces a breaking change with removing a deprecated feature: `crud.len(space_id)`. This release also introduces a Cartridge clusterwide config to setup `crud.cfg`. Breaking changes You cannot use space id as a space identifier in `crud.len` anymore. Use space name instead. New features * Timeout condition for the validation of master presence in replicaset and for the master connection (#95). * Cartridge clusterwide configuration for `crud.cfg` (#332). Changes * Forbid using space id in `crud.len` (#255). Fixes * Add validation of the master presence in replicaset and the master connection to the `utils.get_space` method before receiving the space from the connection (#331). * Fix fiber cancel on schema reload timeout in `call_reload_schema` (PR #336).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem:
if
A cryptic error is returned.
Error:
How to reproduce:
Repoducer package:
repro.zip
Line that triggers the error:
crud/crud/common/utils.lua
Line 100 in 7504da3
The text was updated successfully, but these errors were encountered: