Prepare release 0.2 (#136)

docs/references/errors.md

@@ -72,7 +72,7 @@ Make sure, when updating a service endpoint, to assign it a new uri.
 
 You can force the override using the `"force": true` field in the discover request, but beware that this can lead in-flight invocations to an unrecoverable error state.  
 
-See the [versioning documentation](http://docs.restate.dev/deployment-operations/versioning) for more information.
+See the [versioning documentation](https://docs.restate.dev/services/upgrades-removal) for more information.
 
 ## META0005 {#META0005}
 
@@ -89,7 +89,7 @@ When implementing a new service revision, make sure that:
 * The service instance type and the key definition, if any, is exactly the same as of the previous revisions.
 * The Protobuf contract and message definitions are backward compatible.
 
-See the [versioning documentation](http://docs.restate.dev/deployment-operations/versioning) for more information.
+See the [versioning documentation](https://docs.restate.dev/services/upgrades-removal) for more information.
 
 ## RT0001 {#RT0001}
 
@@ -105,7 +105,7 @@ Suggestions:
 
 Cannot start Restate because the configuration cannot be parsed. Check the configuration file and the environment variables provided.
 
-For a complete list of configuration options, and a sample configuration, check http://docs.restate.dev/deployment-operations/configuration
+For a complete list of configuration options, and a sample configuration, check https://docs.restate.dev/restate/configuration
 
 ## RT0003 {#RT0003}
 

docs/restate/logging.md

@@ -45,6 +45,7 @@ When testing Restate locally, we recommend keeping the default configuration.
 When deploying in production, we recommend setting the log level to `info` and enabling the `Json` format in conjunction with a log collector, so you can later inspect and filter logs based on its event fields.
 
 We recommend to set up logging to a more verbose filter, and use the `Pretty` format. Some example filters:
-    * `info,restate_ingress_grpc=trace,restate_invoker=trace,restate=debug,hyper=debug` for network related issues
-    * `info,restate_worker::partition::effects=debug` to get insights on the state machine effects
-    * `info,restate_meta=trace` to check service discovery and registration
+
+* `info,restate_ingress_grpc=trace,restate_invoker=trace,restate=debug,hyper=debug` for network related issues
+* `info,restate_worker::partition::effects=debug` to get insights on the state machine effects
+* `info,restate_meta=trace` to check service discovery and registration

docusaurus.config.js

@@ -57,9 +57,9 @@ const config = {
               variableInjector, // replaces eg VAR::RESTATE_DIST_VERSION with config strings
               {
                 replacements: {
-                  RESTATE_DIST_VERSION: '0.1.7',
-                  TYPESCRIPT_SDK_VERSION: '1.0.33',
-                  TOUR_VERSION: 'v0.0.4',
+                  RESTATE_DIST_VERSION: '0.2.0',
+                  TYPESCRIPT_SDK_VERSION: '0.2.0',
+                  TOUR_VERSION: 'v0.2.0',
                 },
               }
             ]

static/schemas/config_schema.json

@@ -63,7 +63,7 @@
             "max_interval": "10s",
             "type": "Exponential"
           },
-          "tmp_dir": "/var/folders/tw/68_ctnh50rn41q721zt5pwfc0000gn/T/invoker-0189d175ff3e7087ada868460b8e75db"
+          "tmp_dir": "/tmp/invoker-018a22ade7907754a1d9efcf97fb2e4c"
         },
         "partitions": 1024,
         "storage_query": {
@@ -307,7 +307,7 @@
               "max_interval": "10s",
               "type": "Exponential"
             },
-            "tmp_dir": "/var/folders/tw/68_ctnh50rn41q721zt5pwfc0000gn/T/invoker-0189d175ff3e704fb5ecfdca68505c8e"
+            "tmp_dir": "/tmp/invoker-018a22ade7907469a8ef400edc0b101e"
           },
           "$ref": "#/definitions/InvokerOptions"
         },
@@ -316,7 +316,7 @@
           "description": "Number of partitions to be used to process messages.\n\nNote: This config entry **will be removed** in future Restate releases, as the partitions number will be dynamically configured depending on the load.",
           "default": 1024,
           "type": "integer",
-          "format": "uint32",
+          "format": "uint64",
           "minimum": 0.0
         }
       }
@@ -511,13 +511,13 @@
         },
         "inactivity_timeout": {
           "title": "Inactivity timeout",
-          "description": "This timer is used to gracefully shutdown a bidirectional stream after inactivity on both request and response streams.\n\nWhen this timer is fired, the invocation will be closed gracefully by closing the request stream, triggering a suspension on the sdk, in case the sdk is waiting on a completion. This won't affect the response stream.\n\nCan be configured using the [`humantime`](https://docs.rs/humantime/latest/humantime/fn.parse_duration.html) format.",
+          "description": "This timer guards against stalled service/handler invocations. Once it expires, Restate triggers a graceful termination by asking the service invocation to suspend (which preserves intermediate progress).\n\nThe 'abort timeout' is used to abort the invocation, in case it doesn't react to the request to suspend.\n\nCan be configured using the [`humantime`](https://docs.rs/humantime/latest/humantime/fn.parse_duration.html) format.",
           "default": "1m",
           "type": "string"
         },
         "abort_timeout": {
           "title": "Abort timeout",
-          "description": "This timer is used to forcefully shutdown an invocation when only the response stream is open.\n\nWhen protocol mode is `restate_service_metadata::ProtocolType::RequestResponse`, this timer will start as soon as the replay of the journal is completed. When protocol mode is `restate_service_metadata::ProtocolType::BidiStream`, this timer will start after the request stream has been closed. Check `inactivity_timeout` to configure a timer on the request stream.\n\nWhen this timer is fired, the response stream will be aborted, potentially **interrupting** user code! If the user code needs longer to complete, then this value needs to be set accordingly.\n\nCan be configured using the [`humantime`](https://docs.rs/humantime/latest/humantime/fn.parse_duration.html) format.",
+          "description": "This timer guards against stalled service/handler invocations that are supposed to terminate. The abort timeout is started after the 'inactivity timeout' has expired and the service/handler invocation has been asked to gracefully terminate. Once the timer expires, it will abort the service/handler invocation.\n\nThis timer potentially **interrupts** user code. If the user code needs longer to gracefully terminate, then this value needs to be set accordingly.\n\nCan be configured using the [`humantime`](https://docs.rs/humantime/latest/humantime/fn.parse_duration.html) format.",
           "default": "1m",
           "type": "string"
         },
@@ -549,7 +549,7 @@
         "tmp_dir": {
           "title": "Temporary directory",
           "description": "Temporary directory to use for the invoker temporary files. If empty, the system temporary directory will be used instead.",
-          "default": "/var/folders/tw/68_ctnh50rn41q721zt5pwfc0000gn/T/invoker-0189d175ff3e7e1cb10a99b29c51216c",
+          "default": "/tmp/invoker-018a22ade78f71aa9d6bd866dc6cf545",
           "type": "string"
         },
         "concurrency_limit": {