text:
[BUG] "findDOMNode is deprecated in StrictMode" error

Describe the bug
Browser freezes when I try to expand a node with few neighbors (9) from Amazon Neptune.
I can reproduce it in Firefox and Chrome (versions attached below).
The Console shows:
Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of Transition2 which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here: https://reactjs.org/link/strict-mode-find-node div Transition2@https://localhost:5173/node_modules/.vite/deps/react-transition-group.js?v=a5a5d86c:111:30 CSSTransition2@https://localhost:5173/node_modules/.vite/deps/react-transition-group.js?v=a5a5d86c:387:35 div TransitionGroup2@https://localhost:5173/node_modules/.vite/deps/react-transition-group.js?v=a5a5d86c:646:30 div div NotificationProvider@https://localhost:5173/src/components/NotificationProvider/NotificationProvider.tsx:69:37 div ThemeProvider@https://localhost:5173/src/core/ThemeProvider/ThemeProvider.tsx:35:23 DndProvider<@https://localhost:5173/node_modules/.vite/deps/react-dnd.js?v=8d77ea20:1591:18 QueryClientProvider2@https://localhost:5173/node_modules/.vite/deps/react-query.js?v=1bf679e6:2643:16 div ConnectedProvider@https://localhost:5173/src/core/ConnectedProvider/ConnectedProvider.tsx:40:7 Router@https://localhost:5173/node_modules/.vite/deps/react-router-dom.js?v=47b6e6dd:2697:7 HashRouter@https://localhost:5173/node_modules/.vite/deps/react-router-dom.js?v=47b6e6dd:3106:7
To Reproduce
Steps to reproduce the behavior:

Go to Graph Explorer
Click on Search Bar
Select one node with 9 neighbour nodes.  Click on "Add Selected". Selected node appears in the canvas.
Click on the new node in the canvas, limit returned neighbors to 1
Click on Expand
Browser freezes. Above error message shows up in the Console.

Expected behavior
I expected to see 1 neighbor node in the canvas when I click "Add Selected".
Desktop (please complete the following information):

OS: MacOS Monterey 12.6.2
Browsers: Chrome (109.0.5414.87 (Official Build) (x86_64)) and Firefox (102.6.0esr (64-bit))
Graph Explorer version: (pulled from Github today, 3.7.0)

Issue resolved in #211.

authors: rubenafo xiazcy

repo: aws/graph-explorer


text:
Support selection of media type in %%sparql cell magics

Is your feature request related to a problem? Please describe.
When using the %%sparql cell magic, I cannot change the media type that the results are printed in.  If I was submitting an HTTP query, I would be able to.
Describe the solution you'd like
I would like a parameter to be added to the %%sparql magic to allow me to specify the media type to output the results in.  For example, there is a long list of media types supported in Neptune listed at https://docs.aws.amazon.com/neptune/latest/userguide/sparql-media-type-support.html
Describe alternatives you've considered
Writing HTTPS requests in Python to achieve this is not user friendly, non-programmer friendly, and loses the convenience of the %%sparql magic.
Additional context

A media type parameter (--media-type/-m) had been added to %%sparql with #313. Resolving.

source: gharchive/issue

authors: brianok-aws michaelnchin

repo: aws/graph-notebook

license_type: permissive

license_source: github-api


text:
Non-string type support for AWS Tag values in the Provisoner CRD spec

Tell us about your request
Hi there,
Thank you for the awesome tool!
Please can you make it so that non-string typed values are supported in the spec.provider.tags attribute of the Provisioner CRD
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
We are trying to ensure consistent tagging across our infra to better understand costs in AWS. To do this, we generate a set of standardized tags in our Terraform, which is passed to all infra pieces to identify them to the product they were created for.
We are running Karpenter 0.10.1 via Helm deployed with Terraform
In the Terraform we declare our tags with values of mixed type (string, bool, number)
# terraform.tf

locals {
  tags = {
    Terraform   = true
    Root        = "path/to/root/in/git"
    Project     = "productA"
    CostCenterID = 43
    Environment = "Production"
  }
}

And then these tags are rendered out to a Provsioner spec values.yaml using terraform templates
# values.yaml.tpl

tags:
  ${indent(2, yamlencode(tags))}

# Renders out to
tags:
    Terraform: true
    Root: "path/to/root/in/git"
    Project: "productA"
    CostCenterID: 43
    Environment: "Production"

And the above tags block is placed in a Provisioner spec at spec.provider.tags
When trying to create a CRD with such tags it will issue error
│Error: cannot patch "<provisioner_name>" with kind Provisioner: admission webhook "validation.webhook.provisioners.karpenter.sh" denied the request: validation failed: v1alpha1.AWS.Tags: ReadString: expects " or n, but found t, error found in #10 byte of ...|rraform":true}}|..., bigger context ...|","root":"path/to/root/in/git","Terraform":true}}|...:

The issue seems to be that Karpenter expects only strings for Tag values where we are passing strings,bools and numbers.
It would be great if this supported other types of tag values and not just strings. (numbers,bools etc)
Are you currently working around this issue?
To work around this we first excluded non-string tags and then did some messy Terraform config to convert to string in the values.yaml

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Agree with Suket. Feel free to reopen if you'd like to continue the discussion

Thanks for the Feedback. I would agree with your comment this code fix rather belongs in Terraform if it weren't for the amount of other charts we are doing exactly this without issue, including official AWS and third party charts. Of the 10 or so Helm charts that we do AWS tagging from Terraform, this has been the only one so far that requires type conversion.
The AWS LB Controller chart supports boolean and number type tag values
The AWS EBS CSI Driver chart supports boolean and number type tag values
The AWS EFS CSI Driver chart supports boolean and number type tag values
Happy to leave closed if you still feel it should be, but please be aware this does not seem to be the route other charts have taken in this regard.
If you need to fix this issue in your Terraform code, this is how you could do it.
{for k,v in local.tags: k => tostring(v)}

Keep in mind, our push back is not in changes to the chart, but changes to the Provisioner API (CRD).

authors: ellistarn morganrowse

repo: aws/karpenter


text:
Remove namespace field for webhooks configuration in helm chart

Version

Karpenter: v0.16.1
Expected Behavior
MutatingWebhookConfiguration and ValidatingWebhookConfiguration should be cluster resources
Actual Behavior
Helm chart adds "namespace" field to their manifests
charts/karpenter/templates/webhooks.yaml:
...
  namespace: {{ .Release.Namespace }}
...

I think you are referring to L5 and  L48.
It makes sense to me to remove them, but is this currently causing an issue for you?

Yes, you are right, exactly these lines
I was installing karpenter with terraform + kustomize provider
https://registry.terraform.io/providers/kbst/kustomization/latest/docs
It generates resources id like this:
group/Kind/namespace/name with _ as a placeholder for empty values

So it generates id with namespace but cannot verify that manifest in k8s and print strange "resource not found" error


text:
no router for /api/posts

navigating to /api/posts fails since there is no router configured for it in server.js
This is as compared to /api/users and /api/threads which return all users and all threads respectively.
Additionally, the tutorial actually recommends testing api and posts services using that url.
The fix is easy...add this to ./3-microservices/services/server.js and /2-containerized/services/api/server.js
router.get('/api/posts', function *() {
  this.body = db.posts;
});

I have done this in a fork (as well as correcting a spelling error).

Merged thanks!

authors: mjtk-ktjm nathanpeck

repo: awslabs/amazon-ecs-nodejs-microservices


text:
Remove snowflake for kubelet secret-polling config

This is no longer needed since the regression (xref - https://github.com/kubernetes/kubernetes/pull/74755) had been fixed by changing to sane defaults in kubelet. And the fixes are already there in each of the latest patch versions we're publishing worker AMIs for:

1.14.7 (watching with regression fixed) https://github.com/kubernetes/kubernetes/blob/v1.14.7/pkg/kubelet/apis/config/v1beta1/defaults.go#L218
1.13.11 (polling) https://github.com/kubernetes/kubernetes/blob/v1.13.11/pkg/kubelet/apis/config/v1beta1/defaults.go#L217
1.12.10 (polling) https://github.com/kubernetes/kubernetes/blob/v1.12.10/pkg/kubelet/apis/config/v1beta1/defaults.go#L207
1.11 and 1.10 have always been at polling

/cc @M00nF1sh

source: gharchive/pull-request

repo: awslabs/amazon-eks-ami


text:
rl_game_server_autopilot

Issue #, if available:
https://t.corp.amazon.com/V146878261
Description of changes:
publish sample
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks for reviewing! I addressed all the actionable issues.

repo: awslabs/amazon-sagemaker-examples


text:
evaluate function issue of the Image Classification - Quick Start tutorial

the evaluate result seems incorrect.
Top-1 test acc: nan
I have tried on my pc. it shows similar messages as the tutorial and return the wrong evaluate result too
"UserWarning: Ignoring data/test/BabyPants of type . Only support .jpg, .jpeg, .png"
is it a bug of getting class names or listing the images? or is there changes about dataset and/or evaluate function?
Thank you

Thanks for reporting. It is a bug recently introduced. We will fix it.

built_in_tasks = {
    'mrpc': MRPCTask,
    'qqp': QQPTask,
    'qnli': QNLITask,
    'rte': RTETask,
    'sts-b': STSBTask,
    'cola': CoLATask,
    'mnli': MNLITask,
    'wnli': WNLITask,
    'sst': SSTTask,
    'toysst': ToySSTTask,
}

repo: awslabs/autogluon


text:
Fix aws_host_utils_is_ipv6 function

Description of changes:

The host will always be stripped of [] and will never be enclosed in it.

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

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

Project coverage is 83.12%. Comparing base (24e2396) to head (8a280d6).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1114      +/-   ##
==========================================
- Coverage   83.14%   83.12%   -0.03%
==========================================
  Files          56       56
  Lines        5760     5753       -7
==========================================
- Hits         4789     4782       -7
  Misses        971      971

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

repo: awslabs/aws-c-common


text:
feat(toolkit): ensure consistent zip files

Zip files were not consistent across deploys resulting in unnecessary S3 uploads and stack updates.
Ensure consistency by appending files in series (guarantees file ordering in the zip) and reseting
dates (guarantees same hash for same content).
Closes #1997, Closes #2759

Pull Request Checklist

[ ] Testing

Unit test added (prefer not to modify an existing test, otherwise, it's probably a breaking change)
CLI change?: coordinate update of integration tests with team
cdk-init template change?: coordinated update of integration tests with team

[ ] Docs

jsdocs: All public APIs documented
README: README and/or documentation topic updated
Design: For significant features, design document added to design folder

[x] Title and Description

Change type: title prefixed with fix, feat and module name in parens, which will appear in changelog
Title: use lower-case and doesn't end with a period
Breaking?: last paragraph: "BREAKING CHANGE: <describe what changed + link for details>"
Issues: Indicate issues fixed via: "Fixes #xxx" or "Closes #xxx"

[ ] Sensitive Modules (requires 2 PR approvers)

IAM Policy Document (in @aws-cdk/aws-iam)
EC2 Security Groups and ACLs (in @aws-cdk/aws-ec2)
Grant APIs (only if not based on official documentation with a reference)

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

Not 100% sure how to correctly unit test this... but I can confirm that I finally have the (no changes) message from the cli across deploys for stacks containing Lambda functions.

Got inspiration from here https://github.com/serverless/serverless/blob/d69d57ea0976544ced0714104fb8774d41d72089/lib/plugins/package/lib/zipService.js

repo: awslabs/aws-cdk


text:
Distribute S3 select over multiple paths and scan ranges

Feature or Bugfix

Feature

Detail

Distribute S3 select over multiple paths and scan ranges

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

AWS CodeBuild CI Report

CodeBuild project: GithubDistributedCodeBuildA-mOAe7SRBXVyY
Commit ID: a237185c71b5748ae2ef14fc18c07113aa17084d
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GithubDistributedCodeBuildA-mOAe7SRBXVyY
Commit ID: 013cac5c432d9698653159cf43927c1cd2f1be7b
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GithubDistributedCodeBuildA-mOAe7SRBXVyY
Commit ID: 5c3537b0971733d22ffda997758fb187ade806fd
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

authors: jaidisido malachi-constant

repo: awslabs/aws-data-wrangler


text:
can't find the access token for setting new password when I look at component logs

as mentioned I checked the logs for in /greengrass/v2/logs/aws.greengrass.labs.jupyterlab.log and I get this output:
2023-07-06T11:05:37.547Z [WARN] (Copier) aws.greengrass.labs.jupyterlab: stderr. [I 2023-07-06 07:05:37.546 ServerApp] 302 GET / (::1) 3.07ms. {scriptName=services.aws.greengrass.labs.jupyterlab.lifecycle.Run.Script, serviceName=aws.greengrass.labs.jupyterlab, currentState=RUNNING}

2023-07-06T11:05:37.569Z [WARN] (Copier) aws.greengrass.labs.jupyterlab: stderr. [I 2023-07-06 07:05:37.568 LabApp] 302 GET /lab? (::1) 4.01ms. {scriptName=services.aws.greengrass.labs.jupyterlab.lifecycle.Run.Script, serviceName=aws.greengrass.labs.jupyterlab, currentState=RUNNING}

2023-07-06T11:05:43.508Z [WARN] (Copier) aws.greengrass.labs.jupyterlab: stderr. [W 2023-07-06 07:05:43.507 ServerApp] 401 POST /login?next=%2Flab%3F (::1) 4.73ms referer=http://localhost:8888/login?next=%2Flab%3F. {scriptName=services.aws.greengrass.labs.jupyterlab.lifecycle.Run.Script, serviceName=aws.greengrass.labs.jupyterlab, currentState=RUNNING}

2023-07-06T11:32:28.265Z [WARN] (Copier) aws.greengrass.labs.jupyterlab: stderr. [W 2023-07-06 07:32:28.264 ServerApp] 401 POST /login?next=%2Flab%3F (::1) 7.77ms referer=http://localhost:8888/login?next=%2Flab%3F. {scriptName=services.aws.greengrass.labs.jupyterlab.lifecycle.Run.Script, serviceName=aws.greengrass.labs.jupyterlab, currentState=RUNNING}

I have used this link http://localhost:8888/login?next=%2Flab%3F to access jupyterlab but it doesnt work it takes me to the login page itself.
I also pasted this "%2Flab%3F" from logs in the token field and it says invalid credentials.
Please tell me know where the token is and what I should copy paste in the token field.
Thank you.

Hi,
I assume you do not have set any value for PASSWORD_HASH in your deployment configuration and hence expect Jupyter Lab to generate a one-time token to access the console.
I just found an issue (#6) where if you had set a PASSWORD_HASH and then reset it, the last password would have still been used by Jupyter Lab. You can pull the latest version of the component (1.0.1) and redeploy.
I strongly suggest to set a PASSWORD_HASH so that you do not need to access the local log file to get the access token.

authors: ahmedmuzammilAI massi-ang

repo: awslabs/aws-greengrass-labs-jupyterlab


text:
use_metrics

While troubleshooting why the custom metrics have not been created, I found out that when use_metrics is not set on the schedule level (left undefined), the value set on the global config level will be ignored and no custom metrics will be created (even if it set to true on the global config level). Wanted to check if this was the intention.
I don't believe that it's supposed to be like that since it means that:

In order to enable custom metrics, it must be configured on the schedule level (irrespective of the setting on the global config level).
The setting of use_metrics on the global config level doesn't have any effect.

PS I really like AWS Instance Scheduler!

Hi thanks for your feedback.
You are right, the global setting is not used as the schedule value if no metrics setting is used at a schedule level. For now you have to set the metrics at schedule level.
We've found the issue and it wil be included in the next maintenance release
p.s. we're glad you like the scheduler :-)

Thank you @arieleeuw

Hi ,
Can you provide reference code or documentation for creating custom metrics with schedule and service dimensions within the custom schedule resource
Thanks

Are you referencing the custom CloudFormation resource? I edited the DynamoDB table manually.

Yes, I tried to set the use_metrics within the custom resource created using the cloud formation template, but it dint work out.So, I edited the dynamodb table manually and it worked.
Thank you

Hope this helps:
{
  "AWSTemplateFormatVersion": "2010-09-09",
  "Description": "Test Schedule ",
  "Resources": {
    "TestSchedule": {
      "Type": "Custom::ServiceInstanceSchedule",
      "Properties": {
        "ServiceToken": "arn:aws:lambda:<stack region here:>:<your account number here> :function:InstanceScheduler-InstanceSchedulerMain",
        "Description": "Working hours",
        "Enforced": "True",
        "Timezone": "Europe/Amsterdam",
        "Metrics" : "True",
        "Periods": [
          {
            "Description": "Opening hours on weekdays",
            "BeginTime": "09:00",
            "EndTime": "23:59",
            "WeekDays": "Mon-Fri"
          },
          {
            "Description": "Opening hours in weekend",
            "BeginTime": "09:00",
            "EndTime": "23:59",
            "WeekDays": "Sat-Sun"
          }
        ]
      }
    }
  }
}

Thank you @arieleeuw for the template .The use_metrics 's value got updated in dynamodb table after i included Metrics: 'True' in my yaml template.  Previously ,I used Use_metrics:'True' in my template and it failed to update the stack.

Closing due to time elapsed since last correspondence. Please re-open this if you are still having an issue.

authors: YaminiMuralidharen arieleeuw maximrozin shsenior

repo: awslabs/aws-instance-scheduler


text:
docs(event-source):  fix incorrect method names in example cloudwatch logs

Signed-off-by: Ashutosh Ojha ashutoshojha5@gmail.com

Issue number: #1867
Summary
Changes

event.parse_logs_data is used in CloudWatch Logs section as an object, but it is method and should be like event.parse_logs_data()

User experience

Please share what the user experience looks like before and after this change

Checklist
If your change doesn't seem to apply, please leave them unchecked.

[ ] Meet tenets criteria
[ ] I have performed a self-review of this change
[ ] Changes have been tested
[x] Changes are documented
[x] PR title follows conventional commit semantics

Is this a breaking change?
RFC issue number:
Checklist:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Hello @ashutoshojha5 thank you very much for sending this PR. I opened an issue and linked to this PR because we need to keep track of all changes to the project.

repo: awslabs/aws-lambda-powertools-python


text:
Lambda not working and not appearing under 'Resources' in Perspective

Describe the bug
AWS Perspective deployed ok (Cloudformation completed successfully and I can login to Perspective).
However under Resources, there is no Lambda items.
Upon viewing the logs in Cloudwatch, there are 400 and 500 errors appearing as well as Alarms in Cloudwatch.
To Reproduce
Deployed the Cloudformation template to my account.
Expected behavior
Excepted the Lambda functions to operate and appear in Perspective.
Screenshots
If applicable, add screenshots to help explain your problem.
Browser (please complete the following information):

Name [e.g. chrome, firefox]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Is it only lambda functions missing or or are there other resource types not there?

Well I think there are likely other resource types missing.  The only ones listed under Resources in the Perspective app are:
APIGateway(19)
ECS(1)
RDS(1)
VPC(3) - which are VPC Endpoints.

Ah, looks like the only stuff that's been brought in are from the decribe* calls, there's something going on with Config, I'll bet. Are you just trying to import the Perspective account or is it a different account?

Yes just the Perspective account for now.

Cool. Can you go to the Config page in the console and follow these steps:
https://docs.aws.amazon.com/solutions/latest/aws-perspective/automated-deployment.html

Ok, thanks @svozza , it looks like you're right.  I've done Config steps and this time Config is looking better as the Dashboard is showing heaps of resources.
I haven't redeployed the CloudFormation stack yet and went into Perspective and there are some more resources showing up but still no Lambda.  Do I need to essentially redeploy the Stack?

Cool. That's good to hear. Let the discovery process run again (it runs every fifteen minutes, so the next run will be at 12.15) and that should take care of getting all the rest of the resources.

Did this solve your issue in the end, @adambjmurdoch ?

I'm going to close this for now, if the issue is not resolved, please feel free to reopen.

authors: adambjmurdoch svozza

repo: awslabs/aws-perspective


text:
iOS Integration Issue

I got this error while running this on swift
Domain=com.amazonaws.AWSLexErrorDomain Code=0 "null" UserInfo={NSLocalizedFailureReason=AccessDeniedException:http://internal.amazon.com/coral/com.amazon.coral.service/, NSLocalizedDescription=null}
I went to modify the permission in AWSServiceRoleForLexBots policy but can't do it
This is the policy summary
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"polly:SynthesizeSpeech"
],
"Resource": [
"*"
]
}
]
}
How can I modify it for this to work ??

Hi @girishnair12345,
What's the Sample app you are trying to run? Lex or Polly?

Lex

You need to have a policy on your cognito role to allow post content operations on Lex. The policy would look something like this:
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "lex:PostContent",
                "lex:PostText"
            ],
            "Effect": "Allow",
            "Resource": [
                "arn:aws:lex:us-east-1:123456789011:bot:OrderFlowers:*",
                "arn:aws:lex:us-east-1:123456789011:bot:BookTrip:*"
            ]
        }
    ]
}

Can you explain how to do that, and wouldn't it be great if you close the issue once the person raising it says its resolved ??

I can't find this setting, How exactly can I enable this ??
Why does lex has to be clouded by so many permissions, it's so easy to use api.ai by google.

@girishnair12345  I'll help you out.  :)
I'm not sure how you setup your app.   But if you are using the sample.   Then I can assume that you are using Cognito Federated Identities.      You go to manage your Federated Identities, by Editing Identity Pool.    You will see Unauthenticated Role,  you can select one or create a new role.    Once you have a role for Unauthenticated Role.   You will have to go to IAM page.    On the IAM page, you'll select the role, you are using for Unauthenticated Role.   On the Summary page for the Role, you will:
Click on Add inline policy, and fill in this statement below:
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "lex:PostContent",
                "lex:PostText"
            ],
            "Resource": [
                "*"
            ]
        },
        {
            "Effect": "Allow",
            "Action": [
                "polly:SynthesizeSpeech"
            ],
            "Resource": [
                "*"
            ]
        }
    ]
}

Thanks for your reply but I am using api.ai now

authors: girishnair12345 kvasukib rohandubal sweeneyapps

repo: awslabs/aws-sdk-ios-samples

license_source: bigquery


text:
Fixed links in README

Fixed the links to modules 3 and 4 in the readme.

Closed accidentally

authors: gthuang mikedeck

repo: awslabs/aws-serverless-workshops


text:
docs: update migration data procedures

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Summary
(describe what this merge request does)
Implementation highlights
(describe how the merge request does for feature changes, share the RFC link if it has)
Test checklist

[ ] add new test cases
[ ] all code changes are covered by unit tests
[ ] end-to-end tests

[ ] deploy web console with CloudFront + S3 + API gateway
[ ] deploy web console within VPC
[ ] deploy ingestion server

[ ] with MSK sink
[ ] with KDS sink
[ ] with S3 sink

[ ] deploy data processing
[ ] deploy data modeling

[ ] new Redshift Serverless
[ ] provisioned Redshift
[ ] Athena

[ ] deploy with reporting
[ ] streaming ingestion

[ ] with Redshift Serverless
[ ] with provisioned Redshift

Is it a breaking change

[ ] add parameters without default value in stack
[ ] introduce new service permission in stack
[ ] introduce new top level stack module

Miscellaneous

[ ] introduce new symbol link source file(s) to be shared among infra code, web console frontend, and web console backend

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.40
< 80

Duplicated lines density
:white_check_mark: OK
5.60
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
2
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/26/2024, 08:38:37 (UTC+0)

SonarQube Code Analytics
Quality Gate passed

Additional information
The following metrics might not affect the Quality Gate status but improving them will improve your project code quality.
Issues
 0 Bugs
 0 Vulnerabilities
 0 Code Smells
Coverage and Duplications
No data Coverage
No data Duplication

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.50
< 80

Duplicated lines density
:white_check_mark: OK
5.60
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
2
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/27/2024, 01:55:35 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.40
< 80

Duplicated lines density
:white_check_mark: OK
5.60
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
2
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/27/2024, 03:35:12 (UTC+0)

repo: awslabs/clickstream-analytics-on-aws


text:
got a ValueError when running the script

INFO:root:Finish to download EC2 pricelist file and upload it to S3 bucket: ec2pricelist.csv
INFO:root:Connected to the database
INFO:root:Importing the CloudWatch files to Redshift table
INFO:botocore.vendored.requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 169.254.169.254
INFO:botocore.vendored.requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 169.254.169.254
INFO:root:Finish to import the CloudWatch files to the Redshift table: cwdatapvbnrmgw
INFO:root:Importing the EC2 pricelist to Redshift
INFO:root:Generate Redshift table structure
INFO:root:Importing the pricelist files to Redshift table: pricelistcrxnwpqt
INFO:botocore.vendored.requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 169.254.169.254
INFO:botocore.vendored.requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 169.254.169.254
INFO:root:Finish to import the EC2 pricelist to Redshift table: pricelistcrxnwpqt
INFO:root:Analyzing the instances need to be resized
Complete percent: 1.0%Traceback (most recent call last):
  File "/tmp/run-rightsizing-redshift.py", line 434, in <module>
    ls_temp_table = right_sizing(conn, ls_pricelist_tabname, ls_cw_tabname)
  File "/tmp/run-rightsizing-redshift.py", line 376, in right_sizing
    determine_right_type(db_conn, ls_resizetype_sql, ls_temp_table, ls_instanceid, ln_iops_usage, ln_ssd_total_size, ln_cpu_nbr, ln_network_level_usage, ln_rate, ln_mem)
  File "/tmp/run-rightsizing-redshift.py", line 251, in determine_right_type
    ln_min_ssd_size = int(ls_min_storage1[ls_min_storage1.find('x')+1:])
ValueError: invalid literal for int() with base 10: '0.475 NVMe'

Can you find the offending line in the file with the format YYYY-MM-DD-before336hour-with60min.csv.gz and post it here?

how can i do that? in the file every line seems ok

I'm getting the exact same error. I've searched through YYYY-MM-DD-before336hour-with60min.csv and I can't find it there either
Complete percent: 19.0%Traceback (most recent call last):
File "/tmp/run-rightsizing-redshift.py", line 434, in
ls_temp_table = right_sizing(conn, ls_pricelist_tabname, ls_cw_tabname)
File "/tmp/run-rightsizing-redshift.py", line 376, in right_sizing
determine_right_type(db_conn, ls_resizetype_sql, ls_temp_table, ls_instanceid, ln_iops_usage, ln_ssd_total_size, ln_cpu_nbr, ln_network_level_usage, ln_rate, ln_mem)
File "/tmp/run-rightsizing-redshift.py", line 251, in determine_right_type
ln_min_ssd_size = int(ls_min_storage1[ls_min_storage1.find('x')+1:])
ValueError: invalid literal for int() with base 10: '0.475 NVMe'

Patches pushed that we believe fixes this issue -- checking SSD storage type is NVMe

authors: eredi93 milbrya ryanaverill stevemorad


text:
fix: use viewport from provider

Overview
Fixes https://github.com/awslabs/iot-app-kit/issues/143

use viewport from provider instead of props, this was overriding actual viewport when interacting with chart
use latest @synchro-charts/core with fix for live mode (do not emit dateRangeChange if not interacting with chart)

Legal
This project is available under the Apache 2.0 License.

We still need the viewport, just don’t pass it directly to the synchro-charts components. Instead they are passed down from the provider.

repo: awslabs/iot-app-kit


text:
fix(kernel): Return object literals as references

Use the javascript Proxy class to coalesce object literals to an
interface type, allowing them to be returned by reference instead of by
value.
Introduces a test in the jsii-kernel to demonstrate the feature works
as intended.
Fixes #248
Fixes awslabs/aws-cdk#774

Does this apply to all objects? What about objects we're passing "as data" in data-typed interfaces?

@rix0rrr I don't reckon there is any such thing as as data per se. Data-types are still returned as object references as far as I know.

repo: awslabs/jsii


text:
Folder Dissapear after Deleting all files

Mountpoint for Amazon S3 version
mount-s3 1.3.1
AWS Region
eu-central-1
Describe the running environment
EC2 Ubuntu 22.04
Mountpoint options
/usr/bin/mount-s3 mybucket /mymount --prefix ftp/ --allow-other --log-directory /var/log/mounts3-log --file-mode 0777 --dir-mode 0777 --allow-delete --auto-unmount --region eu-central-1

What happened?
I mount the S3 for the chrooted FTP user home directory. After deleting some files inside, the folder is gone, and I cannot log in again due to the missing home directory. How can I prevent this?
Relevant log output
2023-12-21T02:01:33.616379Z  WARN lookup{req=50092 ino=1 name="myfolder"}: mountpoint_s3::fuse: lookup failed: inode error: file does not exist

Hey @revanhernandy. As @mschfh wrote, the objects are being grouped based on path. This is also described in our semantics documentation for reference: https://github.com/awslabs/mountpoint-s3/blob/83fa7c654623cba34b44f99c3b8930b693ebd0b1/doc/SEMANTICS.md#directories
One way to resolve your issue would be to create either an empty file for persisting a directory (similar to .gitkeep files for Git), or to create a directory marker. We don't recommended using directory markers generally since they can have adverse affects with larger workloads, but it may work best for your use case.
A directory marker is an empty object with the key matching the prefix of objects that would be contained within. For some directory "dir1", you could create an empty object dir1/ which will be interpreted by many file-oriented connectors/views as a directory. For example, the S3 Console will create this type of object when creating a directory. Note that directory markers cannot be removed by Mountpoint today, and you would need to use another S3 client to remove them later.

Please let us know if this resolves your issue or if you need any further help with it.

Hi @dannycjones thank you for the response.  Got it and makes sense.
Currently, we have an Azure blobfuse filesystem and it can be handled by a temporary path but we need to migrate into S3 stuff 😄 it would be very perfect if Mount S3 could do similar.
But, the first workaround is ideal in this case with making a persistence file with a dot(.) would be helpful in case, vsftpd by default would hide the files and directories starting with dot(.)

Currently, we have an Azure blobfuse filesystem and it can be handled by a temporary path but we need to migrate into S3 stuff 😄 it would be very perfect if Mount S3 could do similar.

Sorry @revanhernandy, I didn't understand what the ask is. What do you mean by a temporary path?

We plan to add the scenario in this issue to a new FAQ/troubleshooting document we're creating, tracking this scenario here: #722.

We'll update the troubleshooting documentation to mention this case, but as discussed above, this is the expected behavior. Creating a hidden .keep file is a good workaround. Thanks for the report!

authors: dannycjones jamesbornholt revanhernandy


text:
Feature request: Agent overlap analysis script for Python

Use case
multi-agent-orchestrator framework should have an agent overlap analysis script for python version.
Solution/User Experience
Implement python version of typescript agent overlap analyzer
Alternative solutions
No response

Working on it

repo: awslabs/multi-agent-orchestrator


text:
Add "Active" config file field for lumped and wave ports

Resolves #171.
In addition, this PR changes field visualization on internal boundaries to always chose the field on the vacuum side (previously, sometimes used vacuum and sometimes used side with lower speed of light).

Only comment would be to add the documentation for Active in the markdown, but the other branch is merging into this with those changes so probably ok.

Only comment would be to add the documentation for Active in the markdown, but the other branch is merging into this with those changes so probably ok.

Good catch, missed this when rebasing the PRs to reverse their order.

authors: hughcars sebastiangrimberg

repo: awslabs/palace


text:
修改函数代码不起作用，日志没什么用

日志永远只有一种错误
Unable to import module 'index': Error
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
完全看不出来是哪一行代码错误，
当我访问图片时，好像不会立刻生成日志
我在代码中加了很多console.log来打印，日志中没有出现我打印的提示

Hi @zhangjianlai522, can you share more detail about your change?

We are closing this issue, but please feel free to open the issue again if you any other support.

repo: awslabs/serverless-image-handler


text:
hostPrefix property in endpoint trait should validate prefix ends in dot (.)

The endpoint trait is not required to end in a dot. Is this by design? In the Smithy docs for hostLabel it has this example:
@endpoint(hostPrefix: "{foo}.data")

But for an endpoint example.com and foo = "foo" it would become foo.dataexample.com, unless clients or code generators are validating against this. I think it's dangerous to allow this because it changes the configured host and not limited to prefixing as the trait suggests. If you agree, I think it also makes sense to call out this validation in the documentation, too.

I think it's dangerous to allow this because it changes the configured host

The whole point of this trait is to allow changing the host, so I don't see why we would forbid this behavior. (We couldn't even if we wanted to since 3/8 of the AWS services that use this don't end it in a period.) Still, we should probably attach an info or warning validation to point out the issue for non-aws services that could potentially be changing their second level domain.

The whole point of this trait is to allow changing the host

I would think that a trait called "hostPrefix" would only prefix the host, not change to an entirely different TLD if misconfigured.. What AWS services have prefixes that don't end in a period?

Well you'd never be able to change the TLD unless the SDK let you pass in an invalid endpoint to start. You can change the 2LD. That's probably a really bad idea if there's a host label in there, which is why the validation I added targets that.

What AWS services have prefixes that don't end in a period?

chime, sfn, and servicediscovery

Thanks

authors: JordonPhillips mullermp

repo: awslabs/smithy


text:
Fix grammar for IDL v2

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

Line 20: service_statement should probably be ServiceStatement
Line 255: operation_statement should probably be OperationStatement
Line 351: resource_statement should probably be ResourceStatement

Good question -- those links refer to anchors that still exist and not grammar rules, so we're ok there.


text:
feat: update message approval args consistent

AXE-6097

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

Project coverage is 98.04%. Comparing base (9309b4a) to head (eafdd9d).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #35   +/-   ##
=======================================
  Coverage   98.04%   98.04%
=======================================
  Files          24       24
  Lines        1790     1790
=======================================
  Hits         1755     1755
  Misses         35       35

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

authors: ahramy codecov-commenter

repo: axelarnetwork/axelar-cgp-soroban


text:
Unable to run tests of snark-verifier

I am trying to run the tests of snark-verifer folder.
I added a file in snark-verifier/configs called verify_circuit.config and added this configuration
{"strategy":"Simple","degree":21,"num_advice":4,"num_lookup_advice":1,"num_fixed":1,"lookup_bits":20,"limb_bits":88,"num_limbs":3}

I ran
cargo run --example recursion --release

to run the recursion example.
The error i am receiving is
read params from ./params/kzg_bn254_5.srs
thread 'main' panicked at snark-verifier/examples/recursion.rs:791:82:
called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[1]    37750 abort      cargo run --example recursion --release

The error is here, you need to rename your config file.

Thank you @yi-sun .
Also another question i had was the example in snark-verifier-sdk is using https://github.com/axiom-crypto/halo2/blob/a4140d7129759c995e29ed203350a90a3c57d896/halo2_proofs/src/plonk/verifier.rs#L24 as its proof verification
while the snark-verifier  one uses https://github.com/axiom-crypto/snark-verifier/blob/343c89e416ff7320a0bca30cc24f2a873c56ce11/snark-verifier/src/verifier/plonk.rs#L61. Why is that?

The one in snark-verifier does an additional check that the KZG accumulator in the proof passes a pairing check.
In the snark-verifier-sdk examples we use the halo2 verifier for debugging purposes because it is easier to invoke.
The verifier circuits and EVM verifier contract all use the verify in snark-verifier's plonk.rs.

Closing because the original issue was resolved.

authors: guha-rahul jonathanpwang yi-sun

repo: axiom-crypto/snark-verifier


text:
tons of new stuff from cf-xarray!

updated docs and tests
can understand axes and coords now with mapping from cf-xarray
more utilities

Codecov Report

Merging #20 (6197165) into main (0845a12) will decrease coverage by 1.48%.
The diff coverage is 90.53%.

:exclamation: Current head 6197165 differs from pull request most recent head cc74b0c. Consider uploading reports for the commit cc74b0c to get more accurate results

@@            Coverage Diff             @@
##             main      #20      +/-   ##
==========================================
- Coverage   98.54%   97.06%   -1.49%
==========================================
  Files          13       14       +1
  Lines         619      783     +164
==========================================
+ Hits          610      760     +150
- Misses          9       23      +14

Flag
Coverage Δ

unittests
97.06% <90.53%> (-1.49%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

cf_pandas/utils.py
97.61% <ø> (+4.76%)
:arrow_up:

cf_pandas/accessor.py
87.40% <86.32%> (-12.60%)
:arrow_down:

cf_pandas/criteria.py
100.00% <100.00%> (ø)

cf_pandas/vocab.py
98.00% <100.00%> (+0.04%)
:arrow_up:

tests/test_accessor.py
100.00% <100.00%> (ø)

tests/test_utils.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

authors: codecov-commenter kthyng

repo: axiom-data-science/cf-pandas

license: MIT


text:
Personal mental notes

a delicate balance, trade-offs
-beyond  lip service
link to visual design principles
Include emphasis on Accessibility
EXPOSURE to an interface before feedback gathering
Deferring changes vs. Denying
Cognitive, mechanical burden
UX Research Landscape
how your methodology can fall on a gradient
context matters
go back to goals of why we are testing: diagnostic, realism
-Operationalizing measures Eg. Effectiveness can be measured as a % of people who completed assigned tasks across multiple usability tests, or Likert scale ratings from a survey

On the front page add the google doc as the pivot around which the document is built,
In challenges talk about how data vis prototyping is complex because he content itself has so many moving parts-- a legend, axis etc. all of which have to be styled. This is different from websites serving images.
In planning the test add the image that explains the current landscape

stand on the shoulder of giants- catchy title

repo: axisgroup/evaluation-toolkit


text:
Look into Single Ease Questionnaire

https://measuringu.com/seq10/

NASA tlx: https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/20000021488.pdf


text:
Error on Deno Deploy using serveFileWithTs

First of all, thank you so much for this great library! I've implemented it in my Simple Deno Website Boilerplate, but it's failing on Deno Deploy:
Uncaught SyntaxError: The requested module 'https://deno.land/std@0.144.0/http/file_server.ts' does not provide an export named 'ServeDirOptions'
    at https://deno.land/x/ts_serve@v1.1.0/mod.ts:1:20

It's quite weird because I can see the export does exist in std and has for a while, maybe it's a Deno Deploy runtime issue (I've asked in the Discord server and also created an issue at https://github.com/denoland/deploy_feedback/issues/252), but wanted to log here in case someone else sees it.

I was able to fix it for myself by implementing a simpler serving of the files but this will likely affect others trying to use this library.

Thanks for letting me know about this issue!
I have seen this error before and remember fixing it. Perhaps if I release a new version everything should be fine. wait a moment please.

This issue has been fixed in https://github.com/ayame113/ts-serve/pull/7/files#diff-e8c3622ccfbed67f4b3058cd4417bf41d066236f49c6f3e63b7c243b584c6734R1-R6 and I just released a new version (v1.2.0) with that fix so I think this can be closed.


text:
'Microsoft.PowerShell.Archive' could not be loaded

Version confirmation

[X] Confirm

Following prerequisites

[X] Confirm

Neovim version
NVIM v0.9.1
Operating system/version
Windows 10 Pro 22H2
Terminal name/version
Windows Terminal 1.17.11461.0
$TERM environment variable
No response
Branch info
main (Default/Latest)
Fetch Preferences
SSH (use_ssh = true)
How to reproduce the issue
Use :MasonInstall clangd module not loaded，but it exist.

Expected behavior
Use :MasonInstall clangd module not loaded，but it exist.

Actual behavior
No response
Additional information
No response

Can you provide the full log content here?

I'm sorry to have cleaned up my environment due to an attempted repair

Okay, I'll go back and try it tonight.

After I cleaned up my environment and replaced the installer choco with scoop, everything became OK, not sure why.

@taynpg A common cause of this issue is only the stub (or receipt) of this module exists on ur file system. Many factors, e.g., the backup mechanism of MS OneDrive could lead to this issue. u can think of this as a broken symlink.
When u change ur package manager, the installer probably recognizes this issue and restores the original copy for u. However, Mason's processing mechanism is rather simple and doesn't check for this.

authors: Jint-lzxy ayamir taynpg

repo: ayamir/nvimdots


text:
Consider organization

As we evolve our projects, we should carefully consider how we'd like to architecturally extend the project.
Summary

Core API is deployed to App Engine (project: ayr-core-service)
Core Backoffice is deployed to App Engine (project: ayr-core-service)
pgadmin is deployed to Compute Engine (a default VM, with Docker Container, on a separate project)
Workspace Agent is deployed to Cloud Run (uses Pub/Sub and Cloud Scheduler, separate project)
Onboarding is deployed to App Engine (on a separate project)
User API is deployed to App Engine (on a separate project)
ALSO Pricelist Sync is deployed to Cloud Run (uses Pub/Sub and Cloud Scheduler, on a separate project)
EPP Outline server is deployed to Compute Engine  (on a separate project)

Things to consider

What is a good organization for our kind of organization? We should read what Google thinks. We should also think about the maximum projects we can have on each billing account.
Logging agents currently needs to be deployed to each project.

👆 Current setup
@bjerkio/thebranches has access to this file here:
https://drive.google.com/file/d/1KSaDZuKfCen0gAH4elIBYou9a8bW2Qzu/view?usp=sharing

A year has passed since this was last updated, and the more time that passe,s the more I feel we should refactor things.
We have grown to use a Kubernetes cluster now as well.

– Core API should be move to Kubernetes

Core Backoffice should be move to Kubernetes
pgadmin should be killed
Workspace Agent is being modernized
Onboarding should be moved to Kubernetes (since it's a Next.js, actually using the backend)
User API should be killed
ALSO Pricelist Sync should be killed
EPP Outline server should be killed (use a fixed internet with normal VPN?)

Just killed Kubernetes temporarily. Seems dumb to spend money on it when we're not really using it.

I'm closing this as done and successful now :)

repo: ayrorg/infra


text:
Adding nscd volume and environment variable for version set id.

Adding a way to setup volume for nscd which is required on Kubernetes.
Adding a way to set environment variables in pod spec builder.

Pull Request Test Coverage Report for Build 5741

9 of 9 (100.0%)  changed or added relevant lines in 1 file are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.003%) to 43.104%

Files with Coverage Reduction
New Missed Lines
%

azkaban-exec-server/src/main/java/azkaban/execapp/JobRunner.java
4
76.36%

Totals

Change from base Build 5740:
0.003%

Covered Lines:
15649

Relevant Lines:
36305

💛  - Coveralls

authors: coveralls jakhani

repo: azkaban/azkaban


text:
Adding ssl policy block to application gateway

We used and tested the module internally.
CR#1
To meet our security and compliance standards, we need ssl policy block to define ssl policies for application gateway, hence added the same, following the dynamic and flexible approach of this module.
CR#2
We noticed that one of the key of variable http_listeners is defined differently inside module, which is causing an issue.
The attribute is named ssl_certificate_name in variables.tf and certificate_name inside the module (application gateway with https configuration)
Hence, we have replaced certificate_name with ssl_certificate_name in the module.
Please review the changes and merge the same as soon as possible. As we want to make use of this module internally.
Awaiting your response.

#34

I have started to work on this feature. Documentation and unit tests need to be added. I will add it for version 2.1.0
Thanks for the contribution
#34

Thank you for considering, looking forward to close this PR!

authors: AnkithaBH gareda


text:
rover 'state rm': state file not found

Hello,
I'm facing an issue when trying to make a state rm in rover command:
rover -lz /tf/caf/.solution/caf/caf_solution \
-var-folder /tf/caf/my_var_folder \
-a 'state rm' \
-p ${PLAN_FILE_NAME} \
-level level4 \
-env ${LZ_PREFIX} \
-tfstate ${TFSTATE_FILE} \
-tfstate_subscription_id ${TFSTATE_SUB_ID} \
-parallelism 30 \
-target_subscription ${SUB_NAME} \
-id "module.solution.module.network_something[\"blabal\"].azurecaf_name.networksomething"`

And the result is a state file was found! error message::
@calling verify_azure_session
Checking existing Azure session
@calling process_target_subscription
Set subscription to -target_subscription SXXXXX01
caf_command landingzone
target_subscription_id 8XXXXXe
TF_VAR_tfstate_subscription_id 8XXXXXe
Resources from this landing zone are going to be deployed in the following subscription:
{
  "environmentName": "AzureCloud",
  "homeTenantId": "axxxxxx",
  "id": "xxxxxf",
  "isDefault": true,
  "managedByTenants": [],
  "name": "XXXXXX",
  "state": "Enabled",
  "tenantId": "xxxxxx",
  "user": {
    "name": "hey@you.onmicrosoft.com",
    "type": "user"
  }
}
debug: 6XXXXXXX
Tfstates subscription set to XXXX (XXXXXXXXXXX)

mode                          : 'landingzone'
terraform command output file : ''
terraform plan output file    : 'foobar_tfplan'
directory cache               : '/home/vscode/.terraform.cache/foobar_launchpad/rover_jobs/20221124112354655979305'
tf_action                     : 'state list'
command and parameters        : '-var-file=/tf/caf/environements/vxxxxx/landingzone.tfvars -var-file=/tf/caf/environements/xxxx/rgs.tfvars -var-file=/tf/caf/environements/xxxxx/resource.tfvars -parallelism 30'

level (current)               : 'level4'
environment                   : 'foobar_launchpad'
workspace                     : 'tfstate'
tfstate                       : 'foobar.tfstate'
tfstate subscription id       : 'XXXXX'
target subscription           : 'XXXXX'
CI/CD enabled                 : 'false'
Symphony Yaml file path       : ''
Run all tasks                 : 'true'
TF_IN_AUTOMATION              : 'true'

@calling process_actions
@calling verify_parameters
landingzone                   : '/tf/caf/landingzone'
@calling_deploy
@calling get_storage_id
@calling_get_logged_user_object_id
 - AZURE_ENVIRONMENT: AzureCloud
 - ARM_ENVIRONMENT: public
Initalizing az cloud variables
 - logged in user objectId: xxxxxx (hey@you.onmicrosoft.com)
Initializing state with user: hey@you.onmicrosoft.com

launchpad already installed

@calling deploy_from_remote_state
Connecting to the launchpad
@calling login_as_launchpad

Getting launchpad coordinates from subscription: 8xxxx9e
 - keyvault_name: vxxxxx-level4
 - tenant_id : axxxxxx8
 - storage_account_name (current): xxx4
 - storage_account_name (lower): xxx3
 - resource_group (current): xxxxlaunchpad-level4
 - resource_group (lower): xxxlaunchpad-level3
@calling deploy_landingzone
Deploying '/tf/caf/landingzone'
Terraform version 0.15 or greater
Upgrading modules...
Downloading aztfmod/caf/azurerm 5.4.8 for dynamic_keyvault_secrets...
- dynamic_keyvault_secrets in /home/vscode/.terraform.cache/foobar_launchpad/rover_jobs/20221112345679305/modules/dynamic_keyvault_secrets/modules/security/dynamic_keyvault_secrets
- dynamic_keyvault_secrets.secret in /home/vscode/.terraform.cache/foobar_launchpad/rover_jobs/20221112345679305/modules/dynamic_keyvault_secrets/modules/security/dynamic_keyvault_secrets/secret

Initializing the backend...

Successfully configured the backend "azurerm"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- terraform.io/builtin/terraform is built in to Terraform
- Finding hashicorp/azurerm versions matching "~> 2.81.0"...
- Finding latest version of hashicorp/local...
[...]
- Using hashicorp/tls v2.2.0 from the shared cache directory
- Using aztfmod/azurecaf v1.2.22 from the shared cache directory

Terraform has been successfully initialized!
Terraform init return code 0
calling other
@calling other
running terraform state rm -state=/home/vscode/.terraform.cache/foobar_launchpad/rover_jobs/20221112345679305/tfstates/levelX/tfstate/'foobar.tfstate module.solution.module.network_something[\"blabal\"].azurecaf_name.networksomething"
Terraform state rm return code: 0
Terraform returned errors:
No state file was found!

State management commands require a state file. Run this command
in a directory where Terraform has been run or use the -state flag
to point the command to a specific state location.
Error on or near line 555: Error running terraform state rm; exiting with status 2003

@calling clean_up_variables
cleanup variables
clean_up backend_files

But a state show is working fine:
rover -lz /tf/caf/.solution/caf/caf_solution \
-var-folder /tf/caf/my_var_folder \
-a 'state show' \
-p ${PLAN_FILE_NAME} \
-level level4 \
-env ${LZ_PREFIX} \
-tfstate ${TFSTATE_FILE} \
-tfstate_subscription_id ${TFSTATE_SUB_ID} \
-parallelism 30 \
-target_subscription ${SUB_NAME} \
-id "module.solution.module.network_something[\"blabal\"].azurecaf_name.networksomething"`

And the result is:
Terraform has been successfully initialized!
Terraform init return code 0
calling other
@calling other
running terraform state list -state=/home/vscode/.terraform.cache/foobar_launchapd/rover_jobs/2022114158234788/tfstates/level4/tfstate/foobar.tfstate module.solution.module.network_something["blabal"].azurecaf_name.networksomething

module.solution.module.network_something[\"blabal\"].azurecaf_name.networksomething"`
Terraform state list return code: 0

@calling clean_up_variables
cleanup variables
clean_up backend_files

real    0m39.992s
user    0m20.880s
sys     0m8.836s

My questions are:

Is the state rm a rover's bug?
Why state list or state show are working?
When is downloaded the tfsate for state show/list?

My environment

aztfmod/rover:1.0.7-2109.2410

Hi there o/
I forget to precise that i've made little enhancement on rover's scripts to be able to manage the id resource:
rover/rover.sh
[...]
        -a|--action)
            export tf_action=$(parameter_value --action "${2}")
            shift 2
            ;;
        -id)
            export tf_id="${2}"
            shift 2
[...]

rover/tfstate_azurerm.sh
function other {
    echo "@calling other"
    echo "running terraform ${tf_action} -state="${TF_DATA_DIR}/tfstates/${TF_VAR_level}/${TF_VAR_workspace}/${TF_VAR_tf_name}" ${tf_id}"
    download_tfstate
    rm -f $STDERR_FILE

    terraform \
        ${tf_action} \
        -state="${TF_DATA_DIR}/tfstates/${TF_VAR_level}/${TF_VAR_workspace}/${TF_VAR_tf_name}" \
        ${tf_id} 2>$STDERR_FILE | tee ${tf_output_file}
        #${tf_command} 2>$STDERR_FILE | tee ${tf_output_file}

    RETURN_CODE=${PIPESTATUS[0]} && echo "Terraform ${tf_action} return code: ${RETURN_CODE}"

 #   upload_tfstate
[...]

You could notice that I add upload_tfstate and download_tfstate to workaround the no state file. I comment it for now to avoid effects for other commands.
Thanks!

Here is a proposal for a clean 'patch' for tfstate_azurerm.sh
function other {
    echo "@calling other"
    #echo "running terraform ${tf_action} -state="${TF_DATA_DIR}/tfstates/${TF_VAR_level}/${TF_VAR_workspace}/${TF_VAR_tf_name}"  ${tf_command}"

    rm -f $STDERR_FILE

    [[ "${tf_action}" == *"rm"* ]] && \
      (echo "tf_action *SHOULD* containing rm: "${tf_action};
          download_tfstate)

    [[ "${tf_action}" == *"state"* ]] && \
      (echo "tf_action *SHOULD* containing state: "${tf_action};
      echo "tf_id: "${tf_id};
      echo "running terraform ${tf_action} -state="${TF_DATA_DIR}/tfstates/${TF_VAR_level}/${TF_VAR_workspace}/${TF_VAR_tf_name}"  ${tf_id}";
      terraform \
        ${tf_action} \
        -state="${TF_DATA_DIR}/tfstates/${TF_VAR_level}/${TF_VAR_workspace}/${TF_VAR_tf_name}" \
        ${tf_id} \
        2>$STDERR_FILE | tee ${tf_output_file};
        echo ${PIPESTATUS[0]} > /tmp/tf_pipe_code);

    [[ "${tf_action}" != *"state"* ]] && \
      (echo "tf_action *SHOULD NOT* containing state: "${tf_action};
      echo "running terraform ${tf_action} -state="${TF_DATA_DIR}/tfstates/${TF_VAR_level}/${TF_VAR_workspace}/${TF_VAR_tf_name}"  ${tf_command}";
      terraform \
        ${tf_action} \
        -state="${TF_DATA_DIR}/tfstates/${TF_VAR_level}/${TF_VAR_workspace}/${TF_VAR_tf_name}" \
        ${tf_command} \
        2>$STDERR_FILE | tee ${tf_output_file};
        echo ${PIPESTATUS[0]} > /tmp/tf_pipe_code);

#      terraform \
#        ${tf_action} \
#        -state="${TF_DATA_DIR}/tfstates/${TF_VAR_level}/${TF_VAR_workspace}/${TF_VAR_tf_name}" \
#        ${tf_id} \
#       2>$STDERR_FILE | tee ${tf_output_file}
    #RETURN_CODE=${PIPESTATUS[0]} && echo "Terraform ${tf_action} return code: ${RETURN_CODE}"

    TF_PIPE_CODE=$(cat /tmp/tf_pipe_code);
    rm -f /tmp/tf_pipe_code;
    RETURN_CODE=${TF_PIPE_CODE} && echo "Terraform ${tf_action} return code: ${RETURN_CODE}"

    if [ -s $STDERR_FILE ]; then
        if [ ${tf_output_file+x} ]; then cat $STDERR_FILE >>${tf_output_file}; fi
        echo "Terraform returned errors:"
        cat $STDERR_FILE
        RETURN_CODE=2003
    fi

    if [ $RETURN_CODE != 0 ]; then
        error ${LINENO} "Error running terraform ${tf_action}" $RETURN_CODE
    else
        [[ "${tf_action}" == *"rm"* ]] && upload_tfstate
    fi
    echo ""
}

@gesnaud When I try your changes above, I get "At least one address is required." It doesn't look like the address is being included in the command call:
running terraform state rm -state=/home/vscode/.terraform.cache/sepazcafenv/rover_jobs/20230126154929728220187/tfstates/level3/tfstate/lz_common_subscriptions.tfstate
Usage: terraform [global options] state rm [options] ADDRESS...
Did I miss something?

Hi Jason!
In your rover command line, you specified the resources address right?
Thx,
Greg
----- Mail original -----
De: "Jason Dossett" @.>
À: "aztfmod/rover" @.>
Cc: "Gregory ESNAUD" @.>, "Mention" @.>
Envoyé: Jeudi 26 Janvier 2023 16:53:42
Objet: Re: [aztfmod/rover] rover 'state rm': state file not found (Issue #292)
@gesnaud When I try your changes above, I get "At least one address is required." It doesn't look like the address is being included in the command call:
running terraform state rm -state=/home/vscode/.terraform.cache/sepazcafenv/rover_jobs/20230126154929728220187/tfstates/level3/tfstate/lz_common_subscriptions.tfstate
Usage: terraform [global options] state rm [options] ADDRESS...
Did I miss something?
—
Reply to this email directly, view it on GitHub , or unsubscribe .
You are receiving this because you were mentioned. Message ID: <aztfmod/rover/issues/292/1405218660 @ github . com>

I did not but I quickly figured out that’s what I was doing wrong which is why I deleted the question. :)
Thanks for the patch, it was very helpful!
On Jan 27, 2023, at 4:48 AM, Gregory ESNAUD @.***> wrote:

Hi Jason!
In your rover command line, you specified the resources address right?
Thx,
Greg
----- Mail original -----
De: "Jason Dossett" @.>
À: "aztfmod/rover" @.>
Cc: "Gregory ESNAUD" @.>, "Mention" @.>
Envoyé: Jeudi 26 Janvier 2023 16:53:42
Objet: Re: [aztfmod/rover] rover 'state rm': state file not found (Issue #292)
@gesnaud When I try your changes above, I get "At least one address is required." It doesn't look like the address is being included in the command call:
running terraform state rm -state=/home/vscode/.terraform.cache/sepazcafenv/rover_jobs/20230126154929728220187/tfstates/level3/tfstate/lz_common_subscriptions.tfstate
Usage: terraform [global options] state rm [options] ADDRESS...
Did I miss something?
—
Reply to this email directly, view it on GitHub , or unsubscribe .
You are receiving this because you were mentioned. Message ID: <aztfmod/rover/issues/292/1405218660 @ github . com>
—
Reply to this email directly, view it on GitHubhttps://github.com/aztfmod/rover/issues/292#issuecomment-1406264380, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AU2J37YHQC6AWCNXK76NQFTWUOKVTANCNFSM6AAAAAASKN36BE.
You are receiving this because you commented.Message ID: @.***>

Great :)
Have a nice day!
----- Mail original -----
De: "Jason Dossett" @.>
À: "aztfmod/rover" @.>
Cc: "Gregory ESNAUD" @.>, "Mention" @.>
Envoyé: Vendredi 27 Janvier 2023 11:51:54
Objet: Re: [aztfmod/rover] rover 'state rm': state file not found (Issue #292)
I did not but I quickly figured out that’s what I was doing wrong which is why I deleted the question. :)
Thanks for the patch, it was very helpful!
On Jan 27, 2023, at 4:48 AM, Gregory ESNAUD @.***> wrote:
Hi Jason!
In your rover command line, you specified the resources address right?
Thx,
Greg
----- Mail original -----
De: "Jason Dossett" @.>
À: "aztfmod/rover" @.>
Cc: "Gregory ESNAUD" @.>, "Mention" @.>
Envoyé: Jeudi 26 Janvier 2023 16:53:42
Objet: Re: [aztfmod/rover] rover 'state rm': state file not found (Issue #292)
@gesnaud When I try your changes above, I get "At least one address is required." It doesn't look like the address is being included in the command call:
running terraform state rm -state=/home/vscode/.terraform.cache/sepazcafenv/rover_jobs/20230126154929728220187/tfstates/level3/tfstate/lz_common_subscriptions.tfstate
Usage: terraform [global options] state rm [options] ADDRESS...
Did I miss something?
—
Reply to this email directly, view it on GitHub , or unsubscribe .
You are receiving this because you were mentioned. Message ID: <aztfmod/rover/issues/292/1405218660 @ github . com>
—
Reply to this email directly, view it on GitHubhttps://github.com/aztfmod/rover/issues/292#issuecomment-1406264380, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AU2J37YHQC6AWCNXK76NQFTWUOKVTANCNFSM6AAAAAASKN36BE.
You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHub , or unsubscribe .
You are receiving this because you were mentioned. Message ID: <aztfmod/rover/issues/292/1406332714 @ github . com>

authors: gesnaud jtdossett

repo: aztfmod/rover


text:
fish shell over cliws can not parse arrow keys

I have no problem with bash. But fish shell prints [A[B[C[D when I press arrow keys. Some other key bindings also print something like [I[O. It's only appears over cliws.
I tried using xterm terminal and use TERM=xterm-256color on both sides, still not work.

Figure it out. Seems fish parse [C as [ and C, as the delay between key chars reaches timeout? raise the timeout can solve.
set fish_escape_delay_ms 100


text:
AtVirtualScroll 可视区域行数计算错误

问题描述
AtVirtualScroll 可视区域行数计算错误
版本信息
v1.0.0-alpha.13
涉及的平台
小程序 h5
代码

function getLast(first: number): number {
  // parseInt 笔误，导致 height 值固定不变
  const height = parseInt(`${props.height || 0, 10}`) || elRef.value.$el.clientHeight

  return first + Math.ceil(height / __itemHeight.value)
}

d76edcdc21b76c6e6443a94020cfd36a709564b9
移除 viewport 属性，由 getLast 方法自动计算 viewport 所显示的行数。


text:
go: cannot find GOROOT directory: /home/daniel/go

hi
this is same as #234
I download the binary for linux 64
@ubuntu:~/wide$ go env
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/XXXXX/go" //I delete user name
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0"
CXX="g++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"

please inform how I can correct the GOROOT directory from "/home/daniel/go" to  "/usr/local/go"

solved by deleting the wide directory ( downloaded from binary) and install again from source...


text:
用美国VPS部署项目，但网页无法访问，提示SyntaxError: Unexpected identifier

What operating system are you using?
Mac
What browser are you using?
Chrome
Describe the bug
docker logs 完整提示：
[ssr] SyntaxError: Unexpected identifier
at ESMLoader.moduleStrategy (node:internal/modules/esm/translators:119:18)
at ESMLoader.moduleProvider (node:internal/modules/esm/loader:468:14)
yml文件
`
version: '3'
services:
app:
image: babaohuang/geminiprochat:latest
container_name: geminiprochat
restart: always
ports:
- 3000:3000
environment:
- GEMINI_API_KEY="MY API KEY"
`
之前同样方式部署的chatgpt项目是正常的，奇怪了
What prompt did you enter?
No response
Console Logs
No response
Participation

[ ] I am willing to submit a pull request for this issue.

Starting service
Running script
看起来是服务没起来，不知道是什么原因？

repo: babaohuang/GeminiProChat


text:
BUG: uninstall not working for some scripts

Hello! :hugs:
Firstly, bookmark-files-combiner is a babashka script I installed a week ago with bbin install and now I want to uninstall it (so I can install a newer version afterwards).

My input at the terminal:

bbin uninstall bookmark-files-combiner

Expectation: script is uninstalled globally

What happened instead: script did not uninstall and outputs an error:

----- Error --------------------------------------------------------------------
Type:     clojure.lang.ExceptionInfo
Message:  Invalid script coordinates.
If you're trying to install from the filesystem, make sure the path actually exists.
Data:     {:script/lib "bookmark-files-combiner", :procurer :unknown-procurer, :artifact :unknown-artifact}
Location: /home/amit/.babashka/bbin/bin/bbin:1192:5

----- Context ------------------------------------------------------------------
1188:   (println (str (util/bin-dir cli-opts))))
1189:
1190: (defn- throw-invalid-script [summary cli-opts]
1191:   (let [{:keys [procurer artifact]} summary]
1192:     (throw (ex-info "Invalid script coordinates.\nIf you're trying to install from the filesystem, make sure the path actually exists."
          ^--- Invalid script coordinates.
If you're trying to install from the filesystem, make sure the path actually exists.
1193:                     {:script/lib (:script/lib cli-opts)
1194:                      :procurer procurer
1195:                      :artifact artifact}))))
1196:
1197: (defn- new-script [cli-opts]

----- Stack trace --------------------------------------------------------------
babashka.bbin.scripts/throw-invalid-script - /home/amit/.babashka/bbin/bin/bbin:1192:5
babashka.bbin.scripts/throw-invalid-script - /home/amit/.babashka/bbin/bin/bbin:1190:1
babashka.bbin.scripts/load-script          - /home/amit/.babashka/bbin/bin/bbin:1243:11
babashka.bbin.scripts/load-script          - /home/amit/.babashka/bbin/bin/bbin:1228:1
babashka.bbin.scripts                      - /home/amit/.babashka/bbin/bin/bbin:1273:20
... (run with --debug to see elided elements)
babashka.bbin.cli/bbin                     - /home/amit/.babashka/bbin/bin/bbin:1341:1
babashka.bbin.cli                          - /home/amit/.babashka/bbin/bin/bbin:1347:3
clojure.core/apply                         - <built-in>
babashka.bbin.cli                          - /home/amit/.babashka/bbin/bin/bbin:1351:3
babashka.bbin.cli                          - /home/amit/.babashka/bbin/bin/bbin:1349:1

Thanks for the report. I’ll get this fixed soon.

This will be fixed in the upcoming 0.2.0 release.

0.2.0 has been released.

authors: amitnovick rads

repo: babashka/bbin


text:
Restrict SET/RESET ROLE/SESSION AUTHORISATION from TDS endpoint (#2513)

Description
Before this commit, SET/RESET ROLE/SESSION AUTHORISATION statement executed from TDS endpoint via function, procedure or trigger can change the current user and session user, leading to mess up the Babelfish security context setup.
This commit avoids above scenarios by blocking SET/RESET ROLE/SESSION AUTHORISATION from being executed from TDS endpoint.
Issues Resolved: BABEL-4890
Signed-off-by: Harsh Lunagariya lunharsh@amazon.com
Issues Resolved
BABEL-4890
Cherry-pick of https://github.com/babelfish-for-postgresql/babelfish_extensions/pull/2513
Test Scenarios Covered

Use case based -
Function, Procedure with SET/RESET ROLE
Function, Procedure with SET/RESET ROLE

Boundary conditions -

Arbitrary inputs -

Negative test cases -

Minor version upgrade tests -

Major version upgrade tests -

Performance tests -

Tooling impact -

Client tests -

Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build 8813050781
Details

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 72.939%

Totals

Change from base Build 8812947782:
0.002%

Covered Lines:
41155

Relevant Lines:
56424

💛  - Coveralls

authors: HarshLunagariya coveralls


text:
fixing the issue of select cast with invalid number of function argument

Description
Cherry pick from : https://github.com/babelfish-for-postgresql/babelfish_extensions/pull/3005

Problem - cache lookup failed error when we run cast query with extensions like PgAudit, Valgrind enabled.
RCA - we blindly trying to call cast function with three arguments every time where as in postgres the number of function arguments can vary from 1 to 3.
Fix - Adding the handling cases as per the number of arguments(nargs) passed via cast query.

Issues Resolved
[BABEL-5272] [BABEL-4476]
Sign Off
Signed-off-by: Pranav Jain pranavjc@amazon.com
Test Scenarios Covered
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build 11253339397
Details

8 of 10 (80.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.001%) to 73.679%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contrib/babelfishpg_common/src/sqlvariant.c
8
10
80.0%

Totals

Change from base Build 11223292497:
0.001%

Covered Lines:
42965

Relevant Lines:
58314

💛  - Coveralls


text:
Any chance to set up min_score without raw request?

\ScoutElastic\ElasticEngine::buildSearchQueryPayloadCollection
Looks like it would be a great place here to init min_score for request?
I mean something like ->setIfNotEmpty('body.min_score', $builder->min_score)
        return $payloadCollection->map(function (TypePayload $payload) use ($builder, $options) {
            $payload
                ->setIfNotEmpty('body._source', $builder->select)
                ->setIfNotEmpty('body.collapse.field', $builder->collapse)
                ->setIfNotEmpty('body.sort', $builder->orders)
                ->setIfNotEmpty('body.explain', $options['explain'] ?? null)
                ->setIfNotEmpty('body.profile', $options['profile'] ?? null)
                ->setIfNotNull('body.from', $builder->offset)
                ->setIfNotNull('body.size', $builder->limit);

If it is already implemented please add min_score instructions to documentation

Any thoughts?

@babenkoivan any thoughts?

repo: babenkoivan/scout-elasticsearch-driver

license: mit


text:
When i use * to search, the search rules not be applied

Versions

scout-elastic-driver: 4.2.2
laravel/framwork: 5.5.49
php: 7.4.9
elasticsearch: 7.3.0

Description
When i use any term to search, my search rules is applied correct, but when not use terms, my search rules is ignored
Steps to reproduce
Set up any search rules, enter any term and search, remove the term and search again.

That's the intended behavior. It's explained here

authors: RodrigoGalter gambrosino


text:
run cargo audit in GitHub Actions

https://github.com/rustsec/audit-check

closed by https://github.com/babichjacob/ac-qu-ai-nt/commit/c1bab4d55e3c4a0b05d6d94440e9cdbda8995356, https://github.com/babichjacob/ac-qu-ai-nt/commit/6036d40defa66f6a05be746a612b968b8e7cf64b, https://github.com/babichjacob/ac-qu-ai-nt/commit/0f7cd069bb3199c5afbd88cd01ec0869983cff2c, and https://github.com/babichjacob/ac-qu-ai-nt/commit/dace2d531adf655d152168a2326196a380bb5bcf

repo: babichjacob/ac-qu-ai-nt


text:
Manage compute node CPU resources

We want to exert more fine-grained control over CPU usage of jobs, and so we should set a reasonable value for the limit-job-cpu option on our compute nodes.  This should be enough for executions to run efficiently, but not so much that compute nodes end up blocked in the OS run queue waiting for CPU.
We might also want to choose a sensible default for --limit-total-cpu to ensure we leave enough for the bacalhau nodes to consume.

This looks like specific to our demo network configuration

authors: rossjones wdbaruni

repo: bacalhau-project/bacalhau


text:
🛑 SM Service is down

In ee39053, SM Service (http://smservice.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SM Service is back up in 367850f.

repo: bachmannschumacher/upptime


text:
🛑 SM Service is down

In 47944b7, SM Service (http://smservice.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SM Service is back up in c040765 after 20 minutes.


text:
🚀 Feature: plugin-catalog-backend-module-gitlab support custom

🔖 Feature description
We use the Gitlab catalog discovery plugin, this works as defined. In our use case we want to use a specific type and catalogFile. The custom type is working fine if we import manually. The issue is that the Gitlab discovery import only supports the default url type.
🎤 Context

Support custom yaml file implementations for the gitlab discovery
Not sure if other discovery plugins have similar needs

✌ Possible Implementation
source file `src/providers/GitlabDiscoveryEntityProvider.ts``
  private createLocationSpec(project: GitLabProject): LocationSpec {
    const project_branch = project.default_branch ?? this.config.fallbackBranch;
    return {
      type: this.config.catalogType ?? 'url',
      target: `${project.web_url}/-/blob/${project_branch}/${this.config.catalogFile}`,
      presence: 'optional',
    };
  }

👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

Could also make it a callback that you pass to the provider.
GitlabDiscoveryEntityProvider.fromConfig(config, {
  logger, schedule,
  createLocation: (providerConfig, project) => {
    return { type: 'custom', target: '....' };
  }
})

Thanks @freben - this might be an option as well - can you give me an example how this would be passed in?

authors: freben michaelvogtmobi

repo: backstage/backstage


text:
BEP: Dynamic Frontend Plugins

🔖 Feature description
The dynamic frontend plugins feature is a way of loading additional frontend plugins at runtime, without the requirement of rebuilding and restarting a running backstage instance.
This system should significantly improve frontend plugin management for backstage instances.
The dynamic plugins leverage the declarative UI system to define what a plugin is and how it should be represented in the browser.
🎤 Context
https://github.com/backstage/backstage/tree/master/beps/0002-dynamic-frontend-plugins
✌ Possible Implementation
No response
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

A new PR was added with some results of the initial exploration of combining different module federation builds tools in a single runtime.
Code: https://github.com/scalprum/mf-mixing-experiments
PR: https://github.com/backstage/backstage/pull/22429

@Hyperkid123, regarding https://github.com/backstage/backstage/pull/22513/commits/4d3cbf7877a9eb100c995a7c9ec3472487a17aee#r1472665454: is there any reason not to maximise module sharing? Basically listing every single external dependency as a shared module? Asking just as a way to explore that extreme.
Selecting the correct version range might be a bit tricky, since using the package.json ranges risks that you're testing the plugin towards newer versions of your dependencies, but if a shared module brings in an older one that might not be something that the plugin supports in practice. That could be mitigated by switching out the package.json dependency bump strategy, but it might also make sense to go with a completely different solution, like using the versions that's currently installed as the base.

@Rugvip  Sure. If you list all available modules from a package, the module federation is smart enough to share and include in the output only modules that are used in the source code. So there is no problem if only a fraction of modules is used. We use this approach in our projects and it works well. You minimize the overhead.
If you share the entire package (for example MUI), tree shaking is disabled and you bundle everything even if it's never used.
There are a few scenarios where this becomes problematic.

Massive module libraries like icons where you usually use a fraction of available modules will be just added to the build assets. No way around that.
Required version mismatch. If a remote module has a shared config set to a specific version, and no module in the shared scope would match the version requirement, the remote will fall back to its own. This means that you are constantly pulling new assets (which might not be required), which has a performance impact. I think the impact becomes even worse in backstage use case where all plugins are preloaded even though the user never interacts with them.

And because AFAIK backstage plugins do pin their dependencies, the version requirements would rarely be met.
I would say either don't share these types of dependencies at all or just share individual modules and transform the imports at build time.

A quick summary of module federation feature support by individual tested packages in https://github.com/scalprum/mf-mixing-experiments.
Tested packages

Rspack
Webpack native
Webpack @module-federation/enhanced
Vite @originjs/vite-plugin-federation

Dynamic remotes support

Tool
Out of the box support
Possible to implement custom support

Rspack
:white_check_mark:
:white_check_mark:

Webpack
:white_check_mark:
:white_check_mark:

@module-federation/enhanced
:white_check_mark:
:white_check_mark:

@originjs/vite-plugin-federation
:x:
:white_check_mark:

@module-federation/vite
:question:
:question:

Runtime compatibility

:white_check_mark: Out of the box compatibility
:warning: Requires custom implementation
:x: Not compatible

x
Rspack
Webpack
@module-federation/enhanced
@originjs/vite-plugin-federation

Rspack
-
:white_check_mark:
:white_check_mark:
:warning:

Webpack
:white_check_mark:
-
:white_check_mark:
:warning:

@module-federation/enhanced
:white_check_mark:
:white_check_mark:
-
:warning:

@originjs/vite-plugin-federation
:warning:
:warning:
:warning:
-

None of Vite builds are compatible with @module-federation/runtime package out of the box. An extra bridge is required. Rspack and Webpack (both the core and the @module-federation/enhanced packages) are compatible out of the box.
Module Scope sharing

:white_check_mark: Out of the box compatibility
:warning: Requires runtime specification
:x: Not compatible

x
Rspack
Webpack
@module-federation/enhanced
@originjs/vite-plugin-federation

Rspack
-
:white_check_mark:
:white_check_mark:
:warning:

Webpack
:warning:
-
:warning:
:warning:

@module-federation/enhanced
:white_check_mark:
:white_check_mark:
-
:warning:

@originjs/vite-plugin-federation
:warning:
:warning:
:warning:
-

Feature parity
The best feature parity is between Rspack and Webpack using @module-federation/enhanced tooling.
As mentioned previously, we can make all of the above work with each other. But we have to keep in mind, that runtime dynamic remote support is critical for plugins to be truly dynamic. Currently, that is something the Vite plugin does not support and I was not able to find any plugin that officially supports the feature or a future plan.
We could write a custom plugin, or augment the tested and add a custom dynamic remote support.

Sorry for the radio silence on this for the last lil bit. Love the research into module federation 👍 🎉 I think it's safe to say that we have a way forward there for now right? Likely sticking to Webpack at least in the short term to keep things simple, and use @module-federation/enhanced. Switching to Rspack still seems a lil bit early but def a potential path for the future.
I've now had a proper read through of the BEP and summarized my top prio questions in its current state:

Plugin integration into shell applications

Something I've been thinking about a bit is how we actually manage this config in practice. For example, do you think it's worth building in the ability to essentially dynamically install a plugin + config straight away, or just keep them separate for now?

Plugin registry

It's not actually immediately obvious to me what the purpose of the registry is? Could this be simplified to an interface instead, probably with a baseline implementation that grabs manifest locations or similar from config?
Alternatively I wonder what you think about making this part of the app backend in some form? So that the app backend is generally the source of truth for what additional manifests should be loaded in, maybe even doing some caching/hash validation.

Plugin discovery

Scanning what? isn't the plugin registry already be intended to be the source of truth?

Plugin manifest

At a glance it looks like plugin manifests will be simple to generate, i.e. they're just a build step/artifact, it's not something plugin builders usually need to interact with. Do you agree that that's the case?

Plugin storage

The current proposal covers the case where plugins are deployed and then integrated. What do you think about the case where one wants to install a plugin directly, without requiring a deployment step?

Likely sticking to Webpack at least in the short term to keep things simple, and use @module-federation/enhanced. Switching to Rspack still seems a lil bit early but def a potential path for the future.

Agreed. RSPack seems promising, but it still has a long way to go to.

Something I've been thinking about a bit is how we actually manage this config in practice. For example, do you think it's worth building in the ability to essentially dynamically install a plugin + config straight away, or just keep them separate for now?

I see no harm in having this out of the box. From the experience in Janus, making a plugin dynamic was in many cases just a question of triggering the new build pipeline with no changes required in the plugin itself. And because of how the new UI system works in backstage the occasional code tweaks we needed to do will be obsolete.

Alternatively I wonder what you think about making this part of the app backend in some form? So that the app backend is generally the source of truth for what additional manifests should be loaded in, maybe even doing some caching/hash validation.

This is basically what I had in mind. Because backstage is a full stack app, leveraging the backend is a no-brainer IMO. If the config/registry is then exposed via API or embedded into the main HTML file is probably a matter of preference. The important part is, that the registry/config is not cached by the browser or the API cache is always refreshed on a config change.

Scanning what? Isn't the plugin registry already intended to be the source of truth?

More or less. The discovery should be the mechanism that triggers whatever it is that is responsible for generating the registry. It can be as sible as having a chokidar watching a directory in which plugins are loaded. I think this will be more relevant in a future where some sort "plugin catalog" exists where users can enable/disable plugins in the UI. Then there is a question about where to actually look for plugins that can be installed. I might be thinking a bit ahead here.

At a glance it looks like plugin manifests will be simple to generate, i.e. they're just a build step/artifact, it's not something plugin builders usually need to interact with. Do you agree that that's the case?

I don't think they will need to interact at all. Plugin metadata can be generated without the dev input. Again, maybe in the future of some plugin catalog, the manifest might be the right place to add some metadata. Adding an option to extend the manifest with custom properties should not be a big deal if we decide it's needed in the future.

The current proposal covers the case where plugins are deployed and then integrated. What do you think about the case where one wants to install a plugin directly, without requiring a deployment step?

I now realize I was not clear in the BEP. I am working with the assumption that the frontend plugins installation will work similarly if not the same as the backend dynamic plugins. Both frontend and backend plugins are just JS modules so if we can find a common way to handle the installation I think it would benefit all.
Adding plugins without the extra deployment is the end goal we'd like to achieve.

Without an extra build I would say is the main goal?

@Rugvip Yes, sorry got the terms mixed up. Deployments are handled by whoever is running the instance.


text:
[Kubernetes] Check Kubernetes version before fetching resources

Feature Suggestion

For old clusters that do not have the networking.k8s.io/v1beta1/ingresses resource an error will be shown for all services. See example below:

I would like to propose a feature where the kubernetes plugin takes the available resources into account before fetching data from the cluster. And gracefully ignore those resources that are not available.
Possible Implementation

Backstage could do proper filtering depending what resources are available. kubectl get-versions will give you a list of available resources and then use this list to filter out those resources that are not available.

@mclarke47 for visibility 👍

Makes a lot of sense, after we load in the clusters we should compare what resources we intend to fetch with what is configured and not fetch resources we can't get.

@goober I fixed it using apiGroups: ["networking.k8s.io"] in ClusterRole. Hope it helps.

@ananthulasrikar, yeah I think that's a fix for when the groups are hidden because of auth and RBAC, but I think this ticket is more scoped towards those resources / apiGroups not existing on everyone's cluster.

Yes. Without correct RBAC you get 403 in response from the cluster. But as @benjdlambert says the ticket is about when the resource is not available at all, hence the 404

I'm having the same issue. Hope this would get fixed soon

@dweber019 a workaround would be to use the kubernetes. objectTypes config option to specify the types explicitly.
However, I think long term we should consult the api-versions

Have a look at the solution in https://github.com/backstage/backstage/issues/12095 and let me know what you think

first step https://github.com/backstage/backstage/pull/13871

authors: ananthulasrikar benjdlambert goober mclarke47 tszngai


text:
Document and remove warnings in Core API’s api reports

This meta ticket describes changes required to the API documentation in order to release Backstage Core APIs as version 1.0
The following warnings need to be removed before an item should be crossed in the list below:

Exported methods must have documentation. Missing documentation is indicated by // @public (undocumented) in the api report. Best practises for writing API documentation can be found in #7162
All type names used by the API need to be exported. Please note that type name has previously not been exported and might therefore need a new name suitable for external use. This is indicated by // Warning: (ae-forgotten-export) The symbol "FoobarOptions" needs to be exported by the entry point index.d.ts
Package exports must be marked @public. // Warning: (ae-missing-release-tag) "FiltersButton" is exported by the package, but it is missing a release tag (@alpha, @beta, @public, or @internal)

Documentation added to all exports:

[ ] config
[ ] theme
[ ] version-bridge
[ ] cli
[ ] cli-common
[x] config-loader
[ ] core-app-api
[ ] test-utils
[ ] test-utils-core
[ ] core-plugin-api
[ ] core-app-api
[x] errors

Exports marked as public

[x] config
[ ] theme
[ ] version-bridge
[ ] cli
[ ] cli-common
[x] config-loader
[ ] core-app-api
[ ] test-utils
[ ] test-utils-core
[ ] core-plugin-api
[ ] core-app-api
[x] errors

Type names exported

[ ] config
[ ] theme
[ ] version-bridge
[ ] cli
[ ] cli-common
[ ] config-loader
[ ] core-app-api
[ ] test-utils
[ ] test-utils-core
[ ] core-plugin-api
[ ] core-app-api
[ ] errors

cli package doesn't generate a api-report.md file for me, does it work for you?

authors: djamaile jhaals


text:
TechDocs: Use external storage for publishing generated files (GCS)

This PR adds the feature to use an external storage (Google Cloud Storage) as a place to store the generated TechDocs static content. For more context, see https://backstage.io/docs/features/techdocs/architecture
It makes breaking changes to TechDocs (@backstage/plugin-techdocs and @backstage/plugin-techdocs-backend). Please read through the changeset for details.
Closes #3400
Closes #3096
Note to reviewers
This is to help you review this PR faster. If you can not go through everything, I'll be thankful if you can review just these -

Have a look at the new configs. Link
techdocs-backend Router and how it serves to TechDocs using the new techdocs-common package. Link
The abstraction of all types of publishers (Local, GCS, S3, etc.) Link
How the Google Storage publisher works. Link

Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)

@backstage/maintainers May I ask you to please take a look at this, one more time? Some things changed since @freben last approved it. I have added a "Note to Reviewers" in the PR description, docs and changeset should help as well.
We in @backstage/techdocs-core did a mob-review for this. Let me know if you want me to jump in for a chat with you.
Thanks! 🙏 🙇

@Rugvip @freben Review changes ✅

Thanks for the feedback @freben ! All looks good and will follow up on them. Take care 🌻

Something weird happening in CI. All the tests pass locally, but on CI it's not able to find couple of files (which exist!). 🤔

@freben @iamEAP @hooloovooo Thank you so much for your valuable review - good learning experience for me! I have followed up on all of them. Please give a +1 or suggest more changes.

@backstage/maintainers Thinking about merging this today, to unlock more smaller issues/PRs. 😁


text:
stepDefinitions are not recognized on a CI pipeline run

Current behavior
I want to run e2e tests on an Azure Pipeline, but step definitions are not recognized on it.
Everything looks fine when I run my tests locally.

Desired behavior
I have a .cypress-cucumber-preprocessorrc.json where stepDenitions are defined.
{
"json": {
"enabled": false,
"output": "jsonlogs/log.json",
"formatter": "cucumber-json-formatter.exe"
},
"messages": {
"enabled": false,
"output": "jsonlogs/messages.ndjson"
},
"html": {
"enabled": false
},
"stepDefinitions": [
"[filepath]//.{js,ts}",
"[filepath].{js,ts}",
"cypress/e2e/step_definitions/.{js,ts}",
"[filepath]\.{js,ts}",
"[filepath].{js,ts}",
"cypress\e2e\step_definitions\*\*.{js,ts}"
]
}

Test code to reproduce
Versions

Cypress version 10.10.0:
Preprocessor version 13.0.3:
Node version 16.0:

Closed due to inactivity.

authors: badeball cristina-boop

repo: badeball/cypress-cucumber-preprocessor


text:
the default orm waterline.js does not create foreign key constraint when db is created

two possible solutions are:

write a sql script to automate foreign key generation
replace waterline orm with sequalize orm

will replace waterline orm with sequalize, all models and associations will be refactored!

repo: badfuture/huoshui-backend-sailsjs


text:
Maven URL badge: invalid response data

Are you experiencing an issue with...

[x] shields.io
[ ] My own instance
[ ] gh-badges NPM package

:beetle: Description
Shields.io doesn't seem to support Spring's versioning scheme.
Spring projects use 1.2.3.M4 notation for the milestone releases.
:link: Link to the badge

https://img.shields.io/maven-metadata/v/https/repo.spring.io/milestone/io/projectreactor/tools/blockhound/maven-metadata.xml.svg?label=Milestone
Targets https://repo.spring.io/milestone/io/projectreactor/tools/blockhound/maven-metadata.xml
:bulb: Possible Solution
Support "1.2.3.M4"-like notation

The issue is not with the version format, but that our schema currently balks when there's only a single version due to how the xml is parsed.
Adding a .single() to the schema here should resolve this (validated in my local env)

@calebcartwright thanks for fixing it! 👍

authors: bsideup calebcartwright

repo: badges/shields