TimefoldAI / TimefoldAI/timefold-solver
TRACE logging should log which classes/fields are planning cloned for debugging purposes
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 228
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 46
Description
Debugging if a certain class in planning cloned is hard to do.
It would be much easier if at solving start, after the TRACE logging logs the planning entities and planning variables, it also logs which classes are being planning cloned.
Not sure if this is possible, as the planning cloning is dynamic. For example: if a Animal field has a Cat instance, then even if Animal nor Dog isn't planning cloned, Cat might be.
Contributor 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.
Research direction
Start at the TRACE logging emitted when solving begins, after planning entities and planning variables are logged, and inspect how dynamic planning cloning determines the classes and fields it clones. Done means TRACE output identifies the cloned classes and fields, including runtime subclasses such as Cat when referenced through Animal, with tests covering the logging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100