Fix External should also be ProviderID

External should also be ProviderID type

@kebe7jun: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test analyze-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kebe7jun: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test analyze-tests_istio

unit-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kebe7jun: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test analyze-tests_istio

unit-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test unit-tests_istio

release-test_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test release-test_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kebe7jun: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test analyze-tests_istio

unit-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test unit-tests_istio

release-test_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test release-test_istio

lint_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kebe7jun: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test analyze-tests_istio

unit-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test unit-tests_istio

release-test_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test release-test_istio

lint_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test lint_istio

integ-ipv6-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-ipv6-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kebe7jun: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test analyze-tests_istio

unit-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test unit-tests_istio

release-test_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test release-test_istio

lint_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test lint_istio

integ-ipv6-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-helm-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kebe7jun: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test analyze-tests_istio

unit-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test unit-tests_istio

release-test_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test release-test_istio

lint_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test lint_istio

integ-ipv6-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-helm-tests_istio

integ-telemetry-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kebe7jun: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test analyze-tests_istio

unit-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test unit-tests_istio

release-test_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test release-test_istio

lint_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test lint_istio

integ-ipv6-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-helm-tests_istio

integ-telemetry-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-operator-controller-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kebe7jun: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test analyze-tests_istio

unit-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test unit-tests_istio

release-test_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test release-test_istio

lint_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test lint_istio

integ-ipv6-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-helm-tests_istio

integ-telemetry-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kebe7jun: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test analyze-tests_istio

unit-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test unit-tests_istio

release-test_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test release-test_istio

lint_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test lint_istio

integ-ipv6-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-helm-tests_istio

integ-telemetry-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-pilot-k8s-tests_istio

integ-distroless-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kebe7jun: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test analyze-tests_istio

unit-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test unit-tests_istio

release-test_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test release-test_istio

lint_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test lint_istio

integ-ipv6-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-helm-tests_istio

integ-telemetry-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-pilot-k8s-tests_istio

integ-distroless-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-distroless-k8s-tests_istio

integ-cni-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-cni-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kebe7jun: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test unit-tests_istio

release-test_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test release-test_istio

integ-pilot-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
751390596efc42d2dc76594dad23f6c492a90c92
link
/test integ-cni-k8s-tests_istio

lint_istio
7e30f554ce0a204905897fec8f1cd60cb987b7a5
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/LGTM

@shamsher31 can you please take a look here?


Forget pending tx endpoint spec update

Issue Number
#836
Overview
swagger.yaml update:

deleteTransaction summary:  Delete -> Forget
update response codes for Tx forget endpoint
update status for Byron management nodes

Comments

bors r+

bors r+


Refactor admin user filter query parameters

Follows

https://github.com/go-gitea/gitea/pull/18957

Changes:

Only pass status_filter on admin page
Use a more general method to pass query parameters, remove hard-coded keys

Fix the strange URL:
https://try.gitea.io/explore/users?page=3&sort=alphabetically&q=&status_filter[is_active]=&status_filter[is_admin]=&status_filter[is_restricted]=&status_filter[is_2fa_enabled]=&status_filter[is_prohibit_login]=

I think this should also be backported, since the PR this improves upon is also backported. In fact, I'd rather consider this to be part of the backported error fix, as releasing the current state would indeed lead into quite confusing URLs.

@fnetX just send a backport ...


App no longer goes straight to Inbox from phone notification

Expected behavior
After receiving a notification from your phone that you have new mail you tap the notification and the app goes to the Inbox so you can read your new message(s).
Actual behavior
After receiving a notification from your phone that you have new mail you tap the notification and the app goes to the folder list for your email account.  You then have to tap the Inbox to read the new messages.
Steps to reproduce

Wait for a new mail notification from your phone.
Tap on the notification.
Observe that the application does not go to the Inbox.

Environment
K-9 Mail version:
5.201
Android version:
6.0
Account type (IMAP, POP3, WebDAV/Exchange):
POP3 and IMAP

See #1885


MSFT_SqlSetup: AddNode is not working (missing 4 parameters in commandline)

Details of the scenario you tried and the problem that is occurring
As discribed in the SqlSetup documentation, the AddNode is not currently working.
I found that they are 4 parameters missing from the command line that launch the setup.exe from SQL.
So I used the resource as discribed in the documentation, had SQL cluster first node installed with no problem, and, as said, the AddNode feature for the second node is not working.
The DSC configuration that is using the resource (as detailed as possible)
Here is some part of the configuration that I used for that :
            SQLSetup 'InstallSQLClusterFirstNode'
                {
                    Action                = "InstallFailoverCluster"
                    InstanceName          = $Node.InstanceName
                    Features              = $Node.Features
                    SQLCollation          = $Node.SQLCollation
                    SQLSvcAccount         = $Node.SqlServiceCredential
                    AgtSvcAccount         = $Node.SqlAgentServiceCredential
                    FTSvcAccount          = $Node.SqlFullTextCredential
                   # RSSvcAccount          = $Node.SqlReplicationCredential
                   # ISSvcAccount          = $Node.SqlIntegrationCredential
                    SQLSysAdminAccounts   = $Node.SQLSysAdminAccounts

                    InstallSharedDir      = $Node.InstallSharedDir
                    InstallSharedWOWDir   = $Node.InstallSharedWOWDir
                    InstanceDir           = $Node.InstanceDir
                    InstallSQLDataDir     = $Node.InstallSQLDataDir
                    SQLUserDBDir          = $Node.SQLUserDBDir
                    SQLUserDBLogDir       = $Node.SQLUserDBLogDir
                    SQLTempDBDir          = $Node.SQLTempDBDir
                    SQLTempDBLogDir       = $Node.SQLTempDBLogDir
                    SQLBackupDir          = $Node.SQLBackupDir
                    SourcePath            = $ConfigurationData.NonNodeData.SQLsources.SourcePath
                    UpdateEnabled         = $Node.UpdateEnabled
                    ForceReboot           = $Node.ForceReboot
                    SuppressReboot        = $Node.SuppressReboot
                    SecurityMode          = $Node.SecurityMode
                    SAPwd                 = $Node.SAPWD
                    SQMReporting          = $Node.SQMReporting
                    ErrorReporting        = $Node.ErrorReporting

                    FailoverClusterGroupName = $Node.FailoverClusterGroupName
                    FailoverClusterNetworkName = $Node.FailoverClusterNetworkName
                    FailoverClusterIPAddress = $Node.FailoverClusterIPAddress
                    PsDscRunAsCredential  = $Node.SqlInstallCredential
                    DependsOn             = '[WindowsFeature]NetFramework35', '[WindowsFeature]NetFramework45'
                }
        }elseif(($Node.FailoverClusterNetworkName -ne $null) -and ($Node.ClusterSQLfirstNode -eq $false)){
        #Other nodes
           $InstallTask = '[SQLSetup]InstallSQLCluster'

            $NomPremierNoeud = ($AllNodes | where {$_.ClusterSQLfirstNode -eq $true} | Select-Object -First 1).NodeName
            WaitForAll "InstallationNoeud1"
            {
                ResourceName      = '[SQLSetup]InstallSQLClusterFirstNode'
                NodeName          = "$NomPremierNoeud"
                RetryIntervalSec  = 60
                RetryCount        = 60
            }

            SQLSetup 'InstallSQLCluster'
                {
                    Action                = "AddNode"
                    InstanceName          = $Node.InstanceName
                    SQLSvcAccount         = $Node.SqlServiceCredential
                    AgtSvcAccount         = $Node.SqlAgentServiceCredential
                    FTSvcAccount          = $Node.SqlFullTextCredential
                    RSSvcAccount          = $Node.SqlReplicationCredential
                    ISSvcAccount          = $Node.SqlIntegrationCredential

                    SourcePath            = $ConfigurationData.NonNodeData.SQLsources.SourcePath
                    UpdateEnabled         = $Node.UpdateEnabled
                    ForceReboot           = $Node.ForceReboot
                    SuppressReboot        = $Node.SuppressReboot
                    SQMReporting          = $Node.SQMReporting
                    SecurityMode          = $Node.SecurityMode
                    SAPwd                 = $Node.SAPWD

                    FailoverClusterGroupName = $Node.FailoverClusterGroupName
                    FailoverClusterNetworkName = $Node.FailoverClusterNetworkName
                    FailoverClusterIPAddress = $Node.FailoverClusterIPAddress
                    PsDscRunAsCredential  = $Node.SqlInstallCredential

                    DependsOn             = '[WaitForAll]InstallationNoeud1'
            }

I tried to reproduce the issue without DSC, by launching the same command line and SQLSetup throw
me the same error (something like the wrong credential as been passed for SQLAgent$) but.. there's no
credentials passed in the command line, this is the problem.
I added this piece of hardcoded at line 996 of MSFT_SqlSetup.psm1 just to prove my point:
if ($Action -in @('Addnode')) #ajout FRANCOIS ROUSSEAU
{
    $setupArguments += @{
        SQLSVCACCOUNT="domain\svcaccount"
    }
    $setupArguments += @{
       SQLSVCPASSWORD="pass"
    }
    $setupArguments += @{
        AGTSVCACCOUNT="domain\agentAccount"
    }
    $setupArguments += @{
       AGTSVCPASSWORD="pass"
    }
}

With the 4 missing parameters SQLSVCACCOUNT, SQLSVCPASSWORD, AGTSVCACCOUNT and
AGTSVCPASSWORD added to the setupArguments,  the AddNode is working properly. (I guess they're
only necessary when the SQLENGINE is installed...)
My log:
[[SqlSetup]InstallSQLCluster] Starting setup using arguments: /AGTSVCPASSWORD=""
/ACTION="AddNode" /SQLSVCPASSWORD="" /UPDATEENABLED="False"
/AGTSVCACCOUNT="domain\svcaccount" /INSTANCENAME="test"
/SKIPRULES="Cluster_VerifyForErrors" /IACCEPTSQLSERVERLICENSETERMS="True" /QUIET="True"
/SQLSVCACCOUNT="domain\agentAccount" /SQMREPORTING="False"
...
...
[[SqlSetup]InstallSQLCluster] Setup exited with code '0'. Setup finished successfully.
So all the pieces of the puzzle to fix the issue are there,
I hope this can help to fix that issue.
Version of the operating system and PowerShell the target node is running

SQL Server edition and version the target node is running
Edition  : Standard Edition
Version  : 11.4.7001.0
Language : 1033
What SQL Server PowerShell modules, and which version, are present on the target node.
Name         Version Path

xSqlServer   <IP_ADDRESS>
SQLASCMDLETS 1.0
SQLPS        1.0
Version of the DSC module you're using, or write 'dev' if you're using current dev branch
SqlServerDsc <IP_ADDRESS> C:\Program Files\WindowsPowerShell\Modules\SqlServerDsc\<IP_ADDRESS>\SqlServerDsc.psd1

Thanks for this information. It looks like /FEATURES argument is not allowed when /ACTION is 'AddNode', that is why the it's not added to the argument list.
https://github.com/PowerShell/SqlServerDsc/blob/9b6f76804acf1cf241afb8161f85e8a113ecf280/DSCResources/MSFT_SqlSetup/MSFT_SqlSetup.psm1#L1202-L1212
There are more code below these rows that might need to be added as well (and above?)
Wonder what other parameters should be added to the argument list, since we always check if the feature is passed in the $Features parameter. 🤔

Looking at this list, there might just be those for that you mention; https://docs.microsoft.com/en-us/sql/database-engine/install-windows/install-sql-server-from-the-command-prompt?view=sql-server-2017#AddNode

What I understand is that the code is based on what is in $Features but $Features is not allowed in AddNode (by command line it's true, but how DSC will do that if we can't pass the same list of features that were on the 'InstallFailoverCluster' section?)
And as you said, I think that they can be more of 4 parameters missing, in fact, it depends on what features are installed, but if you install AS, I guess you need to add ASSVCPASSWORD and ASSVCACCOUNT, and so on.

If the action is 'AddNode' we could just remove (or not add) the /FEATURES argument from the argumentlist.
There is a check here if it is Features argument, so if 'AddNode' we should just skip that argument and not add it.
https://github.com/PowerShell/SqlServerDsc/blob/4997ae4726171110bdac57122114487cab36ab55/DSCResources/MSFT_SqlSetup/MSFT_SqlSetup.psm1#L1354-L1367
This goes against that every property that is part of a configuration should be the desired state, but adding the Features property to an configuration that has Action = 'AddNode' would simplify code they way it's implemented today.
But maybe the problem is that we use the Features property to choose what properties is added to the argument list, for example if Features contain 'SQLENGINE' we add some properties - maybe we should change so that we always add parameters to the argument list if they are bound ($PSBoundParameters) and depending of what Action it is? 🤔


think about phase of sin (shouldn't two opposing phases interfere (0 and 180)?)

Also, why doesn't Gauss have a phase slider ._.

this maybe fixes something 2e0e1f5cd48440bdabb25d43a38aac90f130fed5


Collect all logs for e2e tests

When a test fail, all the logs should be collected and uploaded at the end of the test... it will save hours of debugging like it happened in this issue https://github.com/rancher/elemental/issues/410....
From the elemental node:
elemental-support
system-upgrade-controller
From the Rancher node (where Rancher manager is installed):
rancher pod logs
Maybe there is a command to generate all logs from rancher.

There is a script to collect all rancher logs: https://www.suse.com/support/kb/doc/?id=000020191


now the client idles and busy waits if he cannot connect to server

Added a function idle_till_server_connection which tries to connect to the server.
If it manages to do so everything continues like before. Otherwise if the error was of the type ConnectionRefused, which indicates that the server is not up yet, it busy waits and tries again. If the error had another type it panics and prints out the error type.

I added a quick fix, because before sometimes (not deterministic) there occurred a ConnectionReset error when the server finally starts and registers itself for the given socket. Now the client does not crash in that case but instead works as intended.


[BUG] RequestPlugin Remove Cookie

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
If there is only one cookie at a reques, I can‘t remove it when I want to；
Because the code judges that only when the return cookie is not empty, it will be updated
Expected Behavior
No response
Steps To Reproduce
No response
Environment
ShenYu version(s):

Debug logs
No response
Anything else?
No response

can you fix it？


[FEATURE] Create workflow with FOR EACH type

Is your feature request related to a problem? Please describe.
This is a feature provided by Databricks to use the For each task to run a task in a loop, passing a different set of parameters to each iteration of the task.
Cloud Information

[x] AWS
[ ] Azure
[ ] GCP
[ ] Other

Describe the solution you'd like
-Adding the For each task to a job requires defining two tasks: The For each task and a nested task. The nested task is the task to run for each iteration of the For each task and is one of the standard Databricks Jobs task types. You cannot add another For each task as the nested task.
-For example, you could use the For each task to perform a common set of transformations on multiple tables, passing a table name from a list of table names to each iteration of the task.
-Instead of creating 100 tasks for 100 table ingestion you can create one task and iterate over the list. It also helps to put a concurrency limit for your tasks which is not available in other type of jobs.
-It will also allow to run many processes using single task.
Describe alternatives you've considered
Currently we are creating 100 tasks for 100 tables ingestion.
Additional context
Add any other context or screenshots about the feature request here.

✋

Is there any work in progress for this ?


chore(avm-simulator): revive field comparison

Partially roll back #4516. Field comparison is needed in Brillig to assert bit sizes.

Benchmark results
Metrics with a significant change:

batch_insert_into_append_only_tree_16_depth_ms (8): 17.4 (+39%)
batch_insert_into_append_only_tree_16_depth_hash_ms (8): 0.735 (+38%)
note_history_successful_decrypting_time_in_ms (5): 1,268 (-23%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 8ffe5df7 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
5,700
18,884
36,452

l1_rollup_calldata_gas
66,156
239,000
469,664

l1_rollup_execution_gas
194,104
500,306
908,922

l2_block_processing_time_in_ms
1,214 (+2%)
4,538 (-2%)
9,068 (+1%)

note_successful_decrypting_time_in_ms
201 (+1%)
549 (+2%)
1,020 (+2%)

note_trial_decrypting_time_in_ms
110 (-2%)
68.6 (+17%)
59.2 (+62%)

l2_block_building_time_in_ms
16,684 (+4%)
63,839
128,424 (+1%)

l2_block_rollup_simulation_time_in_ms
12,659 (+4%)
48,530
97,687 (+1%)

l2_block_public_tx_process_time_in_ms
3,993 (+5%)
15,235 (+1%)
30,566 (+2%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
14,391 (-5%)
27,176 (-3%)

note_history_successful_decrypting_time_in_ms
:warning: 1,268 (-23%)
2,410 (-1%)

note_history_trial_decrypting_time_in_ms
100 (-15%)
158 (-1%)

node_database_size_in_bytes
18,817,104
35,397,712

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
249
44,736
28,001

private-kernel-ordering
179
52,625
14,627

base-rollup
1,296
177,932
933

root-rollup
71.3
4,192
825

private-kernel-inner
315 (-1%)
73,715
28,001

public-kernel-app-logic
193 (+1%)
32,254
25,379

merge-rollup
5.82
2,712
933

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
2 leaves
8 leaves
16 leaves
32 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves

batch_insert_into_append_only_tree_16_depth_ms
9.84
11.6 (+5%)
:warning: 17.4 (+39%)
16.4
22.1 (-5%)
35.8
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.9
17.5
23.0
31.6
47.0
79.0
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.570
0.642 (+5%)
:warning: 0.735 (+38%)
0.507
0.461 (-5%)
0.444
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
N/A
N/A
N/A
45.8
72.5 (-1%)
231
446
871 (-4%)
1,734

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
N/A
N/A
N/A
96.0
159
543
1,055
2,079
4,127

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
0.469
0.446 (-1%)
0.421
0.418
0.414 (-4%)
0.414

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
N/A
N/A
N/A
55.5 (+2%)
109 (+1%)
341 (+1%)
662
1,317 (-2%)
2,642 (+1%)

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
N/A
N/A
N/A
104
207
691
1,363
2,707
5,395

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
0.493 (+2%)
0.487
0.463
0.456
0.456 (-2%)
0.454

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
61.3
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
109
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
0.535
N/A
N/A
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts

tx_size_in_bytes
19,179

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes

tx_pxe_processing_time_ms
2,563 (-3%)
1,362

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
0.0327 (+8%)
471

Merge activity

Mar 6, 5:36 AM EST: @fcarreiro merged this pull request with Graphite.


feat(optimizer): support two phase topn and limit in batch mode

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
As title. related issue #3714.
Please explain IN DETAIL what the changes are in this PR and why they are needed:

Summarize your change (mandatory)
How does this PR work? Need a brief introduction for the changed logic (optional)
Describe clearly one logical change and avoid lazy messages (optional)
Describe any limitations of the current code (optional)

Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
In batch mode, TopN and Limit will be transformed to two phase stage to reduce the cost of data shuffling.
Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.

Plan Change

Refer to a related PR or issue link (optional)
related issue #3714.

to_local should also be changed? At least for limit

OK，let me see.

to_local should also be changed? At least for limit

I don't think so, the local mode is just in the single node and there is no same issue.

to_local should also be changed? At least for limit

I don't think so, the local mode is just in the single node and there is no same issue.

IIUC, local mode isn't just run in a single node, but just it's root stage is in frontend. It's still distributed..


Will V2 ever be released?

The last commit in the v2 branch was over a year ago. Will v2 ever be officially released?

Many think the project is abandoned

That's unfortunate. The V2 API is by far my favorite in comparison to other CLIs

Is there a fork being maintained? What's the alternative? I really like the api as well and would hate to see this get's abandoned.

This library is one of my favorites! I'll try to fork and do my bit. Let's see how it goes!

I think if any of the urfave team members could give those who like to maintain this project admin access, as that would ideal so that people will continue to use the same exact package and not forks of it.

I will try to contact the original team members and see where it leads to.

@asahasrabuddhe any news?  I agree that this is one the nicer CLI libraries available.  It would be nice to get it back into a maintained fork with proper go modules and go context support.

We still waiting to here from maintainers?

:wave: heya! We've got a few people who'd be interested in contributing to this project (including myself!) Might any of the existing maintainers be able to help us along / provide context? I'm gonna cast a wide net with my pings here - I like this CLI and definitely want to see it be improved!
cc @codegangsta / @meatballhat / @AudriusButkevicius / @blaubaer / @jszwedko / @gravis / @jamescun / @muraty / @thesyncim / @tianon / @txgruppi

one more try:
cc @codegangsta / @meatballhat / @AudriusButkevicius / @blaubaer / @jszwedko / @gravis / @jamescun / @muraty / @thesyncim / @tianon / @txgruppi

Whatever the end result is, please link to the fork in this issue so I know where to update my import paths. This is a fun, useful library, and I'll go wherever the developers are.

Everyone is free to fork it, have a v2 and maintain it.
There is a ton of PRs outstanding and no clear maintainer.
If you want to maintain this, you should speak up.
Sadly, I don't think I qualify as someone who can hand admin rights over, as my contribution was a single PR early on.
If there are particular PRs you want me to have a look shout, but I do not intend to properly maintain this.

@AudriusButkevicius see this comment: https://github.com/urfave/cli/issues/805#issuecomment-506621304
It would be best to hand over admin rights than to fork it so that we don't break users
That said, forking the repo is not a bad back up if no maintainer is willing to hand over rights to those in the community willing to maintain it.
Thanks

I can see there are 5 people with owner rights, one of them is me, other two haven't had any activity in the last year, the two that had activity, which is @meatballhat  and @jszwedko.
I guess I could add new members as non-admins and let them drive this and see how this goes.

I've created a new team, enabled enforcement of PR review by atleast 2 people, so ideally would like to gather multiple people, ideally from different companies etc to drive this forward.
If we don't get the candidates stepping up, I guess we can drop it down to 1.
I don't however want "yolo I do whatever I want, self approve PRs and force push to master" stuff.

I don't see myself maintaining the V2, I just won't have enough time :(

@AudriusButkevicius that sounds great. We can start with adding @lynncyrin to the team (if you are still willing to contribute!) and whoever was also willing to make the version 2 release happen.

I am willing to put in the effort and contribute!

We can start with adding @lynncyrin to the team (if you are still willing to contribute!) and whoever was also willing to make the version 2 release happen.

🤚  I'm very interested! I've been wanting a go package to work on ^^

I've created a new team, enabled enforcement of PR review by atleast 2 people, so ideally would like to gather multiple people, ideally from different companies (or rather, unrelated with no shared agenda to plant backdoors) etc to drive this forward.

This is great thinking @AudriusButkevicius 👍👍👍

If anyone interested in having a lower latency convo here, I'm in the gophers slack! It's pretty nice https://invite.slack.golangbridge.org/

I've invited you two to the team, let me know if you are able to review and close PRs. I thimk the first step would be to deal with the backlog of PRs.

🎉📈🎉
I also consider open PRs my top priority! The triage order that I used when working on Bundler was

new open PRs
old open PRs
new issues
old issues
epics (like V2)

So it may be a while before I starting this particular issue (eg. V2), but "a while" here means "just a few weeks" 🙂

To answer the title,

Will V2 ever be released?

Yes it will be! You can talk about that here => https://github.com/urfave/cli/issues/826


Fix excess number of queries

Problem
This fixes #274, which is a regression on Django 1.9/1.10 causing many unnecessary database queries, because the _get_sub_obj_recurse logic is run twice (once on the parent instance and again on the subclass instance). The cached values from the select_related(...) call in select_subclasses() get lost when selecting the subclass instances, and the database is hit again, for ~ each item in the queryset!
Solution
On Django >= 1.9, InheritanceQuerySetMixin.iterator() now yields from InheritanceIterable and doesn't re-run the _get_sub_obj_recurse logic.
Commandments

[x] Write PEP8 compliant code.
[x] Cover it with tests.
[x] Update CHANGES.rst file to describe the changes, and quote according issue with GH-<issue_number>.
[x] Pay attention to backward compatibility, or if it breaks it, explain why.
[ ] Update documentation (if relevant).

I also have a less minimal patch that removes the duplicated code, if that is preferred.

@tony any chance you could take a look at this one? I can confirm that we are using the "less minimal patch" in production and it appears to be working well

Superseeded by #389


Implement common query interface

Currently the Query type passed to store.findMany is undefined. It needs to be a common interface that makes sense in any store, not just the database store.

It needs to be mappable to typeorm's FindOptions
It must be transportable over json
Considerations for security must be taken (probably avoiding all join capabilities to avoid entity permission leak)
Consider severely limiting to force controllers to do the querying if security concerns are too great

Consider graphql, it makes sense across multiple database scheme & transports. Tough part may be data hydration


Refactor to scikit-matter

Opened PR to organize a bit the refactor.
I would merge first:

#140
#149

Anything else we want to reorganize except the name?

More or less copy paste from slack

Rename occurrences skcosmo -> skmatter
Rename occurrences scikit-cosmo -> scikit-matter
Check readthedocs what needs to be renamed(what needs to be renamed
pypi release with old name with a reference to the new github and/or pypi page
rename repo
pypi and release with new name

Took a look and made a few more changes, otherwise it looks great!


Use project based fixtures fo go_module specs

This PR introduces a project based setups for go_modules, meaning that
every test points to a fixture project, which we then turn into a git
repository for each test.
This sets us up for go mod tidy support, in which we'll always assume
that the repository has been checked out.

Scope creep: every project has a main.go located in the project root. I'd dig a sample with .../fixtures/not_root/cmd/main.go, since we have some weirdness around detecting main go files in the root.

Yeah good shout, I think we should add that in #2551, as the main.go files are actually not used in this iteration yet (we generate a dummy file for each update). I opted to already add them here, to make that diff smaller but I can also remove them here and introduce them in that PR.

Idea: maybe go_modules/spec/fixtures/projects $ for i in *; do cd $i; go mod download; cd ..; done

We don't actually want a go.sum in all of these, based on the historical test setup at least, but we can probably check if it's present. Are you thinking we should do this in CI or add a convenience script?

Are you thinking we should do this in CI or add a convenience script?

I was thinking a convenience script. Easy punt as it's only really useful once.
tbh I just wanted a 🤖 way to verify **/go.sums were ~sane in to  ✅ this PR.

We don't actually want a go.sum in all of these,

💯 ; the above added some untracked go.sums that I ignored - the out of date path go_mod/go.sum was the only 🤔 .

Scope creep: every project has a main.go located in the project root. I'd dig a sample with .../fixtures/not_root/cmd/main.go, since we have some weirdness around detecting main go files in the root.

@thepwagner I added a simple case here: https://github.com/dependabot/dependabot-core/pull/2551/commits/b555c7b6ce4ebe1ebd4f9894dfe98a236d95192a


YALRMI: Yet Another LuaRocks Magick Issue

I'm running an impractical setup for image.nvim, consisting of Ubuntu 22.04, Wezterm, and tmux. I believe I have everything installed properly yet it's still not working. I'm running into the infamous image.nvim: magick rock not found, please install it and restart your editor error.
Config details:
$ wezterm --version
wezterm 20240127-113634-bbcac864

$ tmux -V
tmux 3.2a

$ ls ~/.luarocks/share/lua/5.1/magick/
base_image.lua  enum.lua  gmwand  gmwand.lua  init.lua  thumb.lua  version.lua  wand  wand.lua

$ magick --version
Version: ImageMagick 7.1.1-27 Q16-HDRI x86_64 21931 https://imagemagick.org
Copyright: (C) 1999 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Cipher DPC HDRI OpenMP(4.5)
Delegates (built-in): fontconfig freetype jbig jng jpeg lzma pangocairo png tiff x xml zlib
Compiler: gcc (11.4)

$ luarocks --version
/usr/bin/luarocks 3.8.0
LuaRocks main command-line interface

$ luarocks --local install magick
Installing https://luarocks.org/magick-1.6.0-1.src.rock

magick 1.6.0-1 depends on lua 5.1 (5.1-1 provided by VM)
magick 1.6.0-1 is now installed in /home/arjun/.luarocks (license: MIT)

$ nvim -V1 -v
NVIM v0.10.0-dev-2201+g226466a46
Build type: RelWithDebInfo
LuaJIT 2.1.1706185428
Compilation: /usr/bin/cc -O2 -g -Og -g -flto=auto -fno-fat-lto-objects -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wvla -Wdouble-promotion -Wmissing-noreturn -Wmissing-format-attribute -Wmissing-prototypes -fsigned-char -fstack-protector-strong -fno-common -Wno-unused-result -Wimplicit-fallthrough -fdiagnostics-color=always  -DUNIT_TESTING -DHAVE_UNIBILIUM -D_GNU_SOURCE -DINCLUDE_GENERATED_DECLARATIONS -I/home/arjun/apps/neovim/.deps/usr/include/luajit-2.1 -I/home/arjun/apps/neovim/.deps/usr/include -I/home/arjun/apps/neovim/build/src/nvim/auto -I/home/arjun/apps/neovim/build/include -I/home/arjun/apps/neovim/build/cmake.config -I/home/arjun/apps/neovim/src -I/usr/include

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/share/nvim"

Run :checkhealth for more info

$ ueberzug --version
ueberzugpp 2.9.2

I've also added the set -gq allow-passthrough on line in my tmux config, if that's relevant.
If you need my neovim config I've linked it here because it's too much to paste.
Is image.nvim even possible for Wezterm?

After a bit more testing, I got it to work outside of tmux using the minimal config. When I used the minimal config inside of tmux, it said:
Failed to run `config` for image.nvim

...al/share/nvim/lazy/image.nvim/lua/image/utils/logger.lua:54: 16:42:06.006440 [image.nvim] tmux does not have allow-passthrough enabled

# stacktrace:
  - /image.nvim/lua/image/utils/logger.lua:54 _in_ **throw**
  - /image.nvim/lua/image/backends/kitty/init.lua:29 _in_ **setup**
  - /image.nvim/lua/image/init.lua:62 _in_ **setup**

... even though I had set -gq allow-passthrough on and reloaded(+restarted) my tmux config.

We check that passthrough is on with tmux show -Apv allow-passthrough, try running that inside tmux, it should output "on".

For me, this command did not work in tmux 3.2a. Once I updated to tmux 3.3a it started working. It might be worthwhile to put the working tmux versions in the README.
Regarding my situation now, minimal config works in tmux, but image.nvim still gives the same old image.nvim: magick rock not found, please install it and restart your editor error with my custom config. Are there any known conflicting plugins/setups? Why is there a magick rock installation problem on my config but no installation problem in the minimal one?
My neovim configuration is linked here but I know it might be tedious for you to look through it. If you could just point me in the general direction of where I should look for bugs that'd be great. Thanks!

Good news! I got it to work! For some reason the only way it would work is if I added event = "VeryLazy" to it. What I think was happening is initially at startup image.nvim wasn't able to find magick rock (don't know why) and then it just disabled itself. Instead, with VeryLazy on, it was able to find magick rock when it needed to, and worked.
Please let me know if my understanding is accurate! Thanks for this amazing plugin!

Glad it worked! Yeah, I think there's some weird stuff going on with lazy.nvim.
Yesterday I upgraded my Neovim and started to get the rock error as well, and traced it to lazy. For some reason, if lazy was loaded the rock couldn't be resolved anymore, but when I removed it there were no issues.
I reverted back to the Neovim version I had before, and there's no issue with that one, so something must've changed in Neovim that makes lazy break rocks.
Rocks should be available long before lazy does its thing  :shrug:

Having the same problem. Im not using lazy.nvim. And Im not using tmux.
[user@fedora ~]$ ls ~/.luarocks/share/lua/5.1/magick/
[base_image.lua  enum.lua  gmwand  gmwand.lua  init.lua  thumb.lua  version.lua  wand  wand.lua

[user@fedora ~]$ magick --version
[Version: ImageMagick 7.1.1-26 Q16-HDRI x86_64 21914 https://imagemagick.org
Copyright: (C) 1999 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Cipher DPC HDRI Modules OpenMP(4.5)
Delegates (built-in): bzlib cairo djvu fftw fontconfig freetype gslib gvc heic jbig jng jp2 jpeg jxl lcms lqr ltdl lzma openexr pangocairo png ps raqm raw rsvg tiff webp wmf x xml zip zlib zstd
Compiler: gcc (13.2)

[user@fedora ~]$ luarocks --version
[/usr/local/bin/luarocks 3.9.2
LuaRocks main command-line interface

[user@fedora ~]$ luarocks --local --lua-version=5.1 install magick
[Installing https://luarocks.org/magick-1.6.0-1.src.rock

magick 1.6.0-1 depends on lua 5.1 (5.1-1 provided by VM)
magick 1.6.0-1 is now installed in /home/user/.luarocks (license: MIT)

[user@fedora ~]$ nvim -V1 -v
[NVIM v0.9.5
Build type: Release
LuaJIT 2.1.1692716794

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/__w/neovim/neovim/build/nvim.AppDir/usr/share/nvim"

Run :checkhealth for more info

Also, I added these lines at the start of my /home/user/.config/nvim/init.lua:
package.path = package.path .. ";" .. vim.fn.expand("$HOME") .. "/.luarocks/share/lua/5.1/?/init.lua;"
package.path = package.path .. ";" .. vim.fn.expand("$HOME") .. "/.luarocks/share/lua/5.1/?.lua;"

What can be a problem here?

Having the same problem. Im not using lazy.nvim. And Im not using tmux.
[user@fedora ~]$ ls ~/.luarocks/share/lua/5.1/magick/
[base_image.lua  enum.lua  gmwand  gmwand.lua  init.lua  thumb.lua  version.lua  wand  wand.lua

[user@fedora ~]$ magick --version
[Version: ImageMagick 7.1.1-26 Q16-HDRI x86_64 21914 https://imagemagick.org
Copyright: (C) 1999 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Cipher DPC HDRI Modules OpenMP(4.5)
Delegates (built-in): bzlib cairo djvu fftw fontconfig freetype gslib gvc heic jbig jng jp2 jpeg jxl lcms lqr ltdl lzma openexr pangocairo png ps raqm raw rsvg tiff webp wmf x xml zip zlib zstd
Compiler: gcc (13.2)

[user@fedora ~]$ luarocks --version
[/usr/local/bin/luarocks 3.9.2
LuaRocks main command-line interface

[user@fedora ~]$ luarocks --local --lua-version=5.1 install magick
[Installing https://luarocks.org/magick-1.6.0-1.src.rock

magick 1.6.0-1 depends on lua 5.1 (5.1-1 provided by VM)
magick 1.6.0-1 is now installed in /home/user/.luarocks (license: MIT)

[user@fedora ~]$ nvim -V1 -v
[NVIM v0.9.5
Build type: Release
LuaJIT 2.1.1692716794

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/__w/neovim/neovim/build/nvim.AppDir/usr/share/nvim"

Run :checkhealth for more info

Also, I added these lines at the start of my /home/user/.config/nvim/init.lua:
package.path = package.path .. ";" .. vim.fn.expand("$HOME") .. "/.luarocks/share/lua/5.1/?/init.lua;"
package.path = package.path .. ";" .. vim.fn.expand("$HOME") .. "/.luarocks/share/lua/5.1/?.lua;"

What can be a problem here? Thanks for help

Ok. I found a solution)
sudo dnf install ImageMagick-devel


Java implementation of Dijkstra's algorithm

I'm contributing a Java implementation of Dijkstra's algorithm to your repository. It combines optimized code with fundamental theory. Your review and insights are invaluable as we enhance the repository's utility.
Happy coding :)

hello sir i want to contribute in this repository under hacktoberfest through the implementation of Dijkstra's Algorithm
i request you to assaign this task to me

@LokeshYarramallu  go ahead

@LokeshYarramallu  updates?

Insertion sort is applied to the array [55, 56, 58, 54, 56, 57] .What is the content of this array after three iterations of the outermost loop of the insertion sort algorithm?

Assign me this issue.

@huthifaahmas
After three iterations of the outermost loop, the array will look like this: [55, 56, 54, 58, 56, 57]


clangd-indexer asserts with "We assume that the input buffer has a null character at the end"

I am trying to index my project in an attempt to make clangd faster. At [275/1125] I get the following error:
clangd-indexer: /home/user/drive/llvm/llvm-project/clang/lib/Lex/Lexer.cpp:87: void clang::Lexer::InitLexer(const char*, const char*, const char*): Assertion `BufEnd[0] == 0 && "We assume that the input buffer has a null character at the end" " to simplify lexing!"' failed. [276/1125] Processing file ....cpp  #0 0x00005555aa6711d5 llvm::sys::PrintStackTrace(llvm::raw_ostream&) /home/user/drive/llvm/llvm-project/llvm/lib/Support/Unix/Signals.inc:532:0  #1 0x00005555aa671268 PrintStackTraceSignalHandler(void*) /home/user/drive/llvm/llvm-project/llvm/lib/Support/Unix/Signals.inc:593:0  #2 0x00005555aa66f121 llvm::sys::RunSignalHandlers() /home/user/drive/llvm/llvm-project/llvm/lib/Support/Signals.cpp:68:0  #3 0x00005555aa670b8c SignalHandler(int) /home/user/drive/llvm/llvm-project/llvm/lib/Support/Unix/Signals.inc:384:0  #4 0x00007fd4346cb890 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x12890)  #5 0x00007fd433580e97 raise /build/glibc-OTsEL5/glibc-2.27/signal/../sysdeps/unix/sysv/linux/raise.c:51:0  #6 0x00007fd433582801 abort /build/glibc-OTsEL5/glibc-2.27/stdlib/abort.c:81:0  #7 0x00007fd43357239a __assert_fail_base /build/glibc-OTsEL5/glibc-2.27/assert/assert.c:89:0  #8 0x00007fd433572412 (/lib/x86_64-linux-gnu/libc.so.6+0x30412)

The recommended indexing method is background-index nowadays, which can be enabled by passing -background-index into clangd. That aside, indexing won't really make clangd faster. What are you trying to achieve exactly?

I wanted to make a comparison between background-index and clangd-indexer.
I am very new to the tool and I am trying to find out the best configuration for me. I find clangd to struggle a little bit with the dimension of my project and wanted to create the index only once. I guess clangd --compile-commands ... --background-index is all I need?
I believe the results of --background-index go into /.clangd and that that has almost the same effect as what I was trying to achieve with  clangd-indexer?
Pardon my ignorance.

well if you want speed you should definitely go with background-index, because it builds incrementally(will only index files that have changed since last indexing) whereas clangd-indexer will run from scratch every time.
As for a comparison they both improve the quality of code navigation and completion, but background-index is a lot more automated compared to clangd-indexer. With the latter you must trigger indexing every now and then, and also tell clangd about where the index file is.

I believe the results of --background-index go into /.clangd and that that has almost the same effect as what I was trying to achieve with clangd-indexer?

Yes, but you shouldn't care about where the index shards go into. Clangd will find and load them automatically if you've passed --background-index


Update submodule, small README fixes

You need to update the tests.py file with the new number of English words for the test to pass.


Copying range to another cell

Hi @dtjohnson ! Is there any way to copy an existing range or cell to another position in the workbook? I was working with a template and wanted to copy a component to another part of the sheet.
Thanks!

This is not a trivial feature request since xlsx-populate does not yet fully support xlsx and references would also need to be maintained. If copying cells was implemented, it would have to be limited.

let templateRange = sheet1.range(srcRowStart, srcColStart, srcRowEnd, srcColEnd)
// copy
let templateValues = templateRange.value()
let templateStyles = templateRange.style([
  'bold',
  'italic',
  'underline',
  'strikethrough',
  'fontSize',
  'fontFamily',
  'fontColor',
  'horizontalAlignment',
  'verticalAlignment',
  'wrapText',
  'shrinkToFit',
  'textDirection',
  'textRotation',
  'verticalText',
  'fill',
  'border',
  'numberFormat',
])
let templateRowHeights = []
for (let i = srcRowStart; i <= srcRowEnd; i++) {
  templateRowHeights.push(sheet1.row(i).height())
}
// paste
let rowCount = srcRowEnd - srcRowStart + 1
let colCount = srcColEnd - srcColStart + 1
sheet1.range(destRowStart, destColStart, destRowStart + rowCount - 1, destColStart + colCount - 1)
  .value(templateValues)
  .style(templateStyles)
for (let i = 0; i < rowCount; i++) {
  sheet1.row(destRowStart + i).height(templateHeights[i])
}

This should be able to copy value, style and row height to the destination (worked for me). However, my Excel is very simple (table with header + data, only used font color, fill, border and some number formats), I have not tested it with more complicated cases, e.g. I doubt that you can copy formula with this.

After looking into the implementation, I think maybe adding Cell.style() and Range.style() (without any parameter to return the Style or Style[] instances) would be a good start?

I feel like I should comment an easier implementation, although this does not copy as many styles as the previous example. This works because range cell access starts at [0,0] so the indices of the destination and source are aligned.
export function copyRanges(sourceRange: any, destRange: any) {
  sourceRange.forEach((cell: any, rowIndex: number, columnIndex: number) => {
    const destCell = destRange.cell(rowIndex, columnIndex);

    // get style object from current cell
    const style = cell.style([
      "numberFormat",
      "fill",
      "fontColor",
      "verticalAlignment"
    ]);

    // set the values of the destination cell
    destCell.value(cell.value());

    // set the styles of the cell
    destCell.style(style);
  });
}

@mdgozza Thank you. But some cell, it's value is Array, then will copy fail. destcell will be empty.
But it's enough. I just want to keep an empty template. then always copy row1 styles. It works.


TargetFormat.Pkg build fails

MacOS building native distribution in pkg format fails. Error is reported by jpackage:
Bundler Mac PKG Package skipped because of a configuration problem: "Missing --main-jar parameter for non modular application

(file ./build/compose/logs/packagePkg/jpackage-2021-12-14-19-10-24-err.txt)

Any updates on this? I'm also having this issue. Using jpackage directly works, though (jdk17.0.2).

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Custom Screenshot Grabber fails to take screenshot (Java)

Expected behavior
Custom screenshot grabber should be used in Java to take a screenshot and attach it to the html-report
Actual behavior
Gauge reports that the custom screenshot grabber failed to run and that a regular screenshot will be taken. The reports do contain a screenshot, but its not using the selenium webdriver screenshot method. When there is a test failure and screenshot on failure is on, i believe the custom screenshot grabber IS used as expected because the screenshots look different. Compare the screenshots between test steps This is some random step that we did and the failure screenshot in Go to Gauge Get Started Page. Source code is attached below.
Error
Failed to take Custom screenshot: com.example.CustomScreenShotGrabber : null
Capturing regular screenshot..

Steps to reproduce

Run gauge init java_maven_selenium
Add a custom class that implements ICustomScreenshotGrabber. See Below for implementation
Call Gauge.captureScreenshot() in your test step.

Custom Screenshot Grabber
public class CustomScreenShotGrabber implements ICustomScreenshotGrabber
{
    @Override
    public byte[] takeScreenshot()
    {
        System.out.println("Going to take a screenshot.");
        return ((TakesScreenshot)Driver.webDriver).getScreenshotAs(OutputType.BYTES);
    }
}

Test Step calling Screenshot Capture
@Step("This is some random step that we did")
public void screenshotWithComments()
{
  Gauge.captureScreenshot();
  Gauge.writeMessage("This Screenshot shows what happens after A");
}

Gauge.java
When calling Gauge.captureScreenshot() from a test step, the ClassInstanceManager  seems to be null.
public class Gauge {
    // extra stuff omitted.

    private static ClassInstanceManager instanceManager;

    public static void captureScreenshot() {
        byte[] screenshotBytes = (new ScreenshotFactory(instanceManager)).getScreenshotBytes();
        getScreenshots().add(screenshotBytes);
    }
}

Log Snippet (Running from IntelliJ)
Testing started at 3:47 PM ...
gauge.exe run --machine-readable --hide-suggestion --simple-console D:/Development/work/sample-screenshot/specs/example.spec
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".

SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

Starting ChromeDriver 73.0.3683.20 (8e2b610813e167eee3619ac4ce6e42e3ec622017) on port 34049

Only local connections are allowed.
Please protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code.

Feb 25, 2019 3:47:15 PM org.openqa.selenium.remote.ProtocolHandshake createSession
INFO: Detected dialect: OSS

Failed to take Custom screenshot: com.example.CustomScreenShotGrabber : null

Capturing regular screenshot..

Failed to take Custom screenshot: com.example.CustomScreenShotGrabber : null

Capturing regular screenshot..

Going to take a screenshot.

Failed: Go to Gauge Get Started Page
Filename: D:\Development\work\sample-screenshot\specs\example.spec:14
Message: org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//a[@href='/getting-started-guide/we-start']"}
  (Session info: chrome=72.0.3626.109)
  (Driver info: chromedriver=73.0.3683.20 (8e2b610813e167eee3619ac4ce6e42e3ec622017),platform=Windows NT 10.0.17763 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html

Session ID: 989a2433ab50bf94a916895a16d72db8
*** Element info: {Using=xpath, value=//a[@href='/getting-started-guide/we-start']}
Stack Trace:
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
java.lang.reflect.Constructor.newInstance(Constructor.java:423)
org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214)
org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166)
org.openqa.selenium.remote.http.JsonHttpResponseCodec.reconstructValue(JsonHttpResponseCodec.java:40)
org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:80)
org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:44)
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:158)
org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:543)
org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:317)
org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:419)
org.openqa.selenium.By$ByXPath.findElement(By.java:353)
org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:309)
com.example.StepImplementation.gotoGetStartedPage(StepImplementation.java:18)

Successfully generated html-report to => D:\Development\work\sample-screenshot\reports\html-report\index.html

Specifications:	1 executed	0 passed	1 failed	0 skipped
Scenarios:	1 executed	0 passed	1 failed	0 skipped

Total time taken: 14.053s

Process finished with exit code 1

Source Code Attachment
sample-screenshot.zip
Gauge version
Gauge version: 1.0.4
Commit Hash: 3a9a647

Plugins
-------
flash (0.0.1)
go (0.1.2)
html-report (4.0.7)
java (0.7.1)
json-report (0.2.2)
screenshot (0.0.1)
spectacle (0.1.3)
xml-report (0.2.1)

I am able to replicate it with the below version.(Tried in vs code)
[ERROR] Failed to execute goal com.thoughtworks.gauge.maven:gauge-maven-plugin:1.3.3:execute (default) on project sample-screenshot: Gauge Specs execution failed. null: GaugeExecutionFailedException -> [Help 1]

Gauge version: 1.0.5.nightly-2019-02-22
Commit Hash: 9c38118
Plugins
dotnet (0.1.2.nightly-2019-02-22)
html-report (4.0.8.nightly-2019-02-25)
java (0.7.2.nightly-2019-02-22)
js (2.3.5.nightly-2019-01-30)
python (0.3.6.nightly-2019-02-14)
ruby (0.5.2)
screenshot (0.0.1)
spectacle (0.1.4.nightly-2018-12-04)
xml-report (0.2.1)

This issue was moved to getgauge/gauge-java#254


disagg: Increase default establish disagg task timeout

What problem does this PR solve?
Issue Number: close https://github.com/pingcap/tiflash/issues/8148
Problem Summary: The default timeout 15 seconds is too short for a table with about 3TB data, the EstablishDisaggTask actually takes about 20 seconds
What is changed and how it works?

Increase the default timeout to be 60 seconds
Allow setting larger timeout through profiles.default.disagg_build_task_timeout

Increasing the default timeout to handle it now. For further improvement, we should put the delta-cache into the FetchPages streaming RPC https://github.com/pingcap/tiflash/issues/8143
Check List
Tests

[ ] Unit test
[ ] Integration test
[x] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/run-all-tests

/rebuild

/run-integration-test

/run-integration-test

/cherry-pick release-7.4


what is the correct format of python command?

Hi guys,
i am running tensorflow-gpu in windows environment of anaconda. the backslash \ doesnt work in anaconda prompt eg:
python train_model.py \     --training_data=rnn_tutorial_data/training.tfrecord-?????-of-????? \     --eval_data=rnn_tutorial_data/eval.tfrecord-?????-of-????? \     --classes_file=rnn_tutorial_data/training.tfrecord.classes
it works in my ubuntu terminal. i dont want to mess with ubuntu cuz the cuda is 9.1 which doesnt support tensorflow1.6 yet.  what is the correct format command in windows of \ backslash?
Hope to hear your suggestions.

The eqiuvalent character in the Windows command prompt is ^.
https://stackoverflow.com/q/69068/3574081

thank you @mrry! you are the best.


know if the Openwhisk action is executed on a prewarm container by receiving the log from API

I install openwhisk via kubernetes cluster. I invoke my actions through the API and also receive their logs via API. But in the log, it is only known whether the action is cold or warm, through initTime annotation. And it is not clear whether the cold action is executed on a cold container or preWarmed container.
I tried to access this information through the user-events service and metrics endpoint via kubectl port forwarding and localhost:9095/metrics. But at this endpoint, only the cold start number is specified.
How do I know if the action is executed on a prewarm container?

The system does not record the container allocation - so this is not possible without modifying the metric generation or the annotations on activations.

The system does not record the container allocation - so this is not possible without modifying the metric generation or the annotations on activations.

can you suggest a metric for this?

I feel this implies more fine-grained starting types such as prewarm, cold, recreated, and warm in activation results?

What’s the use case for knowing this?
I thinks it’s for research purposes. Is it useful otherwise?

What’s the use case for knowing this?
I thinks it’s for research purposes. Is it useful otherwise?

I just need this metric for my work and to get the exact activation logs

Since we already expose cold and warm to users, I just want to provide more fine-grained information.
For example, even if an activation denotes a cold start, the wait time can vary when prewarm is used or the container is recreated.
From the operator perspective, I wanted it to figure out the performance difference among different start types.
With ElasticsearchActivationStore, we can easily get the statistics and dashboard for each type.

Since we already expose cold and warm to users, I just want to provide more fine-grained information.
For example, even if an activation denotes a cold start, the wait time can vary when prewarm is used or the container is recreated.
From the operator perspective, I wanted it to figure out the performance difference among different start types.
With ElasticsearchActivationStore, we can easily get the statistics and dashboard for each type.

Can you please explain more? I have never worked with Elasticsearch. How can I access the activation logs through the API using Elasticsearch?

@parichehrvn You can use Elasticsearch as an activation store.
https://github.com/apache/openwhisk/blob/f788d095565c14d3a2908cdf71215498a5512b36/ansible/README.md#using-elasticsearch-to-store-activations
But only cold and warm start type is available now.
Also, we can indirectly infer the start type by the existence of "initTime" but there is no explicit field for them.
So I doubt you can directly get some statistics using the start type.
But the wsk CLI is already exposing the start type.
$ wsk activation list
Datetime            Activation ID                    Kind      Start Duration   Status  Entity
2020-10-28 13:05:29 64b84f88d5f345c5b84f88d5f335c5c8 nodejs:10 cold  31ms       success style95/env:0.0.7
2020-10-28 13:05:29 79950b09eb5f4581950b09eb5fb58158 unknown   warm  0s         success style95/zxcvasdfasdfasdf:0.0.2

So I imagined explicitly adding such information in annotations.
Then we can query Elasticsearch using the field.

This requires code changes in the invoker. I think the metric has to be emitted from the container proxy which will know if it's a pre-warm container or a new container. The information has to be retained until the activation record is created so that it's added as an annotation.


Constructor on type 'SQLCC.Impl.MsSqlProvider.MsSqlProvider' not found.

Constructor on type 'SQLCC.Impl.MsSqlProvider.MsSqlProvider' not found.
AssemblyLoader.cs: Line 68
here's the line that the exception occurs on:
return (T)Activator.CreateInstance(type, args);
it's because args = object[0] and there is no constructor for MsSqlProvider that accepts that as input.
debugging GetNamedArgumentArray shows something interesting happen on line 84:
if (providedSignature != orderedParams) continue;

Here's the local variables being compared:
orderedParams	"dbp.applicationName,dbp.connString,dbp.traceDir"	string
providedSignature	"dbp.applicationName,dbp.connString,dbp.traceDir,dbp.traceName"	string
there are no other constructors, so the foreach ends, so then the last line of the method is:
return new object[0];

This error occurs when the config file is edited (per instructions from issue: KeyNotFoundException) (config addition below)
<add key="dbp.traceName" value="TraceFile" />

I've removed the above line from the config file, and added --app.traceName to the arguments when running the EXE and all seems well.  Looks like we need an update to support dbp.traceName in the config file.

Closed due to no response


Issue running under wine

Wine (even in the latest 6.11 version) doesn't implement to entirety of SetFileInformationByHandle, notably in this crate's case, FILE_DISPOSITION_INFO, which can cause hangs when used.
I don't consider this a super high priority issue since this can be worked around by just...not calling remove_dir_all, but figured I would mention this in case someone else runs up against this issue and/or wants to fix it it by using a fallback method or the like.

What's the bug link for this in wine?

Thank you for your issue! You can also try downgrading to 0.5 in the meantime which does not use SetFileInformationByHandle .

This has perhaps gotten worse with the TOCTOU fixes? I'll note that rust itself since the overhaul of remove_dir_all in the std library also uses NtCreateFile and SetFileInformationByHandle. I'm very open to non-intrusive patches to support wine users, but ultimately it is on Wine as an emulator, to well, emulate.

Since the release of the Steamdeck, wine's support has gotten a lot better, and I think this issue might be resolved. Would you be able to confirm @Jake-Shadle?

I did a quick check with wine64. Runs without error, but given a tree of symlinks/dirs/files, it didn't delete the symlinks, but the NtCreateFile and SetFileInformationByHandle doesn't seem to be a concrete problem.
wine64 --version
wine-5.0.3 (Ubuntu 5.0.3-3ubuntu2)

I'm going to close it for now then, and we can make a issue or re-open if it comes up again.