How do I execute this project?

I only want to execute the trigger part for SQL.

We have docs here : https://github.com/Azure/azure-functions-sql-extension/blob/main/docs/BindingsOverview.md#trigger-binding
And samples here : https://github.com/Azure/azure-functions-sql-extension/tree/main/samples/samples-csharp/TriggerBindingSamples (see other folders for other languages)
Let us know if you still have any questions!

I read it.
I see you have created the database in the project.
I only want to execute the samples-python from vs code.
How do I execute the code from the VS Code?
Is it possible later on I want to add my database connection in the project to monitor my project.
Please guide me I downloaded the entire main branch and then I hit
func start --build
But I'm getting errors in the cmd What I'm doing wrong? I installed the azure functions extensions

@Charles-Gagnon
Microsoft.Azure.WebJobs.Host: Error indexing method 'Functions.ProductsTrigger'. Microsoft.Azure.WebJobs.Extensions.Sql: ConnectionStringSetting 'SqlConnectionString' is empty in your function app settings, please update the setting with a valid SQL connection string.
[2023-09-25T19:06:56.176Z] Error indexing method 'Functions.ProductsTrigger'
[2023-09-25T19:06:56.179Z] Microsoft.Azure.WebJobs.Host: Error indexing method 'Functions.ProductsTrigger'. Microsoft.Azure.WebJobs.Extensions.Sql: ConnectionStringSetting 'SqlConnectionString' is empty in your function app settings, please update the setting with a valid SQL connection string.
[2023-09-25T19:06:56.184Z] Function 'Functions.ProductsTrigger' failed indexing and will be disabled.
[2023-09-25T19:06:56.187Z] Microsoft.Azure.WebJobs.Host: Error indexing method 'Functions.ProductsTriggerLeasesTableName'. Microsoft.Azure.WebJobs.Extensions.Sql: ConnectionStringSetting 'SqlConnectionString' is empty in your function app settings, please update the setting with a valid SQL connection string.
[2023-09-25T19:06:56.190Z] Error indexing method 'Functions.ProductsTriggerLeasesTableName'
[2023-09-25T19:06:56.192Z] Microsoft.Azure.WebJobs.Host: Error indexing method 'Functions.ProductsTriggerLeasesTableName'. Microsoft.Azure.WebJobs.Extensions.Sql: ConnectionStringSetting 'SqlConnectionString' is empty in your function app settings, please update the setting with a valid SQL connection string.
The listener for function 'Functions.TimerTriggerProducts' was unable to start.
[2023-09-25T19:13:31.254Z] The listener for function 'Functions.TimerTriggerProducts' was unable to start. Azure.Core: Retry failed after 6 tries. Retry settings can be adjusted in ClientOptions.Retry. (No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:10000)) (No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:10000)) (No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:10000)) (No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:10000)) (No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:10000)) (No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:10000)). Azure.Core: No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:10000). System.Net.Http: No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:10000). System.Net.Sockets: No connection could be made because the target machine actively refused it.
[2023-09-25T19:13:31.263Z] Host started (395363ms)
[2023-09-25T19:13:31.264Z] Job host started
[2023-09-25T19:13:31.280Z] The 'ProductsTrigger' function is in error: Microsoft.Azure.WebJobs.Host: Error indexing method 'Functions.ProductsTrigger'. Microsoft.Azure.WebJobs.Extensions.Sql: ConnectionStringSetting 'SqlConnectionString' is empty in your function app settings, please update the setting with a valid SQL connection string.
[2023-09-25T19:13:31.283Z] The 'ProductsTriggerLeasesTableName' function is in error: Microsoft.Azure.WebJobs.Host: Error indexing method 'Functions.ProductsTriggerLeasesTableName'. Microsoft.Azure.WebJobs.Extensions.Sql: ConnectionStringSetting 'SqlConnectionString' is empty in your function app settings, please update the setting with a valid SQL connection string.
Authorization:REDACTED
[2023-09-25T19:13:17.090Z]    at Azure.Core.Pipeline.HttpClientTransport.ProcessAsync(HttpMessage message, Boolean async)
[2023-09-25T19:13:17.096Z] client assembly: Azure.Storage.Blobs
[2023-09-25T19:13:17.098Z]    at Azure.Core.Pipeline.HttpPipelineTransportPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory1 pipeline) [2023-09-25T19:13:17.104Z]    at Azure.Core.Pipeline.ResponseBodyPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory1 pipeline, Boolean async)
[2023-09-25T19:13:17.106Z]    at Azure.Core.Pipeline.LoggingPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory1 pipeline, Boolean async) [2023-09-25T19:13:19.087Z] Request [26ef9b18-cddc-40eb-968e-371764a0e9fc] exception Azure.RequestFailedException: No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:10001) [2023-09-25T19:13:19.090Z]  ---> System.Net.Http.HttpRequestException: No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:10001) [2023-09-25T19:13:19.092Z]  ---> System.Net.Sockets.SocketException (10061): No connection could be made because the target machine actively refused it. [2023-09-25T19:13:19.094Z]    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken) [2023-09-25T19:13:19.096Z]    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token) [2023-09-25T19:13:19.098Z]    at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken) [2023-09-25T19:13:19.100Z]    at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken) [2023-09-25T19:13:19.106Z]    --- End of inner exception stack trace --- [2023-09-25T19:13:19.107Z]    at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken) [2023-09-25T19:13:19.110Z]    at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) [2023-09-25T19:13:19.112Z]    at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) [2023-09-25T19:13:19.114Z]    at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(HttpRequestMessage request) [2023-09-25T19:13:19.120Z]    at System.Threading.Tasks.TaskCompletionSourceWithCancellation1.WaitWithCancellationAsync(CancellationToken cancellationToken)
[2023-09-25T19:13:19.122Z]    at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
[2023-09-25T19:13:19.124Z]    at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
[2023-09-25T19:13:19.126Z]    at System.Net.Http.HttpClient.g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
[2023-09-25T19:13:19.128Z]    at Azure.Core.Pipeline.HttpClientTransport.ProcessAsync(HttpMessage message, Boolean async)
[2023-09-25T19:13:19.131Z]    --- End of inner exception stack trace ---
[2023-09-25T19:13:19.135Z] Request [5a526b04-ca73-4598-ae51-af541d5a8ee2] exception Azure.RequestFailedException: No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:10000)
[2023-09-25T19:13:19.137Z]    at Azure.Core.Pipeline.HttpClientTransport.ProcessAsync(HttpMessage message, Boolean async)
[2023-09-25T19:13:19.139Z]  ---> System.Net.Http.HttpRequestException: No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:10000)
[2023-09-25T19:13:19.141Z]    at Azure.Core.Pipeline.HttpPipelineTransportPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory1 pipeline) [2023-09-25T19:13:19.145Z]    at Azure.Core.Pipeline.ResponseBodyPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory1 pipeline, Boolean async)
[2023-09-25T19:13:19.143Z]  ---> System.Net.Sockets.SocketException (10061): No connection could be made because the target machine actively refused it.
[2023-09-25T19:13:19.150Z]    at Azure.Core.Pipeline.LoggingPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory1 pipeline, Boolean async) [2023-09-25T19:13:19.152Z]    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken) [2023-09-25T19:13:19.156Z]    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token) [2023-09-25T19:13:19.158Z]    at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken) [2023-09-25T19:13:19.160Z]    at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken) [2023-09-25T19:13:19.162Z]    --- End of inner exception stack trace --- [2023-09-25T19:13:19.168Z]    at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken) [2023-09-25T19:13:19.169Z] An unhandled exception has occurred. Host is shutting down. [2023-09-25T19:13:19.170Z]    at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) [2023-09-25T19:13:19.172Z] Azure.Core: No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:10001). System.Net.Http: No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:10001). System.Net.Sockets: No connection could be made because the target machine actively refused it. [2023-09-25T19:13:19.174Z]    at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) [2023-09-25T19:13:19.182Z]    at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(HttpRequestMessage request) [2023-09-25T19:13:19.184Z]    at System.Threading.Tasks.TaskCompletionSourceWithCancellation1.WaitWithCancellationAsync(CancellationToken cancellationToken)
[2023-09-25T19:13:19.186Z]    at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
[2023-09-25T19:13:19.187Z]    at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
[2023-09-25T19:13:19.189Z]    at System.Net.Http.HttpClient.g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)

We do not have the ability to directly run the samples from our repo, they are meant more as a guide for someone getting started to see how to do certain things.
The error you're seeing seems to be because you have not defined a connection string
ConnectionStringSetting 'SqlConnectionString' is empty in your function app settings, please update the setting with a valid SQL connection string.
I would suggest starting with your own function project using Azure Function Core Tools and then using our README to get started making a SQL trigger from there.

It might be easier to start with an empty project and then copy over our samples to that project - that way you don't have to worry about anything else in our repo causing problems. But making changes to our project locally is fine too if you want to get started there! For example, you can add the connection string to your own server here
https://github.com/Azure/azure-functions-sql-extension/blob/main/samples/samples-csharp/local.settings.json#L6
To get a config that is similar to what you'd do in your own project.
And then yes, you can use the core tools to run your project locally! That's what func start will do - and after that you should be able to make changes in your database and see your function execute locally.

@Charles-Gagnon
I really appreciate your help on this.
I made changes in the project and added my connection string for the database.
Now I get this error:-
Failed to start SQL trigger listener for table: 'dbo.xrxImagesD', function ID: '8816252bf6717978'. Exception: System.InvalidOperationException: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100
[2023-09-25T19:37:48.987Z]    at Microsoft.Azure.WebJobs.Extensions.Sql.SqlBindingUtilities.VerifyDatabaseSupported(SqlConnection connection, ILogger logger, CancellationToken cancellationToken)
[2023-09-25T19:37:48.991Z]    at Microsoft.Azure.WebJobs.Extensions.Sql.SqlTriggerListener1.StartAsync(CancellationToken cancellationToken) [2023-09-25T19:37:48.994Z] Sending exception event: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100 [2023-09-25T19:37:48.998Z] [channel] received 47283336-d306-481e-8085-ff9175e8c846: RpcLog [2023-09-25T19:37:49.000Z] Received WorkerInitRequest, python version 3.10.11 (tags/v3.10.11:7d4cc5a, Apr  5 2023, 00:38:17) [MSC v.1929 64 bit (AMD64)], worker version 4.14.0, request ID 9e271a24-15bd-4a89-81e7-78f48e66a9a7 [2023-09-25T19:37:49.002Z] [channel] received 47283336-d306-481e-8085-ff9175e8c846: RpcLog [2023-09-25T19:37:49.013Z] The listener for function 'Functions.ProductsTrigger' was unable to start. [2023-09-25T19:37:49.015Z] The listener for function 'Functions.ProductsTrigger' was unable to start. Microsoft.Azure.WebJobs.Extensions.Sql: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100. [2023-09-25T19:37:49.021Z] Host started (838ms) [2023-09-25T19:37:49.023Z] Job host started [2023-09-25T19:37:49.030Z] File event source initialized. [2023-09-25T19:37:49.033Z] Debug file watch initialized. [2023-09-25T19:37:49.040Z] Diagnostic file watch initialized. [2023-09-25T19:37:49.042Z] Hosting started [2023-09-25T19:37:49.044Z] Host state changed from Initialized to Running. [2023-09-25T19:37:49.048Z] Startup operation '6ca71046-2cca-4baa-9499-e94c3c491801' completed. [2023-09-25T19:37:49.144Z] [channel] received 47283336-d306-481e-8085-ff9175e8c846: WorkerInitResponse [2023-09-25T19:37:49.147Z] Received WorkerInitResponse. Worker process initialized [2023-09-25T19:37:49.150Z] Worker capabilities: [SharedMemoryDataTransfer, true], [RawHttpBodyBytes, true], [TypedDataCollection, true], [WorkerStatus, true], [RpcHttpTriggerMetadataRemoved, true], [RpcHttpBodyOnly, true] [2023-09-25T19:37:49.275Z] Worker metadata: { "runtimeName": "python", "runtimeVersion": "3.10", "workerVersion": "4.14.0", "workerBitness": "AMD64" } [2023-09-25T19:37:49.281Z] Updating capabilities: { "SharedMemoryDataTransfer": "true", "RawHttpBodyBytes": "true", "TypedDataCollection": "true", "WorkerStatus": "true", "RpcHttpTriggerMetadataRemoved": "true", "RpcHttpBodyOnly": "true" } [2023-09-25T19:37:49.286Z] Adding jobhost language worker channel for runtime: python. workerId:47283336-d306-481e-8085-ff9175e8c846 [2023-09-25T19:37:49.291Z] Setting up FunctionInvocationBuffer for function: 'ProductsTrigger' with functionId: 'e1a581fa-6845-4039-a745-92bb12f69fe7' [2023-09-25T19:37:49.297Z] Sending FunctionLoadRequest for function: 'ProductsTrigger' with functionId: 'e1a581fa-6845-4039-a745-92bb12f69fe7' [2023-09-25T19:37:49.303Z] Worker process started and initialized. [2023-09-25T19:37:49.307Z] [channel] received 47283336-d306-481e-8085-ff9175e8c846: RpcLog [2023-09-25T19:37:49.309Z] Received WorkerLoadRequest, request ID 9e271a24-15bd-4a89-81e7-78f48e66a9a7, function_id: e1a581fa-6845-4039-a745-92bb12f69fe7,function_name: ProductsTrigger, [2023-09-25T19:37:49.310Z] [channel] received 47283336-d306-481e-8085-ff9175e8c846: RpcLog [2023-09-25T19:37:49.313Z] [channel] received 47283336-d306-481e-8085-ff9175e8c846: FunctionLoadResponse [2023-09-25T19:37:49.313Z] Successfully processed FunctionLoadRequest, request ID: 9e271a24-15bd-4a89-81e7-78f48e66a9a7, function ID: e1a581fa-6845-4039-a745-92bb12f69fe7,function Name: ProductsTrigger [2023-09-25T19:37:49.317Z] Received FunctionLoadResponse for function: 'ProductsTrigger' with functionId: 'e1a581fa-6845-4039-a745-92bb12f69fe7'. [2023-09-25T19:37:51.036Z] Retrying to start listener for function 'Functions.ProductsTrigger' (Attempt 1) [2023-09-25T19:37:51.048Z] Failed to start SQL trigger listener for table: 'dbo.xrxImagesD', function ID: '8816252bf6717978'. Exception: System.InvalidOperationException: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100 [2023-09-25T19:37:51.053Z]    at Microsoft.Azure.WebJobs.Extensions.Sql.SqlBindingUtilities.VerifyDatabaseSupported(SqlConnection connection, ILogger logger, CancellationToken cancellationToken) [2023-09-25T19:37:51.055Z]    at Microsoft.Azure.WebJobs.Extensions.Sql.SqlTriggerListener1.StartAsync(CancellationToken cancellationToken)
[2023-09-25T19:37:51.057Z] Sending exception event: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100
[2023-09-25T19:37:51.059Z] The listener for function 'Functions.ProductsTrigger' was unable to start.
[2023-09-25T19:37:51.061Z] The listener for function 'Functions.ProductsTrigger' was unable to start. Microsoft.Azure.WebJobs.Extensions.Sql: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100.
[2023-09-25T19:37:55.317Z] Retrying to start listener for function 'Functions.ProductsTrigger' (Attempt 2)
[2023-09-25T19:37:55.323Z] Failed to start SQL trigger listener for table: 'dbo.xrxImagesD', function ID: '8816252bf6717978'. Exception: System.InvalidOperationException: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100
[2023-09-25T19:37:55.325Z]    at Microsoft.Azure.WebJobs.Extensions.Sql.SqlBindingUtilities.VerifyDatabaseSupported(SqlConnection connection, ILogger logger, CancellationToken cancellationToken)
[2023-09-25T19:37:55.327Z]    at Microsoft.Azure.WebJobs.Extensions.Sql.SqlTriggerListener1.StartAsync(CancellationToken cancellationToken) [2023-09-25T19:37:55.329Z] Sending exception event: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100 [2023-09-25T19:37:55.331Z] The listener for function 'Functions.ProductsTrigger' was unable to start. [2023-09-25T19:37:55.337Z] The listener for function 'Functions.ProductsTrigger' was unable to start. Microsoft.Azure.WebJobs.Extensions.Sql: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100. [2023-09-25T19:38:00.692Z] Retrying to start listener for function 'Functions.ProductsTrigger' (Attempt 3) [2023-09-25T19:38:00.702Z] Failed to start SQL trigger listener for table: 'dbo.xrxImagesD', function ID: '8816252bf6717978'. Exception: System.InvalidOperationException: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100 [2023-09-25T19:38:00.705Z]    at Microsoft.Azure.WebJobs.Extensions.Sql.SqlBindingUtilities.VerifyDatabaseSupported(SqlConnection connection, ILogger logger, CancellationToken cancellationToken) [2023-09-25T19:38:00.707Z]    at Microsoft.Azure.WebJobs.Extensions.Sql.SqlTriggerListener1.StartAsync(CancellationToken cancellationToken)
[2023-09-25T19:38:00.712Z] Sending exception event: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100
[2023-09-25T19:38:00.714Z] The listener for function 'Functions.ProductsTrigger' was unable to start.
[2023-09-25T19:38:00.716Z] The listener for function 'Functions.ProductsTrigger' was unable to start. Microsoft.Azure.WebJobs.Extensions.Sql: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100.
[2023-09-25T19:38:09.567Z] Retrying to start listener for function 'Functions.ProductsTrigger' (Attempt 4)
[2023-09-25T19:38:09.574Z] Failed to start SQL trigger listener for table: 'dbo.xrxImagesD', function ID: '8816252bf6717978'. Exception: System.InvalidOperationException: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100
[2023-09-25T19:38:09.576Z]    at Microsoft.Azure.WebJobs.Extensions.Sql.SqlBindingUtilities.VerifyDatabaseSupported(SqlConnection connection, ILogger logger, CancellationToken cancellationToken)
[2023-09-25T19:38:09.578Z]    at Microsoft.Azure.WebJobs.Extensions.Sql.SqlTriggerListener1.StartAsync(CancellationToken cancellationToken) [2023-09-25T19:38:09.580Z] Sending exception event: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100 [2023-09-25T19:38:09.583Z] The listener for function 'Functions.ProductsTrigger' was unable to start. [2023-09-25T19:38:09.588Z] The listener for function 'Functions.ProductsTrigger' was unable to start. Microsoft.Azure.WebJobs.Extensions.Sql: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100. [2023-09-25T19:38:29.006Z] Retrying to start listener for function 'Functions.ProductsTrigger' (Attempt 5) [2023-09-25T19:38:29.012Z] Failed to start SQL trigger listener for table: 'dbo.xrxImagesD', function ID: '8816252bf6717978'. Exception: System.InvalidOperationException: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100 [2023-09-25T19:38:29.015Z]    at Microsoft.Azure.WebJobs.Extensions.Sql.SqlBindingUtilities.VerifyDatabaseSupported(SqlConnection connection, ILogger logger, CancellationToken cancellationToken) [2023-09-25T19:38:29.017Z]    at Microsoft.Azure.WebJobs.Extensions.Sql.SqlTriggerListener1.StartAsync(CancellationToken cancellationToken)
[2023-09-25T19:38:29.019Z] Sending exception event: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100
[2023-09-25T19:38:29.021Z] The listener for function 'Functions.ProductsTrigger' was unable to start.
[2023-09-25T19:38:29.026Z] The listener for function 'Functions.ProductsTrigger' was unable to start. Microsoft.Azure.WebJobs.Extensions.Sql: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100.
[2023-09-25T19:38:31.624Z] Host instance '00000000000000000000000048546A02' failed to acquire host lock lease: Azure.Core: No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:10000). System.Net.Http: No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:10000). System.Net.Sockets: No connection could be made because the target machine actively refused it.
[2023-09-25T19:38:59.727Z] Retrying to start listener for function 'Functions.ProductsTrigger' (Attempt 6)
[2023-09-25T19:38:59.734Z] Failed to start SQL trigger listener for table: 'dbo.xrxImagesD', function ID: '8816252bf6717978'. Exception: System.InvalidOperationException: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100
[2023-09-25T19:38:59.737Z]    at Microsoft.Azure.WebJobs.Extensions.Sql.SqlBindingUtilities.VerifyDatabaseSupported(SqlConnection connection, ILogger logger, CancellationToken cancellationToken)
[2023-09-25T19:38:59.739Z]    at Microsoft.Azure.WebJobs.Extensions.Sql.SqlTriggerListener`1.StartAsync(CancellationToken cancellationToken)
[2023-09-25T19:38:59.740Z] Sending exception event: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100
[2023-09-25T19:38:59.747Z] The listener for function 'Functions.ProductsTrigger' was unable to start.
[2023-09-25T19:38:59.749Z] The listener for function 'Functions.ProductsTrigger' was unable to start. Microsoft.Azure.WebJobs.Extensions.Sql: SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100.
This is how my locals.setting.json looks like
{
"IsEncrypted": false,
"Values": {
"AzureWebJobsStorage": "UseDevelopmentStorage=true",
"FUNCTIONS_WORKER_RUNTIME": "python",
"SqlConnectionString": "Server=Myserver.database.windows.net;Database=MyDataBase;User Id=myUSerId;Password=myPassword;",
"Sp_SelectCost": "SelectProductsCost",
"ProductCost": 100
}
}
My host.json did not change anything
{
"version": "2.0",
"logging": {
"applicationInsights": {
"samplingSettings": {
"isEnabled": true,
"excludedTypes": "Request"
}
},
"logLevel": {
"default": "Trace"
}
},
"extensionBundle": {
"id": "Microsoft.Azure.Functions.ExtensionBundle.Preview",
"version": "[4.*, 5.0.0)"
}
}
and my function.json is below
{
"bindings": [
{
"name": "changes",
"type": "sqlTrigger",
"direction": "in",
"tableName": "dbo.xrxImagesD",
"connectionStringSetting": "SqlConnectionString"
}
],
"disabled": false
}
I go to the directory azure-functions-sql-extension\samples\samples-python> and then hit func start --build to execute the project
Do you know what I'm doing wrong here?
I have done this setting on my database for which I'm adding triggers
ALTER DATABASE [SampleDatabase]
SET CHANGE_TRACKING = ON
(CHANGE_RETENTION = 2 DAYS, AUTO_CLEANUP = ON);
ALTER TABLE [dbo].[ToDo]
ENABLE CHANGE_TRACKING;
Again I really appreciate your help on this.

SQL bindings require a database compatibility level of 130 or higher to function. Current compatibility level = 100
The database you've specified has the compat level at 100, which unfortunately doesn't support the OPENJSON statement that is required by our extension. See https://github.com/Azure/azure-functions-sql-extension/blob/main/README.md#supported-sql-server-versions for more details. So you'll need to change the compat level to 130 or higher to be able to use the SQL extension.

@Charles-Gagnon
Thanks it is working fine on my DB and locally.
Whenever I'm making changes on the SSMS in the table then I can get the changes in my azure function app which I'm running locally. But when I make changes using the published app in the database those changes is not reflecting in the locally executed program. Do I have to publish my Azure function for this?
Also, after getting changes in the azure function I want to upload the image on the blob container and then I want to delete the binary string in the database using the Azure function code Can I do that?
Please let me know if you have any questions for me. I really appreciate your help and guidance.

Could you explain this a bit more?  But when I make changes using the published app in the database those changes is not reflecting in the locally executed program
What "app" is this? A function app or just some other application that is making modifications to your DB?
About your second question - you definitely can! Look into blob output bindings and SQL input bindings. You can have multiple bindings on one function - so you could you have your SQL-triggered function then also trigger the blob output binding and sql input binding in the same function.

@Charles-Gagnon
It is the web application that is making modifications on my DB. My Azure function is not able to catch those modifications.
Even if I run that web application locally on my computer I still not able to catch changes made by that application in azure function program.
I have one more question, Can I monitor one more database in the same azure function program?

And you're sure that the database/table being modified is the same one being monitored by your function?
Yes, you can monitor multiple databases/tables - but you will need a separate function for each.

Yes, it is monitoring same database but UserId in the connection string is different in web application. Is that the reason?
Can you please give me example how can I monitor the different database from same Azure Function?
I need to have two connection strings in function.json file and also do I need to use two index.json file?
Also, I also need to do the bulk transfer means I want to transfer all entries in my database to blob container.
How do I access the all entries in the database using this azure function program.(I need to access all entries in the database in loop)

User ID shouldn't make a difference. Could you file a separate issue for that and we can follow up with helping investigate that specific issue?
Unfortunately you can't monitor two separate DBs from the same function. You will need to create a separate function for each. These functions can be in the same function app though.
SQL input bindings can be used to retrieve data from a database, and then you'd use an output binding (such as the blob output binding) to take that data and push it elsewhere. The docs and samples should help with getting that set up.

Sure. I will create a new issue for this.
So you are saying we can publish two different projects in one Azure function App?
I will look into documents for the Bulk migrations.
@Charles-Gagnon Thanks for your help.

You can have 1 project that contains multiple functions (see the Azure Functions docs for information on how to do that using the core tools or something like VS Code), or you could split them into separate projects. It's up to you what one you'd prefer.


Fixed uninitialized error in check_for_events

Replaced uninitialised calls with MaybeUninit.

Thanks! Running cargo run --example samples (and others) no longer panics.
@ojhp this project has a policy of giving merge access to people who get code accepted. Would you be interested in that?
(note that none of the current maintainers including myself are able to devote time and effort to future development of tcod-rs, but I'll keep merging PRs when I get to it)

Thanks! Running cargo run --example samples (and others) no longer panics.
@ojhp this project has a policy of giving merge access to people who get code accepted. Would you be interested in that?
(note that none of the current maintainers including myself are able to devote time and effort to future development of tcod-rs, but I'll keep merging PRs when I get to it)

@tomassedovic Sure, I'm happy to help out when I get a chance. Just let me know if there's any contributors rules or anything.

@tomassedovic Sure, I'm happy to help out when I get a chance. Just let me know if there's any contributors rules or anything.

@ojhp the rules are just: open a PR instead of pushing directly, give others some time (1-2 days) before merging your own change, don't do anything malicious and don't be an arsehole.

I've sent you an invite.

Nice and simple, thanks!

Nice and simple, thanks!


Patch rubyzip CVE

I rule and have completed some work on Case Manager that's ready for review!
Not something we were extremely affected by or at risk of, but nonetheless.
This pull request makes the following changes:

bundle update selenium-webdriver (the parent library)

No issues

Not prod facing (we only use rubyzip as part of selenium-webdriver) so invoking godmode and merging.


Minimum tag for Random Float Shard

Currently there is a maximum tag
And to change the minimum I just use a math.subtract

This makes sense logically but with a minimum tag it might be better UX wise

Hey team! Please add your planning poker estimate with Zenhub @guusw @sinkingsugar @tdbe


Maintenance release testing for Safari input

Main issue is https://github.com/phetsims/scenery/issues/770 (Working around Safari's iOS 11.3+ passive events changes and lack of touch-action:none).
NOTE: Please go through one of the bottom "exemplar" sims first to see if there are any problems before testing other sims. If there is a problem with that one sim (or really any regression), please interrupt testing and let me know.
The main problem was that, for iPads/iPhones after iOS 11.3+, dragging anywhere in the sim will scroll the sim (like it's a normal web page). Testers should try out a public sim on our website to verify what the buggy behavior looks like. Each sim below should be tested to make sure that it does NOT have that issue (plus ~10-30 seconds of testing to make sure something crazy isn't going wrong).

[x] https://bayes.colorado.edu/dev/html/acid-base-solutions/1.2.12-rc.3/acid-base-solutions_en.html
[x] https://bayes.colorado.edu/dev/html/area-builder/1.1.7-rc.1/area-builder_en.html
[x] https://bayes.colorado.edu/dev/html/arithmetic/1.0.11-rc.1/arithmetic_en.html
[x] https://bayes.colorado.edu/dev/html/atomic-interactions/1.0.5-rc.1/atomic-interactions_en.html
[x] https://bayes.colorado.edu/dev/html/balancing-act/1.1.11-rc.1/balancing-act_en.html
[x] https://bayes.colorado.edu/dev/html/balancing-chemical-equations/1.1.11-rc.1/balancing-chemical-equations_en.html
[x] https://bayes.colorado.edu/dev/html/balloons-and-static-electricity/1.2.5-rc.1/balloons-and-static-electricity_en.html
[x] https://bayes.colorado.edu/dev/html/beers-law-lab/1.4.6-rc.1/beers-law-lab_en.html
[x] https://bayes.colorado.edu/dev/html/bending-light/1.1.8-rc.1/bending-light_en.html
[x] https://bayes.colorado.edu/dev/html/build-an-atom/1.6.1-rc.1/build-an-atom_en.html
[x] https://bayes.colorado.edu/dev/html/capacitor-lab-basics/1.5.1-rc.1/capacitor-lab-basics_en.html
[x] https://bayes.colorado.edu/dev/html/charges-and-fields/1.0.5-rc.1/charges-and-fields_en.html
[x] https://bayes.colorado.edu/dev/html/circuit-construction-kit-dc/1.0.2-rc.1/circuit-construction-kit-dc_en.html
[x] https://bayes.colorado.edu/dev/html/circuit-construction-kit-dc-virtual-lab/1.0.2-rc.1/circuit-construction-kit-dc-virtual-lab_en.html
[x] https://bayes.colorado.edu/dev/html/color-vision/1.1.11-rc.1/color-vision_en.html
[x] https://bayes.colorado.edu/dev/html/concentration/1.3.8-rc.1/concentration_en.html
[x] https://bayes.colorado.edu/dev/html/energy-skate-park-basics/1.1.7-rc.1/energy-skate-park-basics_en.html
[x] https://bayes.colorado.edu/dev/html/expression-exchange/1.1.1-rc.1/expression-exchange_en.html
[x] https://bayes.colorado.edu/dev/html/faradays-law/1.1.11-rc.1/faradays-law_en.html
[x] https://bayes.colorado.edu/dev/html/forces-and-motion-basics/2.3.1-rc.1/forces-and-motion-basics_en.html
[x] https://bayes.colorado.edu/dev/html/fraction-matcher/1.1.9-rc.1/fraction-matcher_en.html
[x] https://bayes.colorado.edu/dev/html/friction/1.4.1-rc.1/friction_en.html
[x] https://bayes.colorado.edu/dev/html/function-builder/1.0.11-rc.1/function-builder_en.html
[x] https://bayes.colorado.edu/dev/html/function-builder-basics/1.0.3-rc.1/function-builder-basics_en.html
[x] https://bayes.colorado.edu/dev/html/gene-expression-essentials/1.0.2-rc.1/gene-expression-essentials_en.html
[x] https://bayes.colorado.edu/dev/html/graphing-lines/1.2.2-rc.1/graphing-lines_en.html
[x] https://bayes.colorado.edu/dev/html/graphing-slope-intercept/1.0.2-rc.1/graphing-slope-intercept_en.html
[x] https://bayes.colorado.edu/dev/html/gravity-and-orbits/1.1.3-rc.1/gravity-and-orbits_en.html
[x] https://bayes.colorado.edu/dev/html/gravity-force-lab/2.1.3-rc.1/gravity-force-lab_en.html
[x] https://bayes.colorado.edu/dev/html/hookes-law/1.0.11-rc.1/hookes-law_en.html
[x] https://bayes.colorado.edu/dev/html/isotopes-and-atomic-mass/1.0.10-rc.1/isotopes-and-atomic-mass_en.html
[x] https://bayes.colorado.edu/dev/html/john-travoltage/1.3.2-rc.1/john-travoltage_en.html
[x] https://bayes.colorado.edu/dev/html/least-squares-regression/1.1.8-rc.1/least-squares-regression_en.html
[x] https://bayes.colorado.edu/dev/html/make-a-ten/1.0.4-rc.1/make-a-ten_en.html
[x] https://bayes.colorado.edu/dev/html/molarity/1.3.2-rc.1/molarity_en.html
[x] https://bayes.colorado.edu/dev/html/molecule-polarity/1.0.3-rc.1/molecule-polarity_en.html
[x] https://bayes.colorado.edu/dev/html/molecule-shapes/1.1.12-rc.1/molecule-shapes_en.html
[x] https://bayes.colorado.edu/dev/html/molecule-shapes-basics/1.1.10-rc.1/molecule-shapes-basics_en.html
[x] https://bayes.colorado.edu/dev/html/molecules-and-light/1.4.1-rc.1/molecules-and-light_en.html
[x] https://bayes.colorado.edu/dev/html/neuron/1.1.5-rc.1/neuron_en.html
[x] https://bayes.colorado.edu/dev/html/ohms-law/1.3.9-rc.1/ohms-law_en.html
[x] https://bayes.colorado.edu/dev/html/pendulum-lab/1.0.3-rc.1/pendulum-lab_en.html
[x] https://bayes.colorado.edu/dev/html/ph-scale/1.2.12-rc.1/ph-scale_en.html
[x] https://bayes.colorado.edu/dev/html/ph-scale-basics/1.2.12-rc.1/ph-scale-basics_en.html
[x] https://bayes.colorado.edu/dev/html/plinko-probability/1.1.3-rc.1/plinko-probability_en.html
[x] https://bayes.colorado.edu/dev/html/projectile-motion/1.0.3-rc.1/projectile-motion_en.html
[x] https://bayes.colorado.edu/dev/html/proportion-playground/1.0.2-rc.1/proportion-playground_en.html
[x] https://bayes.colorado.edu/dev/html/reactants-products-and-leftovers/1.1.11-rc.1/reactants-products-and-leftovers_en.html
[x] https://bayes.colorado.edu/dev/html/resistance-in-a-wire/1.4.1-rc.1/resistance-in-a-wire_en.html
[x] https://bayes.colorado.edu/dev/html/rutherford-scattering/1.0.8-rc.1/rutherford-scattering_en.html
[x] https://bayes.colorado.edu/dev/html/states-of-matter/1.0.3-rc.1/states-of-matter_en.html
[x] https://bayes.colorado.edu/dev/html/states-of-matter-basics/1.0.3-rc.1/states-of-matter-basics_en.html
[x] https://bayes.colorado.edu/dev/html/trig-tour/1.0.10-rc.1/trig-tour_en.html
[x] https://bayes.colorado.edu/dev/html/under-pressure/1.1.6-rc.1/under-pressure_en.html
[x] https://bayes.colorado.edu/dev/html/unit-rates/1.0.5-rc.1/unit-rates_en.html
[x] https://bayes.colorado.edu/dev/html/wave-on-a-string/1.1.10-rc.1/wave-on-a-string_en.html

Furthermore, the 6 sims here are exemplars of the 6 different patches that were used (because of incompatible changes made to Scenery between sim publications). For these, I would like testing with mouse/touch/stylus input done on a variety of platforms (including iPhone if possible), to see if this introduces input bugs. This includes dragging things while the pointer goes out of the window, how it behaves in iframes, how it works with gestures, or anything else that looks/feels buggy. For non-Safari based things, somewhat brief testing should be used (a good chance nothing changes), but for Safari-based things (desktop and mobile Safari) it changes a lot of how input may work, and I want to make sure it doesn't break things.

[x] https://bayes.colorado.edu/dev/html/acid-base-solutions/1.2.12-rc.3/acid-base-solutions_en.html
[x] https://bayes.colorado.edu/dev/html/ph-scale/1.2.12-rc.1/ph-scale_en.html
[x] https://bayes.colorado.edu/dev/html/gravity-and-orbits/1.1.3-rc.1/gravity-and-orbits_en.html
[x] https://bayes.colorado.edu/dev/html/balloons-and-static-electricity/1.2.5-rc.1/balloons-and-static-electricity_en.html
[x] https://bayes.colorado.edu/dev/html/projectile-motion/1.0.3-rc.1/projectile-motion_en.html
[x] https://bayes.colorado.edu/dev/html/circuit-construction-kit-dc/1.0.2-rc.1/circuit-construction-kit-dc_en.html

Assigning to @ariel-phet to prioritize.

Since this bug renders sims pretty unusable in our app, seems like next priority after Area Model 1.0

@jonathanolson @ariel-phet we have too many sims.
I tested on iOS 11.3, iOS 11.2.5, iOS 9.3.5, Win 10 all four browsers, macOS 10.13.14 Safari and Chrome, and our Android tablet. No regressions form this patch and the sims work correctly on iOS 11.3.

Oh and @lmulhall-phet did an iPad Pro iOS 11.3 with a stylus and didn't report any problems.

Thanks!


Unwanted transparency in Tilemap

Windows. Godot version 2.1.4
Issue description:
Unwanted transparency
Steps to reproduce:
Accidentally imported tiles with around 95% alpha value from Inkscape. Noticed slight transparency immediately in the tilemap, observed that I could faintly see the furthest background objects though the tiles.
I fixed the transparency issue and re-imported all the tiles. Still didn't fix anything in Godot, even though the transparency was gone in the actual tile assets. Made sure Opacity and Self Opacity of tilemap were set to 1. Tried nuking the tilemap and starting from scratch, duplicating the node, nothing worked. Tried using completely new tileset.res- this did work. However, any new tilesets built from the old tiles, even though they were fixed, did not work.
Finally, just for kicks, I tried setting the Opacity and Self-Opacity to 1.1, which reverted back to 1.0 correctly in the editor, and rebuilt my game. It worked, and the transparency is no longer there.
So the issue appears to be the tiles themselves, or the tileset.res itself. Is it possible it retains some sort of metadata about transparency and hangs onto it?
Also unsure about why setting the opacity to over 1.0 fixed it.
This might not be reproducible, but figured I'd post it anyway in case someone else ran into it.
Cheers

Are you sure your transparent tiles were not saved as local resources on the scene? That may explain why fixing the tileset didn't changed the alpha (different resources).

@eon-s I am guessing that is what happened, because if I edit the .tscn file, I see the opacity set to 1.1 still. If I change it back to 1.0, the slight transparency comes back.
How can I tell if they did? And if so, how can I over-write the local resources in a scene with new ones?

The scene (or tileset?) may include image data instead of a reference to the image file, you can see that on the "texture" property of the tileset too (if is pointing to the file or some resource in the scene file).

In my Tileset.tscn file, all of my tiles' "texture" property say "ExtResource", and at the top of the file each one has for example:
[ext_resource path="res://Scenes/Z1TS1Top.png" type="Texture" id=1]
In multiple levels, for example, the tileset is defined at the top of the .tscn file as:
[ext_resource path="res://Scenes/Tileset.res" type="TileSet" id=10]
In each TileMap object in the .tscn file, the tileset points to a resource such as:
tile_set = ExtResource( 4 )

Is ok that way, strange bug.

Ok, thanks for taking the time to walk me through the steps. I'll keep looking into it.


Release 3.1.0 in violation of semantic versioning?

Release 3.1.0 broke the build of lzma-rs (possibly among others). The reason seems to be the changed trait bound of crc::Digest:

https://docs.rs/crc/3.1.0/crc/struct.Digest.html: pub struct Digest<'a, I: Implementation>
https://docs.rs/crc/3.0.1/crc/struct.Digest.html: pub struct Digest<'a, W: Width>

As per my understanding this is not in line with semantic versioning requirements. Would it be possible to yank this version and fix this or publish it as 4.0 instead?
Thanks for being considerate of the wider eco system.

Thanks for reporting this, just yanked 3.1.0 and will investigate further.

Yup, this'll do it: https://github.com/gendx/lzma-rs/blob/168221a91f66000cf2424a62f9ffd18cf5fd91b7/src/encode/util.rs#L7. I suspect this is a somewhat uncommon use of the API, but it's still a breaking change that's not acceptable.
Unfortunately, I don't see an easy way to replace Width with Implementation when there are generic call sites explicitly referencing Width.
Will either have to rename Implementation to Width or release 4.0.0.

I have a solution for this that doesn't break semver: https://github.com/mrhooray/crc-rs/pull/115. Will do some more testing (incl. against lzma-rs before release 3.1.0).


Wrong guess on PyContextNLP

This project is biomedical research. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4863379/

Depsy is no longer being updated. See https://twitter.com/depsy_org/status/970376969782149120


Add book

Added the book Head First Javascript

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

Hi @utkarshnag, thank you for the PR! However, we do not accept PRs that only add books or links, especially affiliate ones.
I'm going to close this PR, but feel free to open a new one with more content. Happy coding!


Add an option to download Chandra data exactly as it is on the HEASArc FTP

This would be for people who want the 'standard' data distribution so that they can run chandra_reproc (for instance). I.e. they just want to use DAXA for data acquisition rather than using it to process.

Ryan and Kyndrel have shown that the Chandra downloading with the standard dataset can now successfully be processed by the chandra_repro script, which is what I wanted to achieve!


Using Curl to control the ha-bridge

Must be a brain block I have. What would the syntax for using curl to control the bridge to turn on/off a specific light? Below is what I am trying in all sorts of iterations to no avail.
curl -X PUT -H "Content-Type: application/json" -d '{"lights":"11":"state":"on":"true"}' "http://<IP_ADDRESS>:88/api/test" which results in a 404 error but I can browse to the url and get the device list.
Thank you for a fantastic piece of software.

ON full bright would be:
curl -X PUT -H 'Content-Type: application/json' -d '{"on":"true","bri","255"}' http://<IP_ADDRESS>:88/api/username/lights/{DEVICEID}/state
replace {DEVICEID} for your device ID
OFF would be:
curl -X PUT -H 'Content-Type: application/json' -d '{"on":"false"}' http://<IP_ADDRESS>:88/api/username/lights/{DEVICEID}/state
replace {DEVICEID} for your device ID
DIM would be:
curl -X PUT -H 'Content-Type: application/json' -d '{"on":"true","bri","255"}' http://<IP_ADDRESS>:88/api/username/lights/{DEVICEID}/state
replace {BRIGHTNESS} with your desired brightness 1 to 255, and replace {DEVICEID} for your device ID.

Fixed the "DIM" part...

@101jallen Did this answer your question?

@bwssytems,
I was just testing this out. Perfect! Hooked this in with ifttt.com for some custom strings of events.
Perfect thanks you!
Jerry

Glad it's being useful! Have fun!


[WIP] implement var operator

Description
This is a work-in-progress pull request to implement variance (var) operator. I plan to write JIRA issue once the PR gets ready.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Add std operator
[ ] Write tests to ensure correctness
[ ] Ensure that the "hidden" output of the forward operator gets properly forwarded to the backward operator.

Looks like the result is not normalized? Please add tests in tests/python/unittest/test_operator.py

@piiswrong I've added tests. The var operator works, but the accuracy is not that good.  Let me come up with an alternative implementation that does not involving squaring.

@piiswrong I ended up changing the variance implementation slightly to improve precision. As for testing backward results, I used both numerical and symbolic tests. Numerical gradients have low precision, so I set a high threshold for numerical tests.

Looks like two of the CI tests failed for reasons unrelated to the var/std operators. I'll trigger CI again to make sure tests pass.

Looks like you didn't test for axis?

@piiswrong I added tests for axis.

@piiswrong @anirudh2290 surfacing again for review.

Thanks for your contribution @hcho3
@mxnet-label-bot[pr-awaiting-review]

@hcho3 Can you please address the comments on this PR so that we can move forward with it?


Support for async execs.

This adds a new task type called AsyncExec which has a similar interface
as Exec, but unblocks once the exec has started rather than waiting for
it to complete. A separate type, StopAsyncExec, can be used to stop it
explicitly. If it isn't stopped, then it will be killed once the dagger
client shutsdown.
This is intended for creating ephemeral services used by other tasks in
the DAG, such as a DB against which tests can be run in different tasks.
AsyncExecs cannot output state and any state they create while running
will be thrown away once the DAG finishes executing. The only exception
is if they use a shared cache mount, in which case state will be applied
to the cache mount and accessible by other Execs, async or not.
There is currently an issue with Buildkit where if the dagger client
exits ungracefully without running cleanups, then the container will
leak and keep running in Buildkit. There is also no way for a subsequent
client to query what containers are running and delete any leaked ones,
so the only remedy in this case would be restarting buildkitd. This is
an issue that needs to be fixed Buildkit-side.
Signed-off-by: Erik Sipsma<EMAIL_ADDRESS>

I wanted to open this open quickly (hence the draft) because I want to double check if the way I'm setting up an explicit dependency is actually sound:
dagger.#Plan & {
 	actions: {
 		test: {
 			image: core.#Pull & {
 				source: "alpine:3.15"
 			}

 			asyncExec: core.#AsyncExec & {
 				input: image.output
 				args: [
 					"sleep", "30",
 				]
 			}

 			sleep: core.#Exec & {
 				input: image.output
 				args: [
 					"sh", "-c",
 					#"""
 						echo taking a quick nap
 						sleep 1
 						"""#,
 				]
 				always: true
 			}

 			stop: core.#StopAsyncExec & {
 				exec: asyncExec
 				_dep: sleep
 			}
 		}
 	}
 }

Above you can see the explicit dependency set on the line _dep: sleep. It results in the stop action waiting for the sleep action to finish before running.
The thing is, _dep is not a field I have set in #StopAsyncExec. In fact, this seems to work with any private field, i.e. you could write _foobar: sleep and get the same end effect of creating an explicit cue/flow dependency but without interfering with anything else.
I feel like I'm missing something because it seems too easy, but it does work at leasat in this case AFAICT. I also tested briefly and found it worked for setting up multiple deps like _dep: [sleepA, sleepB]. It's additionally nice in that there's no chance of conflicts because any hidden fields in #StopAsyncExec won't be visible and thus can't conflict with the hidden field in the struct being unified with.
My question is if this can be a solution to the problem of setting up explicit dependencies in general? Or (more likely) am I missing something that prevents us from using this everywhere.

@sipsma This should work! But it does have some caveats. If stop weren't a CUE task, but rather an "action" or similar, this would not work. The big issue with explicit dependencies in general is that they only work CUE task <-> CUE task. And thus, when we have higher level actions such as build: docker.#Build, we can't depend on that field.

Instead of a separate AsyncExec, can we have an async: bool field in the normal Exec?

Instead of a separate AsyncExec, can we have an async: bool field in the normal Exec?

I think this is possible but I went with the separate types because even though there is a lot of overlap between the two, there are fields and requirements that are mutually exclusive to one or the other, e.g.:

normal Exec supports output, but AsyncExec doesn't
AsyncExec can be stopped by StopAsyncExec, but a normal Exec can't.
AsyncExec inherently runs as though always is true (its results can never be cached)
AsyncExec can support spawning exec'ing processes inside the container at arbitrary points after the start (not implemented yet).
AsyncExec can support plugging arbitrary streams into the stdio of the process, even the client's tty (not implemented yet)
AsyncExec doesn't support secret env vars right now (the underlying mechanism just wasn't implemented in Buildkit yet).

If we made async a bool field we could enforce all those requirements in the task implementation, but I guess that would be a runtime assertion whereas defining them as separate cue types is a "compile-time assertion" (in a way). It also might be more confusing to users.
Let me know if you disagree of if there's a way of approaching this with cue that I'm not aware of.

I see. My problem is that we have a lot of definitions on top of core.#Exec (e.g., docker.#Run, bash.#Run, etc....). We want to encourage importing from universe.dagger.io not dagger.io/dagger/core, so just wondering about duplication in the higher lever packages.

I see. My problem is that we have a lot of definitions on top of core.#Exec (e.g., docker.#Run, bash.#Run, etc....). We want to encourage importing from universe.dagger.io not dagger.io/dagger/core, so just wondering about duplication in the higher lever packages.

Ah sure, I can see the concern. The thing is, if we go with the async: bool field here then presumably we will also have similar async: bool fields for all the higher-level packages, so those packages will also have the same differences between sync and async execs as the lower-level tasks in core. But at that point I'm not sure how we could enforce the various requirements (like that bash.#Run can't have an output set if async: true) because it won't be a task implemented in go.
So even though I see the ugliness of having to maintain things like bash.#Run and bash.#AsyncRun, I'm wondering if it's nonetheless cleaner than maintaining the implementation of bash.#Run w/ async: false and the implementation of bash.#Run w/ async: true. Again though, I'm still in the learning phase when it comes to cue, so let me know if there's a clean way of dealing with this type of issue.

@helderco I tried out combining the two types using async: bool and cue if statements. It almost works perfectly but does have some downsides in certain cases. One example is that if you have another cue type that specifically needs an exec with a certain async value (i.e. StopExec requires that it's provided one with async: true), then that can only be checked at runtime unless the user explicitly sets the async value.
In practice, this means that if you accidentally try to stop an Exec where async has defaulted to false, you won't get an error until after the sync exec has finished executing. This is as opposed to maintaining a separate Exec and AsyncExec where that type of user-error is always caught immediately on invoking dagger do.
In terms of higher-level packages, I actually don't think having separate Exec and AsyncExec definitions means we necessarily have to have separate docker.#Run and docker.#AsyncRun types. That would be an option, but we could also choose to instead support an async: bool flag in those packages and use if statements to switch between the two underlying definitions from core. In that sense, I guess keeping the types separate in core gives us the most flexibility for both approaches in higher-level packages.

we could also choose to instead support an async: bool flag in those packages and use if statements to switch between the two underlying definitions from core

Yes, that was my second thought in case doing it in core isn't ideal.

Pinging @helderco / @shykes for CUE API review

Re-pinging. Realize our main focus right now is elsewhere, but this new feature would be quite useful for some other things we are working on, such as being able to test complex workflows involving cache import/export (as described here). If we want to put this on hold I understand too though and can just use it in my fork for now.

(I just realized my point 2. has been addressed in earlier comments)

Also, just wanted to note that I'm excited to have this! It'll unblock the changelog.com config that's been in stasis for while longer than I'd like.

How exactly will we define "async" to developers, and explain when to use one versus the other?

Here's a first shot, can expand in documentation followups to this PR:
AsyncExec should be used for "sidecar" services and fixtures that assist the execution of other tasks in an action. Whereas an Exec is used to run synchronous commands with cache-able outputs, such as building code or executing a test, an AsyncExec has no FS output consumable by other tasks. Additionally, it will be considered "completed" once it has started successfully rather than blocking until it exits. It can be stopped using the StopAsyncExec task if needed; otherwise it will be stopped when the current plan finishes.
Example use cases include:

Running a database that's used by test cases running in other tasks
Running a daemon that synchronizes the state of a shared cache mount with some external backend

Developers will ask: "why can't I kill a synchronous exec?" What will we answer?

The output of a synchronous Exec task can be cached and is thus expected to be a function of its own definition and inputs, which serve as its cache identity. Allowing arbitrary other tasks to terminate an Exec at any time would mean that the output the Exec is strongly determined by something other than its own definition and inputs, thus making it unsafe to cache.
^^ This kind of ignores more subtleties to the issue here. BuildKit/Dagger doesn't actually force an ExecOp/Exec to be 100% hermetic, it tries to strike a balance between hermeticity and usability. This is why you can talk to the internet, tell the time, read from /dev/random, etc. The problem is that allowing async killing of an ExecOp would be such a huge violation of hermeticity that it's not worth enabling. We could document these subtleties too, though it might be too much detail for just the AsyncExec docs.

Any thoughts on how we might integrate this in docker?

I mean on the most basic level we can obviously make a type that accepts a docker.Image as the input rather than just FS. Other than that I don't currently see much else that would make sense to specially integrate, but would have to think about it more.

Thanks for the details @sipsma . I think calling them #Start and #Stop might be more intuitive for developers and aligned with your explanation. wdyt?

I think calling them #Start and #Stop might be more intuitive for developers and aligned with your explanation. wdyt?

Yeah I like that, updated with it. I would actually argue that along these same lines #Run might be a better name than #Exec, but that's probably best left as a different issue (and also not a big deal anyways).

:wave: arriving a bit late to the party here.
I love this feature and it's a great work indeed, congrats @sipsma!.
Looking at the conversation the following comment raised my attention:

it will be considered "completed" once it has started successfully rather than blocking until it exits

I'll bring a past experience that probably @shykes @samalba and @aluzzardi  remember from the docker-compose early days about service dependency healthyness. The situation pretty much summarizes to this:
What happens if my async task starts but it shortly exists due to a transitory error?  Dagger is going to mark the action as completed but then my tests are going to fail (or hang forever) because the async task exited with an error without me knowing about it.
I believe it's worth challenging this UX to see if we can do better than compose this time to avoid going through the same service dependency/healthiness limbo we experienced with compose.
ref: https://docs.docker.com/compose/compose-file/compose-file-v3/#healthcheck

I agree that healthchecks is an important part of the DX for this. We should take responsibility for it, and not consider the feature completed until that dimension is successful. I love this.
In terms of implementation, I want to make sure we keep all our options open. In particular, the more can be done in pure CUE, as opposed to hardcoded in the engine, the better.

and not consider the feature completed until that dimension is successful. I love this.

agree. I'll create an issue to track this. It'd be great to catalog / group it under the async exec epic? cc @mircubed

In terms of implementation, I want to make sure we keep all our options open. In particular, the more can be done in pure CUE, as opposed to hardcoded in the engine, the better.

+1. I haven't fully processed the current implementation yet, I'll take a close look tomorrow :pray:

I think compose was not able to fully solve the problem, precisely because it doesn't have the luxury of a programmable platform: the only way for docker healthchecks to work in every application, is to implement everything in the core. We have the luxury of not doing that.

good point. I'm eager to see how we could compose (cuack) async execs with high level actions that already include their "curated" healthchecks out of the box. That'd be awesome!

By the way, another dimension which I am equally excited about is networking, more specifically client side proxying. In theory you can already hack together a compose equivalent with the current version, but at at a cost which I consider to be too high: losing magical infrastructure independence. There is only one reliable portable way to expose a port from a Dagger container to the outside world, and that is through a client proxy. Implementing that will have major, MAJOR implications for Dagger as a platform.

Yeah I agree healthchecks are an important higher-level construct. Right now you'd implement them as a separate task that has a dependency on the async exec starting successfully. Then, instead of having other tasks put their dependency directly on the core.#Start, you'd have them put their dependency on the separate healthcheck task.
I'd argue that this is the right approach vs. trying to put something specifically inside the core.#Start definition. It gives the most flexibility for higher level packages outside of core. Those higher-level packages can wrap the core.#Start and whatever healthcheck task they want into one single definition that's used together, so the end users aren't exposed to any of the underlying complexity.

By the way, another dimension which I am equally excited about is networking, more specifically client side proxying

Just to double check, do you mean that the dagger client (i.e. whatever is running dagger do) would listen on the port and then forward any incoming traffic to the container listening on the port? Makes sense if so. I have been thinking more about the case of just containers talking to each other so far, hadn't thought about the "outside world" yet...

Yeah I agree healthchecks are an important higher-level construct. Right now you'd implement them as a separate task that has a dependency on the async exec starting successfully. Then, instead of having other tasks put their dependency directly on the core.#Start, you'd have them put their dependency on the separate healthcheck task.
I'd argue that this is the right approach vs. trying to put something specifically inside the core.#Start definition. It gives the most flexibility for higher level packages outside of core. Those higher-level packages can wrap the core.#Start and whatever healthcheck task they want into one single definition that's used together, so the end users aren't exposed to any of the underlying complexity.

I agree :)

By the way, another dimension which I am equally excited about is networking, more specifically client side proxying

Just to double check, do you mean that the dagger client (i.e. whatever is running dagger do) would listen on the port and then forward any incoming traffic to the container listening on the port? Makes sense if so.

Yes 👍


Update tools-ui-components.md

Added a new react component from Zhihu.
https://github.com/zhihu/griffith

We've removed this page.


Error connecting to ClojureScript REPL: (void-function :number)

What did you expect to happen?
I hit SPC m C and selected my host/port and shadow as the REPL type and then get connected to the REPL
What actually happened?
When I tried connecting to my REPL like usual, I get this error
Debugger entered--Lisp error: (void-function :number)
  :number(0)
  parseclj-lex--leaf-token-value(((:token-type . :keyword) (:form . ":deps") (:pos . 31)))
  parseedn-reduce-leaf((((:token-type . :lbrace) (:form . "{") (:pos . 30))) ((:token-type . :keyword) (:form . ":deps") (:pos . 31)) ((:tag-readers (shadow/env . identity))))
  parseclj-parser(parseedn-reduce-leaf parseedn-reduce-branch ((:tag-readers (shadow/env . identity))))
  parseedn-read(((shadow/env . identity)))
  cider--shadow-get-builds()
  cider-shadow-cljs-init-form()
  cider-cljs-repl-form(shadow)
  cider--update-cljs-init-function((:project-dir "~/Projects/mojo_tools/frontend/" :host "localhost" :port 9000 :cljs-repl-type shadow))
  cider-connect-cljs(nil)
  funcall-interactively(cider-connect-cljs nil)
  call-interactively(cider-connect-cljs nil nil)
  command-execute(cider-connect-cljs)

This is like the previous issue #4539
Describe your attempts to resolve the issue
I removed my ~/.emacs.d directory and reinstalled doom but the issue still happens.
I am on the latest commit of doom
Steps to reproduce

Open a ClojureScript project in Emacs
Hit SPC m C
Select localhost:9000 or your shadow script host
Select shadow

System Information
https://pastebin.com/6UYx8gpG

Duplicate of #5561


[AWS SNS/SQS] Add note re component behavior

Signed-off-by: Hannah Hunter<EMAIL_ADDRESS>Description

Quick grammar/readability pass on doc
Add note on SNS/SQS component behavior

Issue reference
PR will close: #2456

@amimimor could you review my attempt?

LGTM


searchLength=7 aliases searchLength=4

searchLength=7 in ZSTD_parameters is permitted, but it seems to give exactly the same compression and speed results as searchLength=4. Possibly this is because of the switches on matchLengthSearch in the code that have cases for 4-6 but not 7.

Correct.
I omitted this combination in the source code, in order to reduce binary size, since this combination never happens, except for fast strategy.

I think that was true in 0.4.4, but 0.4.5 has searchLength=7 in combination with ZSTD_greedy and ZSTD_lazy in the <= 256 KB table.

You are totally right.
This is mistake, and should be 4.
It went undetected as 7 is automatically translated into 4 ...

zstd_static.h has been fixed


BUG - Sev-3 - Storybook - Fix Code Snippets

What happened?

Specs:

Device:
OS:
User Account:
Accessibility State:

Steps to Reproduce

Desired behavior

Acceptance Criteria

Bug Severity - BE SURE TO ADD THE SEVERITY LABEL

See Bug Tracking for details on severity levels

Impact: High Low
Frequency: High Low

3 - Low
2 - High
1 - Critical

Linked to Story

Screen shot(s) and additional information

Full JSON response for services related to issue (expand/collapse)

Ticket Checklist

[ ] Steps to reproduce are defined
[ ] Desired behavior is added
[ ] Labels added (front-end, back-end, relevant feature, accessibility, etc)
[ ] Estimate of 1 added (for front-end tickets)

Unable to add severity label to this ticket. @narin can you please add it


ability to work with simple_form

I'd love to use this along with simple_form f.input. I don't think it's possible at the moment? Is it?

Can you provide an example?

Simpleform example:
<%= simple_form_for @user do |f| %>
  <%= f.input :username, :label => 'Your username please' %>

It would be nice to be able to do:
<%= twitter_bootstrap_form_for @user do |f| %>
  <%= f.input :username, :label => 'Your username please' %>

Is it really that much effort to specify what kind of field you want? The syntax I provide even ends up being shorter in most cases, I think you'll find.
<%= f.email_field :email, 'Your email address', :placeholder =><EMAIL_ADDRESS>%>
<%= f.input :email, :label => 'Your email address', :input_html => { :placeholder =><EMAIL_ADDRESS>} %>

I don't really see the benefit.

Well - that's what simple_form is providing - just a convention :)
https://github.com/plataformatec/simple_form
and the syntax is consistent with formtastic. I know a lot of people are familiar with that. Also there are projects that can be very easily migrated if the syntax was the same.

I appreciate that, but I think more people likely use the existing Rails helpers. That, and this project is a simple wrapper on top of those helpers. Maintaining a completely parallel FormBuilder with its own syntax (which I personally find to be less flexible, useful, and readable than the current out-of-box experience) adds another level of complexity I'm just not eager to write and maintain.
This project is actually a spin-off of another project I started, semantic_form_for, which was a direct result of aggravation at the inflexibility and verbosity of Formtastic and SimpleForm. They're way more complicated than they need to be, as I think the syntax I provide here demonstrates.
With apologies, I just don't think I can justify the level of effort and complexity in writing and maintaining a second FormBuilder. Doubly so for one that I think has few benefits to offer. I'd be glad to add the :label_html and :wrapper_html options if you need them, however.


Add AvgPool3D layer

Resolves #81. This PR adds support for AvgPool3D layer.

[x] Implement layer class
[x] Add unit tests for layer implementation
[x] Add support for importing models containing this layer from JSON config files
[x] Add support for exporting models containing this layer to JSON config files

NOTE: as commented in the unit tests, currently it gives an error when dataFormat = CHANNELS_FIRST.

@zaleslaw I just merged it with master branch and updated it with recent/requested changes.

@zaleslaw I changed the strides type and default value per your request.


Delete manifest doesn't use schema V2 either

I test the manifest digest and delete, not delete successful in schema V2 registry.
Please take a review one PR of mine, I can fix it later

Fix in new pull request22(https://github.com/heroku/docker-registry-client/pull/26)


Error: getReferences; getDocumentHighLight timeout; getDefinition timeout; getHover - Coc.nvim PARTIALLY stops working

Reporting Subject Errors While Following TSServer Troubleshooting Instructions and Neoclide Gitter Forum Recommendations March 5, 2020 3:16 AM
I). Specs (with newest and stable  nodejs)
vim version: NVIM v0.5.0-139-g610755ff6
node version: v13.9.0
coc.nvim version: 0.0.75-027b7a76e9
term: screen-256color
platform: linux
A) Problem Detail Description:
Coc.nvim abruptly and partially breaks-down with errors: ERROR getDocumentHighLight timeout, ERROR [languages] - getDefinition timeout, and ERROR [plugin] - Error: getDefinition. CocOpenLog reports that all Coc.nvim functionalities such as getDefinition, getDocumentHighlight, getReferences , getHover crash at one and the same line code 49805 in the coc.nvim plugin
B) Steps Taken To Remedy Problem:
a) Apps are up-to-date: and in particular, NVIM v0.5.0-139-g610755ff6 latest version. Nodejs used stable current version 13.9.0 (see point I above) and subsequently, LTS versions 12.6.1 (see point II below). Each time in init.vim applied the line of code let g:coc_node_path = '/path/to/node'
b) Neovim checkhealth - all "OK"
c) In Neovim i execute to reinstall and rebuild language servers: a) PlugInstall, b) PlugUpdate, c) UpdateRemotePlugins, d) CocRebuild, e) CocRestart, f) CocUpdate.
Also, prior to using Coc executed command :CocRebuild to rebuild coc extensions.
d) reinstalled Coc.nvim plugging several times appling in init.vim:
Plug 'neoclide/coc.nvim', {'branch': 'release'}
C) Observation of Problem Occurrences:
a) Coc.nvim is partially working - Coc.nvim works only in newly created files and directories. Coc.nvim stops working on files/directories (collection of my earlier files/directories) prior to Coc.nvim update.
b) CocOpenLog reports that all Coc.nvim functionalities such as getDefinition, getDocumentHighlight, getReferences , getHover crash/timeout at one and the same line code 49805 in the coc.nvim plugin:
at Timeout._onTimeout (/home/sky/.config/nvim/plugged/coc.nvim/build/index.js:49805:28)

c) Changing Nodejs version from current stable 13.9.0 to LTS 12.6.1 did NOT make any tangible improvement. The problem continues to persist.
D) Log Reports:
1. CocCommand tsserver.openTsServerLog Report:

[A] coc-nvim-tsc.log
[B] coc-nvim-tsc.log

2. CocCommand workspace.showOutput tsserver:

[A] tsserver.log
[B] tsserver.log

3. CocOpenLog:

[A] CocOpenLog.log
[B] coc-nvim-27690.log

4. CocInfo:

[B] info.log

II). Specs (with LTS stable nodejs version 12.6.1)
vim version: NVIM v0.5.0-139-g610755ff6
node version: v12.6.1
coc.nvim version: 0.0.75-027b7a76e9
term: screen-256color
platform: linux
1. CocCommand tsserver.openTsServerLog Report:

[C] coc-nvim-tsc.log

2. CocCommand workspace.showOutput tsserver:

[C] tsserver.log

3. CocOpenLog:

[C] coc-nvim-7291.log

4. CocInfo:

[C] info.log

Please, assist with resolving this problem. Hints, suggestions, solutions or any observations will be greatly appreciated.

It looks like you have some links on your disk and tsserver looks at files in /home/sky/.cache which is too big and blocked tsserver.
Info 61   [4:58:51.890] sysLog:: /home/sky/.cache/doc:: Changing to fsWatchFile
Info 62   [4:58:57.362] sysLog:: /home/sky/.cache/restic/0043ae64d9942eea7ad09d2f46dbeeaba82e003647791f3f0187c23cacd6b69c/data/62:: Changing to fsWatchFile
Info 63   [4:58:57.363] sysLog:: /home/sky/.cache/restic/0043ae64d9942eea7ad09d2f46dbeeaba82e003647791f3f0187c23cacd6b69c/data/68:: Changing to fsWatchFile
Info 64   [4:58:57.364] sysLog:: /home/sky/.cache/restic/0043ae64d9942eea7ad09d2f46dbeeaba82e003647791f3f0187c23cacd6b69c/data/9b:: Changing to fsWatchFile
Info 65   [4:58:57.364] sysLog:: /home/sky/.cache/restic/0043ae64d9942eea7ad09d2f46dbeeaba82e003647791f3f0187c23cacd6b69c/data/a4:: Changing to fsWatchFile
Info 66   [4:58:57.364] sysLog:: /home/sky/.cache/restic/0043ae64d9942eea7ad09d2f46dbeeaba82e003647791f3f0187c23cacd6b69c/data/e3:: Changing to fsWatchFile
Info 67   [4:58:57.364] sysLog:: /home/sky/.cache/restic/0043ae64d9942eea7ad09d2f46dbeeaba82e003647791f3f0187c23cacd6b69c/data/ec:: Changing to fsWatchFile

@chemzqm : also noticed this restic thing in the report, but cannot make any sense out of it. I am not using anything of that sorts, and thing is not on my $PATH. What would be the best thing to do in such case ?

Try other vim plugin or VSCode

I asked you how can i fix the problem above ?

No idea，your tsserver get blocked.

Fixed !

I'm running into this as well. @Annis-Monadjem can you share how you fixed this?

@sergeichestakov: i deleted /home/sky/.cache/restic/ and the problem went away for good.


Experiment 1 Implementation

Experiment 1 Implementation
The following PR implements experiment 1 in two variations : one with walls and the other one with putative_cooperation component ( invisible to human view, but tangible in ASCII map)

commons_harvest__private_property.py: variation from commons__harvest_open
commons_harvest__private_property_pc.py: variation from common_harvest_partnership

Scripts modified
__init__.py in meltingpot>substrates : this basically registers a new substrate
configs.py : add substrates
run_ray_train.py : flags and substrates
Test.
It has been evaluated in evaluate.py and made some videos shared in slack, but to be sure it would be nice if you could double check this in python via python run_ray_train.py --exp commons_harvest__private_property  python run_ray_train.py --exp commons_harvest__private_property_pc

Thanks ! Im now preparing the other PR , and will add both README.md for that and this one!


Updated on ES and Kafka

I looked into the kafka-python documentation and I think the reason kafka fails on sending the first message is that SimpleProducer sends message in synchronous mode. Since topic creation takes time, it fails on sending the first message. I also found that SimpleProducer is deprecated in the most recent version of Kafka (1.0.2) (http://kafka-python.readthedocs.org/en/master/simple.html#simpleproducer-deprecated). I try upgraded kafka-python in container and everything works out fine. I will submit a pull request for this.

I merged in David's Docker 1.9 PR. Can you re do your PR against that?
Also it looks like this requires a new Dockerfile for the tp33/Django container. Do you have a PR for that?


fix: select: adds optional chaining to avoid null reference errors at runtime

SUMMARY:

Adds optional chaining
Updates placeholder to show when options are null in multiple mode
Adds unit tests covering null or empty array scenarios
Updates options to ensure id alignment.

https://github.com/EightfoldAI/octuple/assets/99700808/4e1e18c7-81da-4707-be4e-10a158edfa2c
GITHUB ISSUE (Open Source Contributors)
https://github.com/EightfoldAI/octuple/issues/666
JIRA TASK (Eightfold Employees Only):
ENG-58585
CHANGE TYPE:

[x] Bugfix Pull Request
[ ] Feature Pull Request

TEST COVERAGE:

[ ] Tests for this change already exist
[x] I have added unittests for this change

TEST PLAN:
Pull the PR branch and run yarn and yarn storybook. Verify the Select stories behave as expected when its options are null or [].

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@447d2a1). Click here to learn what that means.
Patch has no changes to coverable lines.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #669   +/-   ##
=======================================
  Coverage        ?   84.82%
=======================================
  Files           ?      880
  Lines           ?    17876
  Branches        ?     6373
=======================================
  Hits            ?    15164
  Misses          ?     2641
  Partials        ?       71

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


PostgreSQL

Hi @andrey-helldar
it doesn’t work with postgresql 10? Correct? 13 and up only?
...
Steps To Reproduce:
...

The package works with the standard Laravel database drivers.
According to the documentation, Laravel 8 supports the PostgreSQL 9.5+ database.

What error are you getting?

I added tests for PgSQL 9, 10, 11, 12 and 13 versions to GitHub Actions and they succeed:
https://github.com/andrey-helldar/migrate-db/actions/runs/1005954605

What versions are you using?
Migrate DB Version:
Laravel Version:
Database Name & Version:
PHP Version:


Add link to sign up form

Purpose of this pull request
This pull request (PR) adds a link to the beta signup form.
Affected pages

...

Links to Magento Open Source code

...

Fixed in #190


Fix various items in inventory

There are several bugs related to the inventory screen:

The tablets appear in the order emerald -> ruby -> amber even if you get them in another order. Meaning if you have 1 tablet it will always show emerald; 2 tablets, emerald and ruby; 3 tablets, emerald, ruby and amber.

The thunder dragon's song text is broken (shows "==== ===="). This is due to not having the bit making the life tree seedling visible + a bit related to the life tree fruit. Also they all use the same slot in the inventory (same with triforce and tablets actually)

It would also be nice to have a slot for sea chart, small keys and boss keys (for keysanity), but that is more of a feature.

I haven't looked into any of the inventory code, so I don't actually know how all of this works, but how would be the best way of dealing with things that occupy the same slot? Just draw all of them over each other? Cause I kinda doubt that will work, so we probably have to rearrange the item menu so everything we need can be displayed. Having all of the keys displayed would definetly be neat, but that definetly needs a bit of custom code, which the current patches aren't designed for. I really want to transform them into proper asm patches anyways, but haven't gotten around to that


Update websocket-extensions gem

Responds to security alert
https://github.com/MushroomObserver/mushroom-observer/network/alert/Gemfile.lock/websocket-extensions/open

Coverage remained the same at 91.988% when pulling 26607e0723142a06ee58b60e857577bd040a7a96 on JoeCohen:CVE-2020-7662 into 4e11859bb24393b1aad16ce3bdba18fbd5eb59db on MushroomObserver:master.


Typo in paragraph 2 - In the Microsoft.Compute/virtualMachineScaleSets

The line for commonNames has one [ too many.
add "commonNames": ["[parameters('certificateCommonName')]"]
should be
add "commonNames": "[parameters('certificateCommonName')]"]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d34f6d36-58e7-ab10-e659-bdd10a64deca
Version Independent ID: 25d94e4b-8c95-7423-2665-7c09d438a16b
Content: Update an Azure Service Fabric cluster to use certificate common name
Content Source: articles/service-fabric/service-fabric-cluster-change-cert-thumbprint-to-cn.md
Service: service-fabric
GitHub Login: @rwike77
Microsoft Alias: ryanwi

and also a ] too much in the end


size_array operator returns wrong results on MacOS

Description
size_array operator returns incorrect results on MacOS but works correctly on Linux systems
Package used (Python/R/Scala/Julia):
I'm using Python
Compiler (gcc/clang/mingw/visual studio):
clang
MXNet commit hash:
50f43f05ab61fe9e19698bb18dc34858a240b263
Build config:
make -j $(nproc) USE_OPENCV=1 USE_BLAS=openblas
Minimum reproducible example
import mxnet as mx
a = mx.nd.array([1,2,3,4,5])
print(mx.nd.size_array(a))

Steps to reproduce

Run the above script in MacOS, the function will return a junk memory location.
Run it on Linux and it will work fine.

What have you tried to solve it?

Use the operator on a linux system.

In src/operator/tensor/elemwise_unary_op_basic.cc#L546,
  const index_t size_var = in_data.Size();
  memcpy(out_data.dptr_, &size_var, 1U * sizeof(int64_t));

In 3rdparty/dmlc-core/include/dmlc/data.h,
typedef unsigned index_t;

It's confusing that index_t may not the same as int64_t

@mxnet-label-bot [Call for Contribution, Good First Issue]

Issue has been fixed:
>>> import mxnet as mx
a = mx.nd.array([1,2,3,4,5])
>>> a = mx.nd.array([1,2,3,4,5])
>>> print(mx.nd.size_array(a))

[5]
<NDArray 1 @cpu(0)>
>>>


When trying to generate qr-code locally

When trying to generate qr-code locally after taking the pull from the latest commit
Parse error: syntax error, unexpected '?', expecting function (T_FUNCTION) or const (T_CONST) in /opt/lampp/htdocs/smiley-qr/vendor/chillerlan/php-qrcode/src/Data/QRMatrix.php on line 58

This means that you're running a PHP version lower than 7.4 - the error is caused by a typed property.

No, Actually I m using PHP 7.4.3.

The line that produces the error is this one: https://github.com/chillerlan/php-qrcode/blob/b6777fd58b2275ff108c75abc9fa9767b180a16b/src/Data/QRMatrix.php#L58 - it should run without issues on PHP 7.4 as it does on CI.

We've been there before:

https://github.com/chillerlan/php-qrcode/issues/43
https://github.com/chillerlan/php-qrcode/discussions/119

btw. this is a private repo for the qrcode demo i'm running on my website. I'm going to move this issue to the qrcode  repo.


TypeError: _flash_attn_varlen_forward() missing 1 required positional argument: 'window_size'

From the call to _flash_attn_varlen_forward() on line 179 in llama_flash_attn_ckpt_monkey_patch.py, it looks like window_size is not specified. From the documentation, would the default value of window_size=(-1,-1) be appropriate here?

Hi! window_size is only useful when you want to do sparse version of FlashAttention. By default, window_size=(-1,-1) means it will compute full attention. You're not supposed to see this error as it should just use the default setting. Please let me know if manually passing window_size=(-1,-1) can help. Thanks!

Yes, window_size=(-1,-1) resolved this as expected. Thanks for the clarification.


feat: upgrade to Angular 6rc/rxjx 6/webpack 4

** PR Checklist
Please check if your PR fulfills the following requirements:

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

** PR Type
What kind of change does this PR introduce?

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

** What is the current behavior?

Issue Number: #57, #284, #344, #369
** What is the new behavior?
** Does this PR introduce a breaking change?
[x] Yes
[ ] No

** Other information

@fulls1z3 Are this warnings a problem?
(node:34756) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead

Warning<EMAIL_ADDRESS>System.import() is deprecated and will be removed soon. Use import() instead.
For more info visit https://webpack.js.org/guides/code-splitting/
 @ ./src/client/main-spa-aot.ts 5573:15-36 2:0-47 12:0-14

Warning<EMAIL_ADDRESS>System.import() is deprecated and will be removed soon. Use import() instead.
For more info visit https://webpack.js.org/guides/code-splitting/
 @ ./src/client/main-spa-aot.ts 5585:15-102 2:0-47 12:0-14

Warning: asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
  app.7d1883b7ba0ce8ac1edf.bundle.js (1.65 MiB)

Warning: entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
  app (1.71 MiB)
      app.7d1883b7ba0ce8ac1edf.bundle.js
      app.7d1883b7ba0ce8ac1edf.style.css

    (4) warning(s) total.

@vlados for the first two, the Angular team has an ongoing PR (can’t remember the link now, came to a beerhouse lol).
The last two are performance warnings due to bundle size.
As a rule of thumb, i don’t suppress warnings. But anyway it’s safe to go, I use the same setup on my commercial projects already.

Super! Great work man!


Koa update problem

When I compared KOA with Express, I found that koA and its peripheral plug-ins were too slow to update and maintain. Could you tell me why

What package are you referring to?

Actually, I'll answer by rephrasing.
Koa core is generally a stable library with little requirement for updates.
As far as packages, you'll have to ask the maintainers of those packages.
I'm going to close this issue but if you feel my answer is inadequate, don't hesitate to reopen this ticket.


Setup spot area not working as expected

Hi,
I am currently trying to setup my new Deebot Ozmo 950. The map setup is finished and the renaming of the areas is completed. Installation is as follows:
Homebridge Deebot 6.1.1
Homebridge 3.0.17
Synology DSM 7.2-64570 Update 3
Node.js 18.15.0-1008
I am trying to find the spot areas in Homebridge log as described, but cannot find them. The log is attached. I have tryed to but the pugin to debug mode with configuration entry "debug": "true" but no success.
Could you help me out? Many thanks in advance.
Mathias

hblog.txt

I got exactly the same problem

@datarepos76 Hi mate, I installed beta version and it did show all the map area info


No actucal effects

pretty much the same as https://github.com/Cologler/logseq-remove-empty-blocks-typescript/issues/1

The new version is released.

Can confirm it works now.


Allow multi_process_shared objects to be called

This will allow things like models that are invoked via model(args*) to work.
Fixes #26169

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

flakes are due to jenkins issues

retest this please

retest this please

Run Python PreCommit

Run PythonDocker PreCommit

Run Python_Integration PreCommit

Run Python_Runners PreCommit

retest this please


Tag-Along not working

The Unity build and Visual Studio deployment to my HoloLens were successful but the Tag-Along functionality was not working.  When I played the game scene in Unity, I got:
MissingComponentException: There is no 'Renderer' attached to the "AstroMan" game object, but a script is trying to access it.
You probably need to add a Renderer to the game object "AstroMan". Or your script needs to check if the component is attached before using it.
UnityEngine.Renderer.get_materials () (at C:/buildslave/unity/build/Runtime/Export/GraphicsRenderers.bindings.cs:80)
Interactible.Start () (at Assets/Scripts/Interactible.cs:17)
Any suggestion would be much appreciated.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4c49bf7f-19f2-3dae-0a5c-562ef686e4ea
Version Independent ID: 6bf4877d-e20b-e055-1ee4-ab6d5d6c7976
Content: Holograms 210 - Mixed Reality
Content Source: mixed-reality-docs/holograms-210.md
Service: unspecified
GitHub Login: @keveleigh
Microsoft Alias: kurtie

@keveleigh @davidkline-mis Can you guys take a look at this and see if some detail is missing from the Holograms 210 steps for implementing tag-along that might be affecting @debyeleong?
Thanks,
Matt

Thanks for catching this! Turns out it was caused by an errant step that isn't necessary to complete the course. I've addressed this in #335.

Still having some trouble with the Tag-Along portion of the tutorial. Not getting any errors but astronaut doesn't tag-along or billboard after chapter 6. The billboarding portion worked fine in the previous chapter and I'm following the instructions and downloaded files from #335.
Any idea what's going on/any more details I can provide to help find a solution?

@ThreeTreeTrolls
#335 refers to some archived pages that no longer exist. Are you following the updated tutorial here: https://docs.microsoft.com/en-us/windows/mixed-reality/holograms-210?
I believe the steps to tagalong the astronaut have been removed, and the steps for billboarding the astronaut are undone at the end of chapter 5.

@keveleigh
I had originally followed the updated tutorial and ran into issues with Billboarding (the astronaut was facing the wrong direction - the fix was in the other closed discussion.) and Tag along. Since the fix worked I tried to follow #335 but tag along didn't seem to be working from there either.
I've given the updated tutorial from your link another try, but tag along and billboarding does not seem to be working after building Chapter 6. (I have remembered to delete the script from AstroMan before moving on to the next step).
Any idea what might be going wrong?

@ThreeTreeTrolls
On the billboard.cs script I changed the direction to the following so that the astronaut will face the user:
Vector3 directionToTarget = transform.position - TargetTransform.position;
(basically transform.position was swapped with TargetTransform.position)
&& that will cause the Tagalong to face the opposite direction.
and this causes the UI billboard tagalong to face away making it not visible. So, continue in the project window inside the holograms folder into the Tagalong prefab, clicking the little arrow will open up the children of that gameObject. Then, still in the Project window select the child of Tagalong, ui_transform and change the Y value of the rotation of the transform in the inspector to 180.
I believe the UI's and gameObject's normal direction is somehow different, so when the astronaut faces the user we cannot see the ui and when the astronaut faces away the UI is visible. (they both have a billboard component attached)


Best practicse wanted

I think ponzu is fantastic.
after dig into the docs, I still have some thing to ask.
1 Is ponzu is designed as a datastore of contents and  can generate apis to access contents? so, in theory, the front end (end user front  such as web pages)  whould have to be implimented seperatedly? and if things like this, what is the best practise to develop the front end(web pages)?
2 as ponzu contents could be added by admin user, but in working enviourment, admin would not be given to end user. so what is the best practise to setup users with roles? such as some roles can edit users content, while other roles can only edit product contents ,things like that.
3 any crud apis posting contents that provided by ponzu could be pended and have to be approved by admin, or auto approved by ponzu. while in the later situation, what is the best practise to apply role based control of content crud?
even through the admin can crud contents, but as doc shows that this is for developing, so the upper 3 question is vital for developing.
thanks for your attention.

To prevent input of This issue hasn't had an answer, and is now quite old. I am going to add an answer for completeness and close it.

Yes. The front end could either be a clientside application using JavaScript to make requests to Ponzu, or a serverside application, running on the same server as Ponzu, or a different one. Which is chosen will depend on which technologies are most familiar.

2 & 3. Beyond admin, there is no notion of roles in Ponzu. By default it is not possible to add items over the API. To open this up, the creatable and maybe mergeable interfaces should be looked at. The former allows item creation over API, while mergeable will remove the need for admin review and make it public for GET requests over the API.


⚠ 366.ru has degraded performance

In e8e4de6, 366.ru (https://366.ru) experienced degraded performance:

HTTP code: 200
Response time: 5726 ms

Resolved: 366.ru performance has improved in 02c02d7.


[d3d10] Stalker CP crashes

Software information
S.T.A.L.K.E.R. Call of Pripyat with d3d10 renderer (a.k.a renderer_r3) enabled
System information

GPU: Nvidia GTX 1050
Driver: 396.51
Wine version: 3.13
DXVK version: git, commit 4867c8b6e55c699af0934401681a8b726c50be3b
Set up using setup_dxvk32 because prefix is 32-bit and the game is 32-bit too.
Arch Linux 64-bit

Apitrace file(s)
Game crashes when apitracing it.
Log files
game's own log
xrEngine_d3d11.log
xrEngine_dxgi.log
and xrEngine_d3d10.log is empty.
The same bug when using DXUP.
The game works well with d3d11 renderer a.k.a renderer_r4.

Excuse me, apitrace crashed before, not game.
But finally i apitraced it:
xrEngine.trace.zip

Replaying the (very small) trace doesn't crash on my end. Was the trace recorded with DXVK? If so, it needs to be done on a platform where it works, i.e. wined3d if it works, or Windows.

No, i recorded it with wined3d. Sadly i have no Windows.

Please let me know if dad015bd6782d9f332137349235f0873e57aa462 fixes the issue.

I can confirm dx10 mode fixed with latest master.

@axredneck
Here is full overrides list for both 10/11 renderer options:
stalker-cop-dll.reg
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Wine\AppDefaults\xrEngine.exe\DllOverrides]
"d3d10"="native"
"d3d10_1"="native"
"d3d10core"="native"
"d3d11"="native"
"d3dcompiler_42"="native"
"d3dcompiler_43"="native"
"d3dcompiler_47"="native"
"d3dx10_42"="native"
"d3dx10_43"="native"
"d3dx11_42"="native"
"d3dx11_43"="native"
"dxgi"="native"

Maybe not all of them are really needed.

@pchome I installed all of them with winetricks (except compilers 42 and 47, i added them manually and copied them to Stalkers "bin" directory), but the same issue.

@axredneck I have tested the game in a 64 bit prefix and it works for me (both dx10 and dx11). Maybe you should try it in a 64 bit prefix. Install both 32 bit and 64 bit DXVK binaries.

@axredneck

64 bit prefix (default)
winxp version set for xrEngine.exe (to be sure)
dxvk.conf with dxgi.fakeDx10Support = True in game's root directory (where DXVK log files created)
missing 32 bit DLLs in game's bin/ directory
r3_use_dx10_1 on and renderer renderer_r3 manually set in user.ltx config file
winelib build

Don't know if there is other differences can be. Check log files produced by game/WINE .

p.s.
Stalker CP GOG version without mods with dxvk-git form AUR works for me in D3D11 mode but crashes in D3D10 one. xrEngine_d3d10.log file is empty.
I try D3D10 because one of mods i want to play (Klondyke 2.0) doesn't support D3D11. Also i want to play Stalker CS with some mods later and it doesn't have D3D11 at all.

Oh, i just rebuilt dxvk-git and now it works!


Repository checker [#374]

We have to raise the adapter version to release it with these changes. These changes are no patches or bug fixes so the minimum is a minor change. So the next version should be 1.5.0.


darkworld bug (nvidium + embedium) and crash on resource pack reload :|

crash-2024-07-14_15.40.47-client.txt

after a while of looking i found the whats causing the issue it is a odd interaction with nvidium, jsg and embedium (i am loading nvidium in forge using the connector mod)

Fixed in dev