docs: [docs-drift] create_profile_set_custom_seed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- java
- Domain
- documentation
Research direction
Start by reading service/definition/src/main/java/ai/timefold/solver/service/definition/api/domain/RunConfiguration.java to confirm the public options field. Then update docs/src/modules/ROOT/pages/running-timefold-solver/service/rest-api.adoc and consumer-guide.adoc, including the request examples, field count, and execution-profile description. Done means both service pages describe options consistently.
Written by the indexing model from the issue text.
Description
[!WARNING]
Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Merged input: TimefoldAI/timefold-solver#2665 by diogodanielsoaresferreira (feat: Create profile set custom seed). No matching merged pull request was found in timefold-solver-enterprise or timefold-quickstarts.
Finding 1 — Added public run option
- Code change:
TimefoldAI/timefold-solver,service/definition/src/main/java/ai/timefold/solver/service/definition/api/domain/RunConfiguration.java(merged change), added the publicRunConfiguration.optionsfield of typeMap<String, String>. - Docs location:
docs/src/modules/ROOT/pages/running-timefold-solver/service/rest-api.adoc:147-153anddocs/src/modules/ROOT/pages/running-timefold-solver/service/consumer-guide.adoc:127-140previously described the run configuration withoutoptionsand omitted it from request examples. - Confidence: high.
- What I changed: Added
optionsto both JSON request examples, updated the REST API field count from four to five, and documented that the map carries optional key-value parameters used by execution profiles in both service pages.
The group is already merged, so this pull request fixes the documentation on main. It should be updated if more pull requests on create_profile_set_custom_seed merge.
[!NOTE]
This was originally intended as a pull request, but the git push operation failed.Original error: Remote branch "docs-drift/create_profile_set_custom_seed" already exists and preserve-branch-name is enabled. Set recreate-ref: true to force-delete and recreate the remote ref, or disable preserve-branch-name to allow renaming the branch.
Workflow Run: View run details and download bundle artifact
The bundle file is available in the
agentartifact in the workflow run linked above.
Create the pull request manually
# Download the artifact from the workflow run
gh run download '36855821369' -n agent -D '/tmp/agent-36855821369'
# Resolve the bundle source ref, fetch it into a temporary ref, then create the local branch
bundle_path='/tmp/agent-36855821369/aw-timefoldai-timefold-solver-docs-drift-create_profile_set_custom_seed.bundle'
temp_ref='refs/bundles/create-pr-docs-drift-create-profile-set-custom-seed-c16f243a'
target_ref='refs/heads/docs-drift/create_profile_set_custom_seed'
bundle_source_ref=$(git bundle list-heads "$bundle_path" | awk '$2 ~ /^refs\/heads\// { print $2 }')
if [ -z "$bundle_source_ref" ]; then
bundle_source_ref=$(git bundle list-heads "$bundle_path" | awk '$2 == "HEAD" { print $2 }')
fi
if [ "$(printf '%s\n' "$bundle_source_ref" | sed '/^$/d' | wc -l | tr -d ' ')" != "1" ]; then
echo "Expected exactly one bundle source ref, found: $bundle_source_ref" >&2
exit 1
fi
git fetch "$bundle_path" "${bundle_source_ref}:${temp_ref}"
git update-ref "$target_ref" "$temp_ref"
git checkout 'docs-drift/create_profile_set_custom_seed'
# Ensure the working tree matches the updated branch
git reset --hard
# Remove the temporary bundle ref
git update-ref -d "$temp_ref"
# Push the branch to the target remote
git push 'origin' 'docs-drift/create_profile_set_custom_seed'
# Create the pull request
gh pr create --title 'docs: [docs-drift] create_profile_set_custom_seed' --base 'main' --head 'docs-drift/create_profile_set_custom_seed' --repo 'timefoldai/timefold-solver'
Generated by Solver Docs Drift Detector · copilot · gpt56 · 15.9 AIC · ⊞ 27.2K · ◷
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 237
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 58
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TimefoldAI/timefold-solver
-
component/docs
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
TimefoldAI/timefold-solver#2671 ·
Maintainers usually reply within 1 day
-
SolutionManager.update() does not update entities in no value rangePossibly taken @Christopher-Chianelli claimed this 2 days ago. Open
TimefoldAI/timefold-solver#2737 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
SolverWorker can overwrite SOLVING_COMPLETED with SOLVING_ACTIVE when a best-solution save races the completionPossibly taken @rsynek claimed this 3 days ago. Opencomponent/service
TimefoldAI/timefold-solver#2730 · 1 assignee ·
Maintainers usually reply within 1 day
-
First initialized solution event shares the working solution with the consumer thread (ConcurrentModificationException)Possibly taken @zepfred claimed this 3 days ago. Open
TimefoldAI/timefold-solver#2728 · 1 assignee ·
Maintainers usually reply within 1 day
-
process/needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
TimefoldAI/timefold-solver#2708 ·
Maintainers usually reply within 1 day
All issues in TimefoldAI/timefold-solver
Similar issues
-
`Processing lsp` never exits and leaves orphaned processesPossibly taken @overcast302 claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
processing/processing4#1578 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
Maintainers usually reply within 1 day
-
[BUG] S3 CORS responses omit Access-Control-Allow-Credentials for matched originsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
floci-io/floci#5369 · 1 comment ·
Maintainers usually reply within 1 day
-
securityHeaders replaces a route's own Content-Security-Policy (0.9.9; weakens embedders' pages)Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sqlcipher/sqlcipher-android#97 · 1 comment ·