summaryrefslogtreecommitdiff
path: root/src/leap/common/events/client.py
AgeCommit message (Collapse)Author
2016-02-29[tests] adapt events tests to recent changesKali Kaneko
2015-10-07[bug] consider STANDALONE for the pathsIvan Alejandro
Since we need to write a file we have to consider whether we are running in 'standalone' mode or not to use the right path prefix. - Related: #7512
2015-09-16[refactor] move checking flag to main moduleKali Kaneko
2015-07-29[bug] register and unregister controlled by flagVictor Shyba
Since register and unregister cant be used without full zmq initialization, it should make sense to also check flag for them.
2015-07-29[refactor] Extract flags check to callerVictor Shyba
Checking was done inside of emit method. Doing on emit function at a module level makes it cleaner with less lines inside of check.
2015-07-28[bug] Consider events flag when ensuring clientVictor Shyba
Change EventsClientThread behavior so it won't start anymore if the events flag is set to False
2015-07-21[feature] add global flag for disabling the events frameworkKali Kaneko
this will be used to allow the unittests to disable the events framework. this way, emit() will become a passthrough. note that, until now, the basetest class is making use of the threaded version of the client, which launches a zmq tornado-based ioloop. this is wrong, and will have to be addressed in a future commit. we'll have to make use of the global EVENTS_ENABLED flag in the txclient version when those changes are made. Related: #7259 Relases: 0.4.2
2015-07-20[refactor] remove use of reactor in threaded version of events clientKali Kaneko
the idea is that we'll be able to use the threaded version of the client, which makes use of the tornado ioloop, in a non-twisted module, like the main graphical client probably will be in the near future.
2015-06-26[bug] run callback from thread in events clientdrebs
2015-06-11[bug] remove extraneous data from events logsdrebs
The emission of an event was being logged twice, and the second time was logging the pickled content of the event. This pickled content contained line breaks and other things that caused strange output on the client log. This commit removes the second loggin of the event pickled content. Closes #7130.
2015-05-28[bug] use dict keys to iterateVictor Shyba
We ran into a RuntimeError yesterday on this line, the callback can modify this dict and make the iteration raise an error. Using keys method to iterate is safer. See http://stackoverflow.com/questions/11941817/python-runtimeerror-dictionary-changed-size-during-iteration-how-to-avoid-th/11941855#11941855
2015-05-27[feat] refactor events to use ZMQdrebs
Before this commit, protobuf and protobuf.socketrpc were used to serialize and transmit messages between events clients. This change implements a simpler ZMQ client/server events mechanism that uses ZMQ sockets for transmitting messages from clients to server and to redistribute such messages to subscribed clients. Closes: #6359
2013-09-03change verbosity level in loggingKali Kaneko
2013-09-03cosmetic changes to importsKali Kaneko
2013-09-03Fix Exception useKali Kaneko
2013-07-25Fix events doc about reqcbk signature. Closes #3261drebs
2013-07-24Add doc and tests about events sync/async behaviour.drebs
* Also fix docstrings identation so sphynx doesn't complain.
2013-07-24Trying to init events server raises when given port is not free.drebs
* Also fix and improve some tests.
2013-07-24Refactor events so components become clients.drebs