Add files via upload

Updated 6/14/2022. Updated 'VNetWithGW.bicep' file for rapid progress.

Overview/Summary
Updated 6/14/2022. Updated 'VNetWithGW.bicep' file for rapid progress.
This PR CHANGES/BUILDS UPON the existing bicep file to work better with the flow of the upcoming UI changes in the AVS Accelerator.

Distinguishes New vs. Existing Virtual Network
Distinguishes New vs. Existing Gateway Subnet
Distinguishes New vs. Existing ExpressRoute Gateway
Creates a connection from New or Existing Vnet to AVS
Uses Private Cloud Objects to create connection Authorization Key

Breaking Changes

Replace me
Replace me

Testing Evidence

Replace this with any testing evidence to show that your Pull Request works/fixes as described and planned (include screenshots, if appropriate)

As part of this Pull Request I have

[ ] Checked for duplicate Pull Requests
[ ] Ensured my code/branch is up-to-date with the latest changes in the main branch
[ ] Performed testing and provided evidence.
[ ] Updated relevant and associated documentation.

Nice to meet you, @Scott @.***>,
Ah, I suspect the use of utcNow() to create a unique name/label for the “AuthKeyName” param is causing the issue. Standby on change…

would love to see how this fits into the bigger picture.
Having a checkpoint meeting with @@.> and @@.> later today. I can forward the invite you if you’d like.

I am also having trouble pushing via vscode and git bash. “Azure”  Credential Manager OAuth, SSO errors? I manually uploaded the file through the github web ui.
Best,
 --  --
Aaron A. Rhoden
Azure VMware Solution (AVS) Engineer
Mobile:<PHONE_NUMBER>
<EMAIL_ADDRESS>[Microsoft]
@.[A close up of a sign  Description automatically @. @.*** @.***
From: Scott Holden @.>
Sent: Wednesday, June 15, 2022 12:03 AM
To: Azure/Enterprise-Scale-for-AVS @.>
Cc: Aaron Rhoden @.>; Author @.>
Subject: Re: [Azure/Enterprise-Scale-for-AVS] Add files via upload (PR #115)
@ScottHolden requested changes on this pull request.
Hey, added a few notes, would love to see how this fits into the bigger picture.
Also, does this compile for you? I get the following error when compiling this module using Bicep 0.7.4:
[image]https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F20675893%2F173740361-a4cb905d-fbe5-41e0-83e2-edc9ad43c1a9.png&data=05|01|Aaron.Rhoden%40microsoft.com|87da68f4af6243e8416408da4e8c5b10|72f988bf86f141af91ab2d7cd011db47|1|0|637908661976578865|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=IsJqVLHPUqqZs8YMMFhdN8RthVyn1tRfyJ4PstnZj5Y%3D&reserved=0

In AVS-Landing-Zone/GreenField/Bicep/Modules/Networking/VNetWithGW.bicephttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FEnterprise-Scale-for-AVS%2Fpull%2F115%23discussion_r897531990&data=05|01|Aaron.Rhoden%40microsoft.com|87da68f4af6243e8416408da4e8c5b10|72f988bf86f141af91ab2d7cd011db47|1|0|637908661976578865|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=JSPf%2BuJ6sW1O7WUXjNS0SgbTPyCkGC%2BdK1PBfdISQfo%3D&reserved=0:

}

-}

-output VNetName string = VNetExists ? ExistingVNet.name : VNet.name
-output GatewayName string = VNetExists ? ExistingGateway.name : Gateway.name
-output VNetResourceId string = VNetExists ? ExistingVNet.id : VNet.id
@.***('''
+The name (string) of AVS Prvate Cloud
+This is used to:
+- More easily generate an Express Route Authoiration Key.
+- Obtain a handle on the AVS Express Route itself.
+''')
+param PrivateCloudName string

@.***('Label name for the Express Route Authorization Key. This value is NOT the key itself.')
+param AuthKeyName string = 'bicepGeneratedAuthKey-${utcNow()}'
using utcNow in a module will lead to non-idempotent behavior. (Each run will have a different value)
https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/template-functions-date#utcnowhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-resource-manager%2Ftemplates%2Ftemplate-functions-date%23utcnow&data=05|01|Aaron.Rhoden%40microsoft.com|87da68f4af6243e8416408da4e8c5b10|72f988bf86f141af91ab2d7cd011db47|1|0|637908661976578865|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=XPc4lqkFFiDqiRESkWrPnKKw0RA9bnR%2BdJEhcdAvoHk%3D&reserved=0
Recommend either constructing a value that will remain the same between runs (eg, uniqueString), or explicitly ask for a parameter.

In AVS-Landing-Zone/GreenField/Bicep/Modules/Networking/VNetWithGW.bicephttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FEnterprise-Scale-for-AVS%2Fpull%2F115%23discussion_r897533010&data=05|01|Aaron.Rhoden%40microsoft.com|87da68f4af6243e8416408da4e8c5b10|72f988bf86f141af91ab2d7cd011db47|1|0|637908661976578865|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=MT1CKgbawNJN4aukv%2BwgXreuHKUtfi35EE05Yf8YTWw%3D&reserved=0:

   properties: {

     privateIPAllocationMethod: 'Dynamic'

     subnet: {

       id: GatewaySubnetExists ? ExistingGatewaySubnet.id : NewGatewaySubnet.id

     }

     publicIPAddress: {

       id: NewGatewayPIP.id

     }

   }

 }

]

}

+}

+// Use AVS Private Cloud to Generate an Express Route Authoriation Key.
+resource ExistingPrivateCloud @.***' existing = {
There is no scope on this resource, will the parent modules be re-written to deploy into a single resource group? (ESLZ design has network components in a separate RG to the private cloud as private cloud ops require contributor on the RG, and most customers want to explicitly separate network & private cloud concerns.

In AVS-Landing-Zone/GreenField/Bicep/Modules/Networking/VNetWithGW.bicephttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FEnterprise-Scale-for-AVS%2Fpull%2F115%23discussion_r897533269&data=05|01|Aaron.Rhoden%40microsoft.com|87da68f4af6243e8416408da4e8c5b10|72f988bf86f141af91ab2d7cd011db47|1|0|637908661976578865|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=6wp%2Fl3ufbap6BMQmufRA7zIFkL8qlzlzLn8bcVfBLWQ%3D&reserved=0:

     publicIPAddress: {

       id: NewGatewayPIP.id

     }

   }

 }

]

}

+}

+// Use AVS Private Cloud to Generate an Express Route Authoriation Key.
+resource ExistingPrivateCloud @.***' existing = {

name: PrivateCloudName

+}
+// Derive the Express Route Id from the AVS Private Cloud resource.
+var AvsExpressRouteId = ExistingPrivateCloud.properties.circuit.expressRouteID
+resource ExpressRouteAuthKey @.***' = {
Likewise, what is the scope for this resource, this module is deployed to the networking RG at the moment.

In AVS-Landing-Zone/GreenField/Bicep/Modules/Networking/VNetWithGW.bicephttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FEnterprise-Scale-for-AVS%2Fpull%2F115%23discussion_r897533711&data=05|01|Aaron.Rhoden%40microsoft.com|87da68f4af6243e8416408da4e8c5b10|72f988bf86f141af91ab2d7cd011db47|1|0|637908661976578865|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=5H3t4gG2iLIgBeonrOhSnS17baf9s383uKreZbUSZ28%3D&reserved=0:

name: AuthKeyName

parent: ExistingPrivateCloud

+}
+output ExpressRouteAuthorizationKey string = ExpressRouteAuthKey.properties.expressRouteAuthorizationKey
+output ExpressRouteId string = ExistingPrivateCloud.properties.circuit.expressRouteID

+// Create Connection from vnet via Express Route Gateway to AVS Private Cloud
+resource VnetToAvsConn @.***' = {

name: VnetToAvsConnName

properties: {

connectionType: 'ExpressRoute'

authorizationKey: ExpressRouteAuthKey.properties.expressRouteAuthorizationKey

enableBgp: true

// FastPath option incurs additional costs, yet has performance benefit.

// This can be enabled later.

expressRouteGatewayBypass: false

Might be worthwhile adding to documentation, as this will also require a premium sku.

In AVS-Landing-Zone/GreenField/Bicep/Modules/Networking/VNetWithGW.bicephttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FEnterprise-Scale-for-AVS%2Fpull%2F115%23discussion_r897535449&data=05|01|Aaron.Rhoden%40microsoft.com|87da68f4af6243e8416408da4e8c5b10|72f988bf86f141af91ab2d7cd011db47|1|0|637908661976578865|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=f0UyEL6TsY4CBUvl3S92xdBh4OmIPJ4f5OOG3YzqcxY%3D&reserved=0:

]

}

+}

+// Use AVS Private Cloud to Generate an Express Route Authoriation Key.
+resource ExistingPrivateCloud @.***' existing = {

name: PrivateCloudName

+}
+// Derive the Express Route Id from the AVS Private Cloud resource.
+var AvsExpressRouteId = ExistingPrivateCloud.properties.circuit.expressRouteID
+resource ExpressRouteAuthKey @.***' = {

name: AuthKeyName

parent: ExistingPrivateCloud

+}
+output ExpressRouteAuthorizationKey string = ExpressRouteAuthKey.properties.expressRouteAuthorizationKey
+output ExpressRouteId string = ExistingPrivateCloud.properties.circuit.expressRouteID
nit: outputs at end of file
—
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FEnterprise-Scale-for-AVS%2Fpull%2F115%23pullrequestreview-1006862341&data=05|01|Aaron.Rhoden%40microsoft.com|87da68f4af6243e8416408da4e8c5b10|72f988bf86f141af91ab2d7cd011db47|1|0|637908661976578865|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Cpp%2BIi6N67Y1ZDro8PjHaZebahW9Mm3WNDvQFw5LSiU%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAXHIAGT2WN6CYDUTGO6FQETVPFPZHANCNFSM5YZ4PIYQ&data=05|01|Aaron.Rhoden%40microsoft.com|87da68f4af6243e8416408da4e8c5b10|72f988bf86f141af91ab2d7cd011db47|1|0|637908661976578865|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=0UWhtsWj%2FRgXyPBWv7llcCoiTdlhLWzSWjLje0%2BflxE%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>


[DOCFIX] Update Configuring-Alluxio-with-GCS.md

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20630/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.server.ft.journal.JournalBackupIntegrationTest.backupRestoreSingleMaster
Test FAILed.


connection.invoke example should describe how to retrieve response data

This example is incomplete.  It is missing a description of how to retrieve data from the response.
I'm pretty sure you use .then(), it it would be very helpful is this was clearer.

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

ID: 3cf283c9-5cd2-a9ff-b8c8-372d8a04356d
Version Independent ID: 729fddcf-24e4-b563-4952-a8045b231868
Content: ASP.NET Core SignalR JavaScript client
Content Source: aspnetcore/signalr/javascript-client.md
Product: aspnet-core
Technology: aspnetcore-signalr
GitHub Login: @bradygaster
Microsoft Alias: bradyg

This information is present in the linked doc:

The invoke method returns a JavaScript Promise. The Promise is resolved with the return value (if any) when the method on the server returns. If the method on the server throws an error, the Promise is rejected with the error message. Use the then and catch methods on the Promise itself to handle these cases (or await syntax).


Setting a fixed width for a Toggler with text breaks its apperance.

Is there an existing issue for this?

[X] I have searched the existing issues.

Is this issue related to iced?

[X] My hardware is compatible and my graphics drivers are up-to-date.

What happened?
Setting the width of a toggler widget to a fixed value breaks the appearance of the widget if and only if it has a text. Specifically, the "slider" becomes very thin.
SSCCE: See the Toggler with fixed width example in my iced playground.
What is the expected behavior?
The toggling part itself should look the same, independent of text and widget width.
Version
crates.io release
Operating System
Linux
Do you have any log output?
No response

The issue is fixed with the current master branch of iced. This bug can be closed with the next release.


0.14 build 1

Hi @ocefpaf
there was a mistake I made in the release of v0.14.0, in that the version number was incorrect inside the code base.
I have fixed this, but I have done this and recut the release tag, rather than making a 14.1
this means that the current recipe has the wrong sha for the tag
I have updated the recipe and indexed the build number, in the hope that this represents a sensible fix
mark

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Thanks @marqh!


[SPARK-41456][SQL] Improve the performance of try_cast

What changes were proposed in this pull request?

For try_cast and the legacy cast (cast with ANSI SQL mode off), there are conversions which has the same behaviors:

cast(string as date/timestamp/TimestampNTZ)
cast(string as double/float/decimal)

So, the try_cast can be faster if it uses the evaluation code path of the legacy cast, instead of turning into ANSI cast and catching exceptions.
Why are the changes needed?

For better performance of try_cast(string as datetime|Fractional numeric).
I also observed performance regression for the method summary() after https://github.com/apache/spark/pull/35699 under ANSI SQL mode. The try...catch is actually unnecessary.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Existing UT

@cloud-fan @HyukjinKwon @LuciferYang Thanks for the review.
Merging to master


Doesn't compile with clang

The default compiler on Mac (clang/LLVM) is not supported. (I know: make mac sort of circumvents this but in theory there should be no need to install GCC in addition.)
$ make clean

$ make
Makefile:66: "*** WARNING g++ minor version <7 ***"
mkdir -p obj_linux/src/alignment/
g++ -static-libgcc -static-libstdc++ -D__cplusplus=201103L -I"./src/" -I"/usr/include/" -I"libs/libdivsufsort-2.0.1/build/include" -I"libs/seqan-library-1.4.2/include" -DRELEASE_VERSION -O3 -fdata-sections -ffunction-sections -c -fmessage-length=0 -ffreestanding -fopenmp -m64 -std=c++11 -Werror=return-type -pthread -o obj_linux/src/alignment/myers.o src/alignment/myers.cpp
clang: warning: argument unused during compilation: '-static-libgcc'
clang: warning: argument unused during compilation: '-static-libstdc++'
clang: warning: argument unused during compilation: '-fopenmp'
mkdir -p obj_linux/src/alignment/
g++ -static-libgcc -static-libstdc++ -D__cplusplus=201103L -I"./src/" -I"/usr/include/" -I"libs/libdivsufsort-2.0.1/build/include" -I"libs/seqan-library-1.4.2/include" -DRELEASE_VERSION -O3 -fdata-sections -ffunction-sections -c -fmessage-length=0 -ffreestanding -fopenmp -m64 -std=c++11 -Werror=return-type -pthread -o obj_linux/src/alignment/cigargen.o src/alignment/cigargen.cc
clang: warning: argument unused during compilation: '-static-libgcc'
clang: warning: argument unused during compilation: '-static-libstdc++'
clang: warning: argument unused during compilation: '-fopenmp'
In file included from src/alignment/cigargen.cc:9:
./src/utility/utility_general.h:108:10: error: no member named 'iota' in namespace 'std'
    std::iota(begin(indices), end(indices), static_cast<size_t>(0));
    ~~~~~^
./src/utility/utility_general.h:120:10: error: no member named 'iota' in namespace 'std'
    std::iota(begin(indices), end(indices), static_cast<size_t>(0));
    ~~~~~^
2 errors generated.
make: *** [obj_linux/src/alignment/cigargen.o] Error 1

$ g++ --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 6.0 (clang-600.0.54) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin13.4.0
Thread model: posix

#include <numeric>

in ./src/utility/utility_general.h fixes the iota problem.
Then you get
src/graphmap/graphmap.cc:8:10: fatal error: 'omp.h' file not found
because clang doesn't support OMP yet!
Can be closed as 'won't fix' but add info to README or INSTALL


Issue #7441 Enable non-list elements in Accordions

Fixes #7441 Instead of selecting an li element, I set the selector to accordion-item. I tested using nested div elements instead of a list and it worked correctly.

See #7231
Would love to get this in before patch time.

I've added an additional check for the data attribute in the logic. I have it first check for the list element and if zero are returned, then look for the attribute. I tested it using two separate accordion components, one using nested div and the other using ul and li


[ListItem] rightIconButton doesn't prevent ripple on mobile

It works in desktop without the ripple.
Here is an example:

Visit https://mtg.zone (site only works on chrome and safari because I use websql)
Make your screen small so you see the icon on the top right menu
Add a card to deck
Click on the top right icon
Tap (with a touch event) on the zoom button to trigger the ripple

Touch tap

Mouse click

Hi @EloB I tried to reproduce this in desktop using step you described but for me it's working perfectly fine. I'm using Chrome (Version: 48.0.2564.116)
I've also checked in Safari(Version: 9.0.3) working fine there too.
Here's the Mouse Click example:

@heetvachhani What happens when you use chrome dev tools to simulate a touch?
That reproduces it for me: http://g.recordit.co/CxJkQbaWuD.gif

Yes that reproduced for me :grin:

@EloB : I'm trying to fix this and was trying to reproduce it. So I wanted to understand the structure of the list that you are using.
Can you shed some light on this. Check this page from our docs site and see if you find issue with the nested lists.

@EloB :  So, I tried reproducing the issue you are having on the docs page and I was able to do it on the nested list example which looks similar to your use case.
I noticed the nested list-item did not let the touch ripple bubble up to the list-item parent. However the parent list-item labelled "inbox" behaved in the same way as your use-case.

I added the prop  disabled={true} to the parent list-item labelled "inbox" and that solved the problem. The ripple can be seen on touch only but not on click of the list-item since its disabled. I bet the problem with your use-case is similar.

Let me know, if this solves the problem.
@nathanmarks : Is this an bug in our docs page? I see it as more of a use-case thing.

Im getting the bug on the docs as well.

Do you have emulate touch screen in devtools?

I need to be able to click the list and also the rightButtonElement. So disable it will only make the rightButtonElement to work right?

I think the way ListItem triggers the ripples are kind of broken. On a phone it triggers the ripples everytime you touch them. Very annoying when you scroll the page. Maybe this is another bug. Should I make another issue with that? Try this on a phone and scroll down the page: https://mtg.zone/#/sets

@EloB : Yes. I did enable touch on devtools. Thank you for explaining your use-case.
Yes you are right. The list-item won't be clickable but the icon will be. I misunderstood from your screengrab. Now that I know what you are trying to achieve, let me try and see if it is fixable.
Also, i checked your website on phone. The list-item, is not clickable when I tried it through my phone. only the right-icon is clickable.

The clicking the ListItem it should decrease the left avatar number by one.

The clicking the ListItem it should decrease the left avatar number by one.

Doesn't work in mobile chrome browser. It closes the side nav when I click on the list-item. Anyway, Let me see what I can do.

Oh that's because its the last item if you have more than one card in the deck. Then you will see that is decreases.

@EloB : Yeah I did see that. Thanks!

Thanks for solving this issue! :+1:

@Elob : No worries man. Happy to help! Best of luck with your project.


Make $hp point to the first available byte, instead of the one before it

See https://github.com/FuelLabs/fuel-vm/pull/377

Are we reverting some of the changes made in https://github.com/FuelLabs/fuel-specs/pull/464


user-specified summary has extra paragraph tag under some conditions

Not sure if this is related to #1217 or not, so I'm opening a new issue. I observed this behavior in 0.19, and still see it in 0.21.
Consider the following post bodies and the summary each yields:
Test A
Test A.

- Test list

Next test paragraph?

Final test paragraph.

Yields:
"
Test A.

Test list

Next test paragraph?

"

Test B
Test B.

- Test list

Next test paragraph?

Final test paragraph.

Yields:
"
Test B.

Test list

Next test paragraph?

"

Test C
Test C.

- Test list

Final test paragraph.

Yields:
"
Test C.

Test list

"

Test D
Test D.

- Test list

Final test paragraph.

Yields:
""

Is (or should be) included in whatever tests will close #3349


Support linking to homepage in docs

This feature is an end-to-end docs feature:
1/ FDR (the docs backend) should support taking in homepage link
2/ Update the docs-config fern definition to take homepage link
2a/ Make sure you register the homepage link with fdr using the SDK
3/ Consume homepage link on the frontend so that when a user clicks on the logo, they are redirected to homepage

Done.


Setup of shielded connection and restrictions

Hello,
Have you looked for an answer?
We have looked through the documentation for the command line tools and the code.
Question/Issue:
Please help with the following.
[Q1]
Is there a command to instruct optiga that read/write access to a data object should only happen if shielded connection is established? Or is this only achievable through changing the metadata for the data object? If so, what metadata should be written to the data object through the command bin/trustm_metadata?
We have only changed the OPTIGA_COMMS_DEFAULT_PROTECTION_LEVEL, and run the scripts/misc/write_default_shared_secret
When the restrictions are setup, how do we tell optiga that our local device knows the secret? We are currently using a Raspberry pi as our local device.
[Q2]
Is there a command to link a monotonic counter to one of the RSA key objects, to ensure the maximum number of usage? Will linking a counter make it read-only or is that an option needed to be set?
We use an identical setup to the one shown in documentation.
Thanks for the help

Hi,
Thank you for those references.


Adding theme override support

Platforms Impacted

[x] iOS
[ ] macOS

Description of changes
This change adds the capability for the client app to override any token defined in the YAML file.
There are many aspects associated with this change:
1. Compatibility with the ColorProviding protocol currently used by client apps:
The current version of FluentUI allows client app to override the app brand color (along with its tint and shade variations). This is done through the ColorProviding protocol that needs to be implemented by the apps willing to override those colors.
The ColorProviding is passed through the Colors.setProvider func which also allows associating a specific instance of the ColorProviding to a given UIWindow instance of the app (multi window apps can specify different brand colors per window).
This change adds a call to the StylesheetManager creating a new instance of the FluentUIStyle class (the class that defines all the tokens defined in the YAML file) and overrides the brand color variations with the values provided by the ColorProviding instance passed as a parameter
2. SwiftUI Environment Values:
SwiftUI provides support for Environment Values which are in a nutshell the ability to define values that are shared across items in the view hierarchy. The view requesting that value will get the default value or the value that was set to its closest parent view in a hierarchical override fashion.
We are creating a theme environment value that will hold a reference to the FluentUIStyle instance that represents the theme applied to that SwiftUI view which represents the FluentUI Vnext control.
3. UIKit support (using the UIWindow to get to the correct theme:
Because FluentUI Vnext controls support interoperability for being added to UIKit view hierarchies (UIWindow/UIView), changes to the wrapper classes needed to be made in order to allow the calling code to pass a specific theme as well as providing the UIWindow associated to the UIHostingController's view property so that the tokens class of that control is able to retrieve the correct FluentUIStyle instance.
Demo
The videos below demonstrate the Theme overriding per window. By tapping the override button, the Green theme is set for all the FluentUI Vnext controls being used in that UIWindow hierarchy.
The purple squared buttons and purple avatars below are not affected by the window theme override because they are set to use a specific override of the FluentUIStyle, which takes precedence over the window theme.
https://user-images.githubusercontent.com/68076145/103688756-28294e00-4f47-11eb-9bc3-b02041f6e509.mov
https://user-images.githubusercontent.com/68076145/103689133-bef60a80-4f47-11eb-9401-9fd8531e7fa7.mov
Pull request checklist
This PR has considered:

[x] Light and Dark appearances
[ ] VoiceOver and Keyboard Accessibility
[ ] Internationalization and Right to Left layouts
[ ] Different resolutions (1x, 2x, 3x)
[ ] Size classes and window sizes (iPhone vs iPad, notched devices, multitasking, different window sizes, etc)

Microsoft Reviewers: Open in CodeFlow

Will the checked-in Drawer + List be okay with the AppearanceProxyType changes?

Will the checked-in Drawer + List be okay with the AppearanceProxyType changes?

Will the checked-in Drawer + List be okay with the AppearanceProxyType changes?

It shouldn't break the build but there's still work that needs to be done on the List and Drawer controls to ensure they'll adhere to the theming proposed on this review. I do plan to make those changes once this is merged.

Will the checked-in Drawer + List be okay with the AppearanceProxyType changes?

It shouldn't break the build but there's still work that needs to be done on the List and Drawer controls to ensure they'll adhere to the theming proposed on this review. I do plan to make those changes once this is merged.


Tekton Type system scope and design doc

Tekton Types Design Doc (starter)
Type system and any methods of extensibility to consider on top of the Types (including as-plugin or as an external project entirely). There are already JSON Schema validators. Can Tekton let you provide your own validator, or should Tekton ignore validations? This has somewhat of an impact on what happens in Arrays, Templates, and reuse of Pipelines/Resources/Tasks
Tracking discussion and followup on Types for Tekton.
Is there anything limiting reuse if Types are arbitrary strings that simply need to match? How would our intended Duck Typing of resources function? Duck Typing of parameters?
Specifically interesting is the question of type validation. Not interested to re-implement any existing language for type validation. Need to leave the doors open to a 3rd party providing a rich system of type validations for Pipeline Distributors and 3rd-party product creators that rely on Tekton under-the-hood.
Meeting notes (copied on 2019-07-10 at 17:08 GMT)   :
"Would we want Task authors to be able to add further validation? E.g. the string must be X chars or less, must be at least 50
Would want ppl to be able to use Tasks right out of the box, ideally should contain the validation needed?
Some ideas:
Can look at the type system that Puppet (Lyra) is using
People will make types as complex as they possibly can!
Would be cool to make a proof of concept that uses this
pcore library from lyra: https://github.com/lyraproj/pcore
example workflow with types: https://github.com/ahpook/lyra-local/blob/master/workflows/azure_wordpress.yaml
JSON schema?
Don’t want to create a new validation language!
Could also look into OPA language rego"
https://www.openpolicyagent.org/
https://www.openpolicyagent.org/docs/latest/how-do-i-write-policies/
"Simon has tackled this problem a few times as well, and Eric can share the puppet approach"
Intention is to list out a few alternative options in a design doc for review at next week's meeting (7/17), along with recommended choice
@ Eric Sorenson and @ Simon Kaegi

@ahpook @skaegi

reading https://puppet.com/blog/lyra-brings-puppet-concepts-and-more-cloud-native

reading https://blog.openpolicyagent.org/securing-the-kubernetes-api-with-open-policy-agent-ce93af0552c3

filed https://github.com/tektoncd/pipeline/issues/1078 and https://github.com/tektoncd/pipeline/issues/1079

created https://docs.google.com/document/d/1pH9wyVaGVLjnhi5tOa2TSq7d1j5HTTeCbCmosRo4jWE

asked about Types again at the weekly working group meeting
PipelineResources may turn into updates to the TaskRun/PipelineRun (hanging the results from the run directly), as one potential future direction. Related conversation in #544

I've done some work on a more go-like type system "dgo" (dynamic go) where the type syntax is designed to be close to the go syntax. If something like pcore was of interest, then I think this can be even more so: https://github.com/lyraproj/dgo

Can this issue be closed in favor of https://github.com/tektoncd/pipeline/issues/1393? @bobcatfish @skaegi ?

At least for built-in type validation in Tekton I'd suggest that we do not want to stray far from the platform and follow what api machinery is suggesting -- e.g. open api v3 / json schema / jsonpath -- and essentially follow the versions and support what they spec.
This does not prevent other forms of validation, it just means at least for now it must be layer above Tekton. For example OPA is handled at a higher layer for us. We might eventually support pluggable custom validators but I think we could still do that in the context of JSON schema.
@dibyom let's finalize our thoughts for beta in #1393 and then if we're happy I can open a separate issue that breaks out the schema and jsonpath support and we could continue the typing discussion there. wdyt?

Sounds good to me @skaegi
I'll close out this issue and we can continue the discussion in #1393
/close


Import an account

Hey Jorge, sending this for your review!
The article is missing the Mobile section for Keycard, as the designs are still in progress. I still think we can publish this since the desktop version is ready.

The article is missing the Mobile section for Keycard

Checking @shamisem; reviewing it now – To keep track of what's missing, please, create a new 'update' issue in your GitHub project board with a note about what's missing now and needs to be added in the future update. Thanks.


fixbug: #1076

Features
fixbug: #1076

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 81.16%. Comparing base (933a242) to head (89b263a).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1080      +/-   ##
==========================================
- Coverage   81.35%   81.16%   -0.19%
==========================================
  Files         248      248
  Lines       13883    13885       +2
==========================================
- Hits        11294    11270      -24
- Misses       2589     2615      +26

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Feature/code coverage merge

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Please also include any acceptance criteria if you have any.

Change A
Change B

Type of change
Please delete options that are not relevant.

[ ] 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)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

[ ] Test A
[ ] Test B

Checklist:

[ ] My code follows the javascript standard style
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation and versioning
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have rebased onto master and there are no code conflicts

Some context in the description about what the change is and how it's been tested etc would be helpful


Change ipxe's undionly.kpxe to syslinux's undionly.kkpxe

it's the same with master's PR https://github.com/RackHD/on-http/pull/91
undionly.kpxe from ipxe is not the original gPXE undionly.kkpxe from syslinux which has been validated for installing ESXi on multiple platforms, correct it here. This will fix the chainload failure issue when installing ESXi OS

+1

:+1:

Merge this due to the urgency of 1.1.x, and We identify this PR should not be the cause of Jenkins test failure.


Update README.md

Added information from contents of homology modelling slides to main readme file.

Can't seem to indent the bullet points more, @RMeli maybe one to fix if you can work it out.
Otherwise lgtm!

Not sure it's possible...


Failed to update cluster to enable mTLS with cert-manager

Modify the cluster CRD to enable mTLS.
Pods failed to start due to secrets not found
FailedMount
MountVolume.SetUp failed for volume "worker-mtls-certificate" : secret "temporal-tok-worker-mtls-certificate" not found
FailedMount
MountVolume.SetUp failed for volume "internode-certificate" : secret "temporal-tok-internode-certificate" not found
FailedMount
MountVolume.SetUp failed for volume "frontend-certificate" : secret "temporal-tok-frontend-certificate" not found
FailedMount
MountVolume.SetUp failed for volume "frontend-intermediate-ca-certificate" : secret "temporal-tok-frontend-intermediate-ca-certificate" not found

Despite they were already generated by cert-manager
kubectl get secrets
NAME                                                 TYPE                             DATA   AGE
temporal-tok-admintools-mtls-certificate             kubernetes.io/tls                3      18m
temporal-tok-aws-dev1-db-password                    Opaque                           1      6d18h
temporal-tok-aws-dev1-ro-db-password                 Opaque                           1      6d18h
temporal-tok-aws-dev1-rw-db-password                 Opaque                           1      6d18h
temporal-tok-frontend-certificate                    kubernetes.io/tls                3      18m
temporal-tok-frontend-intermediate-ca-certificate    kubernetes.io/tls                3      18m
temporal-tok-internode-certificate                   kubernetes.io/tls                3      18m
temporal-tok-internode-intermediate-ca-certificate   kubernetes.io/tls                3      18m
temporal-tok-root-ca-certificate                     kubernetes.io/tls                3      18m
temporal-tok-ui-mtls-certificate                     kubernetes.io/tls                3      18m
temporal-tok-worker-mtls-certificate                 kubernetes.io/tls                3      18m

Deleting the cluster and recreate works though.

Hi @yujunz !
Could you please give me some reproducing steps ?
I tried on my side an it worked. I created a new cluster using this example where I removed the spec.mtls section.
Once the cluster has been created I restored the mTLS section and it worked well.

I am not able to reproduce this either.  I provisioned the cluster with this:
apiVersion: temporal.io/v1beta1
kind: TemporalCluster
metadata:
  name: temporal
  namespace: temporal-mtls-repro
spec:
  version: 1.23.0
  numHistoryShards: 8
  persistence:
    defaultStore:
      sql:
        user: temporal
        pluginName: postgres
        databaseName: temporal
        connectAddr: temporal-db-rw:5432
        connectProtocol: tcp
      passwordSecretRef:
        name: temporal-db-credentials
        key: password
    visibilityStore:
      sql:
        user: temporal
        pluginName: postgres
        databaseName: temporal_visibility
        connectAddr: temporal-db-rw:5432
        connectProtocol: tcp
      passwordSecretRef:
        name: temporal-db-credentials
        key: password
  ui:
    enabled: true

I waited for the cluster to become healthy in ArgoCD.  I checked the UI and everything looked healthy as well.  I pushed another commit to add this section and re-synced in ArgoCD:
mTLS:
  provider: cert-manager
  internode:
    enabled: true
  frontend:
    enabled: true
  certificatesDuration:
    clientCertificates: 1h0m0s
    frontendCertificate: 1h0m0s
    intermediateCAsCertificates: 1h30m0s
    internodeCertificate: 1h0m0s
    rootCACertificate: 2h0m0s
  renewBefore: 55m0s

The Certificate objects took ~20s or so on my homelab cluster and all the Temporal deployments completed as soon as the Certificate objects were marked valid.  I didn't have any clients connected, but it seemed like a pretty seamless change.  I vote to close this issue and re-open if we have a reproduction.


Add Kotlin 1.7.0-RC2 to tested versions

See https://github.com/JetBrains/kotlin/releases/tag/v1.7.0-RC and https://github.com/JetBrains/kotlin/releases/tag/v1.7.0-RC2
Discovered issues:

~KT-52448, in fact https://github.com/gradle/gradle/issues/20550~
False positive
With the kotlinjs plugin removed, we should add a smoke test for the new javascript support
Opened https://github.com/gradle/gradle/issues/20920

@bot-gradle test AST

OK, I've already triggered the following builds for you:

AllSmokeTestsPullRequestFeedback build

@bot-gradle test AST

OK, I've already triggered the following builds for you:

AllSmokeTestsPullRequestFeedback build

@bot-gradle test AST

OK, I've already triggered the following builds for you:

AllSmokeTestsPullRequestFeedback build

@bot-gradle test AST

OK, I've already triggered the following builds for you:

AllSmokeTestsPullRequestFeedback build

OK, I've already triggered the following builds for you:

AllSmokeTestsPullRequestFeedback build

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


Add "latest" version of API docs to provide more stable external link targets

Currently, links to API docs include the version in the URL. Additionally, the website only includes the current version. That means that any external links to the API docs break each time we update to a new version.
This PR adds a latest symlink so that external links can refer to (for example) .../kubernetes-api/latest/#pod-v1-core instead of .../kubernetes-api/v1.18/#pod-v1-core and then as long as the reference target #pod-v1-core lives on from version to version, the link would continue to work.

Preview available at:
https://deploy-preview-21858--kubernetes-io-master-staging.netlify.app/docs/reference/generated/kubernetes-api/latest/
Looks like it doesn't work. Perhaps the web server doesn't follow symlinks. Investigating.

Building sites … WARN 2020/06/17 18:02:39 Unsupported symlink found in "/opt/build/repo/static/docs/reference/generated/kubernetes-api/latest", skipping.

So it won't work. I'll try to think of an alternative method to get the same or similar functionality.


[Doc] Add pulsar-admin command and fix inconsistencies

Fix https://github.com/apache/pulsar/issues/5345

@Jennifer88huang could you please help review? Thank you

run java8 tests

@codelipenghui thank you

run cpp tests

@aahmed-se thank you


Adding support for F#

Issue
Hi,
What is required to add support for a new language (F#, in this case)?  Is it just a tree-sitter grammar?  Or is there more beyond that?  If the former, there is an implementation here: https://github.com/ionide/tree-sitter-fsharp
Thank you!
Version and model info
No response

Thanks for trying aider and filing this issue.
Aider will probably work well with F# already. Have you tried it?

Thanks for trying aider and filing this issue. This doc may be helpful:
https://aider.chat/docs/languages.html#how-to-add-support-for-another-language

I'm going to close this issue for now, but feel free to add a comment here and I will re-open or file a new issue any time.


Build failed due to clean-css

Hi,
I deployed successfuly an Angular 8 web application 3 months ago.
Today, I tried to push a new version but the build failed. But it's weird because I didn't add any dependencies
Here is the message :
21:48:20.496  	TypeError: value.replace is not a function
21:48:20.496  	    at tidyAtRule (/vercel/workpath0/node_modules/clean-css/lib/optimizer/level-1/tidy-at-rule.js:3:6)
21:48:20.496  	    at level1Optimize (/vercel/workpath0/node_modules/clean-css/lib/optimizer/level-1/optimize.js:639:47)
21:48:20.496  	    at optimize (/vercel/workpath0/node_modules/clean-css/lib/clean.js:144:5)
21:48:20.496  	    at /vercel/workpath0/node_modules/clean-css/lib/clean.js:120:29
21:48:20.496  	    at /vercel/workpath0/node_modules/clean-css/lib/reader/read-sources.js:26:64
21:48:20.496  	    at loadOriginalSources (/vercel/workpath0/node_modules/clean-css/lib/reader/load-original-sources.js:26:5)
21:48:20.496  	    at /vercel/workpath0/node_modules/clean-css/lib/reader/read-sources.js:26:14
21:48:20.496  	    at applySourceMaps (/vercel/workpath0/node_modules/clean-css/lib/reader/apply-source-maps.js:34:5)
21:48:20.496  	    at /vercel/workpath0/node_modules/clean-css/lib/reader/read-sources.js:25:12
21:48:20.496  	    at fromStyles (/vercel/workpath0/node_modules/clean-css/lib/reader/read-sources.js:152:5)
21:48:20.496  	    at fromString (/vercel/workpath0/node_modules/clean-css/lib/reader/read-sources.js:48:10)
21:48:20.496  	    at doReadSources (/vercel/workpath0/node_modules/clean-css/lib/reader/read-sources.js:33:12)
21:48:20.496  	    at readSources (/vercel/workpath0/node_modules/clean-css/lib/reader/read-sources.js:24:10)
21:48:20.496  	    at /vercel/workpath0/node_modules/clean-css/lib/clean.js:115:12
21:48:20.497  	    at processTicksAndRejections (internal/process/task_queues.js:79:11)
21:48:20.529  	npm ERR! code ELIFECYCLE
21:48:20.529  	npm ERR! errno 1
21:48:20.530  	npm ERR<EMAIL_ADDRESS>build: `ng build --prod`
21:48:20.530  	npm ERR! Exit status 1
21:48:20.530  	npm ERR!
21:48:20.530  	npm ERR! Failed at the<EMAIL_ADDRESS>build script.
21:48:20.531  	npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
21:48:20.546  	npm ERR!  Was it code-base specific? Placing the answer here, even if not entirely relevant to the library, could help future programmers with issues that they are struggling with.


RFC:  bump aws-embedded-metrics from 1.0.6 to 4.0.1

Key information

RFC PR: (leave this empty)
Related issue(s), if known: https://github.com/awslabs/aws-lambda-powertools-java/pull/943
Area: (i.e. Tracer, Metrics, Logger, etc.) Metric
Meet tenets: (Yes/no)

Summary

There are some work required to bump aws-embedded-metrics to 4.0.1

Motivation
I had a quick look on the issue that appeared when dependabot bumped aws-embedded-metrics to 4.0.1.
I looks that in latest version some components of aws-embedded-metrics throw checked exceptions which are not handled in the app. I will create a PR showing the issue and fix.

Work on this would be much appreciated, I'm running into these excessive socket error logs upon using MetricsUtils.withSingleMetric when running unit tests, which I've been suggested can be reduced by bumping aws-embedded-metrics to > 2.x.
ERROR TCPClient:43 - Failed to connect to the socket due to the exception:
java.net.SocketException: Socket closed
    at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:1.8.0_332]
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[?:1.8.0_332]
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[?:1.8.0_332]
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[?:1.8.0_332]
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[?:1.8.0_332]
    at java.net.Socket.connect(Socket.java:607) ~[?:1.8.0_332]
    at java.net.Socket.connect(Socket.java:556) ~[?:1.8.0_332]
    at software.amazon.cloudwatchlogs.emf.sinks.TCPClient.connect(TCPClient.java:40) ~[aws-embedded-metrics-1.0.6.jar:1.0.6]
    at software.amazon.cloudwatchlogs.emf.sinks.TCPClient.sendMessage(TCPClient.java:63) ~[aws-embedded-metrics-1.0.6.jar:1.0.6]
    at software.amazon.cloudwatchlogs.emf.sinks.AgentSink.accept(AgentSink.java:52) ~[aws-embedded-metrics-1.0.6.jar:1.0.6]
    at software.amazon.cloudwatchlogs.emf.logger.MetricsLogger.flush(MetricsLogger.java:66) ~[aws-embedded-metrics-1.0.6.jar:1.0.6]
    at software.amazon.lambda.powertools.metrics.MetricsUtils.withSingleMetric(MetricsUtils.java:120) ~[powertools-metrics-1.12.2.jar:?]

I would recommend using v4.0.3 instead as there is a known bug in v4.0.1 which affects most users.

This introduces breaking changes:
A simple metricsLogger.putMetric(...) now throws checked exception (InvalidMetricException).
This should be released in a v2 of lambda-powertools-metrics.

I'm going to close this issue because we have a much clearer issue and reason why we want to upgrade now. #1041 requires v4.x and gives an additional feature we want to support.


Add the ability to get the display's refresh rate

This might come in handy for frame timing calculations. Tested on Wayland and X11, works fine.

Thanks for the PR 🙂


[Feature Request] avoid change directory when use :LeaderfFile

Currently, when run command like LeaderfFile ~/vimwiki and open the file, the pwd will be changed to the directory of the file.
Could the pwd be kept without change when use LeaderfFile?
Thanks!

https://github.com/Yggdroot/LeaderF/blob/b9146ddf617c1041adec23b762a540a2f657d2cd/doc/leaderf.txt#L552-L556

Hi @Yggdroot ,
After add the configuration let g:Lf_NoChdir = 1, following error will occur when run :LeaderfFile ~/vimwiki:

What is the output of :echo g:Lf_Debug_Cmd  and pwd ?

The result of :echo g:Lf_Debug_Cmd is:
git ls-files --recurse-submodules "/Users/hbliu/vimwiki" && git ls-files --others --exclude-standard  "/Users/hbliu/vimwiki"

And the pwd is /Users/hbliu

What is the output of echo g:Lf_WorkingDirectoryMode ?

It's c.

I think this issue is not related to LeaderF, it is an issue of git. You can try git ls-files --recurse-submodules "/Users/hbliu/vimwiki" && git ls-files --others --exclude-standard  "/Users/hbliu/vimwiki" in the comandline to figure out the root cause.

Why git is used since ~/vimwiki is not a git repo?

When let g:Lf_NoChdir = 0, the command :LeaderfFile ~/vimwiki  could work.

What is the output of :echo g:Lf_Debug_Cmd if let g:Lf_NoChdir = 0` ?

Why git is used since ~/vimwiki is not a git repo?

It is because there is a .git directory in its ancestor path. So ~ is a git repo ?

What is the output of :echo g:Lf_Debug_Cmd if let g:Lf_NoChdir = 0` ?

The output is git ls-files --recurse-submodules "/Users/hbliu/.dotfiles/private/link/vimwiki" && git ls-files --others --exclude-standard  "/Users/hbliu/.dotfiles/private/link/vimwiki" .

It is because there is a .git directory in its ancestor path. So ~ is a git repo ?

~ is not a git repo. In fact, ~/vimwiki is a link to /Users/hbliu/.dotfiles/private/link/vimwiki and /Users/hbliu/.dotfiles/private is a git repo.

Do you know the root cause now?
Run git ls-files --recurse-submodules "/Users/hbliu/.dotfiles/private/link/vimwiki" && git ls-files --others --exclude-standard "/Users/hbliu/.dotfiles/private/link/vimwiki" at /Users/hbliu and ~/vimwiki respectively,  I think you can find the reason.

Using following cmd should work:
cmd = '(cd %s && git ls-files %s && git ls-files --others %s %s) | sed "s,^,%s/," ' % (dir, recurse_submodules, no_ignore, ignore, dir)

The let g:Lf_UseVersionControlTool = 0 setting could also solve my problem.


Run lint in all folders

Closes #34
Summary
Added all the folders containing python scripts to be inspected by lint
Local Tests
Run tox
End-to-End Tests
N/A

I added all the folders to be inspected by lint but I did not notice anything that needed to be updated.

I did not notice anything that needed to be updated. I added all the missing python files to be inspected by the linter.

Yes, appreciated you double checking @Alopalao, I turns out I had an older branch that was with py39 for the local dev of this NApp. But, I'm glad you took the opportunity to also fix the adjacent parts here.


502 Bad Gateway

Getting this error since today :
Logger: homeassistant.config_entries
Source: custom_components/panasonic_cc/__init__.py:79
Integration: Panasonic Comfort Cloud (documentation)
First occurred: 8:32:42 (1 occurrences)
Last logged: 8:32:42

Error setting up entry for panasonic_cc
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 304, in async_setup
    result = await component.async_setup_entry(hass, self)  # type: ignore
  File "/config/custom_components/panasonic_cc/__init__.py", line 79, in async_setup_entry
    devices = await hass.async_add_executor_job(api.get_devices)
  File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 52, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.9/site-packages/pcomfortcloud/session.py", line 172, in get_devices
    self.login()
  File "/usr/local/lib/python3.9/site-packages/pcomfortcloud/session.py", line 99, in login
    self._create_token()
  File "/usr/local/lib/python3.9/site-packages/pcomfortcloud/session.py", line 132, in _create_token
    raise ResponseError(response.status_code, response.text)
pcomfortcloud.session.ResponseError: Invalid response, status code: 502 - Data:
<title>502 Bad Gateway</title>

502 Bad Gateway

I think it's a server side problem. Even Panasonic Android app didn't work.
Now both (HA integration and app) work!

Indeed, working again... Many thanks


Means to add alt text when posting images

There is a means to include alt text for uploaded images in the Twitter client API
Alt text support for Twitter Cards and the REST API

A good suggestion, I didn't know this existed.
I wish Twitter hadn't split everything up via separate endpoints though, makes the time it takes to actually post a tweet longer.
Will need to take some time to consider how to design this, for describing alt text every time I want to post an image gets really cumbersome.


x/build/internal/releasetargets: distribute official binaries for linux/riscv64

What version of Go are you using (go version)?
1.18
(I got stressed out between the 6 bug templates and 6 external communities to discuss Go topics so here goes nothing.)
The only tracking issues I can find for riscv64 seem to be closed:

https://github.com/golang/go/issues/27532
https://github.com/golang/go/issues/36641

However, https://go.dev/dl/?mode=json&include=all does not include a bootstrap for GOOS=linux GOARCH=riscv64.
NixOS and nixpkgs currently use this json and the pre-built bootstraps for some/most Go packaging support, so this would likely help us get riscv64 support going a bit further.
Alternatively, maybe there's an unofficial builder out there producing builds that I could at least experiment with?
Thanks!

@golang/release

This is done as part of #53862.
Binary releases for the linux/riscv64 port will be available starting with Go 1.21.
For example, see go1.21rc2.linux-riscv64.tar.gz at https://go.dev/dl/#go1.21rc2.
(It happens to also be the port visible in the image at https://twitter.com/golang/status/1671582916567080962.)


Stuck at Load table relations

Description
I'm having an issue when trying to query a specific table. All other tables works normaly. The odd is that usign MySql workbench it works normally, but in dbeaver it get stucks at "Load Table relations" and never end loading.

DBeaver Version
24.1.4
Operating System
Ubuntu 24.04 LTS
Database and driver
MariaDB
Steps to reproduce

Try to execute the query SELECT * FROM user_profiles;

Additional context

It's not using a SSH tunnel but it is on a VPN connect
Using MySql Workbench I can query normally

Please provide a minimal example DDL to reproduce the issue.

@MarceloZapatta
As a workaround, you can turn on the following setting Connection configuration->Metadata->Do not read tables information in SQL and data editors. Does it help?

@MashaKorax I wasn't able to generate a minimal example DDL because at my local database works normally.
@E1izabeth Thanks! Now at least I'm able to query the results. This kinda solve my problem I'm having, but look's like is something related with the indexes, if I try to see the menu "Foreign Keys" at least one time it hangs on a infinite loading in also any other menu. And seems like a infinite loop because eventually it makes dbeaver crashes

The table just have a FK that points to the same table. The odd that at my localhost is working normally:

Table DDL:
CREATE TABLE `user_profiles` (
  `user_id` bigint(20) unsigned NOT NULL DEFAULT '0',
  `email_alias` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `group` int(10) unsigned DEFAULT NULL,
  `mls_id` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  `external_vendor_id` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `default_lender` bigint(20) unsigned DEFAULT NULL,
  `status` int(10) unsigned NOT NULL DEFAULT '1',
  `email` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  PRIMARY KEY (`user_id`),
  UNIQUE KEY `email_alias_unique` (`email_alias`),
  KEY `group` (`group`),
  KEY `twilio_number` (`tracked_phone`),
  KEY `work_phone` (`work_phone`),
  KEY `mls_id` (`mls_id`),
  KEY `external_vendor_id` (`external_vendor_id`),
  KEY `user_profiles_default_lender_foreign` (`default_lender`),
  KEY `status` (`status`) USING BTREE,
  KEY `user_email` (`email`),
  CONSTRAINT `user_profiles_default_lender_foreign` FOREIGN KEY (`default_lender`) REFERENCES `user_profiles` (`user_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci

Hello @MarceloZapatta,
Are you executing your query with auto-commit enabled? Do you have pending transactions?

@ShadelessFox yes it's with auto-commit enabled

Thank you for your report.
Unfortunately, we can't reproduce this issue, but it seems that this is related to a FK that points to the same table


about cuda version

does cuda need to be 11.3? I use 11.7 cuda and corresponding pytorch, but now it seems have some problems with compling thirdparty, is it related to the cuda version?

I tried with cuda 11.7 + torch 1.13.1 and successfully run setup.py, but when running demo undefined symbol occurred(i guess the problem is with libc10). Did you solve the problem eventually? Thanks very much!


Strip undefined values from props to avoid unintentionally shadowing defaults

Ran into a problem when creating a new layer in which passing props that are undefined shadow defaults, requiring application-layer or CompositeLayers to run checks to avoid passing a prop at all if it's undefined.
E.g.:
class FooLayer extends Layer {
  // ...
  renderLayers() {
    const valueNeededForRender = this.props.someAccessor();
    // ...
  }
}
FooLayer.defaultProps = {
  someAccessor: () => true
};

// application code:
// ...
render() {
  // `someAccessor` not passed in or defined due to some valid condition/use case...
  const {someAccessor} = this.props;
  new FooLayer({
    someAccessor
  });
}

In this case, the expectation is that omitting someAccessor will allow FooLayer to fall back to its default definition for someAccessor. Instead, the default is shadowed by the undefined value passed as a prop, causing a runtime error.
This PR fixes that case, but I can easily imagine it will surface other bugs in which that shadowing is unintentionally expected / accounted for and unshadowing will cause other errors. So...not sure how best to proceed, but figured I'd put this out to see what you think.

New layers are instantiated and old ones disposed every frame, so this is on the critical path for performance. In that light, this PR could be refactored to avoid creating an array (Object.keys()) and an object (.reduce()). It's also critical to benchmark the performance impact on layer creation; for this, we can use npm run bench.
Note that this PR came from my experience with React. This SO post highlights React's handling of undefined props vs. defaultProps and this thread contains a conversation between React devs about the intentionality of that handling.
I suggest we sit on this for a bit to see if the risk is worth the reward --  it's a relatively small ergonomic improvement and may be mostly inconsequential. But might also be useful.
Side note: this would also allow application developers to intentionally fall back to layer defaults via this pattern:
new FooLayer({
  someProp: expectedValue || undefined
});

(Some of this echoes @ibgreen's comments above, which landed while I was writing this 😉 )

Operation
no removal
for-in removal
keys + filter + reduce removal

color#parseColor (string)
(±2.41%) 933,494
(±2.88%) 938,705
(±2.70%) 964,603

color#parseColor (3 element array)
(±5.03%) 29,357,109
(±1.15%) 34,774,314
(±2.00%) 32,609,815

ScatterplotLayer#construct
(±1.76%) 238,476
(±0.99%) 290,293
(±1.77%) 193,576

ChoroplethLayer#construct
(±1.61%) 353,570
(±1.59%) 393,048
(±1.42%) 255,971

PolygonLayer#construct
(±2.11%) 170,612
(±2.28%) 137,970
(±1.70%) 153,315

ScatterplotLayer#initialize
(±3.02%) 147
(±2.26%) 154
(±2.58%) 154

PathLayer#initialize
(±4.52%) 20.65
(±3.34%) 21.35
(±2.52%) 21.73

ChoroplethLayer#initialize
(±5.19%) 4.78
(±5.61%) 5.46
(±3.96%) 5.59

PolygonLayer#initialize (flat)
(±1.54%) 13,066
(±1.45%) 11,979
(±0.98%) 13,427

PolygonLayer#initialize (extruded)
(±5.95%) 10,382
(±1.97%) 11,893
(±3.64%) 11,479

PolygonLayer#initialize (wireframe)
(±7.62%) 11,133
(±3.49%) 10,615
(±2.80%) 11,375

ExtrudedChoroplethLayer64#initialize
(±3.19%) 21,453
(±3.38%) 20,115
(±4.49%) 16,378

Thanks for collecting these.
It is mainly three Laye#construct cases that are of interest here.
Interestingly, your (optimized) change seems to increase speed in 2 of 3 cases, which seems promising. (Note that there is a bit of run-to-run variability in these benchmarks due to unpredictable machine load.)
It would be good to add test and benchmark cases for more layers (ideally driven by a table), and for various numbers of props (a short list of props will of course be faster to resolve than a longer list).

Closing for now as benefits are debated and perf impact is indeterminate.


core/radvd Slightly Reorganise UI for disabling of DNS advertisements

https://github.com/opnsense/core/issues/5919

mind if I take this over?

@pmhausen thanks, if you can please have a brief look at https://github.com/opnsense/core/commit/68894e989dc890954746507fe85cd4f5c087d94a to see if it makes sense (help texts)
Ok, I'll try to place the plugin issue in the appropriate queue.

I find the wording "If a setting here is used the information below is ignored" a bit clumsy.
How about "If checked no DNS information is sent and the next setting concerning DHCPv6 is ignored."

I tend to agree. The text, however, is trying to explain both settings at the same time. The below configuration is not DHCPv6 -- only the checkbox option above is.

@pmhausen how about 1c322498c90 ? might be a little over the top but now the checkboxes do what the configuration actually does (disable other checkbox, hide custom dns options)


Improve food cards' design

Hey, I've noticed that the food cards' UI can be improved, like adding link to the card, not to just the food name and better transition effects for better user experience. I'd like to work on that. Can you assign it to me? Thanks.

@Rikir-M
i assign you this issue , post video or photo of site , when you make Pr

make sure you star ⭐ repo if you like and follow on github

@mohitahlawat2001
Ok, noted. I will. Thanks for assigning me this issue.

any progress ?

hello, yes. I'm working on it

I think this one and issue #55 both are the same issue. Assign this to me, once i complete these you can close both the issues


Chrome mobile view in dev tools forces "rotate" camera mode.

Describe the bug
CameraMode "pan" does not work in Google Chrome developer tools "Toggle device toolbar" mobile view.
The issue doesn't happen on Firefox.
Steps to Reproduce the Bug or Issue

Create a GraphCanvas with a few nodes.
Open in Chrome
Open developer tools
Click "Toggle device toolbar" to switch to mobile view.
Observe that the graph no longer pans, but rotates.

Expected behavior
As a user, I expect to be able to test reagraph in mobile device emulation in Chrome.
Screenshots or Videos
No response
Platform

Reagraph Version: 4.11.1
OS: Windows
Browser: Chrome
NodeJS version: 18.16.0

Your Example Website or App
No response
Additional context
No response

did you fix the issue

This is still a bug FYI


Added file.zip for Shaker Heights High School stu.shaker.org domain addition

school website: https://www.shaker.org/
IT specific courses: https://www.shaker.org/Science.aspx
IT specific career technical courses: https://www.shaker.org/CareerTechnicalEducation.aspx
Official emails including shaker.org domain (staff domain): https://www.shaker.org/BoardofEducation.aspx
stu.shaker.org is the student specific domain.

Please fork SWOT repository, copy file.zip in the root folder of your forked SWOT repository. Then unzip file.zip there with no changes to the directory structure. Then make a new pull request. If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message. I have to close this request without merging. Thank you for your understanding.


Problem Publishing Chrome Extension

Hello Chrome Team,
Google has declined the Chrome extension during validation process (see mail below) :
Dear Developer,
Your Google Chrome item, "Mystique", with ID: ojmoejdlbloponkglceckmdoenkjhaed did not comply with our policies and was removed from the Google Chrome Web Store.
We routinely review items in the Chrome Web Store for compliance with our Program policies to ensure a safe and trusted experience for our users. Per our policies, where possible, make as much of your code visible in the package as you can. If some of your app's logic is hidden and it appears to be suspicious, we may remove it.
During the course of a review, your item was found to be suspicious and has requested/fetched one or more external scripts.
To have your item reinstated, please make any necessary changes to avoid requesting or executing remotely hosted code (including by referencing remote javascript files or executing code obtained by XHR requests).
If you'd like to re-submit your item, please make the appropriate changes to the item so that it complies with our policies, then re-publish it in your developer dashboard. Please reply to this email for issues regarding this item removal.
*Please keep in mind that your re-submitted item will not be immediately published live in the store. All re-submitted items undergo a strict compliance review and will be re-published if the item passes review.
*Important Note
Repeated or egregious violations in the store may result in your developer account being banned from the store. This may also result in the suspension of related Google services associated with your Google account. All re-submitted items will continue to be subject to Chrome Web Store policies and terms of service.
Thank you for your cooperation,
Google Chrome Web Store team

Developer Terms of Service:
https://developers.google.com/chrome/web-store/terms
Program Policies:
https://developers.google.com/chrome/web-store/program_policies
Branding Guidelines:
https://developers.google.com/chrome/web-store/branding

Hi,
is anybody working on this topic? Who can come up with solutions?

Hi @svendeswan,
Flo and me will take care of this within the next days.
Best, Jan.

@belafarinrod91: Did you guys manage to take a look at it yet?
Are there functional changes that might also affect Mozilla Firefox group or Library group?

could this be related to any of the libs introduced by the library team loading more content? Or rather to a faulty declaration on where the background script is running?

@FrankeA90 - I will take a look this evening. Was busy until now.
@bensteUEM - Let me check, I hope I can come back with a proper solution.

@bensteUEM - did you already manage to upload the ff extension ?
@FrankeA90 - It's not really clear to me, what could be wrong as the message is far too generic. Please answer to the rejection email and ask why the app was not approved (as stated here: https://developer.chrome.com/webstore/faq#faq-listing-10).
@svendeswan - we'll keep on working ;)

Hi everybody, are there any news regarding the publishing problem? As far as I can see we only include Blubird and JQuery as external scripts but they are not hidden. Maybe they complain about the Ajax calls to Google Search.

Hello all,
i have contacted Google. The Problem seems to be the Name or the Description of our Extension.
Can anyone change the Name of the Extension. Maybe to: Mystique: Hide your identity or something like that.
I will adjust the description in Webstore.
Here the Mail from Google:
Dear Developer,
Thank you for your reply. Please note, Chrome Extensions must have a clear title and description that explain its functionality. If your extension has a suspicious description, we may remove it.
If you’d like to re-submit it, please modify the item so that it complies with the policies, then re-publish it in your developer dashboard. Please reply to this email for issues regarding this item removal.
Thank you for your cooperation,
Chrome Web Store team


[FEATURE] CodeSandbox template features for using eccentric touch

⭐ Suggestion
Need to provide buttons for using a template for testing eccentric touch features.
The list of buttons will be given where templates will be for Plain HTML, CSS, JS, React, Vue.

Create templates on codesanbox
Link templates of all the type using buttons on the docs

💻 Use Cases
This feature will give users/developers a power to directly get a taste of eccentric touch, without creating new projects and files.
❌ Related Problems
Not related to a problem, Just a good feature to be added. ✅

This feature has been added ✅


Ruby hotkeys requires matchit.zip

Some hotkeys like: ,rrlv needs matchit to work

ok! There's a note in README. Thanks to report @camponez !


Add instance-variables to eslint react/sort-comp rule

Currently, our eslint config requires instance variables to be defined after the constructor and lifecycle handlers like below.
constructor() {
  this.myProp = doSomething();
}

onComponentDidMount() {
  doSomethingElse();
}

myProp;

If we add instance-variables to the order before lifecycle, then this should require instance variables be defined before the constructor and after static members like below. This only applies to jsx/tsx files.
myProp;

constructor() {
  this.myProp = doSomething();
}

onComponentDidMount() {
  doSomethingElse();
}

It will require some manual fixing as the rule doesn't have auto-fix.

Adding this rule affects many memoized getters we have b/c they are set using instance variable notation and not instance methods. E.g. getCachedItems = memoize(...);
We could instead use type-annotations here with the main downside there that any instance variable initialization would be put after lifecycle methods. E.g. myItems: Item[] would be expected before the constructor, but myItems: Item[] = [] would be expected after lifecycle methods.


Add step-by-step examples on contract deployment

Add instructions on deploying core contracts such as:

onboard account
data on chain

currently, for typescript we only use pre-deployed contracts only. we should consider adding the deployment functionality as we have in python - but still considering its useability later on.


Do not list both country and country code inside a person file

There is no doubt about "Norway" but there may be doubt about "NO" or "N". Also NO can be interpreted as false.

Is it "SE"? Or "S"? Again, no doubt about "Sweden".

I agree now that country codes look better on page overviews. But we want to get rid of the redundancy in person data pages.

Sure, I only included both so you would have the ability to easily A/B compare and see for yourself.
Way forward (I think) is to put assign country code in "country" and drop country_code. And (possibly) template our way to full country names where suitable (which I guess is the person page only?).

Fixed in b579777c90cc9b7d3a50d6ba70e2055192a148a8.


Allow attaching user's own OpenCL context to Boost.Compute

This PR allows user to attach their own OpenCL context via default_context(context* = 0), with such benefits as described in #827. It adheres to default_context() behavior defined in boost/compute/system.hpp :

The default context is created once on the first time this function is called. Calling this function multiple times will always result in the same context object being returned.

Now user can either let Boost.Compute decide which context to initialize with:
MyLib::MyLib(context ctx)
{
    boost::compute::default_context(); // optional
}

Or attach their own context:
MyLib::MyLib(context ctx)
{
    boost::compute::default_context(&ctx);
}

Test result of repeatedly attaching user context concurrently will correctly return only one unique context. See test_user_context_thread_safety.cpp:
$ ctest -C Release -R \w*user_default_context_thread_safety --repeat-until-fail 512

1/1 Test #16:
Start 16: core.user_default_context_thread_safety
core.user_default_context_thread_safety ...   Passed    0.06 sec
# … repeat 512 times

100% tests passed, 0 tests failed out of 1

Total Test time (real) =  31.65 sec

Tests passed with the following flags:
BOOST_COMPUTE_THREAD_SAFE=ON, BOOST_COMPUTE_USE_CPP11=ON
BOOST_COMPUTE_THREAD_SAFE=ON, BOOST_COMPUTE_USE_CPP11=OFF

I am closing this while preparing to open another PR


Context

How to use CreateContext and UseContext

multi-exports is not supported yet. I suggest you move the context on a separate module for now.

尚不支持多导出。我建议您现在将时间转移到单独的模块上。

I try, thank you for reply

In this way, the reaction is lost

What's the file extension?

文件扩展名是什么？
tsx

Do you have use "solid-sfc"; or .solid.tsx

Do you have use "solid-sfc"; or .solid.tsx

.solid.tsx seems to have not been used

Do you have use "solid-sfc"; or .solid.tsx

I try it first

No you don't have to add them

No you don't have to add them

what

You don't have to use the SFC condition. I'm just trying to know what the root of the problem is

You don't have to use the SFC condition. I'm just trying to know what the root of the problem is

How to operate the context in this sfc


Create Blog “2022-04-13t19-23-48-082z-this-is-a-new-test-blog”

Automatically generated by Netlify CMS

👷 Deploy Preview for iridescent-khapse-0bbbf4 processing.

Name
Link

🔨 Latest commit
069fa40035a53c608cfdf758c815a7df426cb9d3

🔍 Latest deploy log
https://app.netlify.com/sites/iridescent-khapse-0bbbf4/deploys/6257234e32e686000813ac9f


wav2vec 2.0 inference pipeline (issue #2651)

Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos, doc improvements)

In issue #2651, #2618, Some researcher wants a single python script that loads and runs inference with wav2vec 2.0 pre-trained model on a single wav file or on a programmatically loaded waveform signal.

[ ] Did you read the contributor guideline?

Yes, I did.

[ ] Did you make sure to update the docs?

I clone today.
What does this PR do?
Added a code that gives the inference of the Wav2vec-2.0 model to one audio file. like following:

Command

$ python3 examples/wav2vec/recognize.py --wav_path $WAV_PATH --w2v_path $W2V_PATH --target_dict_path $TARGET_DICT_PATH

Output

I LOVE THEE FREELY AS MEN STRIVE FOR RIGHT I LOVE THEE PURELY AS THEY TURN FROM PRAISE

PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Yes !!

I made only one independent recognize.py without touching other codes.

Hmm... I don`t know what is wrong. I just add recognize.py for one audio inference.

This is awesome by the way @sooftware ! Any chance you could merge master and update your PR? I'm looking forward to playing with this!
Thanks!

I have some problems with merging this code. There was a lot of change when Fairseq version was upgraded.
If you use Fairseq 0.9.0 version, you can refer to this issue for information.

I'm on master. I might try to have a look to see which parts changed and if I can help port this PR over in anyway later if I find time :) Thanks for your quick answer.

I've created pull request https://github.com/pytorch/fairseq/pull/3244 for similar purpse.


fix(259): add bundle size analysis comment as a comment on each pull request

Description
Added a new GitHub Actions workflow to track and report bundle size changes on pull requests.
Changes

Added bundle-size.yml workflow that:

Builds both base and PR branches
Calculates total bundle size
Provides detailed breakdown of JS and CSS files
Comments size differences on PRs automatically

Testing

Tested locally using act
Verified workflow syntax and job configuration

Notes

Workflow triggers on PRs targeting main branch
Uses GitHub token for PR comment permissions
Timeout set to 15 minutes for build process

Related
Inspired by similar workflow in tscircuit/core, but optimized for Vite applications
/claim #259

@seveibar We switched to using job summaries for now, as they should work fine until GitHub adds a comment scope we can utilize.

@nocodeventure-nl i don't think anyone will look at the build summaries, we should try to find a solution. I'm told that having a PR invoke an action (via a workflow dispatch) gets around the issue

Also just a note on your bundle summary, you should use something vite-specific, it's kind of useless as-is. We want to know what makes the vite bundle so big

@melmathari helo, I tried to do this but failed. I want to pass it to you to see how it should be done. Could you please after you complete it check my pr and see where I've gone wrong?

@melmathari helo, I tried to do this but failed. I want to pass it to you to see how it should be done. Could you please after you complete it check my pr and see where I've gone wrong?

@ShiboSoftwareDev What do you mean as to complete  what...?

@melmathari if you check my pr you can see I succeeded with posting a comment on the pr, but failed to generate the analysis. The issue and the bounty are still up and I would like you to have a go at it.

@melmathari if you check my pr you can see I succeeded with posting a comment on the pr, but failed to generate the analysis. The issue and the bounty are still up and I would like you to have a go at it.

I won't be able to on the short run but kindly have a look at the files I modified in my repo. https://github.com/tscircuit/snippets/pull/274/files


Strange disconnection when more than one account is set up

Describe the bug
Something happens when two accounts are configured: the setup process is ok, but the second account lost the entities after some minutes. The entities dissapear from the "configuration - integration - Alexa media player - account". A restart (or integration reload) fix temporally the issue, but  finally it happens again in minutes. Not sure since which version is happening this. Delete integrations for both accounts just solve the problem temporally, and the same if delete the integration and readed from HACS
To Reproduce
Steps to reproduce the behavior:

Add 1st account as usual
Check entities
Add 2nd account
Check entities
Wait minutes
Suddenly, the entities from 2nd account are not available

Expected behavior
More that one account working fine as always
Screenshots

System details

Home-assistant (version): 2021.5.4
Hassio (Yes/No): yes
alexa_media  (version from const.py or HA startup): V3.10.4
alexapy (version from pip show alexapy or HA startup):
Amazon 2FA is enabled (y/n). Yes

Logs
I'll provide if request
Additional context
Amazon domain: .es
EDIT: testing with v3.10.0 and no issues by now

Please provide startup logs up to the removal.

Sure. Please, let me the issue open meanwhile I find some time to unistall, reinstall, enable debug, etc


WIP: Collect and aggregate code coverage across all test environments

Investigating code coverage reporting.

Create cov-clean tox environment
Create cov-report tox environment
All other test environments depend upon cov-clean.
cov-report depends on all test-environments.
usedevelop to install vcrpy so that the paths to the original source files are the same across tox environments to accumulate test coverage. Some paths only occur in certain environments.

For example:

Module
statements
missing
excluded
branches
partial
coverage

vcr/__init__.py
11
4
0
0
0
64%

vcr/_handle_coroutine.py
3
2
0
0
0
33%

vcr/cassette.py
201
5
0
60
1
98%

...
...
...
...
...
...
...

vcr/util.py
63
1
0
22
2
96%

Total
1522
128
68
434
31
90%

TODO:

[x] Aggregate across travis and enforce no code coverage regressions

Not necessary. CI runs the build then uploads to CodeCov

[x] Investigate alternatives:

~~https://coveralls.io/~~ Terrible documentation.
https://codecov.io/

[ ] PRs should fail on CodeCoverage regressions.

@1oglop1 I finally added some AWS credentials to Travis as Kevin granted me access.
Locally the credentials work. On Travis I'm getting:
 EndpointConnectionError: Could not connect to the endpoint URL: "https://iam.default.amazonaws.com/"

Did you have that issue configuring your version of TravisCI?

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@9d37210). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #460   +/-   ##
=========================================
  Coverage          ?   87.84%
=========================================
  Files             ?       26
  Lines             ?     1522
  Branches          ?      215
=========================================
  Hits              ?     1337
  Misses            ?      159
  Partials          ?       26

Continue to review full report at Codecov.

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

Ok that is weird.
I added the same AWS credentials to neozenith/vcrpy travis-ci and it passes.
https://travis-ci.org/neozenith/vcrpy/builds/564815856
Seems like there is something cached against kevin1024's TravisCI builds which is borking the boto3 integrations.

Did you add AWS creds as Env vars to travis?
I'd get rid of secure: strings in Travis config, I assume it contains incorrect AWS credentials

Ok cheers. I'll try that.
It's so weird. I can get it to pass on neozenith/vcrpy, you can get it to pass on jans-forks/vcrpy, but this instance of kevin1024/vcrpy for TravisCI dies.
Might be time for stronger coffee, heavier music and reading the docs. Thanks for your help.

The error from here: https://travis-ci.org/kevin1024/vcrpy/jobs/564842481
E           botocore.exceptions.NoCredentialsError: Unable to locate credentials
Often means that credentials are not in ENV vars or .aws/credentials file

Ok. I added them the same way in both mine and Kevin1024 Travis-CI.
Maybe it’s not exposing them correctly because they are secret.
I’ll try removing and re-adding them.
There is something interfering that I’m not seeing. I think that’s my green-ness to TravisCI to know where to look and what to google. So thanks for your help generating new hypotheses for me to run down. 😄

Helps to read the logs.
https://docs.travis-ci.com/user/pull-requests/#pull-requests-and-security-restrictions

Pull requests sent from forked repositories do not have access to encrypted variables or data even if these are defined in the fork source project.

So contributions are never going to pass CI if we have those credentials in the Repository settings and not encrypted in the .travis.yml


Initial version of "Improving Sendable Inference"

Thank you @benrimmington for the editing!

This will be superseded by a set of separate proposals.


Fix typo in README (react)

Issue:
I think there is a typo error in README (simplebar-react package). In Simplebar component's render prop pattern, props showed two objects with the same name.
What is done to fix it:
When we use render prop pattern, the props are scrollableNodeProps, contentNodeProps.

Thanks!


Event when device does not support camera

Add the event notsupported in order to handle visually on frontend when the camera is not available in the devices eg: desktop pc

@cchicohaymg Thank you for your feedback! sorry it took a while to get back to you.
We will consider this, but for the moment we are rather busy, we would welcome a PR anytime tho!


Clock calibration and TDMA docmuent?

Hi,
I am trying to understand uwb_ccp and tdma packet. Could you give me the documents from which you reference to implement?

Hi @tuannv0898  - I am trying to understand the same protocols, any luck in getting any documentation?


[NEW] add PeerSwap

[x] add for LND
[ ] test with LND
[x] add for CLN
[ ] test with CLN
[ ] add to menu

Tracking:

[x] https://github.com/ElementsProject/peerswap/issues/88
[x] https://github.com/ElementsProject/peerswap/issues/89
[ ] https://github.com/ElementsProject/peerswap/pull/79

Includes #3219

@openoms there are still open todos in the list - are you still targeting v1.8.1 (end october) or should I push further to v1.8.2?

testing time is scarce so would target 1.8.2

closing as there were no updates in PeerSwap in 2023 and a future integration should be started from scratch

doing swaps to L-BTC makes a lot of sense so will revisit this with Elements support: https://github.com/ElementsProject/peerswap/blob/master/docs/setup_elementsd.md

Reopening related to #4573


Use std::move() when statting all files in a directory on windows, to reduce string copies

To elaborate on why this is a big improvement:
if (ffd.cFileName[0] == '.' && ffd.cFileName[1] == '.') {

Skips an allocation and copy if the result wouldn't be used.
stamps->emplace(std::move(lowername), TimeStampFromFileTime(ffd.ftLastWriteTime));

instead of
stamps->insert(make_pair(lowername,
                             TimeStampFromFileTime(ffd.ftLastWriteTime)));

Skips two allocations and copies.

emplace() instead of insert(make_pair()) skips copying the resulting std::pair, which contains a string, which results in an allocation and copy.
std::move() on lowername skips an allocation and copy for the std::string that's emplaced into the map.

Do you have any benchmark data on how much this saves?

I do not have a windows computer, and this is windows specific code, so I'm unable to run benchmarks for this change.
I would rather see this change implemented directly in https://github.com/ninja-build/ninja/pull/1671, but implemented it in this PR both so it doesn't have to wait for the other UTF-8 changes, and also to stand as an isolated example.

As this change doesn't involve the WinAPI directly, you can test with WINE. Here's how you would do that on Fedora Linux for example:
mingw64-cmake -H. -Bbuild-mingw -DCMAKE_BUILD_TYPE=Release -GNinja
ninja -Cbuild-mingw
./misc/measure.py wine build-mingw/ninja.exe -C path/to/big/project/with/no/work/to/do

I don't really see how benchmarking this code is going to do any good.
As I detailed in a previous comment, this change postpones a potentially unneeded allocation+copy, as well as uses rvalue-reference / move to construct the map node, instead of the allocate+copy of std::string.
It should be impossible for this to be slower.

It should be impossible for this to be slower.

Sure, but we wonder if it's really a "big improvement". Sometimes the optimizer does magic things, therefore it's good to check any performance optimization and not optimize prematurely.

The C++ standard forbids compilers from implicitly casting variables to rvalue-references when passing those variables to functions as parameters.
The only situations where implicit cast to rvalue-references are allowed is around return-value-optimzation and copy-elision and the like.


[1.13] Update docs for low-cardinality metrics

Fixes #3987
Includes documenting the new "http.increasedCardinality" configuration option

Could you also add metrics into the schema for configuration here https://docs.dapr.io/reference/resource-specs/configuration-schema/#sidecar-format since it is missing currently.

Yes, I'll do that tomorrow

Does this new option completely remove the need for regular expressions?

Doesn't remove the need entirely, but originally regexs for metrics were "marketed" as a solution to the high cardinality problem. I suspect a lot of users who figured that out (and I can tell you by first-hand experience we did not make it easy to figure that out at all!) were using them for this purpose. However, there could be other purposes and those could still be valid.


#2311 Measure FE test coverage on CI

Reopen PR to run checks

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@943d579). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #273   +/-   ##
=======================================
  Coverage        ?   73.29%
=======================================
  Files           ?       92
  Lines           ?     5246
  Branches        ?      577
=======================================
  Hits            ?     3845
  Misses          ?     1400
  Partials        ?        1


core tuning scripts are cgroups v1 specific

https://github.com/jboss-container-images/openjdk/blob/00718e4767766920d2228e724616cbb4301cac74/modules/jvm/bash/artifacts/opt/jboss/container/java/jvm/container-limits#L24
I think the above (and perhaps other bits) are cgroups V1 specific. At least, when running under cgroups v2 and specifying CPU limits in podman, those paths do not exist.

Yes. That's cgroups v1 specific. What are those used for these days?

It is used to determine an (integral) CPU count and enables these parameters:
-XX:ParallelGCThreads=${core_limit} " \
              "-Djava.util.concurrent.ForkJoinPool.common.parallelism=${core_limit} "\
              "-XX:CICompilerCount=2"

The first is Parallel GC specific, and we do default to specifying Parallel GC, but these scripts will emit that even if the user specifies another GC. So that needs changing. The others, I wonder what the JVM would default to anyway and whether they're still effective or best practise.

Provided that container detection works, it's not needed:
On a cgroups v2 system (JDK default is #of-cores - 1):
$ sudo podman run --cpu-quota=300000 --cpu-period=100000 --rm -it --entrypoint /bin/bash registry.access.redhat.com/ubi8/openjdk-17 -c "echo 'System.out.println(\"getParallelism() = \" + ForkJoinPool.commonPool().getParallelism())' | jshell - -J-showversion 2>&1"
openjdk version "17.0.2" 2022-01-18 LTS
OpenJDK Runtime Environment 21.9 (build 17.0.2+8-LTS)
OpenJDK 64-Bit Server VM 21.9 (build 17.0.2+8-LTS, mixed mode, sharing)
Mar 11, 2022 1:18:44 PM java.util.prefs.FileSystemPreferences$1 run
INFO: Created user preferences directory.
getParallelism() = 2
$ sudo podman run --cpu-quota=400000 --cpu-period=100000 --rm -it --entrypoint /bin/bash registry.access.redhat.com/ubi8/openjdk-17 -c "echo 'System.out.println(\"getParallelism() = \" + ForkJoinPool.commonPool().getParallelism())' | jshell - -J-showversion 2>&1"
openjdk version "17.0.2" 2022-01-18 LTS
OpenJDK Runtime Environment 21.9 (build 17.0.2+8-LTS)
OpenJDK 64-Bit Server VM 21.9 (build 17.0.2+8-LTS, mixed mode, sharing)
Mar 11, 2022 1:19:01 PM java.util.prefs.FileSystemPreferences$1 run
INFO: Created user preferences directory.
getParallelism() = 3

On a cgroups v1 system:
$ sudo podman run --cpu-quota=400000 --cpu-period=100000 --rm -it --entrypoint /bin/bash registry.access.redhat.com/ubi8/openjdk-11 -c "echo 'System.out.println(\"getParallelism() = \" + ForkJoinPool.commonPool().getParallelism())' | jshell - -J-showversion 2>&1"
openjdk version "11.0.13" 2021-10-19 LTS
OpenJDK Runtime Environment 18.9 (build 11.0.13+8-LTS)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.13+8-LTS, mixed mode, sharing)
Mar 11, 2022 1:21:04 PM java.util.prefs.FileSystemPreferences$1 run
INFO: Created user preferences directory.
getParallelism() = 3
$ sudo podman run --cpu-quota=300000 --cpu-period=100000 --rm -it --entrypoint /bin/bash registry.access.redhat.com/ubi8/openjdk-11 -c "echo 'System.out.println(\"getParallelism() = \" + ForkJoinPool.commonPool().getParallelism())' | jshell - -J-showversion 2>&1"
openjdk version "11.0.13" 2021-10-19 LTS
OpenJDK Runtime Environment 18.9 (build 11.0.13+8-LTS)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.13+8-LTS, mixed mode, sharing)
Mar 11, 2022 1:21:12 PM java.util.prefs.FileSystemPreferences$1 run
INFO: Created user preferences directory.
getParallelism() = 2

Same for ParallelGCThreads. See:
https://github.com/jboss-container-images/openjdk/issues/266#issuecomment-1065101812
Not sure what the intention of -XX:CICompilerCount=2 is. Maybe it should be -XX:-CICompilerCountPerCPU. That would need to be discussed more broadly, though.

On a cgroups v2 system (JDK default is #of-cores - 1):

So the JDK will pick a value which is different to these scripts, probably a more sensible default but an argument could be made that we should preserve the decision made in the scripts for the legacy images.

Not sure what the intention of -XX:CICompilerCount=2 is. Maybe it should be -XX:-CICompilerCountPerCPU. That would need to be discussed more broadly, though.

The intention seems to be to set the number of compiler threads to == number of available CPUs. CICompilerCountPerCPU sets instead 1 compiler thread for log(N CPUs). The default JVM behaviour in our JDK8 and JDK11 is not yet container aware (I get a default CICompilerCount of 12 no matter the CFS settings, versus 17). Perhaps there's something further to backport here. But as with the last parameter, it could be argued that we should not change the behaviour from what the scripts do for the legacy images, at least.

On a cgroups v2 system (JDK default is #of-cores - 1):

So the JDK will pick a value which is different to these scripts, probably a more sensible default but an argument could be made that we should preserve the decision made in the scripts for the legacy images.

Not sure what the intention of -XX:CICompilerCount=2 is. Maybe it should be -XX:-CICompilerCountPerCPU. That would need to be discussed more broadly, though.

The intention seems to be to set the number of compiler threads to == number of available CPUs. CICompilerCountPerCPU sets instead 1 compiler thread for log(N CPUs).

Hmm, that seems to be a bad value to set it to (too large for many core deployments). Where does this, compiler threads to == number of available CPUs come from?

The default JVM behaviour in our JDK8 and JDK11 is not yet container aware (I get a default CICompilerCount of 12 no matter the CFS settings, unlike with JDK17).

Hmm, that's very weird. Well at least if you have tried it on a cgroups v1 system. I see this working as expected for JDK 8 and 11:
$ sudo podman run --cpu-quota=700000 --cpu-period=100000 --rm -it registry.access.redhat.com/ubi8/openjdk-11 java -XX:+PrintFlagsFinal -version 2>&1 | grep CICompilerCount
     intx CICompilerCount                          = 3                                         {product} {ergonomic}
     bool CICompilerCountPerCPU                    = true                                      {product} {default}
$ sudo podman run --cpu-quota=200000 --cpu-period=100000 --rm -it registry.access.redhat.com/ubi8/openjdk-11 java -XX:+PrintFlagsFinal -version 2>&1 | grep CICompilerCount
     intx CICompilerCount                          = 2                                         {product} {ergonomic}
     bool CICompilerCountPerCPU                    = true                                      {product} {default}
$ sudo podman run --cpu-quota=100000 --cpu-period=100000 --rm -it registry.access.redhat.com/ubi8/openjdk-11 java -XX:+PrintFlagsFinal -version 2>&1 | grep CICompilerCount
     intx CICompilerCount                          = 2                                         {product} {ergonomic}
     bool CICompilerCountPerCPU                    = true                                      {product} {default}
$ sudo podman run --cpu-quota=300000 --cpu-period=100000 --rm -it registry.access.redhat.com/ubi8/openjdk-11 java -XX:+PrintFlagsFinal -version 2>&1 | grep CICompilerCount
     intx CICompilerCount                          = 2                                         {product} {ergonomic}
     bool CICompilerCountPerCPU                    = true                                      {product} {default}
$ sudo podman run --cpu-quota=400000 --cpu-period=100000 --rm -it registry.access.redhat.com/ubi8/openjdk-11 java -XX:+PrintFlagsFinal -version 2>&1 | grep CICompilerCount
     intx CICompilerCount                          = 3                                         {product} {ergonomic}
     bool CICompilerCountPerCPU                    = true                                      {product} {default}
$ sudo podman run --cpu-quota=400000 --cpu-period=100000 --rm -it registry.access.redhat.com/ubi8/openjdk-11 java -XX:-CICompilerCountPerCPU -XX:+PrintFlagsFinal -version 2>&1 | grep CICompilerCount
     intx CICompilerCount                          = 2                                         {product} {default}
     bool CICompilerCountPerCPU                    = false                                     {product} {command line}
$ sudo podman run --cpu-quota=300000 --cpu-period=100000 --rm -it registry.access.redhat.com/ubi8/openjdk-11 java -XX:-CICompilerCountPerCPU -XX:+PrintFlagsFinal -version 2>&1 | grep CICompilerCount
     intx CICompilerCount                          = 2                                         {product} {default}
     bool CICompilerCountPerCPU                    = false                                     {product} {command line}
$ sudo podman run --cpu-quota=200000 --cpu-period=100000 --rm -it registry.access.redhat.com/ubi8/openjdk-11 java -XX:-CICompilerCountPerCPU -XX:+PrintFlagsFinal -version 2>&1 | grep CICompilerCount
     intx CICompilerCount                          = 2                                         {product} {default}
     bool CICompilerCountPerCPU                    = false                                     {product} {command line}
$ sudo podman run --cpu-quota=100000 --cpu-period=100000 --rm -it registry.access.redhat.com/ubi8/openjdk-11 java -XX:-CICompilerCountPerCPU -XX:+PrintFlagsFinal -version 2>&1 | grep CICompilerCount
     intx CICompilerCount                          = 2                                         {product} {default}
     bool CICompilerCountPerCPU                    = false                                     {product} {command line}
$ sudo podman run --cpu-quota=100000 --cpu-period=100000 --rm -it registry.access.redhat.com/ubi8/openjdk-8 java -XX:-CICompilerCountPerCPU -XX:+PrintFlagsFinal -version 2>&1 | grep CICompilerCount
     intx CICompilerCount                          := 2                                   {product}
     bool CICompilerCountPerCPU                    := false                               {product}
$ sudo podman run --cpu-quota=200000 --cpu-period=100000 --rm -it registry.access.redhat.com/ubi8/openjdk-8 java -XX:-CICompilerCountPerCPU -XX:+PrintFlagsFinal -version 2>&1 | grep CICompilerCount
     intx CICompilerCount                          := 2                                   {product}
     bool CICompilerCountPerCPU                    := false                               {product}
$ sudo podman run --cpu-quota=700000 --cpu-period=100000 --rm -it registry.access.redhat.com/ubi8/openjdk-8 java -XX:-CICompilerCountPerCPU -XX:+PrintFlagsFinal -version 2>&1 | grep CICompilerCount
     intx CICompilerCount                          := 2                                   {product}
     bool CICompilerCountPerCPU                    := false                               {product}
$ sudo podman run --cpu-quota=700000 --cpu-period=100000 --rm -it registry.access.redhat.com/ubi8/openjdk-8 java -XX:+PrintFlagsFinal -version 2>&1 | grep CICompilerCount
     intx CICompilerCount                          := 3                                   {product}
     bool CICompilerCountPerCPU                     = true                                {product}
$ sudo podman run --cpu-quota=200000 --cpu-period=100000 --rm -it registry.access.redhat.com/ubi8/openjdk-8 java -XX:+PrintFlagsFinal -version 2>&1 | grep CICompilerCount
     intx CICompilerCount                          := 2                                   {product}
     bool CICompilerCountPerCPU                     = true                                {product}
$ sudo podman run --cpu-quota=100000 --cpu-period=100000 --rm -it registry.access.redhat.com/ubi8/openjdk-8 java -XX:+PrintFlagsFinal -version 2>&1 | grep CICompilerCount
     intx CICompilerCount                          := 2                                   {product}
     bool CICompilerCountPerCPU                     = true                                {product}

Missing cgroups v2 support in JDK 8 and 11 might explain what you were seeing.

Perhaps there's something further to backport here. But as with the last parameter, it could be argued that we should not change the behaviour from what the scripts do for the legacy images, at least.

Perhaps. CICompilerCount == # of cores seems too large to me, though.

Hi @jerboaa , I've slept on this a few nights and I think I've come back around to the idea that we go with JDK defaults and if they aren't right, fix them in the JDK. Before removing these tuning parameters I want to dig a bit deeper into CICompilerCount though. Thanks for your help

Hmm, that's very weird. Well at least if you have tried it on a cgroups v1 system. I see this working as expected for JDK 8 and 11:

Yep that was a cgroups v2 issue, it works fine on cgroups v1. So I think we can drop all these tuning parameters from the run scripts.

I've filed https://issues.redhat.com/browse/OPENJDK-630 to clean up the core side of things in the scripts.

All this stuff has now gone as of 1.12