lib/temporal/worker.rb
# binary_checksum: The binary checksum identifies the version of workflow worker code. It is set on each completed or failed workflow
#   task. It is present in API responses that return workflow execution info, and is shown in temporal-web and tctl.
#   It is traditionally a checksum of the application binary. However, Temporal server treats this as an opaque
#   identifier and it does not have to be a "checksum". Typical values for a Ruby application might include the hash
#   of the latest git commit or a semantic version number.
#
#   It can be used to reset workflow history to before a "bad binary" was deployed. Bad checksum values can also
#   be marked at the namespace level. This will cause Temporal server to reject any polling for workflow tasks
#   from workers with these bad versions.
#
#   See https://docs.temporal.io/docs/tctl/how-to-use-tctl/#recovery-from-bad-deployment----auto-reset-workflow
The binary checksum identifies the version of workflow worker code. It is set on each completed or failed workflow
task. It is present in API responses that return workflow execution info, and is shown in temporal-web and tctl.
It is traditionally a checksum of the application binary. However, Temporal server treats this as an opaque
identifier and it does not have to be a "checksum". Typical values for a Ruby application might include the hash
of the latest git commit or a semantic version number.

It can be used to reset workflow history to before a "bad binary" was deployed. Bad checksum values can also
be marked at the namespace level. This will cause Temporal server to reject any polling for workflow tasks
from workers with these bad versions.


The binary checksum identifies the version of workflow worker code . It is set on each completed or failed workflow task . It is present in API responses that return workflow execution info and is shown in temporal - web and tctl . It is traditionally a checksum of the application binary . However Temporal server treats this as an opaque identifier and it does not have to be a " checksum " . Typical values for a Ruby application might include the hash of the latest git commit or a semantic version number . It can be used to reset workflow history to before a " bad binary " was deployed . Bad checksum values can also be marked at the namespace level . This will cause Temporal server to reject any polling for workflow tasks from workers with these bad versions .
def start
      workflows.each_pair do |(namespace, task_queue), lookup|
        pollers << workflow_poller_for(namespace, task_queue, lookup)
      end
      activities.each_pair do |(namespace, task_queue), lookup|
        pollers << activity_poller_for(namespace, task_queue, lookup)
      end
      trap_signals
      pollers.each(&:start)
      sleep 1 while !shutting_down?
    end
def start workflows . each_pair do | ( namespace , task_queue ) , lookup | pollers << workflow_poller_for ( namespace , task_queue , lookup ) end activities . each_pair do | ( namespace , task_queue ) , lookup | pollers << activity_poller_for ( namespace , task_queue , lookup ) end trap_signals pollers . each ( & :start ) sleep 1 while ! shutting_down? end
binary_checksum: The binary checksum identifies the version of workflow worker code.
binary_checksum : The binary checksum identifies the version of workflow worker code .
# keep the main thread alive