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

Usage of invalid addresses after rerun failed sc-server #79

Closed
NikitaZotov opened this issue Jun 21, 2022 · 0 comments · Fixed by #316
Closed

Usage of invalid addresses after rerun failed sc-server #79

NikitaZotov opened this issue Jun 21, 2022 · 0 comments · Fixed by #316
Assignees
Labels
bug Something isn't working help wanted Extra attention is needed L2 Medium issue

Comments

@NikitaZotov
Copy link
Member

Describe the bug
If sc-server wasn't normally closed, then after rerun of sc-server there will be invalid addresses in memory.

To Reproduce
Steps to reproduce the behavior:

  1. Run sc-server;
  2. Add elements with sc-server API;
  3. Press on Ctrl+Z;
  4. Rerun sc-server;
  5. Find last created with sc-server API.

Expected behavior
There wiil be opportunity to save kb version history and checkout the last correct of them.

Desktop (please complete the following information):

  • OS: [e.g. Ubuntu 20.04]
  • Version [e.g. 0.7.0]
@NikitaZotov NikitaZotov added bug Something isn't working sc-server Changes in sc-server module help wanted Extra attention is needed labels Jun 21, 2022
@NikitaZotov NikitaZotov added L2 Medium issue and removed sc-server Changes in sc-server module labels Sep 15, 2022
NikitaZotov pushed a commit to NikitaZotov/sc-machine that referenced this issue Apr 4, 2023
@NikitaZotov NikitaZotov linked a pull request Nov 28, 2023 that will close this issue
3 tasks
@NikitaZotov NikitaZotov self-assigned this Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed L2 Medium issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant