73 receive exit signal - Githubissues

anyproto / any-sync-dockercompose

docker-compose for testing any-sync

MIT License

234 stars 29 forks source link

73 receive exit signal #74

Closed fb929 closed 6 days ago

fb929 commented 1 week ago

[x] I understand that contributing to this repository will require me to agree with the CLA

Description

What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[x] 🧑‍💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 tech-docs
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

hellodword commented 1 week ago

https://man7.org/linux/man-pages/man7/signal.7.html

The signals SIGKILL and SIGSTOP cannot be caught, blocked, or ignored.

Edit:

Noticed that these 3 containers are not that important

fb929 commented 6 days ago

Noticed that these 3 containers are not that important

yes, these containers are auxiliary. the main changes for this PR are here: https://github.com/anyproto/any-sync-node/pull/105 https://github.com/anyproto/any-sync-filenode/pull/117 https://github.com/anyproto/any-sync-consensusnode/pull/46 https://github.com/anyproto/any-sync-coordinator/pull/79