You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The abstract class KernelProcessStep has an on_activate method, which one would assume is called when the step is activated, but the method is never called.
To Reproduce
Steps to reproduce the behavior:
Create a KernelProcessStep subclass that overrides the on_activate method,
Put the step into a process,
Run the process: the on_activate method is never called.
Expected behavior
The KernelProcessStep.on_activate method would be called when a step is activated, in both the local and Dapr runtimes. This would act as a form of zero-argument init method for when a step is activated.
Screenshots
Result of the code search showing that on_activate is never called.
Platform
OS: Windows
IDE: gVim + PowerShell
Language: Python
Source: pip package version 1.16.0
Additional context
n/a
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
Bug: Process Framework KernelProcessStep.on_activate is never called
Python: Bug: Process Framework KernelProcessStep.on_activate is never called
Nov 26, 2024
Describe the bug
The abstract class
KernelProcessStep
has anon_activate
method, which one would assume is called when the step is activated, but the method is never called.To Reproduce
Steps to reproduce the behavior:
KernelProcessStep
subclass that overrides theon_activate
method,on_activate
method is never called.Expected behavior
The
KernelProcessStep.on_activate
method would be called when a step is activated, in both the local and Dapr runtimes. This would act as a form of zero-argument init method for when a step is activated.Screenshots
Result of the code search showing that
on_activate
is never called.Platform
Additional context
n/a
The text was updated successfully, but these errors were encountered: