Merge branch 'main' into py_ast

.github/workflows/cli.yml

@@ -113,7 +113,7 @@ jobs:
           # spawning a script prints only a PID
           ./openc3.sh cli script spawn INST/procedures/checks.rb | grep -v "^\s*\d+\s*$"
           # run a script that will fail and look for the failure message
-          ./openc3.sh cli script run --wait 10 INST/procedures/checks.rb | tee /dev/tty | grep -q "script failed"
+          ./openc3.sh cli script run --wait 20 INST/procedures/checks.rb | tee /dev/tty | grep -q "script failed"
           # run a script that will complete successfully
           ./openc3.sh cli script run INST/procedures/stash.rb | tee /dev/tty | grep "script complete"
       - name: openc3.sh util save,load

.github/workflows/playwright.yml

@@ -50,6 +50,8 @@ jobs:
           docker ps
           docker logs cosmos-openc3-cosmos-init-1
           docker logs cosmos-openc3-operator-1
+          docker logs cosmos-openc3-cosmos-cmd-tlm-api-1
+          docker logs cosmos-openc3-cosmos-script-runner-api-1
         # Build a test plugin for playwright and a copy so we can 'upgrade'
       - name: Build plugin
         shell: 'script -q -e -c "bash {0}"'

README.md

@@ -33,7 +33,7 @@ After configuring OpenC3 COSMOS to talk to your hardware, you immediately can us
 
    - Script Runner allows for running OpenC3 COSMOS test procedures or any other Ruby code from a graphical environment that highlights each line as it executes. At anytime during execution, the script can be paused or stopped. If a telemetry check fails or any other exception occurs, the script is immediately stopped and the user notified.
 
-   - Script Runner also allows you to break your operational or test procedures down into discret test cases that each complete with either SUCCESS or FAILURE. After running, a script report is automatically created for you. Convenient features such as the ability to loop testing help get the kinks out of your system before formal runs.
+   - Script Runner also allows you to break your operational or test procedures down into discrete test cases that each complete with either SUCCESS or FAILURE. After running, a script report is automatically created for you. Convenient features such as the ability to loop testing help get the kinks out of your system before formal runs.
 
 1. **Packet Viewer**
 

compose.yaml

@@ -114,6 +114,7 @@ services:
       OPENC3_BUCKET_USERNAME: "${OPENC3_BUCKET_USERNAME}"
       OPENC3_BUCKET_PASSWORD: "${OPENC3_BUCKET_PASSWORD}"
       OPENC3_SERVICE_PASSWORD: "${OPENC3_SERVICE_PASSWORD}"
+      ANYCABLE_REDIS_URL: "redis://${OPENC3_REDIS_USERNAME}:${OPENC3_REDIS_PASSWORD}@${OPENC3_REDIS_HOSTNAME}:${OPENC3_REDIS_PORT}"
     env_file:
       - ".env"
 
@@ -147,6 +148,7 @@ services:
       OPENC3_SR_BUCKET_USERNAME: "${OPENC3_SR_BUCKET_USERNAME}"
       OPENC3_SR_BUCKET_PASSWORD: "${OPENC3_SR_BUCKET_PASSWORD}"
       OPENC3_SERVICE_PASSWORD: "${OPENC3_SERVICE_PASSWORD}"
+      ANYCABLE_REDIS_URL: "redis://${OPENC3_REDIS_USERNAME}:${OPENC3_REDIS_PASSWORD}@${OPENC3_REDIS_HOSTNAME}:${OPENC3_REDIS_PORT}"
     env_file:
       - ".env"
 
@@ -155,7 +157,8 @@ services:
     image: "${OPENC3_REGISTRY}/${OPENC3_NAMESPACE}/openc3-operator${OPENC3_IMAGE_SUFFIX}:${OPENC3_TAG}"
     restart: "unless-stopped"
     # ports:
-    #  - "127.0.0.1:7779:7779" # Open port for the demo router
+    #   - "127.0.0.1:7779:7779" # Open port for the demo router
+    #   - "127.0.0.1:8081:8081/udp" # Open a udp port
     depends_on:
       - "openc3-redis"
       - "openc3-redis-ephemeral"

docs.openc3.com/docs/configuration/interfaces.md

@@ -74,6 +74,14 @@ INTERFACE INTERFACE_NAME openc3/interfaces/tcpip_client_interface.py host.docker
 
 The TCPIP server interface creates a TCPIP server which listens for incoming connections and dynamically creates sockets which communicate with the target. This interface is used for targets which open a socket and try to connect to a server.
 
+NOTE: To receive connections from outside the internal docker network you need to expose the TCP port in the compose.yaml file. For example, to allow connections on port 8080 find the openc3-operator section and modify like the following example:
+
+```yaml
+openc3-operator:
+  ports:
+    - "127.0.0.1:8080:8080" # Open tcp port 8080
+```
+
 | Parameter          | Description                                                                           | Required |
 | ------------------ | ------------------------------------------------------------------------------------- | -------- |
 | Write Port         | Port to write commands to (can be the same as read port)                              | Yes      |
@@ -120,6 +128,14 @@ INTERFACE INTERFACE_NAME openc3/interfaces/tcpip_client_interface.py 8080 8080 1
 
 The UDP interface uses UDP packets to send and receive telemetry from the target.
 
+NOTE: To receive UDP packets from outside the internal docker network you need to expose the UDP port in the compose.yaml file. For example, to allow UDP packets on port 8081 find the openc3-operator section and modify like the following example:
+
+```yaml
+openc3-operator:
+  ports:
+    - "127.0.0.1:8081:8081/udp" # Open udp port 8081
+```
+
 | Parameter         | Description                                                                                                        | Required | Default                                       |
 | ----------------- | ------------------------------------------------------------------------------------------------------------------ | -------- | --------------------------------------------- |
 | Host              | Host name or IP address of the machine to send and receive data with                                               | Yes      |