Refactor/function parameters

AssertElementPresent(), AssertTextPresent(), getInnerText(), getNumberInString() all now accept an object {selector, type} as parameters, to accommodate the new way we are creating new selectors
AssertAllElementPresent() was removed since it was used only once, and was replaced by two uses of AssertElementPresent()
done() was removed from the test since a new update in jest makes it unnecessary.

I don't know what's that with the comments file, and why is formatted like that. Can we resolve it here in the PR?

I thought @juampibermani fixed that in the original PR. Maybe you need to update the branch?

@katspaugh @juampibermani @francovenica there were some conflicts because we were still working in develop branch while new test comments were only added to main branch. We synced, solved the conflicts and we are ready to transition to only main branch workflow


glossary-updates

Review glossary page and provide updates on terminology.

https://github.com/Y-Foundry-Dao/yfd-docs/pull/59#event-8031742804


fixed the issue #4660 - shouldn't use a hook like function name for a variable

changed the name of the variable from hook like function name  to normal variable name.

@Kaku-g thanks for the contribution, but I don't think it's relevant issue for now.

@sneridagh It was in response to an issue Tiberiu opened -- should we close #4660 as well?

@davisagli Uh, I missed that Tiberiu was asking for it... in that case, let's consider it again.

@sneridagh done the requested changes!


[Enhancement] : Tic Tac Toe Ui Changed

Description

In this Tic_Tac_Toe game completely changed the Ui.

Fixes:  #1119

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] I have made this from my own
[ ] I have taken help from some online resourses
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK
Screencast from 2024-06-07 08-21-09.webm

Hello @Sulagna-Dutta-Roy , I will finished it please merge it..


Manually deleting an env

Which Category is your question related to?
env
Amplify CLI Version
4.13.3
What AWS Services are you utilizing?
api, auth, function
Is there a way to manually delete an amplify backend?
I've got a mangled environment that I've been trying to drop, however whenever I run it, it throws an error and keeps spinning (it spun overnight)
PS C:\Users\clay\Documents\Projects\oldmanhoops> amplify env remove dev
? Are you sure you want to continue? (This would delete all the environments of the project from the cloud and wipe out all the local amplify resource files) Yes
- Deleting resources from the cloud. This may take a few minutes...
Deleting env:dev
| Deleting resources from the cloud. This may take a few minutes...(node:4868) UnhandledPromiseRejectionWarning: NoSuchKey: The specified key does not exist.
    at Request.extractError (C:\Users\clay\AppData\Roaming\nvm\v12.2.0\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\services\s3.js:816:35)
    at Request.callListeners (C:\Users\clay\AppData\Roaming\nvm\v12.2.0\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\sequential_executor.js:106:20)
    at Request.emit (C:\Users\clay\AppData\Roaming\nvm\v12.2.0\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\sequential_executor.js:78:10)
    at Request.emit (C:\Users\clay\AppData\Roaming\nvm\v12.2.0\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\request.js:683:14)
    at Request.transition (C:\Users\clay\AppData\Roaming\nvm\v12.2.0\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\request.js:22:10)
    at AcceptorStateMachine.runTo (C:\Users\clay\AppData\Roaming\nvm\v12.2.0\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\state_machine.js:14:12)
    at C:\Users\clay\AppData\Roaming\nvm\v12.2.0\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\state_machine.js:26:10
    at Request.<anonymous> (C:\Users\clay\AppData\Roaming\nvm\v12.2.0\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\request.js:38:9)
    at Request.<anonymous> (C:\Users\clay\AppData\Roaming\nvm\v12.2.0\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\request.js:685:12)
    at Request.callListeners (C:\Users\clay\AppData\Roaming\nvm\v12.2.0\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\sequential_executor.js:116:18)
(node:4868) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:4868) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I can delete the vast majority of individual resources and remove the entry for the env in team-provider-info.json, but I can't seem to get rid of the backend. The "delete" button in the amplify console just tells me to run the CLI command that fails.
If you have any recommendations, it would be appreciated!

@claym Did you manually delete the S3 deployment bucket?

No, i didn’t manually delete anything , except for a dynamo table, which may have started this whole nonsense
It’s deleted cloud formation stacks, cognito pools, and IAM roles though.
I’ve tried creating empty replacement of the stack and roles, but no dice.

I'm in a similar situation except (perhaps due to this fix) I get
multi-environment support is not available for Amplify projects with Mobile Hub migrated resources.
(this is when I try to run amplify env remove kaputenv)
Meanwhile, I am not using or referencing any Mobile Hub resources, migrated or otherwise. This will be the second time in less than two weeks that I will have had to rebuild my Amplify configuration and amazingly enough neither time was my fault (phew!). This stuff has to get more stable. It needs to move past errors or have an option to blow things away.

Well, this worked really well! AWS CLI v1.18 (not supported in 1.16 and not in 2.x)
aws amplify delete-backend-environment --app-id your-app-id-here --environment-name kaputenv
App ID is that alphanumeric string found in amplify/team-provider-info.json under { "any-environment": { "awscloudformation": { "AmplifyAppId".
AWS CLI to the rescue. Just make sure to find a version that supports it, like 1.18.

@rt-demetri does your project have any Mobile Hub created resources or did this message just show up out of the blue?

@rt-demetri does your project have any Mobile Hub created resources or did this message just show up out of the blue?

The project does not, to my knowledge (and I have created it twice) so this is out of the blue for us. I have Hosting (amplifyhosting), Auth (Cognito), Storage (DynamoDB), Function (a custom lambda behind API Gateway), and Api (REST, that calls the lambda). I wondered if the Amplify CLI was misperceiving one of these as Mobile Hub-related but this didn't happen prior to another person manually deleting a test environment in the console. I was previously able to enumerate the environments just fine. Now any environment-specific command returns the above error. So I fixed the hanging environment issue but the error persists.
Thanks for inquiring further!

@rt-demetri does your project have any Mobile Hub created resources or did this message just show up out of the blue?

Help is on the way! https://github.com/aws-amplify/amplify-cli/issues/5520


Retraining a trained model with ludwig==<IP_ADDRESS> results into key errors.

Describe the bug
Retraining a trained model with ludwig==<IP_ADDRESS> results into key errors. Downgrading to ludwig==0.2.2 solved the problem
File "/usr/local/lib/python3.6/site-packages/ludwig/models/model.py", line 442, in train
[of['name'] for of in output_features] + ['combined']
ValueError: The specificed validation_field combined is not valid.Available ones are: ['class', 'combined']
To Reproduce
Steps to reproduce the behavior:

Train a simple default model
Save the model
Load the model with the python api
Train the model
Receive error

Error occurs even when following the basic yaml files and tutorial on the Ludwig Examples.
Expected behavior
When training the model it should not result in key-error for.
Environment (please complete the following information):

OS: Ubuntu
Version 19.10
Python version 3.7.1
Ludwig version <IP_ADDRESS>

Additional context
Add any other context about the problem here.

Already solved by the last commit: https://github.com/uber/ludwig/commit/49648aac505f5d6b584aabec531c254d27ec5e8e
You can install from master but there will be a <IP_ADDRESS> release incorporating it soon.

Here's the link to the new release that fixes the problem: https://github.com/uber/ludwig/releases/tag/v<IP_ADDRESS>
it's also already on Pypi ;)


Update Couchbase Exporter to the official exporter

This updates the couchbase exporter from a community exporter with last update from 2019 to the official Couchbase exporter.

:+1: Thanks!


To add multi-arch support for compliacen-operator images

As part of the security work for OCP, we need Compliance operator to be get supported for Power, for that we are planning to have all images as Multi-arch supported.
As per our understanding there are Four images which required for deployment of compliance-operator and also they should be multi-arch supported,
Below is list for the same.

Compliance-operator
Compliance-operator-index
openscap-ocp
Compliance-operator-bundle

We are already worked on Compliance-operator, openscap-ocp images using Github action and those are multi-arch supported, and we have tested them.
For getting multi-arch support for compliance-operator, openscap-ocp images can we raise PR as we have tested them.
Note: For Compliance-operator-index image which is depending on Compliance-operator-bundle, as Compliance-operator-index is not having any docker file. So how would you suggest to have multi-arch support?

For getting multi-arch support for compliance-operator, openscap-ocp images can we raise PR as we have tested them.

Sure, go ahead.

Note: For Compliance-operator-index image which is depending on Compliance-operator-bundle, as Compliance-operator-index > is not having any docker file. So how would you suggest to have multi-arch support?

For testing (see the index-image: target and the opm: target in the Makefile) we build an index using opm. Looking at https://github.com/operator-framework/operator-registry/releases it looks like opm supports also ppc64le and s390x, would that help?
You should maybe note PR #41 that will restructure the Makefile quite a bit. I'm not sure how much your PR would depend on Makefile, but if it does a lot, you might want to check the new targets there.

As per discussed we have raised PR for compliance operator and content images below are the link for the same:
PR link for compliance-opeartor repo:
https://github.com/ComplianceAsCode/compliance-operator/pull/80
PR link for content repo:
https://github.com/ComplianceAsCode/content/pull/9330

As part of the security work for OCP, we need Compliance operator to be get supported for Power, for that we are planning to have all images as Multi-arch supported.
As per our understanding there are Four images which required for deployment of compliance-operator and also they should be multi-arch supported,
Below is list for the same.

Compliance-operator
Compliance-operator-index
openscap-ocp
Compliance-operator-bundle

We are already working on Compliance-operator, openscap-ocp and content images using Github action and those are multi-arch supported, and we have tested them.
PR links for above images:
Compliance-operator : https://github.com/ComplianceAsCode/compliance-operator/pull/83
openscap-ocp: https://github.com/ComplianceAsCode/compliance-operator/pull/83
content: https://github.com/ComplianceAsCode/content/pull/9330
For Compliance-operator-index image as we do not have dockerfile which can be required for github action to give multi-arch support for compliance-operator-index image.
We are having below Approach:

We need to update clusterserviceversion yaml files with updated multi-arch images (because Currently the images present in clusterserviceversion yaml files are not multi-arch and has only amd64 support)
After updating csv files we need to build bundle image.
Using newly built bundle image, we can create index.Dockerfile by providing --generate option to opm index command in Makefile.
After generating the index.Dockerfile which can be used to build index image, we can then build multi-arch index image using github action.

Example for building index image in github action:
- name: Build index image for ppc64le
        uses: redhat-actions/buildah-build@v2
        with:
          image: ${{ env.IMAGE_NAME }}
          tags: ${{ env.IMAGE_TAG }}-linux-ppc64le
          arch: ppc64le
          containerfiles: |
            ./index.Dockerfile

We have already tested this and it is working fine.
Please let us know can we raise PR for index image as per above approach?

Hi Team,
As per drafted in below image, currently the images are pushed to different repositories.

For installing and testing CO through CLI, images are pushed to Quay.io
For installing and testing CO through web console, images are pushed to RedHat registry.
For internal testing, images are pushed to ghcr.io

Hence could you please confirm the location where we need to push/pull images for compliance operator?

Hi Team,
As per drafted in below image, currently the images are pushed to different repositories.
1. For installing and testing CO through CLI, images are pushed to [Quay.io](http://quay.io/%5D(https://quay.io/repository/compliance-operator/compliance-operator?tab=info))

Upstream releases are pushed to quay.

2. For installing and testing CO through web console, images are pushed to [RedHat registry](https://catalog.redhat.com/software/containers/compliance/openshift-compliance-rhel8-operator/607dc35087c834779d776118).

This is not entirely correct, the RH registry is what is built internally in RH's buildsystem. The installation method is not as relevant as using different base images and the whole pipeline that includes security scanning etc. These are also the only images that are supported, documented and go through QE.

3. For internal testing, images are pushed to [ghcr.io](http://ghcr.io/)

IIRC, ghcr is what's used for images built after every pull request with GH actions.

Hence could you please confirm the location where we need to push/pull images for compliance operator?

Hi Team,
We are adding approach for multi-arch index support using github action:
We are already working on Compliance-operator, openscap-ocp and content images using Github action and those are multi-arch supported, and we have tested them. PR links for above images: Compliance-operator : #83 openscap-ocp: #83 content: ComplianceAsCode/content#9330
For Compliance-operator-index image as we do not have dockerfile which can be required for github action to give multi-arch support for compliance-operator-index image.
We are having below Approach:

We need to update clusterserviceversion yaml files with updated multi-arch images (because Currently the images present in clusterserviceversion yaml files are not multi-arch and has only amd64 support)
After updating csv files we need to build bundle image.
Using newly built bundle image, we can create index.Dockerfile by providing --generate option to opm index command in Makefile.
After generating the index.Dockerfile which can be used to build index image, we can then build multi-arch index image using github action.

Example for building index image in github action:
- name: Build index image for ppc64le

Just to clarify, you should not need to build an index for each architecture, instead you would build one index that points to your bundle, and that bundle contains the manifest list reference that was pushed as part of the build actions.

    uses: redhat-actions/buildah-build@v2
    with:
      image: ${{ env.IMAGE_NAME }}
      tags: ${{ env.IMAGE_TAG }}-linux-ppc64le
      arch: ppc64le
      containerfiles: |
        ./index.Dockerfile

We have already tested this and it is working fine.

Please let us know can we raise PR for index image as per above approach?

Note that we are currently finishing a big overhaul of the Makefile in #41 . Part of the changes will be making it easier to create a bundle and index for specific images, so I would suggest waiting until that PR is committed.

Hi Team,
As per drafted in below image, currently the images are pushed to different repositories.

For installing and testing CO through CLI, images are pushed to Quay.io
For installing and testing CO through web console, images are pushed to RedHat registry.
For internal testing, images are pushed to ghcr.io

Hence could you please confirm the location where we need to push/pull images for compliance operator?

It is not multi-arch, it provides independent images for each arch.:

This is part of multi-arch. independent architecture builds are produced and included in a manifest list (this is what the proposed github actions do). Images are pulled by the manifest list SHA and that resolves the platform specific architecture.

Deploying works from Web Console

Note that when you deploy from the web console on an OCP install, it's pulling the architecture-relevant images that RH has published in the container catalog (we usually refer to these as downstream)

From CLI is does not work.

CLI install currently only references the quay.io images (these are more or less "convenience" images that a developer builds locally when creating a new version release). In PR #41 we have better support for deploying custom images from the source tree.

Weird Situation: Multiple Image Repositories

Like Jakub mentioned, this really comes down to what we can say about the support for each repo. Simply put:

Upstream quay.io images: convenience, operator testing (providing a working default deployment),
Downstream RH catalog: Supported by RH, QE tested, signed, etc.
gchr.io: For GH workflow auto-builds, since it includes signing.

Hi @jhrozek @mrogers950 Thanks for providing brief overview of image release process.
However could you please let us know how the image releasing process will work for the merged PR #83
Also please confirm if the images will be pushed to Quay.io for the new release and when should we expect that?

Hi @jhrozek @mrogers950 Thanks for providing brief overview of image release process. However could you please let us know how the image releasing process will work for the merged PR #83

Since the GH action should be triggered on pushing to the master branch (or the v* branches for the releases) we should know how they work when other commits are merged, currently that PR is the latest in the tree.

Also please confirm if the images will be pushed to Quay.io for the new release and when should we expect that?

I don't see anything in the GH action that would push to quay.
More generally -- can you explain why it matters? What is the intended use of the multiarch container images?
It can't be production use because these images don't go through QE, only the in-house built images that are released through the RH container reqistry are. Why is ghcr not suitable for testing and development?

@jhrozek :
Thanks for the response.
Actually our main concern was related to installing compliance operator through CLI.
Because as per our understanding, when we install compliance-operator through web console it uses images from RH registry which has support all arch including ppc64le,amd64 and s390x.
But when we try to install compliance operator through CLI, it pulls images from Quay.io registry which does not have xupport for ppc64le.
Following is the file which pulls images from Quay.io
https://github.com/ComplianceAsCode/compliance-operator/blob/master/deploy/operator.yaml
But when we raise PR the images are getting pushed to ghcr.io, thus the confusion happened.
Hence could you please let us know what we are supposed to do in case we need Quay.io images multi-arch in order to install CO through CLI.

@jhrozek :
Thanks for the response. Actually our main concern was related to installing compliance operator through CLI. Because as per our understanding, when we install compliance-operator through web console it uses images from RH registry which has support all arch including ppc64le,amd64 and s390x. But when we try to install compliance operator through CLI, it pulls images from Quay.io registry which does not have xupport for ppc64le. Following is the file which pulls images from Quay.io https://github.com/ComplianceAsCode/compliance-operator/blob/master/deploy/operator.yaml But when we raise PR the images are getting pushed to ghcr.io, thus the confusion happened. Hence could you please let us know what we are supposed to do in case we need Quay.io images multi-arch in order to install CO through CLI.

This is not the right way to install the official bits via CLI. This deploys the upstream bits, not through the OLM but by creating a Deployment directly, so you don't get upgrades etc. This method is really only useful for testing or anyone running a "community version". But not supported or endorsed by RH.
I thought we cleared up the confusion earlier in this ticket.
We have the procedure to install CO through the CLI documented in the RH docs. I haven't tested it on non-Intel, but I would hope it works.
HTH

Hi @jhrozek
We have tested CO installation using RH docs, and it is working fine on ppc64le.

On Fri, Aug 26, 2022 at 04:53:19AM -0700, Jakub Hrozek wrote:

@jhrozek :
Thanks for the response. Actually our main concern was related to installing compliance operator through CLI. Because as per our understanding, when we install compliance-operator through web console it uses images from RH registry which has support all arch including ppc64le,amd64 and s390x. But when we try to install compliance operator through CLI, it pulls images from Quay.io registry which does not have xupport for ppc64le. Following is the file which pulls images from Quay.io https://github.com/ComplianceAsCode/compliance-operator/blob/master/deploy/operator.yaml But when we raise PR the images are getting pushed to ghcr.io, thus the confusion happened. Hence could you please let us know what we are supposed to do in case we need Quay.io images multi-arch in order to install CO through CLI.

This is not the right way to install the official bits via CLI. This deploys the upstream bits, not through the OLM but by creating a Deployment directly, so you don't get upgrades etc. This method is really only useful for testing or anyone running a "community version". But not supported or endorsed by RH.
I thought we cleared up the confusion earlier in this ticket.
We have the procedure to install CO through the CLI documented in the RH docs. I haven't tested it on non-Intel, but I would hope it works.

Thank you for the confirmation!
Please let us know if the GH actions for the multi-arch images are still needed.

@aditijadhav38 @gauravpbankar FYI the Z build has come up with a failure in our latest release PR: https://github.com/ComplianceAsCode/compliance-operator/pull/125
We're not going to hold the PR for this failure, so it can be addressed in a separate PR afterwards.
From the latest discussion here it sounds like the downstream images satisfy your needs. Should we disable these jobs if you're not using the images built by them?

Hi @mrogers950 ,
Yes. As our downstream images are working with power as expected so we can disable this this jobs as we are getting issue with Z images.

Spoke to @mrogers950 about issue, and we agreed to remove the Jobs and rely on downstream to build the multiarch images.  @gauravpbankar please confirm

Dug into the issue
[Fail] Resultserver testing Raw result directory rotation [It] Rotates directories according to the rotation policy (3 directories with one lost+found and policy=2)
/go/src/github.com/openshift/compliance-operator/cmd/manager/resultserver_test.go:160

There is an implied wait when creating the directory and files in BeforeEach test using time.Sleep(100 * time.Millisecond).
When I added some logging to the test, I found:
2022/10/25 17:08:28 Directory /tmp/rotate-root4097677180/rotate-13713656550 2022-10-25 17:08:28 +0000 UTC
2022/10/25 17:08:28 Directory /tmp/rotate-root4097677180/rotate-22092874256 2022-10-25 17:08:28 +0000 UTC
2022/10/25 17:08:28 Directory /tmp/rotate-root4097677180/rotate-31859717235 2022-10-25 17:08:28 +0000 UTC
2022/10/25 17:08:28 Post-Sorted
2022/10/25 17:08:28 Directory /tmp/rotate-root4097677180/rotate-13713656550 2022-10-25 17:08:28 +0000 UTC
2022/10/25 17:08:28 Directory /tmp/rotate-root4097677180/rotate-22092874256 2022-10-25 17:08:28 +0000 UTC
2022/10/25 17:08:28 Directory /tmp/rotate-root4097677180/rotate-31859717235 2022-10-25 17:08:28 +0000 UTC
2022/10/25 17:08:29 Pre-Sorted
2022/10/25 17:08:29 Directory /tmp/rotate-root1711445415/rotate-12070323603 2022-10-25 17:08:28 +0000 UTC
2022/10/25 17:08:29 Directory /tmp/rotate-root1711445415/rotate-24065574402 2022-10-25 17:08:28 +0000 UTC
2022/10/25 17:08:29 Directory /tmp/rotate-root1711445415/rotate-31947875413 2022-10-25 17:08:28 +0000 UTC

time.go doesn’t have any os/arch specific calls, and this passes for amd64/ppc64le. I think this is result of the clock for qemu.  The clock doesn't seem to have ms precision.
Net: I think the right move is to remove it.

Hi Team,
We are closing this issue,  As we have already commented on the same below is the reference.
https://github.com/ComplianceAsCode/compliance-operator/issues/79#issuecomment-1290727572


Regenerated internal types to include ActivitiesToDispatchLocally

What changed?
Regenerated internal types to include ActivitiesToDispatchLocally

Why?
Previous version was generated using older version of thrift package, therefore was missing this field.

How did you test it?

Potential risks

Coverage increased (+0.006%) to 59.604% when pulling 78a662b59ab64d66144240fa15f685f308c4a78a on vytautas-karpavicius:activities-to-dispatch-locally into 2069ee4d8c50a73affc5fb86da43e14daf459e63 on uber:master.


bug(button-toggle): Accessibility breaks with matTooltip

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
When adding the tooltip on a button toggle, the screen reader loses the group detection.
Reproduction
StackBlitz link: https://stackblitz.com/edit/dh5vz6?file=src%2Fexample%2Fbutton-toggle-overview-example.ts,src%2Fexample%2Fbutton-toggle-overview-example.html
Steps to reproduce:

Use NVDA screen reader
Navigate with the browse mode

Expected Behavior
The second button toggle should be detected as a whole. Like the first button toggle.
Actual Behavior
When navigating on the second button toggle, the screen reader doesn't mention all the other buttons at once.
Environment

Angular: 16
CDK/Material: 16
Browser(s): Edge
Operating System (e.g. Windows, macOS, Ubuntu): Windows 11
Screen reader: NVDA

Hello @ice-blaze ,
We need more information. Thank you for reporting accessibility issues. Unfortunately, this issue may not be actionable without further information. Do you have an accessibility requirement that's not being meet or an explanation why it's a problem for the user? I don't think I understand what "the screen reader doesn't mention all the other buttons at once" means.
I cannot reproduce.

https://stackblitz.com/edit/5n2guz?file=src%2Fexample%2Fbutton-toggle-exclusive-example.html
NVDA 2<IP_ADDRESS>854
Chrome Version Version 121.0.6167.189 (Official Build) (64-bit)
Windows 10 Enterprise Version 22H2

-Zach

Couldn't try it right now on a windows machine but just by looking at your stackblitz, you are missing the import of the MatTooltipModule, which makes the tooltip not visible on your example.

Hello,
Good catch on that, yes, I added the missing MatTooltipModule 🤦 . I am able to test the demo on Windows machine with tooltip working. I have tested on NVDA, and I don't see anything wrong. I don't see anything that looks like an a11y criteria not being meet.

Expected Behavior
The second button toggle should be detected as a whole. Like the first button toggle.
Actual Behavior
When navigating on the second button toggle, the screen reader doesn't mention all the other buttons at once.

I don't think I understand what mentioning all the other buttons at once means or detected as a whole means :). The toggle buttons are native button elements, so I don't think there needs to be anything complicated with the a11y semantics. I don't think I see what requirement this test case is based on.

Chrome Version 122.0.6261.129 (Official Build) (64-bit)
NVDA version 2<IP_ADDRESS>265
Windows 10 Enterprise Version 22H2

Best Regards,
Zach

I could get my hands on a windows machine. So I adapted your examples just by duplicating your toggle and remove the tooltips. So when I'm on browse mode (using the arrows key up and down) we can see the output of NVDA is one line for each button.
In the second case there are no tooltips and NVDA change the behavior by mentioning the buttons all at once in one line.
out of frame  button    Close Preview
Preview page  frame    toggle button  not pressed    Text align left
toggle button  not pressed    Text align center
toggle button  not pressed    Text align right
toggle button  unavailable  not pressed    Text align justify
Selected value:
toggle button  not pressed    Text align left  toggle button  not pressed    Text align center  toggle button  not pressed    Text align right  toggle button  unavailable  not pressed    Text align justify
Current build: 17.2.1

Also for context, I'm only mentioning browse mode, not focus mode (the one when you navigate with tab). With focus mode, the cursor goes on each button in both cases (with and without tooltips).
I hope I was more clear here.

Edge version 122.0.2365.80
NVDA version 2022.1
Windows 11 Enterprise version 10.0.22621 build 22621


Update KaTeX to 0.10.0-beta

What does "beta" mean in this context? Is there a stable version we should be using instead?

Beta is just the pre-release. I chose to use 0.10.0-beta over 0.9.0 because the changeset for the 0.10.0 release is actually substantial, and has a lot of improvements to KaTeX. It shouldn't make any difference to most users that this is a beta release.
In any case, I can either:

Change the PR to 0.9.0
Commit to make a new PR when 0.10.0 gets released

What do you prefer?

I'd prefer to use 0.10, do you know when that might be released?
On Thu, Jul 26, 2018 at 7:10 PM Bernardo Meurer<EMAIL_ADDRESS>wrote:

Beta is just the pre-release https://github.com/Khan/KaTeX/releases. I
chose to use 0.10.0-beta over 0.9.0 because the changeset for the 0.10.0
release is actually substantial, and has a lot of improvements to KaTeX. It
shouldn't make any difference to most users that this is a beta release.
In any case, I can either:

Change the PR to 0.9.0
Commit to make a new PR when 0.10.0 gets released

What do you prefer?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/euclio/aurelius/pull/12#issuecomment-408262577, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABTxFuKsQXEgsE5q4WSJRfJvA6KNnSGXks5uKkyBgaJpZM4VfkEn
.

There is no ETA as far as I know, but my guess would be in 1-2 months?

Ok, I'll merge this now and we can update it again when it's released.

Cheers!


Spacing isn't correct

Different input fields have different sizes. Sizes aren't lining up with their containers.
Examples are DetailView and ModalCollectionList

Fixed


Implemented Concurrent Execution

Concurrent Execution

The AzureEvaluator, JudgeVMSS and JudgeVM all have a submitted_requests queue. Each spawns a worker thread upon initialization which checks the queue for new requests and assigns them to the right resource. The AzureEvaluator assigns it to a specific VMSS, the VMSS to a specific JudgeVM. Consequently, calling submit on any of these classes, adds it to the submitted_requests queue.
Addtion of dormant vm's: This feature was added to ensure that a request that creates new resources, also gets those resources first. When a new VM is created, a local JudgeVM is already created before the Azure VM is setup, but it is marked as dormant. The request that caused the creation of this new VM, is added to the local JudgeVM queue, and will be the first to execute. The JudgeVM worker thread, waits until it has a connection to the Azure VM.
Addition of timed removing: There is now an environment variable MAX_VM_IDLE_TIME. Only if a VM was not busy for that amount of time, will it be removed.
A lot of locks/conditions were added to prevent corruption of shared objects.

edit: also added functionality for cutelog logger since it's really nice and usable. on default it will not be used, only if you change the env variable USE_CUTELOG.

There's currently some bug with doing many requests at the same time. When making 10 requests at the same time, it should make 4 machines, each doing 3 requests (last doing only 1). However, it only makes 2 machines.


Update mockito-scala to 1.17.27

About this PR
📦 Updates org.mockito:mockito-scala from 1.17.12 to 1.17.27
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (1.17.12).
You might want to review and update them manually.
CHANGELOG.md

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.mockito", artifactId = "mockito-scala" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.mockito", artifactId = "mockito-scala" }
}]

labels: test-library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Superseded by #495.


Address attribution

Wash "I" => "we" through the content

Edited all the references I could find.


Path doesn't display when selected

I was using this asset for some months now, and when I started experimenting with rendering features it stopped displaying when I select a Path. The problem now is I can't get it to display again even if the rendering settings are back to default, however, the path does display when is not selected.

This is when the path is selected

Display options are enabled but it doesn't work

Fixed the problem!
There was an error when I was importing an fbx. For some reason, this error messed the Path Creator Editor Script and did not created the gizmo.
So, make sure not to get any errors or this might happen.


ADD A CURSOR EFFECT

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
its not a problem its more  of an enhancement
Describe the solution you'd like
A clear and concise description of what you want to happen.
i would like to add cursor effect when ever and where ever a cursor moves
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
there are other alternative animations which i could try out like the cursor tail effect, line or string follow effect, blurred tail effects etc.
Additional context
Add any other context or screenshots about the feature request here.
i thought it would be fun and interactive for the user and the user will know which way they are going through a fun cursor animation instead of a boring and normal one

@ANSHIKA-26 kindly assign this to me!


tqdm dependency

Hi, I had to install tqdm to get training to work. So maybe you can add it to requirement.txt

Done. Thanks.


Remove instance of ambassador.namespace in emissary helm chart

Issue #, if available:
Description of changes:
generated-emissary                 emissary                           3m7s   installing                                                                      3.9.1-55065bbc34a4bd3af2fddd18af272b037e876387 (latest)                     installing helm chart generated-emissary: template: emissary/templates/rbac.yaml:173:18: executing "emissary/templates/rbac.yaml" at <include "ambassador.namespace" .>: error calling include: template: no template "ambassador.namespace" associated with template "gotpl"

When testing emissary locally, saw this error when installing helm chart. Updating the patch to remove all instances of ambassador.namespace
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve

/lgtm


.mailmap example file, thanks to Ariel rich personality ;)

Excellent! Could you please add a short explanation in the readme?
On Sep 28, 2017 6:32 PM, "Yaroslav Halchenko"<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/uwescience/shablona/pull/74
Commit Summary

.mailmap file, thanks to Ariel rich personality ;)

File Changes

A .mailmap
https://github.com/uwescience/shablona/pull/74/files#diff-0 (3)

Patch Links:

https://github.com/uwescience/shablona/pull/74.patch
https://github.com/uwescience/shablona/pull/74.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/uwescience/shablona/pull/74, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHPNtRUfL2706FsYg--sjG9pt2Aq_eGks5snEiRgaJpZM4PoFxs
.

only for you and only today - done @arokem ;) Cheers!

Wonderful. I love getting preferential treatment.


[Inquiry: Total Number of Training Samples]

Hello,
Thank you for providing this excellent research. While using it for my experiments, I noticed that the total number of training samples is not explicitly mentioned in the dataset description.
Could you kindly let me know this detail?
Thank you for your consideration, and I look forward to your reply.
Best regards

Hi,
Thank you for your interest!
We use combination of Flickr2K images (2.65k) and LSIDR dataset (85k) as clean images along with 60k blur kernels synthetically generated for training the dataset. These large image datasets are necessary since diffusion models can be be very data intensive to train.
The arxiv version doesn't contain these details but we'll update them soon.
Thanks,
Yash Sanghvi

During training, we randomly sample from the clean image dataset and the blur kernel dataset and use create blurred iamges using the two. We train the diffusion network for 100k iterations, with a batch size of 8.


transforms.to_pil_image mishandles float type tensors that are not in range [0,1]

transforms.to_pil_image() internally multiplies single-channel float tensors with 255 and then converts them to byte type. That leads to unexpected results when the value range of the float tensor is not between 0 and 1.
The doc doesn't state that values should be in [0,1], and indeed states that the correct mode for transferring to PIL image will be chosen automatically by dtype.  PIL does have a mode for floats ("F"), but that doesn't get used.
I suggest adding a note about the required value range [0,1] to the docs, or not converting float tensors with values outside of [0,1] to byte type.
Here's some code:
import numpy as np
import torch
import torchvision.transforms as transforms
from PIL import Image
npimg = np.arange(9).reshape((3,3)) + 0.5
image_from_array = Image.fromarray(npimg)
tensor = torch.from_numpy(npimg).type(torch.float)
image_from_tensor = transforms.functional.to_pil_image(tensor)
print("Image from array: ", np.array(image_from_array))
print("Image from tensor: ", np.array(image_from_tensor))
Output:
Image from array:
[[0.5 1.5 2.5]
[3.5 4.5 5.5]
[6.5 7.5 8.5]]
Image from tensor:
[[127 126 125]
[124 123 122]
[121 120 119]]

I just realised that this issue was fixed by the latest commit 19 days ago (0c75d99d59bbc8e22e9dc40469c5b4ec1d742f03).


Error when loading app, but only when pinia tab in vue devtools is open on pinia tab

Reproduction
https://github.com/garfunkel/vue-pinia-devtools-bug
Steps to reproduce the bug

Start app in dev mode
Open vue devtools
Click on the pinia tab in devtools
hard refresh app page
See error traceback in browser console

Expected behavior
No error/traceback.
Actual behavior
In Firefox:
Uncaught (in promise) TypeError: U is null
In Chrome:
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'state')
Additional information
No response

Just found a recent issue on the devtools repo which may be related: https://github.com/vuejs/devtools/issues/707

Let’s keep it in devtools for the moment since the devtools code here hasn’t changed


A couple of clarifications on features and predictions.

I have successfully run the movielens examples but there are two questions that I cannot answer yet.
1-Why use timestamps instead of ratings as the features? It seems to me that a rating is a much better feature rather than a timestamp, although I understand that what a user has cheked out recently is relevant, i think that tha rating given to a movie is an even better (at least more intuitive) feature.
2-After i have run the examples, i have tried to predict recomendations for myself, so I created an input file with movies I like and run it, the results however are... almost always the same, example of an input file:
`
X1    1590,974820748:91231,974820776:
X2    71164,974820691:78316,974820943:7362,974820691:1762,974820943:
X3    5960,974820748:46808,974820889:47446,974820889:26349,974820748:57041,974820889:597,974820748:
X4    58332,974820720:4634,974820943:60338,974820720:79594,974820720:33072,974820776:87572,974820748:7098,974820943:91692,974820748:
X5    86544,974820943:5687,974820776:33679,974820889:48322,974820943:67087,974820691:7214,974820776:84508,974821014:8196,974820943:71748,974820776:7446,974820748:
`
The output is
`X1     858,0.922:1221,0.811:2959,0.630:2571,0.597:527,0.555:2023,0.501:6016,0.499:597,0.495:1193,0.484:110,0.481:
X2     858,0.918:1221,0.805:2959,0.623:2571,0.590:527,0.562:6016,0.504:597,0.500:2023,0.498:1193,0.486:110,0.479:
X3     858,0.924:1221,0.811:2959,0.633:2571,0.596:527,0.591:597,0.561:6016,0.516:2023,0.497:500,0.494:1193,0.494:
X4     858,0.919:1221,0.807:2959,0.620:2571,0.593:527,0.564:597,0.503:6016,0.503:2023,0.499:1193,0.487:110,0.479:
X5     858,0.912:1221,0.795:2959,0.628:2571,0.593:527,0.546:6016,0.522:597,0.509:2023,0.487:1193,0.470:4993,0.468:`
(Sorry, i did not manage that to get properly formatted)
As you can see, the recommendations are almost the same ones.
I have tried this with a number of different examples, and I never seem to be able to get something right, however, if I pass the neuronal network a traning example such as
8	1,833981871:3,833981733:6,833982631:10,833981834:19,833981918:21,833981710:39,833981963:47,833981896:48,833982197:110,833981870:150,833973081:153,833973175:161,833981804:165,833973175:168,833982178:172,833982178:173,833981993:185,834586861:207,833982765:208,833981834:231,835087532:236,833982013:253,833981834:266,833981963:276,833982244:277,833982245:288,833981870:292,833981834:296,833973081:316,833973235:329,833973235:338,834586900:339,833981834:344,833973175:349,833973175:350,833982244:353,833982683:355,833982808:356,833982259:357,833982790:364,833982013:367,833982133:372,834587089:377,833982715:380,833973081:381,833982668:434,833981804:442,833982259:454,835087603:457,833981896:480,833982648:500,833982790:508,833982957:527,833973298:539,833982860:550,834587074:551,833982668:552,833982859:553,833982013:587,833982889:588,833973175:589,833982668:590,833973081:592,833973081:593,833981896:595,835087532:597,833982889:610,833981710:648,834586915:733,834586590
then i get proper recommendations
8	590,0.831:480,0.821:110,0.770:500,0.763:858,0.758:527,0.719:589,0.718:597,0.712:434,0.686:364,0.651:
What am i missing here?

+1


Textareas in overflown containers aren't scrolling to bottom in Mozilla

Bug, feature request, or proposal:
Bug
What is the expected behavior?
When I type in a textarea that is taller than it's container, I want to see what I type.
What is the current behavior?
The textarea doesn't scroll to bottom on keystrokes
What are the steps to reproduce?
(I had issues with Mozilla and stackblitz, if you can't see the output in live editing, try the other link)
Live editing : https://stackblitz.com/edit/angular-dsscz4-xas344?file=app/text-field-autosize-textarea-example.html
Result : https://angular-dsscz4-xas344.stackblitz.io/
What is the use-case or motivation for changing an existing behavior?
A user typing text he can not see isn't really user-friendly
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
See stackblitz
Is there anything else we should know?
If it can be of any help, I have stumbled upon this SOF question : https://stackoverflow.com/questions/12105440/why-is-typing-in-a-textarea-in-firefox-causing-the-screen-to-scroll

Hello, I am digging this up because I got no answer in 5 days, hope you see this !

I spent some time looking into it and I don't think we can do much about it. This is down the browsers not setting the scroll position consistently: e.g. Chrome scrolls the container so the text cursor is in the view, whereas Firefox scrolls it so the top of the input is visible. It can be worked around for this one case by calling textarea.scrollIntoView(false) however doing so will move the user's scroll position unnecessarily in most other cases. We could've used scrollIntoViewIfNeeded, but it isn't support on Firefox.

I spent some time looking into it and I don't think we can do much about it. This is down to browsers not setting the scroll position consistently: e.g. Chrome scrolls the container so the text cursor is in the view, whereas Firefox scrolls it so the top of the input is visible. It can be worked around for this one case by calling textarea.scrollIntoView(false) however doing so will move the user's scroll position unnecessarily in most other cases. We could've used scrollIntoViewIfNeeded, but it isn't supported on Firefox.

Closing this issues as "won't fix" for above reasons.


2 'pain' terms in ontology

VEuPath has 2 'pain' terms: HP:0012531 and SYMP:0000099. Both are defined, and the two definitions seem similar. Only the SYMP term is used in ClinEpi (as 'Aches or pains'); based on that, it would seem better to remove the HP term. However, HP appears to be in more active development.

Let's go with the HP term.

The SYMP term has been replaced with the HP term, both in eupath-dev and in ClinEpi projects. Closing.


Add "Contact" media item type

Enable user to send a dummy contact to the chat.

Hello everyone!
I'm sorry to inform the community that I'm officially deprecating this project. 😢 Please read my blog post for details:
http://www.jessesquires.com/blog/officially-deprecating-jsqmessagesviewcontroller/
Thus, I'm closing all issues and pull requests and making the necessary updates to formally deprecate the library. I'm sorry if this is unexpected or disappointing. Please know that this was an extremely difficult decision to make. I'd like to thank everyone here for contributing and making this project so great. It was a fun 4 years. 😊
Thanks for understanding,
— jsq


Revert previous sort order

A recent PR (#16) flipped the return value of sort.Interface.Less() for equal records. Flip it again to get back to where we were before.

Maybe add a test?

I'll merge this without for now, but yes we should add a test in this repo at some point.


refactor(Topology/Order) : Fix inconsistencies between Lower/Upper and Scott topologies

Make type explicit in def of Scott-Hausdorff and Scott topologies
Move With{Lower|Upper}Homeomorph into the correct namespace

bors r+
Thanks!


Quick Network install mode

I would like a mode where it installs a cia that is sent over the network, after the cia is installed it would be launched. Hold Y when starting FBI to activate?

You... could just use the normal network installation, switch to launch, and launch it.

It would be faster.

It wouldn't be all that faster. Plus, what's the point? Installation is generally a one-time thing, so once it's installed you can easily launch it as many times as you need

Devolpment.


Fixed mastodon verification + Added rel Button attribute

Proposed Changes

Fixed mastodon verification (mastodon require you to have the rel="me" attribute set in the HTML element that contain your profile link in order to show it as verified. More reading here
Added optional rel attribute to make the change as clean as possible and provide better flexibility

Screenshot (If Applicable)
Checklist

[x] Tested locally
[x] Ran yarn ci to test my code
[x] Did not add any unnecessary changes
[x] All my changes appear after other changes in each file
[x] Included a screenshot (if adding a new button) [not relevant]
[x] 🚀

Thank you!

Thanks again, works great!

Yeah 👍


[Enhancement] Skip to write Iceberg table/column comment if comment is empty

Why I'm doing:
StarRocks will set the table comment to empty by default, but the empty comment is valid in iceberg table, and this will make other engines(Hive/Trino/Spark) display the useless empty comment when show create table.
What I'm doing:
Like https://github.com/StarRocks/starrocks/pull/39683 , we need to skip to write the empty comment to avoid the useless comment and then other engines(Hive/Trino/Spark) won't dispaly the useless empty comment.
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

cc @stephen-shelby


Implement file and folder tags on the Explorer as an addon

📝 File and Folder Tags Explorer Addon
Files and folders can be tagged with keywords which can later on be used as a search keyword for better file organization similar to the one used in macOS.
Yeah, exactly the one from macOS. No shame. 😅
If you'd like to see this feature implemented, add a 👍 reaction to this post.

dup #150


Snow fix

Purpose

Closes #421

[ ] I have read and checked the items on the review checklist.

Parent issue already closed by https://github.com/CliMA/ClimaCoupler.jl/issues/435


[daal-2020-mnt] kNN predict optimizations

This is a cherry-pick from #518
The PR optimizes knn predict algorithm if training data set in model is represented as a homogen SOA numeric table (default behavior for C++ and only one available for IDP Sklearn).

PCm: http://intel-ci.intel.com/ea7a6e00-cd09-f1b8-9d90-8cdcd4b723a1
Perf:  http://intel-ci.intel.com/ea7a7666-78e5-f12a-b7d5-8cdcd4b723a1


Bump to grpc 1.44

Please provide a description of this PR:

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
fc280d855e1d816d5b1c076e6486c5c5f39179c3
link
true
/test integ-telemetry_istio

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

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
fc280d855e1d816d5b1c076e6486c5c5f39179c3
link
true
/test integ-telemetry_istio

integ-pilot-istiodremote_istio
fc280d855e1d816d5b1c076e6486c5c5f39179c3
link
true
/test integ-pilot-istiodremote_istio

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

/retest


Please update docs for network firewall policy rule update to reflect correct protocols

Hello,
I recently found an issue with the docs on this page: https://docs.microsoft.com/en-us/cli/azure/network/firewall/policy/rule-collection-group/collection/rule?view=azure-cli-latest#az_network_firewall_policy_rule_collection_group_collection_rule_update
--protocols
Space-separated list of protocols and port numbers to use, in PROTOCOL=PORT format. Valid protocols are Http, Https. --remove
In the portal, in addition to Http and Https it is possible (and needed) to add Mssql as a valid protocol to a Firewall Policy Rule Collection.
Despite the documentation, I ran the command including Mssql protocol and it worked.
az network firewall policy rule-collection-group collection rule update --collection-name MyCollection --name AllowAKSMicrosoft --policy-name MyPolicyName --rcg-name DefaultApplicationRuleCollectionGroup --resource-group MyResourceGroup --protocols Https=443 Mssql=1433
However, the corresponding Terraform module in azurerm provider only accepts Http and Https.
Request is to review and update the docs, so that Terraform implementation can match it.
Hope it helps,
Best regards,
-Luis

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

ID: 51bc8847-2744-bb66-7b83-0518aa47536c
Version Independent ID: c1c31748-e899-dd98-e418-e01ed781a14a
Content: az network firewall policy rule-collection-group collection rule
Content Source: latest/docs-ref-autogen/network/firewall/policy/rule-collection-group/collection/rule.yml
Service: virtual-network
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

@kairu-ms for awareness


When you released the code !

Dear noah ：
Thank you very much for your work！I looked at your paper and was struck by the beauty of it！
I want to know When you will released the code!
THANK YOU!

Also waiting for the code release +1

+1

+4

Dear noah ：
Thank you very much for your work！I looked at your paper and was struck by the beauty of it！
I want to know When you will released the code!
THANK YOU!

Thanks for your attention. Code will be released soon.

Dear noah ：
Thank you very much for your work！I looked at your paper and was struck by the beauty of it！
I want to know When you will released the code!
THANK YOU!

We have already released our MindSpore code.  You can refer to https://gitee.com/mindspore/mindspore/tree/master/model_zoo/research/cv/IPT

Waiting for pytorch version!

+1

+1


Reading Panel4D stored in HDF5

pd.__version__ ### '0.15.2'
store = pd.HDFStore('synthetic_networks.h5',mode='w', table=True)

controls = pd.Panel4D(labels=['a', 'b', 'c'],
                    items=arange(100),
                    major_axis=arange(121),
                    minor_axis=arange(121),
                    dtype='float64')

store.append('controls', controls)
store.close()

store_emp = pd.HDFStore('synthetic_networks.h5',mode='r', table=True)
controls = store_emp['controls']

---------------------------------------------------------------------------
NotImplementedError                       Traceback (most recent call last)
<ipython-input-4-b8e1db9431a6> in <module>()
      1 store_emp = pd.HDFStore('synthetic_networks2.h5',mode='r', table=True)
----> 2 controls = store_emp['controls']

/home/jeffrey_alstott/anaconda3/lib/python3.4/site-packages/pandas/io/pytables.py in __getitem__(self, key)
    407
    408     def __getitem__(self, key):
--> 409         return self.get(key)
    410
    411     def __setitem__(self, key, value):

/home/jeffrey_alstott/anaconda3/lib/python3.4/site-packages/pandas/io/pytables.py in get(self, key)
    617         if group is None:
    618             raise KeyError('No object named %s in the file' % key)
--> 619         return self._read_group(group)
    620
    621     def select(self, key, where=None, start=None, stop=None, columns=None,

/home/jeffrey_alstott/anaconda3/lib/python3.4/site-packages/pandas/io/pytables.py in _read_group(self, group, **kwargs)
   1265         s = self._create_storer(group)
   1266         s.infer_axes()
-> 1267         return s.read(**kwargs)
   1268
   1269

/home/jeffrey_alstott/anaconda3/lib/python3.4/site-packages/pandas/io/pytables.py in read(self, where, columns, **kwargs)
   3701
   3702                 lp = DataFrame(new_values, index=new_index, columns=lp.columns)
-> 3703                 objs.append(lp.to_panel())
   3704
   3705         # create the composite object

/home/jeffrey_alstott/anaconda3/lib/python3.4/site-packages/pandas/core/frame.py in to_panel(self)
   1062         if (not isinstance(self.index, MultiIndex) or  # pragma: no cover
   1063                 len(self.index.levels) != 2):
-> 1064             raise NotImplementedError('Only 2-level MultiIndex are supported.')
   1065
   1066         if not self.index.is_unique:

NotImplementedError: Only 2-level MultiIndex are supported.

I assume this is a known issue but I can't find any analysis of it. Am I doing something wrong?

you don't need to pass table in the call to HDFStore; it is not a valid argument (and ignored)
You have a completely nan Panel4D so by default nothing is written, so you can do:
# fill it with actual values
In [25]: store.append('controls', controls.fillna(0))

In [26]: store
Out[26]:
<class 'pandas.io.pytables.HDFStore'>
File path: synthetic_networks.h5
/controls            wide_table   (typ->appendable,nrows->1464100,ncols->3,indexers->[items,major_axis,minor_axis])

# you can force the writing
In [27]: store.append('controls2', controls, dropna=False)

In [28]: store
Out[28]:
<class 'pandas.io.pytables.HDFStore'>
File path: synthetic_networks.h5
/controls             wide_table   (typ->appendable,nrows->1464100,ncols->3,indexers->[items,major_axis,minor_axis])
/controls2            wide_table   (typ->appendable,nrows->1464100,ncols->3,indexers->[items,major_axis,minor_axis])

this is done for efficiently storing this as you can see it is materialized in 2-d, which causes it be very
large.

Thanks for picking out the problem in my example. I now realize I was actually doing another thing wrong, which led to problems even when there was data.
I built a Panel4D full of nans, then:

calculate a portion of the data
do store.append('controls', controls) (so as to not lose that data in case something went wrong later)
Return to 1 until all the data is calculated.

I assumed the appending would overwrite the old 'controls', but it simply added onto them, creating a monster. That monster was then unreadable, throwing the exact same error:
NotImplementedError: Only 2-level MultiIndex are supported.
What is the best way to iteratively overwrite data in an HDFStore, so that I don't end up in this scenario?

use put to overwrite
note that this will be very inefficient (in terms of space; hdf5 doesn't actually delete data)
and should either do this in memory
or repack when u r done


Chap2 mb

Purpose/implementation Section
What changes are being implemented in this Pull Request?
Chap2 OCS Infrastructure: created feedback section and moved survey info, added diagrams and more details to website, search tool, and github sections
What was your approach?
What GitHub issue does your pull request address?
Tell potential reviewers what kind of feedback you are soliciting.
New Content Checklist

[ ] New content/chapter is in an Rmd file with this kind of format and headers.

[ ] New content/chapter contains Learning Objectives and are in the correct format.

[ ] Bookdown successfully re-renders and any new content files have been added to the _bookdown.yml.

[ ] Spell check runs successfully in Github actions style-n-check).

[ ] Any newly necessary packages that are needed have been added to the Dockerfile and image.

[ ] Images are in the correct format for rendering.

[ ] Every new image has alt text and is in a Google Slide.

[ ] Each slide is described in the notes of the slide so learners relying on a screen reader can access the content. See https://lastcallmedia.com/blog/accessible-comics for more guidance on this.

[ ] The color palette choices of the slide are contrasted in a way that is friendly to those with color vision deficiencies.
You can check this using Color Oracle.

this preview failed due to a conflict in the .rds file


yii\db\BaseActiveRecord::deleteAll() should be compatible with yii\db\ActiveRecordInterface::deleteAll()

What steps will reproduce the problem?
BaseActiveRecord declares method deleteAll() declared at ActiveRecordInterface changing its signature:
https://github.com/yiisoft/yii2/blob/master/framework/db/ActiveRecordInterface.php#L262
https://github.com/yiisoft/yii2/blob/master/framework/db/BaseActiveRecord.php#L199
Creating custom ActiveRecord implementation extending BaseActiveRecord forces to use new signature, even if it makes no sense.
What is the expected result?
Custom ActiveRecord should be able to use ActiveRecordInterface::deleteAll(), which accepts single paramerter only:
public static function deleteAll($condition = null) {}

What do you get instead?
PHP Compile Error – yii\base\ErrorException
Declaration of yii2tech\filedb\ActiveRecord::deleteAll($condition = NULL) must be compatible with yii\db\BaseActiveRecord::deleteAll($condition = '', $params = Array)
Additional info

Q
A

Yii version
2.0.11

PHP version
*

Operating system
*

Issue extracted from https://github.com/yii2tech/filedb/pull/7

Indeed that looks a wrong and $params = [] should be in the interface but I don't understand how it works now. It is like that since 2013.

Additional params can be added during class/interface inheritance - it is fine.
The problem is adding $params at BaseActiveRecord twists the function signature unnecessary.
Additonal argument $params makes sense for yii\db\ActiveRecord, which uses PDO, but is absolutely redundant for NOSQL based ActiveRecord like MongoDB.

so we should remove $params from BaseActiveRecord, right?

Resolved by commit 319e27c45c04d19a21b39598998038ad5464d2f8


Support DockerSync 0.4.6

Docker sync has been updated, some utility commands have been deprecated so functionality has been moved into different tools. No longer are we going to use docker-sync-daemon as it's going to be removed in 0.5.0+.

Added in 0.2.4


Default properties values are not working

Description
Default values are not being applied when a property has one specified and its corresponding attribute is not defined.
Live Demo
https://lit-element-example-km85zd.stackblitz.io
Steps to Reproduce

Create my-element
Define a property with a default value
Use the default value in the element's template
Append my-element to document.body

Expected Results
The default value should be rendered
Actual Results
The default value is not rendered (nor is it passed to _render in the props object)
Browsers Affected

[x] Chrome -- other browsers were not tested

Versions

lit-element: v0.5.2
webcomponentsjs: v2.0.2
polymer: v3.0.2

Default values are set in the constructor, not in the properties object.
constructor() {
  super();

  this.mood = 'happy';
}

Yes, using Polymer you can set the default value in properties or the constructor, for lit-element it uses the constructor only.

Ah okay.  Are there any other property restrictions?  I feel like I may have missed some documentation somewhere.

Yeah, observer, readOnly, notify, etc are all not available in a Lit Element. It may be helpful to remember that a Polymer element is not a Lit element and, while they both do support the concept of properties, they are very different classes.

That makes sense, I'd just add that it's not super clear from the README and it's easy to make assumptions since this element is part of the Polymer project.  Would it make sense to add some sort of feature comparison to PolymerElement in the README?

Looks like another difference is that attributes are not converted to camelCase when mapped to properties...

how to solve somehow we want to get values from an element prototype?
when we get value from "litelemnt.prototype.accessKey" the browser gets an error and stops running the code.


setting property in callback causes type hint error

VS Code Version: 1.53.2
OS Version: macOS Catalina (10.15.6)

Steps to Reproduce:

Have a normal Javascript project (jsconfig.json) with one .js file containing:

// @ts-check

class Foo {
  /**
   * @param {(this: this) => void | Promise<void>} fn
   */
  bar(fn) {
    fn.call(this);
  }

  baz = false;
}

const foo = new Foo();
foo.bar(function() {
  this.baz = true;
});

Alternatively, have a Javascript project (jsconfig.json) with a types/index.d.ts for Intellisense purposes only

types/index.d.ts:
declare global {
  class Foo {
    bar(fn: (this: this) => void | Promise<void>): void;
    [key: string]: any;
  }
}

in some .js file:
// @ts-check

/** @type {Foo} */
const foo = undefined; // pretend it gets initialized somehow

foo.bar(function() {
  this.newProp = true;
})

I see the vscode error:

Workaround to avoid the error is to have two separate signatures:
class Foo {
  bar(fn: (this: this) => void): void;
  bar(fn: (this: this) => Promise<void>): void;

  [key: string]: any;
}

If you create a pure .ts file you don't see the hint error:
class Foo {
  bar(fn: (this: this) => void | Promise<void>): void {
    fn.call(this);
  }

  [key: string]: any;
}

const foo = new Foo();

foo.bar(function() {
  this.newProp = true;
})

Does this issue occur when all extensions are disabled?: Yes

In a JS file we auto-detect this assignments and turn the function expression into effectively a class constructor, which has a different this type. TS doesn't have that behavior. It's not clear to me what you're trying to do here.

@RyanCavanaugh the bar is a hook callback function. Specifically ember-qunit has a NestedHooks.beforeEach(fn: (this: TestContext, assert: Assert) => void | Promise<void>) which has a hint error if I set something on the TestContext.

Forgot to mention that I added a merged declaration to support any key
declare module 'ember-test-helpers' {
  interface TestContext {
    [key: string]: any;
}

Also If I don't use a union in the signature void | Promise<void> then I don't see the hint error, do you know why that would be?
// @ts-check

class Foo {
  /**
   * @param {(this: this) => void} fn
   */
  bar(fn) {
    fn.call(this);
  }

  baz = false;
}

const foo = new Foo();
foo.bar(function() {
  this.baz = true;
});

Here's an example that mimics the use case more clearly with the same hint error. But even if it were a class constructor, the hint error still doesn't make sense to me.
// @ts-check

class Bar {
  qux = false;
}

class Foo {
  /**
   * @param {(this: Bar) => void | Promise<void>} fn
   */
  setupBar(fn) {
    this.bar = new Bar();
    fn.call(this.bar);
  }

  bar;
}

const foo = new Foo();
foo.setupBar(function() { // still get the hint error here
  this.qux = true;
});


Add external source for IANA documents, using their assignments API

Currently, we resolve IANA references statically indexed via relaton-data-iana.
However, since IANA seems to offer an API endpoint, it can be registered as another external source, like Crossref and Datatracker. We could use it as a fallback in xml2rfc paths, and possibly in service GUI (if search is augmented to support external sources).

@strogonoff instead of the API, we directly use the IANA rsync endpoint which contains the full data. The rsync endpoint is the authoritative data set and is preferable over the IANA website (not an API) which is generated from the data set.

@strogonoff instead of the IANA website (it's not an API), we directly use the IANA rsync endpoint which contains the full data. The rsync endpoint is the authoritative data set and is preferable over the IANA website (not an API) which is generated from the data set.

It’s like with Datatracker though, using external source could provide more up-to-date bibliographic data before it’s indexed…🤔

It’s like with Datatracker though, using external source could provide more up-to-date bibliographic data before it’s indexed…🤔

The nature of I-Ds and IANA registries are different.
Authors have direct access to publish I-Ds, and therefore it is reasonable they want to cite a published draft directly.
Authors have NO access to creating or modifying IANA registries. IANA registries are managed by IANA, a non-IETF organization. Thus RFC/I-D authors cannot have an expectation that a new IANA registry is created at some certain time. Remember we are talking about registries, not registry items.
Moreover, the frequency of I-Ds is high, IANA registries is low.
Finally, the same argument can be applied to ALL non-datatracker bibliographic sources. IANA is a separate organization, just like NIST and IEEE.
We need to strike a balance between resources and effectiveness. At this point, I prefer the mode of operation today for IANA registries because it is predictable and complete in terms of data.


paste_on_remote_yank is not working, and please add an option to enable it for everything

Hello.
Thanks for experimenting with this idea for a plugin.
My main use case 99% of the times is to bring some remote piece of code to the place I have the cursor, but I always have to do too many keystrokes because after yank, I have to manually paste, which is almost as much work as jumping there using normal motion, yank, c-o to get back and then paste. Will be cool to be able to enable paste_on_remote_yank for everything.
And, I never got it working, not sure how it is supposed to be used, if you can explain I will be grateful.

+1 on this, I was trying it for 30 minutes, wondering why it's not working

paste_on_remote_yank works fine for me on 748b261 with this setup and default leap bindings.
    config = function()
      require("leap-spooky").setup({
        paste_on_remote_yank = true,
      })
    end,

What's in your configs?

I'm on the same commit, using lazy.nvim, and this is what I have:
{
  'ggandor/leap-spooky.nvim',
  event = 'BufReadPost',
  dependencies = { 'leap.nvim' },
  opts = {
    paste_on_remote_yank = true,
  },
}

Using your config worked for me as well. What's your leap config and what mappings are you using for spooky motions, and what Nvim version?

My nvim version is 0.8.3
My leap config is also very basic (I haven't set up its default mappings, and I want to use it in the context of spooky)
{
  'ggandor/leap.nvim',
  config = function()
    vim.api.nvim_set_hl(0, 'LeapBackdrop', { link = 'Comment' }) -- grey out search area
  end,
}

As for the mappings, I'm trying, for example, doing yrr, then the leap search (2 char, marker, jump). The line is indeed yanked, but it isn't pasted

This is my also very basic (IMO) config:
return {
  "ggandor/leap-spooky.nvim",
  requires = "ggandor/leap.nvim",
  config = function()
    require("leap-spooky").setup {
      affixes = {
        -- These will generate mappings for all native text objects, like:
        -- (ir|ar|iR|aR|im|am|iM|aM){obj}.
        -- E.g `darw` for delete a remote word
        -- Special line objects will also be added, by repeating the affixes.
        -- E.g. `yrr<leap>` and `ymm<leap>` will yank a line in the current
        -- window.
        -- You can also use 'rest' & 'move' as mnemonics.
        remote = { window = "r", cross_window = "R" },
        -- magnetic means you are going to move to the position where you are yanking
        magnetic = { window = "m", cross_window = "M" },
      },
      -- If this option is set to true, the yanked text will automatically be pasted
      -- at the cursor position if the unnamed register is in use.
      paste_on_remote_yank = true,
    }
  end,
}

Yeah, I think our setups are the same (if I'm not mistaken, the values you have for affixes are the defaults, and that's why I didn't add them, so I think, basically we have the same configuration. So confused as to why it works for you and not mine 🤔

@farzadmf Have you tried without lazy.nvim, calling setup manually?

This feature used to work for me, but suddenly stopped at some point in the last couple of weeks. I've been making heavy changes in my config over this time (including migration to lazy.nvim). So after reading this thread I thought this may be due to lazy.nvim indeed. Turns out, the problem is the default register used for yanking. For some reason, Spooky pastes only if the target register is ":
https://github.com/ggandor/leap-spooky.nvim/blob/748b2614e859704d8004e86be97401c9f3e28e80/lua/leap-spooky.lua#L127-L128
As a part of my migration, I adopted this option from LazyVim:
https://github.com/LazyVim/LazyVim/blob/befa6c67a4387b0db4f8421d463f5d03f91dc829/lua/lazyvim/config/options.lua#L9
This changed my default yanking register to system clipboard ("+") and thus broke Spooky paste.

For some reason, Spooky pastes only if the target register is "

That is because you never want to allow pasting right away if you use a non-default register - you usually use a named register to accumulate multiple selections, or store yanked stuff to be used later, after certain in-between operations. The thing I missed is that v.clipboard can actually change the value of the default register.

Thank you @ggandor for fixing this, I guess I had a similar setting somewhere because I am using system clipboard as well

@ggandor Thanks for the explanation and the quick fix! (and the plugin itself, of course)

Yeah, I think our setups are the same (if I'm not mistaken, the values you have for affixes are the defaults, and that's why I didn't add them, so I think, basically we have the same configuration. So confused as to why it works for you and not me 🤔

Who says it works for me? I'm commenting here because it does not work for me either.

Who says it works for me? I'm commenting here because it does not work for me either.

Oops, sorry, I mixed up the usernames, and I thought you're the one that has it working.
But I think the recent change actually fixed the issue, and seems to be working for me

I can confirm that, after updating to 0bb68f0 it works for me. Thank you very much! Now I will be able to yank much much faster.


Update URL of the public signing key + bump up version

https://github.com/sgerrand/alpine-pkg-glibc#please-note

Builds failed for alpine 3.3, 3.4 and 3.5 while installing glibc apks


Incomplete plugin SecurityContexts

Describe the bug
Plugins do not match k8s baseline security standards (mainly due to host mounts), but that could be compensated somewhat by adopting relevant policies from the k8s restricted security standard.   When containers are run with root user, they could at least drop unnecessary privileges...
To Reproduce
Check what capabilities are dropped in SecurityContext sections listed in plugins deployments:
https://github.com/intel/intel-device-plugins-for-kubernetes/tree/main/deployments
For example:
https://github.com/intel/intel-device-plugins-for-kubernetes/blob/main/deployments/gpu_plugin/base/intel-gpu-plugin.yaml
Expected behavior
Something like this:
securityContext:
  readOnlyRootFilesystem: true
  allowPrivilegeEscalation: false
  capabilities:
     drop: [ "ALL" ]
     add: [<whatever is actually necessary>]
  seccompProfile:
    type: RuntimeDefault

Screenshots
E.g. in above listed GPU plugin deployment, SecurityContext is just:
        securityContext:
          seLinuxOptions:
            type: "container_device_plugin_t"
          readOnlyRootFilesystem: true
          allowPrivilegeEscalation: false

System (please complete the following information):

Device plugins version: git HEAD

@eero-t can you submit a PR for this?

@eero-t can you submit a PR for this?

Not this or next week, maybe after that.


Verification codes expiration date

Describe the bug
Hey!
In our app we use Amplify for the sign in flow and password reset. We have some bug in logic compares to Android sdk, which works as expected.
User receives verification code #1 and then request another code #2. We expect that only newest verification code will be valid, but in fact all received verification codes are valid.
Android sdk accept only newest verification code.
This function is used for password reset.

Steps To Reproduce
Steps to reproduce the behavior:
1. Got to reset password
2. Click on 'Resend code' and have 2 codes in your mail.
3. Use old one
4. This old one code is accepted as valid

Expected behavior
Only newest verification code accepted
Amplify Framework Version
2.8.1
Amplify Categories
Auth
Dependency manager
Swift PM
Swift version
5
CLI version

Xcode version
14.3
Relevant log output
No response
Is this a regression?
Yes
Regression additional context
No response
Platforms
No response
OS Version
15.0
Device
iPhone 13 Pro max
Specific to simulators
no
Additional context
No response

@Elza-Hoff I tested on Amplify Swift and can see that older codes are not accepted. Amplify Swift simply passes on the code to Cognito and doesn't have any client side logic.
Would you be able to share testing steps that you are performing for this use case? Is there anything different compared to iOS and Android implementation?

@Elza-Hoff
I am still not super clear what the use case is.. You have shared with me 2 very different API's. One API is for sign up whereas the other one is for reset password.
Would you be able to share the code snippet that is causing you this problem?


More visible note about the risk of using community actions, referenced by tag/branch name instead of SHA, in combinations with secrets

What article on docs.github.com is affected?
https://docs.github.com/en/actions/learn-github-actions/finding-and-customizing-actions#using-release-management-for-your-custom-actions
What part(s) of the article would you like to see updated?
I'd like to add a more visible note about the risk of using actions from the community, that might require a secret and then not referencing it via a SHA but a branch or tag name instead, as it is "suggested" everywhere else in the docs.
Additional information
I was exploring what is possible with GitHub Actions recently and that was what I was wondering about the whole time. Then I found this article: https://julienrenaux.fr/2019/12/20/github-actions-security-risk/
And I also just successfully posted the GITHUB_TOKEN in an issue (https://github.com/mktcode/test-action/issues/6) by force-pushing to the action's repo and overwriting the commit to which my v1.0-maybe tag was linked to.

Thanks
Get Outlook for iOShttps://aka.ms/o0ukef

From: welcome[bot] @.>
Sent: Wednesday, June 9, 2021 4:05:17 PM
To: github/docs @.>
Cc: Subscribed @.***>
Subject: Re: [github/docs] More visible note about the risk of using community actions, referenced by tag/branch name instead of SHA, in combinations with secrets (#7216)
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelineshttps://github.com/github/docs/blob/main/CONTRIBUTING.md.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/github/docs/issues/7216#issuecomment-857601595, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUEDMN3CSP36XSOESYGB4CDTR5DG3ANCNFSM46LZWQTQ.


How to make appRTC listen on its host's IPV4 ?

Hello,
I've installed appRTC on a Debian server.
Output at launch :

INFO     2016-11-06 10:02:33,024 sdk_update_checker.py:229] Checking for updates to the SDK.
INFO     2016-11-06 10:02:33,250 sdk_update_checker.py:257] The SDK is up to date.
INFO     2016-11-06 10:02:33,289 api_server.py:205] Starting API server at: http://localhost:56817
INFO     2016-11-06 10:02:33,296 dispatcher.py:197] Starting module "default" running at: http://localhost:8080
INFO     2016-11-06 10:02:33,297 admin_server.py:116] Starting admin server at: http://localhost:8000

Seems like appRTC is only listening to its host's loopback. I've read some documentation about Google AppEngine SDK and figured out that creating a file called dispatch.yaml might solve my problem :
dispatch:
  # Default module serves simple hostname request.
  - url: "<IPV4 ADRESS>:8080/"
    module: default

I've rebuilt appRTC with this file, yet nothing seems to change.
Right now I only can access appRTC using two paths:
Locally by using host's web browser, typing localhost:8080
Externally by using SSH tunneling, typing localhost:8080
I want anyone to be able to access appRTC externally just by typing :8080
How do I do that ?
Thanks in advance.

There is a parameter for your dev_appserver.py called --host. You can use --host=<IP_ADDRESS> to addess via :8080
http://stackoverflow.com/questions/15513064/address-0-0-0-0-argument-not-working-after-upgrading-to-app-engine-1-7-6

Yes the above comment is correct. Do note that dev_appserver.py is a development tool, not for production deployment.


add react select (originally from josephdlawson21-add-react-select). Fixes #892

No idea why this is passing CI and the original PR (#977) was not...

Fixes #892.

@knod Did a merge that changed Household.js--would appreciate a review of the new merge!

@dylanesque (or anybody else)--I would like to have at least 2 approvals on this before I merge, since I didn't write the original.

Doesn't look like it broke anything to me and the code styles are pretty close to what we're establishing. I stand by my approval!


Migrate from ASP.NET Core 6.0 to 7.0

.NET platform has a new major release. Now supporting .NET 7 is a major release that improves developer quality by improving fundamentals like performance, functionality, and usability.
Migration Article -> Migrate from ASP.NET Core 6.0 to 7.0

Related existing pull requests -> #518, #521, #522


Rework async operations in generateHashArrayFile.js

The current async operations I've done in the generator script need work. I don't think I've implemented it correctly. Opening this up as an issue.

changes merged


Releases/3.4

Please add a @date tag to the framework so users can track the creation date of their code. I generate a "new Date()" in the console and attach that to a @Date tag, even though it isn't supported. For example: @date Fri Mar 18 2016 13:21:03 GMT-0700 (Pacific Daylight Time).
The help file for @author found at: http://usejsdoc.org/tags-author.html, omits a complete example of the syntax, making this page less than useful. This is especially vexing, because the author chooses to "bunt" instead of giving a complete example, with the following partial summary:
", if the author's name is followed by an email address enclosed in angle brackets,"
that is vague and lacks precision, based on the syntax:
"@author <name> [<emailAddress>]"
Did the author mean <>, or []. Both are angular. The reason I find this confusing is that "<name>" also uses what could be construed as "angle brackets", yet these do not appear in the partial example. The syntax however, uses two forms of "angular" brackets, "<> and []". While I call the latter [], square brackets, this is the only distinction between "<name>", and [<emailAddress>]. So I am wondering what the author's intention was. At minimum the author is INCONSISTENT! Without a complete example of the syntax, how is one to know for sure? Please advise.
Lastly, the use of endless tags in support of JavaScript mimicking of classical inheritance is a disservice to JavaScript programmers everywhere. The JavaScript community will continue in the errors of their fathers if you aid and abet them, never learning to understand or exploit the superior capabilities of the language.
Using JavaScript to mimic classical inheritance is a misuse of the language and  a violation of solid principles in software design. It breaks encapsulation, creates the tightest coupling attainable in software design, is unnecessary and a waste of time in JavaScript. This is the real reason that Yahoo mothballed YUI. The light bulb finally turned on for them. Dynamic object extension and prototypal inheritance is a superior way to write software!
Kind Regards,
Michael D. Alexander
La Jolla, California
<EMAIL_ADDRESS>+1-619-496-5038

I'm not sure why this is a pull request rather than an issue.
In response to your requests:

I'd prefer not to add a @date tag to JSDoc, but you can define one yourself using a JSDoc plugin. You'll need to modify the JSDoc template to display the tag value.
The @author tag documentation has been fixed.
JSDoc tries to support many different ways of writing JavaScript, including "mimicking of classical inheritance." This is unlikely to change.


Add Openstack to list of valid prefixes for tag mapping

see also: https://github.com/ManageIQ/manageiq-providers-openstack/pull/325

:+1:


[incompatible] [bugfix] s/RemoteUser/RemoteLogname/g

At #11, I accepted RemoteUser feature, but its naming is not accurate. RemoteLogname is better for it, so I fixed.

Coverage remained the same at 95.0% when pulling<PHONE_NUMBER>5c79328ddea9a0a1729837462dc087 on remote-user into e73c23429bee75016666cd825b72725362e1fcc4 on master.

Coverage remained the same at 95.0% when pulling<PHONE_NUMBER>5c79328ddea9a0a1729837462dc087 on remote-user into e73c23429bee75016666cd825b72725362e1fcc4 on master.


https://hikarinoakari.com/out/

https://hikarinoakari.com/out/
cant bypass
need fix

Please open this issue using the right template.


Validation on all form fields (Server Side)

Files not changed were already validating correctly on my end.

Small update, not yet complete, almost done.

This will be merged into the forthcoming AJAX forms pull request.


Add content props, #8

This PR adds a content prop that allows to set a text content instead of a DOM element.
It also includes a partial rewrite of the underlying Tooltip class which led to a breaking change as the prop contentClassName has been renamed to containerClassName to be more accurate.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Programmatically clicking a cell for editing

Heya, Great work with the plugin I absolutely love it!
I was wondering however if there was a way to programatically select a cell and show the editing caret inside. Ive tried the standard .focus() and .click() onto the cell to no avail =(
Cheers

I was having the same issue and this worked perfectly for me. Thanks.


Rename the plugin

I don't care for the fact that the plugin must be referred as "plugin-enabled options". That probably should be just "enabler". I'm considering renaming that, but unsure when or how, so I'll await some feedback here first.

Originally posted by @jaraco in https://github.com/jaraco/pytest-enabler/issues/10#issuecomment-1757674381

The reason for naming it "plugin-enabled options" was to give a more descriptive name to the entry point. I hadn't realized at the time that the name of the plugin as defined by the entry point was exposed to the user, so to disable the plugin, one has to use -p "no:plugin-enabled options" and use quotes to ensure proper parsing.
The plan instead is to change that to simply "enabler", following the convention that most pytest plugins use, which is to reflect the pytest-stripped name.


Remove [ValidateNotNullOrEmpty] from -InputObject on Get-Random to allow empty string

PR Summary
Get-Random has [ValidateNotNullOrEmpty] attribute on InputObject parameter which limits a collection from having an empty string.  However, if you use the default positional parameter Maximum it doesn't have this restriction.  This creates confusion to users as they expect these two to be equivalent:
Get-Random @('a','') # this already worked
Get-Random -InputObject @('a','')

Although it's not obvious that this is two different parameter sets.  However, there's no reason to restrict InputObject parameter here.  Since it's mandatory, you can't give it $null only.
This change also allows $null in the collection:
Get-Random @('a',$null) # this already worked
Get-Random -InputObject @(`a`,$null)

PR Context
Fix https://github.com/PowerShell/PowerShell/issues/3682
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

Thanks for the quick turnaround, @SteveL-MSFT  and @iSazonov.
@SteveL-MSFT, to avoid confusion, could you please update the OP to indicate that $null values in the input collection now are accepted (in addition to empty strings)?

It seems we need an issue in Doc repo too.

@iSazonov added

Oops, I thought AutoMerge waits a day before merge 😕


Environments

This PR connects to 27
I have created :

/src/config.ts
This is the file to import, It loads environmental and shareable settings and makes them available to app components
/config/environment.common.default.json
Template file for genereal configuration, where we put our env settings shared between the environments;
/config/environment.default.json
Template file for environment configuration, where we put our env settings for the different environments. We need to have a json file for every enviroment (e.g. dev, prod);

I have changed .gitignore file to prevent commit of the configuration file created on git.
I used this config.ts as model for environment configuration file.

It works, but I have a few comments:
The proxy section in environment.default.json can be removed. It was necessary for the prototype, not for this project.
Would it be possible to use the default config file by default, and overlay it with the local versions? I realize I was the one that suggested to use the default files as templates only, but seeing it in action the obvious downside is that simply checking out and building the project will result in a build error, because there is no config file.
It seems to me it would be better to have it the way it works for dspace 6. You have a default file and you can choose to override certain parts of it by putting them in a local file. You can combine two objects in javascript using Object.assign. So something like Object.assign({}, defaultConfig, localConfig) would result in a new configuration object that uses all the default config's values, overlayed with the ones that exist in the local config.
To be able to do so, we'd also need proper default values, so http://localhost:3000 as baseUrl for both rest and ui, /api as nameSpace for rest, / as nameSpace for ui

I've removed all template files. Now there is an environment.default.js with default parameters that could be override by local environmental files.
I have moved JSON file into JS file so we can add comments.

LGTM

Ok for me also!


upgrade to RN0.44.0 APP Exception

I use react-native-git-upgrade to RN 0.44.0.
After the upgrade is complete,run app error
Error infomation:
Objects are not valid as a React child(found:object with keys {visible}).If you meant to render a collection of chhildren,use an array instead.
Check the render method of View
I use react-navigation.
I need wait react-navigation upgrade too?

@gabriel

我也遇到这个问题了，你是怎么解决的 @759325100

Hey, thanks for reporting this issue!
It looks like your description is missing some necessary information. Can you please add all the details specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.
I am going to close this, but feel free to open a new issue with the additional information provided. Thanks!


feat: responsive design and optimization for queries page in dashboard/mentor

Description of Changes

add: responsive design/optimization for mobile devices

Checklist:

[x] My code adheres to the established style guidelines of this project.
[x] I have conducted a self-review of my code.
[x] I have included comments in areas that may be difficult to understand.
[x] I have made corresponding updates to the project documentation.
[x] My changes have not introduced any new warnings.

Screenshots

@anmode

Liked you changes RIshu!! Great work


schema_plus schema:dump picks the first attribute from a composite primary key as the only primary key

if I execute 'ALTER TABLE my_table  ADD PRIMARY KEY (one,  two)'
The dump looks like
create_table "my_table", primary_key: "one", force: true do |t|

@kjg Thanks for the bug report -- but that's Rails' behavior, not schema_plus.  ActiveRecord doesn't support composite primary keys, and schema_plus doesn't do anything to support them either.
There's a gem https://github.com/composite-primary-keys/composite_primary_keys, but I don't know anything about it.  Looking at its README it doesn't seem to address migrations and dumps.
One could imagine that https://github.com/SchemaPlus/schema_plus_tables could be extended to detect composite primary keys and issue primary_key: ["one", "two"] in the dump -- but I think it would also need to extend create_table to accept an array of columns for primary_key: since AFAIK the option only accepts a single column.   If you'd like you can open an issue there with the feature request.  (I myself probably won't have time to get to it any time soon, but maybe somebody will see it and be motivated...  or you could try to implement it yourself...)

Thank you so much for the detailed response. I will open a feature request on SchemaPlus/schema_plus_tables. If I feel motivated enough, I might try to tackle it as well.

@kjg sounds good -- if you do decide to tackle it feel free to ask if you've got any questions or trouble with it.


spine player ios

Can you please write for ios? I need it, help me

Hi @v2tien, I would like to but unfortunately it is not possible as I don't have any Apple devices.
However, rewriting from Android to iOS shouldn't be hard. Feel free to contribute or fork to create your own iOS version.


fixes unit for performance data

fixes #7185
@yuyiguo, @juztas, @amaltaro please review.
I change other units  from msec to sec. However this implies the keyword changes in fwjr data.
readMaxMSec -> readMaxSec
I am not sure whether this will break anything or it is too big of a unit. If anyone concerned I can change back to MSec.

If we retrieve the Msec information from the original fwjr, then I'd be in favor of keeping the same unit for WMArchive

looks ok for me

Alan, I agree with you. Anyway, Yuyi will provide some statistics which unit make more sense. (milisec or sec for all the parameters). And we can update the patch.

MongoDB was having problem that prevented index creation and searching w/o indexes was too slow to finish.  I think using minutes are safe.

@amaltaro, @vkuznet, @yuyiguo, @juztas, As we discussed in the meeting we will keep the current keyword. readMaxMSec and still the unit is millisecond. Please review. If everyone is ok with this change I will patch the production agents.

test this please

I'm backporting this fix to the next agent release, however this one has to have the unittest fixed before it gets merged (testPerformanceSummary)

Seangchan, it was backported to the wmagent branch.
@ticoann feel free to merge it (I'm removing the labels)

I almost forgot that this test has to be fixed:
WMCore_t.FwkJobReport_t.Report_t.ReportTest:testPerformanceSummary changed from success to failure


fix(receive): don't persist receive state

Description
This allows the app on iOS to recover from https://github.com/synonymdev/bitkit/issues/1176#issuecomment-1675081087
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactoring (improving code without creating new functionality)

Tests

[ ] Detox test
[ ] Unit test
[x] No test

News, Blocks & Facts widgets are down right now, that's why e2e are failing.