Connection to Azure SQL Edge Fails When .NET API Is Started Using an Aspire Host (Issue Limited to macOS?)

I've configured a .NET API and Azure SQL Edge using Aspire, and the connection specifically fails when initiated from an Aspire Host. Here is the exception:
Microsoft.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - 20)

It took me forever to isolate, but it turns out that this only happens when the API is started by the Aspire Host. I've created a Git repository that showcases the problem here: https://github.com/tjementum/AspireWithSqlServer, with even more info in the README.
If the same connection is initiated by starting the .NET API directly, everything works correctly. In fact, if I start everything using Aspire and let it fail, and then manually start the API it works. The repository has a Gif that shows the problem.
Here is a summary.
AppHost.Program.cs:
using Projects;

var builder = DistributedApplication.CreateBuilder(args);

var sqlPassword = "YourSecretPassword01!";

var sqlServer = builder.AddSqlServerContainer("localhost", sqlPassword, 1433)
    .WithAnnotation(
        new ContainerImageAnnotation { Registry = "mcr.microsoft.com", Image = "azure-sql-edge", Tag = "latest" }
    );

builder.AddProject<AspireWithSqlServer_WebApi>("WebApi")
    .WithEnvironment("SQL_PASSWORD", sqlPassword)
    .WithEnvironment("SQL_SERVER", sqlServer.Resource.Name);

builder.Build().Run();

In the API, I connect to the database using Entity Framework with this connection string:
public static string GetConnectionString(this IConfiguration configuration)
{
    var connectionString = configuration.GetConnectionString("Default");
    var sqlServer = Environment.GetEnvironmentVariable("SQL_SERVER") ?? "localhost";
    var sqlPassword = Environment.GetEnvironmentVariable("SQL_PASSWORD") ?? "YourSecretPassword01!";
    return connectionString!
        .Replace("${SQL_SERVER}", sqlServer)
        .Replace("${SQL_PASSWORD}", sqlPassword);
}

appsettings.json:
{
  "ConnectionStrings": {
    "Default": "Server=${SQL_SERVER};Database=weather;User Id=sa;Password=${SQL_PASSWORD};Encrypt=False;TrustServerCertificate=True"
  }
}

I'm running this on a MacBook M1 with an ARM processor, which necessitates the use of Azure SQL Edge, as the standard SQL Server is not supported on ARM architectures.

: https://github.com/tjementum/AspireWithSqlServer, with even more info in the README.

Seems like this is private.
You can simplify your app definition:
var builder = DistributedApplication.CreateBuilder(args);

var sqlPassword = "YourSecretPassword01!";

var sqlServer = builder.AddSqlServerContainer("default", sqlPassword, 1433)
    .WithAnnotation(
        new ContainerImageAnnotation { Registry = "mcr.microsoft.com", Image = "azure-sql-edge", Tag = "latest" }
    );

builder.AddProject<AspireWithSqlServer_WebApi>("WebApi")
    .WithReference(sqlServer);

builder.Build().Run();

That will set the connection string "Default" in your application.
As for why this isn't working, my only guess is that it has something to do with the proxy we have. @mitchdenny ran into a similar issue and ended up using <IP_ADDRESS> instead of localhost.

I'm running this on a MacBook M1 with an ARM processor, which necessitates the use of Azure SQL Edge, as the standard SQL Server is not supported on ARM architectures.

I wonder if we can detect this and make it just work with the SQL server resource.

Seems like this is private.

Apologies, please try again: https://github.com/tjementum/AspireWithSqlServer
I created this repo recalling tweets from you about how unhelpful 'it does not work' bug reports are. 😄

@mitchdenny ran into a similar issue and ended up using <IP_ADDRESS> instead of localhost.

I've tried switching from localhost to <IP_ADDRESS>, but I'm afraid I still facing the same error.

That will set the connection string "Default" in your application.

I just attempted that, but now I received a "ConnectionString is missing." error. I might not be setting it up correctly. I've created a pull request with these changes. Though, this might not be related to our current issue.

I wonder if we can detect this and make it just work with the SQL server resource.

Azure SQL Edge and SQL Server aren't identical (see Azure SQL unsupported-features). I would prefer being explicit about such differences. I'm speaking from experience here. 😃 I would rather have a separate AddAzureSqlContainer() in Aspire.

Added a comment to your PR.

Azure SQL Edge and SQL Server aren't identical (see Azure SQL unsupported-features). I would prefer being explicit about such differences. I'm speaking from experience here. 😃 I would rather have a separate AddAzureSqlContainer() in Aspire.

Got it. Makes sense.

With Docker Desktop 4.25+, SQL Server does now run in docker on M1+.  Does this help your repro?
https://www.brentozar.com/archive/2023/01/how-to-install-sql-server-and-the-stack-overflow-database-on-a-mac/

Also note:
"Azure SQL Edge based on ARM64 architecture is retired"
from:
https://techcommunity.microsoft.com/t5/sql-server-blog/azure-sql-edge-update-september-2023/ba-p/3930827
I hope you are unblocked by being able to run SQL Server using Docker Desktop 4.25+ on M1+

Also note:
"Azure SQL Edge based on ARM64 architecture is retired"
from:
https://techcommunity.microsoft.com/t5/sql-server-blog/azure-sql-edge-update-september-2023/ba-p/3930827
I hope you are unblocked by being able to run SQL Server using Docker Desktop 4.25+ on M1+

Wouldn't a workout to this just to run Rosetta on a Macbook?

I've updated my solution to use the default SQL Server 2022. But I get the exact same error. I've pushed the changes to the main branch here.

I also got the simplified version of passing the connection string from the AppHost to the API (see this pull request). But now I get the error System.Net.Sockets.SocketException (22): Invalid argument.
See this screenshot:

The connection string works fine if I connect manually. But notice, the SQL server is running on a random port even though I've been explicit about port 1433. This seems like a different bug, as I have not been able to spin up the SQL Server on port 1433.
I believe I'm doing it all by the book now, and I'm not convinced it's a Mac problem anymore. Did anyone get SQL Server to work with Aspire? I have not been able to find any YouTube or blog post claiming that it works. I would be great if a Windows user could test the branch and report back if it works. Or point to a sample somewhere that shows that SQL Server works with Aspire.

I've tested the repo provided by @tjementum and I have the same issue on Ubuntu 23.10.
Both main and change-to-ip-and-let-aspire-host-pass-connection-string branches fail with Microsoft.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - Unknown error 203).

Could this be being caused by the Traefik proxy being spun-up in front of the SQL Server container? We intend to change that behavior for scenarios like this AFAIK. @davidfowl do we have an issue for that?

I just tried to upgrade to .NET Aspire Preview 2 🎉, and I have the same problem.
In fact, I have this problem with the official Aspire Sample showcasing SQL Server.

Any workaround would be greatly appreciated.

What are the logs for SQL server telling in the dashboard?

@tjementum just confirming, you're on macOS?

I'll try to reproduce this with preview2 on macOS

Wow... impressive company here :) And thanks for looking into this.

What are the logs for SQL server telling in the dashboard?

They look completely normal. In December when I reported this, I compared the logs line by line when starting the Container with Aspire, vs with Docker. I can share the logs, but it's 500 lines.

@tjementum just confirming, you're on macOS?

Yes. Running on a MacBook Pro M1 Max.
Update:
I've just tried to play around with this again. And I see two different exception types, but when debugging, it sometimes worked! I've narrowed it down to a timing issue. It seems like the connection to the SQL Server fails if I try to connect to it too fast.
If I insert a 20-second sleep, it works. Instead, I made a loop that retries the connection to the database for up to 30 seconds, and somewhere between 2 and 20 seconds, it now always succeeds. I've just pushed this workaround to https://github.com/tjementum/AspireWithSqlServer.
These are the two exceptions I see:

Type: Microsoft.Data.SqlClient.SqlException. Message: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. See screenshot from the original issue report.

Type: System.Net.Sockets.SocketException. Message: Invalid argument. See screenshot from my last post.

Same issue here - thanks to @tjementum for your workaround and repo.  It got me up and running.

Is the workaround to retry while applying runtime migrations?

@davidfowl - Yes - this retry workaround worked for me:
https://github.com/tjementum/AspireWithSqlServer/blob/main/WebApi/Persistence/EntityFrameworkExtensions.cs

You can do this https://github.com/dotnet/aspire/blob/3c99c90958ea79073d4d67d87ad7b2195487f471/playground/eShopLite/CatalogDb/CatalogDbInitializer.cs#L23-L33

I'm afraid I still get the two different exceptions.
I [just pushed a commit] (https://github.com/tjementum/AspireWithSqlServer/commit/b4b05a1b236a375e0e3bfb0c66963959ab290e62) to use the dbContext.Database.CreateExecutionStrategy();.
I still have the retry in my code base, as it did not resolve the issue. But thanks for the suggestion :)

Got it.

@eerhardt we think this is probably your wheelhouse now (pay note to the comments about type 1 and type 2 errors)

@eerhardt we think this is probably your wheelhouse now (pay note to the comments about type 1 and type 2 errors)

I'm not sure what the action here is on Aspire. Can someone explain the issue? (there's been a lot of "Updates" above, and it is hard to follow what the current state is)
Is the problem that your app is trying to connect to the SQL Server instance, but the SQL Server is not ready for connections yet? Yes, you need to handle the server not being there yet, and wait until it is ready.
This was the outcome from https://github.com/dotnet/aspire/issues/1168. See that issue for more information.

It seems like on top of that it seems like the retry execution strategy from EF doesn’t handle this as a transient error

Can someone explain the issue? (there's been a lot of "Updates" above, and it is hard to follow what the current state is)

Let me summarize. The problem occurs on Mac and Linux when you use Aspire to configure a SQL Server like this in the AppHost's Program.cs:
using Projects;

var builder = DistributedApplication.CreateBuilder(args);

var sqlServer = builder.AddSqlServerContainer("default")
    .AddDatabase("weather");

builder.AddProject<AspireWithSqlServer_WebApi>("WebApi")
    .WithReference(sqlServer);

builder.Build().Run();

When starting the WebApi, it throws one of the following two different exceptions when using EF Core:
Microsoft.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - 20)

System.Net.Sockets.SocketException (22): Invalid argument

This repository https://github.com/tjementum/AspireWithSqlServer reproduces the error.
This seems to be a problem only when the API is trying to connect to the SQL server before it's ready, in this case, when EF Core is running migrations during startup.
@davidfowl gave a lot of feedback to try to resolve the issue. I still have the problem, but the repository is now even more to the point.
NOTE: This repository also has the following workaround that retries the migrations in a loop, and eventually, it succeeds. This makes me conclude that it's a timing issue.
var retryCount = 0;
while (retryCount <= 30)
{
    if (retryCount >= 1)
        logger.LogInformation("Waiting for databases to be ready. Retry count: {RetryCount}", retryCount);

    try
    {
        var dbContext = scope.ServiceProvider.GetService<WeatherForecastContext>();

        var strategy = dbContext.Database.CreateExecutionStrategy();

        await strategy.ExecuteAsync(() => dbContext.Database.MigrateAsync(cancellationToken));

        break;
    }
    catch (SqlException ex) when (ex.Message.Contains("an error occurred during the pre-login handshake"))
    {
        // Known error in Aspire, when SQL Server is not ready. See: https://github.com/dotnet/aspire/issues/1023
        retryCount++;
        Thread.Sleep(TimeSpan.FromSeconds(1));
    }
    catch (SocketException ex) when (ex.Message.Contains("Invalid argument"))
    {
        // Known error in Aspire, when SQL Server is not ready. See: https://github.com/dotnet/aspire/issues/1023
        retryCount++;
        Thread.Sleep(TimeSpan.FromSeconds(1));
    }

This isn't unique to mac or sql server, this is a problem in general:

Your code needs to be resilient to networking failures (this is what aspire packages add amongst other things)
Aspire doesn't do any coordination so your app services can start up and their dependencies might not be healthy.

SQL server spins up pretty fast normally, so this issue isn't as pronounced as other services (RabbitMQ is crazy bad takes 10 seconds minimally)
To make it so that you don't get any errors you really need health checks

Now that the problem is understood, I think we can close this issue.
Here's the issue that tracks potentially adding dependencies to reduce the amount of time this happens https://github.com/dotnet/aspire/issues/183

I respectfully disagree. You have this problem in your own Aspire sample.  If I run this sample, it never starts.
If you don’t fix this in Aspire Host, we will have to keep starting SQL using Docker Run to start the SQL server, which is stable, and by the way, also much faster. When I start the SQL server manually, I can debug in a couple of seconds, but with Aspire, it takes up to 20 seconds and on my powerful Mac.
Also, it’s very weird that I have to catch random undocumented internal SQL Server exceptions in production code to get a reliable experience for development.
At a very minimum you should update your sample project to work.

I respectfully disagree. You have this problem in your own Aspire sample. If I run this sample, it never starts.

We'll fix the sample.

If you don’t fix this in Aspire Host, we will have to keep starting SQL using Docker Run to start the SQL server, which is stable, and by the way, also much faster. When I start the SQL server manually, I can debug in a couple of seconds, but with Aspire, it takes up to 20 seconds and on my powerful Mac.

That's very slow. Doesn't change things though, we think we need to fix this issue for sure but this issue has been identified.

Also, it’s very weird that I have to catch random undocumented internal SQL Server exceptions in production code to get a reliable experience for development.

Agree, but this code would never be in production right? Doing migration at application startup isn't what most do in prod?

At a very minimum you should update your sample project to work.

Absolutely.

@karolz-ms Seems like there's a slowness issue on MacOS WRT booting up SQL. We should understand the delta between docker run and aspire to see if there's a delay we don't quite understand.

I will take a look and report what I find.

Perhaps the approach suggested in https://github.com/dotnet/aspire/issues/2090 could be generalized to block whenever the connection string is requested until the endpoint is ready.

@AndriySvyryd

Perhaps the approach suggested in #2090 could be generalized to block whenever the connection string is requested until the endpoint is ready.

Unfortunately the AfterEndpointsAllocatedAsync lifecycle hook I'm using in the sample for #2090 is called after the connection strings for the endpoints are available, but before the database container is running. I'm not sure using that as is would solve the exceptions @tjementum is having.
Two ideas that may solve for applying migrations from AppHost:

Adding a lifecycle hook for when a container is ready and listening.
Use the existing AfterEndpointsAllocatedAsync lifecycle hook like I do in #2090, but start a background thread or task to retry and wait applying the migrations.

Removing this from orchestrator as it appears it isn't something DCP should handle.

I will take a look and report what I find.

@karolz-ms is there any follow up here?

Use the existing AfterEndpointsAllocatedAsync lifecycle hook like I do in https://github.com/dotnet/aspire/issues/2090, but start a background thread or task to retry and wait applying the migrations.

2 is the right approach regardless. There's no support for health checking anywhere in the apphost currently and no plans to get to that for the first preview.
We want to add an "after resources created" event but it doesn't meant that the app resources are healthy either, so you still need to poll until they are.

I will take a look and report what I find.

@karolz-ms is there any follow up here?

I am sorry I have been super busy with P4 work, never had a chance to repro this.  Looks like this will be the case till EOW 😞

Moving to preview5 as this isn't blocking preview4.

There are 2 things we want to look into:

@eerhardt @sebastienros based on your experience with the EF execution strategies, it seems like we can add this invalid argument error to the list of transient errors (seems to happen with the emulator on macos at least). I think that should mitigate the issue here.
@karolz-ms @dbreshears can you reproduce the slow sql emulator startup on macos. Is it a DCP + docker +macos problem

@davidfowl ,  I don't reproduce the slower startup on macos. For me  after examining the container logs it's about 8 seconds (mac) to 10 seconds (windows) seconds to startup the sqlcontainer due to all its system level DB updates.   Its the same whether I manually start the container or let DCP through Aspire.
The main issue is 1 above on Mac (and assume Linux) and doesn't reproduce on Windows since the transient errors are being handled by the EF execution strategy.   Addressing that should alleviate any specific retry logic in the application.

Sounds good. @eerhardt @sebastienros What do you think about a custom execution strategy to fix this problem for sql? We should follow up with the EF team as well to see if this could be baked in.

I don't think we should be adding custom execution strategies to Aspire. It isn't scalable because as soon as the user wants to write their own, ours no longer works. I think the EF team should be consulted on what the appropriate action is here.

The main issue is 1 above on Mac (and assume Linux) and doesn't reproduce on Windows since the transient errors are being handled by the EF execution strategy. Addressing that should alleviate any specific retry logic in the application.

This seems like an EF bug. Why would it work on Windows, but not on Mac (and presumably Linux)?

This seems like an EF bug. Why would it work on Windows, but not on Mac (and presumably Linux)?

It might be a different error, that's not retried.
@tjementum What's the value of .Errors.Select(e => e.Number) for the exception that you get?

@AndriySvyryd , here is what i see if this helps.  Looks like different error
Windows
A transient exception occurred during execution. The operation will be retried after 0ms. Microsoft.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) ---> System.ComponentModel.Win32Exception (10054): An existing connection was forcibly closed by the remote host.
Mac
Microsoft.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - 20) ---> System.ComponentModel.Win32Exception (203): Unknown error: 203 at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)

@dbreshears Ok, but we need the error numbers to be able to reliably detect this in code. The numbers in the message generally don't match the ones in the exception instance.

@AndriySvyryd , looks like 203 on the Mac is the only error code in the Errors collection.     On Windows looks like it is 10054 when setup under the debugger to break on the exception.

Filed https://github.com/dotnet/efcore/issues/33260

Can we make the EF core components handle this until EF makes that change? That's  a .NET 9 change no?

@dbreshears And does the .InnerException contain a Win32Exception on a Mac?

Has anoyone simply tried to increase the default connection timeout to more than the default 15 seconds?

Can we make the EF core components handle this until EF makes that change? That's a .NET 9 change no?

Looks like @AndriySvyryd made an 8.0 fix/backport - https://github.com/dotnet/efcore/pull/33261.

So we can close this?

So we can close this?

I don't understand how you can close this. Even your samples do not work. For example, now you made this DatabaseMigrations sample, and it does not work on macOS and fails right out of the box (see screenshot). I assume this works on Windows, so clearly there is a bug in how this behaves on Mac (and presumably Linux).

It might be that a fix is needed in EF Core, but since you depend on EF Core, the bug is also in Aspire. At the very minimum, please update your samples to show how Aspire is supposed to work.
I know Microsoft FTEs only care about Windows users, but as far as I know, you are committed to being cross-platform, and this does not work on macOS.
One great solution would be if you made it possible to ensure that dependencies were running before starting things. This would not only solve this issue but also the fact that Aspire often fails the very first time you run the Apphost when you have to download docker images (e.g., 1.5 GB for the SQL server and 130 MB for Redis, etc.). This may take minutes, and even if you fix this bug, the API will timeout. I see this every time someone is cloning our Aspire solution.
It could look something like this:
var builder = DistributedApplication.CreateBuilder(args);

var sqlServer = builder.AddSqlServer("default")
    .AddDatabase("weather"); //

builder.AddProject<WeatherApi>("WeatherApi")
    .WithReference(sqlServer, ensureDependenciesStartup: true); // Proposed solution

builder.Build().Run();

Another solution that would be awesome would be to tell Aspire that dependencies should keep running (I often want to explore my SQL data even if my .NET solution is not running). While this will not solve the first-time issue, it would mean I don't have to wait ~10 seconds every time I start the AppHost.
var builder = DistributedApplication.CreateBuilder(args);

var sqlServer = builder.AddSqlServer("default")
    .AddDatabase("weather")
    .KeepContainerRunning(); // Proposed solution

builder.AddProject<WeatherApi>("WeatherApi")
    .WithReference(sqlServer);

builder.Build().Run();

@tjementum I think there has been a regression in SqlClient - can you try to add this to your connection string:
ConnectRetryCount=0

@tjementum I think there has been a regression in SqlClient - can you try to add this to your connection string:
ConnectRetryCount=0

The connection string is generated by Aspire, so I don't know how to do that. But if that is the case, then this is the fix the Aspire team needs to implement.
You can see an example here: https://github.com/tjementum/AspireWithSqlServer (and the dirty workaround here).

I am looking into this

I was able to repro the issue locally using WSL. I tried the fix in EF Core but it didn't solve the problem so I debugged it. The first exception is 203 and EF retries correctly (the inner exception is correct too), but then I get a number 0 with this message:
Microsoft.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - Success)
   at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at Microsoft.Data.SqlClient.TdsParserStateObject.ThrowExceptionAndWarning(Boolean callerHasConnectionLock, Boolean asyncClose)
   at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
   at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync()
   at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket()
   at Microsoft.Data.SqlClient.TdsParser.ConsumePreLoginHandshake(SqlConnectionEncryptOption encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean& marsCapable, Boolean& fedAuthRequired, Boolean tlsFirst, String serverCert)
   at Microsoft.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnectionString connectionOptions, Boolean withFailover)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, Boolean applyTransientFaultHandling, String accessToken, DbConnectionPool pool)
   at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at Microsoft.Data.ProviderBase.DbConnectionPool.WaitForPendingOpen()
--- End of stack trace from previous location ---
   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternalAsync(Boolean errorsExpected, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternalAsync(Boolean errorsExpected, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenAsync(CancellationToken cancellationToken, Boolean errorsExpected)
   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.<>c__DisplayClass20_0.<<ExistsAsync>b__0>d.MoveNext()
ClientConnectionId:86207f62-55b7-4db8-811a-4b45ea17c8a8

Then I updated the retry logic in EF to handle 0 also and @tjementum 's hack was not required anymore. I'll let the EF team be judge of how to interpret error 0 but I would risk thinking the problem lies in SqlClient.
@AndriySvyryd if you need more info on debugging this feel free to ping me.

error: 0 - Success

Yeah, this looks like a SQLClient issue. Could you file it at https://github.com/dotnet/SqlClient ?

I don't think there is anything to do on Aspire's side, but I don't feel like closing this issue either so we can remember to track the progress. If EF had to do something it would be to also catch 0 error codes, and I believe it's not a solution.

Track in this milestone or do we move it?

Given it's still not reliable after the EF Core fix due to the 0 errors and this still requires a workaround, might be a good idea to keep open to track the scenario and link to the issue with SqlClient.

The samples were updated for preview.5 to include retrying for this error and is now verified on Ubuntu as part of CI. Can you check again on mas os?

Can you check again on macOS?

It kind of works. The log is spammed with exceptions on startup, but now it does eventually starts.

We have a zero tolerance for warnings and exceptions, so for now I prefer a more elegant handling. E.g., this is what I have in my own repository.
.
PS: I would LOVE if you would make it possible to keep the SQL Server running instead of starting and stopping it with Aspire (plus the option to restart individual Aspire resources). Working with Aspire is unbearably slow, as everything has to stop and start every time you change a comma in the code (from the screenshot above, you can see it took 20 seconds). It's so bad that we are considering going back to Docker Compose, where it takes a couple of seconds to restart. Let's just say that not all developers think Aspire is an upgrade.

Would you consider submitting a PR to the samples repo with your improve error handling?
In terms of container persistence. We've heard feedback on this. Its something we want to do we just need to make sure we deal with a bunch of the corner cases:

How do we keep track of the state to say container X represents resource Y.
How do we decide when we should stop and restart the container anyway (e.g. env changes).
If things get into a bad state, what is the user experience for blowing everything away.

Regarding the different retry logic, I'd prefer any samples use the product resiliency features rather than manual loops with no backoff. It should be possible to create an EF Core execution strategy that's as simple as a retry loop with 30 iterations and a fixed one second between retries (although fixed retry intervals are generally not recommended).
Regarding the performance concerns, if you're not already, you may want to try using bind mounts or volumes for the database containers so that they don't need to perform initialization during every startup. I've found that the SQL Server container has a particularly long initialization routine if it doesn't have a persisted data directory.

https://github.com/davidfowl/WaitForDependenciesAspire/ is another solution for this problem - A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - 20) is the error you get if you try to connect to SQL server before it's fully initialized

Here's my workaround for macOS - use the built-in strategy on startup but extending it with an additional error number 0 which I receive on mac when SQL Server container is not ready:
using (var scope = app.Services.CreateScope())
{
    var dbContext = scope.ServiceProvider.GetRequiredService<CustomerDbContext>();

    var strategy = new SqlServerRetryingExecutionStrategy(dbContext, 10,
        TimeSpan.FromSeconds(5), new[] { 0 });

    await strategy.ExecuteAsync(async () =>
    {
        var dataFactory = scope.ServiceProvider.GetRequiredService<DataFactory>();
        await dbContext.Database.EnsureDeletedAsync();
        await dbContext.Database.EnsureCreatedAsync();
        await dataFactory.SeedAsync();
    });
}

This is the similar to the workaround I put in the samples https://github.com/dotnet/aspire-samples/blob/98e9c0eea6f8111ef3e4d45546d098b9de61ea65/samples/Shared/RetryingSqlServerRetryingExecutionStrategy.cs

I believe this is fixed in EF 9? @AndriySvyryd ?

This issue can be closed as it's tracked elsewhere -
https://github.com/dotnet/SqlClient/issues/2438
This shouldn't be an issue if WaitForResource is used,
otherwise use the execution strategy https://github.com/dotnet/aspire-samples/blob/98e9c0eea6f8111ef3e4d45546d098b9de61ea65/samples/Shared/RetryingSqlServerRetryingExecutionStrategy.cs


Great

Beautiful project. Good Sensations

Yes
Pada tanggal Min, 18 Jul 2021 04.29, Tbparseval @.***>
menulis:

Beautiful project. Good Sensations
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Aircoin-official/AirCash/issues/6, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUY5KGUVSIVJ6RLV2H3JB7LTYHY2RANCNFSM5AROCUOA
.

🔥🔥🔥

what is fork and clone ?

Good

good project i love this air

Great project


suppress error output to terminal

rofi-mpc is giving output to terminal, if we get out of  any uncompleted task.
is there any option to supress output to terminal?
Traceback (most recent call last):
  File "/home/xxxx/Downloads/rofi-mpc/./rofi-mpc", line 131, in <module>
    res = mpc_command_result(opts_data)
  File "/home/xxxx/Downloads/rofi-mpc/./rofi-mpc", line 48, in mpc_command_result
    raise Exception("Rofi exited before a selection was made")
Exception: Rofi exited before a selection was made

Thanks for the issue. At the moment there is not, but I agree that this should definitely be a command line option. When I have time I'll add a command line flag (-q and --quiet), and make the output prettier without the flag.

This should now be implemented with https://github.com/magnouvean/rofi-mpc/pull/2, simply use the -q or --quiet flags. Also without these flags the output should be much prettier! I will probably add a 1.0.2 release after this :). I'm closing this, but feel free to reopen if there are any issues regarding this still :)


You already have a subscription to this plan.

I upgraded an existing application, because I need the ability to add multiple coupons, to the latest version of the client and I am now unable to create a second subscription on an account like I was previously. I get 'You already have a subscription to this plan.' HttpStatus Code 442. Any ideas what is going on?

Nevermind. I did not have that option turned on my test account. The new client works without issue.


Cloudflare is too painful to be used on privacy respecting system

Maintainers: Please transfer this issue to an appropriate tracker.

Issue
Currently it's painful to use any Cloudflare website on a system that respects privacy, because Cloudflare requires:

Javascript

Cookies

hCaptcha (which needs to be passed on every cloudflare website multiple times a day)

Expected solution
Make it less painful to use Cloudflare services for privacy-concious people.

we do not field general cloudflare requests in this repository, please contact customer support. thanks


Plugin Geocoder not installed

I am trying to make use of the Geocoder plugin that comes with GoogleMaps but when I try to add a marker with the address obtained with the geocoder I get the error message saying that the Geocoder plugin is not installed, so the map loads fine but it shows me the marker With the title blank.

Same issue here... I've tried gitter (https://gitter.im/nightstomp/cordova-plugin-googlemaps) and G+ Community (https://plus.google.com/+AlexGouveaVasconcelos/posts/YgCrvcBWPiM), with no lucky yet.

It's the Geocoder plugin's problem

What does that mean, wf9a5m75?

I don't support the compatibility with other plugins.It's really depends on the plugins you installed. It's too much work.


✨ Observe gif in readme

#14  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @RTLS and the rest of your teammates on  Graphite


New command: Restore deleted Site Collection from Site Collection Recycle Bin

Usage
spo tenant recyclebinitem restore [options]
Description
Restores a deleted Site Collection from Site Collection Recycle Bin.
Options

Option
Description

-u, --url <url>
URL of the site to restore

Additional Information
this command will perform the same action as both the Restore-SPODeletedSite and the Restore-PnPTenantRecycleBinItem cmdlets.

Very nice suggestion @michaelmaillot. Would you like to give it a try and build this command?

Yes, with pleasure! 😁
Thx
Le mar. 18 févr. 2020 à 19:37, Waldek Mastykarz<EMAIL_ADDRESS>a écrit :

Very nice suggestion @michaelmaillot https://github.com/michaelmaillot.
Would you like to give it a try and build this command?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pnp/office365-cli/issues/1362?email_source=notifications&email_token=AKRYOYTEBK5G5WOZWM7LTYLRDQTGXA5CNFSM4KXBIPV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMDIPRA#issuecomment-587630532,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKRYOYVN25P64FJMZDSTP23RDQTGXANCNFSM4KXBIPVQ
.

All yours @michaelmaillot 👏

Great, can you assign it to me ? Thank you.
As I started to work on it, I wanted to use the REST API method which is available and works. But I faced a question about the "retry" process. So I've posted my question here.
Or course, if anyone have an answer, feel free to share it in the mentioned post 🙂.
In the meantime, maybe I should test if the IsComplete property returns false (or the HasTimedout property returns true) and retry the same command with limited attempts.

Typically, we add everyone as contributor to the project after their first PR. So while the issue isn't assigned to you on GitHub, it's all yours and it's set as in progress so no one else will be working on it 👍


About images generation

Thanks for your great work!
I want to apply VMA to my own data and want to know how the images of sd_data are generated? I can only produce single-channel intensity images.

I'm not quite sure how a single-channel intensity image is transformed into a three-channel RGB image, as this is a step in the production process of a BEV (Bird's Eye View) image. The data I have received is already in the form of a three-channel RGB image. Perhaps you can try using cv2.applyColorMap to apply a pseudocolor mapping to the intensity map to achieve this transformation.

Thank you very much for your reply.


The calculation of spec_min and spec_max

Hi. I notice that for each dataset, you calculated and put the spec_min & spec_max in the config files (e.g. https://github.com/MoonInTheRiver/DiffSinger/blob/c2fb5b32502e1e7e4b2a077bd9d83bb1c39e2b4e/usr/configs/popcs_ds_beta6.yaml). How did you calculate these features? (so that we can calculate the consistent features with you).
Thank you very much.

uncomment this part of codes:
https://github.com/MoonInTheRiver/DiffSinger/blob/82f1a1bf169a880db0b33c5fde117554aaddc05d/usr/diffsinger_task.py#L41

Hi, thanks for the answer above. However, I am still confused. Could you briefly explained what do spec_min and spec_max mean, and how can I calculate them if I use a different dataset? If I uncomment the above codes should I just delete spec_min and spec_max in the config files?


[Bug] False detection of shebang

Hi, @weituotian.
Thank you very good plugin.
I noticed.
if there is shebang in markdown malfunction occurs.
for example

Fixed the malfunction by correcting the source as follows.
--- before/example.py   2018-03-24 18:36:33.000000000 +0900
+++ after/example.py    2018-03-24 18:36:27.000000000 +0900
@@ -70,7 +70,7 @@
     def get_toc(self, begin, edit):

         # Search headings in docment
-        pattern_hash = "^#+?[^#]"
+        pattern_hash = "^#+?[^!#]"

         headings = self.view.find_all(pattern_hash)

thansk.

+1. It would be nice, if md_numbered_headers will ignore # symbols in all GitHub Flavored Markdown code blocks for any language.
Thanks.

@sky-joker @Kristinita
Great! this issue and the advice are excellent!
i am attempted to find a way to do that!


Login widget design

This plugin seems to have the headline above the SQRL QR code designed very similarly to a rounded button in a blue "primary" color. If we want to brand the SQRL login, then it would be optimal to have the color on a SQRL logo, maybe one that gets placed inside the QR code, which makes the QR code both appeal to be clicked on (people will try clicking on the colorful logo in the middle) as well as for scanning.

Hi @sesam
Maybe it's easier if you try the plugin out at either.
https://uhash.com/
https://repnet.app/
https://brianoflondon.me/
So you can see it in action.
The headline is the login button for offline clients. Adding these details to the QR code could be something we look into when we create our QR generator, but the current javascript library I use does not have that functionality built-in.
Best regards
Daniel

Thanks @kalaspuffar that helps a lot! Maybe the first two could be mentioned in the explanation somewhere? I assume the readme.txt is for the WordPress plugins directory, while the README.md is for visitors viewing the github repository primarily, and maybe the example sites and some paragraph explaning the two sites should then go into both of those readme documents? What is your opinion? PRs welcome?

Hi @sesam
Sounds great and PRs are always welcome to all my repositories.
Best regards
Daniel


fix: filter out lcov

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-4.5%) to 83.871%

Totals

Change from base Build<PHONE_NUMBER>:
-4.5%

Covered Lines:
26

Relevant Lines:
31

💛  - Coveralls

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Question: regarding fine-tuning with images

Is there a rough count on how many images to train a concept if not using a video? I know for LORA it can be as few as 9-10 but for DreamBooth, usually 2-3x that amount.

was there ever an answer to this question?


[HOLD]  "okay, got it." Modal has some extra empty space on top - reported by @Tushu17

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

You need to have a workspace and some members in it
Go to close account page
Type default contact method
Press close account button
View the "ok, got it" modal.

Expected Result:
There should be same space across borders
Actual Result:
Modal has too much extra empty space on top
Workaround:
unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: 1.1.49-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @Tushu17
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1648072472591519
View all open jobs on GitHub

Hold plz, this might be a dupe (which was reported first) for https://github.com/Expensify/App/issues/8404

Sorry, I just saw Matt's comment now so I'm removing engineering.

Gonna close this one, added @Tushu17 as reported by on https://github.com/Expensify/App/issues/8404


[Program]: Write a Dart program to convert time from 24-hour to 12-hour format

Description
Write a Dart program to convert time from 24-hour to 12-hour format
Input  : 12:05:45
Output : 12:05:45PM

How to contribute

Save the solution in program/program/convert-time-from-24-hour-to-12-hour-format/program/convert_time_from_24-hour_to_12-hour_format.dart file

!assign


Warnings as errors causes compilation failure

There are a few minor lines of code that are breaking the ability of BSK to compile when warnings are treated as errors.  Can we repair those items to ease compilation across different regimes?

I'll put in the PR, but the MRPBase class needs some constructors defined, and there's an extra semi-colon in rigidBodyKinematics.h
Super minor stuff...


Read standard licenses in JSON-LD format and remove dependencies on RDFa

Fixes issue #90, issue #146 and issue #145
Before merging, the license list URL need to be moved from https://spdx.org/licenses/preview to https://spdx.org/licenses
Signed-off-by: Gary O'Neall<EMAIL_ADDRESS>

Just peeking into a JSON-LD file at random, and I'm wondering what the spdx and doap entries are for.

This is an artifact of the Jenna library used to produce the JSON-LD and how it is being invoked.  These are declared namespaces used elsewhere in the SPDX documents.  Apparently, it Jena is including it in all the JSON-LD files, even if they are not used.
I plan to revisit the JSON-LD representation of the licenses in the future.  I'd really like to use an external context file which would make it very clean, compact and easier to maintain.  I just haven't had time to figure out how to generate it using the Jena libraries.  I spent a few hours earlier this week trying to figure it out and decided to wait until after the 3.1 release to pick it back up again.


Don't call transform if it isn't defined.

transform is called in _flush, even if the user didn't provide one.

Thanks! Will merge soon!

@nemo merge pls 🙂

@nemo Could this be merged?

Merged! Version 1.1.1 has the changes.


Provider Error when parsing replay using the odota parser

When trying to parse a replay with the odota parser I get a "no provider found" Exception in clarity:
skadistats.clarity.ClarityException: oops. no provider found for required usage point interface opendota.processors.warding.OnWardKilled
This issue had come up in a similar way before in the odota parser repo, where the bug seemed to be caused by using the wrong JRE. But after ensuring that I'm running 1.8, I am clueless as to what the cause of the error is. I've not gotten a response in the odota repo, so I was thinking, since it's an exception from within clarity, someone here might be able to help?
The setup is a fresh install of Eclipse with Maven, and freshly cloned odota repo.

You have to enable "annotation processors" when compiling clarity.

Simply enabling this option didn't seem to solve the problem, now I get the following Provirder error:
skadistats.clarity.ClarityException: oops. no provider found for required usage point interface skadistats.clarity.processor.packet.UsesPacketReader
I also missed another error that was further above, regarding SLF4J:
SLF4J: No SLF4J providers were found. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details.
I've unsuccessfully tried including a separate version of the slf4j-api-2.0.5.jar in the build path, but that didn't seem to solve the problem.
I'd really appreciate further assistance.

I got similar problem:
Exception in thread "main" skadistats.clarity.ClarityException: oops. no provider found for required usage point interface skadistats.clarity.examples.lifestate.OnEntityDying
	at skadistats.clarity.processor.runner.ExecutionModel.requireProvider(ExecutionModel.java:122)
	at skadistats.clarity.processor.runner.ExecutionModel.requireEventListener(ExecutionModel.java:144)
	at skadistats.clarity.processor.runner.ExecutionModel.requireProcessorClass(ExecutionModel.java:78)
	at skadistats.clarity.processor.runner.ExecutionModel.addProcessor(ExecutionModel.java:48)
	at skadistats.clarity.processor.runner.AbstractRunner.addProcessorsToModel(AbstractRunner.java:40)
	at skadistats.clarity.processor.runner.AbstractRunner.addProcessorsToModel(AbstractRunner.java:38)
	at skadistats.clarity.processor.runner.AbstractRunner.createExecutionModel(AbstractRunner.java:31)
	at skadistats.clarity.processor.runner.AbstractRunner.initWithProcessors(AbstractRunner.java:46)
	at skadistats.clarity.processor.runner.AbstractFileRunner.initAndRunWith(AbstractFileRunner.java:36)
	at skadistats.clarity.processor.runner.SimpleRunner.runWith(SimpleRunner.java:33)
	at busyliving.TableauProcessor.run(TableauProcessor.java:156)
	at busyliving.dirOperation.Main.main(Main.java:43)

I have the box for "Enable annotation processing" checked in the Idea settings but it doesn't work out. Shall I enable "annotation processors" elsewhere? Maybe in the Build.grardle.kts file?

I'm assuming you use 3.0 BusyLivingDota?
Try to enable it in your build.gradle.kts like so:
https://github.com/skadistats/clarity/blob/master/build.gradle.kts#L28

I see. "annotationProcessor("org.atteo.classindex:classindex:3.13")" works out here. GPT told me to use sth like "annotationProcessor("group:name:version")". I mistakenly thought I have to refer somewhere from Clarity. Thanks for the answer!

@FranzHahn
You don't need to checkout / build clarity itself. This makes it easier.
You just need to checkout clarity-examples, and use the provided documentation to run examples.
From there, you can customize an example to build your own.

I have the same issue with Kotlin project.
Exception in thread "main" skadistats.clarity.ClarityException: oops. no provider found for required usage point interface org.example.OnEntitySpawned

You have to enable annotation processors. Somehow.

Can u told how to do it with gradle(kts)?

I read previous comments, and try it, but doesn't help me.
I use it like in doc - gradle implementation in project.

I can't say what the problem is. Can you show your build.gradle.kts?

it's simpliest `plugins {
kotlin("jvm") version "1.9.22"
}
group = "org.example"
version = "1.0-SNAPSHOT"
repositories {
mavenCentral()
}
dependencies {
annotationProcessor("org.atteo.classindex:classindex:3.13")
implementation("com.skadistats:clarity:3.0.2")
testImplementation("org.jetbrains.kotlin:kotlin-test")
}
tasks.test {
useJUnitPlatform()
}`

From my perspective, this is all that's needed.
Where is @OnEntitySpawned defined? In your package org.example, meaning you copied it over from clarity-examples?
Maybe you do not have the class that provides this event?
In clarity-examples, it is here: https://github.com/skadistats/clarity-examples/blob/master/src/main/java/skadistats/clarity/examples/lifestate/SpawnsAndDeaths.java

Notice
@Provides({ OnEntitySpawned.class, OnEntityDying.class, OnEntityDied.class })

If you have no class that has this, then that's your problem.


start using pnpm

we discussed this in the Tooling team and it turns out that the PR was wrong, but not because of the pnpm version. I dropped the node version that CI was using to the same that was in volta before this PR 👍


[5.1] Always give known-empty class properties a zero offset in the static layout.

Field offset vectors are always filled out with either zero or the static layout's offset, depending on the metadata initialization strategy.  This change means that the static layout's offset will only be non-zero for properties with a statically-known layout.  Existing runtimes doing dynamic class layout assign class properties a zero offset if the field offset vector entry is zero and the property is zero-sized.  So this effectively brings the compiler into accord with the runtime (for all newly-compiled Swift code, which will eventually be all Swift code because the current public releases of Swift 5 are not yet considered ABI-stable) and guarantees a zero value for the offset everywhere.
Since the runtime will agree with the compiler about the zero value of the offset, the compiler can continue to emit such offset variables as constant.  The exception to this rule is if the class has non-fragile ObjC ancestry, in which case the ObjC runtime (which is not aware of this special rule for empty fields) will attempt to slide it along with everything else.
Fixes rdar://48031465, in which the FixedClassMetadataBuilder for a class with a legacy-fixed layout was writing a non-zero offset for an empty field into the field offset vector, causing the runtime to not apply the special case and thus to compute a non-zero offset, which it then attempted to copy into the global field offset variable, which the compiler had emitted as a true-constant zero.
This is the 5.1 version of #22738.

@swift-ci Please test.

Build failed
Swift Test Linux Platform
Git Sha - 270808baff836b55b356b8f081585b43e2507a44

Build failed
Swift Test OS X Platform
Git Sha - 270808baff836b55b356b8f081585b43e2507a44

@swift-ci Please test.


Pasting an HTML  does not download the image in the backend but links to the original image URL which is not obvious to the end-user

This takes place in:

TextBlockEdit
HtmlSlateWidget
and maybe also in RichTextWidget

Maybe it is more user friendly to download the image inside the backend and use the newly generated URL in the Slate tree.

I think this problem should be handled only in the TextBlockEdit, where it's obvious what the solution is (upload an image to the nearest possible image container).


test by default on linux, osx, win

@jmartin-tech what's a good way of merging this?

Looks like there are some adjustments need to pass the test in github actions, we can add resolution to those to this PR and once passing this merge will be straight forward.


Unable to download from BBC iPlayer: Coco https://www.bbc.co.uk/iplayer/episode/m000qq5v/coco

output:
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'https://www.bbc.co.uk/iplayer/episode/m000qq5v', u'--verbose']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2020.12.22
[debug] Python version 2.7.16 (CPython) - Linux-5.4.72-v7+-armv7l-with-debian-10.6
[debug] exe versions: ffmpeg 4.1.6-1, ffprobe 4.1.6-1
[debug] Proxy map: {}
[bbc.co.uk] m000qq5v: Downloading video page
[bbc.co.uk] m000qq5v: Downloading playlist JSON
[bbc.co.uk] m000qq5s: Downloading media selection XML
ERROR: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 803, in wrapper
return func(self, *args, **kwargs)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 824, in __extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 532, in extract
ie_result = self._real_extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/bbc.py", line 592, in _real_extract
self._sort_formats(formats)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 1367, in _sort_formats
raise ExtractorError('No video formats found')
ExtractorError: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

This is a known issue which is fixed by at least two Pull Requests that have yet to be merged into the distributed product: my basic https://github.com/ytdl-org/youtube-dl/pull/23415 and the more general https://github.com/ytdl-org/youtube-dl/pull/26821.


Next release of wasi-sdk-22

I wanted to open this up and see if anyone had any objections to publishing a v22 release for wasi-sdk. I'm happy to drive using the instructions @abrown has added, but wanted to make sure beforehand there were no objections.

Sounds good to me.

I've created a tag which has kicked off a build

The release artifacts are not built correctly so I've deleted the tag.
One issue is https://github.com/WebAssembly/wasi-sdk/pull/409 where ./version.py was putting a git hash in the version number when it shouldn't. Another issue is CI built artifacts with a version number of 21.21... which should have been 22.0... and I am trying to figure out why and am being pretty unsuccessful.

I believe the second issue is https://github.com/WebAssembly/wasi-sdk/pull/410, I'll retry the release once those are merged

One issue is #409 where ./version.py was putting a git hash in the version number when it shouldn't. Another issue is CI built artifacts with a version number of 21.21... which should have been 22.0... and I am trying to figure out why and am being pretty unsuccessful.

Did my comment in #409 clear things up?

Yeah sounds good! I'll try a re-tag now and see how it goes

Ok https://github.com/WebAssembly/wasi-sdk/releases/tag/wasi-sdk-22 was produced just now and things look better. If other folks want to give some eyes on that I can hit the publish button later today or tomorrow.

Ok I've hit publish.

I opened https://github.com/WebAssembly/wasi-sdk/pull/414 to see if I could figure out where the extra m suffix came from.


fix(map_loader): map_loader package not working in UTM coordinates

Description

Related links

Fixes: #607
Tests performed

Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

Thanks for your contribution, it looks good so far!
Does this have a related issue? If so please add it to the description with a remark like: closes: #X
For similar keywords see here.
Please fill in the required fields in the PR template.

I updated my branch. @xmfcx  Can you check again. Thanks.

Thank you for contributions, I reviewed the code, it looks fine. But I need to check that the changes in map_loader affect the other modules or not? Did you test it? Please share more information in Notes for reviewers and Tests performed.


No Operation_ID generated for TelemetryClient logs

Hello,
We are migrating our 3.1 functions to .NET 5. After some troubles we have made everything work just fine, last piece we are missing is fully working Application Insights telemetry.
This is our Program.cs
public static async Task Main(string[] args)
{
    var host =
        new HostBuilder()
        .ConfigureFunctionsWorkerDefaults()
        .ConfigureAppConfiguration((hostingContext, configuration) =>
        {
            //this is  the new way to get root folder in isolated func
            var local_root = AppDomain.CurrentDomain.BaseDirectory;//, DIRECTORY_NAMEEnvironment.GetEnvironmentVariable("AzureWebJobsScriptRoot");
            var azure_root = $"{Environment.GetEnvironmentVariable("HOME")}/site/wwwroot";
            var actual_root = local_root ?? azure_root;

            Configuration = configuration.SetBasePath(actual_root)
            .AddJsonFile("local.settings.json", optional: true, reloadOnChange: true)
            .AddEnvironmentVariables()
            .Build();
        })
        .ConfigureLogging(options =>
        {
            var aiKey = Configuration[CustomAppSettingKeys.APP_INSIGHTS_KEY];
            //options.ClearProviders();
            options.AddConsole();
            options.AddApplicationInsights(aiKey, aiOptions =>
            {

            });

            options.SetMinimumLevel(LogLevel.Information);
        })
        .ConfigureServices((c,s) =>
        {
            var appInsightsInstrumentationKey = Configuration[CustomAppSettingKeys.APP_INSIGHTS_KEY];
            s.AddApplicationInsightsTelemetryWorkerService(aiOptions =>
            {
                aiOptions.EnableAdaptiveSampling = false;
                aiOptions.EnableQuickPulseMetricStream = false;
                aiOptions.InstrumentationKey = appInsightsInstrumentationKey;
            });

            s.AddLogging();

            SP = s.BuildServiceProvider();
            var logger = SP.GetService<ILogger<AllUsersRegularJobs>>();
            s.AddSingleton(typeof(ILogger), logger);
        }).
        UseServiceProviderFactory<IContainer>(f =>
        {
            var containerBuilder = new ContainerBuilder();
            return new AutofacProviderFactory(containerBuilder, Configuration, SP);
        })
        .Build();

    await host.RunAsync();
}

When I am reviewing logs locally during debug or within Azure Logstream

Even If I search in the app insights logs they are found, however for some reason they don't get the operation ID of the function execution

Resulting in situation where these logs are flying in outer space with no way to match them against function execution which has the operation_id populated

This was working fine with 3.1.
I have been trying multiple ways of adding app insights logging without any luck. Can someone suggest what am I doing wrong here?
Thanks

Hi, this issue is lying here for 14 days now any chance it will at least get triaged?

Hi, bumping into exactly the same problem. This is blocking our migration to the isolated workers, we need correlation to investigate issues etc..

Hi @sergevm, we gave up,
there seems to be a pull request waiting in the repo https://github.com/Azure/azure-functions-dotnet-worker/pull/548 that is bringing some logging features however it is waiting for https://github.com/Azure/azure-functions-host/pull/7593 and it seems there's no activity for some time..
Anyways what we have done is that we extracted all code from the functions into and executor class library where we are passing all required dependencies for funs and we maintain .net core 3.1 app until this gets some resolution.

@baki32 The issue for us is that we are migrating to EF Core 5 in our functions, which forces us to go to isolated workers in the first place because of incompatible version dependencies in the EF Core libraries

Hitting this now as well...
Any solutions / work arounds?

.Net 6 v4 functios do support in-proc again so just upgrade and don't use isolated. Unfortunatelly this seems to be way not Production ready and support is unfortunatelly very delayed.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Avi Dgany @.>
Sent: Tuesday, January 4, 2022 12:47:16 PM
To: Azure/azure-functions-dotnet-worker @.>
Cc: baki32 @.>; Mention @.>
Subject: Re: [Azure/azure-functions-dotnet-worker] No Operation_ID generated for TelemetryClient logs (#565)
Hitting this now as well...
Any solutions / work arounds?
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-functions-dotnet-worker/issues/565#issuecomment-1004741410, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFOIRFTJMU36ARQGUOG62YLUULM4JANCNFSM5BOT47KQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>

:/ Unfortunately net6 in-proc functions don't support net6 DI,  so we started going down the isolated path..

We are working that around, until it is supported, with AutoFac.
    public class OurContainerBuilder
    {
        private static bool isInitialized = false;
        private static object syncLock = new object();

        public static void Build(IConfigurationRoot config, ILogger log, bool useRealKV = false)
        {
            log.InformationWithPrefix("BUILDING CONTAINER");

            lock (syncLock)
            {
                if (isInitialized)
                {
                    log.InformationWithPrefix("CONTAINER IS ALREADY BUILT");
                    return;
                }

                Container.Setup(b =>
                {
                           //register dependencies
                });

                log.InformationWithPrefix("DONE BUILDING CONTAINER");

                isInitialized = true;
            }
        }
    }

public static class Container
    {

        public static IContainer container;

        public static void Setup(Action<ContainerBuilder> bootstrap)
        {
            if (container == null)
            {
                var builder = new ContainerBuilder();

                bootstrap(builder);

                container = builder.Build();
            }
        }

        public static TService GetInstance<TService>()
        {
            return container.Resolve<TService>();
        }

        public static void Clear()
        {
            container = null;
        }

        public static ILifetimeScope BeginLifetimeScope()
        {
            return container.BeginLifetimeScope();
        }
    }

Then in every function we just use the static method to ensure that container is built and resolving dependenciues usig Container.GetInstance
It is not perfect but it kind of does the trick... Still better than no telemetry logs 😂


isoWeek Problem yearchange 2018/2019

Hello,
i got a problem with the weekdays at the yearchange.
I get the days through the weeknumbers.
Here is my code:
for (let i = 1; i <= 7; i++) {       weekarray.push(moment().day(i).isoWeek(weeknumber).year(this.state.year));     }
in week 52 in year 2018 everything is ok but in week 1 of 2019 the 31.December is missing.
I don't know why.

Same here

The Problem goes on.
In 2019 every week starts with Thursday, because the 31.December is missing.
Some advice from someone?


Dead metric passing the check

I have a problem that when one of the metric stops working the check in Cabot continues to pass.
I would like to receive an email when the metric stops working.
Is there a way to do it?

You have to set "Expected num hosts" to 1 (or however many series you expect) in order to get alerts when the metric stops being collected


[Core][Bugfix][Perf] Introduce MPLLMEngine to avoid Avoid AsyncLLMEngine overheads

SUMMARY:

@njhill and I removed almost all the overhead from the OpenAI server, but still saw significant slowdown running in AsyncLLMEngine rather than LLMEngine on H100, including when we ran "headless" (e.g. with no uvicorn server).
This caused us to believe the asyncio event loop in AsyncLLMEngine was the root cause of the slowdown
This PR replaces AsyncLLMEngine with MPLLMEngine. MPLLMEngine works similarly to AsyncLLMEngine (i.e. it runs a background loop, accepts new requests, and streams requests back to the clients). We use zeromq as the message passing protocol rather than pulling from queues and pushing to generators
This PR also fixes the number of sockets in use by the RPCClient, avoiding all issues with Too Many Open Files

Summary Performance vs Offline:

pr
scenario
offline
serving
slowdown %

main
multistep
42.9
33.3
-22%

pr
multistep
42.9
40.3
-6%

main
single-step
34.8
14.9
-55%

pr
single-step
34.8
31.6
-9%

NOTE: the multistep performance on main is "less-bad" because we currently only stream 1/8 tokens. Once we enable incremental streaming, the performance will be closer to -50% on main.

NOTE: there is still some remaining performance to get by switching the inner loop to using protobufs

Multistep Performance
1xH100 PERFORMANCE BASELINE:
MODEL="meta-llama/Meta-Llama-3.1-8B-Instruct"
python3 benchmarks/benchmark_throughput.py --model $MODEL --dataset benchmarks/ShareGPT_V3_unfiltered_cleaned_split.json --num-scheduler-steps 8

1xH100 SERVING PERFORMANCE

Client:

MODEL="meta-llama/Meta-Llama-3.1-8B-Instruct"
python3 benchmarks/benchmark_serving.py --model $MODEL --dataset-path benchmarks/ShareGPT_V3_unfiltered_cleaned_split.json

Server:

MODEL="meta-llama/Meta-Llama-3.1-8B-Instruct"
vllm serve $MODEL --disable-log-requests --num-scheduler-steps 8 --max-model-len 8192

SUMMARY

branch
setup
throughput

main
offline
42.9

main
serving mp
33.3

main
serving --disable-frontend-multiprocessing
28.9

pr
serving mp
40.3

pr
serving --disable-frontend-multiprocessing
27.9

Single-Step Performance
1xH100 PERFORMANCE BASELINE:
MODEL="meta-llama/Meta-Llama-3.1-8B-Instruct"
python3 benchmarks/benchmark_throughput.py --model $MODEL --dataset benchmarks/ShareGPT_V3_unfiltered_cleaned_split.json

1xH100 SERVING PERFORMANCE

Client:

MODEL="meta-llama/Meta-Llama-3.1-8B-Instruct"
python3 benchmarks/benchmark_serving.py --model $MODEL --dataset-path benchmarks/ShareGPT_V3_unfiltered_cleaned_split.json

Server:

MODEL="meta-llama/Meta-Llama-3.1-8B-Instruct"
vllm serve $MODEL --disable-log-requests --max-model-len 8192

SUMMARY

branch
setup
throughput

main
offline
34.8

main
serving mp
14.9

pr
serving mp
31.6

TODOS:

battle test with high load (abort | HWM?)
improve robustness (startup / teardown)
feature set (ray, non-gpu, pipeline parallel, profiler)
hardening / unit tests for MPLLMEngine
tests passing

co-authored by @njhill
FIX https://github.com/vllm-project/vllm/issues/7920
BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

Transferred from https://github.com/vllm-project/vllm/pull/8092

/ready

The PR for MPLLMEngine is now this one here: @comaniac @youkaichao @joerunde @DarkLight1337 @simon-mo @KuntaiDu @njhill @robertgshaw2-neuralmagic

The PR for MPLLMEngine is now this one here: @comaniac @youkaichao @joerunde @DarkLight1337 @simon-mo @KuntaiDu @njhill @robertgshaw2-neuralmagic

Hello, it's a great honor to see your work. May I ask when this task will be published? I can't wait to give it a try.

I think we need to discuss the name of the new engine. MPLLMEngine is not illustrative enough to me.
before this change, we also use multiprocessing to spawn the process to hold the AsyncLLMEngine.

Some candidates for reference (just for reference):

ZMQLLMEngine, emphasize the fact that we use zmq for ipc communication
RPCLLMEngine, emphasize the fact that engine is in a separate process and the one who creates the engine object actually uses rpc to control that separate process
PollLLMEngine, emphasize the fact that we poll sockets instead of using asyncio

Some candidates for reference (just for reference):

ZMQLLMEngine, emphasize the fact that we use zmq for ipc communication
RPCLLMEngine, emphasize the fact that engine is in a separate process and the one who creates the engine object actually uses rpc to control that separate process
PollLLMEngine, emphasize the fact that we poll sockets instead of using asyncio

I like MQLLMEngine

QQ: I remember async llm engine has some logic to deal with pipeline parallel, but I cannot find it in the MQLLMEngine.
does it support pipeline parallel?

QQ: I remember async llm engine has some logic to deal with pipeline parallel, but I cannot find it in the MQLLMEngine.
does it support pipeline parallel?

Not yet. Hopefully will get to it tomorrow. Need to make the error handling robust first. This is top focus

thanks! I'm also pinging @andoorve for help

thanks! I'm also pinging @andoorve for help

That would be good. I think PP support should be a separate PR

/ready

load testing going well. an advantage of PUSH PULL sockets is that they do not drop messages even without setting hwm
I did notice that with 10k active requests with this design, the frontend can fall behind the engine. The E2E throughput much faster than before, but the logs look a bit funny

@robertgshaw2-neuralmagic we can discuss the PP part sometime this week if that's helpful

@robertgshaw2-neuralmagic we can discuss the PP part sometime this week if that's helpful

I would appreciate that. For now, Im going to use the AsyncLLMEngine if pp is detected.

Thanks @robertgshaw2-neuralmagic the updates look great. I pushed a small change for TP which may also help with the shutdown issue, but can work more on that tomorrow. I can help with the PP impl too.
I also still think we should probably just load the config directly in the client and then can get rid of all those RPCs; should also solve https://github.com/vllm-project/vllm/issues/8288.

Thanks @robertgshaw2-neuralmagic the updates look great. I pushed a small change for TP which may also help with the shutdown issue, but can work more on that tomorrow. I can help with the PP impl too.
I also still think we should probably just load the config directly in the client and then can get rid of all those RPCs; should also solve #8288.

@njhill - doesn’t that function get called in engine_step?

@njhill - doesn’t that function get called in engine_step?

@robertgshaw2-neuralmagic :facepalm: my bad, reverted

Looking good!
Just left some comments about tests- I think they could be cleaned up to rely on sleeps a bit less and run much faster, but not a huge deal since the whole test suite already takes forever and a day

seems this patch break start_profile and 'stop_profile` methods.  would you like to take a look? thanks in advance!


Bank transfer instructions reverted

Describe the bug
On Dec 15 I made an update to OCF's bank transfer instructions, to add EU account details and chance OCF's address, so they looked like this:

Today, Dec 23, I went back to make another edit, and it seems they have reverted to the previous version, without the EU details:

Can the correct updated version be put back, and can someone please look into why this happened? It's important the correct instructions stick in this setting.
P1 high frequency, high impact

@alanna : This is one me as I've explained at, https://opencollective.slack.com/archives/GFH4N961L/p1671745588840579?thread_ts=1671745380.675799&cid=GFH4N961L.


set_target_properties called with incorrect number of arguments

Describe the bug
===>  Performing out-of-source build
/bin/mkdir -p /usr/ports/net/ecal/work/.build
-- GCC detected - Adding flags
-- Module Path: /usr/ports/net/ecal/work/ecal-5.11.1/cmake;/usr/ports/net/ecal/work/ecal-5.11.1/cmake/Modules
-- Prefix Path:
-- Content of the message:
-- Version of this git repo: 11-eol-45116-gb58ddb1e7aeb
CMake Error at cmake/helper_functions/ecal_add_functions.cmake:149 (set_target_properties):
  set_target_properties called with incorrect number of arguments.
Call Stack (most recent call first):
  cmake/helper_functions/ecal_add_functions.cmake:170 (ecal_add_shared_library)
  contrib/ecalproto/CMakeLists.txt:40 (ecal_add_library)

CMake Error at cmake/helper_functions/ecal_add_functions.cmake:158 (set_target_properties):
  set_target_properties called with incorrect number of arguments.
Call Stack (most recent call first):
  ecal/pb/CMakeLists.txt:50 (ecal_add_static_library)

CMake Error at cmake/helper_functions/ecal_add_functions.cmake:149 (set_target_properties):
  set_target_properties called with incorrect number of arguments.
Call Stack (most recent call first):
  ecal/core_pb/CMakeLists.txt:52 (ecal_add_shared_library)

CMake Error at cmake/helper_functions/ecal_add_functions.cmake:149 (set_target_properties):
  set_target_properties called with incorrect number of arguments.
Call Stack (most recent call first):
  app/app_pb/CMakeLists.txt:57 (ecal_add_shared_library)

CMake Error at ecal/core/CMakeLists.txt:19 (project):
  VERSION ".." format invalid.

Desktop (please complete the following information):

OS: FreeBSD 13.1
Version 5.11.1

cmake-3.24.3

This happens when ecal is built from a tarball, not from git clone.

Hey Yuri, nice to see you checking back on eCAL!

Can you post your entire CMake Command line, so I can try replicating it?
What "tarball" are you using? The complete ecal-fat-source.tar.gz including submodules, or are you stitching together your own version with the repo-only-tarball provided by github?

Thanks!
It breaks because git fails to find the version.

Please answer the questions above, if you want us to help you.

eCAL uses git describe to figure out version information, which obviously won't work if you are building from a tarball.
What you will have to do it run CMake with a `-DECAL_BUILD_VERSION=5.y.z" to inject the version from the outside.
If you don't do it, however you should end up with eCAL version "0.0.0", which is not good, but still shouldn't produce the CMake error that you are describing.

seems to be resolved. Please reopen if I am wrong


val .pkl files for pre-training LAVILA Dual-Encoder

Dear authors,
Thanks for your brilliant work!
I'd like to re-produce the pre-training of LAVILA Dual-Encoder, but only find the .pkl files to construct training datasets. In main_pretrain.py, we can see that the pre-training code also requires .pkl files for val datasets, like ego4d_val.rephraser.no_punkt_top3.pkl and ego4d_val.narrator_63690737.return_10.pkl.
How could I get these .pkl files?
Thanks!

Hi @AlbertHuyb
Please take a look at this doc and in particular the narrating section and rephrasing section.
Best,
Yue

Thanks!


angularjs goto definition is not work

angularjs goto definition is not work

Can you share your code? The language service does not support AMD, which is a common way to setup an angularjs project.

Closing as more info needed.
@zongxinbo Can you please provide additional information about your project and what is not working as expected.
Thanks.


Worker node not join to EKS cluster 1.17

I have issues
I use module with tag v12.2.0 and create eks cluster with version 1.17, when all task completed, i cannot see worker node when type command kubectl get nodes
but when create eks cluster with version 1.15 then worker node join success. what wrong on me?
I'm submitting a...

[x ] bug report
[ ] feature request
[ ] support request - read the FAQ first!
[ ] kudos, thank you, warm fuzzy

What is the current behavior?
`module "eks" {
source  = "terraform-aws-modules/eks/aws/"
version = "12.2.0"
cluster_name = "eks-name"
vpc_id       = "......"
subnets      = [...]
cluster_version                 = "1.17" -> change 1.15, it's work.
cluster_endpoint_private_access = "true"
cluster_endpoint_public_access  = "true"
map_roles = [
...
]
worker_groups_launch_template = [
{
name                    = "example"
override_instance_types = ["c4.2xlarge", "c5.2xlarge", "m5.2xlarge"]
spot_instance_pools     = 4
asg_max_size            = 4
asg_desired_capacity    = 2
asg_min_size            = 2
kubelet_extra_args      = "--node-labels=kubernetes.io/lifecycle=spot"
public_ip               = false
autoscaling_enabled     = true
root_volume_size        = 50
pre_userdata            = "exec > >(tee /var/log/user-data.log|logger -t user-data -s 2>/dev/console) 2>&1"
}

]
}`
If this is a bug, how to reproduce? Please include a code sample if relevant.
What's the expected behavior?
Are you able to fix this problem and submit a PR? Link here if you have already.
Environment details

Affected module version:
OS:
Terraform version:

Any other relevant info

Same issue here

This is due to a feature/restriction implemented in kubernetes 1.16 as explained by gertjangaillet in https://github.com/terraform-aws-modules/terraform-aws-eks/issues/856#issuecomment-623155710
The kubernetes.io label namespace now has heavy restrictions. You need to use something else for your label. The linked issue suggested changing to node.kubernetes.io/lifecycle=spot

thanks. it's worked. Maybe my old code create cluster from version 1.14 and when i create new cluster with version 1.17 not work.


[EASI-3505, EASI-4076] updating apollo/client and node v20 🎉

EASI-3505, EASI-4076

Changes and Description

updated to node v20.11.1 LTS
remove apollo since it has been discontinued (end of life blog post)
updated apollo client to 3.9.6

How to test this change

yarn install
scripts/dev down && scripts/dev up
Verify all things are well

PR Author Review Checklist

[ ] Met the ticket's acceptance criteria, or will meet them in a subsequent PR.
[ ] Added or updated tests for backend resolvers or other functions as needed.
[ ] Added or updated client tests for new components, parent components, functions, or e2e tests as necessary.
[ ] Updated the Postman Collection if necessary.

PR Reviewer Guidelines

It's best to pull the branch locally and test it, rather than just looking at the code online!
Check that all code is adequately covered by tests - if it isn't feel free to suggest the addition of tests.
Always make comments, even if it's minor, or if you don't understand why something was done.

Converting back to draft for reasons mentioned in slack thread
https://oddball.slack.com/archives/C059QQA3HK5/p1710266403072569?thread_ts=1710260051.830179&cid=C059QQA3HK5


fully disable the logs

Checklist

[ ] I m looking to implement it with no actual logs

Describe the enhancement request
A clear and concise description of an implementation with no logs

@HXMCPP Hello! This is not currently supported in the WireGuard setup script in this project. Because the standard WireGuard package from your Linux distribution is installed by the script, you can look into this yourself by searching for e.g. WireGuard disable logging on the Internet.


Allow runtime.SetList() on an api.List

SetList doesn't allow api.List

Maybe the bot doesn't know about corporate CLAs?

I think so - it's flagged people with corp CLA almost exclusively

On Feb 15, 2015, at 1:32 AM, roberthbailey<EMAIL_ADDRESS>wrote:
Maybe the bot doesn't know about corporate CLAs?
—
Reply to this email directly or view it on GitHub.

LGTM


chore(tests)/declaration-consistency

Make tests declaration consistent

Codecov Report

Merging #185 (65cb929) into main (5cceca3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #185   +/-   ##
=======================================
  Coverage   98.75%   98.75%
=======================================
  Files          16       16
  Lines         241      241
  Branches       54       54
=======================================
  Hits          238      238
  Misses          3        3

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Performance?

I am running 2.17.5 on an old machine and it is MUCH faster than the 2.19.2 I just installed today. I understand this is not much info but I wanted to submit this before I forgot. I can flesh this out if helpful.
Thanks
Todd

Thanks for letting me know! Can you provide more information to help reproduce this? The invocation would be useful to start.
You can also try to set the amount of threads explicitly, maybe something changed around that?
Thank you

False alarm. Gotta go apples to apples.
root@rescue ~ # sync; echo 2 > /proc/sys/vm/drop_caches
root@rescue ~ # sync; echo 3 > /proc/sys/vm/drop_caches
root@rescue ~ # time dua_2.19.2 i /data

real    6m23.985s
user    3m44.412s
sys     4m3.708s
root@rescue ~ # sync; echo 1 > /proc/sys/vm/drop_caches
root@rescue ~ # sync; echo 2 > /proc/sys/vm/drop_caches
root@rescue ~ # sync; echo 3 > /proc/sys/vm/drop_caches
root@rescue ~ # time dua_2.17.5 i /data

real    6m33.963s
user    4m44.368s
sys     5m2.561s```

the filesystem has around 7 millions files added up to 43TB.

Thank you for such a wonderful tool! I use it all the time.

Todd

Thanks a lot! So it does look like the new version is using significantly more system resources, even though in the end it ends up being more or less in the same ballpark.
It's probably alright, but please let me know if there is anything else to do here.
PS: You might like PDU


can't get started

Hi recent changes were made to the directory structure and it seems that running installation via the current instructions in the readme doesn't work.
In addition, after I run ./install.sh, CLI states "Deploying CDK Application" and nothing else happens afterwards. The only thing that was created was a local image/container on my local machine's Docker. What are the next steps for getting this onto my  AWS account for real-time inference?
In the root readme it states, Navigate to the CloudFormation console and find the API endpoint URL (httpAPIUrl) from the stack output. however I'm not able to find the API endpoint on my account's cloudformation. Thank you.

Hi @InquestGeronimo - Thank you for the feedback.  I've updated the instructions to reflect the new directory structure.
Are you trying to follow on a local machine or AWS Cloud9?  I have just deployed and successfully tested this on a brand new AWS account from a Cloud9 instance (m5.large with resized 50G local storage volume).  Once deployed, the API endpoint URL will be displayed on the terminal.  Moreover, you can find the same info on the CloudFormation console --> MLServerlessStack --> Outputs tab.

Thanks @medarg, Just an FYI, it wasn't clear in the README that using Cloud9 is how you leverage AWS, while using terminal flow is only for local dev. Because in the past I've used terminal to interface with AWS via AWS CLI.

@InquestGeronimo README specifies to run ./install.sh if following along on a local x86 machine or ./cloud9_install.sh if on a Cloud9 instance.  Cloud9 is the preferred way to deploy this sample code as it comes pre-installed/pre-configured with all of the required dependencies.  You can still leverage a local machine as long as the required dependencies are present and configured (NodeJs and NPM, Typescript, Docker, AWS CLI and AWS CDK).


Add expiration rule to S3 bucket

Currently, builds will be kept forever in the S3 bucket. We should have a rule that expires builds after 30 days.

Done!


Refine tutorial.md for devops

Updated tutorial.md for devops

Added whitespaces around numbers and alphabet.
Fixed typo
Added some blank lines to refine

+1


When adding Data objects the pop up says data attributes

Small issue but can be confusing

I believe this is fixed now.
To refresh, suggest pressing Ctrl + F5.
Thanks for reporting, please re-open if it is not fixed.

All good. Thanks


Config

Investigate how someone can specify their API url and other options. Currently all hard coded.

Covered in alpha build #215


Option to activate env using virtphp

It would be great to have an option to activate the env using something like this:
virtphp activate EpisodeIV

Yes, yes it would. :)
@jwoodcock has been looking into this for a while now, and unfortunately, our current thinking is that it isn't possible. The issue is that we have to interact with your terminal shell session, and we can't really do that without hijacking your entire shell, something we're not comfortable doing. I'll let Jacques add any additional details as he's the one that's looked into it.

Yes, I tried some hacks here and it didn't work, since when we call commands from within PHP it uses a new shell environment.
I'm using Python's virtualenv for a while now and there we also need to source a file to activate the env.
Well, if I find something useful I'll let you guys know about it :)

Thanks for the suggestion, @InFog. I've been looking at the source code for phpbrew and thinking through ways to refactor VirtPHP accordingly. I hope to have time in the near future to devote to making a proof-of-concept refactoring that I can submit for review in a pull request.

@InFog so virtualenvwrapper allows you to do this by having you source a pre-file on each shell-session start. This dumps a TON of functions into your session that you can use, including an activate command.
virtualenv actually has the same issue we have. In order to source a file using just virtualenv, you have to provide a full path.
For us, I found a way to simplify the activation process and have submitted PR #57, we're just bad at finishing reviews apparently- *cough cough @ramsey @jakerella. This updated functionality will allow you to type virtphp activate myenv and do two things. 1) if you have a compatible clipboard, copy the source command to it which you can just paste and it will activate the environment. 2) Output the source command with full environment path so all you have to do it copy and paste.
For now, that's the best we can do. I'll be interested to see what @ramsey comes up with in his refactoring, but whatever it is, it'll depend on dumping functions into the shell session.

#57 is not bad at all. I mean, it's a good option and I would like to use it :+1:

Like I said, everyone should take a look at how phpbrew does this. They do it in a really smart way. It's what I'd like to do, but it will require a full refactor, I think.

Any chance of the cliff notes?
Jacques Woodcock
<EMAIL_ADDRESS>615-293-0328
On Jan 5, 2015, at 9:02 AM, Ben Ramsey<EMAIL_ADDRESS>wrote:

Like I said, everyone should take a look at how phpbrew does this. They do it in a really smart way. It's what I'd like to do, but it will require a full refactor, I think.
—
Reply to this email directly or view it on GitHub.

Not today. Maybe I can write up something later this week.d

so what are we waiting on to get the #57 approved?

@jwoodcock Just reviewed, only one real suggested change, then nit-picky stuff.

Nothing, I guess. I was going to try to take a stab at a PR refactoring, as I said, but I haven't had time. Since I'm moving so slow on that, we should go ahead and just accept #57.

Just saw Jordan's notes. Will review and get an updated PR.

Nice! So I think this issue can be closed, since all the work is being done in #57 :)
Thanks, people!