fix: add udp ports to docker compose

[MasterPtato]

Changes

[MasterPtato]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• fix: get pb manager test working e2e again #2721
• fix: convert runner protocol to protobuf #2702
• fix: even more actor api changes #2714
• chore: flatten actor api spec #2698
• fix: increase default actor kill timeout to 5s #2701
• fix: dont clear ingress ports on reschedule #2700
• fix: add cpu constraints to oci config #2697
• fix: api changes #2692
• fix: fix logs for new actors #2649
• feat: add actor queue #2644
• feat: add actor kv to runners #2638
• feat: get multi actors working e2e on docker compose #2637
• fix: add udp ports to docker compose #2635 👈 (View in Graphite)
• chore: fix merge conflicts #2634
• fix: get new actors working on docker compose #2623
• fix: figure out actor log shipping #2622
• fix(pegboard): convert ws manager socket to unix socket #2478
• fix(pb): get new actor ids working e2e #2471
• feat: implement new actor ids #2467
• feat(pb): get multi-actors working e2e, add resources for builds #2465
• feat(pb): add runner logs #2447
• feat: add runners to pb protocol #2433
• chore(pegboard): add exit code log from container runner #2477
• fix(workflows): fix branch version bug #2475
• chore(pegboard): replace computing image size manually with using tar bytes read #2625
• fix: make pb image downloads random, remove prewarm from pb protocol #2784
• fix: clean up worker threads in the event of an error #2783
• fix: make query_as macros retry #2773
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[cloudflare-workers-and-pages]

Deploying rivet with    Cloudflare Pages

Latest commit:	b682e5d
Status:	🚫  Build failed.

View logs

[cloudflare-workers-and-pages]

Deploying rivet-studio with    Cloudflare Pages

Latest commit:	b682e5d
Status:	🚫  Build failed.

View logs

[cloudflare-workers-and-pages]

Deploying rivet-hub with    Cloudflare Pages

Latest commit:	b682e5d
Status:	🚫  Build failed.

View logs

[claude]

Claude finished @MasterPtato's task —— View job

---

Code Review: Add UDP Ports to Docker Compose

Todo List:

• Read and analyze the docker-compose.yml changes
• Review UDP port configuration for correctness
• Assess code quality and best practices
• Check for potential bugs or issues
• Evaluate performance implications
• Analyze security considerations
• Consider test coverage aspects
• Provide comprehensive review feedback

---

Change Analysis

File: docker/dev-full/docker-compose.yml
Lines: 234-235

Change: The rivet-client service port configuration was modified from:

- "7600-7699:7600-7699"

to:

- "7600-7699:7600-7699/tcp"
- "7600-7699:7600-7699/udp"

This change explicitly maps both TCP and UDP protocols for the 7600-7699 port range used for actor networking.

---

Review Assessment

✅ Code Quality & Best Practices

Excellent implementation:

• Explicit Protocol Declaration: Making TCP/UDP protocols explicit is a Docker Compose best practice
• Consistent with Documentation: The change aligns perfectly with existing comments (lines 227-233) explaining "Enable host networking for actors"
• Configuration Alignment: Comments reference correspondence with rivet-client/config.jsonc for actor.network.wan_port_range_min/max

✅ Correctness & Bug Analysis

Configuration is correct:

• Valid Syntax: Docker Compose port mapping syntax is correct for both TCP and UDP protocols
• Port Range Maintained: Preserves the intentional 100-port limit (7600-7699) to avoid iptables performance issues as documented
• Fixes Real Issue: Docker Compose defaults to TCP-only when no protocol is specified - this change ensures both protocols are available

✅ Performance Considerations

Minimal performance impact:

• Port Mapping Overhead: UDP port mapping adds negligible overhead
• Maintained Optimization: Preserves the 100-port limit design to prevent iptables rule explosion (as documented in comments)
• Network Efficiency: Proper UDP support enables better real-time networking for game actors

⚠️ Security Considerations

Acceptable risk for development environment:

• Port Exposure: UDP ports 7600-7699 are now exposed to the host, which is intentional for actor networking
• Limited Attack Surface: 100-port range reduces exposure compared to larger ranges
• Development Context: This is a dev-full compose file, appropriate for local development
• Expected Behavior: UDP exposure aligns with the documented architecture for actor host networking

⚠️ Consistency Observation

Potential improvement opportunity:

• rivet-guard Service: The rivet-guard service (line 158) uses "7500-7599:7500-7599" without explicit protocol specification
• Recommendation: Consider updating rivet-guard to use explicit /tcp and /udp declarations for consistency

ℹ️ Test Coverage

Infrastructure configuration considerations:

• Docker Compose: Configuration files don't typically require unit tests
• Integration Testing: Verification would involve testing UDP connectivity between actors and the host
• Configuration Validation: Ensure port ranges match values in rivet-client/config.jsonc

---

Overall Assessment: ✅ APPROVED

This is a focused, well-implemented fix that addresses UDP port mapping for actor networking. The change:

• Follows Docker Compose best practices
• Maintains existing security and performance considerations
• Is well-documented and aligns with system architecture
• Fixes a real issue where UDP traffic would have been blocked

Optional Enhancement: Consider applying similar explicit protocol specification to the rivet-guard service for consistency.

---

[claude]

Claude finished @MasterPtato's task —— View job

---

Code Review: Add UDP Ports to Docker Compose

Todo List:

• Read and analyze the docker-compose.yml changes
• Review UDP port configuration for correctness
• Assess code quality and best practices
• Check for potential bugs or issues
• Evaluate performance implications
• Analyze security considerations
• Consider test coverage aspects
• Provide comprehensive review feedback

---

Change Analysis

File: docker/dev-full/docker-compose.yml
Lines: 234-235

Change: The rivet-client service port configuration was modified from:

- "7600-7699:7600-7699"

to:

- "7600-7699:7600-7699/tcp"
- "7600-7699:7600-7699/udp"

Review Assessment

✅ Code Quality & Best Practices

Excellent implementation:

• Explicit Protocol Declaration: Making TCP/UDP protocols explicit is a Docker Compose best practice
• Consistent Documentation: The change aligns perfectly with existing comments (lines 227-233) explaining "Enable host networking for actors"
• Configuration Alignment: Comments reference correspondence with rivet-client/config.jsonc for actor.network.wan_port_range_min/max

✅ Correctness & Bug Analysis

Configuration is correct:

• Valid Syntax: Docker Compose port mapping syntax is correct for both TCP and UDP protocols
• Port Range Maintained: Preserves the intentional 100-port limit (7600-7699) to avoid iptables performance issues as documented
• Fixes Real Issue: Docker Compose defaults to TCP-only when no protocol is specified - this change ensures both protocols are available

✅ Performance Considerations

Minimal performance impact:

• Port Mapping Overhead: UDP port mapping adds negligible overhead
• Maintained Optimization: Preserves the 100-port limit design to prevent iptables rule explosion (as documented in comments)
• Network Efficiency: Proper UDP support enables better real-time networking for game actors

⚠️ Security Considerations

Acceptable risk for development environment:

• Port Exposure: UDP ports 7600-7699 are now exposed to the host, which is intentional for actor networking
• Limited Attack Surface: 100-port range reduces exposure compared to larger ranges
• Development Context: This is a dev-full compose file, appropriate for local development
• Expected Behavior: UDP exposure aligns with the documented architecture for actor host networking

⚠️ Consistency Observation

Potential improvement opportunity:

• rivet-guard Service: The rivet-guard service (line 158) uses "7500-7599:7500-7599" without explicit protocol specification
• Recommendation: Consider updating rivet-guard to use explicit /tcp and /udp declarations for consistency

ℹ️ Test Coverage

Infrastructure configuration considerations:

• Docker Compose: Configuration files don't typically require unit tests
• Integration Testing: Verification would involve testing UDP connectivity between actors and the host
• Configuration Validation: Ensure port ranges match values in rivet-client/config.jsonc

Overall Assessment: ✅ APPROVED

This is a focused, well-implemented fix that addresses UDP port mapping for actor networking. The change:

• Follows Docker Compose best practices
• Maintains existing security and performance considerations
• Is well-documented and aligns with system architecture
• Fixes a real issue where UDP traffic would have been blocked

Optional Enhancement: Consider applying similar explicit protocol specification to the rivet-guard service for consistency.

---

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[claude]

Claude finished @MasterPtato's task —— View job

---

Code Review: Add UDP Ports to Docker Compose

Todo List:

• Read and analyze the docker-compose.yml changes
• Review UDP port configuration for correctness
• Assess code quality and best practices
• Check for potential bugs or issues
• Evaluate performance implications
• Analyze security considerations
• Consider test coverage aspects
• Provide comprehensive review feedback

---

Change Analysis

File: docker/dev-full/docker-compose.yml
Lines: 234-235

Change: The rivet-client service port configuration was modified from:

- "7600-7699:7600-7699"

to:

- "7600-7699:7600-7699/tcp"
- "7600-7699:7600-7699/udp"

This change explicitly maps both TCP and UDP protocols for the 7600-7699 port range used for actor networking.

---

Review Assessment

✅ Code Quality & Best Practices

Excellent implementation:

• Explicit Protocol Declaration: Making TCP/UDP protocols explicit is a Docker Compose best practice
• Consistent Documentation: The change aligns perfectly with existing comments (lines 227-233) explaining "Enable host networking for actors"
• Configuration Alignment: Comments reference correspondence with rivet-client/config.jsonc for actor.network.wan_port_range_min/max

✅ Correctness & Bug Analysis

Configuration is correct:

• Valid Syntax: Docker Compose port mapping syntax is correct for both TCP and UDP protocols
• Port Range Maintained: Preserves the intentional 100-port limit (7600-7699) to avoid iptables performance issues as documented
• Fixes Real Issue: Docker Compose defaults to TCP-only when no protocol is specified - this change ensures both protocols are available

✅ Performance Considerations

Minimal performance impact:

• Port Mapping Overhead: UDP port mapping adds negligible overhead
• Maintained Optimization: Preserves the 100-port limit design to prevent iptables rule explosion (as documented in comments)
• Network Efficiency: Proper UDP support enables better real-time networking for game actors

⚠️ Security Considerations

Acceptable risk for development environment:

• Port Exposure: UDP ports 7600-7699 are now exposed to the host, which is intentional for actor networking
• Limited Attack Surface: 100-port range reduces exposure compared to larger ranges
• Development Context: This is a dev-full compose file, appropriate for local development
• Expected Behavior: UDP exposure aligns with the documented architecture for actor host networking

⚠️ Consistency Observation

Potential improvement opportunity:

• rivet-guard Service: The rivet-guard service (line 158) uses "7500-7599:7500-7599" without explicit protocol specification
• Recommendation: Consider updating rivet-guard to use explicit /tcp and /udp declarations for consistency

ℹ️ Test Coverage

Infrastructure configuration considerations:

• Docker Compose: Configuration files don't typically require unit tests
• Integration Testing: Verification would involve testing UDP connectivity between actors and the host
• Configuration Validation: Ensure port ranges match values in rivet-client/config.jsonc

---

Overall Assessment: ✅ APPROVED

This is a focused, well-implemented fix that addresses UDP port mapping for actor networking. The change:

• Follows Docker Compose best practices
• Maintains existing security and performance considerations
• Is well-documented and aligns with system architecture
• Fixes a real issue where UDP traffic would have been blocked

Optional Enhancement: Consider applying similar explicit protocol specification to the rivet-guard service for consistency.

---

[claude]

Claude finished @MasterPtato's task —— View job

---

Code Review: Add UDP Ports to Docker Compose

Todo List:

• Read and analyze the docker-compose.yml changes
• Review UDP port configuration for correctness
• Assess code quality and best practices
• Check for potential bugs or issues
• Evaluate performance implications
• Analyze security considerations
• Consider test coverage aspects
• Provide comprehensive review feedback

---

Change Analysis

File: docker/dev-full/docker-compose.yml
Lines: 235-236 (rivet-client service)

Change: The rivet-client service port configuration was modified from:

- "7600-7699:7600-7699"

to:

- "7600-7699:7600-7699/tcp"
- "7600-7699:7600-7699/udp"

This change explicitly maps both TCP and UDP protocols for the 7600-7699 port range used for actor networking.

Review Assessment

✅ Code Quality & Best Practices

Excellent implementation:

• Explicit Protocol Declaration: Making TCP/UDP protocols explicit is a Docker Compose best practice
• Consistent Documentation: The change aligns perfectly with existing comments (lines 228-234) explaining "Enable host networking for actors"
• Configuration Alignment: Comments reference correspondence with rivet-client/config.jsonc for actor.network.wan_port_range_min/max

✅ Correctness & Bug Analysis

Configuration is correct:

• Valid Syntax: Docker Compose port mapping syntax is correct for both TCP and UDP protocols
• Port Range Maintained: Preserves the intentional 100-port limit (7600-7699) to avoid iptables performance issues as documented
• Fixes Real Issue: Docker Compose defaults to TCP-only when no protocol is specified - this change ensures both protocols are available

✅ Performance Considerations

Minimal performance impact:

• Port Mapping Overhead: UDP port mapping adds negligible overhead
• Maintained Optimization: Preserves the 100-port limit design to prevent iptables rule explosion (as documented in comments)
• Network Efficiency: Proper UDP support enables better real-time networking for game actors

⚠️ Security Considerations

Acceptable risk for development environment:

• Port Exposure: UDP ports 7600-7699 are now exposed to the host, which is intentional for actor networking
• Limited Attack Surface: 100-port range reduces exposure compared to larger ranges
• Development Context: This is a dev-full compose file, appropriate for local development
• Expected Behavior: UDP exposure aligns with the documented architecture for actor host networking

⚠️ Consistency Observation

Potential improvement opportunity:

• rivet-guard Service: The rivet-guard service (line 158) uses "7500-7599:7500-7599" without explicit protocol specification
• Recommendation: Consider updating rivet-guard to use explicit /tcp and /udp declarations for consistency

ℹ️ Test Coverage

Infrastructure configuration considerations:

• Docker Compose: Configuration files don't typically require unit tests
• Integration Testing: Verification would involve testing UDP connectivity between actors and the host
• Configuration Validation: Ensure port ranges match values in rivet-client/config.jsonc

Overall Assessment: ✅ APPROVED

This is a focused, well-implemented fix that addresses UDP port mapping for actor networking. The change:

• Follows Docker Compose best practices
• Maintains existing security and performance considerations
• Is well-documented and aligns with system architecture
• Fixes a real issue where UDP traffic would have been blocked

Optional Enhancement: Consider applying similar explicit protocol specification to the rivet-guard service for consistency.

---

[claude]

Claude finished @MasterPtato's task —— View job

---

Code Review: Add UDP Ports to Docker Compose

Todo List:

• Read and analyze the docker-compose.yml changes
• Review UDP port configuration for correctness
• Assess code quality and best practices
• Check for potential bugs or issues
• Evaluate performance implications
• Analyze security considerations
• Consider test coverage aspects
• Provide comprehensive review feedback

---

Change Analysis

File: docker/dev-full/docker-compose.yml
Lines: 235-236 (rivet-client service)

Change: The rivet-client service port configuration was modified from:

- "7600-7699:7600-7699"

to:

- "7600-7699:7600-7699/tcp"
- "7600-7699:7600-7699/udp"

Review Assessment

✅ Code Quality & Best Practices

Excellent implementation:

• Explicit Protocol Declaration: Making TCP/UDP protocols explicit is a Docker Compose best practice
• Consistent Documentation: The change aligns perfectly with existing comments (lines 228-234) explaining "Enable host networking for actors"
• Configuration Alignment: Verified that port range matches rivet-client/config.jsonc:35-36 where wan_port_range_min: 7600 and wan_port_range_max: 7699

✅ Correctness & Bug Analysis

Configuration is correct:

• Valid Syntax: Docker Compose port mapping syntax is correct for both TCP and UDP protocols
• Port Range Maintained: Preserves the intentional 100-port limit (7600-7699) to avoid iptables performance issues as documented
• Fixes Real Issue: Docker Compose defaults to TCP-only when no protocol is specified - this change ensures both protocols are available

✅ Performance Considerations

Minimal performance impact:

• Port Mapping Overhead: UDP port mapping adds negligible overhead
• Maintained Optimization: Preserves the 100-port limit design to prevent iptables rule explosion (as documented in comments)
• Network Efficiency: Proper UDP support enables better real-time networking for game actors

⚠️ Security Considerations

Acceptable risk for development environment:

• Port Exposure: UDP ports 7600-7699 are now exposed to the host, which is intentional for actor networking
• Limited Attack Surface: 100-port range reduces exposure compared to larger ranges
• Development Context: This is a dev-full compose file, appropriate for local development
• Expected Behavior: UDP exposure aligns with the documented architecture for actor host networking

⚠️ Consistency Observation

Potential improvement opportunity:

• rivet-guard Service: The rivet-guard service (line 158) uses "7500-7599:7500-7599" without explicit protocol specification
• Recommendation: Consider updating rivet-guard to use explicit /tcp and /udp declarations for consistency

ℹ️ Test Coverage

Infrastructure configuration considerations:

• Docker Compose: Configuration files don't typically require unit tests
• Integration Testing: Verification would involve testing UDP connectivity between actors and the host
• Configuration Validation: Confirmed port ranges match values in rivet-client/config.jsonc

Overall Assessment: ✅ APPROVED

This is a focused, well-implemented fix that addresses UDP port mapping for actor networking. The change:

• Follows Docker Compose best practices
• Maintains existing security and performance considerations
• Is well-documented and aligns with system architecture
• Fixes a real issue where UDP traffic would have been blocked

Optional Enhancement: Consider applying similar explicit protocol specification to the rivet-guard service for consistency.

---

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
rivet-site	Error			Aug 21, 2025 8:21pm

[claude]

Claude finished @MasterPtato's task —— View job

---

Code Review: Add UDP Ports to Docker Compose

Todo List:

• Read and analyze the docker-compose.yml changes
• Review UDP port configuration for correctness
• Assess code quality and best practices
• Check for potential bugs or issues
• Evaluate performance implications
• Analyze security considerations
• Consider test coverage aspects
• Provide comprehensive review feedback

---

Change Analysis

File: docker/dev-full/docker-compose.yml
Lines: 235-236 (rivet-client service)

Change: The rivet-client service port configuration was modified from:

- "7600-7699:7600-7699"

to:

- "7600-7699:7600-7699/tcp"
- "7600-7699:7600-7699/udp"

Review Assessment

✅ Code Quality & Best Practices

Excellent implementation:

• Explicit Protocol Declaration: Making TCP/UDP protocols explicit is a Docker Compose best practice
• Consistent Documentation: The change aligns perfectly with existing comments (lines 227-234) explaining "Enable host networking for actors"
• Configuration Alignment: Verified that port range matches rivet-client/config.jsonc:35-36 where wan_port_range_min: 7600 and wan_port_range_max: 7699

✅ Correctness & Bug Analysis

Configuration is correct:

• Valid Syntax: Docker Compose port mapping syntax is correct for both TCP and UDP protocols
• Port Range Maintained: Preserves the intentional 100-port limit (7600-7699) to avoid iptables performance issues as documented
• Fixes Real Issue: Docker Compose defaults to TCP-only when no protocol is specified - this change ensures both protocols are available

✅ Performance Considerations

Minimal performance impact:

• Port Mapping Overhead: UDP port mapping adds negligible overhead
• Maintained Optimization: Preserves the 100-port limit design to prevent iptables rule explosion (as documented in comments)
• Network Efficiency: Proper UDP support enables better real-time networking for game actors

⚠️ Security Considerations

Acceptable risk for development environment:

• Port Exposure: UDP ports 7600-7699 are now exposed to the host, which is intentional for actor networking
• Limited Attack Surface: 100-port range reduces exposure compared to larger ranges
• Development Context: This is a dev-full compose file, appropriate for local development
• Expected Behavior: UDP exposure aligns with the documented architecture for actor host networking

⚠️ Consistency Observation

Potential improvement opportunity:

• rivet-guard Service: The rivet-guard service (line 158) uses "7500-7599:7500-7599" without explicit protocol specification
• Recommendation: Consider updating rivet-guard to use explicit /tcp and /udp declarations for consistency

ℹ️ Test Coverage

Infrastructure configuration considerations:

• Docker Compose: Configuration files don't typically require unit tests
• Integration Testing: Verification would involve testing UDP connectivity between actors and the host
• Configuration Validation: Confirmed port ranges match values in rivet-client/config.jsonc

Overall Assessment: ✅ APPROVED

This is a focused, well-implemented fix that addresses UDP port mapping for actor networking. The change:

• Follows Docker Compose best practices
• Maintains existing security and performance considerations
• Is well-documented and aligns with system architecture
• Fixes a real issue where UDP traffic would have been blocked

Optional Enhancement: Consider applying similar explicit protocol specification to the rivet-guard service for consistency.

---

[claude]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.

[claude]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.