fix: Validate message fields before protobuf encoding for better erro… #163
BulkBeingAnnotations
25 errors and 17 warnings
|
Build, Tag, and Push Image (examples/map/forward_message)
Process completed with exit code 1.
|
|
Build, Tag, and Push Image (examples/sink/log)
The strategy configuration was canceled because "docker_publish.examples_map_forward_mess" failed
|
|
Build, Tag, and Push Image (examples/sourcetransform/event_time_filter)
The strategy configuration was canceled because "docker_publish.examples_map_forward_mess" failed
|
|
Build, Tag, and Push Image (examples/map/multiproc_map)
The strategy configuration was canceled because "docker_publish.examples_map_forward_mess" failed
|
|
Build, Tag, and Push Image (examples/accumulator/streamsorter)
The strategy configuration was canceled because "docker_publish.examples_map_forward_mess" failed
|
|
Build, Tag, and Push Image (examples/sink/async_log)
The strategy configuration was canceled because "docker_publish.examples_map_forward_mess" failed
|
|
Build, Tag, and Push Image (examples/batchmap/flatmap)
The strategy configuration was canceled because "docker_publish.examples_map_forward_mess" failed
|
|
Build, Tag, and Push Image (examples/reduce/counter)
The strategy configuration was canceled because "docker_publish.examples_map_forward_mess" failed
|
|
Build, Tag, and Push Image (examples/reduce/counter)
Response status code does not indicate success: 401 (Unauthorized).
|
|
Build, Tag, and Push Image (examples/map/even_odd)
The strategy configuration was canceled because "docker_publish.examples_map_forward_mess" failed
|
|
Build, Tag, and Push Image (examples/map/even_odd)
Response status code does not indicate success: 401 (Unauthorized).
|
|
Build, Tag, and Push Image (examples/source/simple_source)
The strategy configuration was canceled because "docker_publish.examples_map_forward_mess" failed
|
|
Build, Tag, and Push Image (examples/source/simple_source)
The operation was canceled.
|
|
Build, Tag, and Push Image (examples/map/flatmap)
The strategy configuration was canceled because "docker_publish.examples_map_forward_mess" failed
|
|
Build, Tag, and Push Image (examples/map/flatmap)
The operation was canceled.
|
|
Build, Tag, and Push Image (examples/reducestream/sum)
The strategy configuration was canceled because "docker_publish.examples_map_forward_mess" failed
|
|
Build, Tag, and Push Image (examples/reducestream/sum)
The operation was canceled.
|
|
Build, Tag, and Push Image (examples/reducestream/counter)
The strategy configuration was canceled because "docker_publish.examples_map_forward_mess" failed
|
|
Build, Tag, and Push Image (examples/reducestream/counter)
The operation was canceled.
|
|
Build, Tag, and Push Image (examples/sideinput/simple_sideinput)
The strategy configuration was canceled because "docker_publish.examples_map_forward_mess" failed
|
|
Build, Tag, and Push Image (examples/sideinput/simple_sideinput)
The operation was canceled.
|
|
Build, Tag, and Push Image (examples/sideinput/simple_sideinput/udf)
The strategy configuration was canceled because "docker_publish.examples_map_forward_mess" failed
|
|
Build, Tag, and Push Image (examples/sideinput/simple_sideinput/udf)
The operation was canceled.
|
|
Build, Tag, and Push Image (examples/mapstream/flatmap_stream)
The strategy configuration was canceled because "docker_publish.examples_map_forward_mess" failed
|
|
Build, Tag, and Push Image (examples/mapstream/flatmap_stream)
The operation was canceled.
|
|
Workflow syntax warning:
.github/workflows/build-push.yaml#L12
.github/workflows/build-push.yaml (Line: 12, Col: 9): Conditional expression contains literal text outside replacement tokens. This will cause the expression to always evaluate to truthy. Did you mean to put the entire expression inside ${{ }}?
|
|
Build, Tag, and Push Image (examples/map/forward_message)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build, Tag, and Push Image (examples/reduce/counter)
Back off 18.812 seconds before retry.
|
|
Build, Tag, and Push Image (examples/reduce/counter)
Failed to download action 'https://api.github.com/repos/docker/setup-qemu-action/tarball/c7c53464625b32c7a7e944ae62b3e17d2b600130'. Error: Response status code does not indicate success: 401 (Unauthorized). 5C01:189100:1943BA3:6ADA497:69B24C63
|
|
Build, Tag, and Push Image (examples/reduce/counter)
Back off 17.355 seconds before retry.
|
|
Build, Tag, and Push Image (examples/reduce/counter)
Failed to download action 'https://api.github.com/repos/docker/setup-qemu-action/tarball/c7c53464625b32c7a7e944ae62b3e17d2b600130'. Error: Response status code does not indicate success: 401 (Unauthorized). 5C00:16E297:1AD4285:7196F9C:69B24C51
|
|
Build, Tag, and Push Image (examples/map/even_odd)
Back off 10.128 seconds before retry.
|
|
Build, Tag, and Push Image (examples/map/even_odd)
Failed to download action 'https://api.github.com/repos/docker/setup-qemu-action/tarball/c7c53464625b32c7a7e944ae62b3e17d2b600130'. Error: Response status code does not indicate success: 401 (Unauthorized). F001:215A1D:144B7E5:14A47B6:69B24C6C
|
|
Build, Tag, and Push Image (examples/map/even_odd)
Back off 25.235 seconds before retry.
|
|
Build, Tag, and Push Image (examples/map/even_odd)
Failed to download action 'https://api.github.com/repos/docker/setup-qemu-action/tarball/c7c53464625b32c7a7e944ae62b3e17d2b600130'. Error: Response status code does not indicate success: 401 (Unauthorized). F000:2060FB:1425403:147EB91:69B24C52
|
|
Build, Tag, and Push Image (examples/source/simple_source)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build, Tag, and Push Image (examples/map/flatmap)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build, Tag, and Push Image (examples/reducestream/sum)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build, Tag, and Push Image (examples/reducestream/counter)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build, Tag, and Push Image (examples/sideinput/simple_sideinput)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build, Tag, and Push Image (examples/sideinput/simple_sideinput/udf)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build, Tag, and Push Image (examples/mapstream/flatmap_stream)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|