sitewhere/sitewhere issues and pull requests

#953 - Database substitution tenant_${tenant.id} wildcard of influx is not properly resolved

Issue - State: closed - Opened by ATM006 over 3 years ago - 1 comment
Labels: bug

#953 - Database substitution tenant_${tenant.id} wildcard of influx is not properly resolved

Issue - State: closed - Opened by ATM006 over 3 years ago - 1 comment
Labels: bug

#953 - Database substitution tenant_${tenant.id} wildcard of influx is not properly resolved

Issue - State: closed - Opened by ATM006 over 3 years ago - 1 comment
Labels: bug

#953 - Database substitution tenant_${tenant.id} wildcard of influx is not properly resolved

Issue - State: closed - Opened by ATM006 over 3 years ago - 1 comment
Labels: bug

#953 - Database substitution tenant_${tenant.id} wildcard of influx is not properly resolved

Issue - State: closed - Opened by ATM006 over 3 years ago - 1 comment
Labels: bug

#953 - Database substitution tenant_${tenant.id} wildcard of influx is not properly resolved

Issue - State: closed - Opened by ATM006 over 3 years ago - 1 comment
Labels: bug

#952 - How to use sitewhere-nifi

Issue - State: open - Opened by ATM006 over 3 years ago - 1 comment
Labels: question

#952 - How to use sitewhere-nifi

Issue - State: open - Opened by ATM006 over 3 years ago - 1 comment
Labels: question

#952 - How to use sitewhere-nifi

Issue - State: open - Opened by ATM006 over 3 years ago - 1 comment
Labels: question

#952 - How to use sitewhere-nifi

Issue - State: open - Opened by ATM006 over 3 years ago - 1 comment
Labels: question

#952 - How to use sitewhere-nifi

Issue - State: open - Opened by ATM006 over 3 years ago - 1 comment
Labels: question

#952 - How to use sitewhere-nifi

Issue - State: open - Opened by ATM006 over 3 years ago - 1 comment
Labels: question

#951 - Support invoking device commands via MQTT inputs

Issue - State: open - Opened by derekadams over 3 years ago
Labels: new feature

#951 - Support invoking device commands via MQTT inputs

Issue - State: open - Opened by derekadams over 3 years ago
Labels: new feature

#951 - Support invoking device commands via MQTT inputs

Issue - State: open - Opened by derekadams over 3 years ago
Labels: new feature

#951 - Support invoking device commands via MQTT inputs

Issue - State: open - Opened by derekadams over 3 years ago
Labels: new feature

#951 - Support invoking device commands via MQTT inputs

Issue - State: open - Opened by derekadams over 3 years ago
Labels: new feature

#951 - Support invoking device commands via MQTT inputs

Issue - State: open - Opened by derekadams over 3 years ago
Labels: new feature

#951 - Support invoking device commands via MQTT inputs

Issue - State: open - Opened by derekadams over 3 years ago
Labels: new feature

#951 - Support invoking device commands via MQTT inputs

Issue - State: open - Opened by derekadams over 3 years ago
Labels: new feature

#951 - Support invoking device commands via MQTT inputs

Issue - State: open - Opened by derekadams over 3 years ago
Labels: new feature

#951 - Support invoking device commands via MQTT inputs

Issue - State: open - Opened by derekadams over 3 years ago
Labels: new feature

#951 - Support invoking device commands via MQTT inputs

Issue - State: open - Opened by derekadams over 3 years ago
Labels: new feature

#950 - Command delivery is not available，“Unhandled exception in producer while sending record.”

Issue - State: closed - Opened by ATM006 over 3 years ago - 2 comments
Labels: bug

#950 - Command delivery is not available，“Unhandled exception in producer while sending record.”

Issue - State: closed - Opened by ATM006 over 3 years ago - 2 comments
Labels: bug

#950 - Command delivery is not available，“Unhandled exception in producer while sending record.”

Issue - State: closed - Opened by ATM006 over 3 years ago - 2 comments
Labels: bug

#950 - Command delivery is not available，“Unhandled exception in producer while sending record.”

Issue - State: closed - Opened by ATM006 over 3 years ago - 2 comments
Labels: bug

#950 - Command delivery is not available，“Unhandled exception in producer while sending record.”

Issue - State: closed - Opened by ATM006 over 3 years ago - 2 comments
Labels: bug

#950 - Command delivery is not available，“Unhandled exception in producer while sending record.”

Issue - State: closed - Opened by ATM006 over 3 years ago - 2 comments
Labels: bug

#950 - Command delivery is not available，“Unhandled exception in producer while sending record.”

Issue - State: closed - Opened by ATM006 over 3 years ago - 2 comments
Labels: bug

#950 - Command delivery is not available，“Unhandled exception in producer while sending record.”

Issue - State: closed - Opened by ATM006 over 3 years ago - 2 comments
Labels: bug

#950 - Command delivery is not available，“Unhandled exception in producer while sending record.”

Issue - State: closed - Opened by ATM006 over 3 years ago - 2 comments
Labels: bug

#950 - Command delivery is not available，“Unhandled exception in producer while sending record.”

Issue - State: closed - Opened by ATM006 over 3 years ago - 2 comments
Labels: bug

#950 - Command delivery is not available，“Unhandled exception in producer while sending record.”

Issue - State: closed - Opened by ATM006 over 3 years ago - 2 comments
Labels: bug

#949 - What is the difference between Device States and Device Statuses？

Issue - State: closed - Opened by ATM006 over 3 years ago - 3 comments
Labels: question

#949 - What is the difference between Device States and Device Statuses？

Issue - State: closed - Opened by ATM006 over 3 years ago - 3 comments
Labels: question

#949 - What is the difference between Device States and Device Statuses？

Issue - State: closed - Opened by ATM006 over 3 years ago - 3 comments
Labels: question

#949 - What is the difference between Device States and Device Statuses？

Issue - State: closed - Opened by ATM006 over 3 years ago - 3 comments
Labels: question

#949 - What is the difference between Device States and Device Statuses？

Issue - State: closed - Opened by ATM006 over 3 years ago - 3 comments
Labels: question

#949 - What is the difference between Device States and Device Statuses？

Issue - State: closed - Opened by ATM006 over 3 years ago - 3 comments
Labels: question

#949 - What is the difference between Device States and Device Statuses？

Issue - State: closed - Opened by ATM006 over 3 years ago - 3 comments
Labels: question

#949 - What is the difference between Device States and Device Statuses？

Issue - State: closed - Opened by ATM006 over 3 years ago - 3 comments
Labels: question

#949 - What is the difference between Device States and Device Statuses？

Issue - State: closed - Opened by ATM006 over 3 years ago - 3 comments
Labels: question

#949 - What is the difference between Device States and Device Statuses？

Issue - State: closed - Opened by ATM006 over 3 years ago - 3 comments
Labels: question

#949 - What is the difference between Device States and Device Statuses？

Issue - State: closed - Opened by ATM006 over 3 years ago - 3 comments
Labels: question

#949 - What is the difference between Device States and Device Statuses？

Issue - State: closed - Opened by ATM006 over 3 years ago - 3 comments
Labels: question

#949 - What is the difference between Device States and Device Statuses？

Issue - State: closed - Opened by ATM006 over 3 years ago - 3 comments
Labels: question

#949 - What is the difference between Device States and Device Statuses？

Issue - State: closed - Opened by ATM006 over 3 years ago - 3 comments
Labels: question

#949 - What is the difference between Device States and Device Statuses？

Issue - State: closed - Opened by ATM006 over 3 years ago - 3 comments
Labels: question

#948 - How do you debug sitewhere-3.0 locally

Issue - State: open - Opened by liwh1111 over 3 years ago - 3 comments
Labels: bug

#948 - How do you debug sitewhere-3.0 locally

Issue - State: open - Opened by liwh1111 over 3 years ago - 3 comments
Labels: bug

#948 - How do you debug sitewhere-3.0 locally

Issue - State: open - Opened by liwh1111 over 3 years ago - 3 comments
Labels: bug

#948 - How do you debug sitewhere-3.0 locally

Issue - State: open - Opened by liwh1111 over 3 years ago - 3 comments
Labels: bug

#948 - How do you debug sitewhere-3.0 locally

Issue - State: open - Opened by liwh1111 over 3 years ago - 3 comments
Labels: bug

#948 - How do you debug sitewhere-3.0 locally

Issue - State: open - Opened by liwh1111 over 3 years ago - 3 comments
Labels: bug

#948 - How do you debug sitewhere-3.0 locally

Issue - State: open - Opened by liwh1111 over 3 years ago - 3 comments
Labels: bug

#948 - How do you debug sitewhere-3.0 locally

Issue - State: open - Opened by liwh1111 over 3 years ago - 3 comments
Labels: bug

#947 - A serious error occurred during version 3.0.3 testing“All stream threads have died. The instance will be in error state and should be closed”

Issue - State: open - Opened by ATM006 over 3 years ago - 9 comments
Labels: bug

#947 - A serious error occurred during version 3.0.3 testing“All stream threads have died. The instance will be in error state and should be closed”

Issue - State: open - Opened by ATM006 over 3 years ago - 9 comments
Labels: bug

#947 - A serious error occurred during version 3.0.3 testing“All stream threads have died. The instance will be in error state and should be closed”

Issue - State: open - Opened by ATM006 over 3 years ago - 9 comments
Labels: bug

#947 - A serious error occurred during version 3.0.3 testing“All stream threads have died. The instance will be in error state and should be closed”

Issue - State: open - Opened by ATM006 over 3 years ago - 9 comments
Labels: bug

#947 - A serious error occurred during version 3.0.3 testing“All stream threads have died. The instance will be in error state and should be closed”

Issue - State: open - Opened by ATM006 over 3 years ago - 9 comments
Labels: bug

#947 - A serious error occurred during version 3.0.3 testing“All stream threads have died. The instance will be in error state and should be closed”

Issue - State: open - Opened by ATM006 over 3 years ago - 9 comments
Labels: bug

#947 - A serious error occurred during version 3.0.3 testing“All stream threads have died. The instance will be in error state and should be closed”

Issue - State: open - Opened by ATM006 over 3 years ago - 9 comments
Labels: bug

#947 - A serious error occurred during version 3.0.3 testing“All stream threads have died. The instance will be in error state and should be closed”

Issue - State: open - Opened by ATM006 over 3 years ago - 9 comments
Labels: bug

#947 - A serious error occurred during version 3.0.3 testing“All stream threads have died. The instance will be in error state and should be closed”

Issue - State: open - Opened by ATM006 over 3 years ago - 9 comments
Labels: bug

#947 - A serious error occurred during version 3.0.3 testing“All stream threads have died. The instance will be in error state and should be closed”

Issue - State: open - Opened by ATM006 over 3 years ago - 9 comments
Labels: bug

#946 - API call for getting asset type label fails with NPE

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#946 - API call for getting asset type label fails with NPE

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#946 - API call for getting asset type label fails with NPE

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#946 - API call for getting asset type label fails with NPE

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#946 - API call for getting asset type label fails with NPE

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#946 - API call for getting asset type label fails with NPE

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#946 - API call for getting asset type label fails with NPE

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#946 - API call for getting asset type label fails with NPE

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#945 - Current cache implementation does not respect TTL value

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug/critical

#945 - Current cache implementation does not respect TTL value

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug/critical

#945 - Current cache implementation does not respect TTL value

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug/critical

#945 - Current cache implementation does not respect TTL value

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug/critical

#945 - Current cache implementation does not respect TTL value

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug/critical

#945 - Current cache implementation does not respect TTL value

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug/critical

#945 - Current cache implementation does not respect TTL value

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug/critical

#944 - Calling API for ending an assignment results in 415 response when called from admin UI

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#944 - Calling API for ending an assignment results in 415 response when called from admin UI

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#944 - Calling API for ending an assignment results in 415 response when called from admin UI

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#944 - Calling API for ending an assignment results in 415 response when called from admin UI

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#944 - Calling API for ending an assignment results in 415 response when called from admin UI

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#944 - Calling API for ending an assignment results in 415 response when called from admin UI

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#944 - Calling API for ending an assignment results in 415 response when called from admin UI

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#944 - Calling API for ending an assignment results in 415 response when called from admin UI

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#944 - Calling API for ending an assignment results in 415 response when called from admin UI

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#944 - Calling API for ending an assignment results in 415 response when called from admin UI

Issue - State: closed - Opened by derekadams over 3 years ago
Labels: bug

#943 - feat: add script to publish docker images in tag.

Pull Request - State: closed - Opened by jorgevillaverde-sitewhere over 3 years ago

#943 - feat: add script to publish docker images in tag.

Pull Request - State: closed - Opened by jorgevillaverde-sitewhere over 3 years ago

#943 - feat: add script to publish docker images in tag.

Pull Request - State: closed - Opened by jorgevillaverde-sitewhere over 3 years ago

#943 - feat: add script to publish docker images in tag.

Pull Request - State: closed - Opened by jorgevillaverde-sitewhere over 3 years ago

#943 - feat: add script to publish docker images in tag.

Pull Request - State: closed - Opened by jorgevillaverde-sitewhere over 3 years ago

#943 - feat: add script to publish docker images in tag.

Pull Request - State: closed - Opened by jorgevillaverde-sitewhere over 3 years ago

#943 - feat: add script to publish docker images in tag.

Pull Request - State: closed - Opened by jorgevillaverde-sitewhere over 3 years ago

#943 - feat: add script to publish docker images in tag.

Pull Request - State: closed - Opened by jorgevillaverde-sitewhere over 3 years ago

GitHub / sitewhere/sitewhere issues and pull requests