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

Safe signal handling on call-ins with an option to block signals and avoid EINTR errors #22

Merged
merged 4 commits into from
Mar 30, 2023

Conversation

berwynhoyt
Copy link
Collaborator

  • Implement safe signal handling on call-ins by allowing user to pass optional _yottadb.unblock_ydb_signals to yottadb.require() as an entry-exit function for M
  • Fix bug in call-in parameter processor cast2ydb() which sometimes type-checked an incorrect parameter to cip()
  • Fix: added proper cleanup in cip() when issuing zlinking error

… optional _yottadb.unblock_ydb_signals to

yottadb.require() as an entry-exit function for M
- Fix bug in call-in parameter processor cast2ydb() which sometimes type-checked an incorrect
parameter to cip()
- Fix: added proper cleanup in cip() when issuing zlinking error
@berwynhoyt
Copy link
Collaborator Author

Note: This still requires unit tests for the signal handling and signal documentation in README.md

… right from ydb_init()

- Add substantial documentation section on signal safety
- Benchmark and document the calling overhead of signal blocking
- Document alternative requirements if blocking is not used.
- Add signals unit test to lua-yottadb
@berwynhoyt berwynhoyt merged commit fa1939d into anet-be:master Mar 30, 2023
@berwynhoyt berwynhoyt deleted the safe_signals branch July 10, 2024 02:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant