{"push_id":1252304161,"size":1,"distinct_size":1,"ref":"refs/heads/inputseek","head":"fd98e3f95db8a8b4697dd5103ca0ff1db657c7d8","before":"77395d55d6a40982c114c3392aaaa4d4f3627901","commits":[{"sha":"fd98e3f95db8a8b4697dd5103ca0ff1db657c7d8","author":{"name":"Luca Longinotti","email":"b2d2d1094bc2a1197b054b6da9d98b1e0e2788aa@longi.li"},"message":"Base: enhance the module reset function with knowing which module actually called the reset.\nInputs: supply their module ID to the reset function calls so they can identify them.\nBA/Statistics/Fisualizer: add, but ignore, the new reset source ID parameter.\nOutput: check the new reset source ID parameter, and if the reset comes from the source this module is\nactually responsible for, ensure the TS_RESET event (and its lone packet/container) are committed to the\noutput module's queue. This way, TS_RESET is always correctly part of the event stream, even if Special Events\nare ignored by this output module (for example if you only record Polarity Events). To avoid duplicates, we\nfilter out the \"normal\" TS_RESET Special Event, if it is detected.","distinct":true,"url":"https://api.github.com/repos/inilabs/caer/commits/fd98e3f95db8a8b4697dd5103ca0ff1db657c7d8"}]}
{"actor":{"display_login":"llongi"}}