0FiebddlmZddlZddlmZGddZdZedZdZdS) ) annotationsN)without_property_validationceZdZdZdZdZdS)DashboardComponentaTBase class for Dask.distributed UI dashboard components. This class must have two attributes, ``root`` and ``source``, and one method ``update``: * source: a Bokeh ColumnDataSource * root: a Bokeh Model * update: a method that consumes the messages dictionary found in distributed.bokeh.messages c"d|_d|_dSN)sourceroot)selfs Ilib/python3.11/site-packages/distributed/dashboard/components/__init__.py__init__zDashboardComponent.__init__s  cdS)z=Reads from bokeh.distributed.messages and updates self.sourceN)r messagess r updatezDashboardComponent.updatesrN)__name__ __module__ __qualname____doc__r rrrr rrsA  LLLLLrrctj||fd|t||dS)aAdd periodic callback to doc in a way that avoids reference cycles If we instead use ``doc.add_periodic_callback(component.update, 100)`` then the component stays in memory as a reference cycle because its method is still around. This way we avoid that and let things clean up a bit more nicely. TODO: we still have reference cycles. Docs seem to be referred to by their add_periodic_callback methods. c"tSrr)refsr z'add_periodic_callback..)s fSkkrN)weakrefradd_periodic_callback_attach)doc componentintervalrs @r rrsJ +i C11118<<< CrcJ|}||dSdSrr)rcomps r rr-s, 355D  rct|dst|_|j|dS)N components)hasattrsetr%add)rr s r rr4s; 3 % %Ny!!!!!r) __future__rrbokeh.core.propertiesrrrrrrrr r+s""""""======LLLLLLLL(" """""r