EKS doesn't create AWSServiceRoleForElasticLoadBalancing service-linked role

I have issues
EKS cluster can't create AWSServiceRoleForElasticLoadBalancing at a new AWS account due to ec2:DescribeAccountAttributes action isn't included to the AmazonEKSClusterPolicy IAM policy that attached to IAM role for EKS cluster.
I'm submitting a...

[ ] bug report
[x] feature request
[ ] support request - read the FAQ first!
[ ] kudos, thank you, warm fuzzy

What is the current behavior?
It happens during the process of K8S service creation with a type LoadBalancer for the first time.
I've tested it at 2 AWS accounts.

The best way - it's to have an added action to the AWS managed policy for the  EKS.
But, it would be nice to add the custom IAM policy to the EKS cluster IAM role that will include the ec2:DescribeAccountAttributes action to fix this issue before the AWS policy be updated.
Are you able to fix this problem and submit a PR? Link here if you have already.
Environment details

Affected module version: 12.0.0
EKS: 1.16
Terraform version: 0.12.25

Any other relevant info
One of the previous PRs regarding the service-linked role for ELB - https://github.com/terraform-aws-modules/terraform-aws-eks/pull/160
AWS docs - link

I haven't been able to reproduce this. I tried deleting the service linked role in a test account and a cluster was able to recreate it before creating a load balancer.
Are you using a permissions boundary that does not grant iam:CreateServiceLinkedRole to the eks role? AWS service linked roles docs. Or something else in your account that limits IAM permissions for the cluster role?

Hi @dpiddockcmp
Thanks for your reply.
No, I'm not using the permissions boundary. I deployed cluster with default parameter regarding cluster IAM role(manage_cluster_iam_resources=true) for the Terraform module/
I faced the same issue with the creation of a service-linked role for ELB with EKS at a newly created account as mentioned in one of the previous issues - https://github.com/terraform-aws-modules/terraform-aws-eks/issues/183#issuecomment-435229552.
The root cause is that AWS Managed AmazonEKSClusterPolicy doesn't contain required permissions required for ELB service-linked role creation even allowing the creation of this role
        {
            "Effect": "Allow",
            "Action": "iam:CreateServiceLinkedRole",
            "Resource": "*",
            "Condition": {
                "StringLike": {
                    "iam:AWSServiceName": "elasticloadbalancing.amazonaws.com"
                }
            }
        }

@max-rocket-internet @dpiddockcmp Can we add some additional policy to the managed EKS cluster's IAM role by default? What do you think about it?

I'm still not convinced that the call to DescribeAccountAttributes is the source of your issue.
In a test account I removed the service role: aws iam delete-service-linked-role --role-name AWSServiceRoleForElasticLoadBalancing
And then asked EKS to create a classic ELB: kubectl  create service loadbalancer test --tcp=80:8080
Waited 15 minutes 🙄  and then looked at the full API hits in CloudTrail:
:20:30 eks: AssumeRole eks cluster role - ok
:20:30 eks: DescribeRouteTables - ok
:20:30 eks: DescribeSubnets - ok
:20:30 eks: CreateSecurityGroup - ok
:20:30 eks: DescribeSecurityGroups - ok
:20:30 eks: DescribeInstances - ok
:20:31 eks: CreateLoadBalancer - AccessDenied
:20:31 eks: CreateServiceLinkedRole - ok
:20:31 eks: DescribeSecurityGroups - ok
:20:31 eks: AuthorizeSecurityGroupIngress - ok
:20:31 eks: DescribeAccountAttributes - Client.UnauthorizedOperation
:20:31 eks: DescribeLoadBalancers - AccessPointNotFoundException
:20:31 eks: CreateTags [sg] - ok
:20:36 eks: DescribeRouteTables - ok
:20:36 eks: DescribeSubnets - ok
:20:36 eks: DescribeSecurityGroups - ok
:20:37 eks: DescribeSecurityGroups - ok
:20:37 eks: DescribeAccountAttributes - Client.UnauthorizedOperation
:20:37 eks: DescribeLoadBalancers - AccessPointNotFoundException
:20:37 eks: CreateLoadBalancer - AccessDenied
:20:37 eks: CreateServiceLinkedRole - InvalidInputException
:20:47 ELB: AssumeRole AWSServiceRoleForElasticLoadBalancing - ok
:30:47 ELB: DescribeAccountAttributes - ok
:20:47 eks: DescribeSecurityGroups - ok
:20:47 eks: DescribeSubnets - ok
:20:47 eks: DescribeRouteTables: ok
:20:47 eks: DescribeLoadBalancers: AccessPointNotFoundException
:20:47 eks: DescribeSecurityGroups: ok
:20:47 eks: DescribeVpcs: ok
:20:47 eks: DescribeInternetGateways: Client.UnauthorizedOperation
:20:47 eks: DescribeSubnets: ok
:20:47 eks: DescribeAccountAttributes: Client.UnauthorizedOperation
:20:48 eks: DescribeSecurityGroups: ok
:20:48 eks: DescribeLoadBalancers: ok
:20:48 eks: DescribeSecurityGroups: ok
:20:48 eks: CreateLoadBalancer: ok
:20:48 ELB: DescribeInternetGateways: ok
:20:48 eks: ConfigureHealthCheck: ok
:20:48 eks: DescribeLoadBalancerAttributes: ok
:20:48 eks: DescribeSecurityGroups: ok
:20:48 eks: ModifyLoadBalancerAttributes: ok
:20:54 ELB: CreateNetworkInterface: ok

There are multiple failed calls to DescribeAccountAttributes but it does not block the CreateServiceLinkedRole. The ELB service eventually gets the call to work via its service role.
The kube-controller-manager log shows a similar time line:

Starts creating the resources for the ELB at :20:30. And at :20:31 errors with the failed call to ec2:DescribeAccountAttributes. We see above that the call to CreateLoadBalancer has also failed but the creation of the service account has been successfully started.
Tries going through the flow again at :20:36 and fails with the same error. CreateLoadBalancer also fails. Service account isn't ready yet?
Tries again at :20:47 and succeeds this time. The call to DescribeAccountAttributes was done via the service role.

@dpiddockcmp Thank you a lot for your such deep research regarding this issue.
I've created the EKS cluster at a new AWS account with a default EKS cluster role with the Terraform module. Unfortunately, the ELB service-linked role didn't create after a LoadBalancer service definition during 1h with errors described above.
After that, I've attached the EC2ReadOnly policy to the cluster role. Then service-linked role and LB were successfully created.
Anyway, I'm going to bootstrap one more AWS account soon with the same config. I will check it again and back to you.

Maybe it would be interesting to look through the CloudTrail logs and see what's failing.

Hi @dpiddockcmp
I've tried once again and was waiting during ~2h for ELB service-linked role creation.
Unfortunately, the result was the same as described in the issue.
EKS cluster can't create an ELB service-linked IAM role on a new AWS account.
» kubectl get events -n kube-system
LAST SEEN   TYPE      REASON                   OBJECT                             MESSAGE
8s          Normal    EnsuringLoadBalancer     service/nginx-ingress-controller   Ensuring load balancer
55m         Warning   SyncLoadBalancerFailed   service/nginx-ingress-controller   (combined from similar events): Error syncing load balancer: failed to ensure load balancer: error creating load balancer: "AccessDenied: User: arn:aws:sts::{{ new_account_id }}:assumed-role/{{ some-eks-cluster-role-}}20200609182020032300000001/1591727789516159494 is not authorized to perform: ec2:DescribeAccountAttributes\n\tstatus code: 403, request id: 0230f760-c5fd-4a8e-85e1-2ef93be4dfe7"

After that, I've added inline IAM policy with the ec2:DescribeAccountAttributes permissions to the EKS cluster IAM role.
The result was the same (ec2:DescribeInternetGateways permissions are required) as mentioned here https://github.com/terraform-aws-modules/terraform-aws-eks/pull/902#discussion_r434933437
» kubectl get events

21s         Warning   SyncLoadBalancerFailed   service/nginx-ingress-controller                     Error syncing load balancer: failed to ensure load balancer: error creating load balancer: "AccessDenied: User: arn:aws:sts::{{ new_account_id }}:assumed-role/{{ some-eks-cluster-role-}}20200609182020032300000001/1591727789516159494 is not authorized to perform: ec2:DescribeInternetGateways\n\tstatus code: 403, request id: c91a3082-6ce8-4d62-8a9b-e2588afd3121"

And only when mentioned permissions were attached to the IAM role, EKS cluster was able to create a service-linked IAM role and load balancer for the Kubernetes service.

It was helpful in my case.
Also, I can say, based on the previous issues and actual comments at the PR, this case is not specific only for me.

I hit this on two new clusters today. Confirmed adding the permissions manually fixed my issue.

Fixed in #902


Add Flow Linting support

Reference:

[ ] https://flow.org/en/docs/linting/

Seems to be a duplicate of the linter, closing for now


Fix session-based memory leak.

This fixes a flaw introduced by PR #2050
The error was that we did not fix Http1ClientTransaction::destroy() only the ProxyClientTransaction::destroy().  So the transaction_done() wasn't getting called in many of the Http1 cases.
I also fixed up and added the override keyword as long as I was in there.

Hmm.  I think I see one more issue.  Just a sec.


convert from type=cppdbg to type=gdb

Hello,
Because I want an automatic run of gdb, I want to use this plugin's gdb.
I'm on macos 10.12.6 and compiled gdb with all targets to debug remote linux code.
Here's what I have that works (I need to run gdbserver manualy):
            "name": "hello",
            "type": "cppdbg",
            "request": "launch",
            "program": "./hello",
            "cwd": "/Volumes/share/hello",
            "stopAtEntry": false,
            "MIMode": "gdb",
            "miDebuggerPath": "/Users/fensoft/gdb-8.1.1/bin/gdb",
            "miDebuggerServerAddress": "server"

Here's what I have converted to use this plugin:
            "type": "gdb",
            "request": "launch",
            "name": "hello",
            "target": "./hello",
            "cwd": "/Volumes/share/hello",
            "gdbpath": "/Users/fensoft/gdb-8.1.1/bin/gdb",
            "printCalls": true,
            "showDevDebugOutput": true,
            "ssh": {
                "host": "server",
                "cwd": "/data/hello",
                "keyfile": "/tmp/.id_rsa",
                "user": "root"
            }

The problem is, when I start debugging, it simply briefly show the debug buttons and that's all. No error messages, nothing.
Any idea ?

try making target an absolute path. Does the ssh.keyfile exist? Otherwise I don't really know what could be the issue. Is there no log at all in the debug output panel?

I got it working. Several problems here:
The first looks like a bug in VSCode. To view the debug console, I need to switch to another debug console then switch back to the main debug console again.
The second is that the local machine does not need a local gdb version nor using gdbserver.
And, yeah, put target as an absolute path is mandatory here.

target will be relative to cwd. If you want it relative to your project workspace, use ${workspaceRoot}/path/to/executable
You are right, X11 forwarding defaulting to true seems wrong as it most likely always needs some configuration to make it work.

also, tagging gdb-server for this repo and not using it makes me doing wrong guess on how it's working. Maybe claryfing it in the documentation can be a good idea (i thought it was creating a gdbserver and tunnel it through ssh but it's not the case)

Using gdb server works differently, see https://github.com/WebFreak001/code-debug#using-gdbserver-for-remote-debugging-gdb-only
If you want to use it over SSH, use SSH tunneling to connect to it

Oh, yeah, sorry. So it can also be used to connect to an existing gdbserver.
Is it possible to add a feature to automaticaly run the gdbserver (and managing the ssh tunnel) on the other side ?

you can use a preLaunchTask to run a command


Problem with the pagination visual size.

Angular 2 version:
2.1.0
ng2-pagination version:
latest
https://s17.postimg.org/9d7zek7dr/paginator.png
Is there a way to make it bigger ?
// edit:  for some reason it inherits the bootstrap html font-size of 10px

check it in the ng2-pagination folder under node-modules and find the template.js file. in that locate font-size='some' rem.. increase it .. u ll get what u require..

See https://github.com/michaelbromley/ng2-pagination/issues/64


URL with Trailing Slash with Next.js returns 403 status code

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
d17g4lsg0ngzxg
AWS Region
us-east-1
Amplify Hosting feature
Not Applicable
Describe the bug
I have deployed a simple Next.js SSG website with an index page and test page. Repository: https://github.com/anatolzak/nextjs-trailing-slash
Pages:
https://main.d17g4lsg0ngzxg.amplifyapp.com
https://main.d17g4lsg0ngzxg.amplifyapp.com/test
And I don't have any rewrites or redirects.
When going to https://main.d17g4lsg0ngzxg.amplifyapp.com/test, everything works correctly. But when going to the same url but with a trailing slash, I get a 403 page.
So apparently, trailing slashes don't work
Expected behavior
URLs with a Trailing slash should redirect to their counterpart without a trailing slash which is the default behavior for Next.js apps as described here: https://nextjs.org/docs/api-reference/next.config.js/trailing-slash.
Or URLs with a trailing slash should at least not return 403 status code and instead just render the same page as without a trailing slash.
Reproduction steps

Deploy a Next.js app
Delete any rewrites or redirects
Go to any page except the index page and add a trailing slash to the url, and you should get 403

Build Settings
No response
Log output

# Put your logs below this line

Additional information
No response

For anyone else with the same issue, a workaround for this issue, is to set trailingSlash to true in next.config.js (https://nextjs.org/docs/api-reference/next.config.js/trailing-slash).
After doing that, it looks like AWS Amplify redirects all urls without a trailing slash to the urls with a trailing slash.
I am not sure why by default AWS Amplify can't redirect urls with trailing slashes to their counterpart without a trailing slash which is the default expected behavior for Next.js apps as described here: https://nextjs.org/docs/api-reference/next.config.js/trailing-slash
It is pretty absurd that you can't deploy a Next.js app as is without finding all the different bugs that AWS Amplify has with Next.js apps and trying to find solutions to all the different problems it has to make your deployment actually work.

Hi @anatolzak 👋🏽 thanks for raising this issue and providing feedback. I have not been able to reproduce this on my end. I've deployed SSG and SSR apps with Next.js and navigating to paths ending / just redirected it to the path without it.
Are you experiencing this behavior with any other apps you have deployed?

Hi there, I am having a very similar issue with my relatively plain NextJS 13.4 app using app router. All of my links and images outside of my homepage itself seem to return 403 except for one, which I am linking with a URL parameter.  I am using NextJS  instead of . My appID appears as follows  arn:aws:amplify:us-east-1:[AWS_ARN_HERE]:apps/da397fbpzwtia

@hloriii The issue doesn't occur on next.js ssr apps.
I just deployed a simple next.js ssg app. When going to any route that isn't the base path, for example /test, it works fine. When going to /test/, if there is no redirects or rewrites, it returns 403. If there is a rewrite to 404.html, it returns the 404 page instead of the test route.
Here is the SSG app I just deployed that is behaving in the above described ways: https://main.d3qwejj06ayzs0.amplifyapp.com/test/

I spent about 8 hours troubleshooting and also comparing builds with Vercel on this -- It seems that this issue appears for Vercel deployments as well in my testing. Here are the steps I took to solve my issues:

Nextjs app directory routing+config is extremely case sensitive. Several of my  tags had camelCase text within that needed to be fixed.
NextJS local "release"/"prod" builds are much less strict than deployed ones. yarn build && yarn start might work fine on local but end up breaking on actual deploys
This one is displeasing: builds sometimes change the case of your component name or URL all on their own and ignoring what your source specifies. Check the build logs for your app and change your link tags the output directories you see mentioned in the build logs on amplify console.
Import images on top your file instead of trying to reference them inside  tag.
Output: "standalone", should be inside your next.config.js


Concrete/Wooden/Metal Roof not rendering properl

Roof imports into blender as something similar to a roof panel instead of a square with raised centre.

Can you post a screenshot in NMS to what it should look like?

check out v1.3.0 and let me know if all is good

Have installed an still same issue.

Hmm, was just thinking. Maybe I need to import from my save game file as I just opened my saved blender files. Save Game Editor is nerfed due to latest update so I can't test imports

Can confirm all is working. Thank you


noVNC encountered an error:  Uncaught TypeError: crypto.randomUUID is not a function chrome-extension://dmkamcknogkgcdfhhbddcghachkejeap/injectedScript.bundle.js:2:90761

doing reload when connected to full VNC generates this error message. Oddly, if I connect to the root of noVNC, I can select the Full version just fine. Just happens on reload (I'm using Chrome browser on windows).
This may not be your bug or something you can fix, but I've never seen this before.
noVNC encountered an error:

Uncaught TypeError: crypto.randomUUID is not a function
chrome-extension://dmkamcknogkgcdfhhbddcghachkejeap/injectedScript.bundle.js:2:90761

GREAT work.
Have you thought of including a docker compose.yaml file for sample usage in the readme?
version: "3.8"
### listens on 5901 for VNC connections and
### 6901 for NoVNC web connection
### so point the web browser to 8084 and enter
### the password: x
### when you get in, the sudo password is headless
services:
  debian:
    image: accetto/debian-vnc-xfce-chromium-g3
    hostname: debian
    restart: unless-stopped
    ports:
      - 8084:6901
    shm_size: 512m ## container run time
    environment:
      VNC_PW: x
      VNC_RESOLUTION: 1920x1080
    volumes:
      - /mnt/main/appdata/Debian-Bullseye:/mnt/debian
networks: {}

Hello @skirsch,
thank you for your feedback. I also never got the error you've described. First I'll try to reproduce it and then we'll see, what we can do about it. There is also a newer noVNC version released, which I plan to include.
Some time ago I've moved all README examples to the User Guide, to simplify the maintenance of all the projects. So I need to think about your proposal a little bit, if I could manage.
Regards,
accetto

it is a pretty odd bug for sure. it is 100% repeatable with that docker container setup. got to the home page, pick full vnc fviewer. works fine. Hit refresh: you get that error message 100% of the time.

I've got a second look to the issue title Uncaught TypeError: crypto.randomUUID is not a function chrome-extension://dmkamcknogkgcdfhhbddcghachkejeap/injectedScript.bundle.js and I'm afraid, that you've got a cryptomining malware extension in your web browser. The extension name itself looks pretty ridiculous. What do you think?
I would recommend to uninstall the extension, reboot and to try it without it.

Good catch. Turning on developer mode in Chrome lets you see the codes.

Keplr is SUPPOSED to be legit!!!
I will remove it and try again. And low and behold, you win the prize!!! No more error!

thank you for investigating!

I'm glad you've solved it. :)


X.A.CycleRecentWS: Cycle workspaces, not windowsets

Description
Fixes #504.  The patch got a little bit more complicated; see below.
The way that workspace cycling is implemented right now—by generating
new windowsets where the things we want happen to be true and then
replacing the old windowsets—is not safe, as workspaces and layouts may
carry state with them.  That state will get lost in translation when
windowsets are simply replaced.
As an example, a conflict occurs when using X.L.ShowWName.showWName in
one's layoutHook.  When cycling through workspaces via, e.g.,
cycleRecentWS the flashed workspace tag will not disappear, as the
necessary state to control this isn't present in the new windowset.
Instead, what we want to do is to keep the "current" windowset alive and
actually switch to the requested workspaces.  This mostly works without
much trouble, the only hard part is maintaining the invariant that
previewed workspaces don't count towards the history of recently-viewed
workspaces.  This is done by remembering the tag-order of the original
windowset and then restoring that at the end.
This is a breaking change, insofar as it changes the type signatures of
the exported functions recentWS, cycleWindowSets, and
toggleWindowSets to return a list of WorkspaceIds instead of a list
of WindowSets.
Fixes: https://github.com/xmonad/xmonad-contrib/issues/504
I wonder about renaming at least toggleWindowSets.  The name is not quite accurate anymore and it's already a breaking change so...
@oogeek can you confirm that this works for you?
Checklist

[x] I've read CONTRIBUTING.md

[x] I've considered how to best test these changes (property, unit,
manually, ...) and concluded: The pure functions are rather testable and it may be worth actually implementing tests for them.

- [ ] I updated the XMonad.Doc.Extending file (if appropriate)
TODO:

[ ] I updated the CHANGES.md file

I pushed my attempt to simplify the fix.
Note that I don't hate the MultiWayIf, I just reverted the entire setOption change as I don't think it's necessary any more. Feel free to add another commit that just reformats it again.
Also note that I haven't bothered to actually test the final result in a real xmonad instance, I developed only against the property test. Can @oogeek please test that it still fixes their issue?

@oogeek friendly ping :)

Okay I rebased, updated the CHANGES.md, and enabled PatternGuards in b65b83661b37c3f29738985e796f5cca17a1440a to make the CI happy (thanks for enabling -Werror btw, this will hopefully prevent the buildup of tech debt this time around :))
Will merge once the CI is done and happy


Error in log when using StaticString.format

[INITIALIZATION][CLIENT][ERROR] crafttweaker\tooltips\coin_tooltips.zs:16 > a method available but none matches the parameters (string, int)
This is usually an error in your script, not in the mod
format(string, ZenTypeNative: java.lang.Object[])

It seems that ZenScript has no idea how to convert an int to an object.

Use StaticString.valueOf to convert the int to a string manually?

That's what I ended up doing.


Fix typo: "Troubleshooti" -> "Troubleshoot"

Thanks, I'll take it from here.

Fixed typo in a branch I was just getting ready to publish. Thanks for the correction! The update will be ready in ~15 minutes.


Behat tests for synchronize command.

[ ]   General Comment

Coverage increased (+7.7%) to 83.721% when pulling aadb696135c5fa37f0fae9497ddb7c3dccfb7c7c on kuczek:feature/behat-tests into ba26bb8646e52e5ff1d95d1ff1486fc6dcd20581 on Hexmedia:master.

Coverage increased (+7.7%) to 83.721% when pulling b42883733ad46de01a9a2b97a0d0435569f920ed on kuczek:feature/behat-tests into ba26bb8646e52e5ff1d95d1ff1486fc6dcd20581 on Hexmedia:master.

This pull request is now managed with CodeReviewHub. Refresh.

Coverage increased (+7.7%) to 83.721% when pulling aadb696135c5fa37f0fae9497ddb7c3dccfb7c7c on kuczek:feature/behat-tests into ba26bb8646e52e5ff1d95d1ff1486fc6dcd20581 on Hexmedia:master.

Coverage increased (+7.7%) to 83.721% when pulling b42883733ad46de01a9a2b97a0d0435569f920ed on kuczek:feature/behat-tests into ba26bb8646e52e5ff1d95d1ff1486fc6dcd20581 on Hexmedia:master.

Coverage increased (+7.7%) to 83.721% when pulling b86736c9b1365c386d4b26513744e5d57a7fc42f on kuczek:feature/behat-tests into ba26bb8646e52e5ff1d95d1ff1486fc6dcd20581 on Hexmedia:master.

Coverage increased (+7.7%) to 83.721% when pulling 4c430c76fc0f08ceb33af332edadcb5204bf7219 on kuczek:feature/behat-tests into ba26bb8646e52e5ff1d95d1ff1486fc6dcd20581 on Hexmedia:master.


[BUG] Logo overlapping sidebar for mobile view

Is there any existing issue for this?

[X] I have searched the existing issues

Description
LinksHub home root overlapping the sidebar for mobile view which is not good for user experience.
Screenshots

Any additional information?
No response
What browser are you seeing the problem on?
No response

I could take this up if it's still up for grabs

yes, go-ahead @Leeyah-123

I see it's already fixed though.

@Leeyah-123 could you link the PR, cz I'm still seeing it there

When I pulled main, it was already fixed so there was no change for me to commit.
Maybe try redeploying?


Push to live 12.02.16

:warning: Validation status: warnings

File
Status
Preview URL
Details

aspnetcore/mvc/views/view-components/_static/indexvc.png
:warning:Warning

Details

aspnetcore/mvc/views/view-components/_static/pi.png
:warning:Warning

Details

aspnetcore/mvc/views/view-components/_static/pvc.png
:warning:Warning

Details

aspnetcore/mvc/views/view-components/_static/shared.png
:warning:Warning

Details

aspnet/index.md
:white_check_mark:Succeeded

aspnetcore/fundamentals/localization.md
:white_check_mark:Succeeded

aspnetcore/fundamentals/logging.md
:white_check_mark:Succeeded

aspnetcore/fundamentals/startup.md
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components.md
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/StarterViewComp/Controllers/ToDoController.cs
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/StarterViewComp/Models/ToDoContext.cs
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/StarterViewComp/Program.cs
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/StarterViewComp/Startup.cs
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/StarterViewComp/ViewComponentSample.xproj
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/StarterViewComp/Views/Shared/Error.cshtml
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/StarterViewComp/Views/Shared/_Layout.cshtml
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/StarterViewComp/project.json
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/StarterViewComp/web.config
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/ViewCompFinal/Controllers/ToDoController.cs
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/ViewCompFinal/Models/ToDoContext.cs
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/ViewCompFinal/Program.cs
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/ViewCompFinal/Startup.cs
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/ViewCompFinal/ViewComponentSample.xproj
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/ViewCompFinal/ViewComponents/PriorityList.cs
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/ViewCompFinal/ViewComponents/PriorityListViewComponent.cs
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/ViewCompFinal/ViewComponents/PriorityListViewComponent1.cs
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/ViewCompFinal/ViewComponents/PriorityListViewComponentFinal.cs
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/ViewCompFinal/Views/Shared/Components/PriorityList/_Default.cshtml
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/ViewCompFinal/Views/Shared/Error.cshtml
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/ViewCompFinal/Views/Todo/Index.cshtml
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/ViewCompFinal/Views/Todo/IndexFirst.cshtml
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/ViewCompFinal/project.json
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/sample/ViewCompFinal/web.config
:white_check_mark:Succeeded

aspnetcore/security/data-protection/implementation/key-storage-format.md
:white_check_mark:Succeeded

aspnetcore/mvc/views/view-components/_static/indexvc.png

Line unspecified: [Warning] Model "obj\viewmodel\mvc\views\view-components_static\indexvc.png.xml.view.json" is transformed to empty string with template "Resource.xml"

aspnetcore/mvc/views/view-components/_static/pi.png

Line unspecified: [Warning] Model "obj\viewmodel\mvc\views\view-components_static\pi.png.xml.view.json" is transformed to empty string with template "Resource.xml"

aspnetcore/mvc/views/view-components/_static/pvc.png

Line unspecified: [Warning] Model "obj\viewmodel\mvc\views\view-components_static\pvc.png.xml.view.json" is transformed to empty string with template "Resource.xml"

aspnetcore/mvc/views/view-components/_static/shared.png

Line unspecified: [Warning] Model "obj\viewmodel\mvc\views\view-components_static\shared.png.xml.view.json" is transformed to empty string with template "Resource.xml"

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Updated Supported regions for Azure Arc on articles/azure-arc/servers/onboard-portal.md

fixes #56137

Replace WestAsia with SoutheastAsia
Added EastUS

@kiazhi : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@MGoedtel, this PR is the same fix like #56146 but on a different page.

@kiazhi - Thanks for opening this PR to correct the list.  I'm sorry to say that late yesterday I corrected this before seeing your PR.  The change is already published and live.  My apologies for not seeing this sooner.  #please-close.

@kiazhi - Thanks for opening this PR to correct the list. I'm sorry to say that late yesterday I corrected this before seeing your PR. The change is already published and live. My apologies for not seeing this sooner. #please-close.

@MGoedtel , you know that this is a different page .../articles/azure-arc/servers/onboard-portal.md?

@kiazhi - Yes, I understood this fact, thanks!


Radius function: local normalized coordinate system

🚀 Feature

Radius(x,y,r) finds for each element in y all points in x within distance r. It can be useful to have a parameter to return the set x in a local normalized coordinate system:  if a point u in the set x is within distance r from a point v in the set y, then u = (u - v) / r.
Motivation
This is mainly motivated by a recent paper I'm trying to reproduce using PyTorch Geometric:
Paper Section 4.2, paragraph "Proposal and classification from vote clusters."
Code

Thanks.

Hi, does this really need its own function parameter? I guess you can just compute u in a follow-up step using the edge_index, e.g.:
row, col = radius(...)
u = (x[row] - y[col]) / r

Hi! Thanks for your reply!
As far as I understood I think it should be u = (x[col] - y[row]) / r, but I get a strange behavior when doing that:
the size of x is 163840
the size of 'y' is 16384
the size of x[row] is 955375
the size of 'y[col]' is 955375
the max of row is 16383
the max of col is 163838

Yes, you are right. It is (x[col] - y[row]). I see no strange behavior in your results.

Why is the size of the input point set increasing?

Because you map each node feature to an edge feature.


Enable profiling over HTTP in debug mode

Signed-off-by: Andrea Luzzardi<EMAIL_ADDRESS>

LGTM

LGTM.

Cool! I've never seen this before.
Why no Trace?

@MHBauer What do you mean?

@aluzzardi  maybe I am looking in the wrong place, but I see one more function called Trace, here

LGTM


ts : Migrate feedback_widget.js to typescript

This Pull request migrates feedback_widget.js to typescript
It was also neccesary to make the parameter context of  the render variable in src/hbs.d.ts as optional as it was being invoked without a parameter in feedback_widget.ts in line 133

Self-review checklist

[X] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[X] Explains differences from previous plans (e.g., issue description).
[X] Highlights technical choices and bugs encountered.
[X] Calls out remaining decisions and concerns.
[X] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[X] Each commit is a coherent idea.
[X] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[X] Corner cases, error conditions, and easily imagined bugs.

@nzaih1999 any update on this one? please let me know. I really appreciate your exploration and contribution!

This file was migrated to TypeScript in ebaabc6b6807238b908cfd07e2838d41a6e74746.


If this plugin is enabled, then no caching features are enabled?

If this plugin is enabled, then no caching features are enabled?
I mean if the service worker is invalidated each time? When would it work? Only when is offline?

The main reason to use it, is when you want to unregister ServiceWorker. Like completely remove it and make sure it work. After that, offline or whatever won't work because there won't be registered ServiceWorker.
You later want to ship ServiceWorker again, just remove the code of this project (of the plugin if you're using it) and start using normal ServiceWorker which does what you need.

Got it! 😉


ERROR: Operator SQUARED_DIFFERENCE is not supported by armnn_delegate.

ERROR: Operator SQUARED_DIFFERENCE is not supported by armnn_delegate.

Hi @luchangli03
Can you provide any more details on the issue?
Such as:
ArmNN Version,
ACL version,
TfLite version,
System OS,
what device is being used,
Model information ( can you link the model? )
How are you running the delegate?
Regards,
Ryan

Hi @luchangli03 can you provide more details?
I will close this on October 10th if I do not hear from you.
Thank you,
Keith


Support np.random.permutation with int argument.

We currently replicate the result of the call to np.random.permutation with
integer argument.  Ideally, this should be parallelized, so that each processor
generates a chunk of the permutation array.  But this patch is mostly an exercise on
how to call a C++ extension, and we leave the true parallel implementation of
permutation for future work.

Coverage decreased (-0.2%) to 82.377% when pulling b103cfe6480a6d3cb499d962b985525d742b90c5 on agayev:permutation into 13e62681f3e6a89883d03948ba8873c23f980d66 on IntelLabs:master.


remove interrupt engine logic

Description
Resolves #5164
This PR removes the "interrupt" option from the compute engine window.
Type of change
Task. The feature is no longer used.
How Has This Been Tested?
I've opened up the compute engine window and confirmed the option has been removed.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have updated the release notes
[ ] I have made corresponding changes to the documentation
[ ] I have added debugging support to my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] I have added any new baselines to the repo
[ ] I have assigned reviewers (see VisIt's PR procedures for more information).

I haven't updated the release notes because I'm not sure what this goes under or if it should even be in those notes... It's not really a bugfix, enhancement, or development change.

I would probably put it as an enhancement. "Removed misleading interrupt button"

I consider it a bug fix. You are removing something that doesn't work.

Lol I just added it as an enhancement. I'll switch to bugfix.

Didn't see Eddie's comment. That works for me.

It's probably more of bugfix. It "enhances" visit by removing something that is wrong with it, whereas "enhancement" typically means a new/better feature.


Dev

Merge new updates
Improve readme
Improve docs.
Fix CI.

Codecov Report

Merging #45 (bc41d2c) into master (81f159d) will increase coverage by 0.29%.
The diff coverage is 69.53%.

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


[Angular]  Refactor all services to use new API and generated services

Now that we auto-generate all the apollo angular services, we need to refactor the angular project to use these new service, and to delete any old services no longer in use.

[ ] Update ALL modules/components to use new generated services

Must build sputnik-ui-angular-api locally to generate services.

[ ] Delete any services no longer used

Related to #23 and #24


Clarify how to disable the GCE ingress controller

Closes https://github.com/kubernetes/ingress/issues/1343.
Makes instructions on disabling ingresses more clear.

This change is

Coverage remained the same at 43.943% when pulling 78639ebfbda60d57f2c2ef2ac22814ab821de86b on tonglil:patch-2 into 6cca4c5cdde7ed1d89312add4c2ba93988556ea2 on kubernetes:master.

Coverage increased (+0.03%) to 43.968% when pulling 78639ebfbda60d57f2c2ef2ac22814ab821de86b on tonglil:patch-2 into 6cca4c5cdde7ed1d89312add4c2ba93988556ea2 on kubernetes:master.

Coverage remained the same at 43.943% when pulling 78639ebfbda60d57f2c2ef2ac22814ab821de86b on tonglil:patch-2 into 6cca4c5cdde7ed1d89312add4c2ba93988556ea2 on kubernetes:master.

Coverage increased (+0.3%) to 44.206% when pulling 19f49d5da0ad001fc2c181866d984cf71e8e94f4 on tonglil:patch-2 into 6cca4c5cdde7ed1d89312add4c2ba93988556ea2 on kubernetes:master.

Coverage increased (+0.3%) to 44.206% when pulling 62a480f00774319b2d647cec7e877e4e887bbc2d on tonglil:patch-2 into 6cca4c5cdde7ed1d89312add4c2ba93988556ea2 on kubernetes:master.

Coverage increased (+0.3%) to 44.206% when pulling 62a480f00774319b2d647cec7e877e4e887bbc2d on tonglil:patch-2 into 6cca4c5cdde7ed1d89312add4c2ba93988556ea2 on kubernetes:master.

Coverage decreased (-0.2%) to 43.769% when pulling 9bbabf12f1279b095e2d1cb324d13d88350018ed on tonglil:patch-2 into 6cca4c5cdde7ed1d89312add4c2ba93988556ea2 on kubernetes:master.

Coverage decreased (-0.2%) to 43.781% when pulling 9bbabf12f1279b095e2d1cb324d13d88350018ed on tonglil:patch-2 into 6cca4c5cdde7ed1d89312add4c2ba93988556ea2 on kubernetes:master.

Thanks


This makes the code more concise, and is no different from the original code logic.
Hope to consider merging this PR.

Thank you, @chenqimiao !


Rendering to SurfaceView sometimes does not work in Android

My initial scenario was:

initializeWebRtc in Application (not in Activity, so it survives a tilt)
make a call
hang up
call again
now video is black
tilt the screen in any direction, activity gets rebuilt and everything works OK

According to the logs, webGL is rendering frames but it's all black until the first tilt.
Unfortunately I could not get a minimal replication scenario for this. Should be something similar to this branch https://github.com/mihai1voicescu/WebRTCCompose/tree/with-mainApp
I however managed to replicate the bug (or at least it looks like it) in a different scenario using Activity as the context and rebuilding the webrtc connection each tilt. You can find the minimal replication scenario here https://github.com/mihai1voicescu/WebRTCCompose/tree/master
To replicate, as stated in the readme:

Run App
Connection is established
Tilt screen
Screen is now black but it is rendering frames

I assume it's something regarding some leftover metadata in the webGL context but I am kinda stuck 😅 .
Working render logs:
 01-27 17:40:34.224  I  [10501/15589] org.webrtc.Logging CameraStatistics: Camera fps: 25.
 01-27 17:40:34.307  I  [10501/15678] org.webrtc.Logging EglRenderer: Duration: 4002 ms. Frames received: 100. Dropped: 0. Rendered: 100. Render fps: 25.0. Average render time: 7989 us. Average swapBuffer time: 2912 us.
 01-27 17:40:36.225  I  [10501/15589] org.webrtc.Logging CameraStatistics: Camera fps: 25.
 01-27 17:40:38.226  I  [10501/15589] org.webrtc.Logging CameraStatistics: Camera fps: 25.
 01-27 17:40:38.310  I  [10501/15678] org.webrtc.Logging EglRenderer: Duration: 4003 ms. Frames received: 44. Dropped: 0. Rendered: 44. Render fps: 11.0. Average render time: 7018 us. Average swapBuffer time: 3635 us.
 01-27 17:40:40.227  I  [10501/15589] org.webrtc.Logging CameraStatistics: Camera fps: 25.
 01-27 17:40:42.228  I  [10501/15589] org.webrtc.Logging CameraStatistics: Camera fps: 25.
 01-27 17:40:42.313  I  [10501/15678] org.webrtc.Logging EglRenderer: Duration: 4002 ms. Frames received: 72. Dropped: 0. Rendered: 72. Render fps: 18.0. Average render time: 7423 us. Average swapBuffer time: 3183 us.

Black render logs:
 01-27 17:42:13.401  I  [10501/18707] org.webrtc.Logging EglRenderer: Duration: 4004 ms. Frames received: 120. Dropped: 0. Rendered: 120. Render fps: 30.0. Average render time: 6803 us. Average swapBuffer time: 2567 us.
 01-27 17:42:13.691  I  [10501/18694] org.webrtc.Logging CameraStatistics: Camera fps: 30.
 01-27 17:42:15.691  I  [10501/18694] org.webrtc.Logging CameraStatistics: Camera fps: 30.
 01-27 17:42:17.405  I  [10501/18707] org.webrtc.Logging EglRenderer: Duration: 4002 ms. Frames received: 120. Dropped: 0. Rendered: 120. Render fps: 30.0. Average render time: 4767 us. Average swapBuffer time: 1798 us.
 01-27 17:42:17.692  I  [10501/18694] org.webrtc.Logging CameraStatistics: Camera fps: 30.
 01-27 17:42:18.159  I  [10501/15594] org.webrtc.Logging NetworkMonitorAutoDetect: capabilities changed: [ Transports: WIFI Capabilities: NOT_METERED&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&VALIDATED&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED LinkUpBandwidth>=430185Kbps LinkDnBandwidth>=677812Kbps SignalStrength: -64 AdministratorUids: [] RequestorUid: -1 RequestorPackageName: null]
 01-27 17:42:19.693  I  [10501/18694] org.webrtc.Logging CameraStatistics: Camera fps: 30.
 01-27 17:42:21.410  I  [10501/18707] org.webrtc.Logging EglRenderer: Duration: 4004 ms. Frames received: 120. Dropped: 0. Rendered: 120. Render fps: 30.0. Average render time: 4716 us. Average swapBuffer time: 1845 us.
 01-27 17:42:21.694  I  [10501/18694] org.webrtc.Logging CameraStatistics: Camera fps: 30.
 01-27 17:42:23.694  I  [10501/18694] org.webrtc.Logging CameraStatistics: Camera fps: 30.
 01-27 17:42:25.420  I  [10501/18707] org.webrtc.Logging EglRenderer: Duration: 4006 ms. Frames received: 120. Dropped: 0. Rendered: 120. Render fps: 30.0. Average render time: 5039 us. Average swapBuffer time: 1979 us.
 01-27 17:42:25.695  I  [10501/18694] org.webrtc.Logging CameraStatistics: Camera fps: 30.
 01-27 17:42:27.698  I  [10501/18694] org.webrtc.Logging CameraStatistics: Camera fps: 29.

Any ideas or pointers?
Note that I am using Jetpack Compose which kills the Surfaces after they exit the tree.

I've just checked out your sample. Unfortunately, I couldn't reproduce the issue with my environment. However, I can see the potential problem: the local MediaStream is not released after the call ends in your code. It's required to call MediaStream.release() to stop video capturing and release the camera. I guess it might be the cause of the issue.

The bug seems to not replicate on Android 9. It replicates on Android 11.
For the moment I can't afford to look into it anymore, just made a workaround, but as soon as time allows it I will look more into it.

same question，but device is Android 12, Android 7 is work
_localStream.update {
                runCatching {
                    it?.release()
                }.onFailure {
                    Log.e(TAG, "hangup: release local stream filed.", it)
                }
                null
            }

            Log.d("hangup", "hangup: release local stream")

            runCatching {
                peerConnection?.close()
            }.onFailure {
                Log.e(TAG, "hangup: peerConnection close failed", it)
            }
            peerConnection = null
            _remoteStream.update { null }
            Log.d("hangup", "hangup: release remote stream")

exception
hangup: release local stream filed.
                                                                                java.lang.IllegalStateException: MediaStream has been disposed.
                                                                                at org.webrtc.MediaStream.checkMediaStreamExists(MediaStream.java:134)
                                                                                at org.webrtc.MediaStream.dispose(MediaStream.java:76)
                                                                                at com.orgaiot.call.WebRtcManager$hangup$1.invokeSuspend(WebRtcManager.kt:417)
                                                                                at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)


Golang Envoy filter - OPA integration

Communication with OPA: Passing in information via headers.

Purpose of use: We've currently extracted pod labels from the X-Envoy-Peer-Metadata header and injected into the  X-Prose-Purpose header. (Note that this header may not be available on outgoing requests to mesh external domains: see https://github.com/istio/istio/issues/17635)
PII types: We've derived PII types using Presidio and injected them into the X-Prose-PII-types header.

Each of these headers will be modified by each service proxy on each hop across microservices. So their values need to be base64 encodings of a JSON object map, not a string. The key of this object should be the span ID to avoid ambiguity. Can Envoy expose the span ID to any of the Decode/Encode StreamFilter API functions? Otherwise, we could use the service + API call name so if a key already exists, get its PII types / purpose, and append to its value of PII types or purposes?

The scope of this issue is slightly changed: we are no longer going to pass the information to OPA sidecar via headers or baggage, since we now have OPA sdk built-in right into our golang filter.


'string | undefined' on known index of string[]

Bug Report

🔎 Search Terms
noUncheckedIndexedAccess array index
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about noUncheckedIndexedAccess

First noticed in 4.2.4, tested also in 4.7.4
⏯ Playground Link
https://www.typescriptlang.org/play?noUncheckedIndexedAccess=true#code/JAMwrgdgxgLglgewgAgM4FMYCFMAooAWAhgE6oBcqMJcEA5gNoC6AlJdbXQN4BQPwwOCFzJCpVADoANunowCyALzLkARmQteA4CUxgSKMWQYAGJgG5+wAL58BumPpQByZ5Zs8gA
💻 Code
function setBet(chars:string[]):string{

	if( chars.length === 1 ){
		return chars[0];
	}
	return '';
}

🙁 Actual behavior
TS Error: "Type 'string | undefined' is not assignable to type 'string'."
🙂 Expected behavior
No error. Since the chars parameter is typed as string[], if chars.length === 1, then chars[0] won't be undefined

Duplicate of #38000.


Revampui

@duluca need help with the specific commands you want. I got the first one can you please send me the option and commands for the other options? I can do the necessary.

I say we stick to textual help for this release. I was pretty happy with
the mockup.
I think this is a rabbit hole to tackle later.
On Tue, Oct 15, 2019 at 8:04 PM Kenton Bocock<EMAIL_ADDRESS>wrote:

@duluca https://github.com/duluca need help with the specific commands
you want. I got the first one can you please send me the option and
commands for the other options? I can do the necessary.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/expertly-simple/angular-evergreen/pull/66?email_source=notifications&email_token=AAGIXDZC4HOZSOSOKI3C2H3QOZLCNA5CNFSM4JA7RAFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBKTA6Y#issuecomment-542453883,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGIXD33X3AGATSY7S37ZALQOZLCNANCNFSM4JA7RAFA
.

--
Doguhan Uluca

Text is problematic in the current ui, will need to consider loading a webview if we want richer text. For now going with 2 cli commands, update cli and core and all. Also re-org of structure in ui and removing all other problematic business logic.


Update Website with new Project Vision

Hi Folks,
The new project vision is excellent. I really like it.
We should update the project website with the vision.

I added this to the todo-- We'll try to get it done by alpha

ACK. Thanks


Add embed block

Source: https://github.com/hlxsites/eder-group/tree/3ea2c4c1fdccc1dc05fb71b903fada0563fc7929/blocks/embed
new file:   blocks/embed/embed-facebook.js
new file:   blocks/embed/embed-instagram.js
new file:   blocks/embed/embed-youtube-channel.js
new file:   blocks/embed/embed.css
new file:   blocks/embed/embed.js
Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #6-add-embed-block
Test URLs:

Before: https://main--fresenius--hlxsites.hlx.page/
After: https://6-issue-block-embed--fresenius--hlxsites.hlx.page/

Taking a look at the failed build.


fixed a few issues

Coverage increased (+0.1%) to 82.243% when pulling ac02b841b93b9830d67cc1f5231edefe03643064 on dev into 22d7681cd47124ec11367496197a1863352c7a80 on master.


pkg: cleanup some unused code

- What I did
removed some unused code from pkg
- How I did it
used https://github.com/dominikh/go-unused
- How to verify it
compile docker
- A picture of a cute animal (not mandatory but encouraged)

LGTM

LGTM


[jetson-nano-b01] eeprom_init: EEPROM read failed during Nano booting

Hey, I recently changed my A02 Nano to B01 with SD card and tried to run yocto on it (same that works great on A02).
I noticed that booting procedure takes a way longer that used to.
I connected UART to see full logs from booting and this is what I saw.
[0049.274] I2C write failed
[0049.277] Writing offset failed
[0049.280] eeprom_init: EEPROM read failed
[0049.284] pm_ids_update: eeprom init failed
[0049.288] pm_ids_update: Updating 3,a0, size 256, type 0
[0057.284] pm_ids_update: The pm board id is 3448-0000-400
[0057.291] Adding plugin-manager/ids/3448-0000-400=/i2c@7000c500:module@0x50
[0057.299] pm_ids_update: pm id update successful
[0057.303] pm_ids_update: Updating 3,ae, size 256, type 0
[0057.309] I2C slave not started
[0057.312] I2C write failed
[0057.314] Writing offset failed
[0057.317] eeprom_init: EEPROM read failed
[0057.321] pm_ids_update: eeprom init failed

It is only the part of this log. This eeprom_init: EEPROM read failed occurs 6 times, every 8 seconds and then system start properly.

Hi @przemyslaw-chwiala
I have the Jetson Nano B01 (SDcard), I'm using this repo tegra-demo-distro with dunfell-l4t-r32.4.3 branch. It works fine for me.
I had had the same message as you in the Cboot stage, It happen three time but this is not a blocker for me. the device continue to boot successfully.
Could you please provide more detail on what you have done (build, flash, ...) ? Are you sure that you are using the Nano B01 ?
attached the complete logs from the serial UART.
jetson_nano_sdcard_serial_uart.log

Hi @ichergui,
thank you for your answer.
I'm sure I'm using B01, same soft on A02 works fine. I'm attaching full log from my booting.
I'm working on zeus branch. Could update to dunfell help? There are any additional steps required to switch from A02 to B01?
nano_emmc_error.log

Could you please try with same the repo and the branch that I shared ?
Here is the steps:
$ git clone https://github.com/OE4T/tegra-demo-distro.git
$ git checkout origin/dunfell-l4t-r32.4.3 -b dunfell-l4t-r32.4.3
$ git submodule update --init
$ unset NVIDIA_DEVNET_MIRROR
$ export NVIDIA_DEVNET_MIRROR="/path/to/jetpack_4.4/nvidia/sdkm_downloads"
$ . ./setup-env --machine jetson-nano-qspi-sd --distro tegrademo-mender build-distro
$ bitbake demo-image-base

Note: Please take a look here for SDcard flashing
Please let me know if you need help.

@przemyslaw-chwiala From the log you attached, it looks like you're using a branch based off L4T R32.2.2, is that right? If so, try @ichergui's suggestion, or at least try a build using a branch based off L4T R32.2.3 or later.  IIRC, Nano rev B01 support was introduced in 32.2.3.

Hi @przemyslaw-chwiala
Did you try with the release L4T R32.4.3 ?
Could you please give us updates about your issue ?

I assume you resolved this issue, since it's been a few months. Closing.


Name-spaces are duplicated in certain cases

Sometimes a name-space object is "shared", that is, the same name-space is added to different contexts (units or other name-spaces). This causes such name-spaces and their contents to be duplicated in the generated code making it invalid. It has so far been hit with Mapnik (mentioned at https://github.com/mono/CppSharp/issues/664).
Note: this is not necessarily a bug in the parser, that is, it might be valid behaviour in terms of a C++. However, in this case the bug is in our object model and it would have to be taught to deal with it.

This occurs with Qt# too. In our AST, the translation unit for locale_classes.h contains an std name-space which has the same declarations as the std name-space contained in locale_classes.tcc (both are in include/c++/bits) even though the headers are different.

Exporting a system template in our tests:
/template class DLL_API std::basic_string;
causes the STD name-space to be added to the parent. This might as well be the same bug which would mean we can reproduce it.


marginHorizontal should override marginLeft, marginRight, etc.

Description
If a component is styled with something like:
paragraph: {
  marginLeft: 100,
  marginRight: 100
}

It will not be able to be overridden later by something like:
paragraph: {
  marginHorizontal: 0
}

Which is not the desired behavior.
Reproduction Steps
See the sample code.
Sample Code
https://snack.expo.io/rkVGFONQW
Solution
In CSS, something like:
element: {
  margin-left: 100px,
  marign-right: 100px,
  margin: 0
}

Would result in a 0 margin. The styling in React Native should follow it to make for a more consistent styling experience.
Additional Information

React Native version: 0.44.3
Platform: iOS
Development Operating System: macOS
Build tools: Xcode / Expo 17.0.0

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.


Type signature errors with bootstrapModule() - documentation refers to out of date bootstrapApplication()

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[x] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior
The current documentation demonstrates package setup using bootstrapApplication(...).
Expected behavior
The documentation demonstrates package setup using the default platformBrowserDynamic().bootstrapModule(...) code generated in a new Angular 15+ project.
Minimal reproduction of the problem with instructions
Create a new angular app using ng cli 15+ to see a main.ts along the lines of:
if (environment.production) {
  enableProdMode();
}

platformBrowserDynamic()
  .bootstrapModule(AppModule)
  .catch((err) => console.error(err));

What is the motivation / use case for changing the behavior?
Type signature errors prevent the use of svg-icon with bootstrapModule.

Environment
Angular core: ^15.2.9

Works for me


ARROW-71: [C++] Add clang-tidy and clang-format to the the tool chain.

I changed the ubuntu flavor for building to precise because https://github.com/travis-ci/apt-source-whitelist/issues/199 is currently blocking using trusty.
I also expect there might be a couple of iterations on settings for clang-format and clang-tidy (or if we even want them as standard parts of the toolchain).  @wesm I noticed the lint target explicitly turns off some checks, I don't know if these were copy and pasted or you really don't like them.  If the latter I can do a first pass of turning the same ones off for clang-tidy.
In terms of reviewing: It is likely useful, to look at the PR commit by commit, since the last two commits are 99% driven by the first commit.   The main chunk of code that wasn't machine fixed is FatalLog in logging.
The good news is clang-tidy caught one potential corner case segfault when a column happened to be null :)

This seems good to me. If you're satisfied, will merge and we'll run with this?

@emkornfield according to Travis CI, they aren't in any hurry to whitelist the LLVM apt repos, but because we have sudo on the trusty platform, we can apt-add-repository and do whatever we want. So it should be possible to go back to Trusty and use LLVM 3.8 if we wish


Added some Translated Actions. (Spanish)

Please check that the file structure is correct!

looks good now!


modem: hl7800: only send null packet for TCP

Only TCP sockets should send a NULL packet
if the server closes the connection or there
is a socket error.
UDP sockets do not need to do this because
they are connectionless.
fixes #40107

@jukkar This PR change relates to this comment: https://github.com/zephyrproject-rtos/zephyr/blob/f86f6e00251066815b0a7a7ad45047b525b3fab9/drivers/modem/hl7800.c#L3562
During my testing I found this was necessary to let an app know the socket closed or there was an error. With all my testing this seems to be a correct implementation, but would like to get confirmation from you since you know the networking stack far better than myself.

Codecov Report

Merging #42469 (f86f6e0) into main (f86f6e0) will not change coverage.
The diff coverage is n/a.

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

@@           Coverage Diff           @@
##             main   #42469   +/-   ##
=======================================
  Coverage   50.09%   50.09%
=======================================
  Files         631      631
  Lines       77507    77507
  Branches    18095    18095
=======================================
  Hits        38830    38830
  Misses      32250    32250
  Partials     6427     6427

Continue to review full report at Codecov.

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


[5.1] Allow chunk to exit when the closure returns false

When looping through all of the different rows returned by Eloquent\Builder using a chunk closure, you should be able to specify to Builder that you wish to no longer continue processing chunks by simply returning false inside the closure.
Usage Example
  ExamplesModel::where('is_an_example', true)
        ->chunk(5000, function($urls) use (&$post, &$loop, $time_queries, $time_started) {

            foreach($urls as $url) {
                Lengthy::process($url->path, $url->filename);

                // only allow to run for 20 seconds...
                if ($time_started+20 > microtime(true)) {
                    return false;
                }
            }

        })

Can you include tests please.

I wrote some tests for it.

See https://github.com/laravel/framework/pull/11624.


Variables in import paths are not resolved

What happened?
If I use a variable in the path for imports, it is not resolved. I tried replacing it with a command variable too but it did not work.
What did you expect to happen instead?
I expect the variable to resolve correctly
How can we reproduce the bug? (as minimally and precisely as possible)
My devspace.yaml:
version: v2beta1
name: myapp
imports:
  - path: $(echo "${MY_CONF_DIR}/common")

On running devspace print
fatal read import config: open /path/to/dir/$(echo "${MY_CONF_DIR}/common")/devspace.yaml: no such file or directory

Local Environment:

DevSpace Version: 6.0.0-beta.10
Operating System: mac
ARCH of the OS: ARM64
Kubernetes Cluster:
Cloud Provider: k3s
Kubernetes Version: 1.22.5

Anything else we need to know?

/kind bug

@dhruvbaldawa thanks for creating this issue! Yes that is currently intended as variables are resolved after imports are applied. The only place where variables can be used is imports.*.enabled right now.


User activity endpoint

Feature Description
Well, I'm doing a project where I'm using the gitea api to get the user data for my application. I would like to know if any endpoint exists or is in development that allows us to capture all user activity, eg commit, push, pull, as well as the image above.
I want to bring the data to do something very similar to the one below

Would have this api to bring all the commits of each user?
Screenshots
No response

Could you use the user feed?
e.g. https://try.gitea.io/arandomer.rss

Good idea @zeripath, thanks. but would it be the best way to get this data?

https://APP_URL/username.rss or https://APP_URL/username.atom ?

I managed to implement @zeripath , thanks. a question, this way it only brings us the activities of the public repositories, would it be possible to get the private ones too?


[BUG] - Web Api Template scaffolding error in VS 2022 Community on Latest .NET SDK

Create web api project from scaffolding vanilla template error in VS 2022
Area/Component:
Web Api Stateless Project
To Reproduce
Attempt to create new project from vanilla template of VS 2022 Community with Latest .NET SDK in Windows 11
Expected behavior
Able to successfully create stateless web api project
Observed  behavior:
Screenshots

Service Fabric Runtime Version:

Environment:

Dev cluster
OS: Windows 11 Professional Latest

Additional context
NA

Assignees: /cc @microsoft/service-fabric-triage

I found a workaround. create the project in VS 2019 and then dev through VS 2022

My workaround was to create as a .net 5 project, then upgrading to 6/7.

@ralav sorry for the delay in this being looked into. Unfortunatly this was not brough to my attention till over the weekend (I work on the relevant VS tools). For a quicker response in the future i recommend using the "Report a Propblem" feature in VS as that usually gets to the correct team faster:

I'm testing a fix for you issue, and it should be available in the 17.5 timeframe. In the meantime, an additional workaround to retargeting from .NET 5 is to uncheck "Do not use top-level statements" when making a .NET 6/7 web project:

Out template's code does not handle this new option (yet)

My workaround was to create as a .net 5 project, then upgrading to 6/7.

Never ever do manual efforts around this, as sometimes we will end up in loosing enhanced or ignored.

@ralav sorry for the delay in this being looked into. Unfortunatly this was not brough to my attention till over the weekend (I work on the relevant VS tools). For a quicker response in the future i recommend using the "Report a Propblem" feature in VS as that usually gets to the correct team faster:

I'm testing a fix for you issue, and it should be available in the 17.5 timeframe. In the meantime, an additional workaround to retargeting from .NET 5 is to uncheck "Do not use top-level statements" when making a .NET 6/7 web project:

Out template's code does not handle this new option (yet)

Thanks for the suggestion and regarding workaround I feel not okay. It's fine being package issue but expecting redundant.

A fix for this is available in Visual Studio 2022 17.5 Preview 2


Add back Tika component

It could close

#4470
#3599

@jamesnetherton It seems the maven connection timeout happens again and again. I just find

https://github.com/actions/runner-images/issues/1499
and mentioned a work around to add
-Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.httpconnectionManager.ttlSeconds=120.

How do you think about it?

How do you think about it?

We can add it to CQ_MAVEN_ARGS in each of our workflow YAML files.


Target sensor that spans midnight

Is there a way of setting up a intermittent target sensor to get the cheapest 4 hours from 22:00 to 08:00
I can’t use reoccurring evaluation as the window moves and I only need to charge the house batteries for one 8 x 30 min period.
what would be ideal Would be to evaluate at 22:00 the best slots out of the available rates all the way up until 08:00 the next day.
hope this makes sense?
Dave

Apologies - misunderstood the documentation


add support for template literals

Not sure what you mean; can you eleaborate. This is already in the package.

@gandm should it work like this?

Looks as though you are using a Monokai based theme? The theme determines the colours displayed and Monokai just shows  template strings with embedded vars as yellow. See https://github.com/kevinsawicki/monokai/issues/67
e.g.
Monokai

Atom Dark

Visual Studio Dark

I'll close. Open again if you feel the need,


Add nested HyperV storage perf test against Azure and HyperV

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: xian123 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@xian123 Thank you for your contribution. Before going through PR code, can I see your execution logs please? You can send it to<EMAIL_ADDRESS>

@xian123  please resolve the conflict for ready-to-merge.

Conflicts resolved @juhlee-microsoft Thanks for review.

@xian123  the conflict is not resolved properly, you're including bunch of commits in this PR

suggest to close this one, make a clean branch, and create a new PR

I follow @lizzha advice to close it and create a new PR based on the master.


Make DatabaseGeneratedOption.Identity attribute just set ValueGenerated to OnAdd on SQL Server

This will go in 1.1.1
Part of #7010

@ajcvickers Could you take a look?

@smitpatel Could you take a look since @ajcvickers is OOF?


Z order null to 0

This is more of a discussion as opposed to an issue.
If we interleave bits, 0 will be always be at the top (so to speak). In your code, you convert nulls to 0.

Why push nulls to the top?
Why not val nullValue: Int = math.pow(2, 31) - 1?

Take for example telco data. We will have server hostname and domain name. These columns are used a lot in query where statements. However, the server hostname (where I used to work), would contain a lot of nulls. In a day, we have 10 billion plus records. Stacking all the nulls in the front for interleave wouldn't be ideal (or help with query performance since we are usually looking for non-null entries for some sort of analysis). Instead we pushed them to back for Z ordering (on premise cluster and this wasn't open sourced until a few days ago).
Is there any reason to convert nulls to 0 during Z ordering or was this just a quick idea to overcome null values?

Hi @dwsmith1983, thanks for the question. There is no particular reason why we map null to 0. Currently the Z-Order used Spark's RangePartitioner to map the Z-Order column to a range id (code is here). The mapping of null to 0 is inherited from the Spark's range partitioner.
For the performance, AFAIK it doesn't matter if we put nulls first or last. Z-Order rewrites the data by ordering the data using Z-order value and splitting the data into multiple files. The column stats from the rewritten file are used in skipping reading the file. So it doesn't matter if the nulls are at the end of Z-order curve or beginning. Let me know if I am missing anything here.

@vkorukanti sorry for the slow response. According to DB blog Processing Petabytes of data, data skipping isn't 100% efficient and declines over each column in the z ordering. Of course, the fall isn't as bad as linear ordering. Given this, there would still be inefficients in stacking nulls in the beginning when encounter. If they were all at the back, when searching, we would experience the efficiency loss still but wouldn't be encounter excess nulls to parse through.

Hi @dwsmith1983 - following up on this.
It would be helpful to make this discussion explicit. Can you share a small example of today's behavior (data, z-order command, resulting file layout/distribution) and how an alternate NULL treatment would change the behavior/perf? There's a target size conf for OPTIMIZE ZORDER that can help us work through the problem on a much smaller set of data:
spark.conf.set(DeltaSQLConf.DELTA_OPTIMIZE_MAX_FILE_SIZE.key, 1024*10)

This setting above, for example, would make the max file size ~1kb.

@nkarpov do you have a link to so some sample data to use?

Is it possible to generate a candidate set that has the NULL distribution you want to address?
The example below will be 50% NULLs in 1 file before the zorder command, and 5 active files (with null distribution visible in the addfile stats) afterward.
val data = (0 to 9999 by 2).toSeq.map(x=>(x, x))
val nulls = (1 to 9999 by 2).toSeq.map((_, null))
val df = data.toDF("id","data").union(nulls.toDF("id","data"))
df.repartition(1).write.format("delta").saveAsTable("test")

spark.conf.set(DeltaSQLConf.DELTA_OPTIMIZE_MAX_FILE_SIZE.key, 1024*10)

DeltaTable.forName(spark, "test").optimize().executeZOrderBy("id","data")

{"add":{"path":"part-00000-4767d446-3090-403e-97c1-47e0de33bc53-c000.snappy.parquet","partitionValues":{},"size":11337,"modificationTime":1661364725114,"dataChange":false,"stats":"{\"numRecords\":1969,\"minValues\":{\"id\":0,\"data\":0},\"maxValues\":{\"id\":2559,\"data\":1378},\"nullCount\":{\"id\":0,\"data\":1280}}"}}
{"add":{"path":"part-00001-56016bdb-f27b-4990-b949-a6fccbe5630a-c000.snappy.parquet","partitionValues":{},"size":12388,"modificationTime":1661364725161,"dataChange":false,"stats":"{\"numRecords\":2099,\"minValues\":{\"id\":1370,\"data\":1370},\"maxValues\":{\"id\":5119,\"data\":3018},\"nullCount\":{\"id\":0,\"data\":1280}}"}}
{"add":{"path":"part-00002-81040826-957f-462e-82f6-5075a94f4ebc-c000.snappy.parquet","partitionValues":{},"size":11788,"modificationTime":1661364725226,"dataChange":false,"stats":"{\"numRecords\":1718,\"minValues\":{\"id\":3010,\"data\":3010},\"maxValues\":{\"id\":6455,\"data\":5118},\"nullCount\":{\"id\":0,\"data\":666}}"}}
{"add":{"path":"part-00003-d19d297d-22db-4232-8d8d-239a41563052-c000.snappy.parquet","partitionValues":{},"size":10996,"modificationTime":1661364725272,"dataChange":false,"stats":"{\"numRecords\":2172,\"minValues\":{\"id\":5120,\"data\":5120},\"maxValues\":{\"id\":9999,\"data\":5916},\"nullCount\":{\"id\":0,\"data\":1774}}"}}
{"add":{"path":"part-00004-e0b0bfb2-d6eb-432d-9b20-896f75c9f791-c000.snappy.parquet","partitionValues":{},"size":17048,"modificationTime":1661364725308,"dataChange":false,"stats":"{\"numRecords\":2042,\"minValues\":{\"id\":5910,\"data\":5910},\"maxValues\":{\"id\":9998,\"data\":9998},\"nullCount\":{\"id\":0,\"data\":0}}"}}
{"remove":{"path":"part-00000-2f6df9ec-6997-4095-841b-1a383f25003f-c000.snappy.parquet","deletionTimestamp":1661364724009,"dataChange":false,"extendedFileMetadata":true,"partitionValues":{},"size":60729}}
{"commitInfo":{"timestamp":1661364725317,"operation":"OPTIMIZE","operationParameters":{"predicate":"[]","zOrderBy":"[\"id\",\"data\"]"},"readVersion":0,"isolationLevel":"SnapshotIsolation","isBlindAppend":false,"operationMetrics":{"numRemovedFiles":"1","numRemovedBytes":"60729","p25FileSize":"11337","minFileSize":"10996","numAddedFiles":"5","maxFileSize":"17048","p75FileSize":"12388","p50FileSize":"11788","numAddedBytes":"63557"},"engineInfo":"Apache-Spark/3.2.0 Delta-Lake/2.0.0","txnId":"f5f62ac5-e308-4ee9-ac14-3c68a5414924"}}


feat: Bicep Module for Bing Resource

Description

If you haven't already, read the full contribution guide. The guide may have changed since the last time you read it, so please double-check.
Enable GitHub Worksflows in your fork to enable auto-generation of assets with our GitHub Action.
To trigger GitHub Actions after auto-generation, add a GitHub PAT as a secret in your forked repository called PAT.
Adding a new module

[x] A proposal has been submitted and approved.
[x] I have included "Closes #{module_proposal_issue_number}" in the PR description.
[x] I have run brm validate locally to verify the module files.
[x] I have run deployment tests locally to ensure the module is deployable.

Updating an existing module

[ ] This is a bug fix:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] I have run brm validate locally to verify the module files.
[ ] I have run deployment tests locally to ensure the module is deployable.
[ ] I have read the Updating an existing module section in the contributing guide and updated the version.json file properly:

[ ] The PR contains backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json.
[ ] The PR contains backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] The PR contains breaking changes, and I have bumped the MAJOR version in version.json.

[ ] I have updated the examples in README with the latest module version number.

@dciborow  @shenglol  Can we please register the subscription for Microsoft.Bing ?

@dciborow @shenglol Please help to review

/azp run

Bing Search is no longer part of Cognitive Services since October 2020. I wonder if we should use ai/bing-search as the module path.

@shenglol  i have updated the path . Thanks


fix: cross workflow triggering

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


Fixed URL to ASP.NET Core WebListener

Right link https://docs.asp.net/en/latest/fundamentals/servers.html#weblistener

Hi @wagsousa, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@wagsousa - Hi, thanks for your contribution. We are in the process of refactoring the Azure technical articles, so we can’t merge this PR. When the refactoring is complete, we can give you a link to the new location of the article you updated so you can resubmit your update, if you want to.

@wagsousa - Thanks for your contribution to the Azure docs. On November 16th, we announced the availability of our Azure technical documentation in a new location on docs.microsoft.com. You can read about it on our team blog. This change means the article source lives in a new GitHub repository. Because there are some changes in the source markdown as a result of the move, we can’t pull your contribution over to the new repo without creating a ton of merge conflicts. We invite you to resubmit the change (if you are willing) to the new version of the article at https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-reverseproxy. Thanks for your understanding.


[python] Create an interface file

It would be nice to have a .pyi integrated to the python package that would expose the types for IDEs auto-completion and type checkers.

Agreed! Can you please contribute one, @cbornet?

Why not. But I'm not a typing expert...

Let's give it a try 🤗


The overall status will be shown for kubectl get kfservice

/kind feature
Describe the solution you'd like
While I'm doing the #305 , I think the overall status will be shown for kubectl get kfservice. User want to know if the KFService is ready or not.
For now:
(python36) [root@jinchi1 kfserving]# kubectl get kfservice
NAME             URL                                          DEFAULT TRAFFIC   CANARY TRAFFIC   AGE
flowers-sample   http://flowers-sample.kubeflow.example.com                                      23m

Should be like below I think (added READY):
(python36) [root@jinchi1 kfserving]# kubectl get kfservice
NAME            READY   URL                                          DEFAULT TRAFFIC   CANARY TRAFFIC   AGE
flowers-sample  True       http://flowers-sample.kubeflow.example.com                                      23m

Checked the knative, there is a READY,  I suggest we add one metric READY for kfservice.
kubectl get knative
......
NAME                           SERVICE NAME                   GENERATION   READY     REASON
flowers-sample-canary-mbcjq    flowers-sample-canary-mbcjq    1            True
flowers-sample-default-zmfbh   flowers-sample-default-zmfbh   1            True
helloworld-go-5bs95            helloworld-go-5bs95            2            True

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

@ellis-bigelow @yuzisun comments? Thanks.

@jinchihe good suggestion! Can you try add this annotation +kubebuilder:printcolumn:name="Ready",type="string",JSONPath=".status.conditions[?(@.type=='Ready')].status" to KFService type see if that works?

@jinchihe good suggestion! Can you try add this annotation +kubebuilder:printcolumn:name="Ready",type="string",JSONPath=".status.conditions[?(@.type=='Ready')].status" to KFService type see if that works?

@yuzisun OK, thanks, I'm going to do that :-)
/assign @jinchihe


Use Debian version bullseye-slim

What & Why
To reduce the size of the container we want to use Debian bullseye-slim.

👍 Does this work without any other changes ?

Yes


ADS-1129 added temp template and drop down to select

Added examples to template selection

@RYyusuf @ncollinsRY @ScottInglis Please review the changes so I can merge.  Thanks!


LoudnessEqualizer.json for macOS

Hello,
A thousand thanks to you for sharing this.
After having used this for a while, I can say with certainty that I now prefer Linux just because the madness of loudness is properly tamed only with your preset.
Loudness Equalization on Windows is increasingly gone/unavailable.
SoundSource from RogueAmoeba isn't cutting it for me.
Is there a way to faithfully reproduce this in macOS with SoundSource and Apple's default Audio Units?
If not, with good & cost-effective AUs, without spending too much time on the setup itself?
Thanks again!

Hello @v1gnesh

Loudness Equalization on Windows is increasingly gone/unavailable.

Really? Why? Is this only on Win 11? I'm pretty sure it's available on 10.

Is there a way to faithfully reproduce this in macOS with SoundSource and Apple's default Audio Units? If not, with good & cost-effective AUs, without spending too much time on the setup itself?

I think it's reproducible. In the last weeks I ported the last Calf preset to LSP (because of the Gate migration in EasyEffects). Now all the plugins are provided by Linux Studio Plugins and since they support the LV2 format, it's only a matter of finding a software on Mac compatible with LV2.
I reproduced it on Carla in my Linux system (I also made a specific preset, you can download it). It is available also for Mac as it's reported in the download section.
Try it on Mac. It should install a suite with various executable, you need to start the one named carla-rack and load the plugin inside (just load the carla preset you can download from here).

Oh, I just forgot to say that Linux Studio Plugins should be installed on Mac. I don't know if this is possible. There should be a way.

I took a look at it and there's no LSP build for Mac unfortunately. It seems Calf is available but it misses the Upward Compressor.
Look if there are similar LV2 plugins on Mac. You could add them in Carla Rack and try to reproduce the pipeline of the current Loudness Equalizer. The parameters would not be the same, but at least you could test them.
You need a Gate, an Upward Compressor, a Downward Multiband Compressor (4 bands are enough), an Equalizer (at least 10 bands with Bell filter) and a Limiter.
If you can install Calf, it provides everything except the Upward Compressor.

I'm using Carla with Calf, like you said there's no upward compressor, but after long play with this I made my own 'version' of it. Nothing wrong with LSP, I tried to make it right but in the end Calf won, I don't know if that's because I'm using 5.1 surround speakers, but the default preset wasn't quite right, for my taste and setup. Anyway, everything is basically the same but some parameters are adjusted. I didn't touch the settings for I don't know how long now, more than a month for sure, and I was really testing it thoroughly, with very low and high volume files, also it was very rare, found that only in two materials that I've tried, there were distortions in couple of places, which I was able to eliminate with Calf, I'm sure I could do that as well with LSP, but leveling the sound volume (to my liking) I wasn't able to do with LSP, I don't know. Anyhow, if needed I can upload the Carla preset.

Really? Why? Is this only on Win 11? I'm pretty sure it's available on 10.

The sound enhancements tab doesn't show up on all Windows installs.
With conference calls and all, it is tiring to not have LEq adjusting levels automatically.
https://www.thewindowsclub.com/loudness-equalization-missing-in-windows-10

Anyhow, if needed I can upload the Carla preset.

Please do, thank you!

This is the one I use, it's for 5.1 speakers, so basically you have 3 instances running, they are all the same, except rear speakers, they are little louder and front-center is little quieter, I don't use 'speaker fill' so only 5.1 material is played via all speakers, and stereo is played via front left and right.
For stereo you would use this one, I just removed the other two instances and left only one (front left and right), which I use for playing stereo.

@TheMainMMan I'm happy for you that you found the right preset with Calf, anyway I think the Gate is useless in that configuration. I added it only because the Upward Compressor could increase noise. In your preset there's nothing increasing the signal, so you could just remove it.
@v1gnesh It's unfortunate LSP is not available on Mac. I'm pretty sure there's something available on Mac having all you need, but it would be not free. It's hard to find on Google, but there are several audio suites on Mac that you can buy. From my point of view, there's no point in spending money if there's something free on Linux, but if you really need Mac, you could try a paid option if the price is reasonable.
The only free alternative containing an upward compressor seems to be Xfer Record OTT: https://xferrecords.com/freeware
But I don't know if it contains other plugins like Gate and Limiter. You could give it a try.

@Digitalone1 thanks for the tip, yeah I don't see a difference with or w/o Gate, but it doesn't tax cpu or something so I just left it, plus I'm not that advanced in all of this, really started looking into it recently when I found your preset, honestly I understand just the compressor part and what it does, other stuff not so much. Maybe the GUI part of Calf suits me better, so I was able to get better results with it, it's simpler than LSP.

There is FabFilter, but it's not hobbyist-priced at all.

Do you have any experience with the plugins/extensions that come with Reaper?

No, sorry, never used it.

Okay, another question -
Say I plug the 3.5mm out from a Windows machine or a TV into another PC's line in.
Can I use this same LoudnessEq plugin to process that audio, to get adjusted audio out of the linux box?
3.5mm jack of Windows workstation / HDMI out of TV -->
Line In or Mic (which should I use?) of Linux workstation running EasyEffects -->
Line Out from Linux PC to speakers.

@v1gnesh This is more of a question to ask in EasyEffects issue page.
I never handled this kind of configurations and, to be honest, never played with the input pipeline (I rarely use the mic on my system).
Anyway, the question is another. Why do you need Mac? Linux is more tricky, I know, but if you pick the right distribution, there should be no big issues. If it's for Amazon Prime not being available in 1080p on Linux, there are alternatives running the browser on Wine or using a Virtual Machine with a Windows image.

I have a mini for its portability really. Waiting for Asahi to become usable.
If there was a mini PC that's somewhat as good as the mini is currently, I'd have chosen that.

I have a mini for its portability really. Waiting for Asahi to become usable. If there was a mini PC that's somewhat as good as the mini is currently, I'd have chosen that.

If you can acquire the audio source from the Mac, you can use EasyEffects and output the result. The question is how to do it. I never did. If you want, try to make the same question here. Maybe someone could help you.

Another idea that I had just a couple of minutes ago. Running Linux in a virtual machine on Mac so you could try to run EasyEffects there? The question is if the source in Mac is exposed inside the virtual machine to be handled by EasyEffects.


Feature/pr 522 teaarte feature 519 on slide click

Deployed to https://beghp.github.io/gh-pages-rc-9Fixes #519 - [x] an issue linked to the PR

I checked this PR resolves the problem and doesn't break anything (desktop).
Video: https://recordit.co/1rwmXQ3YAk


[Backport 7.60.x] [EBPF] attacher: Fix cleanup of uprobes (#31419)

(cherry picked from commit c45797dc794766d4bbddf89181cc6cd3322e751d)

What does this PR do?
Backports #31419 to 7.60.x
Motivation
Avoid issues with uprobe cleanup on other users of the uprobe attacher. Related to incident 32654.
Describe how to test/QA your changes
Tested in staging to validate that the issue was resolved, and added extra unit tests to ensure correct behavior.
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Can I get the image Dominant color before its 'Downloaded from URL'

Hello Developer,
Really nice library may say appreciate your work on the algorithm implemented.
I have a query like google Image in Iphone is you Check , if you scroll very fast for the search images grid, the first time you see a background of the most dominent color and then the actual image.
I want to implement the same behaviour, hence Can you please recommend if this can be done in this library or any reference.
I dont want to download an image of 3MB then show the dominent color for the second and then actual image rather it should show the dominent color while loading and then the actual image.
Can you advice.

Hi there - really hard to understand that text, but I think I got it.
There is no way that you can compute a dominant color before you have the image. The color is computed based on the colors in the image.
If you somehow can download a much smaller version of the image beforehand, that would help. The average color of the smaller image (50x50 for example) would be very close to the actual one in the big image. Downscaling images before running the algorithm is in general idea a good idea. Not only for performance reasons, but also because of the aggregating nature of downscaling, which already does part of the summation step.


Relative references from a file in a sub-folder to other folders do not resolve

Originally from swagger-codegen https://github.com/swagger-api/swagger-codegen/issues/3614
If you have a directory structure like
swagger.yaml
-folder1
 -file1.yaml
 -folder2
  -file2.yaml
-folder3
 -file3.yaml

then from file1.yaml it is unable to resolve references to file3.yaml or file2.yaml.
For the case in which file1 references file2, the exception thrown is:
Exception in thread "main" java.lang.RuntimeException: Unable to load RELATIVE ref: ../folder2/file2.yaml
        at io.swagger.parser.util.RefUtils.readExternalRef(RefUtils.java:140)
        at io.swagger.parser.ResolverCache.loadRef(ResolverCache.java:96)
        at io.swagger.parser.processors.ExternalRefProcessor.processRefToExternalDefinition(ExternalRefProcessor.java:30)
        at io.swagger.parser.processors.ExternalRefProcessor.processRefToExternalDefinition(ExternalRefProcessor.java:69)
        at io.swagger.parser.processors.PropertyProcessor.processRefProperty(PropertyProcessor.java:33)
        at io.swagger.parser.processors.PropertyProcessor.processProperty(PropertyProcessor.java:21)
        at io.swagger.parser.processors.PropertyProcessor.processObjectProperty(PropertyProcessor.java:59)
        at io.swagger.parser.processors.PropertyProcessor.processProperty(PropertyProcessor.java:27)
        at io.swagger.parser.processors.ResponseProcessor.processResponse(ResponseProcessor.java:21)
        at io.swagger.parser.processors.OperationProcessor.processOperation(OperationProcessor.java:45)
        at io.swagger.parser.processors.PathsProcessor.processPaths(PathsProcessor.java:89)
        at io.swagger.parser.SwaggerResolver.resolve(SwaggerResolver.java:40)
        at io.swagger.parser.SwaggerParser.read(SwaggerParser.java:66)
        at io.swagger.codegen.config.CodegenConfigurator.toClientOptInput(CodegenConfigurator.java:390)
        at io.swagger.codegen.cmd.Generate.run(Generate.java:221)
        at io.swagger.codegen.SwaggerCodegen.main(SwaggerCodegen.java:36)
Caused by: java.lang.RuntimeException: Could not find ../folder2/file2.yaml on the classpath
        at io.swagger.parser.util.ClasspathHelper.loadFileFromClasspath(ClasspathHelper.java:31)
        at io.swagger.parser.util.RefUtils.readExternalRef(RefUtils.java:135)
        ... 15 more

I created a suite of tests that I believe illustrate the problem, and attached it swagger-relative-file-references.zip.
The test cases that compare "./file1.yaml" vs "file.yaml" can likely be ignored, I created them for my own education to verify which formats of a relative reference were acceptable.

Thank you for submitting this.  Are you testing with master or the latest release?

In the future, consider sending a PR with failing tests.  Then we're all testing the same thing.  But since you did organize your tests, here is my test feedback:

[X] Case 1 Passes with existing master
[X] Case 2 Passes with #307
[ ] Case 3
[ ] Case 4
[ ] Case 5
[ ] Case 6
[ ] Case 7
[ ] Case 8
[ ] Case 9
[ ] Case 10
[ ] Case 11

@fehguy These cases were tested with release 2.2.1 of swagger-codegen. I've also tested with a more recent master version, 4f9ee0f93de77c9d31acf73ef60a0ee2c5f9872f to be specific, and the same behaviour occurs.
I was planning on making a PR soon, but I haven't written Java in several years so I have a bit of ramping up to do =)

This was tested with the latest release, 2.2.1. I can re-run the test cases
with master tomorrow but from my initial testing with master last week the
same issues were occurring.
On Oct 24, 2016 8:04 PM, "Tony Tam"<EMAIL_ADDRESS>wrote:

Thank you for submitting this. Are you testing with master or the latest
release?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/swagger-api/swagger-parser/issues/305#issuecomment-255900030,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJqVOVTFdfiFSBixoD3tQKPDnhWL1iAAks5q3UeDgaJpZM4KfH3N
.

So thank you for getting these tests in.  It was a long time coming, and I've gone through and carefully recreated your scenarios.  This will go in the next parser release, then into codegen.


Log levels of minor errors during import

GraphHopper does currently write a messages to the log during the import which could be moved to a less important log level:

2019-05-07 13:39:16,623 [main] WARN  com.graphhopper.reader.osm.OSMReader - Parsing error in way with OSMID=529711482 : Cannot parse duration tag value: 2,5 Horas

I don't think that errors in OSM tags should trigger a warning. There are so many tagging mistakes and typos in OSM. Is there any reason why exactly these are shown or is this just a inconsistency within GraphHopper? I propose to move this warning to the debug log level.

2019-05-07 13:33:43,638 [main] INFO  com.graphhopper.search.NameIndex - Way name is too long: Колыма — Омсукчан — Омолон — Анадырь на территории Чукотского автономного округа. Участок Омолон — Анадырь с подъездами до Билибино, Комсомольского, Эгвекинота, 77К-022 truncated to Колыма — Омсукчан — Омолон — Анадырь на территории Чукотского ав

I propose to move this message to the debug log level as well.

Probably we can do this.
But the name log message is something which is a limitation of our data storage that has a strict length limit and we cut the string. Although they are official names according to comments here: https://www.openstreetmap.org/user/karussell/diary/26055

How about moving the warnings to INFO?
Personally, I find it helpful that GraphHopper logs OSM tagging issues by default. In the long term, this might improve the quality of OSM data. For example the duration is something that one could easily fix in OSM.

How about moving the warnings to INFO?

My main goal is to lower the log level. I find debug better for such messages because you won't look at it if you "just set up a GraphHopper for someone" but if you handle support complaints.

Personally, I find it helpful that GraphHopper logs OSM tagging issues by default. In the long term, this might improve the quality of OSM data.

I remember Mkgmap logging multipolygon errors but I doubt that it helps. IMHO, it is more helpful to implement validation rules in a validation platform like OSM Inspector or Osmose.