diff --git a/.github/workflows/ci_cd.yml b/.github/workflows/ci_cd.yml index 4bb1c31..83c5751 100644 --- a/.github/workflows/ci_cd.yml +++ b/.github/workflows/ci_cd.yml @@ -50,9 +50,9 @@ jobs: - name: Checkout main repo uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 with: - repository: openremote/openremote - path: openremote - ref: master + repository: openremote/core + path: core + ref: main sparse-checkout: profile sparse-checkout-cone-mode: false @@ -87,7 +87,7 @@ jobs: mkdir -pm 777 tmp # Start the dev-testing stack - docker compose -f openremote/profile/dev-testing.yml up -d --no-build + docker compose -f core/profile/dev-testing.yml up -d --no-build ./gradlew test @@ -178,9 +178,9 @@ jobs: if: ${{ steps.is_publish_event.outputs.value == 'true' }} run: | if [ "$IS_RELEASE" == true ]; then - gh workflow run deploy.yml -R openremote/openremote -f ENVIRONMENT="demo" -f MANAGER_TAG="latest" -f CLEAN_INSTALL="true" + gh workflow run deploy.yml -R openremote/core -f ENVIRONMENT="demo" -f MANAGER_TAG="latest" -f CLEAN_INSTALL="true" else - gh workflow run deploy.yml -R openremote/openremote -f ENVIRONMENT="staging" -f MANAGER_TAG="develop" -f CLEAN_INSTALL="true" + gh workflow run deploy.yml -R openremote/core -f ENVIRONMENT="staging" -f MANAGER_TAG="develop" -f CLEAN_INSTALL="true" fi env: GH_TOKEN: ${{ steps.deployment-token.outputs.token }} diff --git a/DESIGN.md b/DESIGN.md index bc45b44..78b7dcd 100644 --- a/DESIGN.md +++ b/DESIGN.md @@ -1,7 +1,7 @@ ## Introduction The OpenRemote platform is designed for versatility, supporting diverse domains such as energy management, smart cities, and fleet management. -As the platform scales, it is no longer practical or efficient for the Core repository ([openremote/openremote](https://github.com/openremote/openremote/)) to natively support every specific protocol, UI widget or business logic requirement. +As the platform scales, it is no longer practical or efficient for the Core repository ([openremote/core](https://github.com/openremote/core/)) to natively support every specific protocol, UI widget or business logic requirement. ## Purpose diff --git a/ems/src/main/java/org/openremote/extension/ems/manager/distroenergy/DistroEnergyHandler.java b/ems/src/main/java/org/openremote/extension/ems/manager/distroenergy/DistroEnergyHandler.java index c74aefb..9f144d8 100644 --- a/ems/src/main/java/org/openremote/extension/ems/manager/distroenergy/DistroEnergyHandler.java +++ b/ems/src/main/java/org/openremote/extension/ems/manager/distroenergy/DistroEnergyHandler.java @@ -363,10 +363,10 @@ static double toVolume(double powerNetKw) { * *
Under a JVM zone that observes DST the storage frame is not monotonic, so on the fall-back
* day the two instants of the repeated hour collapse onto a single stored row and both read it.
- * That is a consequence of the naive primary key upstream (openremote/openremote#3292). The
- * collapse can only duplicate a read, never erase one, so it cannot turn a day with a forecast
- * into a skip, and while it lasts the repeated hour is never a gap at all: both passes read the
- * one surviving row, so the hour carries as many distinct values as it has ISPs. Once predicted
+ * That is a consequence of the naive primary key upstream (openremote/core#3292). The collapse
+ * can only duplicate a read, never erase one, so it cannot turn a day with a forecast into a
+ * skip, and while it lasts the repeated hour is never a gap at all: both passes read the one
+ * surviving row, so the hour carries as many distinct values as it has ISPs. Once predicted
* datapoints are stored in UTC every instant maps to a row of its own, a producer that writes the
* hour once leaves the other pass empty, and that pass is filled flat as above. The day submitted
* on the fall-back date therefore changes when #3292 lands; no other day is affected.
@@ -471,7 +471,7 @@ static List