notifications  

Messages by Thread

• • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
  • Re: [PR] IGNITE-28203 Use MarshalableMessage for ErrorMessage [ignite] via GitHub
• [PR] IGNITE-28194 Remove `ConfigurationModules` [ignite-3] via GitHub
  • Re: [PR] IGNITE-28194 Remove `ConfigurationModules` [ignite-3] via GitHub
  • Re: [PR] IGNITE-28194 Remove `ConfigurationModules` [ignite-3] via GitHub
  • Re: [PR] IGNITE-28194 Remove `ConfigurationModules` [ignite-3] via GitHub
  • Re: [PR] IGNITE-28194 Remove `ConfigurationModules` [ignite-3] via GitHub
  • Re: [PR] IGNITE-28194 Remove `ConfigurationModules` [ignite-3] via GitHub
• [PR] IGNITE-28191 Fix flaky recreateTableWithTheSameName test [ignite-3] via GitHub
  • Re: [PR] IGNITE-28191 Fix flaky recreateTableWithTheSameName test [ignite-3] via GitHub
• [PR] IGNITE-28018 Fine tuning for CI messages [ignite] via GitHub
  • Re: [PR] IGNITE-28018 Fine tuning for CI messages [ignite] via GitHub
  • Re: [PR] IGNITE-28018 Fine tuning for CI messages [ignite] via GitHub
• [PR] Disable immediate send future completion [ignite-3] via GitHub
  • Re: [PR] Disable immediate send future completion [ignite-3] via GitHub
• [PR] IGNITE-28189 WIP [ignite] via GitHub
  • Re: [PR] IGNITE-28189 WIP [ignite] via GitHub
  • Re: [PR] IGNITE-28189 WIP [ignite] via GitHub
  • Re: [PR] IGNITE-28189 WIP [ignite] via GitHub
  • Re: [PR] IGNITE-28189 WIP [ignite] via GitHub
  • Re: [PR] IGNITE-28189 WIP [ignite] via GitHub
  • Re: [PR] IGNITE-28189 WIP [ignite] via GitHub
  • Re: [PR] IGNITE-28189 WIP [ignite] via GitHub
  • Re: [PR] IGNITE-28189 Fixed incorrect status of a Compute Task when it is canceled [ignite] via GitHub
  • Re: [PR] IGNITE-28189 Fixed incorrect status of a Compute Task when it is canceled [ignite] via GitHub
  • Re: [PR] IGNITE-28189 Fixed incorrect status of a Compute Task when it is canceled [ignite] via GitHub
  • Re: [PR] IGNITE-28189 Fixed incorrect status of a Compute Task when it is canceled [ignite] via GitHub
  • Re: [PR] IGNITE-28189 Fixed incorrect status of a Compute Task when it is canceled [ignite] via GitHub
  • Re: [PR] IGNITE-28189 Fixed incorrect status of a Compute Task when it is canceled [ignite] via GitHub
  • Re: [PR] IGNITE-28189 Fixed incorrect status of a Compute Task when it is canceled [ignite] via GitHub
• [PR] IGNITE-28188 Constant descriptors for messages code generation [ignite] via GitHub
  • Re: [PR] IGNITE-28188 Constant descriptors for messages code generation [ignite] via GitHub
• [PR] Added hashing to C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing to C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing functions for C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing functions for C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing functions for C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing functions for C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing functions for C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing functions for C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing functions for C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing functions for C++ client [ignite-3] via GitHub
• [PR] IGNITE-28187 Non-transactional replica requests should be retried in the same manner as transactional [ignite-3] via GitHub
  • Re: [PR] IGNITE-28187 Non-transactional replica requests should be retried in the same manner as transactional [ignite-3] via GitHub
• [PR] IGNITE-27964 Use index-based approach in RaftLogGarbageCollector [ignite-3] via GitHub
  • Re: [PR] IGNITE-27964 Use index-based approach in RaftLogGarbageCollector [ignite-3] via GitHub
  • Re: [PR] IGNITE-27964 Use index-based approach in RaftLogGarbageCollector [ignite-3] via GitHub
  • Re: [PR] IGNITE-27964 Use index-based approach in RaftLogGarbageCollector [ignite-3] via GitHub
  • Re: [PR] IGNITE-27964 Use index-based approach in RaftLogGarbageCollector [ignite-3] via GitHub
  • Re: [PR] IGNITE-27964 Use index-based approach in RaftLogGarbageCollector [ignite-3] via GitHub
• [PR] IGNITE-28186 DeploymentSPI marked as deprecated [ignite] via GitHub
  • Re: [PR] IGNITE-28186 DeploymentSPI marked as deprecated [ignite] via GitHub
  • Re: [PR] IGNITE-28186 DeploymentSPI marked as deprecated [ignite] via GitHub
  • Re: [PR] IGNITE-28186 DeploymentSPI marked as deprecated [ignite] via GitHub
  • Re: [PR] IGNITE-28186 DeploymentSPI marked as deprecated [ignite] via GitHub
  • Re: [PR] IGNITE-28186 DeploymentSPI marked as deprecated [ignite] via GitHub
• [PR] IGNITE-28118 Add checkstyle rule to disallow TODO comments without ticket [ignite-3] via GitHub
  • Re: [PR] IGNITE-28118 Add checkstyle rule to disallow TODO comments without ticket [ignite-3] via GitHub
  • Re: [PR] IGNITE-28118 Add checkstyle rule to disallow TODO comments without ticket [ignite-3] via GitHub
  • Re: [PR] IGNITE-28118 Add checkstyle rule to disallow TODO comments without ticket [ignite-3] via GitHub
• [PR] IGNITE-28179 Add paged result fetching for CLI SQL [ignite-3] via GitHub
  • Re: [PR] IGNITE-28179 Add paged result fetching for CLI SQL [ignite-3] via GitHub
• [PR] IGNITE-27521 Java client: handle multiple endpoints for the same node [ignite-3] via GitHub
  • Re: [PR] IGNITE-27521 Java client: handle multiple endpoints for the same node [ignite-3] via GitHub
  • Re: [PR] IGNITE-27521 Java client: handle multiple endpoints for the same node [ignite-3] via GitHub
• [PR] IGNITE-28133 : Failure on cache.get() at the eviction [ignite] via GitHub
  • Re: [PR] IGNITE-28133 : Failure on cache.get() at the eviction [ignite] via GitHub
  • Re: [PR] IGNITE-28133 : Failure on cache.get() at the eviction [ignite] via GitHub
• [PR] IGNITE-27857 Set job status to COMPLETED when job ran to completion [ignite-3] via GitHub
  • Re: [PR] IGNITE-27857 Set job status to COMPLETED when job ran to completion [ignite-3] via GitHub
  • Re: [PR] IGNITE-27857 Set job status to COMPLETED when job ran to completion [ignite-3] via GitHub
• [PR] IGNITE-28124 Add new "aipersist" storage consistency metrics [ignite-3] via GitHub
• [PR] Remove deployment spi [ignite] via GitHub
  • Re: [PR] Remove deployment spi [ignite] via GitHub
• [PR] IGNITE-27034 Add client tests for table partition count change [ignite-3] via GitHub
  • Re: [PR] IGNITE-27034 Add client tests for table partition count change [ignite-3] via GitHub
  • Re: [PR] IGNITE-27034 Add client tests for table partition count change [ignite-3] via GitHub
• [PR] IGNITE-28123 ClientPrimaryReplicaTracker: avoid null-partitions failure when primary-replica lookup completes exceptionally [ignite-3] via GitHub
  • Re: [PR] IGNITE-28123 ClientPrimaryReplicaTracker: avoid null-partitions failure when primary-replica lookup completes exceptionally [ignite-3] via GitHub
  • Re: [PR] IGNITE-28123 ClientPrimaryReplicaTracker: avoid null-partitions failure when primary-replica lookup completes exceptionally [ignite-3] via GitHub
• [PR] IGNITE-27994 Create CLI command for REST endpoint to edit cluster name [ignite-3] via GitHub
  • Re: [PR] IGNITE-27994 Create CLI command for REST endpoint to edit cluster name [ignite-3] via GitHub
  • Re: [PR] IGNITE-27994 Create CLI command for REST endpoint to edit cluster name [ignite-3] via GitHub
• [PR] IGNITE-28120 Mute ItRebalanceMetricsTest.testRebalanceMetrics [ignite-3] via GitHub
  • Re: [PR] IGNITE-28120 Mute ItRebalanceMetricsTest.testRebalanceMetrics [ignite-3] via GitHub
• [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117 Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
• [PR] IGNITE-28114 Remove custom configuration for Apache RAT plugin [ignite] via GitHub
  • Re: [PR] IGNITE-28114 Remove custom configuration for Apache RAT plugin [ignite] via GitHub
  • Re: [PR] IGNITE-28114 Remove custom configuration for Apache RAT plugin [ignite] via GitHub
  • Re: [PR] IGNITE-28114 Remove custom configuration for Apache RAT plugin [ignite] via GitHub
  • Re: [PR] IGNITE-28114 Remove custom configuration for Apache RAT plugin [ignite] via GitHub
  • Re: [PR] IGNITE-28114 Remove custom configuration for Apache RAT plugin [ignite] via GitHub
• [PR] IGNITE-28116 update commons-lang3 [ignite] via GitHub
  • Re: [PR] IGNITE-28116 update commons-lang3 [ignite] via GitHub
  • Re: [PR] IGNITE-28116 update commons-lang3 [ignite] via GitHub
• [PR] IGNITE-28113 Load RocksDB in DefaultLogStorageManager [ignite-3] via GitHub
  • Re: [PR] IGNITE-28113 Load RocksDB in DefaultLogStorageManager [ignite-3] via GitHub
• [PR] Bump mockito from 5.21.0 to 5.22.0 [ignite-3] via GitHub
  • Re: [PR] Bump mockito from 5.21.0 to 5.22.0 [ignite-3] via GitHub
• [PR] IGNITE-28112 Bump jline from 3.29.0 to 4.0.0 [ignite-3] via GitHub
  • Re: [PR] IGNITE-28112 Bump jline from 3.29.0 to 4.0.4 [ignite-3] via GitHub
• [PR] IGNITE-28111 fix missed headers (include) files in non-linux distribu… [ignite-3] via GitHub
  • Re: [PR] IGNITE-28111 fix missed headers (include) files in non-linux distribu… [ignite-3] via GitHub
  • Re: [PR] IGNITE-28111 fix missed headers (include) files in non-linux distribu… [ignite-3] via GitHub
• [PR] IGNITE-28110 Fix buffer leak in ClientInboundMessageHandler on invalid message [ignite-3] via GitHub
  • Re: [PR] IGNITE-28110 Fix buffer leak in ClientInboundMessageHandler on invalid message [ignite-3] via GitHub
  • Re: [PR] IGNITE-28110 Fix buffer leak in ClientInboundMessageHandler on invalid message [ignite-3] via GitHub
• [PR] IGNITE-28106 .NET: Fix tx rollback to ignore connection errors [ignite-3] via GitHub
  • Re: [PR] IGNITE-28106 .NET: Fix tx rollback to ignore connection errors [ignite-3] via GitHub
• [PR] IGNITE-28105 Ensure new leader clock is not lower than last applied cmd [ignite-3] via GitHub
  • Re: [PR] IGNITE-28105 Ensure new leader clock is not lower than last applied cmd [ignite-3] via GitHub
  • Re: [PR] IGNITE-28105 Ensure new leader clock is not lower than last applied cmd [ignite-3] via GitHub
  • Re: [PR] IGNITE-28105 Ensure new leader clock is not lower than last applied cmd [ignite-3] via GitHub
  • Re: [PR] IGNITE-28105 Ensure new leader clock is not lower than last applied cmd [ignite-3] via GitHub
• Re: [PR] IGNITE-27091 Fix client tx rollback to ignore connection errors [ignite-3] via GitHub
• [PR] IGNITE-28097 [ignite] via GitHub
  • Re: [PR] IGNITE-28097 [ignite] via GitHub
  • Re: [PR] IGNITE-28097 [ignite] via GitHub
  • Re: [PR] IGNITE-28097 [ignite] via GitHub
  • Re: [PR] IGNITE-28097 [ignite] via GitHub
  • Re: [PR] IGNITE-28097 [ignite] via GitHub
  • Re: [PR] IGNITE-28097 [ignite] via GitHub
  • Re: [PR] IGNITE-28097 [ignite] via GitHub
  • Re: [PR] IGNITE-28097 [ignite] via GitHub
  • Re: [PR] IGNITE-28097 [ignite] via GitHub
  • Re: [PR] IGNITE-28097 [ignite] via GitHub
  • Re: [PR] IGNITE-28097 [ignite] via GitHub
  • Re: [PR] IGNITE-28097 Fixeв unclosed socket if the client node stopped during a reconnect. [ignite] via GitHub
  • Re: [PR] IGNITE-28097 Fixeв unclosed socket if the client node stopped during a reconnect. [ignite] via GitHub
  • Re: [PR] IGNITE-28097 Fixeв unclosed socket if the client node stopped during a reconnect. [ignite] via GitHub
  • Re: [PR] IGNITE-28097 Fixeв unclosed socket if the client node stopped during a reconnect. [ignite] via GitHub
  • Re: [PR] IGNITE-28097 Fixeв unclosed socket if the client node stopped during a reconnect. [ignite] via GitHub
  • Re: [PR] IGNITE-28097 Fixed unclosed socket if the client node stopped during a reconnect. [ignite] via GitHub
  • Re: [PR] IGNITE-28097 Fixed unclosed socket if the client node stopped during a reconnect. [ignite] via GitHub
• [PR] IGNITE-27947 Impossible to rollback client first transaction request [ignite-3] via GitHub
  • Re: [PR] IGNITE-27947 Impossible to rollback client first transaction request [ignite-3] via GitHub
  • Re: [PR] IGNITE-27947 Impossible to rollback client first transaction request [ignite-3] via GitHub
  • Re: [PR] IGNITE-27947 Impossible to rollback client first transaction request [ignite-3] via GitHub
  • Re: [PR] IGNITE-27947 Impossible to rollback client first transaction request [ignite-3] via GitHub
  • Re: [PR] IGNITE-27947 Impossible to rollback client first transaction request [ignite-3] via GitHub
• [PR] IGNITE-28076 Use watch executor in SchemaSafeTimeTrackerImpl [ignite-3] via GitHub
  • Re: [PR] IGNITE-28076 Use watch executor in SchemaSafeTimeTrackerImpl [ignite-3] via GitHub
  • Re: [PR] IGNITE-28076 Use watch executor in SchemaSafeTimeTrackerImpl [ignite-3] via GitHub
  • Re: [PR] IGNITE-28076 Use watch executor in SchemaSafeTimeTrackerImpl [ignite-3] via GitHub
  • Re: [PR] IGNITE-28076 Use watch executor in SchemaSafeTimeTrackerImpl [ignite-3] via GitHub
  • Re: [PR] IGNITE-28076 Use watch executor in SchemaSafeTimeTrackerImpl [ignite-3] via GitHub
  • Re: [PR] IGNITE-28076 Use watch executor in SchemaSafeTimeTrackerImpl [ignite-3] via GitHub
  • Re: [PR] IGNITE-28076 Use watch executor in SchemaSafeTimeTrackerImpl [ignite-3] via GitHub
  • Re: [PR] IGNITE-28076 Use watch executor in SchemaSafeTimeTrackerImpl [ignite-3] via GitHub
  • Re: [PR] IGNITE-28076 Use watch executor in SchemaSafeTimeTrackerImpl [ignite-3] via GitHub
• [PR] IGNITE-28094 Revert "IGNITE-27906 Remove creating redundant collections (#7628)" [ignite-3] via GitHub
  • Re: [PR] IGNITE-28094 Revert "IGNITE-27906 Remove creating redundant collections (#7628)" [ignite-3] via GitHub
• [PR] IGNITE-28091 Validate configuration in ConfigurationExtension [ignite-3] via GitHub
  • Re: [PR] IGNITE-28091 Validate configuration in ConfigurationExtension [ignite-3] via GitHub
  • Re: [PR] IGNITE-28091 Validate configuration in ConfigurationExtension [ignite-3] via GitHub
  • Re: [PR] IGNITE-28091 Validate configuration in ConfigurationExtension [ignite-3] via GitHub
  • Re: [PR] IGNITE-28091 Validate configuration in ConfigurationExtension [ignite-3] via GitHub
  • Re: [PR] IGNITE-28091 Validate configuration in ConfigurationExtension [ignite-3] via GitHub
• [PR] IGNITE-28093 Disable IgniteServerStartTest.igniteServerStartTest [ignite-3] via GitHub

• Earlier messages
• Later messages