AddStandardResilienceHandler and healthchecks result in noisy logs with TestHost

The default integration test template calls ConfigureHttpClientDefaults with AddStandardResilienceHandler
https://github.com/dotnet/aspire/blob/b45b0461b789c64d1b1dfa421f63e2e7a09540af/src/Aspire.ProjectTemplates/templates/aspire-nunit/9.0/IntegrationTest1.cs#L19-L22
This however produces a lot of noise in 9.0 with the built in health checks this ends up producing a lot of number of distracting messages in the test host. e.g.
    info: Polly[3]
      Execution attempt. Source: '-standard//Standard-Retry', Operation Key: '', Result: '200', Handled: 'False', Attempt: '0', Execution Time: 1061.2159ms

Are these resiliency headers still a good recommendation for tests in 9.0?  In 8.x before healthchecks & readiness, request resiliency was highly needed to make sure the apps had started up properly, but with 9.0's health check support?  (Particularly if the sample tests replace WaitForResourceAsync with WaitForResourceHealthyAsync)

Here is a slightly more egregious example of noise - this comes from the build server where it's pulling container images for the first time, and so has a lot more waiting (and thus failing of health checks)
info: Aspire.Hosting.DistributedApplication[0]
      Aspire version: 9.0.0+01ed51919f8df692ececce51048a140615dc759d
info: Aspire.Hosting.DistributedApplication[0]
      Distributed application starting.
info: Aspire.Hosting.DistributedApplication[0]
      Application host directory is: /mnt/vss/_work/1/s/src/REDACTED
warn: Polly[3]
      Execution attempt. Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.', Handled: 'True', Attempt: '0', Execution Time: 31.3691ms
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.Net.Http.HttpIOException: The response ended prematurely. (ResponseEnded)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[0]
      Resilience event occurred. EventName: 'OnRetry', Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.'
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.Net.Http.HttpIOException: The response ended prematurely. (ResponseEnded)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[3]
      Execution attempt. Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.', Handled: 'True', Attempt: '1', Execution Time: 5.8369ms
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer.
       ---> System.Net.Sockets.SocketException (104): Connection reset by peer
         --- End of inner exception stack trace ---
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
         at System.Net.Http.HttpConnection.InitialFillAsync(Boolean async)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[0]
      Resilience event occurred. EventName: 'OnRetry', Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.'
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer.
       ---> System.Net.Sockets.SocketException (104): Connection reset by peer
         --- End of inner exception stack trace ---
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
         at System.Net.Http.HttpConnection.InitialFillAsync(Boolean async)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[3]
      Execution attempt. Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.', Handled: 'True', Attempt: '2', Execution Time: 3.811ms
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.Net.Http.HttpIOException: The response ended prematurely. (ResponseEnded)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[0]
      Resilience event occurred. EventName: 'OnRetry', Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.'
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.Net.Http.HttpIOException: The response ended prematurely. (ResponseEnded)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[3]
      Execution attempt. Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.', Handled: 'True', Attempt: '0', Execution Time: 3.8928ms
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.Net.Http.HttpIOException: The response ended prematurely. (ResponseEnded)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[0]
      Resilience event occurred. EventName: 'OnRetry', Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.'
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.Net.Http.HttpIOException: The response ended prematurely. (ResponseEnded)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[3]
      Execution attempt. Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.', Handled: 'True', Attempt: '1', Execution Time: 3.4253ms
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.Net.Http.HttpIOException: The response ended prematurely. (ResponseEnded)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[0]
      Resilience event occurred. EventName: 'OnRetry', Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.'
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.Net.Http.HttpIOException: The response ended prematurely. (ResponseEnded)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[3]
      Execution attempt. Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.', Handled: 'True', Attempt: '2', Execution Time: 4.3873ms
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer.
       ---> System.Net.Sockets.SocketException (104): Connection reset by peer
         --- End of inner exception stack trace ---
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
         at System.Net.Http.HttpConnection.InitialFillAsync(Boolean async)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[0]
      Resilience event occurred. EventName: 'OnRetry', Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.'
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer.
       ---> System.Net.Sockets.SocketException (104): Connection reset by peer
         --- End of inner exception stack trace ---
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
         at System.Net.Http.HttpConnection.InitialFillAsync(Boolean async)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[3]
      Execution attempt. Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.', Handled: 'True', Attempt: '0', Execution Time: 120.1197ms
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.Net.Http.HttpIOException: The response ended prematurely. (ResponseEnded)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[0]
      Resilience event occurred. EventName: 'OnRetry', Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.'
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.Net.Http.HttpIOException: The response ended prematurely. (ResponseEnded)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
info: Polly[3]
      Execution attempt. Source: '-standard//Standard-Retry', Operation Key: '', Result: '200', Handled: 'False', Attempt: '1', Execution Time: 78.4977ms
info: Polly[3]
      Execution attempt. Source: '-standard//Standard-Retry', Operation Key: '', Result: '200', Handled: 'False', Attempt: '0', Execution Time: 3.4084ms
warn: Polly[3]
      Execution attempt. Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.', Handled: 'True', Attempt: '0', Execution Time: 2.4967ms
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.Net.Http.HttpIOException: The response ended prematurely. (ResponseEnded)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[0]
      Resilience event occurred. EventName: 'OnRetry', Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.'
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.Net.Http.HttpIOException: The response ended prematurely. (ResponseEnded)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[3]
      Execution attempt. Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.', Handled: 'True', Attempt: '1', Execution Time: 3.071ms
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer.
       ---> System.Net.Sockets.SocketException (104): Connection reset by peer
         --- End of inner exception stack trace ---
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
         at System.Net.Http.HttpConnection.InitialFillAsync(Boolean async)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[0]
      Resilience event occurred. EventName: 'OnRetry', Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.'
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer.
       ---> System.Net.Sockets.SocketException (104): Connection reset by peer
         --- End of inner exception stack trace ---
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
         at System.Net.Http.HttpConnection.InitialFillAsync(Boolean async)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[3]
      Execution attempt. Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.', Handled: 'True', Attempt: '2', Execution Time: 1.1415ms
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer.
       ---> System.Net.Sockets.SocketException (104): Connection reset by peer
         --- End of inner exception stack trace ---
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
         at System.Net.Http.HttpConnection.InitialFillAsync(Boolean async)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
warn: Polly[0]
      Resilience event occurred. EventName: 'OnRetry', Source: '-standard//Standard-Retry', Operation Key: '', Result: 'An error occurred while sending the request.'
      System.Net.Http.HttpRequestException: An error occurred while sending the request.
       ---> System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer.
       ---> System.Net.Sockets.SocketException (104): Connection reset by peer
         --- End of inner exception stack trace ---
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
         at System.Net.Http.HttpConnection.InitialFillAsync(Boolean async)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
info: Polly[3]
      Execution attempt. Source: '-standard//Standard-Retry', Operation Key: '', Result: 'The operation was canceled.', Handled: 'False', Attempt: '3', Execution Time: 674.6852ms
      System.Threading.Tasks.TaskCanceledException: The operation was canceled.
       ---> System.IO.IOException: Unable to read data from the transport connection: Operation canceled.
       ---> System.Net.Sockets.SocketException (125): Operation canceled
         --- End of inner exception stack trace ---
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
         at System.Net.Http.HttpConnection.InitialFillAsync(Boolean async)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
info: Polly[3]
      Execution attempt. Source: '-standard//Standard-Retry', Operation Key: '', Result: '200', Handled: 'False', Attempt: '0', Execution Time: 7036.2245ms
info: REDACTED[0]
      1: 2024-11-25T11:07:15.1032400Z Waiting for resource 'REDACTED' to complete.
info: REDACTED[0]
      2: 2024-11-25T11:07:15.1085103Z Waiting for resource 'REDACTED' to enter the 'Running' state.
info: REDACTED[0]
      3: 2024-11-25T11:07:28.0533651Z Waiting for resource 'REDACTED' to become healthy.
info: REDACTED[0]
      4: 2024-11-25T11:07:39.4573760Z Finished waiting for resource 'REDACTED'.
info: REDACTED[0]
      5: 2024-11-25T11:08:05.2686739Z Finished waiting for resource 'REDACTED'.
info: REDACTED[0]
      1: 2024-11-25T11:07:15.1112952Z Waiting for resource ''REDACTED'' to enter the 'Running' state.
info: REDACTED[0]
      2: 2024-11-25T11:07:15.1113495Z Waiting for resource 'REDACTED' to enter the 'Running' state.
info: REDACTED[0]
      3: 2024-11-25T11:07:28.0526149Z Waiting for resource 'REDACTED' to become healthy.
info: REDACTED[0]
      4: 2024-11-25T11:07:41.3254477Z Waiting for resource 'REDACTED' to become healthy.
info: REDACTED[0]
      5: 2024-11-25T11:07:42.4269559Z Finished waiting for resource 'REDACTED'.
info: REDACTED[0]
      6: 2024-11-25T11:08:05.2596140Z Finished waiting for resource 'REDACTED'.
info: Aspire.Hosting.DistributedApplication[0]
      Distributed application started. Press Ctrl+C to shut down.
info: Polly[3]
      Execution attempt. Source: '-standard//Standard-Retry', Operation Key: '', Result: 'The operation was canceled.', Handled: 'False', Attempt: '0', Execution Time: 114.5811ms
      System.Threading.Tasks.TaskCanceledException: The operation was canceled.
       ---> System.IO.IOException: Unable to read data from the transport connection: Operation canceled.
       ---> System.Net.Sockets.SocketException (125): Operation canceled
         --- End of inner exception stack trace ---
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()


Schema stitching refresh

Hey, my team is using schema stitching and really love it!
I did have one question about it to which I could've find an answer for in the docs.
If you've got graph's A and B with A pointing to B (A -> B), if B's schema changes/is added to, it does not appear to propagate to A automatically without a server reboot or some other type of intervention. Is there a setting to do this?

We are working on this at the moment. If you head over to our slack channel you can find the roadmap.
https://join.slack.com/t/hotchocolategraphql/shared_invite/enQtNTA4NjA0ODYwOTQ0LTViMzA2MTM4OWYwYjIxYzViYmM0YmZhYjdiNzBjOTg2ZmU1YmMwNDZiYjUyZWZlMzNiMTk1OWUxNWZhMzQwY2Q

Awesome, really great to hear as we very much have enjoyed schema stitching thus far!


JENKINS: update readme to indicate the correct image that is used by default

What this PR does / why we need it:
After reading this blog post and checking the chart I thought we were using the wrong image
https://jenkins.io/blog/2018/12/10/the-official-Docker-image/
but it turns out that it's just the README that is wrong.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

Signed-off-by: Jeff Knurek<EMAIL_ADDRESS>

/ok-to-test
/assign
/lgtm


New rule: Always inject dispatchers

Expected Behavior of the rule
When standard dispatchers like Dispatchers.IO/Default/Unconfined are being used directly without dependency injection, violations should be reported.
The following scenarios shouldn't be reported.

Coroutine dispatchers used as a default argument of the constructor.
Dispatchers.Main/Dispatchers.Main.Immediate because this is overrideable by [Dispatchers.setMain] (https://kotlin.github.io/kotlinx.coroutines/kotlinx-coroutines-test/kotlinx.coroutines.test/set-main.html) and Dispatchers.resetMain

Context
If a coroutine dispatcher is not injected, it is extremely difficult to write unit tests that can complete.
This is recommended by https://developer.android.com/kotlin/coroutines/coroutines-best-practices#inject-dispatchers
as well as https://youtu.be/KMb0Fs8rCRs?t=839.

Playing devils advocate here: Should this be a part of an android rule set  instead of the detekt core rule sets?

Playing devils advocate here: Should this be a part of an android rule set instead of the detekt core rule sets?

Not really. Dispatchers.IO/Default/Unconfined could be used also in non-Android project (i.e. backend) and follow the same guideline imho

Problem with this rule is in koin you need to declare what dispatcher you are injecting.  This then violates the rule.  I've been shutting off this cause its annoying.

Hello,
I was wondering if this rule is still recommended when using it in combination with Spring's Dependency Injection? It won't be able to find a Bean with CoroutineDispatch:

"Could not autowire. No beans of 'CoroutineDispatcher' type found. "

This "error" makes sense, as we don't have a CoroutineDispatcher bean anywhere. Nor do we want that. We can fix the error by making it not required in Spring:
@Autowired(required = false) private val dispatcher: CoroutineDispatcher = Dispatchers.IO,

However, the question remains whether it is a best practice in this situation. If someone declared a bean as follows:
@Bean
fun oops() = Dispatchers.Main

Then all dependency injected dispatchers are ran on the main thread instead of their default assigned dispatcher. Of course one would say "well don't declare a Spring Bean of type CoroutineDispatcher" which is fair, but that is harder to enforce in every Kotlin/Spring repository. Would love to hear your thoughts!


Extension using too much CPU

This extension, PHP IntelliSense is consuming almost 100% CPU.
What is wrong?

There is nothing wrong, it is doing expensive operations. Why should it not use the resources available? And how would it do that?


Support for GH Enterprise

Does this currently support or have planned future support for github enterprise?
I see step 2 in the readme specifically says github.com.

No ETA yet, but want to tackle this eventually for the release of GHES 3.0

Commenting so its not stale

any ETA on this? is it more complicated than exposing an editable hostURL setting?

Would also be interested in a support for GHES.

does this mean the issue has been resolved?


Fix broken URL in package.json

The subdomain was wrongly set as domain.
Besides that this project is public - so setting "private: true" doesn't make sense.

@CMiksche private: true in a package.json means that the package will not be published to NPM as a package, which is the case here.

@CMiksche private: true in a package.json means that the package will not be published to NPM as a package, which is the case here.

This package is already released in npm, there is no need to protect it from publishing?!

@CMiksche private: true in a package.json means that the package will not be published to NPM as a package, which is the case here.

Ok, i've added that line again ;-)


Update scalatest to 3.2.19

About this PR
📦 Updates org.scalatest:scalatest from 3.2.18 to 3.2.19
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
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.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalatest", artifactId = "scalatest" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalatest", artifactId = "scalatest" }
}]

labels: test-library-update, early-semver-patch, semver-spec-patch, commit-count:1

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.939%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
93

Relevant Lines:
99

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.939%

Totals

Change from base Build<PHONE_NUMBER>0:
0.0%

Covered Lines:
93

Relevant Lines:
99

💛  - Coveralls


chore(support): ref forwardRef support for input

Fixes for ref forwardRef support for all the components
https://beta.reactjs.org/reference/react/forwardRef

https://github.com/hidaytrahman/react-carbonui/issues/18


Will a version compiled based on jdk17 or 21 be provided in the future?

i have the same question ! Would be very nice if you could update


DotNetAdaptor fails to be restored

Describe the bug
The latest update to DotNetAdaptor seems to have a dependency on System.Drawing.Primitives that does not get restored automatically when restoring the DotNetWinRT nuget package. This was causing my MRTK project to have compile errors on editor loading.
To reproduce
Steps to reproduce the behavior:

Ensure the nuget cache of system.drawing.primitives does not exist before proceeding. This is usually located here: %userprofile%.nuget\packages\system.drawing.primitives.
Open a existing MRTK project that has been set to build for hololens 2 i.e. UWP, .net standard api....
Note: If you need to create a project with the settings from step 1 you will have to close the project and repeat step 1 - 2
Result:
The DotNetAdaptor project fails to restore with the following error:

%userprofile%.nuget\packages\microsoft.windows.mixedreality.dotnetwinrt\0.5.1043\build\Microsoft.Windows.MixedReality.DotNetWinRT.targets(26,5): error MSB3030: Could not copy the file "%userprofile%.nuget\packages\microsoft.windows.mixedreality.dotnetwinrt\0.5.1043\build......\System.Drawing.Primitives\4.3.0\lib\netstandard1.1\System.Drawing.Primitives.dll" because it was not found. [C:\Development\MixedRealityToolkit-Unity\Assets\MixedRealityToolkit.Providers\WindowsMixedReality\DotNetAdapter\DotNetAdapter.csproj]
UnityEngine.Debug:LogError(Object)
Microsoft.Build.Unity.MSBuildProjectBuilder:LogProgressMessage(String, ProgressMessageType) (at Library/PackageCache/com.microsoft.msbuildforunity@0.8.3/Editor/ProjectBuilder/MSBuildProjectBuilder.cs:348)
Microsoft.Build.Unity.<>c__DisplayClass9_0:b__1(ValueTuple2) (at Library/PackageCache/com.microsoft.msbuildforunity@0.8.3/Editor/ProjectBuilder/MSBuildProjectBuilder.cs:181) Microsoft.Build.Unity.DelegateProgress1:Report(ValueTuple2) (at Library/PackageCache/com.microsoft.msbuildforunity@0.8.3/Editor/ProjectBuilder/MSBuildProjectBuilder.cs:489) Microsoft.Build.Unity.<>c__DisplayClass10_0:<BuildProjectsAsync>b__1(ValueTuple2) (at Library/PackageCache/com.microsoft.msbuildforunity@0.8.3/Editor/ProjectBuilder/MSBuildProjectBuilder.cs:293)
Microsoft.Build.Unity.DelegateProgress1:Report(ValueTuple2) (at Library/PackageCache/com.microsoft.msbuildforunity@0.8.3/Editor/ProjectBuilder/MSBuildProjectBuilder.cs:489)
Microsoft.Build.Unity.<>c__DisplayClass17_0:b__0(Object, DataReceivedEventArgs) (at Library/PackageCache/com.microsoft.msbuildforunity@0.8.3/Editor/ProjectBuilder/MSBuildProjectBuilder.cs:435)
System.Threading._ThreadPoolWaitCallback:PerformWaitCallback()
Expected behavior
The DotNetAdaptor should restore any dependencies it requires automatically.
Your setup (please complete the following information)

Unity Version 2018.4.14f1
MRTK Version v2.2.0

Target platform (please complete the following information)

HoloLens 2

Additional context
This offending nuget package is Microsoft.Windows.MixedReality.DotNetWinRT. Specifically the latest update "0.5.1043 "

@dfields-msft, is there a new dependency?

The use of System.Drawing.SizeF was introduced in early December as part of the changes to enable the HolographicDepthReprojectionMethod API; I believe this predates MRTK 2.2's use of M.W.MR.DotNetWinRT. However, a package dependency on System.Drawing.Primitives was just added to the NuGet definition at the end of January as part of @majaeger's changes to support the .NET scripting backend.

I recently restored 0.5.1043 (after modifying the csproj file in mrtk) with no errors.

Could it be an issue with MSBuild for Unity 0.8.3 that has been fixed in 0.9.1?

@PeterUbimax I can confirm I see an error in the editor, though it does resolve after the restore happens.
Do you get in a permanently busted state?

@PeterUbimax, I've published an updated nuget package for Microsoft.Windows.MixedReality.DotNetWinRT, version 0.5.1044, which should fix the issue.
Can you try updating to the newer version and let us know if that revolves the problem?

@wiwei It's not permanently busted and the workaround at least for me was to create a new mrtk project and switch the build player to WSA. Then the nuget cache for system.drawing,primitives gets downloaded and solves any issues with other projects.

@majaeger Can confirm the latest nuget packge for DotNetWinRT resolves the issue I was seeing.
FYI: for the definitive way to test this I did the following:

Deleted any cache of system.drawing.primitives from the following location: %userprofile%.nuget\packages\system.drawing.primitives.

Download the MRTK project  and navigate to MixedRealityToolkit.Providers\WindowsMixedReality\DotNetAdapter

Ensure the ".obj" and "Plugins" folders are deleted

Run command "dotnet msbuild DotNetAdapter.csproj -restore  -v:minimal -p:NuGetInteractive=true  -t:Build -p:Configuration=Release"

Result: The system.drawing.primitives nuget package restored as expected
Note: if you want to see the original behavior I reported repeat the above steps but open the DotNetAdapter.csproj and replace line "" with "PackageReference Include="Microsoft.Windows.MixedReality.DotNetWinRT" Version="0.5.1043" />" before doing step 4.


packaging: Integrate github workflows to automate the air-gapping process of wave university

The PR fulfills these requirements: (check all the apply)

[ ] It's submitted to the main branch.
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. feat: Add a button #xxx, where "xxx" is the issue number).
[ ] When resolving a specific issue, the PR description includes Closes #xxx, where "xxx" is the issue number.
[ ] If changes were made to ui folder, unit tests (make test) still pass.
[ ] New/updated tests are included

This closes issue #2163

Thanks for the PR @sulhicader!
What's the reason for splitting into multiple files/workflows? It seems like an unnecessary abstraction that introduces plenty of duplication which will be hard to maintain for a few relatively trivial tasks - build and publish docker/helm.
Can we put it into existing workflow files instead? Also, it seems like you are only doing this for Wave University app so there is no need to make it overly parametrized, and hardcoding for simplicity should be fine for now.

@mturoci Thanks you for the inputs.
.github/workflows/wave-bundle-docker-build-publish.yaml, .github/workflows/wave-bundle-helm-release.yaml workflows will going to be common for all the apps going to pusblish from wave repo ( for now university and tour ). Also I mainly using the workflows from https://github.com/h2oai/wave-template/tree/main/.github/workflows template repo and in future if any additions comes to it, it will be easier to reflect those here. Here new workflows are triggered from .github/workflows/publish-university.yml which is existing workflow. As you suggest We can reduce the workflow files but putting into one file, but it also deviate from the standard template. WDYT?

The template is designed to build an arbitrary app for scratch, not to be integrated into existing workflows like here so it doesn't make sense to introduce it since all the apps have their builds already defined.

The builds only need to be adjusted to use h2o cli instead of plain zip.
Add steps to push to ECR / Helm as needed.

Correct me if I missed something in ^^.
Also, if anything changes, I can guarantee you (or anyone) will be able to resolve it much faster in 2 files with proper context than juggling across 6 files.

Sure @mturoci, I am working on this.

Hi @mturoci, I addressed the review comments and took the functionalities into one script. Please feel free to add comments  if any changes needed.


Flutter web scroll problem inside iframe

I have a flutter application which I deployed on a server. On a webpage, I embedded the flutter application Inside an Iframe.
Problem
When I scroll the page, After reaching the iframe, I cannot scroll any more. It seems Flutter application consumes scroll events and do not pass the events to the web page.
And I need user interaction with the iframe as well. I have multiple widget like carousel, Poll slide, Horizontal scrolling and vertical scrolling inside the iframe.
I have implemented one of my widget with jquery (not flutter) and it worked perfectly.
I researched more than 2 months about this issue, I found the work around for desktop :
s.addEventListener.apply(s,["wheel",q,r])
If I remove this line from main.dart.js, The scroll behavior fixes in desktop browsers But I still have problem in mobile browsers such as Safari.
Thank you in advance.

see https://github.com/flutter/flutter/issues/86021#issuecomment-887912902

Hi @gh-arman, does the comment in https://github.com/flutter/flutter/issues/86021#issuecomment-887912902 provide some more information?

Thank you for your reply.
I have checked that comment before, But It did not solve my issue.
As he said, It is browser limitation, So I will try the work around again, if I couldn't solve the problem I will open another issue.


[Mobile] Toolbar and Selection Abnormal work

During my use on iOS, I found that both double clicking and long pressing will trigger the toolbar, which makes it impossible to move both cursors to select content.
Simultaneously long press and hold to select a section of text, and you will find that only the last selected short section of text is copied to the clipboard after copying.

Yeah, even on Android. And I also noticed setting controller.text =''; apart from the initState like using a button function makes the keyboard not show again.

I can't select the text on the mobile if I implement toolbarController. I want the toolbar on long press or on the selection.
Usually I paste to replace the existing stuff. Which is not possible right now.

It was fixed on the latest version.


Split download process failed when downloading an app for the first time

The payload structure to download splits if the app doesn't belong to the account was wrong. Now it's been fixed.

Thanks!


BadImageFormatException and InvokeOnCustomGUIAvailable

BadImageFormatException: Could not resolve field token 0x040001df, due to: Could not load type of field 'PlanBuild.Blueprints.BlueprintManager+<>c:<>9__9_0' (1) due to: Could not load file or assembly 'MMHOOK_assembly_valheim, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies. assembly:MMHOOK_assembly_valheim, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null type: member:(null) signature: assembly:C:\Users\micah\AppData\Roaming\r2modmanPlus-local\Valheim\profiles\Server\BepInEx\plugins\MathiasDecrock-PlanBuild\PlanBuild\PlanBuild.dll type:<>c member:(null) signature:
Stack trace:
PlanBuild.PlanBuildPlugin.Awake () (at <7c23de4df02740f6b3263f9f9c4f3a9d>:0)
UnityEngine.GameObject:AddComponent(Type)
BepInEx.Bootstrap.Chainloader:Start()
UnityEngine.Application:.cctor()

[Warning:Jotunn.EventExtensions] Exception thrown at event InvokeOnCustomGUIAvailable in BlueprintGUI.Register:
System.ArgumentNullException: Value cannot be null.
Parameter name: source
at System.Linq.GroupedEnumerable2[TSource,TKey]..ctor (System.Collections.Generic.IEnumerable1[T] source, System.Func2[T,TResult] keySelector, System.Collections.Generic.IEqualityComparer1[T] comparer) [0x00016] in <351e49e2a5bf4fd6beabb458ce2255f3>:0
at System.Linq.Enumerable.GroupBy[TSource,TKey] (System.Collections.Generic.IEnumerable1[T] source, System.Func2[T,TResult] keySelector) [0x00000] in <351e49e2a5bf4fd6beabb458ce2255f3>:0
at PlanBuild.Blueprints.BlueprintGUI.RefreshBlueprints (PlanBuild.Blueprints.BlueprintLocation location) [0x00018] in <7c23de4df02740f6b3263f9f9c4f3a9d>:0
at PlanBuild.Blueprints.BlueprintGUI.Register () [0x00437] in <7c23de4df02740f6b3263f9f9c4f3a9d>:0
at Jotunn.EventExtensions.SafeInvoke (System.Action events) [0x00018] in D:\coding\vs_workspace\Jotunn\JotunnLib\Extensions\EventExtensions.cs:26

Closed this issue. This was caused by not having let MMHOOK regenerate. There are still some problems with the latest version 0.13.0, but someone already has an issue in for it.


Descriptions are not seen on apps

See: https://github.com/rancher/dashboard/issues/3038#issuecomment-853767511

The backend looks fine, it is the UI that looks up the value at the wrong field.
see my comment for details: https://github.com/rancher/dashboard/issues/3038#issuecomment-868845524

I think there's still an issue, the field referenced is only the user one when the app's state is deployed - https://github.com/rancher/dashboard/issues/3038#issuecomment-871524064

see my comment for why this is not a bug.


Zoomable line chart type='category'

I was using apexcharts line chart for visual representation and the X axis had timestamp in nanoseconds, the datetime type only works till microseconds and the numeric type has also restricted digit size of 16, this I could not use both. The category type can be used but it is not zoomable which is something that I require, kindly provide zooming in category

I agree! Zooming shouldn't be limited to datetime. I have a chart that can contain +100 values. Zooming options would make it much more readable. Anyone knows a workaround to get zooming working on category types?

I am also looking for the same feature. Can anyone help ?

Could you please fix this? Please enable zooming for type='category' ! That's a truly critical feature for us

Released v3.15.0 with the zooming enabled on category x-axis.
Example - https://apexcharts.com/javascript-chart-demos/column-charts/column-with-rotated-xaxis-labels/
Doc: https://apexcharts.com/docs/zooming-in-category-x-axis/


Fix window resizing not always updating layout

Fixes #1199: resizing a window didn't always update
the layout split. The underlying reason is that the
mouse down coordinates for window resizing are not
always within the CGRect of the window's frame;
often they are just outside the window's frame when
the resize cursor appears.
I changed the event tap location to kCGAnnotatedSessionEventTap,
which includes the field kCGMouseEventWindowUnderMousePointerThatCanHandleThisEvent
in the event metadata that always accurately identifies the window
that the click affects. This does alter the point in the input
stack at which Yabai observes events, but examining EVENT_TAP_CALLBACK(mouse_handler)
and user-testing the mouse features seems to show that changing
the observation point does not cause any regression.
I might be wrong about this. Please let me know if changing
the event tap location is a bad idea, and I will try to find
another workaround for this problem.

Ooooh!  I hadn't seen the issue but I'm glad to know it's not just me.  Any chance this fix would also resolve the issue where Yabai doesn't always refresh when a window is dragged?

It might, because, before this fix, Yabai was matching mouse-down cursor coordinates to window frame extents. I can't imagine why that would go wrong when you have to drag from inside a window's frame in order to move it, but it seems reasonable that getting the window ID directly from the event stream might eliminate ambiguity. Let me know if this does resolve the issue.

This doesn't actually fix the core issue of #1199 , which is caused by event order. https://github.com/koekeishiya/yabai/blob/master/src/mouse.c#L3 is the logic that causes problem, because the AX API has not yet reported that the window size has changed, so we use an outdated cached value and perform an incorrect comparison, causing the layout not to update. This code is triggered from a mouse-up event.
If we actually fail to determine the window on a mouse-down event as you mention in the description, that would be another bug.

tl;dr: Agreed, this is only a partial fix for #1199. Would you merge but leave the issue open?
Explanation
During troubleshooting, I added some debug statements to the code to print:

window_id and position/size (via new_frame) during every  WINDOW_RESIZED event
Position/size from both g_mouse_state.window->frame and g_mouse_state.window_frame during every MOUSE_DRAGGED and MOUSE_UP event

What I discovered was that sometimes the size in g_mouse_state.window->frame was not being updated even though I could see accurate data in messages from WINDOW_RESIZED. Looking at the unchanging sizes being printed from the MOUSE_DRAGGED events led me to realize that they were for a different window. Adding a few more debug print statements confirmed that the window_id values were different between what MOUSE_DOWN assigned to g_mouse_state.window (and cached in .window_frame) and what WINDOW_RESIZED events were printing. This is what led to this patch.
I never observed the case of the late-arriving WINDOW_RESIZED event causing a failure of the layout to update, but I don't doubt that it occasionally happens and that a fix for that issue is necessary to completely eliminate the layout falling out of sync with actual window sizes. I think the failure mode of late WINDOW_RESIZED events is that the layout is partially out of sync with the new window size, while the mode of misidentifying the window being resized is that the layout misses the entire resize operation.
Now that I've rambled out my inner thoughts... I agree that this does not completely close #1199. Should I open a separate issue, or would you consider merging this as a partial fix referencing that issue and leave it open?

I did some further investigation and implemented a preliminary fix to handle the late WINDOW_RESIZED events. The behavior from the fix I observed was that the affected window sizes seemed to "wobble" while the late events were being handled.
I added some debug prints of the before & after sizes seen by the window resize event handler. I saw that all of the late resize events I was seeing were those generated by yabai to adjust the layout in response to the MOUSE_UP event, because the size was very far off from the last "live" resize event before MOUSE_UP and the difference would be approximately half the delta (the other half being "given" to the other window in the split).
See my non-working patch here: overhacked/yabai@b2a995f8188e8474984d73d2aaae9f09324eea9a

Made some similar adjustments in https://github.com/koekeishiya/yabai/commit/d4aa4c9781dffb741d5348f1a8dbe01ee8047252
#1199 can probably be fixed by using the faster CG notification system, but that API can only track a limited number of windows.

I guess we need a different workaround to this problem. See #1809, #1877, #1552, #2154

Found a different fix.


Add instalation instructions to MacOS

12 files changed?

12 files changed?

walac/macos was force-pushed, so now this branch needs a rebase

As rebase was needed so I took the chance to squash commits too.


Introspection

I find very useful for developers to have a way to make use of new fragments that maps to the new introspection opcodes, very useful for making covenants.
DO you have an idea if this fits the purpose of Miniscript and, if yes, what could be a timeline, especially for an initial agreement on the spec? We are implementing in other languages descriptors/miniscript for Elements, so would be cool to work in parallel as soon there could be consensus

DO you have an idea if this fits the purpose of Miniscript

Yes -- well, Elements Miniscript at least. Naturally we can't support this in the "real" Miniscript until Bitcoin has some form of introspection ability.

if yes, what could be a timeline,

My hope was "already" but our upstream re-architecture for Taproot took much longer than expected. Let's say "2 months".

especially for an initial agreement on the spec?

That will take longer. Initially we'll just stick some new fragments in to solve practical problems that Blockstream and other Liquid developers are trying to solve. It will take some iteration before we're confident that we've gotten the right set of fragments and that we've implemented them optimally.

We are implementing in other languages descriptors/miniscript for Elements, so would be cool to work in parallel as soon there could be consensus

I think your best bet is to keep up with the current state of this library, provide feedback, yell at us if we change things in ways that break your applications, etc. If you actually deploy something in production using a certain set of fragments we will be careful not to break things after that.

My current need is giving a way to users to load complex script types into Marina Wallet, so it can track balances and spend them if solvable/can sign so to speak.
There is no way to express with current fragments things like CSFS, CAT, new arithmetic opcodes or introspection ones. I understand it will come, so will keep an eye.
For the time being in our JavaScript parser, we are introducing a custom asm fragment that let user to load arbitrary opcodes so we can mix them with current fragments.
I know that this is useless since makes impossible to analyze etc.. but we only want a way to share these opcodes in a formal way, and use descriptor/miniscript when possible alrrady.

If you actually deploy something in production using a certain set of fragments we will be careful not to break things after that.

Will try to write here the synthetic asset smart contract and propose some new fragment for new opocodes so maybe we can make some early thoughts.

For the time being in our descriptor parser, we are introducing a custom asm fragment that let user to load arbitrary opcodes so we can mix them with current fragments.

I know that this is useless since makes impossible to analyze etc.. but we only want a way to share these opcodes in a formal way, and use descriptor/miniscript when possible already.

Be careful with this! It's not only the asm fragment itself that is "impossible to analyze" but the entire Miniscript that contains it. But this is likely a reasonable way to proceed for research & development.
With Simplicity we will be able to provide asm in the main library since Simplicity's type system can be leveraged to prevent arbitrary code inside one fragment from messing up code in other fragments, without requiring we have a fixed curated set of fragments.

"impossible to analyze" but the entire Miniscript that contains it

Yep! Totally understood.  User will know this is a very reckless feature and they need to be 100% sure of the asm code they are loading.
The idea is just to have a way to share opcodes at runtime for script path spends and implicitly tell the type of address shall be generated. We only parse the descriptor, detect the top level fragment and if a CHECKSIG op is there and a pubkey template, a way for wallet to fill it with his own.
As soon all the new opcodes will be mapped to Miniscript, will likely drop this asmfragment and maybe at that point use this library directly  (maybe compiled to WASM to run in the browser if you will provide bindings)

Have you looked at the Extensions in the library? If you want to create any new fragments. You can do it downstream by implementing the Extension trait.
However, in this case, you are responsible for making sure that the fragment can be parsed unambiguously by the miniscript parser.

That looks interesting.
Not that much experience in Rust tho, would wait for the reference implementations and examples eheh :)
We pretty close to finish our TypeScript descriptor parser btw, we added asm fragment as temporary solution and we made sure is valid only inside TREE of a eltr descriptor, new opcodes must be used in tapscripts anyway. Will drop it as soon new fragments are there and/or with extension trait.

Hello @tiero, introspection support with arithmetic operations is now supported. See https://github.com/ElementsProject/elements-miniscript/blob/master/doc/extension_spec.md for details. Still awaiting #28 to be merged

Amazing @sanket1729
We plan to add support to our ionio-lang.org for current elements-miniscript fragments, to allow to parse miniscript and compile to opcodes, generating an Ionio Artifact JSON in the process, so SDK(s) and libraries can easily spend taproot output scripts.


Fix Adapter bug causing Linkerd version in e2e tests not being found

Current Behavior

Expected Behavior

Screenshots/Logs

Environment

Host OS: Mac Linux Windows
Platform: Docker or Kubernetes
Meshery Server Version: stable-v
Meshery Client Version: stable-v
Meshery Adapter Version: stable-v

Contributor Guides and Resources

📝 Meshery Adapters Spreadsheet
🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

Covered in https://github.com/meshery/meshery-linkerd/issues/449


StreamPipelineControl output FIFO is sometimes sized too small

In some cases, StreamPipelineControl seems to size its output FIFO smaller than the pipeline depth, resulting in (oscillating) backpressure. NUM_PIPE_REGS=2 and MIN_CYCLES_PER_TRANSFER=1 replicates the issue.

Closing this as it is now part of https://github.com/abs-tudelft/vhlib
Copied to
https://github.com/abs-tudelft/vhlib/issues/4


CPU overloaded at the <IP_ADDRESS>

After upgrede to <IP_ADDRESS> cpu utilization continuatelly height. Reverting to previous version solves issue, reinstall or/and reboot - not.
Environment - Proxmox, HAOS. Addon configuration: exit node, funnel - all works, exept CPU issue. Nothing weird in the logs.

2023/08/02 01:15:27 router: disabling tunneled IPv6 due to system IPv6 config: kernel doesn't support IPv6 policy routing: querying IPv6 policy routing rules: address family not supported by protocol
2023/08/02 01:15:27 dns: [resolved-ping=yes rc=unknown ret=direct]
2023/08/02 01:15:27 dns: using "direct" mode
2023/08/02 01:15:27 dns: using *dns.directManager
2023/08/02 01:15:27 link state: interfaces.State{defaultRoute=enp0s18 ifs={docker0:[<IP_ADDRESS>/23] enp0s18:[<IP_ADDRESS>/24] hassio:[<IP_ADDRESS>/23]} v4=true v6=false}
2023/08/02 01:15:27 magicsock: disco key = d:41adeb77a50bdbb4
2023/08/02 01:15:27 Creating WireGuard device...
2023/08/02 01:15:27 Bringing WireGuard device up...
2023/08/02 01:15:27 Bringing router up...
2023/08/02 01:15:27 external route: up
2023/08/02 01:15:27 Clearing router settings...
2023/08/02 01:15:27 Starting network monitor...
2023/08/02 01:15:27 Engine created.
2023/08/02 01:15:27 pm: using backend prefs for "profile-06d6": Prefs{ra=true dns=true want=true routes=[<IP_ADDRESS>/0 ::/0 <IP_ADDRESS>/24] snat=true nf=on host="haos" Persist{lm=, o=, n=[H1KK9]<EMAIL_ADDRESS>2023/08/02 01:15:27 envknob: TS_NO_LOGS_NO_SUPPORT="true"
2023/08/02 01:15:27 logpolicy: using system state directory "/var/lib/tailscale"
2023/08/02 01:15:28 got LocalBackend in 115ms
2023/08/02 01:15:28 Start
2023/08/02 01:15:28 Backend: logs: be:7206ccb7ab321dc0fe158d38866f4845f30dc3c28bd7b44177447eaa77f114c1 fe:
2023/08/02 01:15:28 control: client.Login(false, 0)
2023/08/02 01:15:28 control: doLogin(regen=false, hasUrl=false)
2023/08/02 01:15:28 health("overall"): error: not in map poll
2023/08/02 01:15:28 control: control server key from https://controlplane.tailscale.com: ts2021=[fSeS+], legacy=[nlFWp]
2023/08/02 01:15:28 control: RegisterReq: onode= node=[H1KK9] fup=false nks=false
2023/08/02 01:15:28 control: creating new noise client
[01:15:28] INFO: Adding advertised local subnets to ip rules with higher priority than Tailscale's routing,
[01:15:28] INFO: to prevent routing advertised local subnets if the same subnet is routed within your tailnet.
[01:15:28] INFO:   Adding route <IP_ADDRESS>/24 to ip rules
2023/08/02 01:15:28 control: RegisterReq: got response; nodeKeyExpired=false, machineAuthorized=true; authURL=false
2023/08/02 01:15:28 control: netmap: got new dial plan from control
2023/08/02 01:15:28 active login<EMAIL_ADDRESS>2023/08/02 01:15:28 serve: creating a new proxy handler for http://<IP_ADDRESS>:8123
2023/08/02 01:15:28 Hostinfo.WireIngress changed to true
2023/08/02 01:15:28 Switching ipn state NoState -> Starting (WantRunning=true, nm=true)
2023/08/02 01:15:28 magicsock: SetPrivateKey called (init)
2023/08/02 01:15:28 wgengine: Reconfig: configuring userspace WireGuard config (with 0/2 peers)
2023/08/02 01:15:28 wgengine: Reconfig: configuring router
2023/08/02 01:15:28 wgengine: Reconfig: configuring DNS
2023/08/02 01:15:28 dns: Set: {DefaultResolvers:[<IP_ADDRESS>] Routes:{duck-buri.ts.net.:[] ts.net.:[<IP_ADDRESS> 2620:111:8007::53]}+65arpa SearchDomains:[duck-buri.ts.net.] Hosts:3}
2023/08/02 01:15:28 dns: Resolvercfg: {Routes:{.:[<IP_ADDRESS>] ts.net.:[<IP_ADDRESS> 2620:111:8007::53]} Hosts:3 LocalDomains:[duck-buri.ts.net.]+65arpa}
2023/08/02 01:15:28 dns: OScfg: {Nameservers:[<IP_ADDRESS>] SearchDomains:[duck-buri.ts.net.] MatchDomains:[] Hosts:[]}
2023/08/02 01:15:28 rename of "/etc/resolv.conf" to "/etc/resolv.pre-tailscale-backup.conf" failed (rename /etc/resolv.conf /etc/resolv.pre-tailscale-backup.conf: device or resource busy), falling back to copy+delete
2023/08/02 01:15:28 peerapi: serving on http://<IP_ADDRESS>:61465
2023/08/02 01:15:28 peerapi: failed to do peerAPI listen, harmless (netstack available) but error was: listen tcp6 [fd7a:115c:a1e0:ab12:4843:cd96:6254:c44d]:0: bind: cannot assign requested address
2023/08/02 01:15:28 peerapi: serving on http://[fd7a:115c:a1e0:ab12:4843:cd96:6254:c44d]:1
2023/08/02 01:15:28 portmapper: UPnP meta changed: {Location:http://<IP_ADDRESS>:49095/rootDesc.xml Server:Keenetic Ltd. UPnP/1.1 MiniUPnPd/2.0 USN:uuid:7a3f4b5b-ca1c-3c87-13ca-a4e3b2a09da3::urn:schemas-upnp-org:device:InternetGatewayDevice:1}
2023/08/02 01:15:28 magicsock: home is now derp-22 (waw)
2023/08/02 01:15:28 magicsock: adding connection to derp-22 for home-keep-alive
2023/08/02 01:15:28 control: NetInfo: NetInfo{varies=false hairpin=false ipv6=false ipv6os=true udp=true icmpv4=false derp=#22 portmap=active-UMC link=""}
2023/08/02 01:15:28 magicsock: 1 active derp conns: derp-22=cr0s,wr0s
2023/08/02 01:15:28 derphttp.Client.Connect: connecting to derp-22 (waw)
2023/08/02 01:15:28 Switching ipn state Starting -> Running (WantRunning=true, nm=true)
2023/08/02 01:15:28 magicsock: endpoints changed: <IP_ADDRESS>:44475 (portmap), <IP_ADDRESS>:44475 (stun), <IP_ADDRESS>:44475 (local), <IP_ADDRESS>:44475 (local), <IP_ADDRESS>:44475 (local)
2023/08/02 01:15:28 wgengine: Reconfig: configuring userspace WireGuard config (with 0/10 peers)
2023/08/02 01:15:28 serve listening on <IP_ADDRESS>:443
2023/08/02 01:15:28 magicsock: derp-22 connected; connGen=1
[01:15:30] INFO: Tailscale is running
[01:15:30] INFO: Clamping the MSS to the MTU for all advertised subnet's interface,
[01:15:30] INFO: to support site-to-site networking better
[01:15:30] INFO:   Clamping the MSS for interface enp0s18
s6-rc: info: service post-tailscaled successfully started
s6-rc: info: service proxy: starting
s6-rc: info: service taildrop: starting
s6-rc: info: service taildrop successfully started
2023/08/02 01:15:28 health("overall"): ok
2023/08/02 01:15:31 serve: closing idle connections to http://<IP_ADDRESS>:8123
2023/08/02 01:15:31 closing listener <IP_ADDRESS>:443
2023/08/02 01:15:31 closing listener [fd7a:115c:a1e0:ab12:4843:cd96:6254:c44d]:443
2023/08/02 01:15:31 Hostinfo.WireIngress changed to false
2023/08/02 01:15:31 serve: creating a new proxy handler for http://<IP_ADDRESS>:8123
[01:15:31] INFO: Tailscale Proxy is enabled:
[01:15:31] INFO:   Your Home Assistant instance is available within your Tailnet VPN at
[01:15:31] INFO:   https://network.ts.net
s6-rc: info: service proxy successfully started
s6-rc: info: service funnel: starting
2023/08/02 01:15:31 serve listening on <IP_ADDRESS>:443
2023/08/02 01:15:31 wgengine: Reconfig: configuring userspace WireGuard config (with 0/2 peers)
[01:15:31] INFO: Tailscale Funnel is enabled:
[01:15:31] INFO:   Your Home Assistant instance is publicly available on the internet at
[01:15:31] INFO:   https://network.ts.net
s6-rc: info: service funnel successfully started
s6-rc: info: service legacy-services: starting

What I missed? Will be appreciated for your help. THanks for the great job!

Strange, I've checked what I've changed (https://github.com/lmagyar/homeassistant-addon-tailscale/commit/45419363f41befb1683e3f7a2a4bbd8c5a91ab3e), and based on your log, my script executes the same steps as the previous version, so my guess is that the problem is with the binaries (tailscale or base-image).
I see only one strange unrelated thing in the logs: https://network.ts.net
So please:

what is the output of this command, executed in the add-on's cli: /opt/tailscale status --self=true --peers=false --json | jq "{HostName: .Self.HostName, DNSName: .Self.DNSName, MagicDNSSuffix: .MagicDNSSuffix, CertDomains: .CertDomains}"
it should be something like this:
{
  "HostName": "dev-homeassistant",
  "DNSName": "dev-homeassistant-beta.tail6158.ts.net.",
  "MagicDNSSuffix": "tail6158.ts.net",
  "CertDomains": [
    "dev-homeassistant-beta.tail6158.ts.net"
  ]
}

you can get into the add-on's container with something like docker exec -it addon_09716aab_tailscale /bin/bash

I've created a new beta version v<IP_ADDRESS>-rc02 of my fork, with the latest binaries (base-image v14.0.7), I don't think it will solve the CPU issue, but this is a first step to test, so please:

stop the non-beta tailscale version
install, start, login, configure the beta version from here: https://github.com/lmagyar/homeassistant-addon-tailscale-beta
note: it creates a tailscale2 interface, just to not completely mess up networking if accidentally started parallel with the non-beta version
does this solve the CPU issue?
stop the beta, start the non-beta add-on

If the CPU issue doesn't solved, I will create a downgraded beta release (downgraded tailscale, then downgraded base-image versions, but with my latest script version), maybe we will see something. Eg. there is an issue with taildrop and network performance: https://github.com/hassio-addons/addon-tailscale/issues/168

I see only one strange unrelated thing in the logs: https://network.ts.net

I replaced some personal info for security reason.
Thank you, I will test beta version and give you feedback soon.

Ah, OK. :) So the link that is shown in the log, as "Your Home Assistant instance is publicly available on the internet at https://network.ts.net" in reality is working? I was scared that something is really different on a Proxmox/HAOS installation.

Both version works and accessible from external, but beta without CPU overload:

...
2023/08/03 01:53:47 serve: creating a new proxy handler for http://<IP_ADDRESS>:8123
[01:53:48] INFO: Tailscale Funnel is enabled:
[01:53:48] INFO:   Your Home Assistant instance is publicly available on the internet at
[01:53:48] INFO:   https://host.nw.ts.net
s6-rc: info: service funnel successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2023/08/03 01:53:48 Hostinfo.WireIngress changed to true

If any additional testing required please let me know.

Wow! This means the problem is with the v14.0.6 base image.
I've released v<IP_ADDRESS> NON-beta version.
Please report back, if the new v<IP_ADDRESS> NON-beta version works without extra CPU load.

I've released v<IP_ADDRESS> NON-beta version.

I updated to v<IP_ADDRESS> and nothing changes for me. Extra load was found again, so then I totally uninstalled main version and reinstalled it again. Add-on asked for autorization by url and then all extra CPU loads was fixed. So my best gues - this is not related with a binary or/and add-on and something at the cloud side. Thank you for your help.

Computers are 'a complete mystery'... :)
Closing this issue for now, reopen it if you think it is relevant again.


[FLOC-1266] Release 0.3.3dev4

This branch should not be merged until the release process is complete.
https://clusterhq.atlassian.net/browse/FLOC-1266

The build is still in progress but I guess that the files changed can be checked already.

There's one suspicious broken link:
gettinginvolved/contributing.rst:44: [broken] https://github.com/ClusterHQ/flocker/compare/release/flocker-1.2.3...release-maintenance/flocker-1.2.3/fix-a-bug-FLOC-1234?expand=1: HTTP Error 404: Not Found

http://build.clusterhq.com/builders/flocker-docs/builds/3818/steps/build-linkcheck/logs/errors
But that can be fixed in another issue. And one solution would be for it to be plain text rather than a link.

Seems that you have to specify the --flocker-version when running the acceptance tests. Docs need updating:
admin/run-acceptance-tests --distribution fedora-20 --flocker-version=<IP_ADDRESS>5.g742fd6d
Where version is the version shown by vagrant box list
(flocker-release-0.3.3dev4)(release/flocker-0.3.3dev4 =)[~/.../HybridLogic/flocker-0.3.3dev4]$ vagrant box list
centos65-x86_64-20140116   (virtualbox, 0)
chef/centos-7.0            (virtualbox, 1.0.0)
clusterhq/fedora20-updated (virtualbox, 2014.09.19)
clusterhq/flocker-dev      (virtualbox, <IP_ADDRESS>4.g7987f9b)
clusterhq/flocker-tutorial (virtualbox, <IP_ADDRESS>5.g742fd6d)
ubuntu/trusty64            (virtualbox, 14.04)

I'm seeing some errors when running acceptance tests locally eg
(flocker-release-0.3.3dev4)(release/flocker-0.3.3dev4 =)[~/.../HybridLogic/flocker-0.3.3dev4]$ admin/run-acceptance-tests --distribution fedora-20 --flocker-version=<IP_ADDRESS>5.g742fd6d
==> node2: VM not created. Moving on...
==> node1: VM not created. Moving on...
Bringing machine 'node1' up with 'virtualbox' provider...
...

<EMAIL_ADDRESS>out: Status: Image is up to date for clusterhq/mongodb:latest
<EMAIL_ADDRESS>out:

Disconnecting from<EMAIL_ADDRESS>done.
flocker.acceptance.test_deployment
  DeploymentTests
    test_application_volume_quotas ... Unhandled Error
Traceback (most recent call last):
  File "/usr/lib64/python2.7/threading.py", line 784, in __bootstrap
    self.__bootstrap_inner()
  File "/usr/lib64/python2.7/threading.py", line 811, in __bootstrap_inner
    self.run()
  File "/usr/lib64/python2.7/threading.py", line 764, in run
    self.__target(*self.__args, **self.__kwargs)
--- <exception caught here> ---
  File "/opt/flocker/lib/python2.7/site-packages/twisted/python/threadpool.py", line 196, in _worker
    result = context.call(ctx, function, *args, **kwargs)
  File "/opt/flocker/lib/python2.7/site-packages/twisted/python/context.py", line 118, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File "/opt/flocker/lib/python2.7/site-packages/twisted/python/context.py", line 81, in callWithContext
    return func(*args,**kw)
  File "/opt/flocker/lib/python2.7/site-packages/flocker/node/_docker.py", line 432, in _add
    _create()
  File "/opt/flocker/lib/python2.7/site-packages/flocker/node/_docker.py", line 427, in _create
    host_config=host_config,
  File "/opt/flocker/lib/python2.7/site-packages/docker/client.py", line 556, in create_container
    return self.create_container_from_config(config, name)
  File "/opt/flocker/lib/python2.7/site-packages/docker/client.py", line 564, in create_container_from_config
    return self._result(res, True)
  File "/opt/flocker/lib/python2.7/site-packages/docker/client.py", line 98, in _result
    self._raise_for_status(response)
  File "/opt/flocker/lib/python2.7/site-packages/docker/client.py", line 94, in _raise_for_status
    raise errors.APIError(e, response, explanation=explanation)
docker.errors.APIError: 500 Server Error: Internal Server Error ("Could not create local directory '/flocker/899fd0d6-1899-4ad3-967a-a0a6228af1b8.default.565d4aee-9a88-43c4-ad5c-32ba0ea2941d' for bind mount: mkdir /flocker/899fd0d6-1899-4ad3-967a-a0a6228af1b8.default.565d4aee-9a88-43c4-ad5c-32ba0ea2941d: read-only file system!")
main function encountered error
Traceback (most recent call last):
Failure: twisted.internet.defer.FirstError: FirstError[#0, [Failure instance: Traceback: <class 'docker.errors.APIError'>: 500 Server Error: Internal Server Error ("Could not create local directory '/flocker/899fd0d6-1899-4ad3-967a-a0a6228af1b8.default.565d4aee-9a88-43c4-ad5c-32ba0ea2941d' for bind mount: mkdir /flocker/899fd0d6-1899-4ad3-967a-a0a6228af1b8.default.565d4aee-9a88-43c4-ad5c-32ba0ea2941d: read-only file system!")
/usr/lib64/python2.7/threading.py:784:__bootstrap
/usr/lib64/python2.7/threading.py:811:__bootstrap_inner
/usr/lib64/python2.7/threading.py:764:run
--- <exception caught here> ---
/opt/flocker/lib/python2.7/site-packages/twisted/python/threadpool.py:196:_worker
/opt/flocker/lib/python2.7/site-packages/twisted/python/context.py:118:callWithContext
/opt/flocker/lib/python2.7/site-packages/twisted/python/context.py:81:callWithContext
/opt/flocker/lib/python2.7/site-packages/flocker/node/_docker.py:432:_add
/opt/flocker/lib/python2.7/site-packages/flocker/node/_docker.py:427:_create
/opt/flocker/lib/python2.7/site-packages/docker/client.py:556:create_container
/opt/flocker/lib/python2.7/site-packages/docker/client.py:564:create_container_from_config
/opt/flocker/lib/python2.7/site-packages/docker/client.py:98:_result
/opt/flocker/lib/python2.7/site-packages/docker/client.py:94:_raise_for_status
]]
Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
  File "/usr/lib64/python2.7/threading.py", line 784, in __bootstrap
    self.__bootstrap_inner()
  File "/usr/lib64/python2.7/threading.py", line 811, in __bootstrap_inner
    self.run()
  File "/usr/lib64/python2.7/threading.py", line 764, in run
    self.__target(*self.__args, **self.__kwargs)
--- <exception caught here> ---
  File "/home/richard/.virtualenvs/flocker-release-0.3.3dev4/lib/python2.7/site-packages/twisted/python/threadpool.py", line 196, in _worker
    result = context.call(ctx, function, *args, **kwargs)
  File "/home/richard/.virtualenvs/flocker-release-0.3.3dev4/lib/python2.7/site-packages/twisted/python/context.py", line 118, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File "/home/richard/.virtualenvs/flocker-release-0.3.3dev4/lib/python2.7/site-packages/twisted/python/context.py", line 81, in callWithContext
    return func(*args,**kw)
  File "/home/richard/projects/HybridLogic/flocker-0.3.3dev4/flocker/common/_ipc.py", line 90, in get_output
    raise IOError("Bad exit", remote_command, e.returncode, e.output)
exceptions.IOError: ('Bad exit', ['flocker-changestate', 'nodes:\n  <IP_ADDRESS>: []\n  <IP_ADDRESS>: [mongodb-example-application]\nversion: 1\n', "applications:\n  mongodb-example-application:\n    image: clusterhq/mongodb\n    volume: {dataset_id: 565d4aee-9a88-43c4-ad5c-32ba0ea2941d, maximum_size: '104857600',\n      mountpoint: /data/db}\nversion: 1\n", '<IP_ADDRESS>:\n  applications: {}\n  used_ports: [22, 111, 48118, 48852]\n  version: 1\n<IP_ADDRESS>:\n  applications: {}\n  used_ports: [22, 111, 43085, 51276, 53274, 55954, 55967]\n  version: 1\n', '<IP_ADDRESS>'], 1, '')
                                  [FAIL]

Yeah, I'm seeing this for all the acceptance tests

Yeah, I'm seeing this for all the acceptance tests

Sorry, didn't mean to close the PR.

Same problem is showing up on buildbot:

http://build.clusterhq.com/builders/flocker%2Facceptance%2Fvagrant%2Ffedora-20/builds/352/steps/trial/logs/stdio

I created some related issues:

https://clusterhq.atlassian.net/browse/FLOC-1273
https://clusterhq.atlassian.net/browse/FLOC-1272
https://clusterhq.atlassian.net/browse/FLOC-1274


Fix _this.input.focus() is undefined issue on mobile

On mobile browsers I've seen this problem in our error logs quite often:
TypeError: l.input.focus is not a function
1
File "webpack:///./node_modules/react-autosuggest/dist/Autosuggest.js" line 249 col 19 in Autosuggest
_this.input.focus();

It's very similar to what has been mentioned in these issues:
https://github.com/moroshko/react-autosuggest/issues/646
https://github.com/moroshko/react-autosuggest/issues/669
I simply wrapped the focus function so that we make sure it is defined before trying to call the function.
We were able to reproduce the bug consistently by scrolling on the dropdown component in a mobile browser or iOS Simulator.
Hope this helps!

I've been trying to replicate this for so long. Thank you.
Didn't even know where this issue was coming from. But indeed needed to scroll from the Autosuggest dropdown. It sends that error even though there's nothing to scroll..

Hello, can we merge this PR ? I also get the same error

@carolineBda at this point I'd suggest migrating to another package that is maintained. The other option is to use patch-package method but that will increase tech debt in your project even more.


Synchrony Ingress Path Incorrect

The ingress path for synchrony is incorrect.
- path: "{{ trimSuffix "/" .Values.ingress.path }}/synchrony"

This should not rely on the .Values.ingress.path as it then nests the synchrony path inside the Confluence contextPath and/or puts synchrony at the same base path, which usually users have to authenticate to with SSO. I fixed it manually by just changing this path to /synchrony in the ingress, as I already have a context path for Confluence.
The path in the ingress should be changed to /synchrony if Confluence is using a contextPath already. But, ideally the ingress for Synchrony should be broken down in the same way the ingress is for Confluence where a host and a path are both parameters. There will also be a different requirement for ingress depending on whether the user uses or does not use a contextPath with Confluence.
User Case 1 - User uses a contextPath with Confluence

The same ingress can be used for both Confluence and Synchrony by putting both Confluence and Synchrony at different contextPaths. Confluence would route to {{ .Values.ingress.host }}/confluence and and Synchrony would route to {{ .Values.ingress.host }}/synchrony for example.

Use Case 2 - User does not use a contextPath with Confluence

The same ingress can't be used for both Confluence and Synchrony as a different ingress will be used for a second host used by Synchronys ingress to avoid SSO collisions with the baseURL. Synchrony would route to {{ .Values.sychrony.ingress.host }} and Confluence would route to  {{ .Values.ingress.host }} where they don't have any chance of colliding.

This would create a conditional requirement to create a second ingress specifically for synchrony if a contextPath is not used as well.
I can work on a PR if you think creating a conditional for second ingress and breaking down synchrony into host and path options is feasible.

On second thought, it will probably always make sense just to make two ingresses.... One for confluence and one for synchrony.

I agree that we shouldn't force people to have Confluence and Synchrony on the same host or with the same context path. I think it's OK to always create a separate ingress for Synchrony - I don't like the idea of having a conditional ingress, as it adds complexity.
We can introduce new values Values.synchrony.ingress.host and Values.synchrony.ingress.path. They can by default resolve to what they are now (confluence.host and confluence.path/synchrony), but the user can override them if they want.
This gives the user more flexibility, but at the same time we have sensible default values and we don't force additional configuration on the user.
Finally, I see no problem of having multiple ingresses, because Confluence does it now anyway and it works well: there is a separate ingress for /setup endpoints because they need bigger timeout.

Yes, @badgersow makes perfect sense. I use a kubectl patch with our current deployment to fix the ingress, but looking forward to eliminating the need for that patch.

Just checking back to see if you would like me to submit a PR for this. When using context path the bug fix is:
'''
kubectl patch ingress -n jira-data enter jira-datacenter --type=json -p '[{"op": "replace", "path": "/spec/rules/0/http/paths/1/path", "value":"/synchrony"}]'
'''

@nanux Do we want to accept the contribution here or this ticket is on our roadmap already?

Hi @bordenit just wondering if you've had time to look into submitting a PR for this yet?

No I have not had time. If someone else wants to pick it up feel free.

All good @bordenit, we'll look into getting this tee'd up on our end.

@errcode1202 I through something together, but will wait to create PR until my other PR is merged. I just removed the syncrhony ingress from values.yaml, and updated the other files to use /synchrony context path appended to the ingress.host variable. I think that kind of makes sense, since less than .01% of people are probably going to have an external synchrony service. Maybe it can be just an automatic thing that is set in the background that user never needs to configure.


Acceptance testing

@galamit86
I have started to do some acceptance testing. Running statline-bq from main branch with config as-is yields the following error:
Traceback (most recent call last):
  File "cli.py", line 57, in <module>
    upload_datasets()
  File "/Users/dkapitan/.pyenv/versions/3.8.5/lib/python3.8/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/Users/dkapitan/.pyenv/versions/3.8.5/lib/python3.8/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/Users/dkapitan/.pyenv/versions/3.8.5/lib/python3.8/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Users/dkapitan/.pyenv/versions/3.8.5/lib/python3.8/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "cli.py", line 53, in upload_datasets
    main(id=id, config=config, gcp_env=gcp_env)
  File "/Users/dkapitan/.pyenv/versions/3.8.5/lib/python3.8/site-packages/statline_bq-0.1.0-py3.8.egg/statline_bq/utils.py", line 1482, in main
    cbsodata_to_gbq(
  File "/Users/dkapitan/.pyenv/versions/3.8.5/lib/python3.8/site-packages/statline_bq-0.1.0-py3.8.egg/statline_bq/utils.py", line 1006, in cbsodata_to_gbq
    desc_dict = get_col_descs_from_gcs(
TypeError: get_col_descs_from_gcs() got an unexpected keyword argument 'gcp'

Should I run a different branch?

@dkapitan
Not sure when I messed it up, but main should have worked, of course.
It's a small issue, handing config + gcp_dev instead of gcp. PR #36 fixes it, and it should run properly.

@galamit86
So, I have setup a completely new working laptop:

Dell XPS 15
Pop!_OS 20.10 with zsh as shell
Python 3.8 as default

If I git clone this repo, do poetry install and then .../statline_bq/statline-bq I get an error:
zsh: command not found: statline-bq

I have never used poetry before to actually install the commandline scripts. Am I missing something?

@galamit86
So, I have setup a completely new working laptop:

Dell XPS 15
Pop!_OS 20.10 with zsh as shell
Python 3.8 as default

If I git clone this repo, do poetry install and then .../statline_bq/statline-bq I get an error:
zsh: command not found: statline-bq

I have never used poetry before to actually install the commandline scripts. Am I missing something?

@galamit86
Never mind, me being a noob. Of course it should be:
poetry run statline-bq

Will update README.md immediately

@galamit86
Never mind, me being a noob. Of course it should be:
poetry run statline-bq

Will update README.md immediately


Dataset

Hi, I was exploring a project in Bigdata PySpark and found your repository I would love it if you could share the dataset with me, the drive link in collab is not working anymore. Thanks :)

Hi, thank you for your message! Unfortunately the dataset was made available by our professor and I also don't have access to the drive anymore, but maybe this link will help? https://chriswhong.com/open-data/foil_nyc_taxi/

Thanks!


Web Extension

Closes #426

FYI:

Manifest version 2 is deprecated, and support will be removed in 2023. See https://developer.chrome.com/blog/mv2-transition/ for more details.

Yup, we're aware of that and are planning to migrate to V3 as soon as there is full support for V3 in Firefox.

There's also an issue here:
return window.fetch(chrome.runtime.getURL('checksums.txt'))

A display issue:

And it's not working, because that screen is made on a website, where the latest Offen version is installed. However, the FF version works fine:

I have a suggestion here: Change the icon color, so that one can see, that the website is running Offen. Let me know, if you want me to create an issue instead.

Thanks for the feedback, but as always the first Version contains a few bugs and we are already working on a 1.3.1 fix. Until then please consider the extension a bit broken. Sorry for that. I'll ping here once it's released.

That's absolutely fine :) Just wanted to inform you about my findings so far.
Oh, and the documentation should provide at least some kind of information, that CORS needs to be enabled on the server to make the extension work.

Oh, and the documentation should provide at least some kind of information, that CORS needs to be enabled on the server to make the extension work.

Could you elaborate on when exactly this (I assume you mean setting Access-Control-Allow-Origin: * ?) is needed? Up until now I did not ever need to set this when building / testing the extension, but maybe I was missing something or this behaves differently cross browser?
In case it is indeed required we should set it in Offen itself (as it's serving the script file) instead of just mentioning it in the documentation I guess.

There it is:

This seems to happen in Chrome only. I've seen it in Firefox too but there it was possible to fix it by requesting an extra permission. I will read up on why Chrome behaves the way it does and then fix it accordingly.

Seems it's ok to do it from the background script in Chrome still (right now it's fetching the script from the content script which is blocked): https://stackoverflow.com/a/56502776/797194


use safe auth when supported

https://github.com/jhunt/safe/issues/21

Check out safe v0.0.16 (https://github.com/jhunt/safe/releases/tag/v0.0.16)

Blacksmith now manages its own vault in-code, so there is no reliance on safe anymore.


Support for uBO regexp domain list

uBo implemented regex, if someone trust something like:
/bad-js.$domain=/[a-z-]{18}\.[\w]{2,20}/
/[a-z-]{18}\.[\w]{2,20}/##.bad-class
!
! regex in the dumb version - rather, the webmaster fell how to avoid falling into a safe regex.

but fail for , in cosmetic/scriptlet filters and | in network filters if gorhill rejected repair:
https://github.com/uBlockOrigin/uBlock-issues/discussions/2234#discussioncomment-5403472

In theory, network filtering can be unprotected by domain=/from= and cosmetic filtering can be based on the site's permanent DOM tree (No match to 99% of the rest of the sites on the Internet).
The scriptlet is also still possible to run all over the Internet in uBo, but there have been considerations for years whether to secure this with a minimum of "I am an advanced user" activation.

Also voe is covered sometimes: https://github.com/uBlockOrigin/uAssets/commit/5a660a989b0e836e47bb4886b9a28bf19136783a
(Unfortunately, I don't see how to turn these 36 domains into which regex - The site appears to have no fixed pattern (diffrent words, number order).)
Originally posted by @krystian3w in https://github.com/AdguardTeam/CoreLibs/issues/1550#issuecomment-1553743192

@maximtop We should move this to AGTree

ok, lets move

Via ZenHub, native "transfer issue" or manually by copy few sentences from here?