Install Error

I have a problem . The problem is this ,when i install the chatterbot the cmd tells me
ERROR: Command errored out with exit status 1: 'C:\Users\Ariel\AppData\Local\Programs\Python\Python38-32\python.exe' 'C:\Users\Ariel\AppData\Local\Programs\Python\Python38-32\lib\site-packages\pip' install --ignore-installed --no-user --prefix 'C:\Users\Ariel\AppData\Local\Temp\pip-build-env-3gguqdfl\overlay' --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple -- setuptools 'wheel>0.32.0,<0.33.0' Cython 'cymem>=2.0.2,<2.1.0' 'preshed>=2.0.1,<2.1.0' 'murmurhash>=0.28.0,<1.1.0' 'thinc>=7.0.8,<7.1.0' Check the logs for full command output

Hello @arielpajares, I would suggest go for python 3.7.2 also keep in mind to delete the cache file after uninstalling. So,
delete the pip folder from C:\Users\soham\AppData\Local\pip and
delete the old python setup files from C:\Users\soham\AppData\Local\Programs\Python
then reinstall python 3.7.2
then pip install chatterbot

I believe this installation issue may have been resolved with #2027. Please let me know or open a new ticket if issues persist.


Check if port 80 is used

If apache is running on host, check if port 80 is in used, and disable it if possible.

Done.


JWS has invalid anti-replay nonce

I'm getting this error with increasing frequency. The response looks something like:-
{"type":"urn:acme:error:badNonce","detail":"JWS has invalid anti-replay nonce **NONCE**","status":400}

The only "fix" appears to be re-running dehydrated, sometimes several times, until it succeeds.
In https://github.com/diafygi/gethttpsforfree/issues/150#issuecomment-380361381 they suggest that "nonce timeouts are becoming more common". I assume that's what I'm seeing here too?

Mh that is weird, I never encountered that issue... A nonce timeout seems unlikely to me as dehydrated retrieves a nonce for every signed request and immediately uses it.
If you encounter this issue often you could help me identify the issue by adding an echo "Nonce: ${nonce}" >&2 after the whole code-block marked as # Retrieve nonce from acme-server.
If it happens again compare the nonce to the previous working ones and see if it is somehow shorter or looks completely different, has a special character the other nonces don't have, whatever it could be.

I am also seeing this.  Example output:
Processing demidamson.org with alternative names: *.demidamson.org
 + Checking domain name(s) of existing cert... changed!
 + Domain name(s) are not matching!
 + Names in old certificate: cliff.demidamson.org demidamson.org mail.demidamson.org proof.demidamson.org www.demidamson.org
 + Configured names: *.demidamson.org demidamson.org
 + Forcing renew.
 + Checking expire date of existing cert...
 + Valid till Jun  5 18:02:05 2018 GMT (Longer than 30 days). Ignoring because renew was forced!
 + Signing domains...
 + Generating private key...
 + Generating signing request...
 + Requesting new certificate order from CA...
Nonce: kSCHApAbf9-DzROJ2tDz5PHWQ6415Wt_NjqPB3tw41E
 + Received 2 authorizations URLs from the CA
 + Handling authorization for demidamson.org
 + Handling authorization for demidamson.org
 + 2 pending challenge(s)
 + Deploying challenge tokens...
 + Responding to challenge for demidamson.org authorization...
Nonce: 24xRxskZFAvH6TLV8h9E0xgE82Ozx3GeTbIizm0Gt0A
 + Challenge is valid!
 + Responding to challenge for demidamson.org authorization...
Nonce: 274clr42IKJTC3MUNPPdaxVaBGJDK88AknJ_Yv8K7PM
 + Challenge is valid!
 + Cleaning challenge tokens...
 + Requesting certificate...
Nonce: LhkvE7j-vosfFHtkjQ5EVFIZhuH5DAaBtMKL0-LULwU
  + ERROR: An error occurred while sending post-request to https://acme-v02.api.letsencrypt.org/acme/finalize/9161467/3737048 (Status 400)

Details:
HTTP/1.1 100 Continue
Expires: Thu, 26 Apr 2018 17:10:25 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache

HTTP/1.1 400 Bad Request
Server: nginx
Content-Type: application/problem+json
Content-Length: 169
Boulder-Requester: 9161467
Replay-Nonce: 2Gb7gCvUgTvEc1kbUca5bZpiLj5iNdecPXPMoY9GDYQ
Expires: Thu, 26 Apr 2018 17:10:25 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Thu, 26 Apr 2018 17:10:25 GMT
Connection: close

{
  "type": "urn:ietf:params:acme:error:badNonce",
  "detail": "JWS has an invalid anti-replay nonce: \"LhkvE7j-vosfFHtkjQ5EVFIZhuH5DAaBtMKL0-LULwU\"",
  "status": 400
}

Request failure: 400 {
  "type": "urn:ietf:params:acme:error:badNonce",
  "detail": "JWS has an invalid anti-replay nonce: \"LhkvE7j-vosfFHtkjQ5EVFIZhuH5DAaBtMKL0-LULwU\"",
  "status": 400
}

In case it helps, my config file contains:
CHALLENGETYPE="dns-01"
WELLKNOWN="${BASEDIR}/wellknown"
HOOK="${BASEDIR}/hook2.pl"
HOOK_CHAIN="yes"
<EMAIL_ADDRESS>

This is a really hard issue to debug... I'm running dehydrated in a loop right now but I'm not able to get it to fail even once. I'll try to implement retries using the nonce send back by the server, but it's really really hard for me to test as I just can't get it to fail.

OK, so it fails first time on every machine I'm trying it on.
Output (with echo) is below...
Nonce: UawgckMjzaYcfL8ic2bQRQLjBs0VKqAhzY7GOxSwvzc
Nonce: 3fYLEt90kzqRapD-wg3VTmnMufWboHwO4ux0Iid0Qgg
Nonce: Bv-Juf5kr281OAdl_bR9NcwRYKyPdxQxEy0tsNbeqg0
  + ERROR: An error occurred while sending post-request to https://acme-v02.api.letsencrypt.org/acme/finalize/5474087/3738618 (Status 400)

Details:
HTTP/1.1 100 Continue
Expires: Thu, 26 Apr 2018 17:41:29 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache

HTTP/1.1 400 Bad Request
Server: nginx
Content-Type: application/problem+json
Content-Length: 169
Boulder-Requester: 5474087
Replay-Nonce: 6bYt73P6LBAu0R2dNcCxJ7xBJCOK2B_sVIPdP4d0h2M
Expires: Thu, 26 Apr 2018 17:41:30 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Thu, 26 Apr 2018 17:41:30 GMT
Connection: close

{
  "type": "urn:ietf:params:acme:error:badNonce",
  "detail": "JWS has an invalid anti-replay nonce: \"Bv-Juf5kr281OAdl_bR9NcwRYKyPdxQxEy0tsNbeqg0\"",
  "status": 400
}

@CliffS @legsak1mbo do you by any chance have multiple egress ip addresses or a dual stack (ipv4+ipv6) setup? can you verify if the issue goes away if you set IP_VERSION=6 in your config file?

@legsak1mbo are you sure? no NAT or something that could result in the request coming from a different IP? that's basically the only way I'm able to reproduce this issue.

I don't believe so. Certainly nothing that would change between requests in the same run.

@legsak1mbo can you do a few curl https://my-ipv4.kurz.pw requests and see if the result changes between runs? just to make sure.

Well heck, it certainly does!
Time to get on the phone to my ISP...

@lukas2511 Fixing it to IPv6 appears to have solved the problem for me.

We encountered the same problem today.  It appears that a customer has changed the DNS configuration of one of the domains of the certificate failing to renew to a previous configuration where the A record was the IP address of an old shared hosting by OVH and no AAAA record was set.
Because OVH can do TLS for shared hosting through letsencrypt, my guess is that when the letsencrypt validation server tries to fetch a token it gets one from OVH (maybe an old one, and of course it's not what the validation server expects so the renewal fail… and the "invalid anti-replay nonce" message makes sense).
@CliffS Maye it's worth double-checking that both IPv4 and IPv6 resolves to the same server for your domain: that would explain why renewing over IPv4 would work if accessing through IPv6 brings you somewhere else?

@smortex Interestingly there was no reverse DNS for the IPv6 address, though IPv4 reverse was correct.  I have fixed the IPv6 reverse and I will retest without forcing the IPv6.

@CliffS I don't think reverse DNS has an impact here. I was thinking about the IPv4 address and the IPv6 address not being served by the same machine.

I had this issue today on a certificate with 6 alternative names: it was failing randomly on one of them.
After talking about it on irc with @lukas2511 and reading this thread, setting IP_VERSION=6 did indeed fix the issue for me. The server in question has 2 IPv4 addresses and 1 IPv6 addresses, but never had the issue before.
Checking with curl https://my-ipv4.kurz.pw, I always see the same IPv4 address, so I don't think it flickers.
I'll try to test that by creating a certificate with a lot of alternative name and run tcpdump to capture the result and see what exactly is going on.

I was having this same problem today and found that setting IP_VERSION=4 fixed the issue. My laptop has an IPv4 and IPv6 address.

I had this issue today, but unfortunately the ISP won't change its behavior.
@lukas2511 looking around the forums at LetsEncrypt there was a suggestion that the client retry the request with the nonce from the response a few(reasonable) times before giving up.
Would it be hard to implement this in dehydrated?

@lukavia i want to implement two things in the not-too-far future:
I want to try to find a way to resolve the api hostname only once, so that every further curl call uses the same server, this will solve this bug.
I also want to add retries, but those are a lower priority for me as use-cases with hundreds of domains per single certificate are low and everything else can quickly be solved by just running the script again.

@lukas2511 Unfortunately even if you resolve the api hostname only once, the problem will persist since the provider route would still be different every time. Here is an example:
I have 2 internet providers with pfSense router installed. pfSense is making load balance one on one. That means that on every request to the same ip each time it goes through the other provider and the originator (your) ip is different.
So I think retry feature should be higher priority.
P.S. Since you use curl, you can just make "host" command the first time to get the ip, and then use the ip with Host header for each request

@lukavia you can simply program a pfsense rule to route traffic to letsencrypt through one provider (i.e do not load balance it).
That's what I did when I I had the same issue.

This was an example of the problem. When the provider does the same you don't have access to those settings.

I also have the same issue, it seems to happen randomly, I have to launch dehydrated in a loop until it succeeds…

We're also seeing this, probably related to being behind NAT (so outgoing IP changes all the time). It's not clear to me why this should matter - is the source IP encoded in the Nonce somehow, or is it stateless at the server and and you're just getting a different remote server each time?
In any case, having dehydrated be able to retry with the new Nonce each time would be better, but perhaps this is a problem with Boulder itself?

From my side when I've added IP_VERSION=6 nonce error disappeared

Just to chime in, as I encountered this issue on a completely unrelated system and Googling brought me here.
This issue is essentially caused by LE being unable to get the ACME challenge from the specified domain name. It's clearly not as simple as DNS not being set up correctly, as it's more nuanced than this.
A lot of the people in this thread have found out that when you have multiple IP addresses, they don't always route to the same endpoint. Likewise if you're on a shared IP of any kind, there's no way to guarantee that you'll get the right host either. This is why a lot of people setting IP_VERSION=6 or IP_VERSION=4 "fixes" the issue, it's simply removing the "other" IP Addresses. Essentially, it boils down to your local configuration/network/setup and that's why there's no single thing that will "fix" it.
In my case, IP addresses weren't the issue but rather a redirect was redirecting .well-known incorrectly, causing it to return a 200 with content, just not the content of the ACME challenge - hence "bad nonce".
I was able to figure this out by simply trying to navigate to .com/.well-known/acme-challenge/ - it should return the nonce directly and not anything else.
To sum up, if you're getting this error:

Check how many IP addresses you have and ensure they all route to the same place
Ensure you're not using a shared IP address
Ensure you haven't got any redirects affecting .well-known
Make sure you can do a GET on the .well-known/acme-config/ from external sources

I am getting this error quite a lot with IPv6.  My server is using the same static IP when sending, but I noticed with tcpdump curl seems to alternate between two destinations for acme-v02.api.letsencrypt.org: 2600:1415:8:185::3a8e , 2600:1415:8:192::3a8e which may be causing problems if the backend servers aren't synchronising properly.  If I put in a single entry in my hosts file, I don't seem to get the error as often.  IPv4 is reliable, but dns normally only returns one ip address for acme-v02.api.letsencrypt.org.  Should I report this to Let's Encrypt since using the new nonce might be invalidated when curl connects to the other remote server again?

Actually my problem might just be with my connection as when I try on other Linux servers using the same two destinations I'm not getting the error.

ACME clients are supposed to transparently retry requests that fail due to an invalid nonce. This is explicitly mentioned in the spec (https://tools.ietf.org/html/rfc8555#section-6.5):

When a server rejects a request because its nonce value was
unacceptable (or not present), it MUST provide HTTP status code 400
(Bad Request), and indicate the ACME error type
"urn:ietf:params:acme:error:badNonce".  An error response with the
"badNonce" error type MUST include a Replay-Nonce header field with a
fresh nonce that the server will accept in a retry of the original
query (and possibly in other requests, according to the server's
nonce scoping policy).  On receiving such a response, a client SHOULD
retry the request using the new nonce.

Whether or not this is caused by NAT, multiple IP addresses, or server-side goings on, it generally shouldn't cause a fatal error. You can look at clients like acme.sh or Certbot to see how they handle this.

I've had the same problem. After updating from 0.6.3 to 0.6.5 the problem disappeared. Probably this helps someone else.

I ran into this today and tried it four or five times without success. I'm on PureOS, a Debian derivative. When I checked out the current code from the repo, the issue disappeared.

I'm getting error when I try to register and accept terms. I've already check that I'm using just one IP address. I'm using version 0.6.5
dehydrated configuration
INFO: Using main config file /shared/dehydrated/config
declare -- CA="https://acme-staging.api.letsencrypt.org/directory"
declare -- CERTDIR="/shared/dehydrated/certs"
declare -- ALPNCERTDIR="/shared/dehydrated/alpn-certs"
declare -- CHALLENGETYPE="http-01"
declare -- DOMAINS_D=""
declare -- DOMAINS_TXT="/shared/dehydrated/domains.txt"
declare -- HOOK="/shared/dehydrated/hook.sh"
declare -- HOOK_CHAIN="no"
declare -- RENEW_DAYS="30"
declare -- KEYSIZE="2048"
declare -- WELLKNOWN="/shared/dehydrated"
declare -- PRIVATE_KEY_RENEW="yes"
declare -- OPENSSL_CNF="/etc/pki/tls/openssl.cnf"
declare -- CONTACT_EMAIL=""
declare -- LOCKFILE="/shared/dehydrated/lock"
INFO: Using main config file /shared/dehydrated/config
Dehydrated by Lukas Schauer
https://dehydrated.io
Dehydrated version: 0.6.5
GIT-Revision: unknown
OS: BIG-IP <IP_ADDRESS> Build 0.0.6
Used software:
bash: 4.2.46(2)-release
curl: curl 7.47.1
awk: GNU Awk 4.0.2
sed: sed (GNU sed) 4.2.2
mktemp: mktemp (GNU coreutils) 8.22
grep: grep (GNU grep) 2.20
diff: diff (GNU diffutils) 3.3
openssl: OpenSSL 1.0.2p-fips  14 Aug 2018
INFO: Using main config file /shared/dehydrated/config

Generating account key...
Registering account key with ACME server...

ERROR: An error occurred while sending post-request to https://acme-staging.api.letsencrypt.org/acme/new-reg (Status 400)

Details:
HTTP/2.0 400
server:nginx
date:Wed, 02 Oct 2019 21:15:32 GMT
content-type:application/problem+json
content-length:100
cache-control:public, max-age=0, no-cache
replay-nonce:0002_xoIBQHkeneUKKhLjCGvLu2pNl-Me7aP-dTwuVkTtBU
{
"type": "urn:acme:error:badNonce",
"detail": "JWS has no anti-replay nonce",
"status": 400
}
Error registering account key. See message above for more information.

@altasnet Noticed you arent declaring "CA_TERMS", that's going to be required for the correct environment (staging or Prod) to register a new account.  You are using the Staging cert authority, may be defaulting to prod license terms if not defined and generating an invalid nonce for that reason.  Just a thought.

@altasnet Noticed you arent declaring "CA_TERMS", that's going to be required for the correct environment (staging or Prod) to register a new account. You are using the Staging cert authority, may be defaulting to prod license terms if not defined and generating an invalid nonce for that reason. Just a thought.
declare -- CA_TERMS="https://acme-staging.api.letsencrypt.org/terms"

Thank you for your time!
We get the same error in production:

Generating account key...
Registering account key with ACME server...

ERROR: An error occurred while sending post-request to https://acme-v02.api.letsencrypt.org/acme/new-acct (Status 400)

Details:
HTTP/2.0 400
server:nginx
date:Thu, 03 Oct 2019 13:04:33 GMT
content-type:application/problem+json
content-length:112
cache-control:public, max-age=0, no-cache
link:https://acme-v02.api.letsencrypt.org/directory;rel="index"
replay-nonce:0002JNQGAJOKMNtHGIDom3Mth9pEqsTPh7C3_zivlpEyN2k
{
"type": "urn:ietf:params:acme:error:badNonce",
"detail": "JWS has no anti-replay nonce",
"status": 400
}

@altasnet just a note:
"JWS has no anti-replay nonce"
and
"JWS has invalid anti-replay nonce"
are different errors.

@altasnet just a note:
"JWS has no anti-replay nonce"
and
"JWS has invalid anti-replay nonce"
are different errors.

I didnt get invalid anti-replay, it always no anti-replay.
Do you have any idea what could it be?

Same here:
Details:
HTTP/1.1 200 Connection established

HTTP/1.1 400 Bad Request
Server: nginx
Date: Fri, 04 Oct 2019 11:23:43 GMT
Content-Type: application/problem+json
Content-Length: 112
Connection: keep-alive
Boulder-Requester: 46078664
Cache-Control: public, max-age=0, no-cache
Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
Replay-Nonce: 00029Vzf0xEXudqikduz93gYlcO2Dg-cWv9FsO32GN44xyA

{
  "type": "urn:ietf:params:acme:error:badNonce",
  "detail": "JWS has no anti-replay nonce",
  "status": 400
}

FWIW, I encountered "JWS has no anti-replay nonce" today.  Eventually stumbled upon this thread, and solved the issue on my machine by adding CURL_OPTS="--http1.1" to my dehydrated config file.

This may be magically fixed when dehydrated at some points gets retry logic. Until then please just fix your network configuration.


 I tested it with various snippets, also snippets that just contain plain text and no "<" character or special chars, but it always fails with the same error:
execution error: Error: SyntaxError: JSON Parse error: Unrecognized token '<' (-2700)

Please provide the file in question. You can zip it first so GitHub will allow it to be uploaded.

C.zip
This one for example, I believe is because it contains quotes (").
I tried more of my snippet collections and there were indeed some that worked. It's probably because I have quite a lot of coding snippets with quotes or slashes. Thanks for checking!

Thank you, that helped. The issue wasn’t in the snippet itself, but I wasn’t ignoring the info.plist which includes more information on the collection.
Fixed in 2023.2.


Added 'react-app' to package.json

Correct webpack bundle error due to missing 'react-app' package.

@alerosa thanks!


[BUG] : In Categories section the images on the cards are not of the same size

Description
in categories section of the website the images on cards are of not same size
Screenshots

Any additional information?
To make website good looking it should have same image size.
What browser are you seeing the problem on?
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I'm a GSSoC'24-Extd contributor
[ ] I'm a Hacktoberfest'24 contributor
[X] I am willing to work on this issue (optional)

Please assign me this bug I will work on it


fix: update CI/CD process to enable auto-release workflow

Description

add new hook to pre-commit to fix eof lines
add new release.yml workflow. this workflow will automatically:

create and push new tag for next semver based on conventional-commits
create GitHub release with notes
update Changelog with release notes
this workflow will also automatically notify PRs that are included in the release, mimicking the manual behavior but now its automated https://github.com/clowdhaus/terraform-aws-rds/pull/1#issuecomment-952097291

remove old chglog configs and Makefile

Motivation and Context

automate release process in a standardized manner
standardize new CI workflow (copying from RDS)

Breaking Changes

No

How Has This Been Tested?

[x] https://github.com/terraform-aws-modules/terraform-aws-rds/pull/361

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

@antonbabenko FYI - looks like the Semantic Pull Request isn't on this repo (also not sure if that is broken since it seems to be hanging lately on checks that are valid)

"Semantic Pull Request" was deactivated on org-level and it has to be removed from all repos (I did it already on many).

ah ok

Btw, is it possible to adjust this message - https://github.com/terraform-aws-modules/terraform-aws-s3-bucket/pull/116#issuecomment-962667053 ?
Let's wait a bit before copying to other repos. I have a few comments before rolling forward.

hmm, I don't know to be honest

I have tried to fix the commit message in multiple PRs and I think it is good now - https://github.com/terraform-aws-modules/terraform-aws-rds-aurora/pull/257


TypeError: WebApiClient.ChangeSet is not a constructor

Hi there,
I'm building a custom component for CRM 365, and I'm using this nice library :).
When I'm using Batch functionality, I'm getting the following error:
TypeError: WebApiClient.ChangeSet is not a constructor
This is function I'm using:
export const saveFrequencies = qualityElements => {
  const reqs = [];
  qualityElements.forEach(qe => {
    const req = WebApiClient.Update({
      entityName: 'wfd_monitoringprogrammefrequency',
      entityId: qe.id,
      entity: {
        wfd_year1frequency: parseInt(qe.year1frequency) || 0,
        wfd_year2frequency: parseInt(qe.year2frequency) || 0,
        wfd_year3frequency: parseInt(qe.year3frequency) || 0,
        wfd_samplingperiod: qe.samplingperiod,
      },
      asBatch: true,
    });
    reqs.push(req);
  });

  const chSets = new WebApiClient.ChangeSet({
    requests: reqs,
  });

  const batch = new WebApiClient.Batch({
    changeSets: [chSets],
  });

  return WebApiClient.SendBatch(batch);
};

The batch updates work (those records are updated in CRM), but then my component fails, since I get that javascript error.
I'm using Chrome last version or Firefox last version.
Any Idea?

Hey there,
the ChangeSet constructor looks fine. If the update is being sent to CRM as well, then this can't be your issue location.
Can you check whether you tried to instantiate a change set somewhere after the call succeeds?
Kind Regards,
Florian

Hi Florian,
No, I didn't instantiate a change set after the call as far as I know :).
At the moment I've changed the batch, for an array of regular Updates and I manage them with Promise.all.
That at least works without type error.
Cheers,
Antonio.

Hi @garciasa,
I'll close this task as it seems to have caused no further issues to you.
If it does, please paste a minimum working example on a CRM default entity (such as account) and reopen this issue.
Kind Regards,
Florian


Help users to confirm a phone number

This is a work-in-progress proposed pattern for the GOV.UK Design System which covers asking users to enter a code sent to them via text message (SMS) for authentication purposes.
➡  Preview of the pattern
What
Asking users for a security code sent to them via text message.
Why
Government services are increasingly using a second form of authentication (2FA), in order to improve security. This often takes the form of asking for a code sent via text message, in order to demonstrate the user has something (their phone) as well as knows something (their password).
This has been adopted in slightly different forms by: HMRC, Home Office, DWP, GDS, and the Office for Product Safety and Standards (OPSS) in production services, and has been user tested to varying degrees.
Adopting this as a pattern within the GOV.UK Design System will help to improve cross-government consistency and make it faster for teams to add this feature to services.
The Design System has an existing pattern for password but not for text message security codes.
Considerations
Some services also allow users to choose between a security code sent via a text message or via an authenticator app (which is considered more secure, but has usability and practical challenges). It is proposed that the pattern only covers text message codes for the time being. In future the pattern could be expanded to cover authenticator app codes, or that could be a separate pattern.
The pattern includes some security recommendations, such as a 5 digit code and a 15 minute time limit, but doesn’t give a full specification, as this is likely out-of-scope for the Design System and is likely to vary by service. For instance, how often to ask for the security code, and how to handle repeated failed attempts, are not prescribed.
The pattern recommends that services describe what users should do if they do not have access to their phone number, either temporarily or permanently. However this is likely service-specific, any may involve contacting a support team, or asking a colleague or team admin to update their phone number. Consequently it is hard to include text for this within the actual pattern, and so instead this is left to the guidance. However it may be helpful to describe where this information should appear.

Could we recommend adding a domain-bound code where possible? https://developer.apple.com/news/?id=z0i801mg https://github.com/WICG/sms-one-time-codes

There's two other items in the GOV.UK Design System backlog that align closely with this new pattern:

Identifying users #25
Recover an account #84

Impact of repeated digits in security codes
We heard that codes with repeated digits (for example 11122 or 98776) are more difficult to transcribe for people with dyslexia or dyscalculia.
So I changed the algorithm which generates our code to avoid these runs of repeated digits (see https://github.com/alphagov/notifications-api/pull/3336). That change was made on 30 September 2021.
Effect on likelihood of entering the code correctly first time
From 4 July to 30 September 2021 there were 17,880 sessions and 19,855 page views on the page where people enter their security code1.
If we infer that people viewing the page more than once are people who have received an error and need to try to enter the code again that means 90.05% of attempts to enter the code are correct first time.
From 30 September 2021  to 4 November 2021 90.27% of attempts to enter the code are correct first time.
This is an improvement of 1%, but according to an A/B test calculator there’s only a 72% chance that this is a genuine improvement, in other words it is not a statistically significant result.
Effect on time taken to enter the code
The average time spent on the page from 4 July to 30 September 2021 was 38 seconds.  Most of this time will be spent finding your phone and waiting for the text message to arrive, rather than entering the code itself.
From 30 September to 4 November 2021 the average time spent on the page was 37 seconds.2
However this variable is hard to control. The are other factors which mean the deliverability of text messages may be faster from one month to another. So I think it’s hard to say whether this 1 second improvement is meaningful. Without doing a proper A/B test where the two choices are offered at random.
Conclusion
It may be that:

there is an improvement, but it’s too small to measure with the tools I have
it may require less cognitive load to enter a number without repeated digits – which is meaningful – but not measurable in terms of error rate or time taken

I’ve also heard from another dyslexic person who said they would find a number with no pattern more difficult:

I think I would find something like 55899 or 88221 easier than for example 67432, but that is just my intuition

I suspect that reducing the number of digits would be a more universal and significant change. I’d love to hear from anyone who’s able to properly A/B test 4 versus 5 versus 6 digits.

With the usual caveat that this only represents users who have opted in to Google Analytics
Google Analytics only gives us a number to the nearest second, so this could be a change from 37.0 to 38.4  (1.4 seconds) or from 37.4 to 38.0 (0.6 seconds). Not sure you could get statistical significance from this level of prevision

@quis thanks for sharing! I'm also interested in the 4 vs 5 vs 6 digit debate. The current draft guidance suggests 4 digits (in part thanks to your earlier suggestions), but nearly all the government service I’ve used have used 5 or 6.
Intuitively it feels that 4 digits (plus technical measures to prevent repeated incorrect attempts) ought to be more usable, accessible and just as secure, but I’d be interested to hear from anyone who has implemented this.

GOV.UK Design System working group review
The Design System working group reviewed this proposal in November to December 2021. They’ve approved it to be useful and unique.
It’s now ready to be worked on to add more details, guidance and information on how to implement.
The working group also made recommendations to consider:

how this pattern would work for different circumstances, such as people with limited internet access or no access to a phone
how the time limit (currently 15 minutes) would affect people with poor reception — could it delay delivery of  the text message or otherwise cause panic?
if the journey should be slightly different ‘when creating an account’ compared to ‘when signing in’ (currently they’re nearly the same design) — users usually expect more verification to set up security processes
if the code should be more than 4 digits — 5 or 6 would be more secure, and 2 groups of 3 digits (123 456) might be easier to remember
grouping this page with related design standards for other authentication methods

Before we publish this contribution as a pattern, the working group will review it again to make sure it’s usable, consistent and versatile.

Hi @christopherthomasdesign, finished a review to polish this and match GOV.UK style. Offered suggestions, but some are hunches.
This pattern's feeling very thorough!

I also have a few queries about the content, for example:

is "resend" plain English or should it be "send a text message again" or similar?
would we say "incorrect security code", or "wrong security code" or "enter correct security code"?
do we do questions as links? or should it be an action such as "request a new code or use a different phone number"
for the example of the text message, surely every service we're working with will have the domain of gov.uk? why not just have that in the example (or at least explicitly say it in the guidance)?

Looking at related services, I feel that there's probably a fair bit of extra research needed on things such as:

if we need to tell people how long they have until the code expires
how we give people the option to skip 2-factor authentication on a service

@vickytnz thanks for reviewing this! Really appreciate it.

is "resend" plain English or should it be "send a text message again" or similar?
would we say "incorrect security code", or "wrong security code" or "enter correct security code"?

I’ll leave these to @calvin-lau-sig7. I just checked and Notify use "Code not found" and Government Gateway uses "Enter a valid access code".

do we do questions as links? or should it be an action such as "request a new code or use a different phone number"

I'm not sure if there are any issues with questions as links? I'm not sure that "Request a new code" would be enough, as the "Resend security code" page that the link goes to also contains advice about what to do if you do not have access to your phone (which would be service-specific advice).
If it's weird to have a question mark as a link, it could be something like "What to do if you have not received the text message" or similar?

for the example of the text message, surely every service we're working with will have the domain of gov.uk? why not just have that in the example (or at least explicitly say it in the guidance)?

It would need to be the full domain of the service, including any subdomain. So potentially we could use @www.example-service.service.gov.uk #12345 as the example?

Looking at related services, I feel that there's probably a fair bit of extra research needed on things such as:

if we need to tell people how long they have until the code expires

My feeling was that it was ok to only mention the 15 minute window on the "Resend security code" page, so the "Check your phone" page could be simpler, on the basis that most of the time users don't need to know the time limit. But open to persuasion!

how we give people the option to skip 2-factor authentication on a service

We've tried to avoid giving too much specific advice over whether & when to use SMS 2-factor authentication, as that soon veers into security guidance, which is possibly better handled elsewhere, and because it's so service-dependent (eg internal vs external services, high-risk vs low-risk)!
The introductory paragraph currently suggests two options:

Ask users to enter a security code when they need to sign in or complete a higher-risk task, such as changing a password.

Being able to opt-in to SMS 2FA might be another option, or to have alternatives like back up codes, authenticator apps, and so on might be other options we could allude to - although some of those also pose lots of questions!
Do you have any thoughts on how we can strike the right balance?

@frankieroberto cool - those all sound good, and I should say that when I meant "further research", I wasn't meaning so much in a blocking way but that it might be good to have those to the list of other things to investigate? For example, with the 15 minute thing, on the govuk account and also with a tax service we found that it helped people in areas with dodgy mobile access as it made them realise that they needed to get somewhere fairly quickly to get the message!

Thanks both!

is "resend" plain English or should it be "send a text message again" or similar?

Good spot, 'resend' might not be the most user-centric word as it's an action the service is performing, rather than the user. I'll put in suggestions for "Request a new security code". I've been considering just "Get" but it'd lose a lot of context.

would we say "incorrect security code", or "wrong security code" or "enter correct security code"?

Looks like it's more secure to avoid explicitly saying a security code is incorrect, will suggest change to: "Enter a correct security code"

@frankieroberto cool - those all sound good, and I should say that when I meant "further research", I wasn't meaning so much in a blocking way but that it might be good to have those to the list of other things to investigate? For example, with the 15 minute thing, on the govuk account and also with a tax service we found that it helped people in areas with dodgy mobile access as it made them realise that they needed to get somewhere fairly quickly to get the message!

Ah, interesting - which screen did you put the message on? The one asking for the code, or another page? Can you share a screenshot?
We've made some changes in response to your other suggestions, thanks! 🙌

Thanks @EoinShaughnessy! I've taken on your suggestions in 1 commit. Think we're good to go if you'd like to approve?


ethereum: Resend pending requests upon WebSocket close

Addresses https://github.com/oasislabs/oasis.js/issues/227

As discussed offline, we decided to punt this to the application layer. Closing.


combine Redshift cluster management, sql and data DAG

currently, we have 3 DAG and 3 times we create and delete cluster. Find the possibility to combine it

https://github.com/astronomer/astronomer-providers/blob/main/astronomer/providers/amazon/aws/example_dags/example_redshift_cluster_management.py
https://github.com/astronomer/astronomer-providers/blob/main/astronomer/providers/amazon/aws/example_dags/example_redshift_data.py
https://github.com/astronomer/astronomer-providers/blob/main/astronomer/providers/amazon/aws/example_dags/example_redshift_sql.py

As we are deprecating Astronomer Providers, we might not need this anymore, closing this


Sending a partition key makes targeted multi-partition aggregation queries more expensive

Describe the bug
When I run a targeted multi-partition aggregation query against the same data (two levels of depth), the request charge depends on the presence of the partition key. With a partition key that includes the first level of subpartitioning, the request charge is orders of magnitude higher than if I omit the partition key.
To Reproduce
I wrote a simple console application to reproduce the issue. Please download the solution, open the Program.cs file and specify a connection string to an Azure Cosmos DB for NoSQL account. The application will create a new database with two containers, non-subpartitioned and subpartitioned. For both of them it will upsert the same set of data, run an aggregation query (with and without a partition key) and display important metrics. You can run the application multiple times, it will create resources and upsert data only once.
Each container contains 100 documents (articles) with the following properties:

Id : string
CustomerId : Guid
Label : string
Title : string

The value of the Id property is a random GUID. The value of the CustomerId and Label properties is always the same. The value of the Title property is unique for each document.
Both containers share the same indexing policy; automatic and consistent. However, the partition key is different. The first container (non-subpartitioned) uses a partition key /customerId, so there is a single logical partition with 100 documents. The second container (subpartitioned) uses a hierarchical partition key /customerId, /id, so there are 100 hierarchical logical partitions with one document.
Then I run a query SELECT VALUE COUNT(1) FROM c WHERE c.customerId = @customerId AND c.label = @label against both containers:

Non-subpartitioned: I send the customer id as the partition key (in the request options).
Subpartitioned: I send the customer id as the partition key (in the request options).
Subpartitioned: I do not send a partition key.

I can observe the following results:
Container: NonSubpartitioned
Partition key: ["df165b31-7641-4664-9549-37862ed806ee"]
Request charge: 3,09
Container: Subpartitioned
Partition key: ["df165b31-7641-4664-9549-37862ed806ee"]
Request charge: 6,27
Container: Subpartitioned
Partition key:
Request charge: 3,09
Expected behavior
Sending a partition key that includes the first level of subpartitioning does not make aggregation queries more expensive.
Actual behavior
With enough data and a partition key that includes the first level of subpartitioning, the request charge of aggregation queries is orders of magnitude higher.
Environment summary
SDK Version: 3.37.1
OS Version: Windows 11 Enterprise (10.0.22631 Build 22631)
Additional context
It happens in both Direct and Gateway mode. Also, even if I set the PopulateIndexMetrics request option, the response does not contain the metrics.
In previous experiments we generated more data and captured diagnostics from the SDK. See the results from the subpartitioned container; with the first level of subpartitioning and without a partition key.

@alesk-kontent thanks for reporting the issue. I downloaded your app and confirmed your findings.
Comparing the execution of the queries in the subpartitioned collection:

For the query that was executed without any partition key in the request, the query engine is able to push both the filter (WHERE) and aggregation (COUNT) to the index fully. The outcome of this is that the query engine is able to calculate the result without loading any documents.
For the query that was executed with the partial partition key in the request, the query engine is able to only push the filter (WHERE) to the index but still requires runtime evaluation. This has to do with the facts that

hierarchical Partition key filter (supplied in the request) is represented differently in the request and effective partition key range (aka epk range) is different from what user supplied in the API
the index is for the entire physical partition and therefore the epk filter needs to be re-evaluated at runtime
The outcome of this is that the query engine needs to evaluate the partition key filter and then calculate the aggregate (COUNT) by loading each document returned by the index (using query filter). Because query execution contains 1 index consultation and runtime evaluation, RU consumption is higher than case 1 above (where only 2 index consultations are involved).

For the non-subpartitioned collection, query execution is identical to case 1 above where both the filter and the aggregate can be fully pushed to the index and query is executed without loading any documents.
As a mitigation for case 2, we can enable indexing epk range for such case. In this case, it should allow query execution using 3 index consultations (query filter, epk filter and aggregate). Please note that indexing epk range can be expensive for a large number of unique hierarchical partition keys. Generally speaking, in most cases, the RU consumption of epk filter evaluation should be much lower compared to loading the documents, but there may be outlier cases.
I also confirmed your finding regarding index advisor not returning results and are investigating it actively. The latest released sdk (3.38.0) should have this fix and index advice should flow as expected.
However we also found another issue that affects the advice returned by the index advisor in case 2 above (epk filter) and are actively working on the fix.
Hope this helps. Kindly let me know if you have any subsequent questions.

The issue affecting the advice is addressed and fix in this PR https://github.com/Azure/azure-cosmos-dotnet-v3/pull/4303


Maintain node order

Hello,
This is an attempt to fix https://github.com/Apicurio/apicurio-studio/issues/1675 / https://github.com/Apicurio/apicurio-studio/issues/1676, where items in the specification are re-ordered when you use the source editor to make changes.
Rather than removing and adding nodes, I've tried to update the existing entries in-place. As far as I can tell, this will fix it, but I've only dipped into the code around this, so I might be missing some wider context and I might have got the wrong end of the stick as to what's going on.
JSONassert doesn't appear to support strict ordering assertions on fields within an object, so I've not made any changes to the tests for this (so far). It would be good to make assertions on the ordering not changing in this context, but I don't know how far it is worth going if it means changing library etc?
I've also got some question marks in there about whether a ReplaceNodeCommand would ever have an old node with one path and a new node with a different path. I assume not, but just want to check if it's worth handling.
Also I've taken advantage of the fact that the addXyz methods (e.g addSchemaDefinition) are actually puts into maps. I thought about renaming those methods or adding methods to make it clear that it's an update rather than an add, but thought that might be overkill?
What do you think?
Thanks

Will look at this ASAP, but wanted to say 'thank you' for the contribution!  So.... thank you.  :)
I haven't checked the code yet, but your explanation sounds very interesting.  The existing ReplaceNode style commands are very basic, so having something more sophisticated will be very nice.  We'll need to worry about backwards compatibility, but I'm guessing it's just an algorithm change, not a state change, in the commands.  But I'll check that.
As for testing, we should just add a new assertion path when we care about ordering.  I'd rather not change everything - let's be targeted.  I don't know what test libraries support that.  And we should also make sure to update the tests in both Junit and Jest.  That's critical for this library.

OK help me understand how this is different from what was happening before.  I see the change to the base command, where instead of a "remove" then an "add", instead there is a "replace".  That makes sense.  But the implementations of this "replace" method seems to mostly be doing a remove and then an add, just like before.  What am I missing?  :)

I've also got some question marks in there about whether a ReplaceNodeCommand would ever have an old node with one path and a new node with a different path. I assume not, but just want to check if it's worth handling.

I don't think this can happen.  However, what can happen is that the node being replaced no longer exists.  This can happen in collaborative editing scenarios.  If I edit the source code for a node, but someone else has deleted that node, what do I expect?  Should the node re-appear because I've edited it?  Or should it be gone because someone deleted it first?  I'm honestly not sure.  Your current logic in this case does seem reasonable.  However, I think in other situations like this (in this library) the delete would stick because it happened first.  I think in other commands that's how we handle it.  So perhaps we should have a common check in ReplaceNodeCommand that does nothing if the source node being replaced doesn't exist in the regular document.

But the implementations of this "replace" method seems to mostly be doing a remove and then an add, just like before. What am I missing? :)

So the remove shouldn't be happening if the paths can never change between the old node and new node. Effectively it should only be the adds (puts). The implementation of the maps being updated is a LinkedHashMap, so ordering is preserved on updates (i.e. put with an existing key), while it will not be maintained if the entry is removed and re-added as it was before. That's what I was trying to get at when I said I thought about renaming those methods or adding methods to make it clear that it's an update rather than an add, but thought that might be overkill? :)
I'll have a think about the rest of what you said.

Oh thank you for the explanation.  I understand now - I was reading the logic incorrectly (didn't look closely enough).  I see now - so the remove step only happens if the paths are different (which shouldn't be possible IMO).  This makes total sense now.
That said - I think your instinct to add a replace/update method to make things more explicit is a good idea.  In most/all cases it could perhaps just delegate to the existing add method.  It's probably not a good idea to leverage "insider knowledge" of how these classes work.  So +1 from me on adding update/replace variants for these cases.
One interesting thing for us to consider here is that this library is written in Java but transpiled to Typescript (and ultimately javascript).  So we really need to have a unit test for this to make sure it works as expected in both environments.

I've not forgotten about this. I'll get back to it in a week or two :)

No problem!  I know how it is.  :)

perhaps we should have a common check in ReplaceNodeCommand that does nothing if the source node being replaced doesn't exist in the regular document.

Looking at it again, I think that's what this is doing already https://github.com/Apicurio/apicurio-data-models/blob/master/src/main/java/io/apicurio/datamodels/cmd/commands/ReplaceNodeCommand.java#L81-L85
        @SuppressWarnings("unchecked")
        T oldNode = (T) this._nodePath.resolve(document);
        if (this.isNullOrUndefined(oldNode)) {
            return;
        }

Though, when I commented it out there's no tests failing for it, so that's something to check.
I've made the Command tests assert an exact ordering of elements and found that there were a lot of other Commands that were not maintaing ordering, I've not got through them all yet. This has turned into a bit of mammoth exercise, just because of how many commands there are - though I spent a lot of time fighting the transpiler, which I won't have to do again at least now that I've seen what was going wrong :)
I think there's 4 general categories of Command:

add commands add a new thing on execute and remove the thing on undo, so there is no strict ordering to apply
delete commands remove something on execute so undo should put the thing back where it was.
rename commands modify something on execute and undo and should preserve the position of the renamed element.
replace commands update the value of a key on execute and undo and should preserve the position of the replaced element.

I've added two methods to ModelUtils that do most of the work for those, and I've had to add some extra state to some commands to remember the position on deletes, and there's a fair amount of boilerplate around it.
If you're okay with the general approach, then I will look to tidy things up a bit once I've checked the remaining Commands to see which of them need fixing.

I'll take a look at this soon.  Great writeup and thank you for working on this!  One thing that occurs to me based on your writeup is that any new state we add to existing commands must have a default value.  This is because the commands are marshaled and persisted - so there will be old versions of these things sitting around waiting to be loaded and executed by some new version of this library.
Other than that, great analysis.

Fantastic pull request @colvinco!

One thing that occurs to me based on your writeup is that any new state we add to existing commands must have a default value. This is because the commands are marshaled and persisted.

From what i can see there is no new state added to the commands.
I went through the commands and many have a new property used to track the index which is used to maintain node order. Currently these properties are public, but I don't believe that they need to be as they aren't used externally and are not being used as part of the command state.
@EricWittmann I see @JsonIgnore used in some other commands (RenameChannelItemCommand and RenameParameterCommand so maybe there is a reason to still surface these properties used for indexing?
If there is not, which I think is the case then I think we should be conservative and make all these new properties private.
In case you are thinking of making new changes @colvinco I wonder whether we should merge this into a feature branch and you can work with this as the base. This is already a large change so any future reviews would be smaller and easier to verify etc.

So a good example of my concern is here:
https://github.com/Apicurio/apicurio-data-models/pull/400/files#diff-5fd54972ff284b331a3f9ab9760ace72726dfbf63159f988aec93dc7ffa9ee02
Adding a new field _oldExampleIndex with type int may result in a failure to unmarshal existing commands that have been persisted in the Apicurio Studio DB.  I think that field should be of type Integer and the logic of the command updated to revert to the old legacy logic if the value is null.

So a good example of my concern is here:
https://github.com/Apicurio/apicurio-data-models/pull/400/files#diff-5fd54972ff284b331a3f9ab9760ace72726dfbf63159f988aec93dc7ffa9ee02
Adding a new field _oldExampleIndex with type int may result in a failure to unmarshal existing commands that have been persisted in the Apicurio Studio DB. I think that field should be of type Integer and the logic of the command updated to revert to the old legacy logic if the value is null.
Backwards compatibility! :)

Yep I can definitely update those ones

I think the suggestion to make this a feature branch is a good one.  @craicoverflow @colvinco

https://github.com/colvinco/apicurio-data-models/pull/1 should address those ints.

If you want to create a feature branch in the main repo then that's fine by me. Otherwise I can just create PRs against this here. (though the checks won't run on them)

And https://github.com/colvinco/apicurio-data-models/pull/2 fixes the ordering the rest of the commands that I think needed intervention. It's possible that I've missed something in amongst the 166(!) command classes so I can't say that I've fixed the problem in all situations, but this should definitely cover the majority.
If I revert the actual code changes and run the updated tests then I get 66 failing tests.

Fanstastic!  @craicoverflow unfortunately has had the audacity to get married and go on his honeymoon.  So this is now stuck in my queue.  If it's not too much trouble, can you open a PR against the new branch I made for this?
https://github.com/Apicurio/apicurio-data-models/tree/feat/maintain-node-order
I love this change.  I just need to peer intently at it for awhile, since (as you've observed) there are a lot of touch points.

:)
I've pointed the pr at that branch, no worries


Authentication Problem

Hello I installed the system, but "php artisan user:create" not worked saying: There are no commands defined in the "user" namespace.
Then I checked the user in phpmyadmin and found admin :
I entered username and password manually, now it's working

Hey, @vdanelia sorry for the inconvenience. Accidentally this featured was removed from the last commit. I pushed fix please check it out.


Add unit test for Inverse in pkg/labels/matcher.go

This PR is about adding a unit test for Inverse in pkg/labels/matcher.go.
Signed-off-by: Hu Shuai<EMAIL_ADDRESS>

Thanks, PTAL

PTAL

Sorry, I made a mistake.


update per changes to<EMAIL_ADDRESS>

Addresses #6

Thank you @wesnick!
I've added additional commit to keep #1 fixed and merged your work in master branch.
1.x branch was created for support of old versions of symfony/workflow (before BC-break in https://github.com/symfony/symfony/pull/20462)


[UNR-2553][MS] Fix for droppped URL options.

Contributions: We are not currently taking public contributions - see our contributions policy. However, we are accepting issues and we do want your feedback.

Description
Fix for scavengers dropped URL options.

Update.


Add features: createRoot, PromiseWrapper, and react lazy

Hi,
I am very short on time and had to "throw this over the wall" but here are 3 very important React features I'm using for my own needs:

createRoot is the new alternative to ReactDOM.render and if not used will limit React features to version 16
PromiseWrapper is a convenient helper utility to use Suspense for experimental data fetching from any arbitrary source

Here's a great article about this pattern

React Lazy lets you lazy load modules for Suspense

A lot of testing is needed and code cleanup. I am hoping the Slinky community is patient with these WIP changes and is willing to help out a bit too. I will try to support more in time but I wanted to initiate the PR just to get the ball rolling with at least baseline functionality.
Thanks!

addresses: https://github.com/shadaj/slinky/issues/196

Thanks for the PR @evbo! This will be a great starting point for getting Slinky up to speed with the latest React features.
In the near future, would you be able to fix some of the formatting issues? That way we can get this merged and start working on followup testing.

Wondering what needs to be done to get this in

I pretty much just threw the code over the wall, missing some unit testing opportunities, code cleanliness here and there. I left a comment with the only functional change I would still make.


Update RocksDbNative to 6.0.1

Update the native package to get new bug fixes in newer version of rocksdb native.
Fixes AB#1374242

/azp run Mac BuildXL PR Validation
/azp run Mac Public BuildXL PR Validation
/azp run Part B BuildXL PR Validation Expected
/azp run Primary BuildXL PR Validation
/Azp run Public BuildXL PR Validation

A new PR is created, see: https://github.com/Microsoft/BuildXL/pull/255


Extract hardcoded options in cms administration

1. Why is this change necessary?
Add services and blocks to manipulate selection fields more easily and centralized. E.g. when you add a new product box layout you have to change override three twig blocks to add an option. Two of these blocks surround the selections and not the options. So only one can override the selection successfully in a not update-safe way. If I add a new cms block that shall also support product box layouts I can add the standard entries but I won't be automatically be aware of new entries.
2. What does this change do, exactly?
Move every non-null hardcoded option in a selection into a cms service to provide these and possibly future values.
3. Describe each step to reproduce the issue or behaviour.

Add product box layout
Override multiple twig js blocks (non update-safe and competitive to other bundles)
Add new cms block with product box layout selection but without new product box layout from other plugin 🙄
💢

4. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hey Joshua,
we think your PR is awesome! 👍 It allows easier modifications for plugin developers.
I have some ideas to make it even more awesome, because I saw some pitfalls in your implementation:

Performance: The functions get called everytime Vue rerender the view
Runtime Updates: A plugin developer can not add an option on the fly. The view don´t react automatically to this change

To solve these problems I would put all your state information in the store (cms-page.state.js):
Example:
...
state: {
        currentPage: null,
        currentMappingEntity: null,
        currentMappingTypes: {},
        currentDemoEntity: null,
        pageEntityName: 'cms_page',
        defaultMediaFolderId: null,
        currentCmsDeviceView: 'desktop',
        selectedSection: null,
        selectedBlock: null,
        isSystemDefaultLanguage: true,
        fieldOptions: { // you can choose a better name if you want ;)
            pageTypes: {
                page: {
                    label: 'sw-cms.detail.label.pageTypeShopPage'
                },
                landingpage: {
                    label: 'sw-cms.detail.label.pageTypeLandingpage'
                },
                product_list: {
                    label: 'sw-cms.detail.label.pageTypeCategory'
                    /*
                        will be implemented in the future
                    },
                    product_detail: {
                        label: 'sw-cms.detail.label.pageTypeProduct'
                    */
                }
            },
            alignments: {
                'flex-start': {
                    label: 'sw-cms.elements.general.config.label.verticalAlignTop',
                    vertical: true
                },
                center: {
                    label: 'sw-cms.elements.general.config.label.verticalAlignCenter',
                    vertical: true
                },
                'flex-end': {
                    label: 'sw-cms.elements.general.config.label.verticalAlignBottom',
                    vertical: true
                }
            },
            ...
        }
    },
...

Then you need mutation functions for setting new values.
Values which returns modified data like
getVerticalAlignments() {
        return Object.fromEntries(
            Object.entries(this.getAlignments())
                .filter(config => config[1] && config[1].vertical)
        );
    }

can be moved in Getters. Then Vue can automatically cache these and only recalculate when some dependency gets updated.
This allows Vue to dynamically react to changes and don´t call the functions for every rerender of the view. These gives the administration a better performance and plugin developer can add options on the fly and everything updates automatically :)
What would do you think? Would you agree with the idea? If yes, it would be awesome to refactor your PR to the strategy :)

I really like your thoughts about the performance. I am familiar with vuex so this is not an issue for me.
fieldOptions suits.
So there would be a method that is used like this
commit('upsertAlignment', {key: 'foobar', label: 'foobar', vertical: true})

?
In my idea you add alignments like you add languages to the snippet management. Just a onliner
Shopware.Server().get('...').upsertAlignment('foobar', {label: 'foobar', vertical: true})

that can be easily added. Can I alter the states already at plugin injection as well?

The vuex store is directly available when the plugin get injected. Therefore, you can add language at every time in your plugin with this command:
Shopware.State.commit('cmsPageState/yourMutationFunctionName', yourPayload);

I like the benefits you stated.
I will set the label to Incomplete and when you are ready I will remove the label 👍

Hi @JoshuaBehrens,
is there any chance you'll get to this PR any time soon?
This is pending over a month. If you still need time I'd like to close this PR due to inactivity and you are free to create a new one once this is ready :slightly_smiling_face:
Sunny regards
Pantrtxp

I already rebased it yesterday evening #nojoke. I am working on it. I just push my rebase. I think about putting helpers into cms-state mixin. That is my state of work :D

I need a short review. I fiddle around with your requested feature to change data live. But it seems not to change live.
I pushed one example to try it. It is the selection for block categories.
Shopware.State.commit('cmsPageState/setFieldOptionBlockCategory', {name:'foobar', label: 'party'}) does add the new category to the state. You can test it by reading the state Shopware.State.get('cmsPageState').fieldOptions.blockCategory.foobar. The UI is not updating though. When I change the page and come back to the cmsPage editor and open up the block add sidebar there is my newly added block category.
Wrapping the read property in the template into a computed property does not change anything. How do I make it as reactive as intended?

I just had to use Vue.set in the state to make it reactive 🎉  Have a look at the refactory. That should match your proposal.

As @mitelg once suggested I should be part of the authors list, well I added myself now :)

Avatar is fixed

Rebase is out

I'll have a look how to test this. Any reference tests you suggest for Vuex tests?

Thanks :+1: There's one test already using the cms-page store, platform/src/Administration/Resources/app/administration/test/module/sw-product/view/sw-product-detail-base.spec.js. I don't think you'll need to properly register the whole thing like it's done there though. For your mutations/actions, I think the vuex testing guide from vuejs.org is a good orientation. Here they import the store and test the methods in isolation.

Thank you for the explanation. This will help me a lot here. Gonna polish the code 😁

Hello, we're closing this pull request due to inactivity. If this change is still important to you, feel free to create a new pull request.
For more information about our contribution guidelines, see https://docs.shopware.com/en/shopware-platform-dev-en/contribution/contribution-guideline.


.INPUT STATUS

I just requested that input feedback is added (see also: #3).
The suggested format I had was "INPUT HDMI X" where X is the mapped input number, e.g. my Chromecast is plugged into HDMI 1 on my TV and I have it correctly mapped to INPUT HDMI 1 in Roomie.

See #3 for an update from Roomie

Still waiting for Roomie, but I have added .INPUT STATUS back in for now. See #3 for more info


Example S3 function

Hi! I just wanted to add more examples, like #5. This is a s3 example of reading its object.

thanks!


Possible Unhandled Promise Rejection (id:0)

Hey Team,
I get this yellow box:
Possible Unhandled Promise Rejection (id: 0):
Already read
TypeError: Already read
    at consumed (http://<IP_ADDRESS>:8081/index.ios.bundle?platform=ios&dev=true:12146:23)
    at Response.Body.text (http://<IP_ADDRESS>:8081/index.ios.bundle?platform=ios&dev=true:12237:14)
    at _class._onRegisterPressed$ (http://<IP_ADDRESS>:8081/index.ios.bundle?platform=ios&dev=true:73490:940)
    at tryCatch (http://<IP_ADDRESS>:8081/index.ios.bundle?platform=ios&dev=true:10389:30)
    at GeneratorFunctionPrototype.invoke [as _invoke] (http://<IP_ADDRESS>:8081/index.ios.bundle?platform=ios&dev=true:10665:12)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (http://<IP_ADDRESS>:8081/index.ios.bundle?platform=ios&dev=true:10422:13)
    at tryCatch (http://<IP_ADDRESS>:8081/index.ios.bundle?platform=ios&dev=true:10389:30)
    at invoke (http://<IP_ADDRESS>:8081/index.ios.bundle?platform=ios&dev=true:10465:12)
    at http://<IP_ADDRESS>:8081/index.ios.bundle?platform=ios&dev=true:10473:1
    at tryCallOne (http://<IP_ADDRESS>:8081/index.ios.bundle?platform=ios&dev=true:6407:8)

How can I fix this? I'm doing a server request inside a try catch block. Everything is working fine. I'm not getting any errors from my server, only this yellow box appears.
Thank you a lot for this great framework!
albo1337

me too.....

Seems like the response was already processed
http://stackoverflow.com/questions/34786358/what-does-this-error-mean-uncaught-typeerror-already-read

Yep, that error happens when body has been already consumed, with e.g. res.json() call.

Hi there, I have something similiar happening with my app, and it's pretty strange: infact, if I make a request to a Json file for https://en.wikiquote.org/w/api.php?format=json&action=query&list=search&srsearch=wikipedia&srwhat=text&srprop=timestamp&prop=info, it works great, but if I made the same request for the identical file on my website (http://gabrieleventuri.it/pog/getFlow.json), it doens't work and gives me several errors, as below:

This is my code:
’’’javascript
getPostsFromApi() {
var ds = new ListView.DataSource({rowHasChanged: (r1, r2) => r1 != r2})
fetch("http://gabrieleventuri.it/pog/getFlow.json")
 .then((response) => response.json())
 .catch((error) => console.warn("fetch error:", error))
 .then((response) => {
   this.setState({
     pogDataSource: ds.cloneWithRows(response.query.search)}
   )}
 )

}
componentDidMount(){
this.getPostsFromApi()
}
’’’
Can anyone help me? Thank you very much

@gventuri try debugging by removing the this.setState and do a console.log(response) instead. What does that give you? From the error message, it doesn't look like you're getting the json object back.

Yes, it is actually undefined, but I don't understand why. Also, it runs the getPostsFromApi() twice, but again, I don't understand why...

You also need to return response.json()

Ok, now my getPostsFromApi() looks like this
getPostsFromApi() {
    var ds = new ListView.DataSource({rowHasChanged: (r1, r2) => r1 != r2})

    fetch("http://gabrieleventuri.it/pog/getFlow.json")
     .then((response) => response.json())
     .catch((error) => console.warn("fetch error:", error))
     .then((response) => {
       console.log(response)
       return response.json()
     }
     )
  }

and this is the console

`getPostsFromApi() {
var ds = new ListView.DataSource({rowHasChanged: (r1, r2) => r1 != r2})
fetch("http://gabrieleventuri.it/pog/getFlow.json")
 .then((response) => return response.json())
 .catch((error) => console.warn("fetch error:", error))
 .then((response) => {
   console.log(response)
 }
 )

}`
Maybe I should've been clearer, but I meant to put the return response.json() in the first .then

Might be related to this:
https://github.com/facebook/react-native/issues/4415

@jhack32: Thank you very much! Now it works great!

i'm also have this question

Note for future readers: this error also happens if you have throw Error(msg) in your code!

All code examples do not work when changing the .json file and fetching it from another website – for whatever reason I do not know.


refactor: Use nix::mount::mount and related types pervasively

nix is already pulled in so it seems like a good idea to use its mount
wrapper as well. Removes all unsafe from this crate.
BREAKING CHANGE
MsFlags is used over plain c_ulong in the public api

Hi!
Conceptually I'm okay with this. Didn't look at the code, I don't think there will be issues, though.
But I don't think I'm okay with pulling out MsFlags. The main issue is that nix has a breaking release very-very often. Even if upgrading is trivial it does send a wrong signal for the libmount users. I already have this issue in other libraries and it's very annoying.

Fair point, fixed.

Merged. Thank you!


Vim Chord and Vim Mode display freeze / stop working when switched to a new note, on another tab and after some time

Bug:
Vim Chord and Vim Mode display freezes and stops reacting to chords and mode state, when switched to a new note, on another tab and after some time

Since it ceases to work when the window changes I think there is something not working with "initializing" the display on the note workspace?
The only method I found to make it work again is to reset obsidian
To Reproduce:
Steps to reproduce the behavior:

leave Obsidian in reading mode for some time (I tested around 15min)
change a note in a tab (chords and display will stop working even when coming back to last note)
change the tab (chords and display won't work on the new tab, but will still work in the oryginal tab)

System info

OS: Windows 10
Vimrc plugin version: 0.8.0

Additional context:
I tested this on my main vault and on a fresh vault with stock settings and no other plugins.

@DonDon-9097 I have the same problem, did you solve it?

I missclicked, the bug is still up.
I'm not really a dev, so I haven't looked into this bug, it does annoy me, but I'd have to research a lot to understand why it doesn't work... since it stops working on a second tab, or after a longer incactivity I'd guess it's not liked as a process that shoud start on the tab start/re-focus.
I've spent a little bit of time looking around and I think it's a bug inside the code, not something in options/system.


Enable semantic-release

On hold until 1.x.x release-ready

:tada: This PR is included in version 0.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ValueError: SHA b'f697dc989970b..9' could not be resolved, git returned: b'f697dc989970b..9 missing'

Hi,
I am trying to use this package in github actions. But, I get the above error. I verified that the commit actually exists. May I know what am I missing here?

on:
  push:
    branches: [ main ]

jobs:
  Build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-python@v4
        with:
          python-version: 3.9
      - name: Install Python Poetry
        uses<EMAIL_ADDRESS>        with:
          poetry-version: 1.6.1
      - name: Configure poetry
        shell: bash
        run: python -m poetry config virtualenvs.in-project true
      - name: View poetry version
        run: poetry --version
      - name: Install dependencies
        run: |
          python -m poetry install

  Release:
    needs: Build
    # https://github.community/t/how-do-i-specify-job-dependency-running-in-another-workflow/16482
    if: github.event_name == 'push' && github.ref == 'refs/heads/main' && !contains(github.event.head_commit.message, 'chore(release):')
    runs-on: ubuntu-latest
    permissions:
      packages: write
      contents: write
      issues: write
      pull-requests: write
    steps:
      - uses: actions/setup-python@v4
        with:
          python-version: 3.9
      - name: Checkout code
        uses: actions/checkout@v3
      - name: Semantic Release
        run: |
          pip install python-semantic-release
          git config user.name github-actions
          git config user.email<EMAIL_ADDRESS>          semantic-release version --print
          ```

Hi
I just fixed this exact error by adding fetch-depth: 0 to the checkout action.

I am getting the same error using Gitlab CI. python-semantic-release just tries to resolve unknown random SHA


Headings inside tech switcher don't display in TOC

The docs tech switcher will currently only accept headings in HTML form, and not Markdown. These are then not added to the TOC due to a known issue with Gatsby and MDX.

I would double check if that is actually, fully true and it indeed does not accept Markdown headlines at all or if there were other reasons sometimes HTML was used instead.


Ra/js/collocation/2

Internal previews

📄 File
🔗 Preview link

aspnetcore/mvc/views/tag-helpers/built-in/samples/ScriptTagHelper/wwwroot/lib/jquery-validation/LICENSE.md
aspnetcore/mvc/views/tag-helpers/built-in/samples/ScriptTagHelper/wwwroot/lib/jquery-validation/LICENSE

aspnetcore/mvc/views/tag-helpers/built-in/script-tag-helper.md
Script Tag Helper in ASP.NET Core

aspnetcore/razor-pages/index.md
[Visual Studio](https://review.learn.microsoft.com/en-us/aspnet/core/razor-pages/index?branch=pr-en-us-33697)

@sliekens
Thanks for the contribution. Be sure to check out your name as a contributor about the 3rd of next month on the What's new page in the Community contributors section at the bottom.
Check out is:issue is:open label:"code help wanted" " and is:open is:issue label:"Good first issue" if you're interested it writing some code. We'll take care of the writing.


Add an optional aria-label to the nav element for screen readers

When including a TOC on a page, it can happen that this is not the only nav container on a page, with the main navigation possibly being at least one other. it would be good if the plugin would include a default name for the nav element, set via aria-label, and add an option to override this. So the nav would be:
nav aria-label="Table of contents" ...
...
</nav>

or the user provided alternative if they set it.
I am using Markdown-It-TOC-Done-Right in a new Eleventy project and found it the best TOC solution, with only this little bit missing.
Thank you for considering accessibility as one of the reasons why Markdown-It-TOC-Done-Right is the better choice over others! ❤

I love this plugin and the philosophy but this feels abandoned, need help @nagaozen ?

Sure, more arms are welcome


Export the NAMESPACE variable before using it

On the JupyterHub page, we start by telling folks to run this command:
kubectl get svc -n=${NAMESPACE}
But we haven't set the variable. By default, the deployment uses namespace "kubeflow", so we should set the variable to "kubeflow" before using it.
https://www.kubeflow.org/docs/guides/components/jupyter/
This issue was probably caused when we split the user guide into separate pages, and this page therefore assumes the variable has been set. We should check other pages for similar assumptions.

/good-first-issue
/starter
/area docs

Greetigns!
Can I work on it?


add remote soundcard volume control

Originally reported by: Menno van der Graaf (Bitbucket: mercotui, GitHub: mercotui)

A feature could be implemented where the Website could denote how loud the clients audiocard has to be set (using something like ALSA mixer). This technique was already used to set the volume, but was replaced by an pulse_audio based solution. Which frees it up for this use.
The benefit would be that you can easily equalize the volumes across different types of hardware.

Bitbucket: https://bitbucket.org/han_iot/dynamic-network-of-speakers/issue/8

The new audio library, as of commt 1de4d6ebbdb83d39b04f20d8c62881394f707cf6,  no longer overrides the clients volume, so this might not be very relevant anymore, as you can configre your client volume yourself (i.e. by calling asla by hand)


Lock repository to lts/fermium (node v14)

This PR resolves Repository update to Node v16 (or lock to Node v14) and locks the cwa-documentation repository to use Nodejs v14 (lts/fermium) as defined in https://nodejs.org/en/about/releases/ which is node v14.18.1 (with npm v6.14.15).
This keeps the cwa-documentation repository on the same node v14 version as used on the cwa-website repository, making it easier to work on both repositories from the same environment.

The change was successful. See
2021-11-26T13:00:35.7778321Z ##[group]Run actions/setup-node@v2
2021-11-26T13:00:35.7778812Z with:
2021-11-26T13:00:35.7779231Z   node-version: lts/fermium
2021-11-26T13:00:35.7779681Z   always-auth: false
2021-11-26T13:00:35.7780144Z   check-latest: false
2021-11-26T13:00:35.7786451Z   token: ***
2021-11-26T13:00:35.7786847Z ##[endgroup]
2021-11-26T13:00:35.9775167Z Attempt to resolve LTS alias from manifest...
2021-11-26T13:00:36.4020535Z Found in cache @ /opt/hostedtoolcache/node/14.18.1/x64

in the Action raw log file https://github.com/corona-warn-app/cwa-documentation/pull/764/checks.
Unfortunately there was a glitch in connectivity to https://www.coronawarn.app 🙁 .

Please retrigger the check action. I don't have privileges to do that.
The website https://www.coronawarn.app is running again.

Added name: key Setup Node.js environment (v14) to checks.yml for clearer action logging.

Setup Node.js environment (v14)
Run actions/setup-node@v2
  with:
    node-version: lts/fermium
    always-auth: false
    check-latest: false
    token: ***
Attempt to resolve LTS alias from manifest...
Found in cache @ /opt/hostedtoolcache/node/14.18.1/x64

Updated INSTALL.md to include instructions about which Node.js version to use locally for compatibility with this repository.

"This repository is aligned to the Node.js 14 Maintenance LTS version of Node.js (which includes npm). Install the v14 (lts/fremium) version of Node.js which is available from Node.js - Previous Releases page."

@dsarkar
This PR should now be merged.
ubuntu-latest migrated this morning to:
Virtual Environment
  Environment: ubuntu-20.04
  Version: 20211129.1
  Included Software: https://github.com/actions/virtual-environments/blob/ubuntu20/20211129.1/images/linux/Ubuntu2004-README.md
  Image Release: https://github.com/actions/virtual-environments/releases/tag/ubuntu20%2F20211129.1

so now in the cwa-documentation repository, every time .github/workflows/checks.yml runs it hits the v14 version package-lock.json and processes it with node v16:
Run npm install
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...

Although the message says "This is a one-time fix-up" this is not true for this environment because it does not save the results and therefore does the same fix up every time.
At the moment this is just a cosmetic issue, since .github/workflows/checks.yml does succeed. See for example the log from a test PR on https://github.com/corona-warn-app/cwa-documentation/actions/runs/1529989946.
This may however fail some time in the future as it is an unpredictable configuration. It would be better to lock to node v14 by merging this PR.
(Note: This is different to the cwa-website situation which is using a container. I will comment on this situation later on.)

@MikeMcC399 Thanks, we check this today.

👍


[Question] Codeblock highlight for Javascript Browser preview

First of all - I love this plugin. The highlighting of my current active block is helping me a lot in visibility and clearness!
After playing around, I wondered if there is an extension existing that does the same as yours only in the preview browser:

Do you know something like that?
PS: Would you like to activate sponsoring for this GitHub project? Then I can send you some ❤

In the preview, isn't that already very easy?
like this:
This css style will create boxes for all elements.
body * {
  outline: 2px solid rgba(0, 0, 200, 0.3);
}

Or maybe I did not understand the question?

Your Update describe it pretty well :)

Well, this new idea seems really cool and original. I am interested in seeing it in action. Though, I think it's very beyond my skills to plan and implement such feature. Maybe I will be able to do it if I have enough time to research/learn and do some experiments, but my time is very limited currently, so maybe some other developers will pick up this idea and consider implementing it.

At least I can say one possible way to do it (And it kinda seems that it's not so far from my skills, well, I'll think about it).
So, maybe, when developer focuses on a div (or li or button or any element) in the code, the extension should inject special id (or classname or custom attribute) in the div tag.
For example, we have this element:

hello

After focus, the extension should inject special identifier (id or custom attribute, let's do custom attribute):

hello

And of course we should have a global style like this:
[data-isfocused="true"] {
  outline: 2px solid rgba(0, 0, 200, 0.3);
}


Added the 'spo homesite set' command solving #1001

Added the 'spo homesite set' command solving #1001

Coverage remained the same at 100.0% when pulling cb37cbcdd9722537cc215d715ae4209788e89c8e on waldekmastykarz:spo-homesite-set into 8a81ecdcf004ff502a3083b4efc27d46387d0cf6 on pnp:dev.

Merged manually.


Support Kotlin 1.9.10

It is already supported with Compose Compiler 1.5.2-beta01:
compose {
    kotlinCompilerPlugin.set("1.5.2-beta01")
}

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


bumped Go from 1.13.x to 1.17.x in the hopes of fixing CI

I are hoping that this change - namely, to bump Go from version 1.13.x to 1.17.x - will fix CI without having to exclude OSX

Checklist

[ ] make test-all (UNIX) passes. CI will also test this
[ ] unit and/or integration tests are included (if applicable)
[ ] documentation is changed or added (if applicable)

Description of change

I believe the only thing you're running into here is changes to the conditional build directives in 1.17.  If you go through resource/resource_list_genny.go, the system/* files and util/command_windows.go and update those directives that should work.
Just replace:
// +build linux darwin !windows
with:
//go:build linux || darwin || !windows
and you should be good to go.  With those changes and a go mod tidy the build seems to work well for me locally under 1.17.6.


Is there any solution to create a custom map without using RoadRunner

I want to create some custom maps from the OpenStreetMap. But I don't have the license of using RoadRunner. So is there any other way to create the map info and convert to the Autoware map format?

Hi @ghostsun89
Create a custom map from OpenStreetMap, I don't think you can. Although, you can use the OpenStreetMap to create it in CARLA. You can select an area and CARLA turns it into a map. This is the link.
https://carla.readthedocs.io/en/0.9.13/tuto_G_openstreetmap/#generate-maps-with-openstreetmap


Question: is it possible to see the code of a lambda function that is being deployed for a given policy?

Hi Guys,
As per the subject.
I can think of at least 2 cases why this can be good

to stop guessing which actions I need to add to the Lambda policy
to be able to deploy and lifecycle-manage resulting lambda(s) with my existing CI/CD tools.

Thanks and regards,
Victor.

custodian is basically deploying itself as the lambda, along with the policy in question. you can use standard lambda api/cli to download the function code and examine aws lambda get-function.
the policy execution is isomorphic to the execution mode, so a) is handled by just running the policy out of lambda and authoring it to taste (actions, filters, etc). b) lifecycle is handled by invoking custodian from existing ci/cd tools to validate the policy and deploy/update the lambda.
could clarify the goal here re integration existing ci/cd tools?

Thanks for the get-function tip, @kapilt!
Re integration with the existing ci/cd tools - say, we are using Jenkins/CloudFormation. Until custodian has an ability to delete Lambda's we could've used CloudFormation to provision/update/delete them.

we distribute tools/ops/mugc.py for the purpose of deleting custodian policy lambdas no longer extant in config files if that helps.

Thanks @kapilt , I'll give mugc a go.


enh: call voice input sensitivity

It seems when you're using the new call feature when it's speaking (tts) it's hearing itself as if you're talking to it. Which results in it cutting off the tts after a word or 2. Only happens when i'm using it like a speaker phone. If I have my headphones in it works great since it doesn't hear itself talking. I think you need to put in a way to prevent it from listening UNTIL it's done talking, then it can resume listening again. Otherwise the the new call feature works great, just this one bug so far.

It seems when you're using the new call feature when it's speaking (tts) it's hearing itself as if you're talking to it. Which results in it cutting off the tts after a word or 2. Only happens when i'm using it like a speaker phone. If I have my headphones in it works great since it doesn't hear itself talking. I think you need to put in a way to prevent it from listening UNTIL it's done talking, then it can resume listening again. Otherwise the call feature works great, just this one bug so far.

Sorry I can't answer your question, but wondering if there is a trick so playback work.
I can engage in conversation with the model via the new call feature, it hears me fine, but I do not hear any response, but when I end I see the text response.

There are many ways to address that, but the easiest is using a programmable keyboard, "push key," to talk and release it to get the answer while muting the microphone. This is not the perfect scenario because we have to use our hands :) I agree with @hsman2, but I'm not sure about the complexity of coding that, as we would need to get the "end of audio" callback

I'm getting this bug also (MBP). Agree with either holding the mic button or controlling the mic sensitivity.

Updated with the latest!


Col data

@Rashmil-1999 feel free to ignore this PR. As I mentioned on Slack to Dhruv, I'm cleaning up this code and going through a refactor right now.

Ohh, okay.


Feature/import with tags through admin panel

Description
Added a key to differentiate when creating an idea is used with the import functionality on the react-admin panel, If it is, check the tagnames given, create the tag for the given siteId if it does not yet exist and set the relation between the idea and the tag.

I wrote my view on how this should work as code; maybe that is more comprehensible: Amsterdam@7621acf

Looks good except for that it now seems to return an array of tagObjects instead of tagIds, that while line 363 indicates that setTags expects an array of ids. If that is changed to return a list of ids then i think we can use https://github.com/Amsterdam/openstad-api/commit/7621acf1b39a26ea2404abbc8eb0f466cbabede0 instead of this branch

Closed the PR because of an alternative PR made by Niels https://github.com/openstad/openstad-api/pull/280 that offers a more robust and extensive solution


⚠ Mobitopup has degraded performance

In df2c9d5, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 3295 ms

Resolved: Mobitopup performance has improved in 36c476f after 5 minutes.


Various tweaks and improvements

Various fixes and improvements towards the Devito roofline plots. In detail:

New logger and sanity check for data loads
Use GFlops/s for roofline plots
Better axis value scaling and explicit type override for plotting axis values
Include the core anchor points of the roofline in axis range calculations
Tweak the point annotations in the roofline plots

I think this makes sense although I m not very good at interpreting plotting tweaks  :-)
Good to go!


Add gradient filter for tdnn_lstm_ctc

This PR adds the gradient filter for tdnn_lstm_ctc recipe. You could see https://github.com/k2-fsa/icefall/pull/564 for details.

@huangruizhe you can see whether this resolves your problem.

It will be hard to diagnose what's really going on here without looking at the diagnostics files (obtained by starting from intermediate epochs and adding the flag --print-diagnostics=True.. should take about 5 minutes).

This recipe does not support using flag --print-diagnostics=True.

Ruizhe can figure out how to add the code from other recipes, and make a PR.


Feature auth middleware

Description
Adjusts Urql fetchOptions middleware to accept a 'type' string and hand it off to the server for authentication and authorization services
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Change Status

[x] Incomplete/work-in-progress, PR is for discussion/feedback

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My code has been reviewed by at least one peer
[x] I have commented my code, particularly in hard-to-understand areas
[x] There are no merge conflicts

Creating this pull request for myself, small changes were made just to add a new return value to the utils that were passing the token off to the server-side through urql.


ci: use v6 version gh actions for all steps in stg

Will close this one as we moved the tls on wildcard , because of limitation in lets encrypt.
No issues for the apps.


fixed CrateDB-to-PG type mapping for field type object_array

Fields of type object_array have been returned with the OID = 144 (same as object) which should be OID = 199 (same as for geo_shape field type). I'm a bit unsure if this fix will affect a certain edge case for our JDBC driver. This commit added the mapping previously. @mfussenegger what do you mean?
cr> select * from pg_catalog.pg_type where oid in (199, 114);
+-----+----------+---------+---------+
| oid | typdelim | typelem | typname |
+-----+----------+---------+---------+
| 199 | ,        |     114 | _json   |
| 114 | ,        |       0 | json    |
+-----+----------+---------+---------+

I think the travis failures might be related to the change. You've to be careful there. JDBC is only enabled 50% of the time in the tests - so you'll need a couple of test runs to make sure this doesn't break anything. (And I think it does - but I don't remember why we choose to stream it as non-array)

@mfussenegger travis fails because of an additional NoNodeAvailableException. Strange, because I've repeated this tests now > 100 times and nothing fails. Will try to run some crate-jdbc tests to get further progress here.

Closing this as it seems that this change isn't necessary.


Change uses of class(x) == y to is(x, y)

Closed by https://github.com/NCEAS/arcticdatautils/pull/42  Thanks @ThomasThelen!


Context extensions

Bloc has watch, read and select extensions on the BuildContext. I was thinking about readForm, watchForm, watchField, readField where watch/readField would return a class:
class SuperFormFieldDataAndForm {
  SuperFormFieldData? data;
  SuperFormState form;
}

The question is: should these be like ofMaybe so they don't crash when form is not found?

Currently we have
SuperForm.of - SuperForm must be present, updated every time except when listen: false
SuperForm.ofMaybe - SuperForm may be present, updated every time, expect when listen: false
SuperForm.ofField - SuperForm must be present, updated on field change
SuperForm.ofFieldMaybe - SuperForm may be present, updated on field change
SuperForm.ofFieldValue - SuperForm may be present, updated on field and returns field value directly

That's quite a lot, but the API is more obvious than Provider with nullable type.
Working with flutter_bloc, having to manually import it since VS Code can't figure out extensions yet is pretty demanding. Since Flutter is preferring static of instead of context extensions, like MediaQuery.of, Theme.of I think the current solution is OK and quite non-opinionated, which I like.
Closing, but if you have idea or reason do it anyway - please let me know.


Create Offers REST API endpoint

Description:
We are decided to start implementing frontend in Angular 2+ and to do so we should have all objects in our system served in REST API.
This task is limited only to offers, rest of object will be moved in separate issues.
Current behaviour:
No REST API available.
Expected behaviour:
Full REST API (with tests available).

Seems to work as expected. I ran the unit tests and verified API calls for /organizations and /offers.


fix calibre 7.0.0

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Parent issue: #133004
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

2024-01-19T17:09:57.6148401Z ##[section]Starting: 🛡 Guardian: AntiMalware Scanner (Source)
2024-01-19T17:09:57.6268671Z ==============================================================================
2024-01-19T17:09:57.6269146Z Task         : AntiMalware Scanner
2024-01-19T17:09:57.6269543Z Description  : Run AntiMalware / Windows Defender
2024-01-19T17:09:57.6269932Z Version      : 4.212.0
2024-01-19T17:09:57.6270253Z Author       : Microsoft Corporation
2024-01-19T17:09:57.6270590Z Help         : AntiMalware build task must be run on a build agent with Windows Defender already installed.SecDevTools Extension Docs
2024-01-19T17:09:57.6271192Z ==============================================================================
2024-01-19T17:09:58.0978187Z Installing Guardian version: Latest
2024-01-19T17:09:59.6998513Z Installed Microsoft.Guardian.Cli.win-x64 version 0.195.0

(Automated response - build 609.)


Error when push data through api

org.apache.druid.java.util.common.ISE: Failed to get locks for intervals[[2021-03-01T00:00:00.000Z
How can I solve the problem ?

I got the same problem. I submit multiple tasks that will update similar timestamps maybe that is causing this problem but shouldnt druid must handle this?

How did you fix the issue?

if you are using the latest version and your tasks are appending the data to an interval, you can set useSharedLock to true in the task context. That way, appending tasks won't compete for the lock for the same interval.

I did try to implement using multiple retry.


Add support for nested directories, fix deprecated methods, add hierarchical tags

Sorry this is a shit PR but ive added the abillity to create the deck from a nested directory, where each card gets a tag to signify what directory its from, the user can seperate the decks out easily using those hierarchical tags, and the old functionality of making one directory into a deck still works (and the tags are voluntary)
It also includes a smaller commit that just uses the new renamed methods which does make the addon faster since it no longer spams the console for every added image when generating the deck

Hi @saygo-png, thanks for your contributions!
I did some testing, and the importing performance improved by almost 50% on my machine. Nice job.
It seems like the new methods in c1f824c raise the minimum supported Anki version to 2.1.50. This is fine by me, as 2.1.50 was released three years ago.
I will release an updated version of Media Import 2 soon.


6.3: In the generator definition, the simpler range() can be used instead of np.arange()

rows = np.arange(i, min(i + batch_size, max_index))
#can be replaced by the simper
rows = range(i, min(i + batch_size, max_index))

can you time to see if there's any performance difference?

I'm using different (much higher dimensional) data, and I see no significant speed difference in a loop of several generator calls.


MAHOUT-1990 Add Multilayer Perceptron

Purpose of PR:
Implements multi-layer perceptron style neural network
Also introduces some SGD functionality (namely learning strategies) (will, doesn't yet)
Also introduces classifier trait
Important ToDos
Please mark each with an "x"

[x] A JIRA ticket exists (if not, please create this first)[https://issues.apache.org/jira/browse/ZEPPELIN/]
[x] Title of PR is "MAHOUT-XXXX Brief Description of Changes" where XXXX is the JIRA number.
[ ] Created unit tests where appropriate
[ ] Added licenses correct on newly added files
[x] Assigned JIRA to self
[ ] Added documentation in scala docs/java docs, and to website
[ ] Successfully built and ran all unit tests, verified that all tests pass locally.

Does this change break earlier versions?
yes refactored linear regression to new sub-package, and created nonlinear package.
Is this the beginning of a larger project for which a feature branch should be made?
... possibly, but I think I will have it all working in short enough order that it can stay on mine- however I am open to this idea if someone else wants to chip in.

closing this, but will leave branch in case anyone is interested.

Is this just waiting for review?


Fails to discover two ARK_RTK_GPS on CAN1 (Ardupilot)

Setup
CubeOrange running Ardupilot (main) with two ARK_RTK_GPS on CAN1 running AP_Periph or PX4-cannode.
Issue
The dronecan_gui_tool fails to detect any nodes when there are two ARK RTK devices connected on CAN1. It can correctly detect each one individually, but fails when there are 2. This is the case for both AP_Periph firmware and PX4-cannode.
Screenshots
Here are screenshots of the node properties from each node when they are connected individually. Everything works correctly when only 1 node is connected at a time.

Termination resistor was not enabled. Whoopsie!


CSP nonce from middleware

Nonce doesn't applied to nextjs internal scripts. It blocks scripts when you use strict-dynamic inside script-src directive.
Found line where next injects nonce under the hood
https://github.com/vercel/next.js/blob/0fe68736ceca1f69fa2f082bef094b716e8a15b1/packages/next/src/server/app-render/app-render.tsx#L830
Will try to investigate

You need to add the content-security-policy to the request headers as well inside middleware. Related https://github.com/sst/open-next/issues/360