[cueweb] Job Management: Job min/max cores dialog

[ramonfigueiredo]

• Goal: Action to set minCores and maxCores per job.
• CueGUI ref: cuegui/cuegui/RequestCoresDialog.py
• CueWeb work: new dialog under cueweb/components/ui/; action in cueweb/app/utils/action_utils.ts
• Acceptance: Validates min <= max; both updated atomically; row refreshes.
• Estimate: 4h · good first issue

Describe the enhancement
Add a row action to set a job's minCores and maxCores via two number inputs. Both values updated as one user action.

Reference

• cuegui/cuegui/RequestCoresDialog.py.

Version Number

• https://github.com/AcademySoftwareFoundation/OpenCue/releases/tag/v1.19.1

[ramonfigueiredo]

The Academy Software Foundation (ASWF) Dev Days (https://www.aswf.io/dev-days/) is a fantastic way to contribute to the amazing and important #ASWF projects (https://www.aswf.io/projects/) that positively impact our industry. Whether you’re in #vfx, #animation, #softwareengineering, or #softwaredeveloper, this is a great opportunity to get involved.

📅 Next Dev Days: May 14th and September 17th, 2026 (fully virtual, open worldwide)

For this event, we are highlighting OpenCue project - https://docs.opencue.io/, a production-proven render management system originally developed at Sony Pictures Imageworks and part of the ASWF. We’ve prepared more than 30 easy issues and enhancements that are ideal for first-time contributors. These tasks are straightforward, designed to take less than a day to complete, and some can be finished in just a few hours. Everyone is invited to participate and contribute!

🔗 OpenCue codebase: https://github.com/AcademySoftwareFoundation/OpenCue
📘 OpenCue documentation: https://docs.opencue.io
📖 Developer guide: https://docs.opencue.io/docs/developer-guide/index/
🧪 Using the OpenCue Sandbox for Testing: https://docs.opencue.io/docs/developer-guide/sandbox-testing/
💬 OpenCue Slack channel: https://academysoftwarefdn.slack.com/archives/CMFPXV39Q
✅ Available tasks/issues and enhancements (good first issue + help wanted): https://github.com/AcademySoftwareFoundation/OpenCue/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22good%20first%20issue%22%20label%3A%22help%20wanted%22

---

✅ How to Contribute Effectively

• Focus on one issue at a time. Please don’t try to solve or implement all the main issues at once.
• When your work is complete, submit a full pull request (PR). We’ll review it as soon as possible.
• If your PR is not yet ready, submit it as a Draft Pull Request. Once you’re confident it’s ready, change the status to Open so maintainers know it can be reviewed.

How to create a Draft PR on GitHub:

1. When opening a pull request, click the dropdown on the green “Create pull request” button and select “Create draft pull request”.
2. Your PR will be clearly marked as Draft until you’re ready.
3. When it’s ready for review, click “Ready for review” at the top of the PR page - this changes the status to Open.

---

Thank you for your contribution!
Before we can move forward with the code review, please sign the CLA Authorization - EasyCLA

➡️ You only need to sign the CLA once, when you are submitting your first full request to the OpenCue project. After that, you’re all set for future contributions.

Everyone’s collaboration is very much appreciated. Thank you for helping grow OpenCue and for contributing to the software our industry relies on!

[ramonfigueiredo]

Parent issue / enhancement #2016 - Finalize CueWeb with Full CueGUI Functionality and Professional UI

ASWF Dev Days: May 14th and September 17th, 2026 (24-hour open source global development event).
See: https://www.aswf.io/dev-days/

Contributing to OpenCue: https://docs.opencue.io/docs/developer-guide/contributing/

Using the OpenCue Sandbox for Testing: https://docs.opencue.io/docs/developer-guide/sandbox-testing/

• The OpenCue sandbox provides a quick way to run the complete OpenCue stack locally for testing.
• This environment is ideal for developers who want to test changes, experiment with features, or learn how OpenCue works without setting up a full production environment.

Quick start - https://docs.opencue.io/docs/ :

1. Fork https://github.com/AcademySoftwareFoundation/OpenCue + git clone https://github.com/YOURGITHUBUSERNAME/OpenCue
2. docker compose --profile all up -d
   • Profiles (see: docker-compose.yml): default (cuebot, db, flyway, rqd), cueweb (rest-gateway, cueweb), monitoring (db-exporter, prometheus, grafana, loki), monitoring-full (zookeeper, kafka, kafka-ui, elasticsearch, kibana, monitoring-indexer)
3. ./sandbox/install-client-sources.sh
   • Install the rest of the Python client packages (see: ./sandbox/install-client-sources.sh): pycue, pyoutline, cueadmin, cueman, cuesubmit, cuegui, cuecmd, cuenimby
4. Submit your pull request (PR) as Draft if it is not ready for review. Change it to Open when it is ready for review
5. Sign the CLA on your PR

[ramonfigueiredo]

Hi, thank you for contributing to the OpenCue project.

Note: If you are seeing Unauthorized request: Token validation error: token signature is invalid when loading CueWeb locally (for example, when searching for jobs and the /api/job/getjobs request fails), first verify your local CueWeb development environment configuration. This usually means the local Next.js development server is signing JWT requests with a different secret than the Dockerized OpenCue rest-gateway is using to validate them.

The 200 OK response shown in the browser can be misleading, since that is only the local CueWeb API route (localhost:3000) returning a JSON error response. The actual failure happens when CueWeb forwards the request to the OpenCue REST gateway, which rejects the JWT because the token signature does not match.

Check that your cueweb/.env file exists and includes all required variables, especially:

NEXT_PUBLIC_OPENCUE_ENDPOINT=http://localhost:8448
NEXT_PUBLIC_URL=http://localhost:3000
NEXT_JWT_SECRET=opencue-dev-jwt-secret-change-in-production

Make sure NEXT_JWT_SECRET exactly matches the JWT_SECRET used by the rest-gateway service in docker-compose.yml (or any custom value you exported before running docker compose up). Also verify that NEXT_PUBLIC_OPENCUE_ENDPOINT uses localhost:8448, not rest-gateway:8448, since rest-gateway only resolves inside the Docker network.

After making any changes to .env, restart npm run dev, since Next.js only reads environment variables at startup.

To verify the backend secret directly, run:

docker compose exec rest-gateway sh -c 'echo $JWT_SECRET'

Whatever this prints must exactly match your NEXT_JWT_SECRET.

It may also help to compare your local .env against cueweb/.env.example and the project README, since some required variables may be documented but missing from the example file.

If the issue persists after verifying environment consistency, please share the exact error message, relevant logs, and your local setup details so the problem can be investigated further.

Thank you!

[ramonfigueiredo]

Hi,

Please merge the latest master into your branch. An important PR has recently been merged:

[cueweb] Bump Next.js to 15.5.18 to patch CVE-2026-44578 (WebSocket SSRF) #2332

Thanks!

[ramonfigueiredo]

Contributing to OpenCue

Many new CueWeb enhancement issues/features have been created for ASWF Dev Days, a 24-hour global open source development event, to work on the OpenCue project. This guide gets you to a working CueWeb dev environment fast so you can ship a PR within the day.

Event & Context

ASWF Dev Days 2026: May 14th and September 17th (24-hour global event). See: https://www.aswf.io/dev-days/
Parent issue / enhancement: #2016 - Finalize CueWeb with Full CueGUI Functionality and Professional UI
Pick an issue: Browse the open CueWeb issues/features tagged for Dev Days and comment on the one you'd like to take.

References

• Contributing to OpenCue: https://docs.opencue.io/docs/developer-guide/contributing/
• OpenCue Sandbox: https://docs.opencue.io/docs/developer-guide/sandbox-testing/
• CueWeb README: cueweb/README.md
• Sandbox README: sandbox/README.md
• General docs: https://docs.opencue.io/docs/

Architecture (what talks to what)

  ┌────────┐    gRPC :8443     ┌────────────────┐    HTTP :8448    ┌────────┐
  │  RQD   │ ─────────────────▶│     Cuebot     │◀────────────────▶│  REST  │
  └────────┘                   └────────────────┘                  │Gateway │
                                       ▲                           └────┬───┘
                                       │ JDBC                           │
                                ┌──────┴──────┐                         ▼
                                │ PostgreSQL  │                  ┌───────────────┐
                                └─────────────┘                  │   CueWeb      │
                                                                 │ (Next.js:3000)│
   CueGUI / CueSubmit ─── gRPC ─▶ Cuebot                         └───────────────┘

When developing CueWeb, run everything else in Docker and run CueWeb locally with npm run dev so your changes hot reload.

Quick Start

1. Fork & clone

Fork https://github.com/AcademySoftwareFoundation/OpenCue, then:

git clone https://github.com/YOUR_GITHUB_USERNAME/OpenCue
cd OpenCue
git checkout -b dev-days/<issue-number>-<short-description>

2. Deploy & Install Opencue

docker compose --profile all up -d

• Profiles (see: docker-compose.yml): default (cuebot, db, flyway, rqd), cueweb (rest-gateway, cueweb), monitoring (db-exporter, prometheus, grafana, loki), monitoring-full (zookeeper, kafka, kafka-ui, elasticsearch, kibana, monitoring-indexer)

Note:

• If you only need the dockerized backend and skip the dockerized cueweb so port 3000 is free for your local dev server.

mkdir -p /tmp/rqd/logs /tmp/rqd/shots
docker compose up -d db flyway cuebot rqd rest-gateway
# or just docker compose up -d # (default)
docker compose ps          # verify all services are healthy

Endpoints now available (default):

Service	URL	Notes
Cuebot gRPC	localhost:8443	Used by CueGUI, CueSubmit, RQD
REST Gateway	http://localhost:8448	Used by CueWeb
PostgreSQL	localhost:5432	cuebot / cuebot_password
RQD	localhost:8444	Render daemon

Useful commands: docker compose logs -f cuebot, docker compose restart rest-gateway, docker compose --profile all down.

3. Install the Python clients

You'll need CueGUI/CueSubmit to submit test jobs so CueWeb has real data to render.

python3 -m venv venv
source venv/bin/activate
./sandbox/install-client-sources.sh

This installs: pycue, pyoutline, cueadmin, cueman, cuesubmit, cuegui, cuecmd, cuenimby.

Sanity check the connection:

cueadmin -lh        # should list the RQD host

OpenCue Clients & CueWeb & Cuebot (OpenCue's server side)

OpenCue client packages installed by ./sandbox/install-client-sources.sh

• pycue: Python API; the gRPC client library every other tool builds on (import opencue).
• pyoutline: Python library for building OpenCue job definitions (layers, tasks, dependencies) without writing XML.
• cueadmin: CLI admin tool for jobs/layers/frames/hosts/shows/allocations (priorities, kills, resource mgmt).
• cueman: CLI job-management tool focused on efficient filtering and batch operations on jobs/frames/procs.
• cuesubmit: Qt GUI for submitting render jobs; can also run as a plugin in Maya/Nuke.
• cuegui: Main Qt GUI: Cuetopia (artist monitoring) + Cuecommander (admin/farm control).
• cuecmd: CLI that takes a file of shell commands and submits them as chunked frames to the farm.
• cuenimby: Cross-platform system-tray app for controlling NIMBY (lock/unlock workstation rendering).

How to run / quick usage

Activate your venv first (source venv/bin/activate), then:

1. PyCue: Use from a Python shell or scripts

python -c "import opencue; print([s.name() for s in opencue.api.getShows()])"

2. PyOutline: Used programmatically (cuesubmit uses it internally)

python -c "import outline; ol = outline.Outline('demo'); print(ol)"

3. CueAdmin: Admin CLI (jobs, hosts, shows, allocations)

cueadmin -lh                   # list hosts
cueadmin -lj                   # list jobs
cueadmin -lba <alloc>          # list subscriptions
cueadmin -kill <job>           # kill a job
cueadmin -h                    # full help

4. Cueman: The job/frame batch operations

cueman -lp <job>               # list procs on a job
cueman -lf <job> -state DEAD   # list dead frames
cueman -retry <job> -state DEAD
cueman -h

5. CueSubmit: GUI submitter

cuesubmit &

6. CueGUI: Main GUI (Cuetopia + Cuecommander)

cuegui &

7. CueCMD: Submit a list of shell commands as frames

echo -e "echo hello\nsleep 5\nls /tmp" > cmds.txt
cuecmd cmds.txt --chunk 1 --show testing
cuecmd -h

8. CueNIMBY: System-tray NIMBY control (foreground / background)

cuenimby &

All of these OpenCue clients talk to Cuebot (OpenCue server side) on localhost:8443 (the gRPC endpoint you exposed via docker compose up -d.

CueWeb is the web version of CueGUI (under development). CueWeb communicate with CueBot through the REST Gateway on localhost:8448.

4. Submit a couple of test jobs

Run these from the activated venv:

cuesubmit &         # GUI to submit a test job

cuegui &            # Cuetopia + CueCommander

CueGUI is the desktop graphical user interface divided into two main workspaces:

• Cuetopia (artist-focused job monitoring)
• CueCommander (administrator-focused system management)

CueGUI provides comprehensive tools for job monitoring, frame inspection, host management, and system administration.

Submit any small job (e.g. a sleep/echo shell job) so CueWeb has jobs, layers, and frames to display.

Load Test Jobs

It is possible to use the test script sandbox/load_test_jobs.py to submit jobs to OpenCue for testing.

Usage:

# Uses defaults: 1000 jobs, batch size 50
python load_test_jobs.py

# Submit 10 jobs
python load_test_jobs.py -n 10

# Submit 100 jobs
python load_test_jobs.py -n 100

# Submit 500 jobs in batches of 25
python load_test_jobs.py -n 500 -b 25

python load_test_jobs.py --num-jobs 100 --batch-size 10

5. Run CueWeb locally in dev mode (hot reload)

In a new terminal, from the repo root:

cd cueweb

# One-time: create a local .env pointing at the dockerized REST gateway
cat > .env <<'EOF'
NEXT_PUBLIC_OPENCUE_ENDPOINT=http://localhost:8448
NEXT_PUBLIC_URL=http://localhost:3000
NEXT_JWT_SECRET=opencue-dev-jwt-secret-change-in-production
NEXTAUTH_URL=http://localhost:3000
NEXTAUTH_SECRET=canbeanything
# Auth disabled for local dev - leave empty
NEXT_PUBLIC_AUTH_PROVIDER=
# Sentry off for local dev - leave SENTRY_DSN unset
SENTRY_ENVIRONMENT=development
EOF

npm install
npm run dev

Important: NEXT_JWT_SECRET must match the gateway's JWT_SECRET (default opencue-dev-jwt-secret-change-in-production in docker-compose.yml). If you set a custom JWT_SECRET when starting compose, set the same value here.

Open http://localhost:3000 = your test jobs should appear. Edits to files under cueweb/app/, cueweb/components/, cueweb/lib/ reload automatically.

6. Test your changes

cd cueweb
npm run lint
npm run test         # Jest unit tests
npm run format:check

If you touch UI: exercise the golden path (load jobs, search, open layers/frames, view logs, dark mode) and the specific feature from your issue.

Common Dev Commands

Task	Command
Restart Cuebot after a backend change	docker compose restart cuebot
Tail CueWeb-relevant logs	docker compose logs -f cuebot rest-gateway
Rebuild Cuebot from source	docker compose up -d --build cuebot
Reset the DB (wipe all jobs)	docker compose down -v && docker compose up -d db flyway cuebot rqd rest-gateway
Run a single Jest file	cd cueweb && npx jest path/to/file.test.tsx

Submitting your PR

1. Commit small, focused changes referencing the issue: git commit -m "[cueweb] <short summary> (#<issue>)".
2. Push to your fork and open the PR as Draft while in progress, then move to Open for review.
3. Link the PR to the Dev Days issue and include:
   • What you changed and why
   • Screenshots/GIF for any UI change
   • Test plan (the steps you ran in step 6)
4. Sign the CLA comment on your PR - required before merge.

Dev Days tips

• Scope tight - 24 hours rewards small, focused PRs. Feel free to continue on the PR improvements after the Dev Days. Thanks :)
• Push a Draft early so reviewers can see direction.
• If the REST gateway returns 401, your NEXT_JWT_SECRET doesn't match the gateway's JWT_SECRET . Fix and restart npm run dev.
• If jobs don't show up, confirm cueadmin -lh lists the RQD host and submit a job via cuesubmit.
• Stuck? Comment on the issue or reach out in the OpenCue Slack channel: https://academysoftwarefdn.slack.com/archives/CMFPXV39Q

[ttpss930141011]

Hi @ramonfigueiredo! Thanks again for reviewing and merging #2391 🎉

I’d like to look into the Job Management actions. I was looking at these three issues:

• [cueweb] Job Management: Job min/max cores dialog #2281: Job min/max cores dialog
• [cueweb] Job Management: Multi-job batch operations confirmation #2283: Multi-job batch operations confirmation
• [cueweb] Job Management: "Unbook" job action #2288: “Unbook” job action

Since they seem to touch the same areas, I was thinking that, if you’re okay with it, I could handle them together in one PR, similar to how #2397 grouped the host actions. That said, since I’m still pretty new to contributing to this project, I’m also happy to split them into separate PRs and work through them one by one if bundling all three feels too large in terms of scope.

And like the previous issue, I just wanted to ask have you already started on them? If not, would you be open to handing them over to me?

Also, one thing I noticed while looking around:

• [cueweb] Job Management: Job priority adjustment dialog #2280 looks like it may already be done in [cueweb/docs] Job menu actions: Part 1 - Unmonitor, View Job Details, Copy Job Name, Comments, Pause, Unpause, Auto-Eat On and Off, Retry Dead Frames, Eat Dead Frames, Kill Job. Part 2 - Email artist, Request Cores, Subscribe to Job, Set Priority #2374, since the priority slider dialog and /api/job/action/setpriority route are already in master. Maybe that issue can be closed, or is there anything else we should do for it?