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
When using Actors, the server-side logs will always contain warnings about methods with invalid signatures, which is fine if it wasn't true for the required ones being part of ServerImplBaseCtx.
The messages are generated here and should imo not warn about required methods, as it just bloats the server logs.
== APP == method GetStateManager is illegal, err = the latest return type actor.StateManagerContext of method "GetStateManager" is not error, just skip it
== APP == method ID is illegal, err = the latest return type string of method "ID" is not error, just skip it
== APP == method SetID is illegal, err = num out invalid, just skip it
== APP == method SetStateManager is illegal, err = num out invalid, just skip it
== APP == method Type is illegal, err = the latest return type string of method "Type" is not error, just skip it
The text was updated successfully, but these errors were encountered:
When checking for valid Actor methods, the SDK no longer emits warnings about invalid or inappropriate method signatures for the ones needed to be implemented for each Actor type.
Fixesdapr#585
Signed-off-by: Willi Eggeling <[email protected]>
When checking for valid Actor methods, the SDK no longer emits warnings about invalid or inappropriate method signatures for the ones needed to be implemented for each Actor type.
Fixesdapr#585
Signed-off-by: Willi Eggeling <[email protected]>
Describe the bug
When using Actors, the server-side logs will always contain warnings about methods with invalid signatures, which is fine if it wasn't true for the required ones being part of
ServerImplBaseCtx
.The messages are generated here and should imo not warn about required methods, as it just bloats the server logs.
To Reproduce
Expected behavior
The output matches the one listed in the README
Actual behavior
Server-side logs contain the following warnings:
The text was updated successfully, but these errors were encountered: