mirror of
https://github.com/valitydev/salt.git
synced 2024-11-08 17:33:54 +00:00
Software to automate the management and configuration of any infrastructure or application at scale. Get access to the Salt software package repository here:
cb326f06da
`cls.instance_map` was growing unbounded. This was because `io_loop.close()` was invoked before `stream.close()`. The stategy used to fix this issue was discussed in pull request #28530 and can be summarized as follows: The `close()` method on the async object will be called if it exists. This will be called before the `io_loop.close()` to give the async object the opportunity to close its stream. The del of the async object will continue to happen after io_loop.close(). This is to maintain the fix from pull request #27343. Per file change details: salt/utils/async.py: - Implemented the close logic described above. salt/transport/ipc.py: - Ensured that `close()` may be invoked more than once safely. - In IPCServer, `self.stream` was never actually used. Removed references to it to avoid confusion. salt/transport/zeromq.py: - Ensured that `close()` may be invoked more than once safely. salt/transport/tcp.py: - Ensured that `close()` may be invoked more than once safely. - Changed `destroy()` methods to `close()` methods since they involved a stream that should be closed before `io_loop.close()`. - In SaltMessageClient, added more checks for `self._closing`. This makes exit cleaner by not attempting to reconnect while closing. - Removed the code associate with pull request #28113. This code is no longer needed now that the stream is closed before the io_loop. Signed-off-by: Sergey Kizunov <sergey.kizunov@ni.com> |
||
---|---|---|
conf | ||
doc | ||
pkg | ||
requirements | ||
salt | ||
scripts | ||
tests | ||
.codeclimate.yml | ||
.editorconfig | ||
.gitignore | ||
.pylintrc | ||
.testing.pylintrc | ||
.travis.yml | ||
AUTHORS | ||
Contributing.rst | ||
COPYING | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
setup.py |
================== What is SaltStack? ================== Salt is a new approach to infrastructure management. Easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in *seconds*. Salt delivers a dynamic communication bus for infrastructures that can be used for orchestration, remote execution, configuration management and much more. Documentation ============= Installation instructions, getting started guides, and in-depth API documentation. http://docs.saltstack.com IRC Chat ======== Join the vibrant, helpful and positive SaltStack chat room in Freenode at #salt. There is no need to introduce yourself, or ask permission to join in, just help and be helped! Make sure to wait for an answer, sometimes it may take a few moments for someone to reply. http://webchat.freenode.net/?channels=salt&uio=Mj10cnVlJjk9dHJ1ZSYxMD10cnVl83 Salt Air ======== The SaltStack YouTube channel is filled with Salt videos and presentations. Watch the latest Salt Air episodes for updates from Thomas on development, catch tutorials, and stay on the cutting edge of Salt. http://www.youtube.com/user/saltstack Mailing List ============ The SaltStack community users mailing list is hosted by Google groups. Anyone can post to ask questions about SaltStack products and anyone can help answer. Join the conversation! https://groups.google.com/forum/#!forum/salt-users You may subscribe to the list without a Google account by emailing salt-users+subscribe@googlegroups.com and you may post to the list by emailing salt-users@googlegroups.com Developing Salt =============== The Salt development team is welcoming, positive, and dedicated to helping people get new code and fixes into SaltStack projects. Log into GitHub and get started with one of the largest developer communities in the world. The following links should get you started: * https://github.com/saltstack * http://docs.saltstack.com/en/latest/topics/development/index.html Reporting Issues ================ To report an issue with Salt, please follow the guidelines for filing bug reports: * http://docs.saltstack.com/en/develop/topics/development/reporting_bugs.html