Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / cph-cachet/carp.core-kotlin issues and pull requests
#390 - How to best upload data for sensors that send batched data with a single timestamp?
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature, needs discussion
#390 - How to best upload data for sensors that send batched data with a single timestamp?
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature, needs discussion
#390 - How to best upload data for sensors that send batched data with a single timestamp?
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature, needs discussion
#390 - How to best upload data for sensors that send batched data with a single timestamp?
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature, needs discussion
#390 - How to best upload data for sensors that send batched data with a single timestamp?
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature, needs discussion
#390 - How to best upload data for sensors that send batched data with a single timestamp?
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature, needs discussion
#390 - How to best upload data for sensors that send batched data with a single timestamp?
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature, needs discussion
#390 - How to best upload data for sensors that send batched data with a single timestamp?
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature, needs discussion
#390 - How to best upload data for sensors that send batched data with a single timestamp?
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature, needs discussion
#389 - Concatenate `DataTypeMetaDataMap`s
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#389 - Concatenate `DataTypeMetaDataMap`s
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#389 - Concatenate `DataTypeMetaDataMap`s
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#389 - Concatenate `DataTypeMetaDataMap`s
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#389 - Concatenate `DataTypeMetaDataMap`s
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#389 - Concatenate `DataTypeMetaDataMap`s
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#389 - Concatenate `DataTypeMetaDataMap`s
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#389 - Concatenate `DataTypeMetaDataMap`s
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#389 - Concatenate `DataTypeMetaDataMap`s
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#389 - Concatenate `DataTypeMetaDataMap`s
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#389 - Concatenate `DataTypeMetaDataMap`s
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#389 - Concatenate `DataTypeMetaDataMap`s
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#388 - Upgrade to Kotlin 1.6.21 or higher
Issue -
State: closed - Opened by Whathecode over 2 years ago
- 1 comment
Labels: technical debt
#388 - Upgrade to Kotlin 1.6.21 or higher
Issue -
State: closed - Opened by Whathecode over 2 years ago
- 1 comment
Labels: technical debt
#387 - Upgrade to Kotlin 1.6.21, serialization 1.3.3
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
- 1 comment
#387 - Upgrade to Kotlin 1.6.21, serialization 1.3.3
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
- 1 comment
#387 - Upgrade to Kotlin 1.6.21, serialization 1.3.3
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
- 1 comment
#386 - Transfer repository to iMotions
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#386 - Transfer repository to iMotions
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#386 - Transfer repository to iMotions
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#386 - Transfer repository to iMotions
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#386 - Transfer repository to iMotions
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#386 - Transfer repository to iMotions
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#386 - Transfer repository to iMotions
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#386 - Transfer repository to iMotions
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#386 - Transfer repository to iMotions
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#386 - Transfer repository to iMotions
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#386 - Transfer repository to iMotions
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#386 - Transfer repository to iMotions
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#386 - Transfer repository to iMotions
Issue -
State: closed - Opened by Whathecode over 2 years ago
Labels: feature
#385 - Don't rely on Chrome or node installation for unit testing
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: enhancement
#385 - Don't rely on Chrome or node installation for unit testing
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: enhancement
#385 - Don't rely on Chrome or node installation for unit testing
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: enhancement
#385 - Don't rely on Chrome or node installation for unit testing
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: enhancement
#385 - Don't rely on Chrome or node installation for unit testing
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: enhancement
#385 - Don't rely on Chrome or node installation for unit testing
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: enhancement
#385 - Don't rely on Chrome or node installation for unit testing
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: enhancement
#385 - Don't rely on Chrome or node installation for unit testing
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: enhancement
#384 - Support stopping deployment process in `ClientManager`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature
#384 - Support stopping deployment process in `ClientManager`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature
#384 - Support stopping deployment process in `ClientManager`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature
#384 - Support stopping deployment process in `ClientManager`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature
#384 - Support stopping deployment process in `ClientManager`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature
#384 - Support stopping deployment process in `ClientManager`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature
#384 - Support stopping deployment process in `ClientManager`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature
#384 - Support stopping deployment process in `ClientManager`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature
#384 - Support stopping deployment process in `ClientManager`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: feature
#383 - Data streams shouldn't be opened when redeploying devices
Issue -
State: closed - Opened by Whathecode over 2 years ago
- 1 comment
Labels: bug
#383 - Data streams shouldn't be opened when redeploying devices
Issue -
State: closed - Opened by Whathecode over 2 years ago
- 1 comment
Labels: bug
#382 - Release 1.0.0
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
#382 - Release 1.0.0
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
#382 - Release 1.0.0
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
#382 - Release 1.0.0
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
#382 - Release 1.0.0
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
#382 - Release 1.0.0
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
#382 - Release 1.0.0
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
#382 - Release 1.0.0
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
#382 - Release 1.0.0
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
#381 - Build(deps): bump ansi-regex from 3.0.0 to 3.0.1 in /typescript-declarations
Pull Request -
State: closed - Opened by dependabot[bot] over 2 years ago
- 2 comments
Labels: dependencies
#380 - Final changes pre 1.0 release
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
#380 - Final changes pre 1.0 release
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
#380 - Final changes pre 1.0 release
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
#380 - Final changes pre 1.0 release
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
#380 - Final changes pre 1.0 release
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
#380 - Final changes pre 1.0 release
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
#380 - Final changes pre 1.0 release
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
#380 - Final changes pre 1.0 release
Pull Request -
State: closed - Opened by Whathecode over 2 years ago
#379 - `TimeOfDay` does not fully match ISO 8601
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#379 - `TimeOfDay` does not fully match ISO 8601
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#379 - `TimeOfDay` does not fully match ISO 8601
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#379 - `TimeOfDay` does not fully match ISO 8601
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#379 - `TimeOfDay` does not fully match ISO 8601
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#379 - `TimeOfDay` does not fully match ISO 8601
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#379 - `TimeOfDay` does not fully match ISO 8601
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#379 - `TimeOfDay` does not fully match ISO 8601
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#379 - `TimeOfDay` does not fully match ISO 8601
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#379 - `TimeOfDay` does not fully match ISO 8601
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#379 - `TimeOfDay` does not fully match ISO 8601
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#378 - When empty sets are returned in TS, they aren't `instanceof HashSet`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#378 - When empty sets are returned in TS, they aren't `instanceof HashSet`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#378 - When empty sets are returned in TS, they aren't `instanceof HashSet`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#378 - When empty sets are returned in TS, they aren't `instanceof HashSet`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#378 - When empty sets are returned in TS, they aren't `instanceof HashSet`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#378 - When empty sets are returned in TS, they aren't `instanceof HashSet`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#378 - When empty sets are returned in TS, they aren't `instanceof HashSet`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#378 - When empty sets are returned in TS, they aren't `instanceof HashSet`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#378 - When empty sets are returned in TS, they aren't `instanceof HashSet`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#378 - When empty sets are returned in TS, they aren't `instanceof HashSet`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#378 - When empty sets are returned in TS, they aren't `instanceof HashSet`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#378 - When empty sets are returned in TS, they aren't `instanceof HashSet`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug
#378 - When empty sets are returned in TS, they aren't `instanceof HashSet`
Issue -
State: open - Opened by Whathecode over 2 years ago
Labels: bug