Radovan Synek

Results 13 issues of Radovan Synek

- turns the existing test into an integration test that uses a REST API - replaces hardcoded waiting for optaplanner with polling

- switches to ActiveMQ and its [ArtemisCloud operator](https://artemiscloud.io) - integrates with [KEDA](https://keda.sh/) for scaling based on queue length - TODO: update the quickstart ### JIRA https://issues.redhat.com/browse/PLANNER-2698 ### Referenced pull requests...

Having a single vehicle a decreasing its capacity to 0 does not remove a route. Expected: similar to having no vehicle at all, no route should be shown

This request is related to an over-constrained planning. Right now, the application does not properly behave in a situation when vehicles have insufficient capacity => the vehicles should return to...

enhancement
users feedback

DO NOT MERGE. The issue serves as a reproducer of https://github.com/quarkiverse/quarkus-operator-sdk/issues/388.

The reconciler tests in samples show that the injected operator could be started at the beginning of the test method [1]. When there are multiple test methods of a reconciler,...

See https://github.com/kiegroup/optaplanner/pull/2194. Merge after the branch `8.29.x` is created. ### JIRA ### Referenced pull requests ### Checklist - [ ] Documentation updated if applicable. - [ ] Release notes updated...

Updates a readme to reflect changes in https://github.com/kiegroup/optaplanner/pull/2225/. ### JIRA https://issues.redhat.com/browse/PLANNER-2765 ### Referenced pull requests https://github.com/kiegroup/optaplanner/pull/2225 https://github.com/kiegroup/optaplanner-quickstarts/pull/420 How to retest this PR or trigger a specific build: - for pull...

### Describe the bug This is a regression likely introduced by https://github.com/quarkusio/quarkus/commit/827f778c9ab71478b19ce230ac5a5265bfdba592 (confirmed locally by building and using the snapshot). In a Gradle project that uses the `quarkus-hibernate-orm-rest-data-panache`, a generated...

kind/bug
area/panache
area/gradle

The score itself does not tell users why the solution is good or bad. Each quickstart should provide explanation by using constraint matches in the UI.

enhancement