[AUTOPATCHER-CORE] Upgrade openvswitch to 2.15.7 to fix CVE-2022-4338, CVE-2022-4337 -

[AUTOPATCHER-CORE] Upgrade openvswitch to 2.15.7 to fix CVE-2022-4338, CVE-2022-4337
Upgrade pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=293587&view=results
AMD64 build -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=293615&view=results
ARM64 build -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=293616&view=results

The test builds failed, and I have a separate PR for this change #4641


🚀 Feature: Add allcontributors

Bug Report Checklist

[X] I have tried restarting my IDE and the issue persists.
[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Overview
I like those tables like on https://github.com/LearningTypeScript/projects#contributors- 😄
Additional Info
No response

Done!


R: passing train parameters is inconvenient

In the R package, when one wants to fit a model, the functions have an argument params, where one passes an R list.
This is inconvenient and makes it hard to find the right parameter names. Would be better if either:

There was a function lgb.Params which would simply be a constructor wrapper returning a list of the parameters but with documented arguments, so that one could get autocomplete and pop-up documentation in IDEs by doing something like this:

model <- lightgbm(
  data,
  params=lgb.Params(<tab here>)
)

The functions accepted and documented their arguments without needing to pass them as a list.

Thanks very much for the recommendation!
I'm strongly opposed to removing the interface of passing parameters as a list to params. At this point, that would be a very impactful breaking change that would affect most users of LightGBM.
However, I'm open to more discussion on the idea of a function which can make the process of setting parameters easier. So far we've been hesitant to take that on because it introduces some maintenance burden and because copying the details of the LightGBM core library into wrapper packages introduces a risk of inconsistencies (like the one you've already noted in #4196).
Some questions about such a function:

would you want every parameter in https://lightgbm.readthedocs.io/en/latest/Parameters.html to have a corresponding keyword argument in this function?
would you want the arguments in this function to all have the default values documented in https://lightgbm.readthedocs.io/en/latest/Parameters.html, or would you rather that they have no defaults so you have to explicitly choose a value for each?
would you want Dataset parameters like max_bin (https://lightgbm.readthedocs.io/en/latest/Parameters.html#dataset-parameters) to be handled in this function too?

But it doesn't need to be a breaking change. What I suggest would be simply to make a function with documented arguments that would return a list with the same elements and values - e.g.
Parameters <- function(arg1=10, arg2="a") {
    return(as.list(environment()))
}

But with those arguments documented and already set to their defaults (or perhaps to NULL, guess the effect is the same), so that it would play along with RStudio and other IDEs documentation browser, tooltips, and autocomplete.
I think it should be possible to auto-generate such a file from the html or the documentation system of the C++ library, maybe adding a note that it's autogenerated.
And yes, would be nice if the R package documentation would mention everything that's possible to pass.

But it doesn't need to be a breaking change

Right, but the other proposal in https://github.com/microsoft/LightGBM/issues/4195#issue-860695422, "The functions accepter their arguments without needing to pass them as a list", would be a breaking change.

What I suggest would be simply to make a function with documented arguments that would return a list with the same elements and values

I'm open to the idea of a function like lgb.generate_parameters() that is similar to the one you've described, and it would be interesting to try to auto-generate it. I understand how that could make the experience in an IDE a bit easier and how that could be done in a way that is non-breaking.

Are you interested in working on a feature like that?
Have you worked with other machine learning libraries that do something like that, which you think would serve as a good reference?

I'll pass on making a parser from the html, but can provide you some example libraries which have a parameters constructor:

C50 (C5.0Control)
caret ``trainControl`
partykit (ctree_control)

Although those are all R exclusives and the function are not auto-generated.

Alright, thanks.
Since you're not interested in contributing this, I'll add it to this project's backlog of feature requests. In this project, we manage feature requests in a single issue (see #2302). I'll move this there, close this issue, and update the title to more accurately reflect the feature request.

Feature description
For anyone arriving at this issue, please comment if you'd like to contribute this feature. It can be summarized as follows.
Add a new exported function, lgb.generate_parameters(), to the R package with the following characteristics:

Has one keyword argument for each "main" (non-alias) parameter listed at https://lightgbm.readthedocs.io/en/latest/Parameters.html
Has @param roxygen documentation for each parameter, with the same text as the corresponding parameters in https://lightgbm.readthedocs.io/en/latest/Parameters.html (unless any R-specific details might improve usability, such as https://github.com/microsoft/LightGBM/issues/4192#issuecomment-822025193
Returns a named list where element names are parameters and values are the value passed into this function

Since the goal of this function would be primarily to support interactive use, it does not need to support aliases for parameters (e.g. n_iter instead of num_iterations).
If possible, this function and its documentation should be automatically generated from https://github.com/microsoft/LightGBM/blob/7ea2bc4dbca53c03eaae2aa2b22f9b30447caea4/include/LightGBM/config.h. You can see https://github.com/microsoft/LightGBM/blob/7ea2bc4dbca53c03eaae2aa2b22f9b30447caea4/helpers/parameter_generator.py for inspiration. At a minimum, to ensure that this function remains consistent with LightGBM's core library, tests should be added which will break if any inconsistencies are detected (similar to https://github.com/microsoft/LightGBM/blob/7ea2bc4dbca53c03eaae2aa2b22f9b30447caea4/.ci/test.sh#L50-L51).


Action to mark an activity as private

I would love to have an action to mark an activity as private, i.e. change the privacy controls option "Who Can See" to the value "Only You".

Unfortunately this is not possible anymore :-( Strava removed the privacy settings from their API some years ago. If in the future I find any other way to change privacy controls again I will surely implement it.

Bummer. I like to upload my short workouts drills to Strava but don't want them to spam my activity feed.


Add section heads to help commands.

Fixes: #9936
This is a WIP.  When done I'll remove the TODO file.

If someone can take a look at the output, I'd like an opinion of there should be blank line before each section.

First pass done; all programs with >=20 help lines: asn1parse ca cms crl dgst ecparam enc ocsp pkcs12 pkcs8 pkeyutl req rsa rsautl s_client s_server smime speed ts verify x509

All commands done, out of WIP, ready for review.

in order to entice folks to look at and review this, here's some output:
; ./apps/openssl rsa --help
Usage: rsa [options]

General options:
 -help              Display this summary
 -check             Verify key consistency
 -*                 Any supported cipher
 -engine val        Use engine, possibly a hardware device

Input options:
 -in val            Input file
 -inform format     Input format, one of DER PEM
 -pubin             Expect a public key in input file
 -RSAPublicKey_in   Input is an RSAPublicKey
 -passin val        Input file pass phrase source

Output options:
 -out outfile       Output file
 -outform format    Output format, one of DER PEM PVK
 -pubout            Output a public key
 -RSAPublicKey_out  Output is an RSAPublicKey
 -passout val       Output file pass phrase source
 -noout             Don't print key out
 -text              Print the key in text
 -modulus           Print the RSA key modulus

PVK options:
 -pvk-strong        Enable 'Strong' PVK encoding level (default)
 -pvk-weak          Enable 'Weak' PVK encoding level
 -pvk-none          Don't enforce PVK encoding
;
; ./apps/openssl rand --help
Usage: rand [flags] num

General options:
 -help               Display this summary
 -engine val         Use engine, possibly a hardware device

Output options:
 -out outfile        Output file
 -base64             Base64 encode output
 -hex                Hex encode output

Random state options:
 -rand val           Load the file(s) into the random number generator
 -writerand outfile  Write random data to the specified file

For common options (OPT_[VSXR]_OPTIONS in apps/lib/opt.c), as shown in the "Random state options" text above, the prolog is common text.

fixup commit pushed.

As for the Input, Output, Input/Output: if there were a bunch of options, or I thought it made sense, I divided them into sections, otherwise I didn't.  I agree it might be better to go for consistency, but I also dislike a section that has only one option (yes sometimes that is unavoidable).
I hope that this topic can be addressed in a separate PR.  (Probably by someone else :)

My approval still holds.

ping @openssl/omc for 2nd review

Another sample, to entice reviewers:
; ./apps/openssl pkcs7 --help
Usage: pkcs7 [options]

General options:
 -help             Display this summary
 -engine val       Use engine, possibly a hardware device

Input options:
 -in infile        Input file
 -inform PEM|DER   Input format - DER or PEM

Output options:
 -outform PEM|DER  Output format - DER or PEM
 -out outfile      Output file
 -noout            Don't output encoded data
 -text             Print full details of certificates
 -print            Print out all fields of the PKCS7 structure
 -print_certs      Print_certs  print any certs or crl in the input
;

Travis failures seem relevant, there seems to be some option duplication in some commands.

Yeah, the rebase broke the apps/enc.c. There are added duplicate options in, out, and pass.

OK, re-approved now.
ping @levitte ?

Another sample:
; ./apps/openssl ocsp --help
Usage: ocsp [options]

General options:
 -help                   Display this summary
 -ignore_err             Ignore error on OCSP request or response and continue running
 -CAfile infile          Trusted certificates file
 -CApath infile          Trusted certificates directory
 -no-CAfile              Do not load the default certificates file
 -no-CApath              Do not load certificates from the default certificates directory

Responder options:
 -timeout +int           Connection timeout (in seconds) to the OCSP responder
 -resp_no_certs          Don't include any certificates in response
 -multi +int             run multiple responder processes
 -no_certs               Don't include any certificates in signed request
 -badsig                 Corrupt last byte of loaded OSCP response signature (for test)
 -CA infile              CA certificate
 -nmin +int              Number of minutes before next update
 -nrequest +int          Number of requests to accept (default unlimited)
 -reqin val              File with the DER-encoded request
 -signer infile          Certificate to sign OCSP request with
 -sign_other infile      Additional certificates to include in signed request
 -index infile           Certificate status index file
 -ndays +int             Number of days before next update
 -rsigner infile         Responder certificate to sign responses with
 -rkey infile            Responder key to sign responses with
 -rother infile          Other certificates to include in response
 -rmd val                Digest Algorithm to use in signature of OCSP response
 -rsigopt val            OCSP response signature parameter in n:v form
 -header val             key=value header to add
 -rcid val               Use specified algorithm for cert id in response
 -*                      Any supported digest algorithm (sha1,sha256, ... )

Client options:
 -url val                Responder URL
 -host val               TCP/IP hostname:port to connect to
 -port +int              Port to run responder on
 -out outfile            Output filename
 -noverify               Don't verify response at all
 -nonce                  Add OCSP nonce to request
 -no_nonce               Don't add OCSP nonce to request
 -no_signature_verify    Don't check signature on response
 -resp_key_id            Identify response by signing certificate key ID
 -no_cert_verify         Don't check signing certificate
 -text                   Print text form of request and response
 -req_text               Print text form of request
 -resp_text              Print text form of response
 -no_chain               Don't chain verify response
 -no_cert_checks         Don't do additional checks on signing certificate
 -no_explicit            Do not explicitly check the chain, just verify the root
 -trust_other            Don't verify additional certificates
 -no_intern              Don't search certificates contained in response for signer
 -respin val             File with the DER-encoded response
 -VAfile infile          Validator certificates file
 -verify_other infile    Additional certificates to search for signer
 -path val               Path to use in OCSP request
 -cert infile            Certificate to check
 -serial val             Serial number to check
 -validity_period ulong  Maximum validity discrepancy in seconds
 -signkey val            Private key to sign OCSP request with
 -reqout val             Output file for the DER-encoded request
 -respout val            Output file for the DER-encoded response
 -issuer infile          Issuer certificate
 -status_age +int        Maximum status age in seconds

Validation options:
 -policy val             adds policy to the acceptable policy set
 -purpose val            certificate chain purpose
 -verify_name val        verification policy name
 -verify_depth int       chain depth limit
 -auth_level int         chain authentication security level
 -attime intmax          verification epoch time
 -verify_hostname val    expected peer hostname
 -verify_email val       expected peer email
 -verify_ip val          expected peer IP address
 -ignore_critical        permit unhandled critical extensions
 -issuer_checks          (deprecated)
 -crl_check              check leaf certificate revocation
 -crl_check_all          check full chain revocation
 -policy_check           perform rfc5280 policy checks
 -explicit_policy        set policy variable require-explicit-policy
 -inhibit_any            set policy variable inhibit-any-policy
 -inhibit_map            set policy variable inhibit-policy-mapping
 -x509_strict            disable certificate compatibility work-arounds
 -extended_crl           enable extended CRL features
 -use_deltas             use delta CRLs
 -policy_print           print policy processing diagnostics
 -check_ss_sig           check root CA self-signatures
 -trusted_first          search trust store first (default)
 -suiteB_128_only        Suite B 128-bit-only mode
 -suiteB_128             Suite B 128-bit mode allowing 192-bit algorithms
 -suiteB_192             Suite B 192-bit-only mode
 -partial_chain          accept chains anchored by intermediate trust-store CAs
 -no_alt_chains          (deprecated)
 -no_check_time          ignore certificate validity time
 -allow_proxy_certs      allow the use of proxy certificates
;

For the record my approval still holds.

I had to rebase this because #8442 added new flags to several commands.  There were, of course, merge conflicts.  No other changes were made.
Seeking reviews.  First opened September 19.  No feedback (except poor patient @t8m :) for nearly a month.

My approval still holds. It would be nice if @openssl/omc provided the second review soon to avoid further merge conflicts.

I believe we should focus on real errors/mistakes and not try to achieve perfection in this PR. IMO  even in the state as it is now it would be major improvement over the current situation.

I don't understand your question.

(PS:  Want to tweak the labels so the 24hour hold timer works?)

I'm wondering why there are OPT_MORE_STR lines in the text.  They seem to be manually putting line breaks in places -- this could be automated.
It's quite poissible I missing something egregious.

The number really didn't change.  Auto-wrapping the text would be more trouble than it's worth for the roughly-a-dozen lines:
; g m
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
; g grep OPT_MORE_STR | wc
     14     105     859
; g co app-help-categories
Switched to branch 'app-help-categories'
; g grep OPT_MORE_STR | wc
     13      91     750
;

Merged to master.  Thanks for the effort and endurance on of this one.


A question about PO ID system

Hello! I'm new to Plant Ontology database, and while checking the definition of PO terms, I'm wondering how the ID system is built. To be more specific, the accession number of "plant embryo proper" is PO:0000001, so what do the seven digits represent, respectively? Thank you.

The seven digit accession numbers, which are preceded by a 2 or 3 letter code are created during curation of the term into the ontology.  They are unique identifiers, sort of like a social security number and form part of a universal resource identifier (URI) for each term.  They are never reused, so if the term is deprecated, the PO:ID is retired.  This is standard practice in the ontology community.  You can compare with the ones used by the Gene Ontology.

Thank you! So are the 7 digits organized in some specific manner, like first one or two digits represent something, and the next one or two represent something? Otherwise, is the number part for the PO accession number determined by the date that the term was curated?


EnumerateRefsOfObject dose not return all fields

Hi,
I am reading the documentations.

Why do we need EnumerateRefsOfObject?
You might be wondering why we need EnumerateRefsOfObject at all. As you will see in the next tutorial, you can walk each field in the object and get its value. You could implement this algorithm by walking fields instead. However, EnumerateRefsOfObject is much, much faster. It uses the same algorithm the GC does to get object references out of the object, which is far more efficient than walking fields to look for objects.

I tried to run EnumerateRefsOfObject on one of the System.StackOverflowException and did not receive any fields values, but when I looked with dot memory I saw additional fields

I succeeded to get the same value by calling get value with the field name ... am I doing something wrong?

Thanks Eran

EnumerateRefsOfObject only returns object reference fields, not all fields.  The reason for using it is to be 100% sure you find all object references in an object, using the same code the GC does.
This is for building the object graph.  You should use ClrType.Fields instead here.

Thanks a lot for your help 👍


Release 2.3.0

This is a draft of changelog for the 2.3.0 release.
Here you can find all related translations changes: 2.2.0...master.

⚠ Do not merge this pull request manually ⚠
You should approve this pull request instead. After approving, I will automatically update it (release date needs to be adjusted), merge, and tag a new release. You can read more about the process on forum.

Show release notes preview
2.3.0

General changes:

Updated validation translations.

Added support for new extensions:

blomstra/sort-order-toggle
datlechin/flarum-copy-links
datlechin/flarum-discussion-overview

Updated translations for extensions:

blomstra/search
flarum/suspend
zerosonesfun/expired-posts

All changes: 2.2.0...2.3.0.

Success! Now you can announce new release on forum:
## Version [`2.3.0`](https://github.com/flarum-lang/hebrew/releases/tag/2.3.0)

**General changes**:

* Updated validation translations.

**Added support for new extensions**:

* [`blomstra/sort-order-toggle`](https://github.com/blomstra/flarum-ext-sort-order-toggle)
* [`datlechin/flarum-copy-links`](https://github.com/datlechin/flarum-copy-links)
* [`datlechin/flarum-discussion-overview`](https://github.com/datlechin/flarum-discussion-overview)

**Updated translations for extensions**:

* [`blomstra/search`](https://github.com/blomstra/flarum-ext-search)
* [`flarum/suspend`](https://github.com/flarum/suspend)
* [`zerosonesfun/expired-posts`](https://github.com/zerosonesfun/expired-posts)

All changes: [2.2.0...2.3.0](https://github.com/flarum-lang/hebrew/compare/2.2.0...2.3.0).

In order to update run these commands:

```console
composer update flarum-lang/hebrew
php flarum cache:clear
```


Reddit integration : Add date to the footer

Date should be displayed like on reddit, "Submitted X hours/days ago by u/username"
Also if you could rework the post data in the footer a bit :+1:

I'll take a look at this!

I think the postData has a timestamp variable to help you with that

I will reformat the footer a bit. Maybe a different font would look better?

I think we should keep embeds coherent if you want to change the font use the one used in the twitter embed.
When I was talking about the footer it was more about moving the post score and comments inline or something like that. Finding a good placement for each information

Font looked good enough, so I didn't change. But maybe do an extension-wide font change in the future? Neat extension by the way!

We will discuss font change once we have a defined style, I'm closing this with #28


Fix intermittent sql database project test failure

Added a few missing awaits that were causing the "Should update sqlcmd variable values if value changes" test to fail intermittently

Pull Request Test Coverage Report for Build 334248356

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.001%) to 39.64%

Totals

Change from base Build 333993046:
0.001%

Covered Lines:
20570

Relevant Lines:
47670

💛  - Coveralls


Version 1.16 "Release Notes" has bad GitHub query

VSCode Version: Code - Insiders 1.16.0-insider (b73b7df1290d0fe66ca8b8060743711a327af622, 2017-08-14T05:16:07.578Z)
OS Version: Windows_NT x64 10.0.15063

Steps to Reproduce:

Install new Insiders build.
Look at "Release Notes: 1.16.0-insider".
Click "Closed bugs" or "Closed feature requests".

Expected: GitHub is launched with results.
Actual: GitHub is launched with "No results matched your search." because the milestone query isn't in quotes. Repros in Chrome and Edge.

works for me here: https://github.com/Microsoft/vscode-docs/blob/vnext/release-notes/v1_16.md

Okay, now I can reproduce. But when using the documentation links, it's working fine. Looks like vscode is stripping something...

I confirmed this issue on Windows using Firefox and Chrome. Edge seems to work and I also haven't been able to repo this on mac

This may be an electron issue: https://github.com/electron/electron/issues/10285
@gregvanl Let's see if we can work around this by changing the url's encoding in the release notes

This issue was moved to Microsoft/vscode-docs#1136

I think I can fix this by using the milestone number in the query.


Enable IPv6 for submission and verification server

Current Implementation
In production, only the distribution CDN is reachable via IPv6.
Both, submission and verification server do not have AAAA records announced in DNS and are therefor IPv4 only.
Suggested Enhancement
Make all endpoints reachable via IPv6 and add corresponding DNS records.
Expected Benefits
This change avoids NAT and makes the services reachable from IPv6-only networks too, in order to reach as many people as possible,

Thanks for the suggestion. It has been transferred to our Infrastructure team.


Amplify v2 increases Auth.signin() time by 3x

Describe the bug
We have recently migrated to using AWS Amplify SDK for iOS v2.11 and have observed that ~3/10 sign-in operation take significant time to complete (5-10 sec). This was not happening when we were using AWS Amplify SDK v.1.27. The slow response time is related to following API call: https://docs.amplify.aws/lib/auth/signin/q/platform/ios/#sign-in-a-user.
It sometimes “hangs” for 5-10 seconds before completing. We have tried looking into network calls via Proxyman app but we’ve found that the Cognito call are not visible there when using Amplify SDK v2 (eg. As opposed to v1 or other call like AppSync). We have not been able to reproduce the issue when using AWS CLI commands (cognito-idp) - it takes ~1-2 sec to get response.
We have seen similar reports for Amplify framework on other platforms as well, eg: https://github.com/aws-amplify/amplify-js/issues/5539
I am attaching log files and amplifyconfiguration.json files for the few tests I did. Please also see my observations below:
I compared sign-in times when using Amplify SDK v2.11.5 and v1.29.0 in our app and results are as follow:

When using v1 SDK signin call takes ~1-2 sec. (we use exactly the same api calls as in the documentation: https://docs.amplify.aws/lib-v1/auth/signin/q/platform/ios/#sign-in-a-user)

When using v2 SDK the same signin calls take 5-6 sec, sometimes even more. (same as above, we use the same api calls as in the documentation: https://docs.amplify.aws/lib/auth/signin/q/platform/ios/#sign-in-a-user)

What is more, for a application configuration where we use Amplify SDK v1 there is additional Lambda function configured as a PostSignin trigger in Cognito UserPool. Even with this Lambda signin operation only takes ~1-2s when using v1 SDK as compared to 5-6s when using Amplify SDK v2 with no Lambda.
Steps To Reproduce
Can not reproduce on a clean (new) app created with Amplify v2

Expected behavior
Signin time latency should not increase when migrating an app from Amplify v1 to v2
Amplify Framework Version
2.11.5
Amplify Categories
Auth
Dependency manager
Swift PM
Swift version
5.7
CLI version
12.0.0
Xcode version
14.3.1
Relevant log output

Amplify v1 (OK) logs
2023-06-06 11:29:57:519 Evie Beta[987:263140] Request headers:
{
    "Content-Type" = "application/x-amz-json-1.1";
    Host = "cognito-idp.us-west-2.amazonaws.com";
    "User-Agent" = "amplify-iOS/1.29.0 iOS/16.3 en_PL";
    "X-Amz-Date" = 20230606T092957Z;
    "X-Amz-Target" = "AWSCognitoIdentityProviderService.InitiateAuth";
}
2023-06-06 11:29:57:519 Evie Beta[987:263140] Request body:
{"UserContextData":{"EncodedData":"<redacted>"},"ClientMetadata":{"cognito:deviceName":"iPhone","cognito:bundleShortV":"1.0","cognito:idForVendor":"26815F54-49A2-46E6-8BFE-331D269DE9AE","cognito:bundleVersion":"1","cognito:bundleId":"com.movano.ios.debug","cognito:model":"iPhone","cognito:systemName":"iOS","cognito:iOSVersion":"16.3"},"AuthParameters":{"SRP_A":"<redacted>","SECRET_HASH":"<redacted>","USERNAME":"<redacted>"},"AuthFlow":"USER_SRP_AUTH","ClientId":"<redacted>"}
2023-06-06 11:29:57:860 Evie Beta[987:262638] Response headers:
{
    "Content-Length" = 2731;
    "Content-Type" = "application/x-amz-json-1.1";
    Date = "Tue, 06 Jun 2023 09:29:57 GMT";
    "x-amzn-requestid" = "a6e65c8f-5acd-4038-b044-631fad7b1069";
}
2023-06-06 11:29:57:860 Evie Beta[987:262638] Response body:
{"ChallengeName":"PASSWORD_VERIFIER","ChallengeParameters":{"SALT":"<redacted>"}}
2023-06-06 11:29:57:918 Evie Beta[987:262638] Request headers:
{
    "Content-Type" = "application/x-amz-json-1.1";
    Host = "cognito-idp.us-west-2.amazonaws.com";
    "User-Agent" = "amplify-iOS/1.29.0 iOS/16.3 en_PL";
    "X-Amz-Date" = 20230606T092957Z;
    "X-Amz-Target" = "AWSCognitoIdentityProviderService.RespondToAuthChallenge";
}
2023-06-06 11:29:57:918 Evie Beta[987:262638] Request body:
{"UserContextData":{"EncodedData":"<redacted>"},"ChallengeResponses":{"PASSWORD_CLAIM_SECRET_BLOCK":"<redacted>","USERNAME":"<redacted>","SECRET_HASH":"<redacted>","PASSWORD_CLAIM_SIGNATURE":"<redacted>","TIMESTAMP":"Tue Jun 6 09:29:57 UTC 2023"},"ClientMetadata":{},"ChallengeName":"PASSWORD_VERIFIER","ClientId":"<redacted>"}
2023-06-06 11:29:58:375 Evie Beta[987:263140] Response headers:
{
    "Content-Length" = 4218;
    "Content-Type" = "application/x-amz-json-1.1";
    Date = "Tue, 06 Jun 2023 09:29:58 GMT";
    "x-amzn-requestid" = "f20f2450-4b3f-43e7-a41e-b45cef199c81";
}
2023-06-06 11:29:58:375 Evie Beta[987:263140] Response body:
{"AuthenticationResult":{"AccessToken":"<redacted>","ExpiresIn":3600,"IdToken":"<redacted>","RefreshToken":"<redacted>","TokenType":"Bearer"},"ChallengeParameters":{}}
2023-06-06 11:29:58.425859+0200 Evie Beta[987:263140] [Amplify] AWSMobileClient Event listener - signedIn
2023-06-06 11:29:58.426795+0200 Evie Beta[987:263010] [fzy] - signing duration: 0.9446649551391602

Amplify v2 (NOT OK) logs
2023-06-06 10:30:17.999068+0200 Evie Beta[931:244237] [AWSCognitoAuthPlugin] No existing device metadata found. AuthEnvironment(configuration: AWSCognitoAuthPlugin.AuthConfiguration.userPoolsAndIdentityPools(["region": "<REDACTED>", "clientId": "6kjq****6ig8", "poolId": "us-w****Fn3g", "clientSecret": "(nil)", "pinpointAppId": "(nil)", "hostedUI": "[\"oauth\": \"[\\\"signOutRedirectURI\\\": \\\"mova****p://\\\", \\\"signInRedirectURI\\\": \\\"mova****p://\\\", \\\"domain\\\": \\\"auth****loud\\\"]\", \"clientId\": \"6kjq****6ig8\", \"clientSecret\": \"(nil)\"]", "endpoint": "N/A"], ["region": "<REDACTED>", "poolId": "us-w****d529"]), userPoolConfigData: Optional(["region": "<REDACTED>", "clientId": "6kjq****6ig8", "poolId": "us-w****Fn3g", "clientSecret": "(nil)", "pinpointAppId": "(nil)", "hostedUI": "[\"oauth\": \"[\\\"signOutRedirectURI\\\": \\\"mova****p://\\\", \\\"signInRedirectURI\\\": \\\"mova****p://\\\", \\\"domain\\\": \\\"auth****loud\\\"]\", \"clientId\": \"6kjq****6ig8\", \"clientSecret\": \"(nil)\"]", "endpoint": "N/A"]), identityPoolConfigData: Optional(["region": "<REDACTED>", "poolId": "us-w****d529"]), authenticationEnvironment: Optional(AWSCognitoAuthPlugin.BasicAuthenticationEnvironment(srpSignInEnvironment: AWSCognitoAuthPlugin.BasicSRPSignInEnvironment(srpAuthEnvironment: AWSCognitoAuthPlugin.BasicSRPAuthEnvironment(userPoolConfiguration: ["region": "<REDACTED>", "clientId": "6kjq****6ig8", "poolId": "us-w****Fn3g", "clientSecret": "(nil)", "pinpointAppId": "(nil)", "hostedUI": "[\"clientSecret\": \"(nil)\", \"oauth\": \"[\\\"signInRedirectURI\\\": \\\"mova****p://\\\", \\\"signOutRedirectURI\\\": \\\"mova****p://\\\", \\\"domain\\\": \\\"auth****loud\\\"]\", \"clientId\": \"6kjq****6ig8\"]", "endpoint": "N/A"], cognitoUserPoolFactory: (Function), eventIDFactory: (Function), srpClientFactory: (Function), srpConfiguration: (nHexValue: "FFFFFFFFFFFFFFFFC90FDAA22168C234C4C6628B80DC1CD129024E088A67CC74020BBEA63B139B22514A08798E3404DDEF9519B3CD3A431B302B0A6DF25F14374FE1356D6D51C245E485B576625E7EC6F44C42E9A637ED6B0BFF5CB6F406B7EDEE386BFB5A899FA5AE9F24117C4B1FE649286651ECE45B3DC2007CB8A163BF0598DA48361C55D39A69163FA8FD24CF5F83655D23DCA3AD961C62F356208552BB9ED529077096966D670C354E4ABC9804F1746C08CA18217C32905E462E36CE3BE39E772C180E86039B2783A2EC07A28FB5C55DF06F4C52C9DE2BCBF6955817183995497CEA956AE515D2261898FA051015728E5A8AAAC42DAD33170D04507A33A85521ABDF1CBA64ECFB850458DBEF0A8AEA71575D060C7DB3970F85A6E1E4C7ABF5AE8CDB0933D71E8C94E04A25619DCEE3D2261AD2EE6BF12FFA06D98A0864D87602733EC86A64521F2B18177B200CBBE117577A615D6C770988C0BAD946E208E24FA074E5AB3143DB5BFCE0FD108E4B82D120A93AD2CAFFFFFFFFFFFFFFFF", gHexValue: "2"))), userPoolEnvironment: AWSCognitoAuthPlugin.BasicUserPoolEnvironment(userPoolConfiguration: ["region": "<REDACTED>", "clientId": "6kjq****6ig8", "poolId": "us-w****Fn3g", "clientSecret": "(nil)", "pinpointAppId": "(nil)", "hostedUI": "[\"oauth\": \"[\\\"signOutRedirectURI\\\": \\\"mova****p://\\\", \\\"signInRedirectURI\\\": \\\"mova****p://\\\", \\\"domain\\\": \\\"auth****loud\\\"]\", \"clientId\": \"6kjq****6ig8\", \"clientSecret\": \"(nil)\"]", "endpoint": "N/A"], cognitoUserPoolFactory: (Function), cognitoUserPoolASFFactory: (Function), cognitoUserPoolAnalyticsHandlerFactory: (Function)), hostedUIEnvironment: Optional(AWSCognitoAuthPlugin.BasicHostedUIEnvironment(configuration: ["oauth": "[\"signOutRedirectURI\": \"mova****p://\", \"signInRedirectURI\": \"mova****p://\", \"domain\": \"auth****loud\"]", "clientId": "6kjq****6ig8", "clientSecret": "(nil)"], hostedUISessionFactory: (Function), urlSessionFactory: (Function), randomStringFactory: (Function))))), authorizationEnvironment: Optional(AWSCognitoAuthPlugin.BasicAuthorizationEnvironment(identityPoolConfiguration: ["region": "<REDACTED>", "poolId": "us-w****d529"], cognitoIdentityFactory: (Function), eventIDFactory: (Function))), credentialsClient: AWSCognitoAuthPlugin.CredentialStoreOperationClient, logger: DataStoreInfra.LoggingSpyPlugin.(unknown context at $10591ab10).LoggerDecorator)
2023-06-06T10:30:18+0200 info CognitoIdentityProviderClient : [Logging] Request: POST https:443
 Path: /
 Content-Length: 6639,
X-Amz-Target: AWSCognitoIdentityProviderService.InitiateAuth,
Content-Type: application/x-amz-json-1.1,
Host: cognito-idp.us-west-2.amazonaws.com,
x-amz-user-agent: aws-sdk-swift/1.0,
User-Agent: aws-sdk-swift/1.0 api/cognito-identity-provider/1.0 os/iOS/16.3.0 lang/swift/5.7 lib/amplify-swift/2.11.5
 Optional([])
2023-06-06T10:30:18+0200 info SerialExecutor : [Logging] Creating connection pool for Optional("https://cognito-idp.us-west-2.amazonaws.com/?")with max connections: 50
[Instabug] - IBGUser Steps: Captured screenshot using currentImageContext = <UIImage:0x281c00c60 anonymous {375, 667} renderingMode=automatic(original)>
2023-06-06T10:30:19+0200 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-idp.us-west-2.amazonaws.com/?")
2023-06-06 10:30:19.859827+0200 Evie Beta[931:244237] [AWSCognitoAuthPlugin] No existing device metadata found. AuthEnvironment(configuration: AWSCognitoAuthPlugin.AuthConfiguration.userPoolsAndIdentityPools(["region": "<REDACTED>", "clientId": "6kjq****6ig8", "poolId": "us-w****Fn3g", "clientSecret": "(nil)", "pinpointAppId": "(nil)", "hostedUI": "[\"clientSecret\": \"(nil)\", \"oauth\": \"[\\\"signOutRedirectURI\\\": \\\"mova****p://\\\", \\\"signInRedirectURI\\\": \\\"mova****p://\\\", \\\"domain\\\": \\\"auth****loud\\\"]\", \"clientId\": \"6kjq****6ig8\"]", "endpoint": "N/A"], ["region": "<REDACTED>", "poolId": "us-w****d529"]), userPoolConfigData: Optional(["region": "<REDACTED>", "clientId": "6kjq****6ig8", "poolId": "us-w****Fn3g", "clientSecret": "(nil)", "pinpointAppId": "(nil)", "hostedUI": "[\"clientSecret\": \"(nil)\", \"clientId\": \"6kjq****6ig8\", \"oauth\": \"[\\\"domain\\\": \\\"auth****loud\\\", \\\"signOutRedirectURI\\\": \\\"mova****p://\\\", \\\"signInRedirectURI\\\": \\\"mova****p://\\\"]\"]", "endpoint": "N/A"]), identityPoolConfigData: Optional(["region": "<REDACTED>", "poolId": "us-w****d529"]), authenticationEnvironment: Optional(AWSCognitoAuthPlugin.BasicAuthenticationEnvironment(srpSignInEnvironment: AWSCognitoAuthPlugin.BasicSRPSignInEnvironment(srpAuthEnvironment: AWSCognitoAuthPlugin.BasicSRPAuthEnvironment(userPoolConfiguration: ["region": "<REDACTED>", "clientId": "6kjq****6ig8", "poolId": "us-w****Fn3g", "clientSecret": "(nil)", "pinpointAppId": "(nil)", "hostedUI": "[\"clientSecret\": \"(nil)\", \"oauth\": \"[\\\"signOutRedirectURI\\\": \\\"mova****p://\\\", \\\"signInRedirectURI\\\": \\\"mova****p://\\\", \\\"domain\\\": \\\"auth****loud\\\"]\", \"clientId\": \"6kjq****6ig8\"]", "endpoint": "N/A"], cognitoUserPoolFactory: (Function), eventIDFactory: (Function), srpClientFactory: (Function), srpConfiguration: (nHexValue: "FFFFFFFFFFFFFFFFC90FDAA22168C234C4C6628B80DC1CD129024E088A67CC74020BBEA63B139B22514A08798E3404DDEF9519B3CD3A431B302B0A6DF25F14374FE1356D6D51C245E485B576625E7EC6F44C42E9A637ED6B0BFF5CB6F406B7EDEE386BFB5A899FA5AE9F24117C4B1FE649286651ECE45B3DC2007CB8A163BF0598DA48361C55D39A69163FA8FD24CF5F83655D23DCA3AD961C62F356208552BB9ED529077096966D670C354E4ABC9804F1746C08CA18217C32905E462E36CE3BE39E772C180E86039B2783A2EC07A28FB5C55DF06F4C52C9DE2BCBF6955817183995497CEA956AE515D2261898FA051015728E5A8AAAC42DAD33170D04507A33A85521ABDF1CBA64ECFB850458DBEF0A8AEA71575D060C7DB3970F85A6E1E4C7ABF5AE8CDB0933D71E8C94E04A25619DCEE3D2261AD2EE6BF12FFA06D98A0864D87602733EC86A64521F2B18177B200CBBE117577A615D6C770988C0BAD946E208E24FA074E5AB3143DB5BFCE0FD108E4B82D120A93AD2CAFFFFFFFFFFFFFFFF", gHexValue: "2"))), userPoolEnvironment: AWSCognitoAuthPlugin.BasicUserPoolEnvironment(userPoolConfiguration: ["region": "<REDACTED>", "clientId": "6kjq****6ig8", "poolId": "us-w****Fn3g", "clientSecret": "(nil)", "pinpointAppId": "(nil)", "hostedUI": "[\"clientSecret\": \"(nil)\", \"oauth\": \"[\\\"signOutRedirectURI\\\": \\\"mova****p://\\\", \\\"signInRedirectURI\\\": \\\"mova****p://\\\", \\\"domain\\\": \\\"auth****loud\\\"]\", \"clientId\": \"6kjq****6ig8\"]", "endpoint": "N/A"], cognitoUserPoolFactory: (Function), cognitoUserPoolASFFactory: (Function), cognitoUserPoolAnalyticsHandlerFactory: (Function)), hostedUIEnvironment: Optional(AWSCognitoAuthPlugin.BasicHostedUIEnvironment(configuration: ["clientId": "6kjq****6ig8", "clientSecret": "(nil)", "oauth": "[\"domain\": \"auth****loud\", \"signInRedirectURI\": \"mova****p://\", \"signOutRedirectURI\": \"mova****p://\"]"], hostedUISessionFactory: (Function), urlSessionFactory: (Function), randomStringFactory: (Function))))), authorizationEnvironment: Optional(AWSCognitoAuthPlugin.BasicAuthorizationEnvironment(identityPoolConfiguration: ["region": "<REDACTED>", "poolId": "us-w****d529"], cognitoIdentityFactory: (Function), eventIDFactory: (Function))), credentialsClient: AWSCognitoAuthPlugin.CredentialStoreOperationClient, logger: DataStoreInfra.LoggingSpyPlugin.(unknown context at $10591ab10).LoggerDecorator)
2023-06-06T10:30:19+0200 info CognitoIdentityProviderClient : [Logging] Request: POST https:443
 Path: /
 Host: cognito-idp.us-west-2.amazonaws.com,
User-Agent: aws-sdk-swift/1.0 api/cognito-identity-provider/1.0 os/iOS/16.3.0 lang/swift/5.7 lib/amplify-swift/2.11.5,
Content-Length: 7800,
Content-Type: application/x-amz-json-1.1,
X-Amz-Target: AWSCognitoIdentityProviderService.RespondToAuthChallenge,
x-amz-user-agent: aws-sdk-swift/1.0
 Optional([])
2023-06-06T10:30:19+0200 info SerialExecutor : [Logging] Creating connection pool for Optional("https://cognito-idp.us-west-2.amazonaws.com/?")with max connections: 50
2023-06-06T10:30:21+0200 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-idp.us-west-2.amazonaws.com/?")
[Instabug] - IBGUser Steps: Captured screenshot using currentImageContext = <UIImage:0x281c00c60 anonymous {375, 667} renderingMode=automatic(original)>
2023-06-06T10:30:21+0200 info CognitoIdentityClient : [Logging] Request: POST https:443
 Path: /
 x-amz-user-agent: aws-sdk-swift/1.0,
X-Amz-Target: AWSCognitoIdentityService.GetId,
Content-Length: 1357,
Content-Type: application/x-amz-json-1.1,
User-Agent: aws-sdk-swift/1.0 api/cognito-identity/1.0 os/iOS/16.3.0 lang/swift/5.7 lib/amplify-swift/2.11.5,
Host: cognito-identity.us-west-2.amazonaws.com
 Optional([])
2023-06-06T10:30:21+0200 info SerialExecutor : [Logging] Creating connection pool for Optional("https://cognito-identity.us-west-2.amazonaws.com/?")with max connections: 50
2023-06-06T10:30:23+0200 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-identity.us-west-2.amazonaws.com/?")
2023-06-06T10:30:23+0200 info CognitoIdentityClient : [Logging] Request: POST https:443
 Path: /
 x-amz-user-agent: aws-sdk-swift/1.0,
Content-Length: 1353,
Content-Type: application/x-amz-json-1.1,
X-Amz-Target: AWSCognitoIdentityService.GetCredentialsForIdentity,
User-Agent: aws-sdk-swift/1.0 api/cognito-identity/1.0 os/iOS/16.3.0 lang/swift/5.7 lib/amplify-swift/2.11.5,
Host: cognito-identity.us-west-2.amazonaws.com
 Optional([])
2023-06-06T10:30:23+0200 info SerialExecutor : [Logging] Creating connection pool for Optional("https://cognito-identity.us-west-2.amazonaws.com/?")with max connections: 50
[Instabug] - IBGUser Steps: Captured screenshot using currentImageContext = <UIImage:0x281c00cf0 anonymous {375, 667} renderingMode=automatic(original)>
2023-06-06T10:30:23+0200 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-identity.us-west-2.amazonaws.com/?")
2023-06-06 10:30:24.192135+0200 Evie Beta[931:244258] User is signed in!
2023-06-06 10:30:24.193132+0200 Evie Beta[931:244269] [fzy] - signing duration: 6.229087542 seconds

Is this a regression?
Yes
Regression additional context
No response
Device
all
iOS Version
multiple
Specific to simulators
no
Additional context
No response

Amplify v1 configuration
{
    "UserAgent": "aws-amplify-cli/2.0",
    "Version": "1.0",
    "auth": {
        "plugins": {
            "awsCognitoAuthPlugin": {
                "IdentityManager": {
                    "Default": {}
                },
                "CognitoUserPool": {
                    "Default": {
                        "PoolId": "us-west-2_aEXGnKFRT",
                        "AppClientId": "65hdf3qt7ptbl55udk3mp6ilv5",
                        "AppClientSecret": "<redacted>",
                        "Region": "us-west-2"
                    }
                },
                "Auth": {
                    "Default": {
                        "authenticationFlowType": "USER_SRP_AUTH",
                        "OAuth": {
                            "WebDomain": "intent-auth.movano.cloud",
                            "AppClientId": "65hdf3qt7ptbl55udk3mp6ilv5",
                            "AppClientSecret": "<redacted>",
                            "SignInRedirectURI": "movanoapp://",
                            "SignOutRedirectURI": "movanoapp://",
                            "Scopes": [
                                "phone",
                                "email",
                                "openid",
                                "profile",
                                "aws.cognito.signin.user.admin"
                            ]
                        }
                    }
                },
                "AppSync": {
                    "Default": {
                        "ApiUrl": "https://3y7oxixoendsraee4flafesuha.appsync-api.us-west-2.amazonaws.com/graphql",
                        "Region": "us-west-2",
                        "AuthMode": "AMAZON_COGNITO_USER_POOLS",
                        "ClientDatabasePrefix": "INTENT-DEV_AMAZON_COGNITO_USER_POOLS"
                    }
                }
            }
        }
    },
    "api": {
        "plugins": {
            "awsAPIPlugin": {
                "INTENT-DEV": {
                    "endpointType": "GraphQL",
                    "endpoint": "https://3y7oxixoendsraee4flafesuha.appsync-api.us-west-2.amazonaws.com/graphql",
                    "region": "us-west-2",
                    "authorizationType": "AMAZON_COGNITO_USER_POOLS"
                },
                "REST_API": {
                    "endpointType": "REST",
                    "endpoint": "https://ejykq2mu74.execute-api.us-west-2.amazonaws.com/INTENT-DEV",
                    "region": "us-west-2",
                    "authorizationType": "AMAZON_COGNITO_USER_POOLS"
                }
            }
        }
    }
}

Amplify v2 configuration
{
    "UserAgent": "aws-amplify-cli/2.0",
    "Version": "1.0",
    "api": {
        "plugins": {
            "awsAPIPlugin": {
                "RingAppApi": {
                    "endpointType": "REST",
                    "endpoint": "https://90hsa9ir13.execute-api.us-west-2.amazonaws.com/intentd",
                    "region": "us-west-2",
                    "authorizationType": "AMAZON_COGNITO_USER_POOLS"
                },
                "ringapp": {
                    "endpointType": "GraphQL",
                    "endpoint": "https://76gowagcazevheefrg4cwxdcom.appsync-api.us-west-2.amazonaws.com/graphql",
                    "region": "us-west-2",
                    "authorizationType": "AMAZON_COGNITO_USER_POOLS",
                    "apiKey": "da2-vj7owdzna5bahmjjkw72h53ylm"
                }
            }
        }
    },
    "auth": {
        "plugins": {
            "awsCognitoAuthPlugin": {
                "UserAgent": "aws-amplify/cli",
                "Version": "0.1.0",
                "IdentityManager": {
                    "Default": {}
                },
                "AppSync": {
                    "Default": {
                        "ApiUrl": "https://76gowagcazevheefrg4cwxdcom.appsync-api.us-west-2.amazonaws.com/graphql",
                        "Region": "us-west-2",
                        "AuthMode": "AMAZON_COGNITO_USER_POOLS",
                        "ClientDatabasePrefix": "ringapp_AMAZON_COGNITO_USER_POOLS"
                    },
                    "ringapp_API_KEY": {
                        "ApiUrl": "https://76gowagcazevheefrg4cwxdcom.appsync-api.us-west-2.amazonaws.com/graphql",
                        "Region": "us-west-2",
                        "AuthMode": "API_KEY",
                        "ApiKey": "da2-vj7owdzna5bahmjjkw72h53ylm",
                        "ClientDatabasePrefix": "ringapp_API_KEY"
                    }
                },
                "CredentialsProvider": {
                    "CognitoIdentity": {
                        "Default": {
                            "PoolId": "us-west-2:362c3f3b-e385-4874-b490-5c207dd1d529",
                            "Region": "us-west-2"
                        }
                    }
                },
                "CognitoUserPool": {
                    "Default": {
                        "PoolId": "us-west-2_o0zEgFn3g",
                        "AppClientId": "6kjqvc7svub6cq9k0altiv6ig8",
                        "Region": "us-west-2"
                    }
                },
                "Auth": {
                    "Default": {
                        "OAuth": {
                            "WebDomain": "auth2.intent.movano.cloud",
                            "AppClientId": "6kjqvc7svub6cq9k0altiv6ig8",
                            "SignInRedirectURI": "movanoapp://",
                            "SignOutRedirectURI": "movanoapp://",
                            "Scopes": [
                                "phone",
                                "email",
                                "openid",
                                "profile",
                                "aws.cognito.signin.user.admin"
                            ]
                        },
                        "authenticationFlowType": "USER_SRP_AUTH",
                        "mfaConfiguration": "OFF",
                        "mfaTypes": [
                            "SMS"
                        ],
                        "passwordProtectionSettings": {
                            "passwordPolicyMinLength": 8,
                            "passwordPolicyCharacters": []
                        },
                        "signupAttributes": [
                            "EMAIL"
                        ],
                        "socialProviders": [
                            "GOOGLE",
                            "APPLE"
                        ],
                        "usernameAttributes": [
                            "EMAIL"
                        ],
                        "verificationMechanisms": [
                            "EMAIL"
                        ]
                    }
                },
                "DynamoDBObjectMapper": {
                    "Default": {
                        "Region": "us-west-2"
                    }
                },
                "S3TransferUtility": {
                    "Default": {
                        "Bucket": "apps3storage83114-intentd",
                        "Region": "us-west-2"
                    }
                }
            }
        }
    },
    "storage": {
        "plugins": {
            "awsDynamoDbStoragePlugin": {
                "partitionKeyName": "user_id",
                "sortKeyName": "job_id",
                "sortKeyType": "S",
                "region": "us-west-2",
                "arn": "arn:aws:dynamodb:us-west-2:676488953296:table/SleepServiceV2-intentd",
                "streamArn": "arn:aws:dynamodb:us-west-2:676488953296:table/SleepServiceV2-intentd/stream/2023-04-15T00:39:39.073",
                "partitionKeyType": "S",
                "name": "SleepServiceV2-intentd"
            },
            "awsS3StoragePlugin": {
                "bucket": "apps3storage83114-intentd",
                "region": "us-west-2",
                "defaultAccessLevel": "guest"
            }
        }
    }
}

@sebsto @harsh62 I've been trying to reproduce this issue in the AWS SDK for Swift but can't reproduce the type of delays you are reporting.
I note that it says above that you tried to reproduce in a clean / new project but couldn't.
Do you have a code sample or some other way to attempt to recreate the issue?

@jbelkins The code we use in the project is exactly the same as in the official documentation here: https://docs.amplify.aws/lib/auth/signin/q/platform/ios/#sign-in-a-user
I am not sure about the clean project as we only tried on different Amplify SDK versions - I will try to set up new amplify project and replicate it there.

@jbelkins I have created a sample project to demonstrate the issue. You can find it here:
https://github.com/fzy-spyro/AmplifySlowSignin
on "main" branch I am using amplify 2x where signin usually takes > 3 seconds. Logs from the execution are eg:
⏰ signIn() clicked!
2023-07-28T13:58:42+0200 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-idp.us-west-2.amazonaws.com/?")
2023-07-28T13:58:42+0200 info CognitoIdentityClient : [Logging] Request: POST https:443
 Path: /
 Content-Length: 1225,
Content-Type: application/x-amz-json-1.1,
x-amz-user-agent: aws-sdk-swift/1.0,
Host: cognito-identity.us-west-2.amazonaws.com,
User-Agent: aws-sdk-swift/1.0 api/cognito-identity/1.0 os/iOS/16.4.0 lang/swift/5.8 lib/amplify-swift/2.12.0,
X-Amz-Target: AWSCognitoIdentityService.GetId
 Optional([])
2023-07-28T13:58:42+0200 info SerialExecutor : [Logging] Creating connection pool for Optional("https://cognito-identity.us-west-2.amazonaws.com/?")with max connections: 50
2023-07-28T13:58:43+0200 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-identity.us-west-2.amazonaws.com/?")
2023-07-28T13:58:43+0200 info CognitoIdentityClient : [Logging] Request: POST https:443
 Path: /
 User-Agent: aws-sdk-swift/1.0 api/cognito-identity/1.0 os/iOS/16.4.0 lang/swift/5.8 lib/amplify-swift/2.12.0,
Content-Length: 1221,
Content-Type: application/x-amz-json-1.1,
x-amz-user-agent: aws-sdk-swift/1.0,
X-Amz-Target: AWSCognitoIdentityService.GetCredentialsForIdentity,
Host: cognito-identity.us-west-2.amazonaws.com
 Optional([])
2023-07-28T13:58:43+0200 info SerialExecutor : [Logging] Creating connection pool for Optional("https://cognito-identity.us-west-2.amazonaws.com/?")with max connections: 50
2023-07-28T13:58:44+0200 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-identity.us-west-2.amazonaws.com/?")
Signin result: AuthSignInResult(nextStep: Amplify.AuthSignInStep.done)
⏰ signIn() finished! 5.262481343 seconds

Repository also has a amplify-v1 branch to showcase that it takes significantly shorter to sign in with amplify v1. This can be seen by the same print statements:
⏰ signIn() clicked!
Signin result: success(Amplify.AuthSignInResult(nextStep: Amplify.AuthSignInStep.done))
⏰ signIn() finished! 0.7506569623947144

@jbelkins I have created a sample project to demonstrate the issue. You can find it here:
https://github.com/fzy-spyro/AmplifySlowSignin
on "main" branch I am using amplify 2.15.1 where signin usually takes > 3 seconds. Logs from the execution are eg:
⏰ signIn() clicked!
2023-07-28T13:58:42+0200 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-idp.us-west-2.amazonaws.com/?")
2023-07-28T13:58:42+0200 info CognitoIdentityClient : [Logging] Request: POST https:443
 Path: /
 Content-Length: 1225,
Content-Type: application/x-amz-json-1.1,
x-amz-user-agent: aws-sdk-swift/1.0,
Host: cognito-identity.us-west-2.amazonaws.com,
User-Agent: aws-sdk-swift/1.0 api/cognito-identity/1.0 os/iOS/16.4.0 lang/swift/5.8 lib/amplify-swift/2.12.0,
X-Amz-Target: AWSCognitoIdentityService.GetId
 Optional([])
2023-07-28T13:58:42+0200 info SerialExecutor : [Logging] Creating connection pool for Optional("https://cognito-identity.us-west-2.amazonaws.com/?")with max connections: 50
2023-07-28T13:58:43+0200 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-identity.us-west-2.amazonaws.com/?")
2023-07-28T13:58:43+0200 info CognitoIdentityClient : [Logging] Request: POST https:443
 Path: /
 User-Agent: aws-sdk-swift/1.0 api/cognito-identity/1.0 os/iOS/16.4.0 lang/swift/5.8 lib/amplify-swift/2.12.0,
Content-Length: 1221,
Content-Type: application/x-amz-json-1.1,
x-amz-user-agent: aws-sdk-swift/1.0,
X-Amz-Target: AWSCognitoIdentityService.GetCredentialsForIdentity,
Host: cognito-identity.us-west-2.amazonaws.com
 Optional([])
2023-07-28T13:58:43+0200 info SerialExecutor : [Logging] Creating connection pool for Optional("https://cognito-identity.us-west-2.amazonaws.com/?")with max connections: 50
2023-07-28T13:58:44+0200 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-identity.us-west-2.amazonaws.com/?")
Signin result: AuthSignInResult(nextStep: Amplify.AuthSignInStep.done)
⏰ signIn() finished! 5.262481343

Repository also has a amplify-v1 branch to showcase that it takes significantly shorter to sign in with amplify v1 eg 1.30. This can be seen by the same print statements
⏰ signIn() clicked!
Signin result: success(Amplify.AuthSignInResult(nextStep: Amplify.AuthSignInStep.done))
⏰ signIn() finished! 0.7506569623947144

This might be a little out of context, but is there a way to turn off the logs during the execution of all the  Auth functions? I've even tried to set the LogLevel to .none when configuring Amplify and it still doesn't help

@smbrmoyo
These logs are generated by the AWS SDK, you can reduce the SDK verbosity like this :
        // reduce verbosity of AWS SDK
        SDKLoggingSystem.initialize(logLevel: .warning)

Do not forget to import ClientRuntime
Here is how I do it
https://github.com/sebsto/amplify-memories/blob/main/app/Memories/Backend.swift

It works. Thank you very much!

@jbelkins Is there any news here?

@fzy-spyro Thank you much for the sample project you linked above.  I created an account with it, then repeatedly logged in to test login times.  It was immensely useful for troubleshooting this issue.
The issue appears to be that HTTP connections are not being reused when appropriate.  The login request above requires four HTTP requests to complete, and a new connection is being made for each one.  When connections are properly reused, signin times appear to be comparable to the Amplify v1 branch.
We will prepare a fix for aws-sdk-swift, which will then need to be shipped in amplify-swift.  For visibility, the problem in aws-sdk-swift is tracked in https://github.com/awslabs/aws-sdk-swift/issues/1035.

@jbelkins Thanks for the update. I'm glad that the project helped to pinpoint the issues. Looking forward for the fix :)

@jbelkins
A have a question on how the http-sdk works. While doing investigation of this issue on my end I was using a proxy tool to intercept http traffic to understand if this was a network issue etc. What I've observed that with Amplify v1 SDK I could easily see http calls to cognito in proxy (eg proxyman) but when using Amplify V2 those calls were not there. What was more suprprising was that I wasn't able to intercept cognito calls only, graphql or REST request going through eg. APIPlugin were easily tracable in the proxy.
Does the cognito http-sdk has something to do with it? Does it somehow hide this requests from proxies?

Thanks @lawmicha will do. and regarding the fix for the signin time - I see that the sdk team has released the fix: https://github.com/awslabs/aws-sdk-swift/issues/1035
when can we expect the change to be included in amplify update?

@fzy-spyro amplify 2.22.0 has been released yesterday. It includes SDK 0.31.0 with the fix you mentioned.
https://github.com/aws-amplify/amplify-swift/releases/tag/2.22.0
Please try it out as soon as you can and report back the status here.

@sebsto @lawmicha I am still seeing the same behavior with amplify sdk 2.25.5. signin requests lasts for ~3-4 seconds.
logs:
⏰ signIn() clicked!
2024-01-29T13:44:22+0100 info CognitoIdentityProviderClient : [Logging] Request: POST https:443
 Path: /
 X-Amz-Target: AWSCognitoIdentityProviderService.InitiateAuth,
Content-Type: application/x-amz-json-1.1,
Host: cognito-idp.us-west-2.amazonaws.com,
Content-Length: 6684,
User-Agent: aws-sdk-swift/1.0 ua/2.0 api/cognito_identity_provider#1.0 os/ios#17.0.1 lang/swift#5.9 cfg/retry-mode#legacy
 nil
2024-01-29T13:44:22+0100 info SerialExecutor : [Logging] Creating connection pool for cognito-idp.us-west-2.amazonaws.com with max connections: 50
2024-01-29T13:44:22+0100 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-idp.us-west-2.amazonaws.com/")
2024-01-29T13:44:22+0100 info CRTClientEngine : [Logging] Using HTTP/1.1 connection
2024-01-29T13:44:22+0100 info HttpContent : [Logging] read 6684 bytes from data
2024-01-29T13:44:22+0100 info CRTClientEngine : [Logging] Main headers received
2024-01-29T13:44:22+0100 info CRTClientEngine : [Logging] Body chunk received
2024-01-29T13:44:22+0100 info CRTClientEngine : [Logging] Request/response completed
2024-01-29T13:44:23+0100 info CognitoIdentityProviderClient : [Logging] Request: POST https:443
 Path: /
 Content-Type: application/x-amz-json-1.1,
X-Amz-Target: AWSCognitoIdentityProviderService.RespondToAuthChallenge,
Content-Length: 7858,
User-Agent: aws-sdk-swift/1.0 ua/2.0 api/cognito_identity_provider#1.0 os/ios#17.0.1 lang/swift#5.9 cfg/retry-mode#legacy,
Host: cognito-idp.us-west-2.amazonaws.com
 nil
2024-01-29T13:44:23+0100 info SerialExecutor : [Logging] Creating connection pool for cognito-idp.us-west-2.amazonaws.com with max connections: 50
2024-01-29T13:44:23+0100 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-idp.us-west-2.amazonaws.com/")
2024-01-29T13:44:23+0100 info CRTClientEngine : [Logging] Using HTTP/1.1 connection
2024-01-29T13:44:23+0100 info HttpContent : [Logging] read 7858 bytes from data
2024-01-29T13:44:24+0100 info CRTClientEngine : [Logging] Main headers received
2024-01-29T13:44:24+0100 info CRTClientEngine : [Logging] Body chunk received
2024-01-29T13:44:24+0100 info CRTClientEngine : [Logging] Request/response completed
2024-01-29T13:44:24+0100 info CognitoIdentityClient : [Logging] Request: POST https:443
 Path: /
 Host: cognito-identity.us-west-2.amazonaws.com,
X-Amz-Target: AWSCognitoIdentityService.GetId,
User-Agent: aws-sdk-swift/1.0 ua/2.0 api/cognito_identity#1.0 os/ios#17.0.1 lang/swift#5.9 cfg/retry-mode#legacy,
Content-Type: application/x-amz-json-1.1,
Content-Length: 1225
 nil
2024-01-29T13:44:24+0100 info SerialExecutor : [Logging] Creating connection pool for cognito-identity.us-west-2.amazonaws.com with max connections: 50
2024-01-29T13:44:24+0100 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-identity.us-west-2.amazonaws.com/")
2024-01-29T13:44:24+0100 info CRTClientEngine : [Logging] Using HTTP/1.1 connection
2024-01-29T13:44:24+0100 info HttpContent : [Logging] read 1225 bytes from data
2024-01-29T13:44:24+0100 info CRTClientEngine : [Logging] Main headers received
2024-01-29T13:44:24+0100 info CRTClientEngine : [Logging] Body chunk received
2024-01-29T13:44:24+0100 info CRTClientEngine : [Logging] Request/response completed
2024-01-29T13:44:24+0100 info CognitoIdentityClient : [Logging] Request: POST https:443
 Path: /
 Content-Type: application/x-amz-json-1.1,
User-Agent: aws-sdk-swift/1.0 ua/2.0 api/cognito_identity#1.0 os/ios#17.0.1 lang/swift#5.9 cfg/retry-mode#legacy,
X-Amz-Target: AWSCognitoIdentityService.GetCredentialsForIdentity,
Host: cognito-identity.us-west-2.amazonaws.com,
Content-Length: 1221
 nil
2024-01-29T13:44:24+0100 info SerialExecutor : [Logging] Creating connection pool for cognito-identity.us-west-2.amazonaws.com with max connections: 50
2024-01-29T13:44:25+0100 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-identity.us-west-2.amazonaws.com/")
2024-01-29T13:44:25+0100 info CRTClientEngine : [Logging] Using HTTP/1.1 connection
2024-01-29T13:44:25+0100 info HttpContent : [Logging] read 1221 bytes from data
2024-01-29T13:44:25+0100 info CRTClientEngine : [Logging] Main headers received
2024-01-29T13:44:25+0100 info CRTClientEngine : [Logging] Body chunk received
2024-01-29T13:44:25+0100 info CRTClientEngine : [Logging] Request/response completed
Signin result: AuthSignInResult(nextStep: Amplify.AuthSignInStep.done)
⏰ signIn() finished! 3.8088619709014893


Turn entire list item into a link on the dashboard

On the dashboard lists for Blog Posts, Pages, and Text Snippets, only the text is clickable. For easier navigation, the whole item should be a link.
We might also want to consider removing the delete button since we also have it in the edit page and it might improve usability since you'd be able to click anywhere in the list without worrying about hitting delete.
The view code for Snippets and Posts is also very similar. This should be refactored when making these changes to reduce duplication.

Believe this is also on 2.0 roadmap.


Can external-dns be used with a single domain across multiple clusters?

Hello,
Hopefully, this is a basic question.  Can you use a domain across multiple clusters?  Situation:
Cluster k8s.centralus.abc.com exists in AKS central us
Cluster k8s.eastus.abc.com exists in AKS east us
Both use external DNS with domain abc.com.  What I see is that they constantly fight and delete eachothers records. Is there someway to identify separate clusters so they don't kill eachother?

@billabongrob yes, this should work with the TXT registry, you need to give the two External DNS instances different txt-owner-id option values.

See also on how we (Zalando) run External DNS in AWS: we set the txt-owner-id to contain the region and local (cluster) ID: https://github.com/zalando-incubator/kubernetes-on-aws/blob/dev/cluster/manifests/external-dns/deployment.yaml#L32

@billabongrob the variables are specific to our Zalando cluster setup (also the templating you see there). You can use any static string values for your case (e.g. "cluster-1" and "cluster-2").

Awesome, thank you!


swayosd: unstable-2023-09-26 -> unstable-2024-04-15

Description of changes
swayosd: unstable-2023-09-26 -> unstable-2024-04-15
homepage: ErikReider/SwayOSD
Changelog

New brightnessctl backend, set by percentage, and pick device
Added server option to use custom user CSS

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Maybe also patch brightnessctl path? https://github.com/ErikReider/SwayOSD/blob/11271760052c4a4a4057f2d287944d74e8fbdb58/src/brightness_backend/brightnessctl.rs#L63

Maybe also patch brightnessctl path<EMAIL_ADDRESS>
The binary should be available globally from the PATH environment variable, I would think that in any case you have to place that package as a runtime dependency.

The binary should be available globally from the PATH environment variable, I would think that in any case you have to place that package as a runtime dependency.

In this case we would usually override the path in the wrapper, but we have already done enough substitutions, so we can just replace it directly.

@Aleksanaa How about something like this instead of the patch?
https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/misc/avizo/default.nix#L38
https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/misc/nwg-panel/default.nix#L52

Also okay.
preFixup = ''
  gappsWrapperArgs+=(
    --prefix PATH : ${lib.makeBinPath [ brightnessctl ]}
  )
'';

@Aleksanaa Could you please review, I just modified it and did local builds and execution.

Also the commit message has to be reworded


PHP7.4 - Utilize 7.4 and clean ups

Coverage increased (+0.02%) to 93.169% when pulling b719ca8bda97abffe06b3da3bf92cdbc2a0fba59 on SpacePossum:master_74 into ae4246674e99ed21373609ba289c21b555969b09 on FriendsOfPHP:master.


Make prefect linting care about lint levels

i.e., it shouldn't fail on ERROR, WARNING, and INFO. Definitely on ERROR, and maybe on WARNING too.
It may be helpful also to define more clearly what type of lints go in which of these categories.

I think INFO should never result in a failure. WARNING is fine, or we could leave it up to the discretion of the reviewers to determine if that warning is worth blocking the PR.

this makes sense to me: ERROR is a hard fail which doesn't require any other interpretation, and WARNING requires some interpretation to determine how serious it is.
Something like this: https://gcc.gnu.org/onlinedocs/gcc-5.1.0/gcc/Warnings-and-Errors.html

This should help with the implementation: https://github.com/anaconda-distribution/anaconda-linter/pull/120

Tracking: https://anaconda.atlassian.net/browse/PAT-115


[Submission]: Exploring Dynamic Circuits through Gibbs Free Energy Calculations and Error Mitigation

Project name
Exploring Dynamic Circuits through Gibbs Free Energy Calculations and Error Mitigation
Github repo
https://github.com/owaisishtiaqsiddiqui/QRISE
Description
The Project seeks to demonstrate the behavior of Gibbs free energy using dynamic mid-circuit measurements.
We Developed a framework for estimating the free energy of quantum systems using variational quantum algorithms. We Implemented ansatz parameterization techniques to construct parameterized quantum circuits capable of preparing quantum states relevant to the free energy calculation also Designed efficient algorithms for estimating expectation values of Hamiltonians and computing the free energy based on the obtained results and Evaluated the performance of the developed framework through empirical analysis, including benchmarking, optimization,
Email
<EMAIL_ADDRESS>Alternatives
There are no alternatives to this project but there are some tutorials on using Mid circuit measurements using Qiskit.
License
MIT license
Affiliations
No response
Group
other
Labels
Algorithms, Chemistry, Error mitigation, Jupyter notebook, Paper implementation, Physics
Documentation
https://github.com/owaisishtiaqsiddiqui/QRISE/blob/main/QRise_Final_PPT.pdf
Website
No response
Reference paper
https://arxiv.org/pdf/2005.08797.pdf, https://arxiv.org/pdf/2312.14139.pdf

Closing after discussion in with @AbdullahKazi500. We're reducing the scope of the ecosystem to projects that users can install and take advantage of, which excludes demos and research code. We still think this project is valuable and will try to find another home for it. In the meantime, the authors will write a blog post and present about this at a demo day on the 11th of July.


Add node_modules to .npmignore file

Added node_modules to .npmignore

Please provide some description

Why do you have yarn.lock in your PR?

Your commit should be:
ISSUE_NUMBER - ISSUE_TITLE
Example:
https://github.com/chuva-io/sisp_payments_js/issues/17 - Add Portuguese README

Ok i will change the commit message. I didn't provide a description because it would be redundant but i can add one  if you want. As far as the yarn.lock just don't accept the changes.

LGTM 🚀

Fixed the commit message and i also provided a description plus reverted the yarn.lock file changes.

@thypirate thanks for the contribution 🚀


ci: add missing permissions

What this PR changes/adds
Add write permissions to checks an pull-requests on CI
Why it does that
To make Upload-Test-Report job work
Further notes

Linked Issue(s)
Closes #1329
Checklist

[ ] added appropriate tests?
[ ] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[ ] added/updated relevant documentation?
[ ] added relevant details to the changelog? (skip with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

Codecov Report

Merging #1343 (051e5ee) into main (1cf88a5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1343   +/-   ##
=======================================
  Coverage   67.60%   67.60%
=======================================
  Files         716      716
  Lines       15858    15858
  Branches     1041     1041
=======================================
  Hits        10721    10721
  Misses       4663     4663
  Partials      474      474

Continue to review full report at Codecov.

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


How to create patch for merge_patch input ?

Hello,
I need to generate a patch like the one from merge_patch example :
// the patch
json patch = R"({
            "title": "Hello!",
            "phoneNumber": "+01-123-456-7890",
            "author": {
                "familyName": null
            },
            "tags": [
                "example"
            ]
        })"_json;

Is there an existing function to generate this ?
I tried diff function but it create a list of actions to apply, so not what I need.
I search somthing working like this:
// the source document
json source = R"(
    {
        "baz": "qux",
        "foo": "bar"
    }
)"_json;

// the target document
json target = R"(
    {
        "baz": "boo",
        "hello": [
            "world"
        ]
    }
)"_json;

// create the patch
json patch = json::diff(source, target);

Where patch will be
{
    "baz": "boo",
    "foo": null,
    "hello": [
        "world"
    ]
}

Thank you for your help.

I don't believe this is currently supported out of the box. The library supports applying JSON Merge Patches through merge_patch() function, but there is no counterpart "merge_diff" function to generate one. There are some considerations before implementing a general-purpose one (e.g. how to handle null values in source).

@nickaein is right.

Is there a plan to support this case?

There is no real specification for this. Merge requests are welcome!


Kubernetes - Server properties through configmap

I see that the properties are loaded through environment variable that points to properties file on the file system or through an argument (absolute path) to the server (see com.netflix.conductor.server.Main.java). I am in the process of deploying the conductor on kubernetes and have the properties be configured through configMaps. Need some help on how I can do this.

Hi,
If you are storing the entire properties file in a configMap, you could probably refer to Add ConfigMap data to a specific path in the Volume
This would allow you to mount your custom properties file in the server container with a specific path (i.e. path: config-custom.properties) and set then CONFIG_PROP=config-custom.properties as an environment variable in the container spec
However, I have not implemented this yet

Hi,
I did get this working for my deployment, here's the gist of it:

Create a configMap with your properties file:
$ kubectl create configmap conductor-properties --from-file=config/config.properties

Add a volume to your deployment's PodSpec:
volumes:
- name: config-volume
   configMap:
     name: conductor-properties
     items:
     - key: config.properties
       path: config.properties

Mount the volume as part of the container, your properties are mounted to /app/config/config-volume
volumeMounts:
- name: config-volume
  mountPath: /app/config

Set the CONFIG_PROP environment variable for your container
env:
- name: CONFIG_PROP
  value: "config.properties"

I exactly did that and worked. Thank you @c-n-d


Added docs for other HTTP errors

This is needed when a user session expires (or other HTTP errors are thrown) in Laravel. Unpoly will swap the entire <body> of the document when an HTTP error occurs with the Laravel response, which will be a JSON "unauthenticated" message. I've looked at other ways of extending the Illuminate\Http\Request, but this appears to be the only way.
After this change though, Laravel will properly return a redirect response to the login page, which Unpoly will follow and grab the response from, displaying the login form and allowing users to login after their session has expired 👍

@stevebauman thanks for figuring this out and contributing it back as documentation! 🙏


Quarterly Gazetteer Release, 2020-Q1

Type of Feature:
[ ] Collaboration or partnership
[ X ] Improvement or clarification
[ ] New Processing
Description of Feature
Gazetteer update.
Include testing of updates on nationalities.csv

OBE -- Xponents 3.5 refactored gazetteer release. 2021-Q4 is next.


Undefined method authorize

Hello
During development, I often see this error. It goes away when I restart "rails server', but it's pretty annoying. Any suggestions?
thanks.

One might experience this error with any new gem that's added to the Gemfile, you'll need to restart  $ rails serverafter$ bundle install. However, after that the gem should be properly loaded. If this error persist, I'd guess there's some issue with bundler` not properly loading gems on your system.

I am not sure that this issue is truly closed.
I am seeing the same behavior as DmitrlySalko. If I modify a policy within my policies directory, the only way to get rid of the undefined method `authorize' for message is to restart the server. This immediately allows for the server to work.
Environment:
Puma Server
Created with Rails Composer
Gemfile:
Using rake 10.4.2
Using i18n 0.7.0
Using json 1.8.2
Using minitest 5.6.0
Using thread_safe 0.3.5
Using tzinfo 1.2.2
Using activesupport 4.2.1
Using builder 3.2.2
Using erubis 2.7.0
Using mini_portile 0.6.2
Using nokogiri <IP_ADDRESS>
Using rails-deprecated_sanitizer 1.0.3
Using rails-dom-testing 1.0.6
Using loofah 2.0.1
Using rails-html-sanitizer 1.0.2
Using actionview 4.2.1
Using rack 1.6.0
Using rack-test 0.6.3
Using actionpack 4.2.1
Using globalid 0.3.5
Using activejob 4.2.1
Using mime-types 2.4.3
Using mail 2.6.3
Using actionmailer 4.2.1
Using activemodel 4.2.1
Using arel 6.0.0
Using activerecord 4.2.1
Using addressable 2.3.8
Using ast 2.0.0
Using parser <IP_ADDRESS>
Using astrolabe 1.3.0
Using execjs 2.5.2
Using autoprefixer-rails 5.1.9
Using bcrypt 3.1.10
Using coderay 1.1.0
Using better_errors 2.1.1
Using debug_inspector 0.0.2
Using binding_of_caller 0.7.2
Using bootstrap-filestyle-rails 1.1.2
Using sass 3.4.13
Using bootstrap-sass <IP_ADDRESS>
Using columnize 0.9.0
Using byebug 4.0.5
Using xpath 2.0.0
Using capybara 2.4.4
Using ffi 1.9.8
Using childprocess 0.5.6
Using climate_control 0.0.3
Using cocaine 0.5.7
Using cocoon 1.2.6
Using coffee-script-source <IP_ADDRESS>
Using coffee-script 2.4.1
Using thor 0.19.1
Using railties 4.2.1
Using coffee-rails 4.1.0
Using database_cleaner 1.4.1
Using orm_adapter 0.5.0
Using responders 2.1.0
Using warden 1.2.3
Using devise 3.4.1
Using diff-lcs 1.2.5
Using factory_girl 4.5.0
Using factory_girl_rails 4.5.0
Using faker 1.4.3
Using figaro 1.1.0
Using font-awesome-rails <IP_ADDRESS>
Using tilt 1.4.1
Using haml 4.0.6
Using sexp_processor 4.5.0
Using ruby_parser 3.6.6
Using html2haml 2.0.0
Using haml-rails 0.9.0
Using high_voltage 2.2.1
Using interception 0.5
Using multi_json 1.11.0
Using jbuilder 2.2.13
Using jquery-rails 4.0.3
Using sprockets 3.0.0
Using sprockets-rails 2.2.4
Using sass-rails 5.0.3
Using jquery-datatables-rails 3.2.0
Using jquery-ui-rails 5.0.3
Using kaminari 0.16.3
Using launchy 2.4.3
Using method_source 0.8.2
Using paperclip 4.2.1
Using polyamorous 1.2.0
Using powerpack 0.1.0
Using slop 3.6.0
Using pry 0.10.1
Using pry-rails 0.3.4
Using pry-rescue 1.4.1
Using puma 2.11.2
Using pundit 0.3.0
Using quiet_assets 1.1.0
Using bundler 1.6.1
Using rails 4.2.1
Using rails4-autocomplete 1.1.1
Using rails_layout 1.0.25
Using rainbow 2.0.0
Using ransack 1.6.6
Using rspec-support 3.2.2
Using rspec-core 3.2.3
Using rspec-expectations 3.2.1
Using rspec-mocks 3.2.1
Using rspec-rails 3.2.1
Using ruby-progressbar 1.7.5
Using rubocop 0.30.0
Using rubyzip 1.1.7
Using websocket 1.2.1
Using selenium-webdriver 2.45.0
Using simple_form 3.1.0
Using spring 1.3.4
Using spring-commands-rspec 1.0.4
Using sqlite3 1.3.10
Using timeliness 0.3.7
Using turbolinks 2.5.3
Using uglifier 2.7.1
Using upmin-admin 0.1.01
Using validates_timeliness 3.0.14
Using web-console 2.1.2
Steps to recreate:
Ensure that pundit is working properly
View a page that has a policy and uses authorize @object where object is your model
cd to the app/policies directory
touch object_policy.rb
refresh the page
you should receive the same error
It feels as if this may not necessarily be a pundit issue but an issue with how pundit is integrated into the application configuration so that a modified policy is not picked up properly on change.

@achansonjr just tried to replicate this and everything worked just fine. I used a bare Rails app though and you have a lot of gems in there that could be doing something wonky. Maybe try it with a simpler app, or try taking away gems until you find which one breaks it?

Totally understand. This app does have just about everything except the kitchen sink. I will try and investigate to determine what is going on and get back if I find anything. Thanks for the response.

Just a quick note while I was trying something. I am on a different machine that is newer (less rubies, gems, etc) and it is not exhibiting this behavior. No idea but if someone else comes looking for something like this, maybe it will help. It is mainly just annoying in development because it requires a restart for every policy change.

@achansonjr Please post here if you find anything. Thank you.
May it be related to spring gem?
p.s. there is a workaround, but I don't really like it.

@DmitriySalko It is possible. However the bundles for the app should be using the same gems, and running with the same processes, so I can't see why it would be working on one but not the other. I think your idea that there is almost too much crap in here to isolate and say its a pundit issue is on the right track. When I get to the other computer tomorrow I will give it a go by turning off spring, or anything related to the continuous development and see if that fixes it.

currently having this issue and comment out the spring gem, now it works...anyone know whats causing this?

For me, I was missing include Pundit at the top of my controller. Adding that line fixed it.

@jasonswett are you using the Spring gems?

@bliaxiong Yes.

fwiw i had to do the same with rails 5.2 and pundit 2.0 - didnt work before doing so.


how to set enhanced eCommerce in google analytics

this page describe how to implement Google Analytics Enhanced eCommerce with gTag.
I don't know how to implement it?

I'm not sure what your question is, but if you want to integrate GA in Django cleanly with django-analytical and you're a total fresher, start here:

Tutorial
Installation and configuration
Google Analytics (gtag.js) (service details)

I know how to install and configure it and use it  in my project.
I know how to clone it.
but I don't know how to use cloned app in my existing project?

@bittner thanks for your response
this page describe how to set enhanced eCommerce with gtag but i don't see any thing for this purpose in documentation and in code.
Is this feature available?


AttributeError: Can't get attribute 'DGLHeteroGraph' on <module 'dgl.heterograph' >

Hi, I try to run the example code "main_SBMs_node_classification.py" by the following command:
 python main_SBMs_node_classification.py --gpu_id 0 --config 'configs/SBMs_GraphTransformer_CLUSTER_500k_full_graph_BN.json'
But it comes with the following error:
AttributeError: Can't get attribute 'DGLHeteroGraph' on <module 'dgl.heterograph' from '/home/rody/.local/share/virtualenvs/rody-V7qEFACp/lib/python3.6/site-packages/dgl/heterograph.py'>
How can I fix this bug, thanks!

I fix it by remove dgl and install dgl(cuda version) because I run with gpu.

https://blog.csdn.net/weixin_39554819/article/details/128569482
该方法可以用，已测。

I remove dgl and installed dgl 1.1.2+cu118 dglgo 0.0.2, but it still comes with the following errors: cuda available with GPU: NVIDIA GeForce RTX 3090
[I] Loading dataset SBM_CLUSTER...
Traceback (most recent call last):
File "/home/zbh/whd/benchmarking-gnns-master/main_SBMs_node_classification.py", line 428, in
main()
File "/home/zbh/whd/benchmarking-gnns-master/main_SBMs_node_classification.py", line 318, in main
dataset = LoadData(DATASET_NAME)
File "/home/zbh/whd/benchmarking-gnns-master/data/data.py", line 38, in LoadData
return SBMsDataset(DATASET_NAME)
File "/home/zbh/whd/benchmarking-gnns-master/data/SBMs.py", line 160, in init
f = pickle.load(f)
AttributeError: Can't get attribute 'DGLHeteroGraph' on <module 'dgl.heterograph' from '/home/zbh/.conda/envs/dgl/lib/python3.9/site-packages/dgl/heterograph.py'>. How can I fix this bug, thx!

Maybe the .pkl file version is not compatible with the newest version of dgl??


chore: update plugins.ts

What does this PR do?
Add 5 more plugins:
@jayree/sfdx-plugin-manifest
@jayree/sfdx-plugin-org
@jayree/sfdx-plugin-prettier
@jayree/sfdx-plugin-source
sfdx-plugin-update-notifier
What issues does this PR fix or reference?

merged into #29


stays in Init API

thank you for the information. I'm watching this tomorrow.

instagram change the response of the api 🤨

I found same issue.

the API response has changed. I corrected that soon.

It's fixed!


Tray Publisher: Show last available version

Feature
Old standalone publisher showed last published version on selected context:

This is feature missing in Tray Publisher
[cuID:OP-6736]

Is this still relevant? if so, should we move this to ayon-traypublisher @antirotor ?

I think this was related only to traypublisher. And I think there already is option to set explicit version.

I think this was related only to traypublisher. And I think there already is option to set explicit version.

Not sure where one would define that in tray publisher?

It unfortunately also doesnt show the last version as the issue originally requested. (This is likely also due to the Publisher's design where it can't have defaults per instance, but only per creator or plug-in?)


[FEATURE] Distribute disk volume replicas across zones

Harvester should support setting soft and hard anti-affinity to distribute disk volume replicas across zones defined with the well-known node label topology.kubernetes.io/zone
https://longhorn.io/docs/1.2.4/references/settings/#replica-zone-level-soft-anti-affinity

It's automatically done via Longhorn soft anti-affinity across zones. https://longhorn.io/docs/1.2.4/references/settings/#replica-zone-level-soft-anti-affinity
The user needs to add label to the node, and Longhorn will do the right thing automatically.

@janeczku Could you please go into detail what you want to see here? E.g. by describing the expected workflow.

@votdev If the feature works, can we have a document and close the issue?

Test OK, will close the issue
Environment

ipxe 3 nodes (8c/16G/250GB)
1.4.0-rc3

Test Plan
Setup 3 nodes harvester, all nodes are in 2 different zones z1, z2. Then create a 2 replica storage class, and create a volume using the SC and check if LH correctly scheduled all replicas to different zones.

Set LH `Replica Zone Level Soft Anti-Affinity` to `false` (force LH to schedule replicas to different zones)

Set harvester-node-0, harvester-node-1 to zone `z2`, harvester-node-2 to `z1`

Create a storage class which replica count is 2

Create a volume `test` and attach the volume to a VM (make LH replica in running state)

Validate the replicas are in different zones (harvester-node-0 -> z2, harvester-node-2 -> z1)

Set LH `Replica Auto Balance` to `best-effort` (default is disabled, which doesn't rebalance replicas on the fly)

Set harvester-node-0 to `z1` (now harvester-node-0, harvester-node-2 are in zone `z1`, harvester-node-1 is in zone `z2`)

Validate the replicas are rebalanced to different zones (harvester-node-0 -> z1, harvester-node-1 -> z2)

Had a discussion with @brandboat, and we found:

The zone label only affects replica distribution during volume creation
If the volume already has enough replicas, applying the different zone labels will not affect the replica distribution

Maybe we can also mention this on topology-spread-constraints

I checked again and found that setting Replica Zone Level Soft Anti-Affinity to true also make Longhorn to schedule replicas in different zones.
On the other hand, setting it to false prevents more than one replica from being scheduled in the same zone. As a result, if the zone count is less than the replica count, setting this to false will lead to degraded volumes.


Lesson 3.12

The code for the live site appears to be different from the current repository. When I change the div to a button on the live site, text appears at the top with the secret word. When I do the same thing for the code I forked and cloned today, a picture appears in the background of a wombat but no secret text is visible.

Hey @emily-kay I bet that might happen if the local server isn't being run in the right directory. If you open the console in Chrome for your local version you might see errors related to chromevox-lite.
Can you try running a server from the root of the cloned project and then do the test again. I just tried and it seemed to work.
I may look into moving all of these examples to Glitch so folks don't have to mess with the local server step.


[AIRFLOW-3127] Fix out-dated doc for Celery SSL

Make sure you have checked all steps below.
Jira

[x] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-3127
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

Now in airflow.cfg, for Celery-SSL, the item names are "ssl_active", "ssl_key", "ssl_cert", and "ssl_cacert" (since PR https://github.com/apache/incubator-airflow/pull/2806/files).
But in the documentation https://airflow.incubator.apache.org/security.html?highlight=celery#ssl
or https://github.com/apache/incubator-airflow/blob/master/docs/security.rst,
it's "CELERY_SSL_ACTIVE", "CELERY_SSL_KEY", "CELERY_SSL_CERT", and
"CELERY_SSL_CACERT", which is out-dated and may confuse readers.
Screenshot of out-dated doc

Thanks.
BTW for doc only fixes if you put [ci skip] somewhere in the commit message travis won't run tests, which saves the ASF some money :)

Thanks @ashb .
Didn't know this [ci skip] feature. Will take note of it. Thanks!


Modules Overhaul

Currently LWC uses a lot of internal "events" that are triggered on various actions. In doing so, much of the work that exists in Bukkit events are re-implemented, badly. The entire thing is a big mess with unneeded complexity, making it very difficult to maintain. It would be much better if this were overhauled to use the Bukkit event system, reducing overhead and complexity, and greatly increasing maintainability.
This should not block the 2.1.0 release.
I am more than willing to tackle this myself, if so desired, and this can be turned into a meta-issue.

Sub tasks:

[x] Make the LWC "events" into actual Bukkit events and move them to a new events package
[ ] Migrate all modules to event handlers
[ ] Dispatch the events via Bukkit instead of ModuleLoader
[ ] Clean up now-unneeded code

[ ] Scripting package
[ ] Module package

For public discussion, @pop4959 has stated reservations about refactoring these so soon, in that other plugins still use this system.
My thoughts are that indeed, some time should be given for other projects to prepare for and/or update to the new system. The code for this can be sat on for some time before merging it. There is no rush.
That said, how is it known that plugins use the current module system? I have not seen any discussion on this, and indeed that should happen in this issue.

Yes, I think this is something to revisit at a later date. I have investigated the use of the module system in the plugin, and as far as I can tell it's been in place since 1 May 2011.
I don't think we really know yet what the full impact of rewriting this all would be. As mentioned, it's been over 7 years since the system was introduced to the plugin, and so there has been plenty of opportunities for plugins to integrate with it. For example, I found out recently that a popular plugin named ChestShop integrates with LWC. I don't believe that it uses the modules, but it is a good example of why we need to be wary of overhauling core parts of the plugin.
Also, until we have a very compelling reason to change it, I can't see why we can't keep the current system. It might be a bit clunky, but you have to admit it works. Cleaning up and refactoring the code is nice, but I think there are other issues that should be addressed first.
Thanks again @EbonJaeger for your eagerness to help out with the LWC development.
Also, if anyone has something else to add to this discussion, such as to start a list of plugins with LWC as a dependency, it would be greatly appreciated.

I think I'll close this issue, since it's remained stagnant for about a year, and I still don't see much reason to change it at the moment. It is a bit messier, but as I mentioned last time, it seems the events are rather baked in at this point. In addition, the internal event system serves as a sort of API for external plugins. As such, I don't think it is something that can/should be changed at this point, without breaking things.


Releases page doesn't render markdown

published page: https://opentelemetry.io/releases/
line in releases page in repo: https://github.com/open-telemetry/opentelemetry.io/blame/main/content/en/releases/_index.md#L52
hugo shortcode implementation: https://github.com/open-telemetry/opentelemetry.io/blob/main/layouts/shortcodes/release_notes.html#L14
The content of the releases is rendered in a <pre> block:

Since releases are already written in markdown, it'd be nice to take advantage of that and render it as markdown. Hugo has this functionality so I don't think it's a huge change.

Yeah, I still see this problem. For the record, release info is now published under https://opentelemetry.io/status/.


Occasionally some unexpected logs appear

W0217 00:39:04.785645       1 reflector.go:441] pkg/mod/k8s.io/client-go@v0.22.4/tools/cache/reflector.go:167: watch of *v2beta3.ApisixConsumer ended with: an error on the server ("unable to decode an event from the watch stream: unable to decode watch event: no kind \"ApisixConsumer\" is registered for version \"apisix.apache.org/v2beta3\" in scheme \"pkg/runtime/scheme.go:100\"") has prevented the request from succeeding

@tao12345666333 Hello, do you know what caused this log?Not sure if synchronization will be affected
I used the latest ingress controller and still have this log:
W0228 14:51:12.613401       1 reflector.go:441] pkg/mod/k8s.io/client-go@v0.22.4/tools/cache/reflector.go:167: watch of *v2beta3.ApisixUpstream ended with: an error on the server ("unable to decode an event from the watch stream: unable to decode watch event: no kind "ApisixUpstream" is registered for version "apisix.apache.org/v2beta3" in scheme "pkg/runtime/scheme.go:100"") has prevented the request from succeeding

synchronization will not be affected.

There will be some retry mechanism here.  But I don't have time to fix it yet, working on other high priority tasks

If it can't synchronize, there will be problems.
@tao12345666333   Is there any other way to avoid it ?
I used v1.3 before, but because of the problem of  "context cancel " #851 ,  I  changed to V1.4.  But this problem will also lead to instability in production.

@xianshun163  I will add this one to my list.  Fix it after ending other high priority tasks.

@tao12345666333 ,   my  crd  yaml config is like below , I define ApisixUpstream and ApisixRoute, is that anything error for my config file?     with the config, the apisix  work   all right, but  except  the err log below print always.
2022-03-04T15:15:13+08:00       error   ingress/apisix_upstream.go:130  failed to get service test-env/xss: service "xss" not found 2022-03-04T15:15:13+08:00       warn    ingress/apisix_upstream.go:210  sync ApisixUpstream failed, will retry  {"object": {"Type":1,"Object":"test-env/xss","Tombstone":null}, "error": "service \"xss\" not found"} 2022-03-04T15:15:13+08:00       error   ingress/apisix_upstream.go:130  failed to get service test-env/xss2: service "xss2" not found 2022-03-04T15:15:13+08:00       warn    ingress/apisix_upstream.go:210  sync ApisixUpstream failed, will retry  {"object": {"Type":1,"Object":"test-env/xss2","Tombstone":null}, "error": "service \"xss2\" not found"}
`
apiVersion: apisix.apache.org/v2beta3
kind: ApisixUpstream
metadata:
name: xss
spec:
timeout:
connect: 3s
read: 5s
send: 5s

apiVersion: apisix.apache.org/v2beta3
kind: ApisixRoute
metadata:
name: xss
spec:
http:
- name: rule1
match:
paths:
- /testenv/xss/*
backends:
- serviceName: xssservice-svc
servicePort: 8319
plugins:
- name: proxy-rewrite
enable: true
config:
regex_uri:
- "^/testenv/xss/*"
- "/xs/${1}"
- name: prometheus
`

#893 will solve the "xxx not found" problem

This is because ApisixConsumer is not register in scheme. This problem has been fixed in 1.4.1

https://github.com/apache/apisix-ingress-controller/pull/833

I will close it.


apkeep binary packages based on libssl1.1, not working on Ubuntu

The released apkeep binary packages for Ubuntu are linked against libssl1.1. However, Ubuntu uses libssl3 and cannot (easily) install libssl1.1.
If you try to run the binary apkeep-x86_64-unknown-linux-gnu on Ubuntu 22.04
./apkeep-x86_64-unknown-linux-gnu: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

It is a libssl problem
$ ldd apkeep-x86_64-unknown-linux-gnu
	linux-vdso.so.1 (0x00007ffec9b9f000)
	libssl.so.1.1 => not found
	libcrypto.so.1.1 => not found
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fd6d1a14000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fd6d1a0f000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fd6d0f19000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fd6d1a08000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fd6d0c00000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fd6d1a4e000)

Ubuntu 22.04 has both libssl3 and libssl1.1 packages.
Does it make sense to upgrade the binary packages to use libssl3? I am not familiar with the state of libssl and other distros.
Workaround
If you can launch a VM so that you do not mess up your Linux installation, you can
wget https://security.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1-1ubuntu2.1~18.04.21_amd64.deb
sudo apt install -f ./libssl1.1_1.1.1-1ubuntu2.1~18.04.21_amd64.deb

Then, you can run the binary apkeep.
Note: If you try to add symlinks to libssl3, it does not work. There are differences.

The latest version is compiled against libssl-dev from Debian 12, 3.0.11. Please let me know and re-open if problem reoccurs with apkeep 0.16.0.


fix(connector): warn on undefined nested field in struct when parsing JSON

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Undefined top-layer fields will we warned in a unified path after #12659, but nested field in struct of the JSON format will still be silently ignored. I don't find a way to also unify the path for this so manually add another warn here. (Maybe it's possible since a struct builder is essentially a Vec of nested builders?)
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

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

I don't find a way to also unify the path for this so manually add another warn here. (Maybe it's possible since a struct builder is essentially a Vec of nested builders?)

Nested fields in a struct is indeed very similar to top-level fields in a row, but the current definition is a little bit awkward and reusing takes more efforts (#12425). I have a refactor plan #13104 that hopefully would make it easier later.

Not unifying the handling path, I also find a parse failure (instead of undefined) on the nested field may lead to the whole struct to be replaced with NULL. 😕 This might also be confusing to users.


Improved the UI of about us section for issue #1344

I have improved the UI and Alignment of about us section, added hover effects on button, added more paragraph text, changed the alignment of buttons
Before -

After -

@smritig26 Your pull request has been successfully merged! Don't stop here—continue contributing by addressing more issues and aiming to become a top contributor. You can also contribute in my another Repository BuddyTrail which is also under Hacktoberfest
Great contribution to HACKTOBERFEST'24! 🎉


SVG Logitech G900 Data

SVG data for Logitech G900 mouse, with button on underside documented.

Thanks @whot! :+1: