version bump

.gitpod.yml

@@ -1,4 +1,4 @@
-image: temporalio/gitpod-edu:1.2
+image: temporalio/gitpod-edu:1.3
 tasks:
     # task links a bash configuration file to a location that is not
     # specific to this course (/etc/bash.bashrc sources it from there)
@@ -15,6 +15,14 @@ tasks:
         --ui-port 8080 \
         --db-filename /workspace/.cluster-persistence.db
     openMode: tab-after
+  - name: Microservice
+    command: |
+      source /workspace/edu-interacting-with-workflows-java-code/.bash.cfg
+      cd utilities/microservice
+      mvn clean compile
+      echo "Translation Microservice running on this terminal"
+      mvn exec:java -Dexec.mainClass="translationapi.Microservice"
+    openMode: split-right
   - name: Display Web UI
     command: |
       echo "Waiting for server...."

README.md

@@ -21,7 +21,7 @@ For the exercises, make sure to run `temporal server start-dev --ui-port 8080 --
 Samples
 Directory Name | Description
 :----------------------------------| :---------------------------------------------------------------------------------------------------------------------
-`samples/custom-search-attributes` | [Shows a sample of how to use Custom Search Attributes to find queries where the order for pizzas has failed](samples/custom-search-attributes)
+`samples/custom-search-attributes` | [Shows a sample of how to use Custom Search Attributes to find queries where the order for pizzas has failed](samples/custom-search-attributes/README.md)
 
 ## Reference
 

exercises/async-activity-completion/README.md

@@ -9,8 +9,9 @@ During this exercise, you will:
 Make your changes to the code in the `practice` subdirectory (look for `TODO` comments that will guide you to where you should make changes to the code). If you need a hint or want to verify your changes, look at the complete version in the `solution` subdirectory.
 
 ### Prerequisites
-This exercises uses the microservice from Temporal 102. If you are in the GitPod environment, this microservice is
-already running. If you are _not_ using GitPod, you can start the microservice from a separate terminal by changing to
+This exercises uses the microservice from Temporal 102. **If you are in the GitPod 
+environment, this microservice is already running.** If you are _not_ using 
+GitPod, you can start the microservice from a separate terminal by changing to
 the `utilities/microservice` directory and using the following command:
 
 ```bash

exercises/async-activity-completion/practice/src/main/java/asyncactivitycompletion/VerifyAndCompleteTranslation.java

@@ -22,13 +22,11 @@ public static void main(String[] args) throws ExecutionException, InterruptedExc
 
 
     // TODO: PART C: Read in the taskToken from args[0] and decode it from Base64
-    byte[] taskToken = Base64.getDecoder().decode(args[0]);
 
-    // TODO: PART C: Get the translated text from args[1]
+    // TODO: PART C: Get the translated text from args[1] and use it to create a
+    // new TranslationActivityOutput object
 
     ActivityCompletionClient activityCompletionClient = client.newActivityCompletionClient();
-
-    TranslationActivityOutput result = new TranslationActivityOutput(result);
 
     // TODO: PART C: Call the `complete()` method using the `activityCompletionClient` object
     // from above. The call should contain the `taskToken` and the `result`.

exercises/async-activity-completion/solution/src/main/java/asyncactivitycompletion/VerifyAndCompleteTranslation.java

@@ -25,11 +25,11 @@ public static void main(String[] args) throws ExecutionException, InterruptedExc
 
     // Pass in the translated text as a command line argument and pretend to "verify"
     // the results
-    String result = args[1];
+    TranslationActivityOutput result = new TranslationActivityOutput(args[1]);
 
     ActivityCompletionClient activityCompletionClient = client.newActivityCompletionClient();
 
-    activityCompletionClient.complete(taskToken, new TranslationActivityOutput(result));
+    activityCompletionClient.complete(taskToken, result);
 
     System.exit(0);
   }

exercises/querying-workflows/README.md

@@ -99,9 +99,9 @@ temporal workflow query \
 
 It will produce the same result:
 
-```
+```bash
 Query result:
-["Out for delivery"]
+  QueryResult  "Out for delivery"
 ```
 
 ## Part E: Sending a Signal and Querying a Closed Workflow
@@ -129,7 +129,7 @@ completes successfully, then Query the closed Workflow.
    5. You should get the result
    ```bash
    Query result:
-   ["Order complete"]
+     QueryResult  "Order complete"
    ```
 
 ### This is the end of the exercise.

exercises/sending-signals-client/practice/src/main/java/sendingsignalsclient/SignalClient.java

@@ -15,7 +15,7 @@ public static void main(String[] args) throws Exception {
     // TODO: PART A: Set Workflow ID
     PizzaWorkflow workflow = client.newWorkflowStub(PizzaWorkflow.class, "CHANGE_ME");
 
-    // TODO: PART A: Call fulfillOrderSignal, passing `true`
+    // TODO: PART B: Call fulfillOrderSignal, passing `true`
 
     System.exit(0);
   }

samples/custom-search-attributes/README.md

@@ -23,7 +23,7 @@ Within the Pizza Workflow code, we will now dynamically update Search Attributes
 
 ## Part D: Running Your Workflow
 
-1. In one terminal, run `mvn exec:java -Dexec.mainClass='customsearchattributes.PizzaWorker` to start the Worker.
+1. In one terminal, run `mvn exec:java -Dexec.mainClass='customsearchattributes.PizzaWorker'` to start the Worker.
 2. In another terminal and run `mvn exec:java -Dexec.mainClass='customsearchattributes.Starter'` to initiate execution of the Workflow. Now, try your query to retrieve the results. Recall that visibility is eventually consistent, so not all updates are going to be immediately reflected. If you don't see your update, wait a bit an try again. 
 
 ## Part E: Querying Workflows by Search Attributes