| /dports/www/mattermost-server/mattermost-server-6.0.2/jobs/ |
| H A D | schedulers.go | 53 schedulers.schedulers = append(schedulers.schedulers, srv.DataRetentionJob.MakeScheduler())
57 schedulers.schedulers = append(schedulers.schedulers, srv.MessageExportJob.MakeScheduler())
65 schedulers.schedulers = append(schedulers.schedulers, ldapSyncInterface.MakeScheduler())
69 schedulers.schedulers = append(schedulers.schedulers, migrationsInterface.MakeScheduler())
73 schedulers.schedulers = append(schedulers.schedulers, pluginsInterface.MakeScheduler())
77 schedulers.schedulers = append(schedulers.schedulers, expiryNotifyInterface.MakeScheduler())
81 schedulers.schedulers = append(schedulers.schedulers, activeUsersInterface.MakeScheduler())
89 schedulers.schedulers = append(schedulers.schedulers, cloudInterface.MakeScheduler())
97 schedulers.schedulers = append(schedulers.schedulers, importDeleteInterface.MakeScheduler())
101 schedulers.schedulers = append(schedulers.schedulers, exportDeleteInterface.MakeScheduler())
[all …]
|
| H A D | server.go | 44 schedulers *Schedulers member
74 if srv.schedulers == nil {
76 } else if srv.schedulers.running {
79 srv.schedulers.Start()
98 if srv.schedulers == nil {
100 } else if !srv.schedulers.running {
103 srv.schedulers.Stop()
110 if srv.schedulers != nil {
111 srv.schedulers.handleClusterLeaderChange(isLeader)
|
| H A D | schedulers_test.go | 88 for _, element := range jobServer.schedulers.nextRunTimes {
100 for _, element := range jobServer.schedulers.nextRunTimes {
111 for _, element := range jobServer.schedulers.nextRunTimes {
123 for _, element := range jobServer.schedulers.nextRunTimes {
134 jobServer.schedulers.handleConfigChange(nil, nil)
136 for _, element := range jobServer.schedulers.nextRunTimes {
154 jobServer.schedulers.handleConfigChange(nil, nil)
|
| /dports/devel/py-buildbot/buildbot-3.4.1/buildbot/ |
| H A D | scheduler.py | 17 from buildbot.schedulers.basic import AnyBranchScheduler
18 from buildbot.schedulers.basic import Scheduler
19 from buildbot.schedulers.dependent import Dependent
20 from buildbot.schedulers.timed import Nightly
21 from buildbot.schedulers.timed import Periodic
22 from buildbot.schedulers.triggerable import Triggerable
23 from buildbot.schedulers.trysched import Try_Jobdir
24 from buildbot.schedulers.trysched import Try_Userpass
|
| /dports/devel/py-buildbot/buildbot-3.4.1/buildbot/data/ |
| H A D | schedulers.py | 22 from buildbot.db.schedulers import SchedulerAlreadyClaimedError
52 dbdict = yield self.master.db.schedulers.getScheduler(
79 schedulers = yield self.master.db.schedulers.getSchedulers(
82 [self.db2data(schdict) for schdict in schedulers],
112 yield self.master.db.schedulers.enable(schedulerid, v)
118 return self.master.db.schedulers.findSchedulerId(name)
122 d = self.master.db.schedulers.setSchedulerMaster(
141 schedulers = yield self.master.db.schedulers.getSchedulers(
143 for sch in schedulers:
144 yield self.master.db.schedulers.setSchedulerMaster(sch['id'], None)
|
| /dports/finance/odoo/odoo-19d77c2a03335eb95a686bd69a1b56b38e87d609/odoo/addons/event_sms/tests/ |
| H A D | test_sms_schedule.py | 51 …schedulers = self.env['event.mail'].search([('event_id', '=', self.event_0.id), ('interval_type', …
52 self.assertEqual(len(schedulers), 1)
53 …self.assertEqual(schedulers.scheduled_date, self.event_0.create_date, 'event: incorrect scheduled …
56 self.assertEqual(len(schedulers.mail_registration_ids), 3)
57 self.assertTrue(all(m.mail_sent is True for m in schedulers.mail_registration_ids))
58 …self.assertEqual(schedulers.mapped('mail_registration_ids.registration_id'), self.event_0.registra…
72 …schedulers = self.env['event.mail'].search([('event_id', '=', self.event_0.id), ('interval_type', …
73 self.assertEqual(len(schedulers), 1, 'event: wrong scheduler creation')
74 … self.assertEqual(schedulers[0].scheduled_date, self.event_0.date_begin + relativedelta(days=-3))
78 schedulers.execute()
|
| /dports/devel/py-buildbot/buildbot-3.4.1/buildbot/test/fakedb/ |
| H A D | schedulers.py | 19 from buildbot.db import schedulers
68 self.schedulers = {}
80 self.schedulers[row.id] = row.name
136 for sch_id, sch_name in self.schedulers.items():
139 new_id = (max(self.schedulers) + 1) if self.schedulers else 1
140 self.schedulers[new_id] = name
144 if schedulerid in self.schedulers:
147 name=self.schedulers[schedulerid],
158 self.getScheduler(id) for id in self.schedulers
193 self.schedulers[schedulerid] = name
[all …]
|
| /dports/devel/py-apscheduler/APScheduler-3.8.1/docs/modules/schedulers/ |
| H A D | background.rst | 1 :mod:`apscheduler.schedulers.background`
4 .. automodule:: apscheduler.schedulers.background
17 :meth:`~apscheduler.schedulers.blocking.BackgroundScheduler.start` will start the scheduler and it …
28 - ``examples/schedulers/background.py``
29 …(`view online <https://github.com/agronholm/apscheduler/tree/3.x/examples/schedulers/background.py…
|
| H A D | blocking.rst | 1 :mod:`apscheduler.schedulers.blocking`
4 .. automodule:: apscheduler.schedulers.blocking
17 :meth:`~apscheduler.schedulers.blocking.BlockingScheduler.start`, the call never returns.
29 - ``examples/schedulers/blocking.py``
30 …(`view online <https://github.com/agronholm/apscheduler/tree/3.x/examples/schedulers/blocking.py>`…
|
| H A D | tornado.rst | 1 :mod:`apscheduler.schedulers.tornado`
4 .. automodule:: apscheduler.schedulers.tornado
26 - ``examples/schedulers/tornado_.py``
27 …(`view online <https://github.com/agronholm/apscheduler/tree/3.x/examples/schedulers/tornado_.py>`…
|
| /dports/devel/py-buildbot/buildbot-3.4.1/docs/developer/ |
| H A D | schedulers.rst | 6 Buildbot schedulers are the process objects responsible for requesting builds.
9 Many schedulers (e.g., :bb:sched:`SingleBranchScheduler`) request builds in response to changes fro…
26 A scheduler is a subclass of :py:class:`~buildbot.schedulers.base.BaseScheduler`.
45 A scheduler that needs to be notified of new changes should call :py:meth:`~buildbot.schedulers.bas…
48 Once consumption has started, the :py:meth:`~buildbot.schedulers.base.BaseScheduler.gotChange` meth…
55 …dbot.db.buildsets.BuildsetConnector.addBuildset` after applying behaviors common to all schedulers.
68 …In a future version, schedulers will be converted to handle reconfiguration as reconfigurable serv…
75 Simple schedulers can consult the :py:attr:`~buildbot.schedulers.base.BaseScheduler.active` attribu…
77 Most schedulers, however, will implement the ``activate`` method to begin any processing expected o…
78 That may involve calling :py:meth:`~buildbot.schedulers.base.BaseScheduler.startConsumingChanges`, …
[all …]
|
| /dports/devel/elixir-paratize/elixir-paratize-2.1.5/lib/paratize/ |
| H A D | task_options.ex | 7 … - number of workers, default: the number of CPU cores given by `:erlang.system_info(:schedulers)`.
10 defstruct size: :schedulers, timeout: 5000
11 @type t :: %__MODULE__{size: :schedulers | non_neg_integer, timeout: :infinity | non_neg_integer}
19 :schedulers -> :erlang.system_info(:schedulers)
|
| /dports/devel/py-buildbot/buildbot-3.4.1/buildbot/test/integration/ |
| H A D | test_integration_scheduler_reconfigure.py | 19 from buildbot.plugins import schedulers
43 schedulers.AnyBranchScheduler(
46 schedulers.ForceScheduler(
65 schedulers.AnyBranchScheduler(
68 schedulers.ForceScheduler(
|
| /dports/devel/elixir-quantum/quantum-elixir-2.2.6/test/quantum/ |
| H A D | scheduler_test.exs | 53 schedulers = Map.get(context, :schedulers, [])
55 for scheduler <- schedulers do
81 @tag schedulers: [Scheduler]
96 @tag schedulers: [Scheduler]
117 @tag schedulers: [Scheduler]
138 @tag schedulers: [Scheduler]
155 @tag schedulers: [Scheduler]
175 @tag schedulers: [Scheduler]
194 @tag schedulers: [Scheduler]
214 @tag schedulers: [Scheduler]
[all …]
|
| /dports/misc/py-gluoncv/gluon-cv-0.9.0/gluoncv/utils/ |
| H A D | lr_scheduler.py | 18 def __init__(self, schedulers): argument
20 assert(len(schedulers) > 0)
25 self.schedulers = []
26 for lr in schedulers:
35 self.schedulers.append(scheduler)
43 ind = len(self.schedulers) - 1
48 lr = self.schedulers[ind]
|
| /dports/www/tikiwiki/tiki-21.2/templates/ |
| H A D | tiki-admin_schedulers.tpl | 12 {if $schedulers|count > 0}
50 {section name=scheduler loop=$schedulers}
51 {$scheduler_name = $schedulers[scheduler].name|escape}
62 {$schedulers[scheduler].description|escape}
65 {$schedulers[scheduler].task|escape}
68 {$schedulers[scheduler].run_time|escape}
71 {$schedulers[scheduler].status|escape|ucfirst}
77 <input type="checkbox" {if $schedulers[scheduler].re_run}checked{/if} disabled>
80 {if $schedulers[scheduler].stalled}
87 {if $schedulers[scheduler].stalled}
[all …]
|
| /dports/lang/erlang-runtime23/otp-OTP-23.3.4.10/erts/emulator/beam/ |
| H A D | erl_dirty_bif.tab | 22 # Static declaration of BIFs that should execute on dirty schedulers.
32 # all BIFs will of course execute on normal schedulers.
35 # '--enable-dirty-schedulers-test', BIFs with the types 'dirty-cpu-test',
36 # and 'dirty-io-test' will unconditionally execute on dirty schedulers.
38 # on normal schedulers.
41 # execute on normal schedulers.
55 # Functions below will execute on dirty schedulers when emulator has
56 # been configured for testing dirty schedulers. This is used for test
58 # on dirty schedulers on a real system.
|
| /dports/lang/erlang-runtime24/otp-OTP-24.1.7/erts/emulator/beam/ |
| H A D | erl_dirty_bif.tab | 22 # Static declaration of BIFs that should execute on dirty schedulers.
32 # all BIFs will of course execute on normal schedulers.
35 # '--enable-dirty-schedulers-test', BIFs with the types 'dirty-cpu-test',
36 # and 'dirty-io-test' will unconditionally execute on dirty schedulers.
38 # on normal schedulers.
41 # execute on normal schedulers.
55 # Functions below will execute on dirty schedulers when emulator has
56 # been configured for testing dirty schedulers. This is used for test
58 # on dirty schedulers on a real system.
|
| /dports/lang/erlang-runtime22/otp-OTP-22.3.4.24/erts/emulator/beam/ |
| H A D | erl_dirty_bif.tab | 22 # Static declaration of BIFs that should execute on dirty schedulers.
32 # all BIFs will of course execute on normal schedulers.
35 # '--enable-dirty-schedulers-test', BIFs with the types 'dirty-cpu-test',
36 # and 'dirty-io-test' will unconditionally execute on dirty schedulers.
38 # on normal schedulers.
41 # execute on normal schedulers.
55 # Functions below will execute on dirty schedulers when emulator has
56 # been configured for testing dirty schedulers. This is used for test
58 # on dirty schedulers on a real system.
|
| /dports/lang/erlang-wx/otp-OTP-24.1.7/erts/emulator/beam/ |
| H A D | erl_dirty_bif.tab | 22 # Static declaration of BIFs that should execute on dirty schedulers.
32 # all BIFs will of course execute on normal schedulers.
35 # '--enable-dirty-schedulers-test', BIFs with the types 'dirty-cpu-test',
36 # and 'dirty-io-test' will unconditionally execute on dirty schedulers.
38 # on normal schedulers.
41 # execute on normal schedulers.
55 # Functions below will execute on dirty schedulers when emulator has
56 # been configured for testing dirty schedulers. This is used for test
58 # on dirty schedulers on a real system.
|
| /dports/lang/erlang/otp-OTP-24.1.7/erts/emulator/beam/ |
| H A D | erl_dirty_bif.tab | 22 # Static declaration of BIFs that should execute on dirty schedulers.
32 # all BIFs will of course execute on normal schedulers.
35 # '--enable-dirty-schedulers-test', BIFs with the types 'dirty-cpu-test',
36 # and 'dirty-io-test' will unconditionally execute on dirty schedulers.
38 # on normal schedulers.
41 # execute on normal schedulers.
55 # Functions below will execute on dirty schedulers when emulator has
56 # been configured for testing dirty schedulers. This is used for test
58 # on dirty schedulers on a real system.
|
| /dports/lang/erlang-java/otp-OTP-24.1.7/erts/emulator/beam/ |
| H A D | erl_dirty_bif.tab | 22 # Static declaration of BIFs that should execute on dirty schedulers.
32 # all BIFs will of course execute on normal schedulers.
35 # '--enable-dirty-schedulers-test', BIFs with the types 'dirty-cpu-test',
36 # and 'dirty-io-test' will unconditionally execute on dirty schedulers.
38 # on normal schedulers.
41 # execute on normal schedulers.
55 # Functions below will execute on dirty schedulers when emulator has
56 # been configured for testing dirty schedulers. This is used for test
58 # on dirty schedulers on a real system.
|
| /dports/java/springframework31/spring-framework-3.1.4.RELEASE/projects/org.springframework.context/src/main/java/org/springframework/scheduling/annotation/ |
| H A D | ScheduledAnnotationBeanPostProcessor.java | 194 Map<String, ? super Object> schedulers = new HashMap<String, Object>(); in onApplicationEvent() local
195 schedulers.putAll(applicationContext.getBeansOfType(TaskScheduler.class)); in onApplicationEvent()
196 schedulers.putAll(applicationContext.getBeansOfType(ScheduledExecutorService.class)); in onApplicationEvent()
197 if (schedulers.size() == 0) { in onApplicationEvent()
199 } else if (schedulers.size() == 1) { in onApplicationEvent()
200 this.registrar.setScheduler(schedulers.values().iterator().next()); in onApplicationEvent()
201 } else if (schedulers.size() >= 2){ in onApplicationEvent()
205 …"explicitly within the configureTasks() callback. Found the following beans: " + schedulers.keySet… in onApplicationEvent()
|
| /dports/lang/erlang-runtime21/otp-OTP-21.3.8.24/erts/emulator/beam/ |
| H A D | erl_dirty_bif.tab | 22 # Static declaration of BIFs that should execute on dirty schedulers.
32 # all BIFs will of course execute on normal schedulers.
35 # '--enable-dirty-schedulers-test', BIFs with the types 'dirty-cpu-test',
36 # and 'dirty-io-test' will unconditionally execute on dirty schedulers.
38 # on normal schedulers.
41 # execute on normal schedulers.
55 # Functions below will execute on dirty schedulers when emulator has
56 # been configured for testing dirty schedulers. This is used for test
58 # on dirty schedulers on a real system.
|
| /dports/devel/py-dask/dask-2021.11.2/docs/source/ |
| H A D | custom-graphs.rst | 6 cases, you can interact directly with the Dask schedulers. These schedulers
12 schedulers improve or expand to distributed memory, code written to use Dask
13 schedulers will advance as well.
25 sections, the schedulers take a task graph (which is a dict of tuples of
74 Dask schedulers differ in the following ways:
78 2. You get a variety of schedulers ranging from single machine, single core
80 3. The Dask single-machine schedulers have logic to execute the graph in a
|