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
Copy file name to clipboardExpand all lines: blog/2023-07-05-implement-cadence-worker-from-scratch.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ func main(){
33
33
34
34
Next, let's define some basic configurations for the worker. In real production environment, you may need to implement them in configurational languages, but in this tutorial, let's just hard code them for now.
35
35
36
-
```Go
36
+
```go
37
37
varHostPort = "127.0.0.1:7933"
38
38
varDomain = "test-domain"
39
39
varTaskListName = "test-worker"
@@ -45,7 +45,7 @@ Note that the domain is what we've already registered in advance. We will need t
45
45
46
46
Then let's write a simple function to build a Cadence client on gRPC in your worker, which will communicate with the Cadence backend continuously.
If you had already added this repo earlier, run `helm repo update` to retrieve the latest versions of the packages. You can then run `helm search repo cadence` to see the charts.
Copy file name to clipboardExpand all lines: blog/zonal-isolation-v1/zonal-isolation-v1.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -103,7 +103,7 @@ To support Zonal Isolation, please upgrade your SDK versions:
103
103
Drains can be done via the [Admin APIs](https://github.com/cadence-workflow/cadence-idl/blob/50a4ee241e50c6baab8e5d47540b176c5ee022a4/proto/cadence-workflow/cadence/admin/v1/service.proto#L125) of cadence-frontend or CLI.
104
104
105
105
You can check the help message for the CLI by running:
0 commit comments