GlobalEndpointManager.GetAccountPropertiesHelper throwing exception resulting in unhandled exception in client application

We are continuously addressing and improving the SDK, if possible, make sure the problem persist in the latest SDK version.

Describe the bug
GlobalEndpointManager.GetAccountPropertiesHelper is throwing exception. This is a background operation as far as i understand, an exception thrown here isnt handled by application.
CallerContext:CorrelationId=7f72270a-98fc-4e6b-b4d2-d62bddd466ce;ActivityVector=<IP_ADDRESS>. | HandleException:System.AggregateException: One or more errors occurred. ---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Net.Http.HttpClient.d__59.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.CosmosHttpClientCore.d__15.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.CosmosHttpClientCore.d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.GatewayStoreModel.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.DocumentClient.d__303.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Routing.GlobalEndpointManager.GetAccountPropertiesHelper.d__13.MoveNext()
--- End of inner exception stack trace ---
at Microsoft.Azure.Cosmos.Routing.GlobalEndpointManager.GetAccountPropertiesHelper.d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Common.AsyncCache2.<GetAsync>d__8.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.Routing.GlobalEndpointManager.<GetDatabaseAccountAsync>d__38.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.Routing.GlobalEndpointManager.<RefreshDatabaseAccountInternalAsync>d__37.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.Routing.GlobalEndpointManager.<RefreshLocationAsync>d__33.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.ClientRetryPolicy.<ShouldRetryOnEndpointFailureAsync>d__21.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.ClientRetryPolicy.<ShouldRetryAsync>d__16.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.RenameCollectionAwareClientRetryPolicy.<ShouldRetryAsync>d__7.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.Handlers.AbstractRetryHandler.<ExecuteHttpRequestAsync>d__2.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.Handlers.AbstractRetryHandler.<SendAsync>d__1.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.RequestHandler.<SendAsync>d__6.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.Handlers.DiagnosticsHandler.<SendAsync>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.RequestHandler.<SendAsync>d__6.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.Handlers.RequestInvokerHandler.<SendAsync>d__7.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.Handlers.RequestInvokerHandler.<SendAsync>d__9.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.CosmosQueryClientCore.<ExecuteItemQueryAsync>d__10.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.Pagination.NetworkAttachedDocumentContainer.<MonadicQueryAsync>d__16.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.Pagination.PartitionRangePageAsyncEnumerator2.d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Pagination.FullyBufferedPartitionRangeAsyncEnumerator2.<PrefetchAsync>d__8.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.Pagination.ParallelPrefetch.<>c__DisplayClass0_2.<<PrefetchInParallelAsync>b__1>d.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.Pagination.ParallelPrefetch.<PrefetchInParallelAsync>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at Microsoft.Azure.Cosmos.Pagination.ParallelPrefetch.<PrefetchInParallelAsync>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.Pagination.CrossPartitionRangePageAsyncEnumerator2.d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.AsyncLazy1.<GetValueAsync>d__7.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.Pagination.CrossPartitionRangePageAsyncEnumerator2.d__14.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.Pipeline.CrossPartition.Parallel.ParallelCrossPartitionQueryPipelineStage.d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.Pipeline.Aggregate.AggregateQueryPipelineStage.ClientAggregateQueryPipelineStage.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.Pipeline.SkipEmptyPageQueryPipelineStage.d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.Pipeline.LazyQueryPipelineStage.d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.Pipeline.NameCacheStaleRetryQueryPipelineStage.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.Pipeline.CatchAllQueryPipelineStage.d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.QueryIterator.d__14.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.ClientContextCore.d__391.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.Azure.Cosmos.ClientContextCore.<OperationHelperWithRootTraceAsync>d__301.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.CDS.NonRelational.Store.Core.CosmosDBClient.d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.CDS.NonRelational.Store.Core.CosmosDBStore.<>c__DisplayClass31_0.<b__1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.CDS.NonRelational.Common.ExecuteWithRetry.d__101.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at Microsoft.CDS.NonRelational.Common.ExecuteWithRetry.<RunAsync>d__101.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.CDS.NonRelational.Common.ExecuteWithRetry.d__101.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at Microsoft.CDS.NonRelational.Common.ExecuteWithRetry.<RunAsync>d__101.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.CDS.NonRelational.Store.Core.CosmosDBStore.<>c__DisplayClass31_0.<b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.d__111.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.<ExecuteAsync>d__31.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.CDS.NonRelational.Store.Core.CosmosDBStore.d__31.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.CDS.NonRelational.Store.CustomEntityStore.d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.CDS.NRD.WebApi.Controllers.CustomEntityController.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.TaskOfIActionResultExecutor.d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context)
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context)
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Builder.RouterMiddleware.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.d__6.MoveNext()
---> (Inner Exception #0) System.Threading.Tasks.TaskCanceledException: A task was canceled.
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Net.Http.HttpClient.d__59.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.CosmosHttpClientCore.d__15.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.CosmosHttpClientCore.d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.GatewayStoreModel.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.DocumentClient.d__303.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Routing.GlobalEndpointManager.GetAccountPropertiesHelper.d__13.MoveNext()<---
---> (Inner Exception #1) System.Threading.Tasks.TaskCanceledException: A task was canceled.
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Net.Http.HttpClient.d__59.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.CosmosHttpClientCore.d__15.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.CosmosHttpClientCore.d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.GatewayStoreModel.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.DocumentClient.d__303.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Routing.GlobalEndpointManager.GetAccountPropertiesHelper.d__13.MoveNext()<---
---> (Inner Exception #2) System.Threading.Tasks.TaskCanceledException: A task was canceled.
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Net.Http.HttpClient.d__59.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.CosmosHttpClientCore.d__15.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.CosmosHttpClientCore.d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.GatewayStoreModel.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.DocumentClient.d__303.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Routing.GlobalEndpointManager.GetAccountPropertiesHelper.d__13.MoveNext()<---
| LoadException:
To Reproduce
Intermittent, not able to repro
Expected behavior
There isnt anything a client application can do other than catching and ignoring this exception. Should be handled better in the SDK.
Actual behavior
Applications can receive unhandled exception which they need to handle and ignore
Environment summary
SDK Version: 3.31.2
OS Version - Windows server 2019

what is the operation you are making? looks like some cross partition query operation?
Microsoft.Azure.Cosmos.Pagination.CrossPartitionRangePageAsyncEnumerator2.d__20.MoveNext()

Looks like, this stacktrace is mixture of multiple exceptions. can you please provide exception, you are getting and are concerning you.

The possible root is in GlobalEndpointManager.GetDatabaseAccountAsync: singleValueInitFunc isn't awaited (runs in the background) and doesn't have try/catch handling inside.


Support Keychain creation

depend of https://github.com/archethic-foundation/libjs/issues/12

"Add keychain creation and access" ready in libjs
https://github.com/archethic-foundation/libjs/commit/aceec07cf40fb65d3d93abd8cb06926f19302e49
Go to implementation in dart :)

deployed in 1.0.7


Scout Crash on startup

I am trying to use Scout on a brand new VM, and every time I try to compile my scss file I get the following.
Errno::ENOENT on line 102 of org/jruby/RubyFileTest.java: No such file or directory - //psf/Home
org/jruby/RubyFileTest.java:87:in directory?' C:/Program Files (x86)/Scout/vendor/gems/gems/compass-0.12.2/lib/compass.rb:19:in shared_extension_paths'
C:/Program Files (x86)/Scout/vendor/gems/gems/compass-0.12.2/lib/compass/configuration/helpers.rb:112:in discover_extensions!' C:/Program Files (x86)/Scout/vendor/gems/gems/compass-0.12.2/lib/compass/commands/project_base.rb:27:in configure!'
C:/Program Files (x86)/Scout/vendor/gems/gems/compass-0.12.2/lib/compass/commands/project_base.rb:15:in initialize' C:/Program Files (x86)/Scout/vendor/gems/gems/compass-0.12.2/lib/compass/commands/update_project.rb:37:in initialize'
C:/Program Files (x86)/Scout/vendor/gems/gems/compass-0.12.2/lib/compass/exec/sub_command_ui.rb:42:in perform!' C:/Program Files (x86)/Scout/vendor/gems/gems/compass-0.12.2/lib/compass/exec/sub_command_ui.rb:15:in run!'
C:\Program Files (x86)\Scout\bin\compass:12:in `(root)'
Now I fully expect that I have missed something in my install on this system. Are there any prerequisites for running Scout? (other than Air that is). Do I need to install ruby? I've used Scout on an previous computer and didn't have any issues with it. The main difference that I can think of is that I am running Win 7 under a VM instead of on direct hardware.
Any help would be appreciated.

Issue resolved. Closing ticket. Download latest version of Scout-App.

Scout-App 2 (2016)


Add Error() and String() to InterruptedError

fixes #50

InterruptedError extends Exception which has stack trace. If your changes are applied this stacktrace would become inaccessible. I would extract the code that prints stacktrace and call it from both Exception and InterruptedError.

@dop251 not sure I understand the difference re stack between String() and Error(). Why is Exception.Error() not iterating and printing the entire stack?

Error() is a short single-line version because that's what's used by fmt and you don't want to mess the output with multi-line stacktrace. If you need the stacktrace you use String().

Are you still working on it @slavikm ?

Oops, sorry. Yes, will push ASAP.


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit 7891881:
:clock10: Full build: the average full build time is 5 min(s) 59 sec(s), this is based on the last 608 build(s) for this repository.

Docs Build status updates of commit 7891881:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

docs-ref-conceptual/testing.md
:bulb:Suggestion
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/testing.md

[Suggestion] Missing attribute: title. Add a title string to show in search engine results.
[Suggestion] Missing attribute: title. Add a title string to show in search engine results.
[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


NSDate addUnit stuff not working in ios7

The dateByAddingUnit() function is only supported in ios 8 and above, which is what is used in this project.

@pNre if you want to support iOS 7 I can take care of this issue.
If the OS is ios < 8 OR osX < 10.9 we should use NSDateComponents otherwise dateByAddingUnit.

@PGLongo sure, thanks

No problem! I will fix it tomorrow

I have found a funny thing: adding single unit at time or multiple units produces different results
        let components = NSDateComponents()
        components.setValue(seconds, forComponent: .CalendarUnitSecond)
        components.setValue(minutes, forComponent: .CalendarUnitMinute)
        components.setValue(days, forComponent: .CalendarUnitDay)
        components.setValue(hours, forComponent: .CalendarUnitHour)
        components.setValue(weeks, forComponent: .CalendarUnitWeekOfMonth)
        components.setValue(months, forComponent: .CalendarUnitMonth)
        components.setValue(years, forComponent: .CalendarUnitYear)
        var date : NSDate! = calendar.dateByAddingComponents(components, toDate: self, options: nil)!

is different from
        date = calendar.dateByAddingUnit(.CalendarUnitSecond, value: seconds, toDate: self, options: nil)
        date = calendar.dateByAddingUnit(.CalendarUnitMinute, value: minutes, toDate: date, options: nil)
        date = calendar.dateByAddingUnit(.CalendarUnitDay, value: days, toDate: date, options: nil)
        date = calendar.dateByAddingUnit(.CalendarUnitHour, value: hours, toDate: date, options: nil)
        date = calendar.dateByAddingUnit(.CalendarUnitWeekOfMonth, value: weeks, toDate: date, options: nil)
        date = calendar.dateByAddingUnit(.CalendarUnitMonth, value: months, toDate: date, options: nil)
        date = calendar.dateByAddingUnit(.CalendarUnitYear, value: years, toDate: date, options: nil)

Looks like dateByAddingUnit increments the month unit by months while dateByAddingComponents increments by the number of days in each of the next months.

No!
The problem is that operation on dates aren't commutative, for example choose as starting date 30 November

1 days = 1 December
1 month = 1 January

Or

1 month = 30 December
1 day = 31 of December


Generating the TLS certificate at runtime

Hi, Thank you very much for the libraries Socket.swift and HTTP.swift.
I need to generate the certificate used by the HTTP server (and thus the TLS.swift file used in Socket.swift) at runtime. That is to say I need to generate a new certificate everytime the app is launched and I start up the server.
Do you know of any way that this can be achieved on iOS?
I have searched far and wide and it seems most people end up shipping a copy of OpenSSL in their app to do this. I am guessing that if I ended up doing this, then I would need export compliance and sign off from the US government / Apple to do this.

Hey! I don't know if iOS has an api to generate self signed certificates, but googling it revealed this. It does not seem to be part of supported API.
However, it seems this library is able to generate certificates.

I am guessing that if I ended up doing this, then I would need export compliance and sign off from the US government / Apple to do this.

Interesting, why would you?

Thank you for the reply. I will take a look at the library and SO answer.
So as I understand it, when you submit an app to Apple they will ask you some questions regarding the use of encryption. This process has now changed and they require you to answer yes even if you use the Apple frameworks (i.e. ATS + HTTPS means you are using encryption). I am guessing that if I were to bundle OpenSSL with the app then I will have to go through more steps to get an export certificate (or whatever they call it) from the US government.


Integration test for hotrod on k8s

Which problem is this PR solving?

#6086

Description of the changes

How was this change tested?

Checklist

[ ] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
[ ] I have signed all commits
[ ] I have added unit tests for the new functionality
[ ] I have run lint and test steps successfully

for jaeger: make lint test
for jaeger-ui: yarn lint and yarn test

@yurishkuro i have made some changes please have a look


how to count and fetchall in on anonymus function

hi
right now i have this
 Route.where({ORIGIN: origin,DESTINATION:dest,DEP_DATE:date})
    .fetchAll()
    .then(function (user) {

var lookTime= user.pluck('LOOKED_TIME');
var min = _.min(lookTime);
var max = _.max(lookTime);

// res.json({data:user.pluck('id')});
    	});

and also i want to count the rows with same where clause, what is the best way to do this ?

@moeinrahimi
Have you tried FetchPage()


Documentation issue

pip3 install tb-rest-client in Python REST Client docs and README installs tb-rest-client with version up to 1.1.0: https://pypi.org/project/tb-rest-client/#history .
Meanwhile pip3 install tb-rest-client32 installs versions 1.1 or 1.2: https://pypi.org/project/tb-rest-client32/#history.
Which version of pip install ... is correct?
Do you support tb-rest-client32 too?

Hi @aopetrov86,

Which version of pip install ... is correct?
If you want to use the newest version you should use pip install tb-rest-client

Do you support tb-rest-client32 too?
No, tb-rest-client32 is only using for ThingsBoard v. 3.2.


failed on installing

much problem on installing.

update structure url git .
some gem can't download while using command bundle install.

im using debian.

Hi @screamolic. Are you following our installation guide?

yes. im following this.
https://gist.github.com/mjhea0/b6b58eefc38985380ff9

does huginn support post to blogger ?

i got another error with tutorial manual installation.
root@ubuntu-512mb-nyc3-01:/home/huginn/huginn# sudo bundle exec rake production:status
rake aborted!
Errno::ENOMEM: Cannot allocate memory - which
/home/huginn/huginn/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/kernel/agnostics.rb:7:in ' /home/huginn/huginn/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/kernel/agnostics.rb:7:in '
/home/huginn/huginn/lib/tasks/production.rake:11:in runit_installed' /home/huginn/huginn/lib/tasks/production.rake:27:in block (2 levels) in <top (required)>'
Tasks: TOP => production:status => production:check
(See full trace by running task with --trace)

Hi @screamolic,
this error indicates that your server ran out of RAM. We recommend at least 512MB RAM plus the same amount of swap.

thanks

I'm going to close this.  Please reopen if you have more questions!


test std more systematically

Now that rustc itself already runs std tests in CI, it wouldn't make sense to just do the exact same thing here. So let's see if we can test more.

   0.066767   error: multiple definitions of symbol `lgammaf_r`
  0.000046       --> /home/runner/work/miri-test-libstd/miri-test-libstd/rust-src-patched/library/std/src/f32.rs:1196:26
  0.000008        |
  0.000007   1196 |         let x = unsafe { cmath::lgammaf_r(self, &mut signgamp) };
  0.000005        |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ multiple definitions of symbol `lgammaf_r`
  0.000006        |

So, blocked by https://github.com/rust-lang/compiler-builtins/pull/586.

Now blocked on https://github.com/rust-lang/rust/pull/123719 and https://github.com/rust-lang/rust/pull/123891.

Now blocked on https://github.com/rust-lang/rust/pull/123957 and https://github.com/rust-lang/rust/pull/124007

Next blocker: https://github.com/rust-lang/miri/issues/3499

I think that failure is an instance of https://github.com/rust-lang/rust/issues/124409.

Next blocker: https://github.com/rust-lang/rust/issues/124411

Yay, finally. :)


Fix deleting app with no subscription

Fix issue where only happens when the user

create an app with subscription
delete the subscription
https://github.com/stolostron/backlog/issues/22110#issuecomment-1114894639

/lgtm


Privileges not opening on Ventura 13.2

Hi,
I have a config which was working with Monterey, deploying this recipe: com.github.rtrouton.pkg.privileges (so the package "Privileges-1.5.3.pkg" was pulled with AutoPkgr in June 2022 and working fine at that time). Now, if I deploy the same package on Ventura 13.2 Macs with Jamf, along with the config, Privileges.app won't open anymore.
If I check console I'm finding the following entry: "-[PersistentAppsSupport applicationQuit:] | for app:Privileges, _appTrackingState = 2".
No notification / error displayed, when trying to start the app; no difference, whether trying to start with a user-account with elevated or normal privileges.
Any ideas? Do I have to add a pppc entry for Ventura, which wasn't necessary for Monterey? I checked the documentation, didn't find anything relevant there so far.
Thanks in advance.

What is the configuration? Can you share it?
Also, does Privileges work when not using the configuration?

Yes, so I've only the key LimitToUser defined (xml below); but I do have the PrivilegesDemoter script running with some settings... Which works without issues, warns or ignores depending on the user, as defined in the script - so I wasn't expecting this to be the reason.
I'll set up a testmachine without any configuration, and then gradually add 1st the normal config, then Demoter script etc., to check this more in detail tomorrow, will post an update after.
`

LimitToUser
tadmin

`

Ok, deployed just the app, without any settings, and it's not opening either. Have a mcOS 13.0.1 machine, where it's working fine; guess it might be a 13.2 issue, or is it working without issues for others?
Also tested replacing the app with the one, downloaded straight from the latest release here, doesn't make a difference...

My shop has around 16,000 Macs running both Privileges 1.5.3 and macOS 13.2, so if there was an issue with the app not launching on macOS 13.2, we likely would be experiencing the same issue that you're seeing on at least some of them. We're not, so I suspect there's something else for the root cause.
If you haven't yet, you may want to build a new Privileges 1.5.3 installer and test that.

Ok, deployed just the app, without any settings, and it's not opening either. Have a mcOS 13.0.1 machine, where it's working fine; guess it might be a 13.2 issue, or is it working without issues for others?
Also tested replacing the app with the one, downloaded straight from the latest release here, doesn't make a difference...

Looks like it's a config issue after all; haven't got the time to check it in detail, in the middle of a rollout, but it's working with 13.2 now... Therefore closing this, thanks for the feedback.


Fairground content update

Can we remove the words ' The Mainnet Sims are live! Get involved and earn rewards on' from https://fairground.wtf/

The text should read 'Fairground, the official testnet of Vega.' and then the paragraph break and keep 'free from the risk of trading etc' the same

Last paragraph edit 'Participate in the mainnet sims to earn rewards for helping to find bugs and battle harden Vega.' to 'Participate in incentives to earn rewards for helping to find bugs and battle harden Vega.

Closed with https://github.com/vegaprotocol/fairground/pull/352


chore: optimize analytics studio

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Summary

delete preset event parameter _channel
filter and group support all user attributes
sort parameters by category
add prompt for funnel steps
modify embed placeholder when no data

Implementation highlights
(describe how the merge request does for feature changes, share the RFC link if it has)
Test checklist

[ ] add new test cases
[ ] all code changes are covered by unit tests
[ ] end-to-end tests

[ ] deploy web console with CloudFront + S3 + API gateway
[ ] deploy web console within VPC
[ ] deploy ingestion server

[ ] with MSK sink
[ ] with KDS sink
[ ] with S3 sink

[ ] deploy data processing
[ ] deploy data modeling

[ ] new Redshift Serverless
[ ] provisioned Redshift
[ ] Athena

[ ] deploy with reporting

Is it a breaking change

[ ] add parameters without default value in stack
[ ] introduce new service permission in stack
[ ] introduce new top level stack module

Miscellaneous

[ ] introduce new symbol link source file(s) to be shared among infra code, web console frontend, and web console backend

Remove last year in date time picker by the way...

done.


No arp client available, skip send gratuitous ARP

Hello,
I would like to refer again to the following request of mine:
https://github.com/cybertec-postgresql/vip-manager/issues/245
Unfortunately, I have not tested everything here. I have to agree with @sebastiangrill's last comment:
When a leader is changed, the new IP address is now assigned locally, but is not published on the network. This means that the system is not accessible for clients.
The system is only accessible via the VIP when I perform a manual arping.
Dec 27 11:40:23 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:23 IP address <IP_ADDRESS>/23 state is false, desired false
Dec 27 11:40:33 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:33 IP address <IP_ADDRESS>/23 state is false, desired false
Dec 27 11:40:43 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:43 IP address <IP_ADDRESS>/23 state is false, desired false
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 current leader from DCS:
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 current leader from DCS: scm-pgsql-01
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 IP address <IP_ADDRESS>/23 state is false, desired true
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 Problems with producing the arp client: no IPv4 address available for interface
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 Problems with producing the arp client: no IPv4 address available for interface
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 Couldn't create an Arp client: no IPv4 address available for interface
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 Configuring address <IP_ADDRESS>/23 on ens224
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 No arp client available, skip send gratuitous ARP
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 IP address <IP_ADDRESS>/23 state is true, desired true
Dec 27 11:40:53 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:40:53 IP address <IP_ADDRESS>/23 state is true, desired true
Dec 27 11:41:03 scm-pgsql-01 vip-manager[961]: 2024/12/27 11:41:03 IP address <IP_ADDRESS>/23 state is true, desired true

We use vip-manager 2.8.0 from the pgdg repository.
I hope for help.
Thank you very much
André

Hello.
Please, do not hesitate to submit pull request that fixes this issue


Equal Merit Zone Tie-break Tests

We require the functionality on our digital platform to create and run online tests for candidates, to support the JAC’s equal merit approach.
The use of the test will follow a decision made by the Selection and Character Committee (SCC) that there is zone of equal merit following the selection day stage, but members of the SCC cannot make a recommendation on the basis of ethnicity or gender.
This online test format will mirror the existing qualifying tests feature on the platform. The main difference being a new workflow needs to be created, allowing admins to select candidates for the EMZ tie-break online test at the selection day stage/end of the exercise process.
Admin

[ ] Admin users will be required to create the test after candidates have applied for an exercise and participated in selection days.

[ ] Admin users will need to allocate applicants to a test after selection days and SCC have taken place.

[ ] Admin users will be required to designate a day for and timeframe within which the test will take place.

[ ] Admin users will need to supply a scenario onscreen and related questions for candidates participating in the test.

[ ] Admin users will need to designate a time limit for the test and have the option to change time limits for candidates that require reasonable adjustments.

[ ] After candidates take the test, admin users will be required to download responses for scoring and processing.

[ ] Admin users will be required to allocate a result to each participating candidate and process them accordingly.

Apply

[ ] Once allocated to the test candidates will need to be able to see the ‘title’, ‘status’ and ‘start date’/time of the test in the ‘Online tests’ section of their profile.

[ ] The test will need to appear in the either the ‘Open’, ‘Future’ or ‘Past tabs within the ‘Online tests’ display.

[ ] On the day of the test candidates will need to be able to select a link to take them to an information/instruction page.

[ ] Once they have confirmed they have read and understood the instructions, candidates will start the test.

[ ] While completing the test, candidates will need to see a timer counting down at the top of their screen, to alert them of how much time they have left to take the test. When there is only a minute left on the test the candidates will need to be alerted of this.

[ ] As candidates will be answering in free text fields, an auto save function will be needed to ensure work is not lost.

[ ] Candidates will also need the ability to skip and come back to questions.

[ ] When candidates answer all questions, they need the ability to review them before submitting the test.

[ ] The candidates need to submit the test and receive confirmation that they have done so, or once the timer has run out the test needs to be auto-submitted and the candidate notified.

Having the test run on the platform is the best option for admin and end-users. Varies issues were exerienced with recent dry-run and live pilot using Google Forms.

Questions

Can 'under-representation' be defined and quantified in a formula?

Design Ideas:

Database

[x] EMZ tie-breaker tests should have an isTieBreaker flag against them to distinguish them from other Qualifying Tests. This will enable them to be reported on seperately if required.

Admin

[x] Since EM Tie-breakers are going to be very simliar to QTs, reuse existing QT code/components where possible
[x] The system should not allow an EMZ tie-breaker test to be created for an exercise that has no Qualifying Tests.
[x] The system should not allow an EMZ tie-breaker test to be created where the startDate or endDate of the test is outside of the Equal Marit Second Stage date-range for the exercise.
[x] The system should not allow an EMZ tie-breaker test to be opened/started while the Qualifying Tests for the exercise are still open.
[ ] When initialising QTs a qualifyingTestResponse document is created for each candidate. For tie-breakers these should should have an isTieBreaker flag set against them so they can be easily distinguished from the main QT responses.
[ ] EMZ Tie-breakers should not appear on existing QT reports (i.e., they will be on a new (seperate) report instead).

Apply

Since EM Tie-breakers are going to be very simliar to QTs, reuse existing QT code/components where possible
[ ]

Hello @HalcyonJAC I know that we ran through this in our meeting last week, but I have some additional answers for you:
Do exercises ever have multiple Qualifying Tests? - Yes, in that an exercise could hold a critical analysis and situational judge QT and then run a scenario QT after those as past of the shortlisting exercie.
Will exercises ever need to have multiple EMZ tie-breaker tests? - at this stage no. It is the one scenio test after selection days and the recommendation SCC meeting.
Will there be any other need (now or in the future) for tie-breaker tests, other than for Equal Merit purposes? Not to out knowledge.
Will the system ever need to be able to identify instances of "under-representation" itself or will this always be identified outside of the system (i.e. by the SCC)? This is all determined external to the platform
Further to the above, if the system needs to be able to identify "under-representation" itself, how can it be defined / quantified in a formula? **As above**

The requirements above state that the JAC will need to create tie-breaker test sometimes after candidates have applied for an exercise and participated in selection days. Has the option of creating the tie-breaker tests beforehand been considered?, i.e., to eliminate any potential bias in the test or to simply 'get ahead' in the workflow? ****It has been confirmed that: The test will only come into force if the SCC, at the final recommendation stage, cannot determine who to recommend should there be a zone of equal merit.  So it is not shortlisting tool, as all the candidates who use it are selectable. ****
In short this will only be used after selection days and not earlier in the exercise process.
How many candidates per EMZ tie-breaker test are anticipated? This may vary depending on the exercise, however I can confirm that is will be significantly less than the numbers that participate in QTs. It is more likely to be in low double or single digits.
Has the possibility of candidates applying for multiple roles been considered? The test will need to be associated with a particular exercise, so it shouldn't matter if the candidate allocated to a test is applying for other role. The exercises are seperate at that stage of the process.
If candidates could voice their preferences, i.e. 1st choice position, 2nd choice position, 3rd choice position, etc, would this help?
Do candidates ever turn an offer for a position down (i.e. in favour of another position)? This would potentially free-up a position for a EMZ candidate.

Candidates do withdraw from exercises. this would have to occur before the test takes place for another candidate to be allocated.
Are there any specific reporting requirements for EMZ tie-breaker tests? Do existing QT reports need extending? Do new reports need creating? Reports can replicate what is currently in place for scenario QTs.
Do you want EMZ Tie-breakers to be a new type of QT (and therefore listed with other QTs) or in a new section entirely? i.e. add an EMZ Tie-Breakers link under Tasks? The EMZ tests need to be their own task listed seperate to QTs.

Thanks again for getting answers (above) to my questions Kate. Very helpful :)
Here are my notes from our meeting today:

[ ] Allow a tie-breaker test to be created even if no QTs have been created for the exercise.

Note: Sometimes no QTs are created for an exercise, i.e., selection is done via phone interviews.

[ ] Tie-breakers will always be scenario tests. So, when creating a tie-breaker test the system should choose the 'Scenario' test type and prevent the user from choosing another test test type.

Note: Related to the above - I presume that dry-runs are still required as an option here.

[ ] When choosing candidates to include in a tie-breaker the Applications dropdown should only consider candidates that have the EMP flag set against them.

Apply portal

[x] Rename Qualifying tests to Online tests

Following a review with Kate...

[ ] Apply

[ ] Rename qualifying-test to online-test in URLs

Ticket not tested by prevous week's testers.
Sent to UTG on 29/06/21. Awaiting feedback.

I positive test confirmed. Sent to w/c 5 July testers for more feedback.

Unable to release this work due to merge conflicts. Awaiting action by devs.


Fix edition-changes links

Fixes #138

The reason I haven't checked out / merged this yet is that I'm not sure if the issue here is mdbook 0.1 vs 0.2. we have to make sure everything works with 0.2 before we can update, and only a few hours ago was it even possible to use 0.2 with this at all. So, sorry for the wait, but that's the root issue here.

I see.  I'm not sure why you say

only a few hours ago was it even possible to use 0.2 with this at all

because I have mdbook v0.2.3 installed locally and that's what I used to verify this.  So I'm confused.

The edition guide is currently built with 0.1.

On Feb 5, 2019, at 3:39 PM, Dale Wijnand<EMAIL_ADDRESS>wrote:
I see. I'm not sure why you say
only a few hours ago was it even possible to use 0.2 with this at all
because I have mdbook v0.2.3 installed locally and that's what I used to verify this. So I'm confused.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Sorry, even more context:
There are changes between how links work between mdbook 0.1 and 0.2. So, I believe that what exists right now works with 0.1, but since you built with 0.2, they seemed broken.
Upstream builds with 0.1. This updates to the 0.2 style, which works locally but would fail upstream.
Upstream got the ability to build with 0.2 last night.
Does that make sense?

On Feb 5, 2019, at 3:39 PM, Dale Wijnand<EMAIL_ADDRESS>wrote:
I see. I'm not sure why you say
only a few hours ago was it even possible to use 0.2 with this at all
because I have mdbook v0.2.3 installed locally and that's what I used to verify this. So I'm confused.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Yes, thank you, Steve.  Sorry for stealing focus.
This patch is trivial, I'll assume it'll be subsumed by the upcoming PR to upgrade the edition guide to mdbook 0.2.


Create fourth subpage (.html file)

Must be stored in a subfolder of the root folder

Have we decided on a fourth page? I kind of blanked on this one.

I'll make it an about page


Unexpected sensitivity of group normalisation results to batch size

System information

OS Platform and Distribution: Windows 10
TensorFlow version and how it was installed: 2.9.1 (binary, from pip)
TensorFlow-Addons version and how it was installed: 1.17.1 (binary, from pip)
Python version: 3.8
Is GPU used? (yes/no): no

Describe the bug
Results produced by group normalisation differ markedly depending on whether the batch size == 1 or not.
Code to reproduce the issue
The following code applies group normalisation along the last axis, first to a batch of 4 slices, then to individual slices, and finally to pairs of consecutive slices. In principle, the results obtained in each case should be the same, since group normalisation is not done along the batch dimension.
import tensorflow as tf
import tensorflow_addons as tfa

# Dimensions
b = 4
h = 600
w = 400
g = 3
c = g * 8

gn = tfa.layers.GroupNormalization(groups=g, axis=-1)
gn.build([None, None, None, c])

input = tf.random.stateless_uniform([b, h, w, c], seed=[1, 2])

# Apply group normalisation to the whole batch (4 slices) at once
output_b4 = gn.call(input)

# Apply group normalisation to each slice individually
output_0 = gn.call(input[0:1])
output_1 = gn.call(input[1:2])
output_2 = gn.call(input[2:3])
output_3 = gn.call(input[3:4])
output_b1 = tf.concat([output_0, output_1, output_2, output_3], axis=0)
tf.print("Batch size 1 vs batch size 4:", tf.reduce_max(tf.abs(output_b1 - output_b4)))

# Apply group normalisation to pairs of slices
output_01 = gn.call(input[0:2])
output_23 = gn.call(input[2:4])
output_b2 = tf.concat([output_01, output_23], axis=0)
tf.print("Batch size 2 vs batch size 4:", tf.reduce_max(tf.abs(output_b2 - output_b4)))

Output:
Batch size 1 vs batch size 4: 0.000871777534
Batch size 2 vs batch size 4: 2.38418579e-07

So the difference between results obtained for batch sizes 2 and 4 is on the order of machine precision, but that between results obtained for batch sizes 1 and 4 is three orders of magnitude larger.
Other info / logs
The difference is introduced by the call to tf.nn.moments() in GroupNormalization._apply_normalization(). The Reduce operations executed by moments() reshape the input tensor differently depending on whether its first dimension is 1 (and therefore it doesn't matter whether it is reduced over or not) or not (and therefore it must not be reduced over). The determines whether or not all elements with the same batch and group index are located next to each other in memory, and probably affects the order in which these elements are added together by Eigen::Tensor::reduce(). The difference in the final result is then a consequence of the non-associativity of floating-point addition.
The problem can be worked around by transposing the input tensor to a channels-first format, in which all axes not participating in the reduction (batch and group index) are located at the start of the axes list. However, it would be more user-friendly for this transpose to be done automatically inside GroupNormalization. If this sounds reasonable, I'm happy to open a PR patching GroupNormalization in this way.

Can you try to add a new test to cover this case?

Can you try to add a new test to cover this case?

Yes -- I've added a new test in #2746.


Message Sync: Deletes and New Adds (clarification)

In Firebase Database, I added a name but made a misstep and added the text afterward. I later deleted the test_message; however, only the name shows up in the messenger thread on the simulator.
How are deletes and new field adds handled in the Friendly Chat app?

You can find the source for this here, in the completed codelab code. The chat logic is extremely simplistic and only observes additions of new chat messages, capturing the snapshot at that time and adding it to an array of messages. This means if the message changes in the future or is removed, FriendlyChat will ignore it (since it's only listening to child added events, not child changed or child removed events).
In short, deletes and new field adds (modifications) aren't handled at all.

@morganchen12 thanks!


stats: Skip empty symbolic segments in stat_merger_fuzz_test

Commit Message: Found another corner-case that doesn't make sense, where a diff is registered.
Additional Description:
Risk Level: low
Testing: just the one fuzz test
Docs Changes:
Release Notes:
Platform Specific Features:

/retest


pull request for e2e test at 01/31/2017 12:56:12

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


About datasets download

Thanks for your awesome work! Can you provide the download link for ImageNet and AWA2 datasets?

Hi,
For ImageNet you may want to download from http://image-net.org/download-images.
For AwA2 it is https://cvml.ist.ac.at/AwA2/.

Thank you！


SAMZA-1719: Add caching support to table-api

This change adds caching support for Samza tables. This is especially
useful for remote table where the accesses can have high latency for
applications that can tolerate staleness. Caching is added in the form
of a composite table that wraps the actual table and a cache. We reuse
the ReadWriteTable interface for the cache. A simple Guava cache-based
table is provided in this change.
Original PR was inadvertently closed: https://github.com/apache/samza/pull/524

For previous review comments, please refer to: https://github.com/apache/samza/pull/524

Adding @weisong44 @vjagadish1989 for review


nixos/stage-1: set up /dev/fd

Otherwise, stage-2-init.sh will complain about not having access to
/dev/fd/62 as of systemd v246.
On IRC, flokli said:
15:14 <flokli> cole-h: hmmm... I could imagine some of the setup inside /dev has been moved into other parts of systemd
15:14 <flokli> And given we run systemd much later (outside initramfs only) it doesn't work properly here
15:17 <flokli> We probably don't invoke udev correctly

Motivation for this change
Fixes https://github.com/NixOS/nixpkgs/issues/97383.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I tested this by building and running a NixOS VM -- the warning is no longer printed.
cc @flokli + @worldofpeace
(This will need a backport, since we have systemd v246+ in 20.09.)

backported to 20.09 as a780c60f9f7.

Thanks, @flokli!


Merge https://github.com/kubernetes/cloud-provider-aws:master into master

Generated by Cloud Team Rebase Bot

/retest


Random characters at the end of some lines

https://i.alazymeme.com/EmbarrassedDampImage.png
Some lines have " /> at the end of them

Fixed in e0779b7953fa5ecd4c83c5a508c4f0eec772fba0


DOC: Added cual-id to projects page

Added cual-id to projects page fixes #5

Looks good, a couple copyediting comments


Venue is hardly " a short walk from the city center,"

On the venue page, it says that the venue is:

a short walk from the city center,

According to google maps, walking from the Talbot hotel to the Dublin Spire takes 1h and 47min: https://maps.app.goo.gl/pKheaLn8vUi9eoqs5
I'd suggest that this sentence be changed as it could be confusing to people who don't know Dublin very well.

Yep , working on that asap
thank you please
I will close this after I am done with the changes

Thanks for the changes @Darkbeast-glitch . However the page still mentions that the venue is "Just minutes from the bustling Silicon Docks" and from what I've checked there's an hour and a half of walking between the conference venue and the Sillicon docks.

oops, will check that again


add provisioning powershell and Stream Analytics jobdefinition.json

connects to #6
connects to #32
connects to #33
@bennage @francischeung Please review and merge

We need to rebase against the latest master. That's why AppVeyor is failing.

I get the following error:
VERBOSE: The [bennagensiot] namespace in the [Central US] region has been successfully created.
VERBOSE: Creating a NamespaceManager object for the [bennagensiot] namespace...
VERBOSE: NamespaceManager object for the [bennagensiot] namespace has been successfully created.
VERBOSE: Creating the [eventhub01] event hub in the [bennagensiot] namespace: PartitionCount=[16] MessageRetentionInDays=[7]...
New-Object : Cannot find an overload for "SharedAccessAuthorizationRule" and the argument count: "3".
At C:\dev\iot-journey\provision\Provision-EventHub.ps1:99 char:13
+     $Rule = New-Object -TypeName Microsoft.ServiceBus.Messaging.SharedAccessAuth ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [New-Object], MethodException
    + FullyQualifiedErrorId : ConstructorInvokedThrowException,Microsoft.PowerShell.Commands.NewObjectCommand

After updated to the lastest, I now see the following error:
New-AzureStreamAnalyticsJob : HTTP Status Code: BadRequest
Error Code: NoRegisteredProviderFound
Error Message: No registered resource provider found for location 'Central US' and API version '2014-12-01-preview' for type 'streamingjobs'. The supported api-versions and
locations are '2015-03-01-preview (centralus,westeurope,eastus2,northeurope,japaneast,westus,southeastasia,southcentralus,eastasia,japanwest,northcentralus,westeurope,centra
lus,eastus2,northeurope,japaneast,westus,southeastasia,southcentralus,eastasia,japanwest,northcentralus,); 2015-04-01 (centralus,westeurope,eastus2,northeurope,japaneast,wes
tus,southeastasia,southcentralus,eastasia,japanwest,northcentralus,westeurope,centralus,eastus2,northeurope,japaneast,westus,southeastasia,southcentralus,eastasia,japanwest,
northcentralus,); 2014-04-01 (,eastus,eastus2,northcentralus,northeurope,westeurope,brazilsouth,westus,centralus,southcentralus,japaneast,japanwest,eastasia,southeastasia,ea
stus,eastus2,northcentralus,northeurope,westeurope,brazilsouth,westus,centralus,southcentralus,japaneast,japanwest,eastasia,southeastasia)'.
Request Id: 430e70cb-a899-4b38-bce7-b78071aa72eb
Timestamp (Utc):05/21/2015 22:55:01
At C:\dev\iot-journey\provision\Provision-StreamAnalyticsJob.ps1:100 char:1
+ New-AzureStreamAnalyticsJob -ResourceGroupName $ResourceGroupName  -File $TempFi ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [New-AzureStreamAnalyticsJob], CloudException
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.StreamAnalytics.NewAzureStreamAnalyticsJobCommand

Regarding this error:
New-AzureStreamAnalyticsJob : HTTP Status Code: NotFound
Error Code: ResourceGroupNotFound
Error Message: Resource group 'StreamAnalytics-Default-Central-US' could not be found.
Request Id: 3bcbdfae-aa1d-414b-8cf1-59c75bb9bc32
Timestamp (Utc):05/22/2015 00:54:39
At C:\dev\iot-journey\provision\Provision-StreamAnalyticsJob.ps1:100 char:1
+ New-AzureStreamAnalyticsJob -ResourceGroupName $ResourceGroupName  -File $TempFi ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [New-AzureStreamAnalyticsJob], CloudException
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.StreamAnalytics.NewAzureStreamAnalyticsJobCommand

We believe that we need to explicitly create a resource group.

create the resource group in the master script?
name the resource group something like mspnp-iot-journey-sample

[ ] remove the temporary file in a try/ctach/finally


feat: support Web Workers by using the global btoa

Fix #268

Tests are failing. Maybe we could check globalThis.btoa instead?

@antfu I think the tests should be passing now. Thanks for the feedback!

Hooray! Thank you so much.


refactor(axios): export axios types

resolves #639
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: #639
Currently, to have axios types in the NestJS application, we should add axios as a dependency, which can lead to a mismatched version between the 2 libraries.
What is the new behavior?
It has exported the useful axios types to resolve the explained issue.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

I'm going to move axios to be a peer dependency instead


Can't I request the server in another non-English language, like Korean?

Describe the feature
I'm trying to send non-english string to the server by Using ChatGPTUnofficialProxyAPI, but It doesn't work. It seems it has encoding error.
Here is my code:
async function main() {
  const api = new ChatGPTUnofficialProxyAPI({

    accessToken: (my accesstoken),
    debug: false
  })

  const prompt = "고양이에 대한 시를 써줘.";

  let res = await oraPromise(api.sendMessage(prompt), {
    text: prompt
  })

  console.log('\n' + res.text + '\n')

  return 0;
}

main();

then, I receive this:
[Running] node "d:\suhang\lib\js\main.js"
- %EF%BF%BD%D1%B1%EF%BF%BD
√ %EF%BF%BD%D1%B1%EF%BF%BD

I'm sorry, but I'm not sure what you're trying to communicate with "%EF%BF%BD%D1%B1%EF%BF%BD". Could you please provide me with more context or rephrase your question?

[Done] exited with code=0 in 4.81 seconds

Is there a way to send it in different languages?

@sbjeon08 it looks like maybe the encoding of your text editor isn't set properly since Node.js is also printing out the incorrectly formatted string.

I just tested this example and it works on my end:

It works! Thanks :)


Make restore command check if dependencies and lock file are in sync

This may be an issue in Paket.VisualStudio in fact so i'll post in both and well see where it goes
Description
Open a project with changes on Paket.dependencies does not impact paket.lock
The Idea should be :
When you get the Latest source control version, open it and rebuild it (the solution).
You should be using the "dependencies" version, even if it means updation paket.lock
(see repro step)
Repro steps
Please provide the steps required to reproduce the problem

Create a solution that use paket and where paket.dependencies have something like :
nuget MyLib 1.0

paket install

The paket.lock is created, Build your solution and the close Visual Studio
2. To simulation a change on SourceControl open your "paket.dependencies" and change it :
nuget MyLib 2.0

Re open your solution in Visual Studio Try to rebuild all ...
You'll see that "paket.lock" did not took the v2.0 of the lib but is still using 1.0
But paket.dependencies indicate v2.0

Expected behavior
Please provide a description of the behavior you expect.
Actual behavior
Known workarounds
Force "Install manually" when you open the solution (it's a bit f*** up right ?)
Related information

Operating system : Win10
Release 3.1.9
Lastest Vs Extension also
.NET Framework 4.5.x

Paket.lock is not updated after changes in paket.dependencies

That's not going to happen automatically. The lock file is the single truth and the most important file in the system. All changes will remain explicit via install or update commands.
I change the title of this issue since I think we can make restore check if something changed in the deps file. If that happend then we can let restore fail. I think this is a sensible way to detect inconsistencies.

@forki you mean deps vs lock file inconsistency?

yes.

I do agree ... almost all points here
May be the "restore" should Warn (with an option "as error") is it detect that "dependencies" file is not synch with "lock" file
so when you "paket restore" at least in your shell or IDE you have some tips to let you know something is probably bad
Just like NPM does when you "NPM install" and tries to helps you when you're using deprecated version

No. Paket has outdated for that. We don't want to do version checking and stuff like that when doing a paket restore.

No, I don't want to do version checking like outdated does.
I would just use the internal "smart install" logic and perform the same test that install does before it starts resolver.  I mean install command only runs resolver for a given group if it finds a inconsistency between lock file and deps file for that group. We could use this and let restroe fail if that's the case. We would not need any webrequests for that check.

Well then is there an existing command to run this check ?
So that it will break if there's sync issue between lock & deps

I mean, paket solves issue about multi "packages" version in multiple "packages.config" but is not smart enought to tell (or let you know if there's a command for that) if the 2 file of paket "lock" and "dependencies" have different version.
It's hard to defend ...
"We fix the multipe version issue, but know you're not sure of the version you use depending on the file you're looking at"

Well, that seems to be to be a bit of user education.  If you as a user change the requirements for a package (like adding the 2.0 version constraint that you did above) you must tell paket to recompute the dependency graph.  This works the same for when you add a new package, remove a package, change an install option (like target framework version).

@tebeco Please read up here: http://fsprojects.github.io/Paket/dependencies-file.html

you're not sure of the version you use depending on the file you're looking at

You need to look in to the lock file. That's the file that fixes all versions and contains the valid resolution.

So in the latest Paket 3.2 alpha we have the following check in paket restore:

We check if there are any changes in paket.dependencies after the last paket install/update
If we detect that paket.lock and paket.dependencies are out of sync we throw an error:

So now a spark shine,
Do you think having a new feature (that is disable by default) in the paket.VisualStudio to run this the first time the solution is opened ?
So we could be able to warn the user one way or another ?
Or in paket.config (or both)
Or as error ? (just like Warn as error does allready ?)
All the pipeline would be the same as today, it would just give hints about potential technical debts

Paket.VisualStuio will fail on restore with the correct message. I think that's fine and will tell you that something is fucky.

Ok, but please make that opt-out or opt-in. I actually depend on this behavior from time to time when debugging hard to find dependency issues or to find when an incompatibility was introduced. What I do: I update the paket.lock file by hand (i know this is evil) to force paket to install some specific versions (even when the new dependency graph is not even valid). Please let me keep doing this as it helps a lot from time to time. It is easier than updating paket.dependencies and putting == everywhere until I get what I want. Like paket restore --force?

Your use case is still possible as long as the manually changed versions
don't violate the original restrictions.
But you are right we definitely should add a parameter which just brutally
uses the lock file. Ideas for names?
On Jun 23, 2016 8:11 PM, "Matthias Dittrich"<EMAIL_ADDRESS>wrote:

Ok, but please make that opt-out or opt-in. I actually depend on this
behavior from time to time when debugging hard to find dependency issues or
to find when an incompatibility was introduced. What I do: I update the
paket.lock file by hand (i know this is evil) to force paket to install
some specific versions (even when the new dependency graph is not even
valid). Please let me keep doing this as it helps a lot from time to time.
It is easier than updating paket.dependencies and putting == everywhere
until I get what I want. Like paket restore --force?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/1750#issuecomment-228134919,
or mute the thread
https://github.com/notifications/unsubscribe/AADgNEkfJ3SjjFlTSbeeXoLa3VjTtWRIks5qOsxDgaJpZM4I8w6o
.

Agreed, I've done this from time to time as well.

@forki -unsafe? -manualLock?-ignoreDepsFile?

(also we need to give people a way out for when our changedetection is
buggy)
On Jun 23, 2016 8:30 PM, "Isaac Abraham"<EMAIL_ADDRESS>wrote:

Agreed, I've done this from time to time as well.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/1750#issuecomment-228141789,
or mute the thread
https://github.com/notifications/unsubscribe/AADgNN3oYEPeyCzr74xhuztTBD9RVgqUks5qOtDWgaJpZM4I8w6o
.

I think it should be something around "ignore checks". Or we reuse - f
On Jun 23, 2016 8:33 PM, "Steffen Forkmann"<EMAIL_ADDRESS>wrote:

(also we need to give people a way out for when our changedetection is
buggy)
On Jun 23, 2016 8:30 PM, "Isaac Abraham"<EMAIL_ADDRESS>wrote:

Agreed, I've done this from time to time as well.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/1750#issuecomment-228141789,
or mute the thread
https://github.com/notifications/unsubscribe/AADgNN3oYEPeyCzr74xhuztTBD9RVgqUks5qOtDWgaJpZM4I8w6o
.

I suggested --force above but --ignoreDeps (or something like it) might be better. There possibly are use cases where people don't want to have a deps file (because it is managed somewhere else or whatever)

Thinking about it overloading -f for multiple things is probably not a good thing (or at least have the other parameters as well and document like "-f shortcut for --ignore-dependencies-file ... --... ")

@tebeco  What nobody has said jet: You should really add the lockfile to your source control if it isn't (and your report sounds like it isn't). That way you get exactly the same version as the one running paket update or paket install. That's really the way to use paket. There is never a reason to not have the lockfile added to your source control. Plus what @baronfel has already said. You cannot expect paket to do something differently when neither paket install nor paket update has been called.
That's exactly the advantage paket tries to deliver.
This issue shows that throwing an error is probably the better default behavior (but imho its wrong because restore should not need to read paket.dependencies).

going with '--ignore-checks'

Just to weight in, except if there are hidden consequences (I think there is really any risk but i'm thinking about edge cases like https://blogs.msdn.microsoft.com/oldnewthing/20110504-00/?p=10743/ ) the principle seem right to me.
It would stop bad situations on the build server right at the start when paket restore is launched instead of later on a random developer machine when paket install is needed.

Hmmh, I get that very error message after the automatic update to paket <IP_ADDRESS>.
But I can't get out of it. No install, update, clear-cache or other commands seem to fix it. So what is the best way to solve it? Delete the lock file in that case?
I have some version constraints for transitive dependencies in there, but not to complex ones.

Deleting the lock file and doing an install afterwards produced the same lock file again. And I have the error message as well. I am a bit clueless how to resolve the problem.
Are there changes in the package resolution strategy that could cause the error message as well?

Can you please send me the lock file and deps file?
On Jun 24, 2016 5:21 PM, "Martin Bohring"<EMAIL_ADDRESS>wrote:

Deleting the lock file and doing an install afterwards produced the same
lock file again. And I have the error message as well. I am a bit clueless
how to resolve the problem.
Are there changes in the package resolution strategy that could cause the
error message as well?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/1750#issuecomment-228375207,
or mute the thread
https://github.com/notifications/unsubscribe/AADgNP4dVxbn_XsmkPHcvvnNn7QUrFxuks5qO_YKgaJpZM4I8w6o
.

Wow that is quick :+1:
You can find the lock and deps file at:
https://github.com/Martin-Bohring/fixieSpec
Just trying out now, if AppVeyor can build it.

Well AppVeyor creates the same error message and I think I have package caching disabled.
https://ci.appveyor.com/project/Martin-Bohring/fixiespec/build/<IP_ADDRESS>

please retry with latest version.

Wow, that is a turn around time like magic. :100:
Works know.
What was the issue?

auto-detect was triggering the outdated check

I see framwork auto detection

I am afraid something is broken for my projects. When I tried to rebuild previous successfully build projects in appveyor or travis, I get the sync error. I have to delete and rebuild the lock file push the changed file and it is fixed. But I have quite a lot or projects. So, I am not really happy with this.

This is why I asked of visual studio extension could do a force install when the solution is opened (juste like nuget does)
And let it optional in settings ;)

But I do have a paket.lock file in my repository that should be in sync with dependencies as it is the direct result of a paket install. Still it's not working and also, I cannot fix this.

This is the most breaking change ever. Now every succeeded build is failed if I try to build it again. Why don't you go with a --check or give error only when doing paket install, not restore?

yes sorry.
I changed ti to print a warning instead of failing the restore. I will continue to fix the out-of-date check.
Sorry for causing so much trouble,


Update sbt-native-packager to 1.7.0

Updates com.typesafe.sbt:sbt-native-packager from 1.4.1 to 1.7.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe.sbt", artifactId = "sbt-native-packager" } ]

labels: sbt-plugin-update, semver-minor

Codecov Report

Merging #30 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #30   +/-   ##
=======================================
  Coverage   78.58%   78.58%
=======================================
  Files          21       21
  Lines        1130     1130
  Branches       18       18
=======================================
  Hits          888      888
  Misses        242      242

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b2bfde4...7d9de74. Read the comment docs.


PowerShellEditorServices is v1.10.1 (6 years old)

I have noticed that this plugin itself receives relatively regular updates (looks like once a month at least for the last few months), but not the bundled packages. The PowerShellEditorServices package included has a release date from v1.10.1: Dec 2018. The current version is v3.17.0: Jan 2024.
You will have to forgive me, as I am not very familiar (at all) with Jetbrains plugins or what they require when integrating an external language/service, but I was wondering if there was a specific reason for this  (Ex. Does the PSES library require modification, or there are compatibility issues?) or just no one has got around to it?
I am guessing that it must not be as simple as swapping out the old library and replacing it with the new version?
Thanks,
-MH

Ah, actually, this has already been requested, and I even tried that, and it failed (see the comments) :(
See #51. I'm closing this report as a duplicate.

I understand.
The main reason I bring it up, is that overall functionality on my end is broken (presumably because of the age of the library) when using relatively recent functionality.

Example Code in Rider

Example Code in VSCode

The same code is recognized as valid in both VSCode with the powershell plugin, as well as neovim when using an updated version PowerShellEditorServices (as seen by the reference count, lack of error, etc in the second image).
In Rider, everything below the enum declaration is broken, unfortunately, making it unusable for code that uses newer features.

Note that highlighting in the plugin doesn't use PSES, so it is unlikely to be broken because of that. We have quite a few issues with certain modern (and often old as well) snippets and language features not being properly recognized, this all is in my current backlog as well.


Extension failed to activate due to error: Cannot read property 'length' of undefined

After installing the Python extension in VSCode, I'm getting the following error message.
Error Python Extension: 2019-11-17 07:49:10: extension activation failed [TypeError: Cannot read property 'length' of undefined	at m.update (c:\Users\[redacted]\.vscode\extensions\ms-python.python-2019.10.44104\out\client\extension.js:75

Note: Restarting VSCode, after installing the extension allows the extension to load as expected.
Environment data

VS Code version: 1.40.1 (system setup)
Extension version (available under the Extensions sidebar): 2019.10.44104
OS and version: Windows_NT x64 10.0.19023
Python version (& distribution if applicable, e.g. Anaconda): Anaconda, Python 3.7
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions: N/A
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): N/A

Expected behaviour
Python extension loads
Actual behaviour
Python extension fails to activate.
Steps to reproduce:

Start VSCode
Install Python extension

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
No output generated

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
Error Python Extension: 2019-11-17 07:49:10: extension activation failed [TypeError: Cannot read property 'length' of undefined	at m.update (c:\Users\[redacted]\.vscode\extensions\ms-python.python-2019.10.44104\out\client\extension.js:75

@wmeints If this occurs again, can you do the following to get better debugging info:

Turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)

Toggle debugger tools under Help:

Copy the output from console tab and share it with us:

With the current details it is not possible to narrow down the issue, since the extension.js is minified.

@karthiknadig Let me enable the debugging information and reproduce the issue. I'll try to get that done this morning

@karthiknadig Okay, we've got a bit of a problem. Because the extension won't activate after installing it, I can't activate the source maps. When I execute the command > Python: Enable Source Map Support For Extension Debugging, I get the following error:

So, at the moment I can only give you the minimized version, sadly. Unless there's another way to load the source maps.

@wmeints can you provide a list of extensions you have installed?
you could run this and get the result:
dir %USERPROFILE%\.vscode\extensions.
If that command did't work, you can find the extensions folder like using the Extensions: Open Extensions folder command, via the command pallet.

Let me check later today, I don't have my laptop with me at the moment.

@DonJayamanne You said you had ideas on how to get to the correct line even in the minified version?

Sorry for the (very) late response. Here's the list of extensions I'm running:
Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----        19-11-2019     09:13                4ops.terraform-0.1.7
d-----         30-6-2019     19:06                aureliaeffect.aurelia-1.0.3
d-----        26-10-2019     11:25                axetroy.vscode-changelog-generator-0.4.1
d-----         24-5-2019     10:42                batisteo.vscode-django-0.19.0
d-----         30-6-2019     19:06                behzad88.aurelia-1.2.2
d-----         30-6-2019     19:06                christian-kohler.path-intellisense-1.4.2
d-----         22-8-2019     09:19                dbaeumer.vscode-eslint-1.9.1
d-----         26-4-2019     12:38                dragos.scala-lsp-0.2.3
d-----        21-10-2019     19:23                editorconfig.editorconfig-0.14.2
d-----        27-11-2019     14:37                esbenp.prettier-vscode-3.11.0
d-----        20-11-2019     08:11                humao.rest-client-0.23.0
d-----         27-8-2019     19:37                ionide.ionide-fake-1.2.3
d-----        25-11-2019     13:45                ionide.ionide-fsharp-4.3.2
d-----         27-8-2019     19:37                ionide.ionide-paket-1.12.0
d-----        21-11-2019     19:33                jebbs.plantuml-2.13.5
d-----        19-11-2019     09:13                johnpapa.angular2-8.2.0
d-----        11-11-2019     15:49                johnpapa.vscode-peacock-3.2.0
d-----         31-7-2019     08:50                johnpapa.winteriscoming-1.3.0
d-----         16-6-2019     20:34                k--kato.docomment-0.1.8
d-----         9-11-2019     19:23                lextudio.restructuredtext-116.0.0
d-----        10-10-2019     10:55                marvhen.reflow-markdown-2.1.0
d-----        18-11-2019     09:10                mike-lischke.vscode-antlr4-2.2.3
d-----         23-6-2019     12:07                mjmcloug.vscode-elixir-1.1.0
d-----        11-11-2019     15:58                ms-azure-devops.azure-pipelines-1.157.4
d-----         5-11-2019     05:36                ms-azuretools.vscode-azurefunctions-0.20.0
d-----         9-11-2019     19:23                ms-azuretools.vscode-azureterraform-0.3.0
d-----        27-11-2019     07:55                ms-azuretools.vscode-cosmosdb-0.11.0
d-----         5-11-2019     05:36                ms-azuretools.vscode-docker-0.8.2
d-----         2-12-2019     14:19                ms-kubernetes-tools.vscode-kubernetes-tools-1.0.9
d-----        24-11-2019     19:57                ms-python.python-2019.11.50794
d-----         29-6-2019     19:17                ms-python.python-2019.5.18875
d-----        16-11-2019     17:30                ms-vscode-remote.remote-containers-0.83.1
d-----        16-11-2019     17:30                ms-vscode-remote.remote-wsl-0.40.3
d-----        31-10-2019     09:30                ms-vscode.azure-account-0.8.7
d-----        31-10-2019     09:30                ms-vscode.cpptools-0.26.1
d-----        24-11-2019     20:01                ms-vscode.csharp-1.21.8
d-----        25-11-2019     14:06                ms-vscode.powershell-2019.11.0
d-----        12-11-2019     16:06                ms-vscode.vscode-typescript-tslint-plugin-1.2.3
d-----         2-12-2019     14:19                msjsdiag.debugger-for-chrome-4.12.2
d-----         25-7-2019     13:35                orta.vscode-jest-3.0.2
d-----         13-9-2019     20:11                paolodellepiane.fantomas-fmt-0.0.22
d-----        24-11-2019     19:57                pkief.material-icon-theme-3.9.2
d-----        27-11-2019     14:37                prettier.prettier-vscode-3.11.0
d-----        17-11-2019     07:39                redhat.vscode-yaml-0.6.1
d-----         24-5-2019     10:50                shamanu4.django-intellisense-0.0.2
d-----         30-6-2019     19:06                steoates.autoimport-1.5.3
d-----         29-6-2019     19:17                vscode-icons-team.vscode-icons-8.7.0

interesting fact: I've got two versions of the python extension.
d-----        24-11-2019     19:57                ms-python.python-2019.11.50794
d-----         29-6-2019     19:17                ms-python.python-2019.5.18875

@karthiknadig Yep, when I tried the same thing on a computer that was clean, it worked.
I cleaned up my machine and now it's working there as well.


[fix][broker] Return if AbstractDispatcherSingleActiveConsumer closed

Motivation
We should  disconect the consumer and return if AbstractDispatcherSingleActiveConsumer is closed
Modifications
Return after consumer disconnect
Verifying this change

[x] Make sure that the change passes the CI checks.

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository: https://github.com/AnonHxy/pulsar/pull/33

@AnonHxy
Could you write a test?

PersistentStickyKeyDispatcherMultipleConsumers
Good catch @poorbarcode , PTAL again

Codecov Report

Merging #19934 (189b1e3) into master (1e44ba1) will increase coverage by 48.44%.
The diff coverage is 85.55%.

@@              Coverage Diff              @@
##             master   #19934       +/-   ##
=============================================
+ Coverage     24.42%   72.87%   +48.44%
- Complexity      291    31615    +31324
=============================================
  Files          1603     1861      +258
  Lines        124343   137366    +13023
  Branches      13571    15117     +1546
=============================================
+ Hits          30369   100101    +69732
+ Misses        89490    29323    -60167
- Partials       4484     7942     +3458

Flag
Coverage Δ

inttests
24.34% <18.88%> (-0.08%)
:arrow_down:

systests
25.07% <18.88%> (?)

unittests
72.15% <85.55%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...extensions/reporter/TopBundleLoadDataReporter.java
88.88% <ø> (+88.88%)
:arrow_up:

...tent/NonPersistentDispatcherMultipleConsumers.java
71.60% <ø> (+71.60%)
:arrow_up:

...dbalance/extensions/scheduler/TransferShedder.java
81.43% <50.00%> (+81.43%)
:arrow_up:

...ar/metadata/coordination/impl/LockManagerImpl.java
89.47% <71.42%> (+31.57%)
:arrow_up:

...metadata/coordination/impl/LeaderElectionImpl.java
77.56% <75.00%> (+24.66%)
:arrow_up:

...java/org/apache/pulsar/common/util/FutureUtil.java
80.55% <76.92%> (+50.02%)
:arrow_up:

...ker/loadbalance/extensions/models/TopKBundles.java
90.78% <87.17%> (+90.78%)
:arrow_up:

...org/apache/pulsar/broker/ServiceConfiguration.java
99.37% <100.00%> (+1.46%)
:arrow_up:

...nsions/policies/AntiAffinityGroupPolicyHelper.java
90.62% <100.00%> (+90.62%)
:arrow_up:

...ervice/AbstractDispatcherSingleActiveConsumer.java
92.37% <100.00%> (+24.85%)
:arrow_up:

... and 2 more

... and 1568 files with indirect coverage changes

As discussed on the mailing list https://lists.apache.org/thread/w4jzk27qhtosgsz7l9bmhf1t7o9mxjhp, there is no plan to release 2.9.6, so I am going to remove the release/2.9.6 label