Auto-generate the Kamelet Catalog website

This generates an Antora module for the Kamelet catalog directly from the Kamelet YAML files.
cc: @davsclaus , @oscerd , @astefanutti , @squakez , @doru1004 , @lburgazzoli, @christophd
A preview...

Next step for the UI:

Move the markup to the main Camel website UI bundle
Add Netlify integration to this repo
Add a section in the main Camel website

We need @zregvart for including this somewhere in the website.

random thought:

we should probably have some way of grouping kamelets, i.e. there may be a number of telegram related kamelets
we shold think about versioning

random thought:

we should probably have some way of grouping kamelets, i.e. there may be a number of telegram related kamelets
we shold think about versioning

Yeah, so versioning can be done by tagging this repo as per proposal. Antora supports multiple versions oob.
There's a camel.apache.org/kamelet.group=<name of the group> label that should be used for grouping. The UI still does not support that but that's an improvement.
I wonder if we should make the group mandatory and have it for all Kamelets. The catalog can have both a link to a page where single kamelets of a group are listed (if more than one), but also direct links to the specific Kamelets in the display box.

I'm not sure if it makes sense to have the same ui we are using on the camel website, just for visual identity, btw we need @zregvart to include it.

I'm not sure if it makes sense to have the same ui we are using on the camel website, just for visual identity, btw we need @zregvart to include it.

Yeah, this includes a custom UI with additional CSS and layout on top of the Antora default one, but it's a temporary solution until we embed the camel default UI.
I'd like adding the "catalog" layout to the main Camel UI and the best would be to have it published in an HTTP location (maybe using Github actions, like the Antora folks seem to do), so that we can reference it back from here in: https://github.com/apache/camel-kamelets/blob/15165a71c888f373033f370439176039e5987c5a/docs/antora-playbook.yml#L15
Is it possible @zregvart ?

random thought:

we should probably have some way of grouping kamelets, i.e. there may be a number of telegram related kamelets
we shold think about versioning

Yeah, so versioning can be done by tagging this repo as per proposal. Antora supports multiple versions oob.

I was more thinking about kamelet specific versions, giving that they can be used even without a catalog, whould we also let people browse to a specific kamelet version ?

There's a camel.apache.org/kamelet.group=<name of the group> label that should be used for grouping. The UI still does not support that but that's an improvement.
I wonder if we should make the group mandatory and have it for all Kamelets. The catalog can have both a link to a page where single kamelets of a group are listed (if more than one), but also direct links to the specific Kamelets in the display box.

+1 for making group mandatory

@nicolaferraro perhaps you can start a pull request with the changes needed to the website on the website repository. Not sure what's to gain by adding those changes here. Is the end goal to publish to a different domain?

@nicolaferraro perhaps you can start a pull request with the changes needed to the website on the website repository. Not sure what's to gain by adding those changes here. Is the end goal to publish to a different domain?

No, it's only for the Camel website, I did them here just to have a quick preview in dev + I want later to integrate Netlify on PR.. but the code is well separated so the plan was to move it to the camel-website from the beginning. I'll try to publish the layout there, and also the final bundle so I can link it from here (if possible with the new Apache rules for Githu Actions...)

Gorgeous 👏🏼!

@nicolaferraro perhaps you can start a pull request with the changes needed to the website on the website repository. Not sure what's to gain by adding those changes here. Is the end goal to publish to a different domain?

No, it's only for the Camel website, I did them here just to have a quick preview in dev + I want later to integrate Netlify on PR.. but the code is well separated so the plan was to move it to the camel-website from the beginning. I'll try to publish the layout there, and also the final bundle so I can link it from here (if possible with the new Apache rules for Githu Actions...)

If at all possible do not add another UI bundle to the camel-website, there are a number of optimizations that went into the apache-camel-ui UI bundle in the camel-website repository that you'll need to repeat in the second bundle. Adding changes to the existing apache-camel-ui UI bundle should be preferred.
This also maintains the separation of presentation vs content we have between the camel-website and other git repositories we pull to build the website.
Not sure about the Netlify integration, this is already present on the camel-website repository.
If you wish trigger publishing of changes made here to the website, that needs to happen with the trigger to the Camel.website job on the ASF Jenkins. Automating that could be done via a generic webhook on push to this repository (would require a secret to be added by INFRA).

@nicolaferraro perhaps you can start a pull request with the changes needed to the website on the website repository. Not sure what's to gain by adding those changes here. Is the end goal to publish to a different domain?

No, it's only for the Camel website, I did them here just to have a quick preview in dev + I want later to integrate Netlify on PR.. but the code is well separated so the plan was to move it to the camel-website from the beginning. I'll try to publish the layout there, and also the final bundle so I can link it from here (if possible with the new Apache rules for Githu Actions...)

If at all possible do not add another UI bundle to the camel-website, there are a number of optimizations that went into the apache-camel-ui UI bundle in the camel-website repository that you'll need to repeat in the second bundle. Adding changes to the existing apache-camel-ui UI bundle should be preferred.
This also maintains the separation of presentation vs content we have between the camel-website and other git repositories we pull to build the website.
Not sure about the Netlify integration, this is already present on the camel-website repository.
If you wish trigger publishing of changes made here to the website, that needs to happen with the trigger to the Camel.website job on the ASF Jenkins. Automating that could be done via a generic webhook on push to this repository (would require a secret to be added by INFRA).

It wasn't my intention.. I kept changes separated into a bunch of files to merge them: https://github.com/apache/camel-website/pull/536
I managed to display this catalog with the website UI with that change:

I'd like to polish this a bit, either as a PR on top of this PR (preferred) or as a followup PR.

I'd like to polish this a bit, either as a PR on top of this PR (preferred) or as a followup PR.

You're welcome to do so. Look also at https://github.com/apache/camel-website/pull/537 to completely remove the custom UI from here.

I've created a PR to polish this against this PR: https://github.com/nicolaferraro/camel-kamelets/pull/1

Let's merge this to unlock: https://github.com/apache/camel-website/pull/536


[GLUTEN-1594][CH] support native parquet writer for clickhouse backend

What changes were proposed in this pull request?
a basic working version is provided by this PR. (so that we're unblocked to  perform experiments)
however, as there're many TODO notes in the PR:

so, this ability is still incomplete.
experiments show that native parquet writer is about 20%-25% better than previous (Gluten used to convert columnar to row first, and use vanilla Spark's ParquetOutputFormat for writing):

How was this patch tested?
I'll write a simple test case to ensure basic write routine works

@zhztheplayer @rui-mo please help to review, thanks

please add the ut for this new feature.

please add the ut for this new feature.

i'm working on it

Just curious what benchmark we used in our measurements?

Just curious what benchmark we used in our measurements?

customer table in tpch 100.
More comprehensive experiments are still on the way, this is an early PR just to avoid conflict resolve efforts

Run Gluten Clickhouse CI


feat: hide tryit

Fixes: https://github.com/stoplightio/elements/issues/708
We need to be able to hide just TryIt and whole right column.
Initially I wanted to add support for hiding each of the right column components, but Examples depend on more complex inner logic when it comes to displaying it so I went for whole column approach.
Also Request Samples component is currently dependent on TryIt which feeds its props.
Naming is still something I am not sure about. docsOnly seemed better than hideRightColumn but not ideal.
I also considered one visibility prop with value of docsOnly | hideTryIt or full | docsOnly | hideTryIt.
Let me know what you think.
Adding provider isn't necessary but avoids passing props through lot of components. We're starting to get plenty of those providers so we probably need to clean and combine them at some point.

I am not a fan of this option. It feels like we structured out components too rigidly, meaning that we now have to turn bits off instead of using the bits we want in the way we want them.
The end goal of elements is to let people pick and chose bits, maybe mixing their own components in between our own, and not always to be just API and StoplightProject. If we've already hit a roadblock with the structure of our components, to a point where we cant simply hide one piece of it, then we might need to revisit our approach.
If we need this quickly, we can implement docsOnly as a hidden property, undocumented, unsupported, and delete it once we have resolved our composition issue, but I wouldn't want it around for long.

What if we extracted right column content from HttpOperation? So we could define its content on API level and pass down to HttpOperation? This way we could either include it or not and hiding/customizing elements would be simplified. Not sure how difficult it would be though but seems feasible. What do you think @mmiask @mpodlasin @marcelltoth?

What if we extracted right column content from HttpOperation? So we could define its content on API level and pass down to HttpOperation? This way we could either include it or not and hiding/customizing elements would be simplified. Not sure how difficult it would be though but seems feasible. What do you think @mmiask @mpodlasin @marcelltoth?

That's exactly what I was joking about yesterday. IIRC that's how it used to be, but then we put it into Docs.:) But see, that's how things are in SE, I'm supporting your idea if it works well in practice, show me a PR:)

Alright, I'll go that path then. Let's try to make it right at once and not fix later. As I think now it shouldn't be too difficult. Quite exceeding that 1 pointer though, but well ;)

BTW I don't believe hiding with boolean has to affect users.
It's Docs component that can have a boolean flag, not API component as a whole.
API can have only hideTryIt and we are done.
Just to keep this in mind as an alternative solution.
Putting TryIt to Docs made thinks much cleaner, but if you are able to come up with a clean way to have them outside - I will :100: approve.

Ok, if it’s just for docs component then let’s do it for now but we need to make an issue describing the other approach suggested here.
We’ve already got some customers trying to figure out how to do really advanced stuff and we’ll need to do it fairly soon.
--
Phil Sturgeon
Product @ Stoplight.io

On May 14, 2021, at 14:58, Mateusz Podlasin @.***> wrote:

BTW I don't believe hiding with boolean has to affect users.
It's Docs component that can have a boolean flag, not API component as a whole.
API can have only hideTryIt and we are done.
Just to keep this in mind as an alternative solution.
Putting TryIt to Docs made thinks much cleaner, but if you are able to come up with a clean way to have them outside - I will 💯 approve.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub, or unsubscribe.

I've updated it following the suggestion from @mpodlasin . Also removed showMocking from the Provider container and moved it to TryItProvider along with hideTryIt.
Generally when we merge new StoplightProject PR we might be able to remove that old Provider entirely or replace it with something more up to date as the current form is far from perfect.


Detection rule id 'jwt' cannot detect jwt leaks

Describe the bug
when using default gitleaks configuration, rule id 'jwt' cannot detect a normal json web token. However, when i create a customized .gitleaks.toml under the root of repo and change the rule id from 'jwt' to 'my-jwt', it works again.
To Reproduce
i test with this jwt val test = eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c, when i try to commit code with this value, i can commit it and there is no leaks warning from pre-commit hook.
However, if i create .gitleaks.toml and copy the gitleaks jwt rule and replace the rule id from jwt to my-jwt or any other value, it can detect the jwt leaks. Not sure why the name of rule id matters?
[[rules]] description = "JSON Web Token" id = "my jwt" regex = '''(?i)\b(ey[0-9a-z]{10,34}\.ey[0-9a-z-\/_]{30,500}\.[0-9a-zA-Z-\/_]{10,200}={0,2})(?:['|\"|\n|\r|\s|\x60|;]|$)''' keywords = [     "ey", ]

Expected behavior
I expect default jwt rule can detect my jwt leaks.
Basic Info (please complete the following information):

OS: MAC OS
Gitleaks Version: v8.17.0

Additional context
Add any other context about the problem here.
cc @zricethezav

Can you share the full command and output? I quickly tested this with the latest version and can't seem to reproduce it.
$ ./gitleaks detect --verbose --source /tmp/gitleaks-test/

    ○
    │╲
    │ ○
    ○ ░
    ░    gitleaks

Finding:     val test = eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE...c
Secret:      eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE...
RuleID:      jwt
Entropy:     5.444070
File:        mystuff.txt
Line:        1
Commit:      5e00309e9a6f4f2a4b10eddb970cd3ea2f212a0d
Author:      Richard Gomez
Email<EMAIL_ADDRESS>Date:        2023-06-23T14:04:37Z
Fingerprint: 5e00309e9a6f4f2a4b10eddb970cd3ea2f212a0d:mystuff.txt:jwt:1

10:04AM INF 1 commits scanned.
10:04AM INF scan completed in 64.5ms
10:04AM WRN leaks found: 1

I did notice that gitleaks protect seems to have a blindspot for new files, however, I don't think this is related to your problem.
# New file that is untracked.
 $ git status
On branch master
Untracked files:
  (use "git add <file>..." to include in what will be committed)
        BA.kt

nothing added to commit but untracked files present (use "git add" to track)

# Gitleaks protect does not pick it up.
$ gitleaks protect --verbose --config custom.toml --source /tmp/gitleaks-test/

10:10AM INF 0 commits scanned.
10:10AM INF scan completed in 57.7ms
10:10AM INF no leaks found

# Track the new file
$ git add BA.kt
$ git status
On branch master
Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
        new file:   BA.kt

# Scan again, still nothing.
$ gitleaks protect --verbose --config custom.toml --source /tmp/gitleaks-test/

10:10AM INF 0 commits scanned.
10:10AM INF scan completed in 57.7ms
10:10AM INF no leaks found

(Technically this is expected behavior with git diff, but it does seem like a rough edge @zricethezav.)

Hi, thanks for your reply. I found the cause now.
 It can no longer report this jwt leak unless we change the rule ID.
After I commit the .gitleaksignore changes, it can successfully detect it.
Sorry I submitted an error report, it can be closed


[BEAM-12302] [zetasql] Support/test TIMESTAMP as UDF argument/return …

…type.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @apilloud


CRM365+ADFS Authentication problem

Running Linqpad v5.10 with latest version of this crm-driver (v1.4).
Our setup is Dynamics CRM 365 (v8.2) On-Premise with ADFS.
I fill out the ClientId, choose IFD + credentials. I get a list of our organizations, but after that, I get the error "Couldn't authenticate user. If you manually provided clientid, make sure it is registred as multi tenant application in case you access from different domain."
The error log on the ADFS-server gives us:
Encountered error during OAuth authorization request.
Additional Data
Exception details:
Microsoft.IdentityServer.Web.Protocols.OAuth.Exceptions.OAuthInvalidResourceException: MSIS9329: Received invalid OAuth authorization request. The 'resource' parameter's value does not correspond to any valid registered relying party. Received resource: 'https://crm.mydomain.com/MYORG'.
at Microsoft.IdentityServer.Web.Protocols.OAuth.OAuthAuthorization.OAuthAuthorizationRequestContext.Validate()
Any ideas on this? We did the Add-AdfsClient command and restarted service.

I don't have environment right now for testing this. If you know how to debug, could you try to debug the issue? Otherwise I may need to access your environment if possible?


change Twitter logo

Changing twitter logo from bird to X

Good idea. Would you be inclined to submit a PR for this?

unable to figure out as the code is in rust

unable to figure out as the code is in rust

No probs - the website code is actually based on https://starlight.astro.build/ if you're interested in contributing in the future.


memory leaks in Instruments in Starscream 4.0.4

Describe the bug
Hello, we received an issue in https://github.com/aws-amplify/aws-appsync-realtime-client-ios/issues/90 regarding a memory leak. The referencing issue is a package that uses Starscream 4.0.4. The customer describes a memory leak when running Instruments.
>    9 Starscream TCPTransport.connect(url:timeout:certificatePinning:) ../ios/Pods/Starscream/Sources/Transport/TCPTransport.swift:80
  10 Starscream protocol witness for Transport.connect(url:timeout:certificatePinning:) in conformance TCPTransport ../ios/Pods/<compiler-generated>:0
  11 Starscream WSEngine.start(request:) ../ios/Pods/Starscream/Sources/Engine/WSEngine.swift:67
  12 Starscream protocol witness for Engine.start(request:) in conformance WSEngine ../ios/Pods/<compiler-generated>:0
  13 Starscream WebSocket.connect() ../ios/Pods/Starscream/Sources/Starscream/WebSocket.swift:135
  14 AppSyncRealTimeClient closure #1 in StarscreamAdapter.connect(url:protocols:delegate:) ../ios/Pods/AppSyncRealTimeClient/AppSyncRealTimeClient/Websocket/Starscream/StarscreamAdapter.swift:47
  15 AppSyncRealTimeClient thunk for @escaping @callee_guaranteed () -> () ../ios/Pods/<compiler-generated>:0

I wanted to open this issue for your awareness as we gather more information. From a glance at the information provided, it looks like the problem is in TCPTransport.swift:80
Steps to Reproduce
Will provide once we have more details from referencing issue (https://github.com/aws-amplify/aws-appsync-realtime-client-ios/issues/90) or more information when we reproduce it ourselves.
Expected behavior
No memory leaks
Environment:

OS/Version: [e.g. iOS/13.3]
Starscream Version [e.g. 4.0.4]: 4.0.4
Xcode version [e.g. 11.5]

Any steps to reproduce, sample projects, etc would be appreciated.


Can't change the shortcut and the plugin is not working

When I go to the setting section on remnote and then keyboard shortcuts and hit the X button next to the plugin hint (by default is Crl + Shift + : , remains the same and does not allow me to change, when I want to place a hint in a new cloze card, the cloze card is tagged with the cloze hint tag, but the hint does not appear neither when I am editing the document nor when I want to review the card

I was not able to change the shortcut for the hint plugin, instead I solved this changing the shortcut for open a separate panel, this revolved the issue.


react native run-ios fails. ios build fails . android works

Describe the bug
No code changes on my side. Xcode update hapenned and now the build fails. Android works just fine. here is the error i get:
** BUILD FAILED **
The following build commands failed:
SwiftEmitModule normal x86_64 Emitting\ module\ for\ Stripe (in target 'Stripe' from project 'Pods')
SwiftCompile normal x86_64 Compiling\ AddPaymentMethodViewController.swift,\ AfterpayPriceBreakdownView.swift,\ Analytic.swift,\ Analytic+Payments.swift,\ APIRequest.swift,\ ApplePayHeaderView.swift,\ Async.swift,\ BackwardsCompatibleColors.swift,\ BillingAddressEditView.swift,\ BottomSheet3DS2ViewController.swift,\ BottomSheetViewController.swift,\ CardDetailsEditView.swift,\ CardScanningView.swift,\ CheckboxButton.swift,\ CheckboxElement.swift,\ ChoosePaymentOptionViewController.swift,\ CircularButton.swift,\ ConfirmButton.swift,\ ContainerView.swift,\ DefaultPaymentMethodStore.swift,\ DimmedView.swift,\ Dropd
package.json:
"@stripe/stripe-react-native": "^0.1.4",
i saw some other folks got this error and it solved for them to update to ios 14.0. i did the same but does not seem to solve my issue. here is my podfile:
platform :ios, '14.0'
xcode version:
Version 14.0.1 (14A400)

Me too having the same issue with Xcode 14.0.1 (14A400) and iOS SDK 16.0

That version of stripe-react-native is too old to run with Xcode 14. You should try and use the newest version of stripe-react-native if you're building with Xcode 14

thanks @charliecruzan-stripe . upgrading fixed the ios issue but now android build fails .. i changed following settings as per what is there in example..
buildscript {
ext {
googlePlayServicesVersion = "+"
firebaseMessagingVersion = "21.1.0"
buildToolsVersion = "30.0.3"
minSdkVersion = 21
compileSdkVersion = 33
targetSdkVersion = 31
ndkVersion = "21.4.7075529"
}

but i get this error now:

Task :stripe_stripe-react-native:compileReleaseKotlin FAILED
e<EMAIL_ADDRESS>(40, 19): Unresolved reference: reactApplicationContext

i am on react-native  "react-native": "0.63.4", if that helps.

I see- getReactApplicationContext was introduced in RN 0.64, and is not present in 0.63. The changelog mentions that v0.8.0 requires React Native 0.64 and above.


AutoRefreshingTokenCredential is always expired for AzureCliCredential

It seems that changing from chrono to time caused the az account get-access-token --output json --resource "https://storage.azure.com/" command date to be converted to an expired date.
I've ran tests connecting to Azure Storage Account Queues and it works without AutoRefreshingTokenCredential, but with it, it hangs in the refreshing loop.
I've created the following test, and it fails:
    #[test]
    fn test() -> azure_core::Result<()> {
        let tr = AzureCliCredential::get_access_token(Some("https://storage.azure.com/"))?;
        let token = TokenResponse::new(tr.access_token, tr.expires_on);

        println!("{}", token.expires_on);
        // Prints 2022-11-01 16:18:56.0 +00:00:00
        // But the correct time would be `2022-11-01 16:18:56.0 -07:00:00` Notice the TZ portion.
        // Typing `date` on terminal I get: Tue Nov  1 15:05:40 PDT 2022

        let expired = token.expires_on < OffsetDateTime::now_utc() + Duration::from_secs(20);

        assert!(!expired, "Brand new token should not be expired.");
        Ok(())
    }

This is fixed in #1176


Keyboard Shortcuts Sometimes Don't Work

Sometimes keyboard shortcuts fail to work for a little while.  They appear to start working again after a menu has been opened in the top menu bar.

[ ] File menu
[ ] Edit menu
[ ] Deck menu
[x] Help menu


Follow AIP-135 guidance for cascading deletion

Add "force" field to Delete requests in protos
Update expected protoc version to 3.19.3
Regenerate files from updated protos
Update test seeder to ignore nil resources
Follow AIP-135 guidance for cascading deletion
Use transactions for data consistency on deletion
Add tests for cascading deletion

Fixes #414.

I'll look at this more closely after #428 is merged - could we bump the protoc version in a separate PR?

I opened #432 to update the protoc version. The reason I updated the version is because my machine's protoc version upgraded and I couldn't easily downgrade it to rebuild the protos.


Add bootstrapper

This pull request adds a bootstrap static method to Driver.js, this method instantiates a new Driver.js based on custom attributes.

Hey Luís, thanks for the PR. While the PR looks good, we don't have any plans to add this. I don't want unnecessary feature bloat. But thanks though.


Office Integration not working in the new update release

Description
Hi the support team.
I've installed the newest release of DBeaver.  (Version <IP_ADDRESS>411171748).
After the installation, as usual,  the office integrattion addon has been removed and I reinstalled it.
So now it's reinstallaed with the version as below.

The thing is when I try to extract the result, I get an error message.

Would you have any clue how to solve this please ?
Best regards.
DBeaver Version
<IP_ADDRESS>411171748
Operating System
Server Wallix -
Database and driver
DataBase : SQLServer
Driver : MS SQL Server / SQL Server 12.8.0

Steps to reproduce

Run a simple SQL statement
Extract the result clicking on the button Excel and get the error message.

Additional context
No response

Hello @Yoan222,
Can you please provide log files? You can find instructions here: https://github.com/dbeaver/dbeaver/wiki/Log-files

Are you sure it worked against the same query before? It seems like that issue was always present.

Hi,
Yes I'm sure it worked before with the script. And I encountered the issue with another script. (My colleagues as well).
OK let's wait monday then.
Thank you very much.

I suppose the issue is solved


OracleJava/java-8 run build.sh err:Segmentation fault  (core dumped)

WIN10 1909 -> WSL(1) -> Docker ce
docker version
Client:
 Version:           18.06.1-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        e68fc7a
 Built:             Tue Aug 21 17:24:51 2018
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.1-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       e68fc7a
  Built:            Tue Aug 21 17:23:15 2018
  OS/Arch:          linux/amd64
  Experimental:     false

./build.sh

... ...
 ---> Running in 9cbf5bece6ec
+ yum install -y gzip tar
Loaded plugins: ovl
Resolving Dependencies
--> Running transaction check
---> Package gzip.x86_64 0:1.5-10.el7 will be installed
/bin/sh: line 1:     8 Segmentation fault      (core dumped) yum install -y gzip tar
The command '/bin/sh -c set -eux;       yum install -y          gzip            tar     ;       rm -rf /var/cache/yum' returned a non-zero code: 139
... ...

but FROM centos:7 is OK

We do not support running Oracle Linux in Docker under WSL1. You may have better luck with WSL2, but it would still be unsupported.


Add smaller centered window size option

Hi,
would be great to have the tool available in a repository for installing it via home brew cask.
Also I would like to prefer smaller figures to display yippy ... for my eye it comes mostly much to big
Even the small sized center window is very huge on 27" screen.
Currently I'm using Clipy since years and Yippy could be an suiting candidate to rep,ace that but it should not appear linke a screen eater.

Same as https://github.com/mattDavo/Yippy/issues/19

Resolved in https://github.com/mattDavo/Yippy/releases/tag/2.6.0

Resolved in https://github.com/mattDavo/Yippy/releases/tag/2.6.0


Deprecate clang-ocl and replace with clang

On the HIP backend MIOpen uses clang-ocl which is being deprecated. This PR replaces the use of clang-ocl with clang to compile OpenCL kernels on the HIP backend.

FYI: @atamazov

@JehandadKhan could you attach the perf benchmark report to the JIRA ticket?

@JehandadKhan could you attach the perf benchmark report to the JIRA ticket?

The point is either compiler should support clang-ocl, or there should be no performance regressions using clang instead. As we recall the later was not the case unfortunately. We need to keep track of that.

@JehandadKhan It seems more important than #1626. I just want to prioritize my activities, please confirm, thanks!

@JehandadKhan It seems more important than #1626. I just want to prioritize my activities, please confirm, thanks!

We are requesting staging tests on this branch to verify if this is a drop-in replacement. So far I doubt so since we've already seen some perf variations.

Convert to draft? @JehandadKhan

@junliume Done, can we decide what is our way forward ?

This change is needed when the base CI docker image is updated to ROCm 5.2.3

@junliume @JehandadKhan 👍 This is very good as it resolves OpenCL offline build issues.
Right now I am testing if OpenCL kernels built via offline compiler are slower (or faster) vs COMGR-built ones (gfx906/60, FP32 and FP16 convolutions).

@junliume @JehandadKhan 👍 This is very good as it resolves OpenCL offline build issues.
Right now I am testing if OpenCL kernels built via offline compiler are slower (or faster) vs COMGR-built ones (gfx906/60, FP32 and FP16 convolutions).

Thanks @atamazov. I suspect there are some issues, but I have not been able to confirm/deny them. If the args in MIOpen need to be changed, we can fix them in a subsequent PR.

@junliume @JehandadKhan 🟡 Performance of FP32 OCL kernels built with offline compiler is within 5% in ~90% of configs. In other 10% (32 out of 279) of configs performance varies from 0.55 to 1.90 from original. On average, I see +2...4% performance gain (numbers vary depending on how you calculate the average).
🔴 With FP16 the results are similar, but worse. Regressions reach 0.15 (~6X drop) for several WrW configs, and overall performance diff on average is about of 5-20%, which requires investigation at least. The worst case:
./bin/MIOpenDriver convfp16 -x 10 -y 5 -W 341 -H 79 -c 32 -n 32 -k 32 -p 0 -q 0 -u 2 -v 2 -l 1 -j 1 -g 1 -F 4

Helper script to reproduce some of the regressed cases: test-smoke-opencl-comgr-vs-offline-reproduce.sh.txt
I am going to repeat testing with something never than 5.0. I would appreciate if someone would share the latest 5.x RC docker with me.

@junliume @JehandadKhan 🟡 Performance of FP32 OCL kernels built with offline compiler is within 5% in ~90% of configs. In other 10% (32 out of 279) of configs performance varies from 0.55 to 1.90 from original. On average, I see +2...4% performance gain (numbers vary depending on how you calculate the average).
🔴 With FP16 the results are similar, but worse. Regressions reach 0.15 (~6X drop) for several WrW configs, and overall performance diff on average is about of 5-20%, which requires investigation at least. The worst case:
./bin/MIOpenDriver convfp16 -x 10 -y 5 -W 341 -H 79 -c 32 -n 32 -k 32 -p 0 -q 0 -u 2 -v 2 -l 1 -j 1 -g 1 -F 4

Helper script to reproduce some of the regressed cases: test-smoke-opencl-comgr-vs-offline-reproduce.sh.txt
I am going to repeat testing with something never than 5.0. I would appreciate if someone would share the latest 5.x RC docker with me.

./bin/MIOpenDriver convfp16 -x 10 -y 5 -W 341 -H 79 -c 32 -n 32 -k 32 -p 0 -q 0 -u 2 -v 2 -l 1 -j 1 -g 1 -F 0 -V 1 -s 0 -w 2 -t 1 -i 6 -C /home/atamazov/dockerx/miopen-verify2 -F 4
MIOpen(HIP): Info [FindConvBwdWeightsAlgorithm] BWrW Chosen Algorithm: ConvOclBwdWrW2<2> , 1638400, 41.2808
GPU Kernel Time Backward Weights Conv. Elapsed: 6.110705 ms (average)
GPU Kernel Time Backward Weights Conv. Elapsed: 41.274544 ms (average)  <== clang is this much worse than clang-ocl??

@junliume Than COMGR. clang-ocl is not working with my ROCm 5.0, maybe I need to install some specific version of clang-ocl?

@junliume @JehandadKhan
FP32 OCL kernels with ROCm 5.3.022305-mainline-10659:

93% configs are on par
7% configs show perf diff from -80% to +30%
overall perf regression is 0...9% on average

FP16 OCL kernels with ROCm 5.3.022305-mainline-10659:

95% configs are on par
5% configs show perf diff from -80% to +24%
overall perf regression is 2...9% on average

I am going to find and, if possible, fix the root reason.

@junliume @JehandadKhan 🔴 It seems like we have a bug in the compiler that I am unable to work around.
I am going to prepare a reproducible bug report for the compiler team. More info tomorrow...


[ERROR] Unknown output file extension provided

Hi,
I get the following error every time I run the profiler
[14:19:17] Calling ScoreDataExtractor with -msvc -start -d 1 -td 1
Starting MSVC recording...
Recording session started successfully!
Execution Time: 06ms
[14:19:17] Building...
[14:19:29] Calling ScoreDataExtractor with -msvc -stop -tp 100 -td 1 -d 1 -o C:\Git\Pathtracer\compileData.scor
[ERROR] Unknown output file extension provided. The MSVC generator only knows how to generate .scor or .etl files.
Execution Time: 00ms
[14:19:29] [ERROR] Score Data Extractor process failed with code 1. Please check the output pane for more information.
[14:20:45] Score generation completed!

I also get the error A recording is currently in progress on your system is preventing CompileScore from starting a new one.This can occur if you forgot to stop a CompileScore recording prior to running the start command, or if other processes have started ETW traces of their own.Please try running the CompileScore -stop command. every time I dont manually stop the profiler with tracelog -stop MSVC_BUILD_INSIGHTS_SESSION_COMPILE_SCORE

Thanks for sharing the issue! I have never seen this before, the actual output path looks solid and it has the correct extension.
It looks like the stop fails for some strange reason when parsing the output file. This makes the extractor never perform the real stop and leading to the second issue you are describing.
I will have a look when I have some free time.

After clean install of compiler score I get:
[10:36:39] Calling ScoreDataExtractor with -msvc -start -d 1 -td 1
Starting MSVC recording...
Recording session started successfully!
Execution Time: 03ms
[10:36:39] Building...
[10:39:21] Calling ScoreDataExtractor with -msvc -stop -tp 100 -td 1 -d 1 -o C:\QDI\Revenue\Source\Features\4.0\[PBI-135122] Interactive FuG Switches\NG.Evaluations\compileData.scor
[ERROR] Unknown output file extension provided. The MSVC generator only knows how to generate .scor or .etl files.
Execution Time: 00ms
[10:39:21] [ERROR] Score Data Extractor process failed with code 1. Please check the output pane for more information.
[10:39:59] Score generation completed!

Sorry for the late reply. Last weeks have been busy on my end.
Looks like something is wrong with the std::filesystem extension() function. As you said, that dot in the path might be messing with it. It still won't explain why @jan-van-bergen 's path is also failing. I think I will replace that code for my own path extension checker.
Regarding the 'Build and Profile' for the whole solution, I want to add also something to build and profile a single project and a single file.

Sorry for the late reply. I finally had time to dedicate to this.
I fixed some issues with the output path in the Data Extractor:

There were issues when the path had dots or spaces. (I also replaced the IsExtension implementation to not use the stl filesystem extension implementation)
whenever the Stop fails due to what the code thought was bad input data it will now cancel the trace as a fallback to avoid the mentioned tracelog lock.

I hope this helps with the situation. Please let me know if the issue is still present after version 1.5.7.
Thanks for the feedback! It is really appreciated.

Having the same issue with 2022.

...It needed an elevated VS. Why tho?

It looks like it is complaining that multiple recordings are happening.
The MSVC build insights uses the OS event system and are global on the machine, so you don't want to trigger multiple builds while profiling as it will pollute the results with data from other projects. you can try using the 'tracelog -l' command from an elevated command prompt to see if there the tracing session is dangling and kill it if needed.
As a side note it might be nice to have a button to force kill zombie tracing sessions, or at least make the start kill the previous one if existing. Sadly that's not the default behavior provided by the MS SDK atm. But I could try to detect it and force a stop before a start if needed.
I discovered It is not mandatory to use an elevated VS to use the Build SDK ( even thou MS documentation requires it ), that's why I could integrate it properly within VS without problems. Inspecting the tracelogs on your machine might need elevated privileges.

Tried running tracelog or CompileScore -stop, but they aren't recognized. Also tried from a devenv console, same issue with CompileScore, apart from tracelog -l having no result.
Just now tried running tracelog -l in a devenv console from an elevated VS and I'm getting many results. One of them is
Microsoft-Windows-Rdp-Graphics-RdpIdd-Trace and another is Microsoft-VisualStudio-Telemetry-PerfWatson2-29336. There are others but I don't recognize any other potential deal breakers, unless we want no .etls in progress whatsoever.
PS: Not sure if it affects anything, but I also see an Avg-IDP logger. Avg tends to be a thorn on one's side when you least expect it, so I'm mentioning it.

OTOH, it makes no sense if this error is only there when you run VS without elevated rights, yet it does not happen when you do, if running ETW's are the issue. Shouldn't that affect elevated VS as well?


Updated New/Set-RetentionComplianceRule topics

Per Issue #7026, the following parameters don't work with Teams retention rules:
ApplyComplianceTag
ContentContainsSensitiveInformation
ContentMatchQuery
ExcludedItemClasses
ExpirationDateOption
PublishComplianceTag
RetentionDurationDisplayHint

Docs Build status updates of commit 5e611a8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-RetentionComplianceRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-RetentionComplianceRule.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 5e611a8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-RetentionComplianceRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-RetentionComplianceRule.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[BUG] Metric Missing when upgrading from 0.38 to 0.39

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
With the same config, a dynamic metric is missing after the update : StorageBytes on AWS/EFS.
It seems to be related to the dimensions filter and the fact that, as documented by AWS, this specific metric comes with an other Dimension.
It seems to be related to this Pull Request from @femiagbabiaka.
The metric comes with two dimensions
    <Metrics>
      <member>
        <Namespace>AWS/EFS</Namespace>
        <MetricName>StorageBytes</MetricName>
        <Dimensions>
          <member>
            <Name>StorageClass</Name>
            <Value>Total</Value>
          </member>
          <member>
            <Name>FileSystemId</Name>
            <Value>fs-xxxxxxxxxxxxxxxxx</Value>
          </member>
        </Dimensions>
      </member>
      [...]

And the dimensionsFilter discovered has only one filer, on FileSystemId, so it skips the metrics on this line.
It was also reported in this comment by @rasr12 in https://github.com/nerdswords/yet-another-cloudwatch-exporter/issues/643#issuecomment-1222581687_
Expected Behavior
The StorageSize metric (and probably others with the same issue) still works on new release
Steps To Reproduce
With this config, it does not work:
---
apiVersion: v1alpha1
sts-endpoint: eu-north-1
discovery:
  jobs:
  - type: efs
    regions:
      - eu-west-1
      - eu-west-2
    metrics:
      - name: ClientConnections
        statistics:
          - Sum
        period: 60
        length: 300
      - name: "StorageBytes"
        statistics:
          - Average
        period: 900
        length: 3600

Anything else?
I managed to workaround this issue by using static configuration, which allows to specify dimensions :
static:
  - namespace: AWS/EFS
    name: arn:aws:elasticfilesystem:eu-west-2:XXXXXXXXXXX:file-system/fs-xxxxxxxxxxxxxxxxx
    regions:
      - eu-west-2
    dimensions:
      - name: StorageClass
        value: Standard
      - name: FileSystemId
        value: fs-xxxxxxxxxxxxxxxxx
    metrics:
      - name: "StorageBytes"
        statistics:
          - Average
        period: 900
        length: 3600

Thanks for the detailed report @mloiseleur, will have a look at this.

@mloiseleur I've merged a fix (https://github.com/nerdswords/yet-another-cloudwatch-exporter/pull/664), would you be able to test the code from master?

Hello,
I can confirm this works on my use case. Thanks !


I have code but not the specific way

Hello, I do not use or do code but I think I saw who to initiate and when I do it it's say he doesn't found the specific way, I don't unterstand anyone has a suggestion ?

Just noticed this in my inbox (I'm not officially contributing, but have been trying to help with "question" type issues for a while), is this still relevant?
If so, what are you trying to say? From what I could gather, you're getting a cryptic response when running this from command line, correct? And if that's true, can you copy some console logs of what you're doing and the results it gives you? Simply the commands you tried to launch it with, ideally including the directory (you can censor your PC username if you want), and the console output.

Hey hi, I forgot about this comment thanks for response, with luck I find a solution, have a great day man


Fixed query parameters (where not forwarded to SailsSocket)

Bugfix as stated for issue#45 (https://github.com/balderdashy/sails.io.js/issues/45).

Any idea when this will go in? I would love to be able to use it.

Thanks @weblogixx.  Ended up merging #51 which was similar but without the whitespace changes (and with tests!)


You can teleport to a lodestone that no longer exists if it's in unloaded chunks

Lodestone Compass still works even if the Lodestone is destroyed. Btw is it possible to add exp cost when using Lodestone TP

The reason this bug happens is because I just use the vanilla behaviour of lodestone compasses to track when the lodestone has been broken, which only works when both the compass and chunk are loaded. If the chunk is not loaded, compasses will not correctly update to be "unlinked" from their lodestone and show the spinning animation, and instead will act like they are linked just fine until you are looking at them while the chunk with those coordinates in is loaded
To fix this and correctly check if a lodestone can be teleported to in my plugin, I would need to load the chunk the lodestone is in, whichever dimension that might be
This is currently beyond the lengths I'm willing to go to fix this bug and I actually was aware of this when originally making the plugin, but I'll keep it in mind for if I come up with an easy solution

As for an XP cost for teleporting, I've already got #6 to track that as someone suggested it a few months ago just as an idea - If you want it for your server I can add it
I'll look into as well as the dimensions feature request you made

The reason this bug happens is because I just use the vanilla behaviour of lodestone compasses to track when the lodestone has been broken, which only works when both the compass and chunk are loaded. If the chunk is not loaded, compasses will not correctly update to be "unlinked" from their lodestone and show the spinning animation, and instead will act like they are linked just fine until you are looking at them while the chunk with those coordinates in is loaded
To fix this and correctly check if a lodestone can be teleported to in my plugin, I would need to load the chunk the lodestone is in, whichever dimension that might be
This is currently beyond the lengths I'm willing to go to fix this bug and I actually was aware of this when originally making the plugin, but I'll keep it in mind for if I come up with an easy solution

Meaning once they use the compass in the broken lodestone? all other compasses bound to it will not work anymore? cause the chunk has been loaded?

Meaning once they use the compass in the broken lodestone? all other compasses bound to it will not work anymore? cause the chunk has been loaded?

In order for a particular stack of lodestone compasses to "know" its lodestone is broken and become an "unlinked" compass where it just shows the random spinning animation, both things have to simultaneously be true:

The compass is in a player's inventory
The chunk with that lodestone in is currently loaded

So if the compass is in a chest it will not "realise" the lodestone is broken until a player picks it up, and at the time the player picks it up the chunk has to be loaded, otherwise the lodestone compass will still continue to act like the lodestone wasn't broken
Please see https://bugs.mojang.com/browse/MC-176038 which is an open bug report in vanilla Minecraft about this
I hope that clears up your question, in short not all compasses will update correctly when a lodestone is broken


Use travis branch to determine master

Fix for the fix, now it deploys properly, checked on my fork

Thank you 👍


Is DeployStructLib.Parts.Cloth.Initializers.Cloth_Mass_initializer missing?

DeployStructLib.Parts.Cloth.Initializers.Cloth_Mass_initializer is referenced, but not found. Should it be Cloth_MassLoc_initializer?

That may be an artifact of some changes I made a long time ago before moving to git. I've been thinking about simplifying/cleaning up some of the cloth, so let me revisit this.

I've finished simplifying the cloth block.  It should be easier to understand (hopefully) and maintain (hopefully).


Initial commit for GNOME network manager

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 2 files pending identification.

Protex Server Path: /home/blackduck/github/rdkservices/4876/rdkcentral/rdkservices

Commit: 779fe57b2a804f7d386f47e3c1a73ab359d0f2c9

Report detail: gist

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 2 files pending identification.

Protex Server Path: /home/blackduck/github/rdkservices/4876/rdkcentral/rdkservices

Commit: 779fe57b2a804f7d386f47e3c1a73ab359d0f2c9

Report detail: gist

WARNING: A Blackduck scan failure has been waived
A prior failure has been upvoted

Upvote reason: OK - code not matching.  All code files should have RDK headers please.

Commit: 779fe57b2a804f7d386f47e3c1a73ab359d0f2c9


Bump minimum allowable Dask version

Should we bump the minimum allowable dask version? I got a dependabot alert in another repo indicating an update to dask=2021.10.0 is necessary:

An issue was discovered in Dask (aka python-dask) through 2021.09.1. Single machine Dask clusters started with dask.distributed.LocalCluster or dask.distributed.Client (which defaults to using LocalCluster) would mistakenly configure their respective Dask workers to listen on external interfaces (typically with a randomly selected high port) rather than only on localhost. A Dask cluster created using this method (when running on a machine that has an applicable port exposed) could be used by a sophisticated attacker to achieve remote code execution.

Here is where we specify the minimum dask version for napari https://github.com/napari/napari/blob/e13f8651f8bd0151b5ef81f93b28035397576ec5/setup.cfg#L45

I should note: I haven't heard any chatter about this from the Dask side of things, this is just something that popped up on dependabot for another repo of mine the other day.
I don't know much about security, but the words "remote code execution" do make me twitchy.

This is clearly still an issue:
https://github.com/napari/napari/blob/606530943cbfcc3105df08d4b4eb987643263d21/setup.cfg#L50


Abbreviations

See JIRA DDF-450
Unable to find representation for 'Abbreviations' which are part of SOA table in the USDM model and in CDISC excel template. Is this an Alias?

Created by mistake as this just demanded an answer. Closed


Where does the site charge the cc

based on luhn algorithm. It's just a script like mrchecker not an API based checker.


ci(rultor): include gpg signature step

Fix: https://github.com/yegor256/takes/pull/1124#issuecomment-1142174574

@baudoliver7 thanks!


Cannot load EM from platform when some CPUs are hotplugged out - is it a problem?

My Juno board currently has CPUs 4 & 5 unplugged for some tests I want to run. When I try to load the energy model (from the sched_domains, i.e. DT-style full EM), the loader tries to load model data for CPUs which are not currently present in the sched domains. This is the log I get, which makes it pretty clear what happens, but I'm not sure if this is new or not.
I am using PR #605 right now.
2018-06-21 10:44:26,184 INFO    : TestEnv      : Attempting to read energy model from target
2018-06-21 10:44:26,824 INFO    : EMReader     : Attempting to load EM using from_sd_target
2018-06-21 10:44:28,421 ERROR   : TestEnv      : Couldn't read target energy model: No such file: '/proc/sys/kernel/sched_domain/cpu4/domain0/group0/energy/cap_states'
2018-06-21 10:44:28,423 INFO    : TestEnv      : Topology:
2018-06-21 10:44:28,424 INFO    : TestEnv      :    [[0, 3], [1, 2]]

The master branch can't load it either - same error is given. Question is, do we want to fix this and what does that really mean?

From the automated testing point of view, it is not a big issue since we load the EM once after boot, before anything happens on the target, so I'm assuming all CPUs are plugged in at this point.

Raising an exception may not be great, since the user could just want to load an EM corresponding to what EAS sees at this point in time, so I don't see any better way to handle that than logging the issue.


Not working Latest Android version like (Android 7+)

Hi,
NFCForms works well upto Android version 6 but it's not working in Android Version 7+.
Please sort out this issue ASAP
Not working device detail:
Samsung Galaxy S7 (Android version 7.0)
Thanks in Advance!!

Hi @SudharsanKrishnamoorthy, have you had any progress with this? I think I've come to the same problem.


Where is documentation on  query_result instance

I have received the response as a <class 'google.cloud.dialogflow_v2.types.DetectIntentResponse'>
response.query_result give me another object with the information that I would like to access.
But how do i do that? Is there any documentation for the object?
e.g. How do I access the list of parameters?

DetectIntentResponse is documented at https://cloud.google.com/dialogflow-enterprise/docs/reference/rpc/google.cloud.dialogflow.v2#detectintentresponse.

So I'm also having a problem with that, then I tried this a few minutes ago, maybe this could help
#queryResult
response = session_client.detect_intent(session=session, query_input=query_input).query_result
#getting intent
    intent = response.intent
#getting output contexts
output_contexts = response.output_contexts
#getting one of the output contexts
output_contexts[0]
#getting parameters
output_contexts[0].parameters

then you can continue accessing the parameters like you do dictionary. I agree the documentation kinda lacks. I'd be grateful if someone could explain abt this better

Sorry, I should have pointed you to more Python-specific documentation:

Some of the Python samples partially access query_result, e.g. https://github.com/dialogflow/dialogflow-python-client-v2/blob/master/samples/detect_intent_audio.py#L65.
The generated Python documentation provides more details about QueryResult: http://dialogflow-python-client-v2.readthedocs.io/en/latest/gapic/v2/types.html#dialogflow_v2.types.QueryResult

But agreed, this is somewhat hard to find and to read. We'll try to find some way to improve this.
Some more general notes:

The Python objects are generated automatically with protobuf. You can infer the interface from the API using the protobuf guide https://developers.google.com/protocol-buffers/docs/reference/python-generated.
If you already have an object in Python, help(response.query_result) and dir(response.query_result) are useful to get more inside into the internals.

caliph007,
I'd like to make it easier to find the python-specific reference documentation. Can you tell me where you looked for this? Also, are you using the Standard or Enterprise Edition?

Hi, this appears to be resolved, if not, please feel free to re-open.
Thanks! :)

Yeah I think documentation is still lacking. I basically just figured it out through trial+error using ipdb.

I have struggled with the same issues. Even diving into the documentation, I still find it challenging and time-consuming to find out how to access a simple parameter (e.g. named "Organizations" ) as part of the response - i.e. check if present, if present, get the value.
Could someone provide a simple example here? how do i iterate over parameters, and their fields/key values?


Deleting backend env failed

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v14.17.6
Amplify CLI Version
7.5.4
What operating system are you using?
Pop!_OS 21.10
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
In the process I manually deleted the existing S3 deployment bucket, and a lambda function IAM role for sending emails, which weren't initially deleted with the rest of the resources.
Amplify Categories
hosting
Amplify Commands
env
Describe the bug
Hello, I have ended up in a state where I have a backend which shouldn't exists connected to one of my apps, and I cannot delete it. This also means I cannot delete the app.
We've got a monorepo project, where one app "A" has backend connected, and other app B only has frontend. Now I was trying to make another frontend only app "C", but somehow accidentally ended up with the existing dev backend connected to it. I didn't realize this at first, because the appId show under "Edit backend" in console was different.
I tried deleting this dev backend that appeared in the new app C, noticing that now app A dev backend was also in "Deletion in progress" -stage. Looking at cloudformation logs, I see
Embedded stack arn:aws:cloudformation:eu-west-1:xxx:stack/amplify-xxx-dev-115515-functioncontroller-15G4OTLKJEV1/xxxxx-558d-11eb-8426-027144e8a80b was not successfully deleted: The following resource(s) failed to delete: [LambdaExecutionRole].  leading into The following resource(s) failed to delete: [functioncontroller].. So initially I was left with everything else deleted from dev besides this one  lambda. I dont 100% recall how I got rid of it. I also couldn't get new backend with the exact same name "dev" working, while trying to do that I believe I manually removed the existing S3 deployment bucket for the old environment.
Now I have managed to delete the dev backend from the app A (doesn't show up in the list anymore), but dev backend is still listed for the  app C. Trying to delete the backend "dev" backend shown for app C in the console gives Deleting backend env: undefined from app: xxx failed
Expected behavior
Deleting a backend environment should work.
Reproduction steps

Connect existing backend into a new app
Delete the backend from the new app

GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information
No response

In a case like this, you must use the amplify cli and provide ALL of the following: appid, env name, the profile, and the region on the delete command. In below command replace text that is wrapped in <> with your actual values. Then once that is done, you can go run the cli command to delete the app, or use the AWS console.
aws amplify delete-backend-environment --app-id <your_app_id> --environment-name <backend_env_name> --profile <your_local_aws_credentials_profile> --region <region_containing_app>
ex:
aws amplify delete-backend-environment --app-id fasldfjalsdkfj --environment-name dev --profile mymainprofile --region us-east-1

@0afcode few questions about this one.
you seem to be starting your command with aws amplify <whatever> but mention using the Amplify CLI which I'd expect to just be amplify <whatever>
where the heck do I find my profile name?
when running this as amplify I get:
The Amplify CLI can NOT find command:  delete-backend-environment

Hey @parvusville :wave: are you still experiencing this issue? Did the above aws-cli command work for you to delete this stray backend environment?

@josefaidt Hey, yes the above command worked for deleting the backend environment, and now I was able to delete the app from the AWS console. I only tried this now, as I back then wanted to avoid any kind of potential additional problems :sweat_smile: Note that this all included deleting the old dev backend, that I accidentally linked into this new app.

Word of warning about this. This will remove the app from Amplify but it won't clean up the resources that you had in AWS genrally for that app. You will still have Lambdas, OpenSearch, DynamoDB tables etc active within your setup for that environment that you will have to manually remove. I've been doing this by just searching for the "-test" environment name I want to get rid of and then manually deleting. If you do this within CludFormation stacks you can delete a lot of them by deleting the root stack (if you try to delete a child stack if will ask if you want to delete the parent to make it easier).
Biggest of these to clear out is the OpenSearch one as you get charged a minimum free ($50 ish) for that monthly one regardless if you aren't on the tiny instance.
Hope that helps :)


Edit OTU - remove taxon_name

It is impossible to delete a TaxonName from OTU through the web interface. If I delete the taxon name and click Save button, TaxonName comes back.

You must select the -- None -- option in those autocompletes to clear the field.  Type '--' in that one, then select it. Probably we need a reset button beside them.  If you think so add a new issue.

I don't think we can just do clear and save, this is a select.  Just like an html select field you actually have to select a (blank) value.  THe problem arrises when a user partially deletes the text- what then? What about deleting the text then typing the exact text back in again, should user have to select again?
We didn't have much issue with this in mx when everybody learned the idiosyncracies.  We actually tried the clear too- with timeouts etc. it just didn't work well.  The autocompletes there worked slightly different (maybe we can do this here) and -- NONE -- was appended to every result (@jlpereira maybe you can do that here for a temporary fix)

Closing this, the autocomplete selects work by selecting things, there is a long history of people getting used to this (in TW, and mx, etc.), and the ubiquitous nature of this element is fine.  Adding a button means clutter and space.


[IMPROVEMENT] Delays in IdP update when there is a large number of SPs

Describe the issue:
There is a listener called ApplicationIdentityProviderMgtListener [1]. When we update an IdP, the listener's doPreUpdateIdP() gets hit and it does followings.

Get a list of all SP names in the tenant
Iterate the name list and fetch SP objects (a huge on DB since there are multiple queries for each SP)
Iterate through the SPs and check whether any associated SP breaks due to disabling IdP (or one authenticator).

This flow causes a considerable delay for IdP update operation and causes LB timeouts.
How to reproduce:
Create around 100K service providers and try to update an IdP. There will be a huge delay.
Expected behavior:
Other than going through all the SPs to check the associations, we should query the associated SPs for the IdP in the consideration directly from the DB and do the validation.
Environment information

Product Version: All

Related issues
https://github.com/wso2/product-is/issues/6065
[1] https://github.com/wso2/carbon-identity-framework/blob/master/components/application-mgt/org.wso2.carbon.identity.application.mgt/src/main/java/org/wso2/carbon/identity/application/mgt/listener/ApplicationIdentityProviderMgtListener.java

AFAIR @emswbandara introduced an API to find associated SPs with an IDP.
We also have https://is.docs.wso2.com/en/latest/develop/idp-rest-api/#/Connected Apps/getConnectedApps REST API to get the connected apps.
We should be able to make use of this API and implement the change suggested by @rksk

I would consider this as an issue :)


Kafka update to 2.6.0

Added small changes to PR made by @sunshine69 (#1790)
Tested clean install and upgrade:

on prem Ubuntu 1804
AWS Ubuntu 18.04

Kafka updated in:

defaults file,
requirements.txt (centos, rhel, ubuntu)
changelog for 0.9
components.md

Additionally:
Added socket_settings section in Kafka yaml that allows to modify msg sizes, io threads number, network threads number - those values are often manually modified after epicli run.

In addition to comments please check that upgrade document is up to date and inspect the whole role with Ansible linter. The last point is not about this task, but otherwise It will be never done and improved.

My proposition is to create a new issue "Kafka role refactoring" or "Create Kafka Module" where major changes can be covered.

My proposition is to create a new issue "Kafka role refactoring" or "Create Kafka Module" where major changes can be covered.

Separate task is ok for me, but let's be honest, it will be taken to be done not soon/never.

My proposition is to create a new issue "Kafka role refactoring" or "Create Kafka Module" where major changes can be covered.

Separate task is ok for me, but let's be honest, it will be taken to be done not soon/never.

There is a lot of changes to do in kafka tasks (eg. versions in two separate files with the same value), but i don't think it's part of this one. We should create addition change with refactoring of this role

I created another issue for the creation of Kafka Module #1894. If the direction of this component will be changed, this component should be refactored.


libuv: 1.34.1 -> 1.34.2

Motivation for this change
This should fix some flaky tests on darwin: https://github.com/libuv/libuv/issues/2675
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build libuv

This needs to target staging.

Closing in favor of: https://github.com/NixOS/nixpkgs/pull/79381.


fix(curriculum): Remove unnecessary assert message argument from English Data Visualization challenges

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Related to issue #36400
This PR removes assert message arguments from testString for all of the Data Visualization section challenges.

Even if some were not covered (which I do not think), as long as PRs files affected make the correct change, I see no reason to hold any of these PR (in the series of PRs) up.


Add custom_metadata test case

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Spec at: https://github.com/grpc/grpc/blob/master/doc/interop-test-descriptions.md#custom_metadata

Copyrights :)

Done.

I think we do not need to wait for green as the last commit is a comment only change.


How to access compiler API

I am struggling with tapping Hoon compiler.
Basically I would like to be able to access stuff like parser, compiler and execution.
I have managed to uncover some bits, such as ++reap, ++slap, ++mule. With first two I seem to have generated parsed hoon. How do I get it to execute, and where can I find more information?

If you have a ++hoon, the core of the compiler is ++mint:ut.  With
[sut=type gen=hoon], (~(mint ut sut) %noun gen) will give you a [type nock]
cell.  The nock is a formula you can run with .*.
On Thu, Dec 21, 2017 at 11:22 AM, mikolajpp<EMAIL_ADDRESS>wrote:

I am struggling with tapping Hoon compiler.
Basically I would like to be able to access stuff like parser, compiler
and execution.
I have managed to uncover some bits, such as ++reap, ++slap, ++mule. With
first two I seem to have generated parsed hoon. How do I get it to execute,
and where can I find more information?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/issues/520, or mute the thread
https://github.com/notifications/unsubscribe-auth/AALyAZH_F0hmOPV1ce3Q2fsojgcM3QjQks5tCq_zgaJpZM4RKPr6
.

What's the use for mule then? I was hoping it would provide some kind of sandbox. Basically I want to run a code in a context where say certain decks are unaccessible. Is it possible?

It’s a sandbox.  It gives you a crash report if you crash.
Sent from my iPhone

On Dec 21, 2017, at 8:16 PM, mikolajpp<EMAIL_ADDRESS>wrote:
What's the use for mule then? I was hoping it would provide some kind of sandbox. Basically I want to run a code in a context where say certain decks are unaccessible. Is it possible?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

++slap will in fact both compile and run the thing, (slap !>([a=1 b=2])
limb+%a) should get you !>(1)
++mule actually cuts of all access to .^, which is kind of what you want;
as you saw in talk the combination (mule |.((slap !>(.) (ream input))))
will get you an either type containing an evaluated result or a stack trace
++mint on the other hand will give you nock, which you can run with .*
while not inside a !> vase; either in or outside of ++mule as per above
++mock, and the other arms near it in hoon.hoon, will give you more
raw-form virtualization, including accepting a non-"always crash" function
for .^
Note that either with .* or mock, you will not be able to get typed data
out, and will instead get the type as a value output by ++mint:ut. You can
however, validate the untyped * nock result as a specific type using
++hard, or get a pretty-printed rendering of the output [type value] "!>"
pair using ++text
On Thursday, 21 December 2017, mikolajpp<EMAIL_ADDRESS>wrote:

What's the use for mule then? I was hoping it would provide some kind of
sandbox. Basically I want to run a code in a context where say certain
decks are unaccessible. Is it possible?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/issues/520#issuecomment-353518327, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhnC6n2I4-gHwGNo_R7DSLW5d4GGcks5tCy0jgaJpZM4RKPr6
.

This is very helpful, I promise I will build a tutorial for this once I master these compiler concepts ;-)
Suppose I would want to have my own command line tool with parsing (which I presume is what talk is doing). Are there any specific arms in compiler core which I should be interested in?
As a side note, I discovered a nice way of sandboxing stuff.
For example, a simple 'calculator environment' would be:
(slap !>([add=add mul=mul div=div sub=sub]) (ream '(add 2 3)'))
To make sure I fully understand what's going on:

ream parsed the hoon and produced AST. It contains among other things, a wing (reference of sorts)
to add.
!>(x) produces a vase out of any noun x. In this case i supplied it with a tree
which contains relevant operations meant to be accesible.
One thing I don't understand here, is what exactly how exactly does it work. Does the vase for slap
becomes the subject (payload?) of the hoon? If I do !>(..zuse) it seems that at least standard library is accesible. Why !>(..hoon) does not at least expose arms defined in hoon?

For example, if I would want 'bare hoon' to be accesible, but disallow use of clay, to prevent user from messing with the filesystem, I would like to say !>(..hoon) and have the Hoon language and standard library accessible. For some reason it does not work this way...

Okay, it seems something like
(slap !>(..hoon:arvo) (ream '(add 2 5)'))
works. On the other hand, the same line with !>(hoon:arvo) also works, which adds to my confusion.
I know .. gets the core of an arm. But slap seems not to care...

After poking at it for some time, I think I mostly figured it out.
One last question: Is it possible to send moves to arvo vanes when zuse is in our subject?
By the time mule runs, the hoon is already executed as per @ohAitch .
So I don't understand how using mule would prevent anything.

|. is a "trap", a thunk of unexpected code. Just |.(foo) compiles to a
constant; mule takes the code within and executes it. (The other notable
usage of |. is parser combinators, where ++knee creates nesting levels on
demand, by defering parser construction until parse-time)
You send arvo moves as the callee, not the caller: you can certainly make
arvo moves by using the task-arvo type(though gall uses a simplified
whitelisted subset of them), but for them to have any effect, they'd need
to be produced by the ^- [(list effect) self] arm that is the entry point
from gall into the app. So it would very much require cooperation from the
virtualizer.
And if you're in a mark or ford web file, you have no way to cause effects
at all
I guess you could compile a duplicate arvo ~inside~ the user code, and send
moves to it, but the resulting inner-arvo state would have no bearing on
what processes the rest of the events flowing through your urbit; unless,
once again, you export the inner-arvo from the virtualizer, and also patch
arvo.hoon to accept its successor in an operation similar to |reset
On Friday, 22 December 2017, mikolajpp<EMAIL_ADDRESS>wrote:

After poking at it for some time, I think I mostly figured it out.
One last question: Is it possible to send moves to arvo vanes when zuse
is in our subject?
By the time mule runs, the hoon is already executed as per @ohAitch
https://github.com/ohaitch .
So I don't understand how using mule would prevent anything.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/issues/520#issuecomment-353568805, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhjjzakRrphIKjrYfDXwhZlyO3Ul3ks5tC4LFgaJpZM4RKPr6
.

I don't have much to add — but adding documentation in this area would be really fantastic.


Fresh install: pnpm build results in error

Brand new fresh install.
I go to https://github.com/zynth17/vitailse and click "Use this Template"

And create a new repo from this template.
Git clone my new repo to local.
Run pnpm i.
Run pnpm dev, works fine! 👍
Run pnpm build, results in error. First appears fine:

But finishes with error

Brand new fresh install.
I go to https://github.com/zynth17/vitailse and click "Use this Template"  And create a new repo from this template.
Git clone my new repo to local.
Run pnpm i.
Run pnpm dev, works fine! 👍
Run pnpm build, results in error. First appears fine:
But finishes with error

you can try to install workbox

you can try to install workbox

Perhaps it should be included with pnpm i?

So I installed workbox.
But it persists with the same error

Also tried pnpm i workbox-window, same error results.


Feature/edit queues page merge to main

Merge feature/edit-queues-page to main.

very good!

Nice job, lil bro


Allow (limited) passing of xt.{START, END} to twiss start/end

Description
Allow passing xt.START to the twiss parameter start and xt.END to the twiss parameter end, provided reverse=False.
Checklist
Mandatory:

[x] I have added tests to cover my changes
[x] All the tests are passing, including my new ones
[x] I described my changes in this PR description

Optional:

[x] The code I wrote follows good style practices (see PEP 8 and PEP 20).
[ ] I have updated the docs in relation to my changes, if applicable
[ ] I have tested also GPU contexts

The implementation should work also for start=xt.START, end='elm_name' or start='elm_name', end=xt.END. This is not tested, right?


Possible to run on Jetson Nano?

I'm trying to run the gpu accelerated version on a jetson nano. I'm not sure if it's supposed to work though.
I updated docker to the latest version. Unfortunately the gpu version of the package does not support the arm architecture. Thus, I tried to build myself.
When trying to build the Dockerfile.gpu I'm running into the following errors:
#0 47.29 Collecting pycparser
#0 47.33   Downloading pycparser-2.21-py2.py3-none-any.whl (118 kB)
#0 47.41      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 118.7/118.7 kB 1.6 MB/s eta 0:00:00
#0 48.74 Installing collected packages: webencodings, pylev, ptyprocess, msgpack, lockfile, distlib, zipp, urllib3, tomlkit, six, shellingham, pyrsistent, pycparser, poetry-core, platformdirs, pkginfo, pexpect, packaging, more-itertools, jeepney, idna, filelock, crashtest, charset-normalizer, certifi, cachy, attrs, virtualenv, requests, jsonschema, jaraco.classes, importlib-metadata, html5lib, dulwich, cleo, cffi, requests-toolbelt, cryptography, cachecontrol, SecretStorage, keyring, poetry-plugin-export, poetry
#0 58.98 Successfully installed SecretStorage-3.3.3 attrs-22.1.0 cachecontrol-0.12.11 cachy-0.3.0 certifi-2022.12.7 cffi-1.15.1 charset-normalizer-2.1.1 cleo-1.0.0a5 crashtest-0.3.1 cryptography-38.0.4 distlib-0.3.6 dulwich-0.20.50 filelock-3.8.2 html5lib-1.1 idna-3.4 importlib-metadata-4.13.0 jaraco.classes-3.2.3 jeepney-0.8.0 jsonschema-4.17.3 keyring-23.11.0 lockfile-0.12.2 more-itertools-9.0.0 msgpack-1.0.4 packaging-22.0 pexpect-4.8.0 pkginfo-1.9.2 platformdirs-2.6.0 poetry-1.2.0 poetry-core-1.1.0 poetry-plugin-export-1.1.2 ptyprocess-0.7.0 pycparser-2.21 pylev-1.4.0 pyrsistent-0.19.2 requests-2.28.1 requests-toolbelt-0.9.1 shellingham-1.5.0 six-1.16.0 tomlkit-0.11.6 urllib3-1.26.13 virtualenv-20.17.1 webencodings-0.5.1 zipp-3.11.0
#0 61.34 Looking in links: https://download.pytorch.org/whl/torch
#0 63.51 ERROR: Could not find a version that satisfies the requirement torch==1.13.0+cu117 (from versions: 1.8.0, 1.8.1, 1.9.0, 1.10.0, 1.10.1, 1.10.2, 1.11.0, 1.12.0, 1.12.1, 1.13.0)
#0 63.51 ERROR: No matching distribution found for torch==1.13.0+cu117
------
failed to solve: executor failed running [/bin/sh -c python3 -m venv $POETRY_VENV     && $POETRY_VENV/bin/pip install -U pip setuptools     && $POETRY_VENV/bin/pip install poetry==${POETRY_VERSION}     && $POETRY_VENV/bin/pip install torch==1.13.0+cu117 -f https://download.pytorch.org/whl/torch]: exit code: 1

For me it worked on a jetson orin using the following Dockerfile:
FROM swaggerapi/swagger-ui:v4.18.2 AS swagger-ui
FROM nvcr.io/nvidia/l4t-pytorch:r35.2.1-pth2.0-py3

RUN export DEBIAN_FRONTEND=noninteractive \
    && apt-get -qq update \
    && apt-get -qq install --no-install-recommends \
    python3-pip \
    ffmpeg \
    && rm -rf /var/lib/apt/lists/*

RUN pip3 install -U pip setuptools

WORKDIR /app

COPY requirements.txt ./

RUN pip3 install -r requirements.txt

COPY . .
COPY --from=swagger-ui /usr/share/nginx/html/swagger-ui.css swagger-ui-assets/swagger-ui.css
COPY --from=swagger-ui /usr/share/nginx/html/swagger-ui-bundle.js swagger-ui-assets/swagger-ui-bundle.js

CMD gunicorn --bind <IP_ADDRESS>:9000 --workers 1 --timeout 0 app.webservice:app -k uvicorn.workers.UvicornWorker

It is based on nvidia's pytorch container so it can easily make use of the GPU. However this container is based on python 3.8 so additional adjustments are necessary.

Finally I removed the importlib dependency from webservice.py to fix some error.
I guess there are better ways to solve this problem and keep this repositories structure, so I am providing this just as a reference of one way to possibly achieve your goal.

faster-whisper

Thanks for your script here.
How to set the model type =Largev3?


Create Random Password Generator in JavaScript #55

Hey @anuj840 , It will look more yours, if you remove geeksforgeeks written in the code. 😄
I would like to suggest some changes:

Please do add some basic styling.
Add the extension of the file instead of just putting your code as a file of none type.
Add your project to Directory: RandomPassword/USERNAME
Listen, It's very great that at least you have tried to write that code, copying is not bad, but please do modify your code such that it at least doesn't look like copied.
And do read contribution guidelines.
Thank You! 😃

I am sorry but there is no change in the project, on your latest commit.
Please resubmit your PR whenever you are sure that you have done well.
Thank You! 😄


Bump saw

Description of changes:

prove BIKE with full sizes
prove SIKE with full sizes
update all proof script to the latest saw

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

:exclamation: No coverage uploaded for pull request head (bump-saw@02a13a9). Click here to learn what that means.
The diff coverage is n/a.

travis is failing because it uses the old version of saw from the cache; it should succeed after deleting the cache

Deleted all caches and restarted build: https://travis-ci.org/awslabs/s2n/builds/626931448


Datepicker locale mobile format error

Describe the bug
On mobile devices, the datepicker formats the input Date with the current locale
How to reproduce
Stackblitz example.
Steps to reproduce the behavior:

Go to the example
View Page on Desktop-Size-Screen. it should show the current date
Reload the page with a mobile screen setting and look in the dev console of chrome.
See error

Expected behavior
The Date should parsed inside the input field with format 'yyyy-mm-dd' no matter which language is set
Versions
App

Angular: 7.2.5
Node: v11.10.0
Clarity: 1.1.0

Device:

Type: Mobile Screen Size
OS: Windows
Browser: chrome

Just a note, on mobile devices we completely deactivate our datepicker. We believe the native datepicker experience on all mobile devices is going to be better than the shrunk web one we could provide. In particular on phones, picking a date on a small calendar is really difficult, and users are accustomed to whatever the native experience of their phone is (typically spinning wheels on both iOS and Android, for instance).
I'm pretty sure we should still emit [(clrDate)] correctly though, so this does look like a bug to me.


Support HTTP Basic Authentication

We need to support HTTP basic authentication, so WbTstr can be used to access protected sites.
Possibilities include: embedding the credentials in the URL or performing an automation script (i.e. AutoIT).

Embedding in the url will give issues with some browsers as they will mark the url as malicious. I think we can use the Selenium IAlert.SetAuthenticationCredentials Method but we need to verify if it's implemented in all the major browsers.


[portable-file-dialogs] Add new port

[x] Changes comply with the maintainer guide
[x] The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
[x] Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx
[x] The versioning scheme in vcpkg.json matches what upstream says.
[x] The license declaration in vcpkg.json matches what upstream says.
[x] The installed as the "copyright" file matches what upstream says.
[x] The source code of the component installed comes from an authoritative source.
[x] The generated "usage text" is accurate. See adding-usage for context.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is in the new port's versions file.
[x] Only one version is added to each modified port's versions file.

@myd7349, Thanks for your PR, I see that the upstream code provides a CMakeLists file, why not install the CMakeLists file?

Note: I will be converting your PR to draft status. When you respond, please revert to "ready for review". That way, I can be aware that you've responded since you can't modify the tags.

@myd7349, Thanks for your PR, I see that the upstream code provides a CMakeLists file, why not install the CMakeLists file?

Hi @JonLiu1993 Thanks for your review.
Due to the lack of an "install" target in the CMakeLists.txt provided by the upstream repository, it is not possible to install the library using vcpkg_cmake_install. Currently, there is a PR that adds the install target for this library, but it has not been merged yet.
In light of this, considering that the library consists of a single header file, this approach has been adopted for installation.


Change some buttons to links

In this PR are changes to change 3 buttons in our app to links. Those buttons that are now links are:

create on recordset

generate the invalidate id when the component loads
add onContextMenu to trigger the same functionality for right click

bulk edit on recordset

changes for this case were done to allow for the link to be updated when pageLimit or reference change
reference can change independent of page limit changing when sorting or paging

add records on record in the related table actions

separate the rendering of link records and add records
generate the invalidate id when the component loads
add onContextMenu to trigger the same functionality for right click

The changes not made include the ok button in the error modal and the edit button in the action column. For the edit button in the action column, we made changes to use window.open and window.opener.updated to signal the data needed to be refreshed on focus instead of using cookies. Since this relies on using window.open, there's no way to replicate this functionality unless we also implement cookie storage with this change which had "issues" in the past.
Other changes in this PR include changing any use of window to use windowRef instead. I tested most of these cases to verify these changes still worked/ I tested 3 different login scenarios to verify the changes in login.tsx and authen.tsx. I didn't change the use of window in viewer since I wasn't sure how to test them exactly.
This PR issue resolves #2051.

We are not planning on making these change at this time since it would create inconsistency if we don't change all 4 proposed buttons to links. More details in the attached issue


Host Uptime Metric

Host Uptime metric is not available in current version. Is there any plan to add in next version?

Thanks for the suggestion, currently not planned but this shouldn't be too difficult

@Madhu1512, uptime is now available on tip, and will get integrated into the next release


[Feature Request] Allow Box to be rendered as semantic section elements like

Most a11y auditing tools expect pages to define content sections like <nav> and <main> to help screenreaders skip to the page content.
I expected to be able write something like this but got a Type '"nav"' is not assignable to type '"span" | "div" | undefined'. error:
const TopBar = (props) => {
  return <Box as="nav" className="TopBar">
    {props.children}
  </Box>
};

There's a workaround of <Box className="TopBar" asChild><nav>{props.children}</nav></Box> but that feels a little messier.
This should probably work the same for other semantic section-related elements like <header>, <footer>, etc.

as prop is there to improve ergonomics for the most common tags, use asChild for everything else. There’s nothing messy about it, that's why it's there in the first place.
Usually you wouldn't have more than a couple instances of a nav or a header in your app anyway.
Otherwise, there's just a lot possible of HTML tags, and we had to draw a line somewhere.


added support for container architecture specification

*Issue #, if available: generated lambda functions were not working properly if the cdk was built on an arm64 instance.
*Description of changes:

lib/constants.ts - added support for the specification of the architecture of the containers being deployed, default is to x86_64
lib/stacks/infra/core.ts - implemented config change using constants.ts to specify the architecture of the containers
lib/utils/apiFunction.ts - added helper function to translate string LAMBDA_CONFIG.archicture to proper enumeration value and config change using constants.ts to specify the architecture of the containers
lib/stacks/api/restApi.ts - config change using constants.ts to specify the architecture of the containers

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

seems like a duplicate of https://github.com/awslabs/mlspace/pull/39.

they are; i just wanted to get this up, as i knew from Kyle when i raised the issue with hiom that he had placed the ARM support in the backlog.  i just wanted to get my changes pushed back to y'all.

Thanks for the contribution @tomjansto! As discussed we've incorporated similar changes in #39 which will be included in our upcoming release.


fix: updated incorrect link

Updated incorrect link
Issue : asyncApi/website/Issue-1206

@Florence-Njeri @pratik2315 hey folks, pinging you for review.
I think you were not assigned by default because looking at docs, the order in https://github.com/asyncapi/generator/blob/master/CODEOWNERS should be flipped
Order is important; the last matching pattern takes the most precedence

Let me take a look

@Florence-Njeri @pratik2315 hey folks, pinging you for review.
I think you were not assigned by default because looking at docs, the order in https://github.com/asyncapi/generator/blob/master/CODEOWNERS should be flipped
Order is important; the last matching pattern takes the most precedence

Hey @derberg. So if I'm correct, the usernames that come after both @Florence-Njeri and @pratik2315 are kinda overwriting our assignments right? So.. the ideal order should be:
* @fmvilas @derberg @magicmatatjahu @jonaslagoni @asyncapi-bot-eve

# All .md files
*.md @Florence-Njeri @pratik2315

but wouldn't that restrict you guys from getting docs (markdown) related notifications?

but wouldn't that restrict you guys from getting docs (markdown) related notifications?

@pratik2315 good question. Yes, I think it works this way that you will get notifications first. It kinda makes sense to me, that first you and @Florence-Njeri get notification as you are md files maintainers. So basically you do the initial review, and you explicitly ping other maintainers if their review is also needed. So for example in case of link fix (like here) it is enough that you are pinged. Makes sense?
@anaysarkar7 thanks for your patience 🙏🏼 Can you update the PR title to start with docs:  and not use past tense? (use imperative mood please)
@pratik2315 @Florence-Njeri during review please make sure https://github.com/asyncapi/generator/blob/master/CONTRIBUTING.md#conventional-commits is followed. In case of docs, we should not use fix or feat as this will trigger release

but wouldn't that restrict you guys from getting docs (markdown) related notifications?

@pratik2315 good question. Yes, I think it works this way that you will get notifications first. It kinda makes sense to me, that first you and @Florence-Njeri get notification as you are md files maintainers. So basically you do the initial review, and you explicitly ping other maintainers if their review is also needed. So for example in case of link fix (like here) it is enough that you are pinged. Makes sense?
@anaysarkar7 thanks for your patience 🙏🏼 Can you update the PR title to start with docs:  and not use past tense? (use imperative mood please) @pratik2315 @Florence-Njeri during review please make sure https://github.com/asyncapi/generator/blob/master/CONTRIBUTING.md#conventional-commits is followed. In case of docs, we should not use fix or feat as this will trigger release

done :)

LGTM @anaysarkar7 🚀

/rtm


Debugger dock keep old stack trace from breakpoint when running new instance without breakpoint

Godot version:
3.2 beta3
OS/device including version:
win7-64
Issue description:
I seeing the stack trace in debug dock
Steps to reproduce:
I set a breakpoint ,then  in debug dock I see the stack trace.
Then if I run the game I can still se the previous stack trace.
Minimal reproduction project:
none

The description was a bit confusing for me but now I understand.
Here some reproduction steps:

set a breakpoint in an script.
run in debug mode until you reach the breakpoint. It generates stack trace in debug dock.
remove breakpoint.
run it again.

The project runs showing the previous stack trace as (without breakpoints) it didn't need to generate a new one. The question here is, do we want to clear the stack trace on every execution? I guess it could be considered intuitive clearing the stack trace on every run so the user doesn't gets the feel of having a trace not related to the actual execution. But I don't think it hurts that much leaving the last generated stack trace in the debug dock.

"But I don't think it hurts that much leaving the last generated stack trace in the debug dock even if it is not related to the actual execution."
Is is a quality code that someone want to delivery.  How we will know if what we left here it will be not the culprit for another nasty bug somewhere else?

I can confirm that it behaves as described and IMO it should be clear when running a new instance.
It's already fixed in 4.0, but not in 3.x.

Fixed by #66654.


Fix utilitycode generation for const fused typedef

Fixes #5230

@scoder Is it possible to get this released in 3.0.6 release? There is a conflict but the resolution is simple just merge everything together. I can do it but I don't want mess with PR of someone else.

@matusvalo feel free to fix the conflict.

@matusvalo feel free to fix the conflict.

I resolved the conflict but the master was merged to this PR . So I think we will need to cherrypick this PR to backport it to 3.0.X branch if we want to have it in 3.0.6...

We might be able to avoid the whole "deduplicate used names" work if we do this:
base_name = str(dtype).replace('_', '__').replace(' ', '_')
if dtyle.is_typedef:
    base_name = Naming.fused_dtype_prefix + base_name

And actually append the underscore to the Naming.fused_dtype_prefix string directly.
BTW, can't typedefs use Unicode names? If so, we'd need to pyunicode the name instead of just calling str().

Thank you, @da-woods, @matusvalo, and @scoder!

Note that I missed the 3.0.7 release train with this mostly by accident. This will have to wait a little longer for a 3.0.8 release, sorry.

No problem, Stéfan. :)
scikit-learn is still using Cython 0.29.X, and we were wondering whether bugs (such as this one) are going to be back-ported to 0.29.X.
Do you plan to continue to work on 0.29.X? What are your recommendations?

We've actually been very conservative with changes to 0.29.x, for years now. We artificially kept it alive for much too long already. My recommendation since at least 2022 was to migrate away from 0.29.x. We've designed 3.0 so that it won't be a difficult migration target. With a bit of code cleanup in the migration, you'll make your life a lot easier by using Cython 3, which is the current stable release series. It's really so much better.
We're currently focusing mostly on Cython 3.1, which will remove support for all Python versions before 3.7. That enables us to clean up the code base and optimise several bits of the language that we couldn't before due to differences between Python 2 and Python 3. It might be worth targeting that directly in your project. I hope to release it in just a few months. Even if it takes longer, you can still use Cython 3 for the time being. They are not very different from a user perspective.


Reset /lb completionist when new reqs get added

🚀 Feature Proposal
Reset the lb when new reqs get added, it only changes people's percentages if they personally do /completionist check. The way it is currently there won't ever be a new first to comp cape when new reqs get added unless everyone's percents get reset for the update or every currently comped player does /completionist check to reset their own percentage

Done in next update (added a command for us to reset it)


Support for NodeJS 22.x

If the feature solves a problem you have, specify it here.
Hey! Thanks for this tool. Unfortunately it doesn't work with Node 22 because of deprecated import assert syntax. Probably assert can just be replaced with with.
[webpack-cli] SyntaxError: Unexpected identifier 'assert'     at compileSourceTextModule (node:internal/modules/esm/utils:337:16)     at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:164:18)     at callTranslator (node:internal/modules/esm/loader:439:14)     at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:445:30)
Describe the proposed feature.
Now:
import unTypedSchemaOptions from './schemas/plugin-options.json' assert { type: 'json' };
New syntax:
import unTypedSchemaOptions from './schemas/plugin-options.json' with { type: 'json' };
Describe alternatives you've considered
No response
Additional context
No response
Importance
Would make my life easier

Hello @yuri-moskvin, thanks for the report!
Do you want to try to make the changes with a pull request?


Add default support for tenant qualified URLs

Describe the issue:
Currently,  tenant qualified URLs are not enabled in the Identity Server by default. We need to do a comprehensive gap analysis on tenanted URL unsupported features in Identity Server. Following this analysis, we should address these gaps to ensure that tenant-qualified URLs are enabled by default in the Identity Server.

PRs to fix integration test failures after enabling tenanted qualified URLs

https://github.com/wso2/product-is/pull/16683
https://github.com/wso2/product-is/pull/16756


Consider supporting React Native

It may be possible if we detect element's resize with onLayout of View and get scroll position from ScrollView.

what would be the difference with FlatList / SectionList / VirtualizedList?

Yes, I know there have been already FlatList and VirtualizedList (and also FlashList).
I'm not sure it's worth doing. If we were to make it, the RN version would work without configuration of height/width like web version. And it should support bi-directional infinite scrolling like Twitter App in the future.

@inokawa Update: we used FlashList in iOS expo app. In my experience it's focused on recycling views and it fails to accommodate certain use-cases (eg. reverse scrolling with sticky items).

Thank you for sharing the information!
Although React Native is a bit de-prioritized than something for web to me, it will be worth trying it.

@inokawa Same. Althought RN lists can be better, virtua can provide the most value in web given the lack modern, up-to-date and light weight solutions.

@inokawa Same. Althought RN lists can be better, virtua can provide the most value in web given the lack modern, up-to-date and light weight solutions.

Probably there are no flushSync alternatives in react native.
https://github.com/facebook/react-native/issues/41487

React Native 0.76 supported useLayoutEffect.
https://reactnative.dev/blog/2024/10/23/the-new-architecture-is-here#uselayouteffect