remove unused metric

Clean up unused metric and evaluate trace sampling in features
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[X] Does not have any changes that may affect Istio users.

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
8daee597f5a7bb6dd6259f74b6cecc18346682d5
link
/test integ-telemetry-mc-k8s-tests_istio

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

/test integ-telemetry-mc-k8s-tests_istio


Make bottom bar persistent

I want to add BottomBar persistent to every page while navigation to sub child or any page. Is it possible to add bottom bar persistent to every page? I am using GetX for navigation from one page to other.

@ptesting007, it is difficult for me to understand what you want based on your comment. Can you please provide a design or diagram of what you are trying to achieve?

Closing this issue for now. Please reopen it with more details if needed.


Cleanup

autoformatting
flake8 issues resolved
many mypy issues resolved

For reference (seeing from your commit history), you can run make check or pre-commit run --all-files to run the same checks that are performed by github actions :)
I usually pipe them into a file and just have that open in the editor.
$ pre-commit run --all-files > out.txt

The full spec can be found here.
In general, there's two main parts, the software part and the preffered_citation part which is more likely towards the paper authors. There's an example of it here for autosklearn.

In general, in code authors is towards people who developed the code, for paper refrences, you can use githubs Citation.cff.
An example of one is here for autosklearn, where the main section is for software and then there preffered_citation part is for the paper. When you use the cite this repository feature on the right, it will use the preffered_citation part in which you can include an accompanying paper.
The full spec is here if you need the reference :)


Enviro AQI Score

Hello,
I am working on an integration with Home Assistant.
I am struggling with how I can produce an AQI score using MQTT.
The read out I am getting back is when listening to the MQTT messages are
{
"pressure": 955.76,
"temperature": 21.1,
"timestamp": "2024-03-01 10:54:17",
"color_temperature": 3468,
"device": "office",
"humidity": 55.09,
"luminance": 97
}
Its now showing even showing the Gas reading. Is there something I am missing?
Thanks

You might want to check that your device has been flashed with the latest firmware,
only versions after Version 0.0.7 have the calculated gas resistance & AQI

Thanks will have a check.


How to use [Line/Sphere/etc]Trace

I can't seem to find a way to use tracing from within python.
Basic sample of what I'm trying to achieve is an equivalent of this:

If this isn't yet implemented, I'm willing to contribute, but could really use some pointers as to where is the best point to start.

Hi, you can call UFUNCTION's directly from python like described here:
https://github.com/20tab/UnrealEnginePython#the-automagic-uclass-ustruct-and-uenums-mappers
if you want the optimized tracing functions, they are exposed here:
https://github.com/20tab/UnrealEnginePython/blob/master/Source/UnrealEnginePython/Private/UObject/UEPyTraceAndSweep.cpp
feel free to add more functions


Request: Dynamic Updates

It seems that this extension sets the color when the page loads, but it would be nice if there were an option to have it dynamically update as the view updates. A good example of this is how macOS Safari 15 handles content changes.
To demonstrate, here is an example of Safari updating colors as a page changes compared to how this extension handles them using the website ippsec.rocks. On the initial page load, the page is a blue color which Adaptive-Tab-Bar-Color matches:

On this particular website, when you start typing in the main input, the page colors will change. Safari will dynamically change the tab bar color along with these changes, whereas Adaptive-Tab-Bar-Color keeps the original blue color from page load.
Safari:

Firefox:

Would it be possible to mirror this behaviour using this extension and Firefox? I understand that it may come with a performance overhead it is possible, but it could be an experimental feature with a warning for those who are interested in using it.

@aaronnoyes Thanks for your suggestion! Dynamic update should be very cool.

@aaronnoyes I have added some dynamic updates feature, but it still can’t work on the website you mentioned. The CSS animation (color transition) is making it difficult.

@YS-Wong it's working but you have to invoke an input update after typing something (press enter or mouse click on the colored bg)

@YS-Wong thank you so much for working on this!

Hello, I tried making the add-on update tab bar color multiple times with some intervals, which solved the problem but caused another bug: switching tab shortly after tab bar color update starts could result in color applied to a wrong tab. It’s because different scripts run in an unsynchronized manner, timing is quite tricky.
Please leave the issue open. Maybe I’ll figure it out one day. Have a good one :)

@aaronnoyes “Dynamic color update” got updated in latest release. Tab bar color will be refreshed after color transition. It’s still not perfect yet, so I might keep this issue opened.

@YS-Wong Thanks for keeping me updated and for your work!

Dynamic colour update doesn’t properly work for me on all websites, unfortunately. An example is this website, you can change the theme by clicking on the cogwheel near the search bar. Another example is my website alpha.
For the record, on my website, the theme changes when the attribute color-scheme on the body tag changes, as seen in this file (and I just noticed the extensions picks a green colour instead of the correct background colour). I don’t know how the first website manages its own colour schemes, though.

Please disregard my previous comment, I just noticed the dynamic colour update is an option that has to be checked. Once I enabled it, it indeed works correctly. Maybe it could be made opt-out instead of opt-in?

@Phundrak Regarding the latter website, you can open the add-on popup and click “Ignore theme color”. The add-on picked a green color because the website has defined its “theme color” in its HTML <meta name="theme-color" content="#61972e">.

That’s indeed it, thanks for the help!

@Phundrak No worries. As the add-on gets more and more functions, maybe I shall make a small wiki/document.

Although the “Dynamic Update” function will still be improved over time, this is not an “issue” any more.


[plugin] HAWK authentication

https://github.com/hueniverse/hawk
http://blog.getpostman.com/2015/12/05/postman-v3-2-is-out-with-hawk-authentication-support/

+1 on this request


make check - Easy-RSA error

$ /usr/share/easy-rsa/easyrsa --help
Easy-RSA 3 usage and overview
...
$ make check
...
Making check in test
make[1]: Entering directory '/tmp/mycms/test'
Making check in ca
make[2]: Entering directory '/tmp/mycms/test/ca'
make  check-local
make[3]: Entering directory '/tmp/mycms/test/ca'
rm -f built.rootca init-pki
/usr/share/easy-rsa/easyrsa --vars="./rootca.vars" init-pki
Easy-RSA error:
Use of '--vars=FILE init-pki' is prohibited, use '--pki-dir=DIR'
Host: nix | Linux | /bin/bash
make[3]: *** [Makefile:506: built.rootca] Error 1
make[3]: Leaving directory '/tmp/mycms/test/ca'
make[2]: *** [Makefile:374: check-am] Error 2
make[2]: Leaving directory '/tmp/mycms/test/ca'
make[1]: *** [Makefile:381: check-recursive] Error 1
make[1]: Leaving directory '/tmp/mycms/test'
make: *** [Makefile:566: check-recursive] Error 1

This is probably an old ubuntu, you use some fake easy-rsa (pkitool)
instead of the real one.

Oh... so patches are welcomed :)
On Wed, May 24, 2023 at 8:34 PM gilweis @.***> wrote:

I'm using new Ubuntu:
Ubuntu 23.04
—
Reply to this email directly, view it on GitHub
https://github.com/alonbl/mycms/issues/5#issuecomment-1561673820, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJURLMXJQKL5ASXJHWDRTLXHZBC7ANCNFSM6AAAAAAYNTVXJ4
.
You are receiving this because you commented.Message ID:
@.***>

$ apt search easy-rsa
easy-rsa/lunar,lunar,now 3.1.0-0.2 all [installed]
Simple shell based CA utility

You should check what changed in version 3.1 compared to 3.0 and how to
workaround so that tests support both.
On Wed, May 24, 2023 at 8:38 PM gilweis @.***> wrote:

$ apt search easy-rsa
easy-rsa/lunar,lunar,now 3.1.0-0.2 all [installed]
Simple shell based CA utility
—
Reply to this email directly, view it on GitHub
https://github.com/alonbl/mycms/issues/5#issuecomment-1561678904, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJURLP6KPXCBGIVXTARB53XHZBSNANCNFSM6AAAAAAYNTVXJ4
.
You are receiving this because you commented.Message ID:
@.***>

see [1]
[1] https://github.com/OpenVPN/easy-rsa/commit/48f7ed5f103689f6a3d8c5ee05d14ea58e3dd743

Fixed in 9f498dc0bb197b812a16d3cc5a25452a6df21f0f


cdc: collect slow table latency metrics

What problem does this PR solve?

Issue Number: ref #4757
What is changed and how it works?
Collect slow table latency metrics.
Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
No.
Do you need to update user documentation, design documentation or monitoring documentation?
No.
Release note
None

Codecov Report

Merging #7323 (5b94b5b) into master (8f81dbb) will decrease coverage by 5.5490%.
The diff coverage is 48.6111%.

Additional details and impacted files

Flag
Coverage Δ

cdc
?

dm
51.9313% <36.6666%> (-0.0228%)
:arrow_down:

engine
61.0887% <57.1428%> (+0.0158%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #7323        +/-   ##
================================================
- Coverage   59.7265%   54.1774%   -5.5491%
================================================
  Files           790        419       -371
  Lines         91204      52723     -38481
================================================
- Hits          54473      28564     -25909
+ Misses        31987      21422     -10565
+ Partials       4744       2737      -2007

/merge

/run-verify

/verify

/run-verify


Karpenter cannot create new nodes on v1 Policy

Description
When updating the module from 20.17.2 to 20.24.0 (terraform 1.9.5, aws provider 5.64.0 ) and setting enable_v1_permissions = true i get the below plan:
# module.k8s.module.karpenter.aws_iam_policy.controller[0] will be updated in-place
  ~ resource "aws_iam_policy" "controller" {
        id               = "arn:aws:iam::******:policy/KarpenterController-2024022809571951390000000f"
        name             = "KarpenterController-2024022809571951390000000f"
      ~ policy           = jsonencode(
          ~ {
              ~ Statement = [
                  ~ {
                      ~ Resource = [
                          - "arn:aws:ec2:*::snapshot/*",
                          - "arn:aws:ec2:*::image/*",
                          - "arn:aws:ec2:*:*:subnet/*",
                          - "arn:aws:ec2:*:*:spot-instances-request/*",
                          - "arn:aws:ec2:*:*:security-group/*",
                          - "arn:aws:ec2:*:*:launch-template/*",
                          + "arn:aws:ec2:eu-west-1::snapshot/*",
                          + "arn:aws:ec2:eu-west-1::image/*",
                          + "arn:aws:ec2:eu-west-1:*:subnet/*",
                          + "arn:aws:ec2:eu-west-1:*:security-group/*",
                        ]
                      ~ Sid      = "AllowScopedEC2InstanceActions" -> "AllowScopedEC2InstanceAccessActions"
                        # (2 unchanged attributes hidden)
                    },
                  ~ {
                      ~ Action    = [
                            "ec2:RunInstances",
                          - "ec2:CreateLaunchTemplate",
                            "ec2:CreateFleet",
                        ]
                      ~ Condition = {
                          ~ StringEquals = {
                              - "aws:RequestTag/kubernetes.io/cluster/******"  = "owned"
                              + "aws:ResourceTag/kubernetes.io/cluster/******" = "owned"
                            }
                          ~ StringLike   = {
                              - "aws:RequestTag/karpenter.sh/nodepool"  = "*"
                              + "aws:ResourceTag/karpenter.sh/nodepool" = "*"
                            }
                        }
                      ~ Resource  = [
                          - "arn:aws:ec2:*:*:volume/*",
                          - "arn:aws:ec2:*:*:spot-instances-request/*",
                          - "arn:aws:ec2:*:*:network-interface/*",
                          - "arn:aws:ec2:*:*:launch-template/*",
                          - "arn:aws:ec2:*:*:instance/*",
                          - "arn:aws:ec2:*:*:fleet/*",
                        ] -> "arn:aws:ec2:eu-west-1:*:launch-template/*"
                      ~ Sid       = "AllowScopedEC2InstanceActionsWithTags" -> "AllowScopedEC2LaunchTemplateAccessActions"
                        # (1 unchanged attribute hidden)
                    },
                  ~ {
                      ~ Action    = "ec2:CreateTags" -> [
                          + "ec2:RunInstances",
                          + "ec2:CreateLaunchTemplate",
                          + "ec2:CreateFleet",
                        ]
                      ~ Condition = {
                          ~ StringEquals = {
                              + "aws:RequestTag/eks:eks-cluster-name"                         = "******"
                              - "ec2:CreateAction"                                            = [
                                  - "RunInstances",
                                  - "CreateFleet",
                                  - "CreateLaunchTemplate",
                                ]
                                # (1 unchanged attribute hidden)
                            }
                            # (1 unchanged attribute hidden)
                        }
                      ~ Resource  = [
                          ~ "arn:aws:ec2:*:*:volume/*" -> "arn:aws:ec2:eu-west-1:*:volume/*",
                          ~ "arn:aws:ec2:*:*:spot-instances-request/*" -> "arn:aws:ec2:eu-west-1:*:spot-instances-request/*",
                          ~ "arn:aws:ec2:*:*:network-interface/*" -> "arn:aws:ec2:eu-west-1:*:network-interface/*",
                          ~ "arn:aws:ec2:*:*:launch-template/*" -> "arn:aws:ec2:eu-west-1:*:launch-template/*",
                          ~ "arn:aws:ec2:*:*:instance/*" -> "arn:aws:ec2:eu-west-1:*:instance/*",
                          ~ "arn:aws:ec2:*:*:fleet/*" -> "arn:aws:ec2:eu-west-1:*:fleet/*",
                        ]
                      ~ Sid       = "AllowScopedResourceCreationTagging" -> "AllowScopedEC2InstanceActionsWithTags"
                        # (1 unchanged attribute hidden)
                    },
                  ~ {
                      ~ Condition = {
                          - "ForAllValues:StringEquals" = {
                              - "aws:TagKeys" = [
                                  - "karpenter.sh/nodeclaim",
                                  - "Name",
                                ]
                            }
                          ~ StringEquals                = {
                              + "aws:RequestTag/eks:eks-cluster-name"                          = "******"
                              + "aws:RequestTag/kubernetes.io/cluster/******"  = "owned"
                              - "aws:ResourceTag/kubernetes.io/cluster/******" = "owned"
                              + "ec2:CreateAction"                                             = [
                                  + "RunInstances",
                                  + "CreateFleet",
                                  + "CreateLaunchTemplate",
                                ]
                            }
                          ~ StringLike                  = {
                              + "aws:RequestTag/karpenter.sh/nodepool"  = "*"
                              - "aws:ResourceTag/karpenter.sh/nodepool" = "*"
                            }
                        }
                      ~ Resource  = "arn:aws:ec2:*:*:instance/*" -> [
                          + "arn:aws:ec2:eu-west-1:*:volume/*",
                          + "arn:aws:ec2:eu-west-1:*:spot-instances-request/*",
                          + "arn:aws:ec2:eu-west-1:*:network-interface/*",
                          + "arn:aws:ec2:eu-west-1:*:launch-template/*",
                          + "arn:aws:ec2:eu-west-1:*:instance/*",
                          + "arn:aws:ec2:eu-west-1:*:fleet/*",
                        ]
                      ~ Sid       = "AllowScopedResourceTagging" -> "AllowScopedResourceCreationTagging"
                        # (2 unchanged attributes hidden)
                    },
                  ~ {
                      ~ Action    = [
                          - "ec2:TerminateInstances",
                          - "ec2:DeleteLaunchTemplate",
                        ] -> "ec2:CreateTags"
                      ~ Condition = {
                          + "ForAllValues:StringEquals" = {
                              + "aws:TagKeys" = [
                                  + "eks:eks-cluster-name",
                                  + "karpenter.sh/nodeclaim",
                                  + "Name",
                                ]
                            }
                          + StringEqualsIfExists        = {
                              + "aws:RequestTag/eks:eks-cluster-name" = "****"
                            }
                            # (2 unchanged attributes hidden)
                        }
                      ~ Resource  = [
                          - "arn:aws:ec2:*:*:launch-template/*",
                          - "arn:aws:ec2:*:*:instance/*",
                        ] -> "arn:aws:ec2:eu-west-1:*:instance/*"
                      ~ Sid       = "AllowScopedDeletion" -> "AllowScopedResourceTagging"
                        # (1 unchanged attribute hidden)
                    },
                  + {
                      + Action    = [
                          + "ec2:TerminateInstances",
                          + "ec2:DeleteLaunchTemplate",
                        ]
                      + Condition = {
                          + StringEquals = {
                              + "aws:ResourceTag/kubernetes.io/cluster/******" = "owned"
                            }
                          + StringLike   = {
                              + "aws:ResourceTag/karpenter.sh/nodepool" = "*"
                            }
                        }
                      + Effect    = "Allow"
                      + Resource  = [
                          + "arn:aws:ec2:eu-west-1:*:launch-template/*",
                          + "arn:aws:ec2:eu-west-1:*:instance/*",
                        ]
                      + Sid       = "AllowScopedDeletion"
                    },
                    {
                        Action    = [
                            "ec2:DescribeSubnets",
                            "ec2:DescribeSpotPriceHistory",
                            "ec2:DescribeSecurityGroups",
                            "ec2:DescribeLaunchTemplates",
                            "ec2:DescribeInstances",
                            "ec2:DescribeInstanceTypes",
                            "ec2:DescribeInstanceTypeOfferings",
                            "ec2:DescribeImages",
                            "ec2:DescribeAvailabilityZones",
                        ]
                        Condition = {
                            StringEquals = {
                                "aws:RequestedRegion" = "eu-west-1"
                            }
                        }
                        Effect    = "Allow"
                        Resource  = "*"
                        Sid       = "AllowRegionalReadActions"
                    },
                    # (1 unchanged element hidden)
                    {
                        Action   = "pricing:GetProducts"
                        Effect   = "Allow"
                        Resource = "*"
                        Sid      = "AllowPricingReadActions"
                    },
                  ~ {
                      ~ Action   = [
                            # (1 unchanged element hidden)
                            "sqs:GetQueueUrl",
                          - "sqs:GetQueueAttributes",
                            "sqs:DeleteMessage",
                        ]
                        # (3 unchanged attributes hidden)
                    },
                    {
                        Action    = "iam:PassRole"
                        Condition = {
                            StringEquals = {
                                "iam:PassedToService" = "ec2.amazonaws.com"
                            }
                        }
                        Effect    = "Allow"
                        Resource  = "arn:aws:iam::******::role/*****"
                        Sid       = "AllowPassingInstanceRole"
                    },
                  ~ {
                      ~ Condition = {
                          ~ StringEquals = {
                              + "aws:RequestTag/eks:eks-cluster-name"                         = "******"
                                # (2 unchanged attributes hidden)
                            }
                            # (1 unchanged attribute hidden)
                        }
                      ~ Resource  = "*" -> "arn:aws:iam::******::instance-profile/*"
                        # (3 unchanged attributes hidden)
                    },
                  ~ {
                      ~ Condition = {
                          ~ StringEquals = {
                              + "aws:RequestTag/eks:eks-cluster-name"                          = "****"
                              + "aws:RequestTag/topology.kubernetes.io/region"                 = "eu-west-1"
                                # (3 unchanged attributes hidden)
                            }
                            # (1 unchanged attribute hidden)
                        }
                      ~ Resource  = "*" -> "arn:aws:iam::******::instance-profile/*"
                        # (3 unchanged attributes hidden)
                    },
                  ~ {
                      ~ Resource  = "*" -> "arn:aws:iam::******::instance-profile/*"
                        # (4 unchanged attributes hidden)
                    },
                  ~ {
                      ~ Resource = "*" -> "arn:aws:iam::******:instance-profile/*"
                        # (3 unchanged attributes hidden)
                    },
                    {
                        Action   = "eks:DescribeCluster"
                        Effect   = "Allow"
                        Resource = "arn:aws:eks:************"
                        Sid      = "AllowAPIServerEndpointDiscovery"
                    },
                ]
                # (1 unchanged attribute hidden)
            }
        )
        tags             = {
            "Environment" = "revproxy"
            "ManagedBy"   = "Terraform"
            "Team"        = "devops"
        }
        # (7 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

After apply and  updating Karpenter to v1.0.2 it cannot spawn nodes from NodeClaims, this is the error on the NodeClaim resource :
message: >-
        creating instance, getting launch template configs, getting launch
        templates, creating launch template, UnauthorizedOperation: You are not
        authorized to perform this operation. User:
        arn:aws:sts::756979186773:assumed-role/tf-eks-devops-revproxy-karpenter-controller/1726052365915287551
        is not authori...

Rollback to Karpenter 0.37.2 and non v1 policy works ( still on 20.24.0 module version , just setting enable_v1_permissions = false
Did i miss anything ?
Thanks,
Adrian

@adrianmiron Attaching my plan after enabling v1 policy flag
plan.txt
I think this is what does the trick:
                          ~ StringEquals = {
                              - "aws:RequestTag/kubernetes.io/cluster/mgmt"  = "owned"
                              + "aws:ResourceTag/kubernetes.io/cluster/mgmt" = "owned"
                            }
                          ~ StringLike   = {
                              - "aws:RequestTag/karpenter.sh/nodepool"  = "*"
                              + "aws:ResourceTag/karpenter.sh/nodepool" = "*"
                            }

the change from RequestTag to ResourceTag

Yeah, i had to edit quite a few Condition blocks for it to be able to spawn nodes.... But it is still unable to properly delete 0.37.2 nodeclaims because even though 1.X should support both crd types... it does not here. The NodeCLaim is seen an invalid so it cannot even delete it.... I will push this back a few months, 0.37.2 is good enough for now

Hi @bryantbiggs, this is not really a question but a blocking issue which is preventing us from updating Karpenter from v0.37 to v1.

Hi @bryantbiggs, this is not really a question but a blocking issue which is preventing us from updating Karpenter from v0.37 to v1.

While i agree it's blocking, the root causes lies with Karpenter and we need an update there.

Hello, @adrianmiron ,
I agree with you since the v1 policy in the module is perfectly aligned with the one of the v1 migration guide of Karpenter. So the issue is coming from Karpenter.
Could you please give the full error message you are receiving from the controller on the Unauthorized error I would like to see if you have the same error as I do.
Thank you,

It seems the latest version bumps ( 0.37.5 and 1.0.6 ) generate no more erros during the upgrade, not related to the policy anyway ( just be sure to enable the webhooks on 0.37.5 )

I activated the webhook since 0.37.0. Our issue is not related to the policy directly indeed: However we implemented an explicit deny of the creation of public IPs on our AWS accounts and the karpenter controller even though creating nodes on subnets without the auto assign public IPV4 enabled receive an explicit deny like if it was trying to create a public IP on a network interface ... / this is fixed by explicitly defining associatePublicIPAddress to false  but it is not the expected behavior for me.
We mentioned this here: https://github.com/aws/karpenter-provider-aws/issues/6847#issuecomment-2395991560

I activated the webhook since 0.37.0. Our issue is not related to the policy directly indeed: However we implemented an explicit deny of the creation of public IPs on our AWS accounts and the karpenter controller even though creating nodes on subnets without the auto assign public IPV4 enabled receive an explicit deny like if it was trying to create a public IP on a network interface ... / this is fixed by explicitly defining associatePublicIPAddress to false but it is not the expected behavior IMO.
We mentioned this here: aws/karpenter-provider-aws#6847 (comment)

Weird....it must perform a check or something because it does not create a public IP for our nodes ( with them being in private subnets )

Yes that is really weird .... 0.37.5 was not causing this and the policy from my reading is definitely not the issue.
Could you setup a an explicit deny to try to reproduce the error on your side is it too risky ?

I have the same issue, any recommendation, how it can be done?


Sony Alpha 7 II support?

Using Sony Alpha 7 II:
Firmeware (2.0?) and Smart-Remote 4.10 (Updated today). I get:
"Remote request failed" (Locana <IP_ADDRESS>) when i start the app (app detects the WLAN from the camera). Any hints? Thanks

Thank you for the report.
Could you also check with Locana Windows 10 beta v2.0.15?

We can invite you as a beta tester of Windows 10 version if you your phone is running Windows 10.

With <IP_ADDRESS> everything works perfect!!!! Thanks a lot!!! Perfect work!!!

No problem.
Thank you for the report again.


review Lookup Implementations to make it more flexible

Removing RandomLookIp
DefaultLookUp should not use Optional as part of the map definition.
Simplify the logic to use Multiple sources for the value, Classes or Type, Supplier and Function.
Implement a extendible solution for new ways to generate values.


Add an option to disable the creation of the forward index for a column

This PR adds an option to disable the forward index for a given column via the FieldConfig properties list. This is a PR to solve issue https://github.com/apache/pinot/issues/6473.
If the forward index is disabled, only a subset of queries can work. Basically queries that don't need to select, transform, group by, order by but do need to use the column in WHERE clauses can be supported.
To disable the forward index, the following mandates have been added at the moment (depending on the usage of this feature we may decide to relax some of them over time):

The inverted index for the column must be enabled

We require this to add functionality on the reload path to regenerate the forward index in case users decide later that they want a forward index

The column must be a dictionary based column

We require this to add functionality on the reload path to regenerate the forward index in case users decide later that they want a forward index

The column cannot have a V1 type range index present or be a multi-value columns with a range index present

V1 type range index resorts to full scans and needs the forward index to work properly
Multi-value columns always use the V1 type range index

The above checks have been added in the code in the following places:

TableConfig validator
Segment reload path (check when creating the default column)
Segment creation path

Sorted Column Handling:
For sorted columns we decided to allow someone to disable the forward index, but internally it's a no-op operation (we already create only a single index for sorted columns and use it for both forward and inverted index, we'll continue doing the same irrespective of the forwardIndexDisabled flag)
The ability to disable the forward index is currently implemented for the following cases:

New immutable segments generated for a column (all refresh use cases and reload use cases for new segments)

This PR does not add support for disabling the forward index for:

Mutable segments
Handling default and derived columns with the forward index disabled. We have decided to address default columns in the following way (derived still needs thought):

SV default columns should continue to create a sorted forward index (similar to the segment creation code path). We are okay with query inconsistency behavior for end users in this scenario.
MV default columns should not have a forward index but should have the inverted index + dictionary and any other indexes enabled during reload.

Enabling / disabling the disable forward index flag for an existing column -> we will add support for this reload case in a follow up PR shortly after this PR

Validations with other indices can be broadly classified into the following paths:

Query path - ensure that none of the other indices rely on the forward index

We found the range index v1 resorts to a scan on the forward index, thus disabled this feature if a range index of version 1 is present
Sorted columns rely on the forward index as the inverted index as well. We treat sorted column as a no-op when this feature is enabled (do not throw an error)

Segment creation path does not rely on the forward index to create other indices. The indexRow function creates all the indices needed at the same time for a given row.
Segment reload path relies on the forward index to add new indices such as range index, text index, etc. This path cannot be supported until we address enabling/disabling this feature on the reload path and will be done as part of a future PR along with any additional validations needed.

No-op creators have been added for the forward index disabled columns. This is useful for:

On the segment creation side, we can keep code clean and reuse the forward index creator map to walk through all the columns and create other indices

All code paths that need to read the forward index now have null checks added and appropriate exceptions thrown if the forward index doesn't exist.
cc @siddharthteotia @Jackie-Jiang

Codecov Report

Merging #9333 (f7b445c) into master (6047b06) will decrease coverage by 13.13%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master    #9333       +/-   ##
=============================================
- Coverage     28.37%   15.23%   -13.14%
- Complexity       53      168      +115
=============================================
  Files          1867     1826       -41
  Lines         99608    97801     -1807
  Branches      15167    15007      -160
=============================================
- Hits          28260    14899    -13361
- Misses        68608    81779    +13171
+ Partials       2740     1123     -1617

Flag
Coverage Δ

integration1
?

integration2
?

unittests2
15.23% <0.00%> (?)

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

 Learn more

We should allow disabling forward index for sorted column, which is a no-op because the inverted index for sorted column can be used as forward index. I believe it is already allowed in the implementation because the default column is always sorted. No need to add this in the validation.

We should allow disabling forward index for sorted column, which is a no-op because the inverted index for sorted column can be used as forward index. I believe it is already allowed in the implementation because the default column is always sorted. No need to add this in the validation.

Thanks for the suggestion @Jackie-Jiang. From going through the code it looks like for sorted columns the forward index and inverted index are essentially the same. Code snippet from the PhysicalColumnIndexCreator:
        // Single-value
        if (metadata.isSorted()) {
          // Sorted
          // forwardIndexDisabled columns do not need to be handled here as forward index cannot be disabled on a
          // sorted column
          SortedIndexReader<?> sortedIndexReader = indexReaderProvider.newSortedIndexReader(fwdIndexBuffer, metadata);
          _forwardIndex = sortedIndexReader;
          _invertedIndex = sortedIndexReader;
          _fstIndex = null;
          return;
        }

I also see code on the segment creation path where we skip creating the inverted index if the column is sorted even if the inverted index is enabled for the column. So keeping these in mind, we didn't think it made much sense to disable forward index for such columns.
Let me know your thoughts based on the above. cc @siddharthteotia

@somandal We want to disable the forward index to save the storage. For sorted index, we store the index in inverted format (map from dictId to doc range), and also use it as forward index. We should allow disabling the forward index for it in the table config, and simply ignore it when creating the index.

@somandal We want to disable the forward index to save the storage. For sorted index, we store the index in inverted format (map from dictId to doc range), and also use it as forward index. We should allow disabling the forward index for it in the table config, and simply ignore it when creating the index.

Thanks for discussing this, done!

@Jackie-Jiang @siddharthteotia @jackjlli I've updated the PR with the latest discussions. Let me know what you think! Thanks!

@siddharthteotia and @Jackie-Jiang can you folks take a look at this PR again? I've addressed the comments we discussed. I've left one test in the SegmentPreProcesserTest.java file as a disabled test since we'll be addressing the MV column forwardIndexDisabled flag part in Part 2 and I didn't want to rework that test.

All code paths that need to read the forward index now have null checks added and appropriate exceptions thrown if the forward index doesn't exist.

If the forward index is disabled, only a subset of queries can work. Basically queries that don't need to select, transform, group by, order by but do need to use the column in WHERE clauses can be supported.

Can we add compile time checks to catch and fail queries that would not work without forward index being present (or maybe this check was added somewhere and I missed it)? This would avoid wasting resources executing the queries that would fail during runtime due to forward index not being present.

All code paths that need to read the forward index now have null checks added and appropriate exceptions thrown if the forward index doesn't exist.

If the forward index is disabled, only a subset of queries can work. Basically queries that don't need to select, transform, group by, order by but do need to use the column in WHERE clauses can be supported.

Can we add compile time checks to catch and fail queries that would not work without forward index being present (or maybe this check was added somewhere and I missed it)? This would avoid wasting resources executing the queries that would fail during runtime due to forward index not being present.

We considered doing  some kind of static check like this on broker side or planning side but the checks were not straightforward. For e.g. there are many aggregation functions which will work when the forward index is disabled (min, max, some of the distinct count functions) and some which won't (sum, average, etc). We agreed that it's an acceptable tradeoff to fail early during planning for most cases by adding the forward index null checks instead. Few failure scenarios also depend on the existence of other indexes and we'd have to identify such scenarios during execution anyways.

Thanks for the contribution @somandal . Let's please also share the doc on follow-up changes like discussed in last meeting with OSS.


Import to Matrix Field

Hi Guys,
I'm working with your awesome plugin. I have a category containing a matrix field (one block type). The matrix field has a category and a text input field. Is it possible to import to matrix fields and category fields? Do you have an example of that?
Thanks!

There's currently no way to import Matrix fields. You can use any of the hooks (most likely modifyImportRow) to process Matrix data yourself (and if you find a good way, please submit a pull request). Categories are linked by refering to them as Headcategory/Subcategory/Subsubcategory if they're in a structure.


Incorporate pbcf improvements from gh-4587 to scipy.special

Incorporate the asymptotic expansion in gh-4587 into the scipy.special parabolic functions

Just passing by and thought I'd ping this before it gets lost in the mists of time.

@ewmoore Thoughts?

I've actually been working on this...


Assistance with Running DIS on NVIDIA RTX A5000 GPU

Hi DIS Project Team,
I am seeking assistance with running the DIS model on a GPU. I am currently using an NVIDIA RTX A5000 Laptop GPU with 16GB RAM. Following the instructions, I have set up a conda environment named 'pytorch18'. However, when I attempt to train the model with my batch of images using python train_valid_inference_main.py (modified for my data), I encounter a compatibility issue with my GPU and the PyTorch version. The exact error message is:
--- build model ---
/home/ml/anaconda3/envs/pytorch18/lib/python3.7/site-packages/torch/cuda/__init__.py:104: UserWarning:
NVIDIA RTX A5000 Laptop GPU with CUDA capability sm_86 is not compatible with the current PyTorch installation.
The current PyTorch install supports CUDA capabilities sm_37 sm_50 sm_60 sm_61 sm_70 sm_75 compute_37.
If you want to use the NVIDIA RTX A5000 Laptop GPU GPU with PyTorch, please check the instructions at https://pytorch.org/get-started/locally/
warnings.warn(incompatible_device_warn.format(device_name, capability, " ".join(arch_list), device_name))

Following a suggestion from this PyTorch forum thread, I updated my installation with
conda install pytorch torchvision torchaudio cudatoolkit=11.3 -c pytorch

Now,
print(torch.__version__)

displays 1.13.1, and
print(torch.cuda.is_available())

returns False.
As a result, the model starts training on the CPU, leaving the GPU idle and unused.
I am relatively new to the field of machine learning and have been unable to find a solution to make the model train using the GPU. If I cannot resolve this, the training process will take an excessively long time.
For additional context, here are the outputs of
nvidia-smi && nvcc -V

+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.129.03             Driver Version: 535.129.03   CUDA Version: 12.2     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA RTX A5000 Laptop GPU    On  | 00000000:01:00.0 Off |                  N/A |
| N/A   47C    P8              17W / 115W |     10MiB / 16384MiB |      0%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+

+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|    0   N/A  N/A      1816      G   /usr/lib/xorg/Xorg                            4MiB |
+---------------------------------------------------------------------------------------+

nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Fri_Nov__3_17:16:49_PDT_2023
Cuda compilation tools, release 12.3, V12.3.103
Build cuda_12.3.r12.3/compiler.33492891_0

I would appreciate any guidance or suggestions you can provide to resolve this issue and successfully run the model on my GPU.
Thank you for your time and assistance.

https://pytorch.org/ you can check the CUDA version (your current "cuda
version is 12.2" seems not compatible with the pytroch you've installed)
with different pytorch versions in pytorch's official website.
On Sun, Nov 19, 2023 at 12:10 AM Mateusz @.***> wrote:

Hi DIS Project Team,
I am seeking assistance with running the DIS model on a GPU. I am
currently using an NVIDIA RTX A5000 Laptop GPU with 16GB RAM. Following the
instructions, I have set up a conda environment named 'pytorch18'. However,
when I attempt to train the model with my batch of images using python
train_valid_inference_main.py (modified for my data), I encounter a
compatibility issue with my GPU and the PyTorch version. The exact error
message is:
--- build model ---/home/ml/anaconda3/envs/pytorch18/lib/python3.7/site-packages/torch/cuda/init.py:104: UserWarning: NVIDIA RTX A5000 Laptop GPU with CUDA capability sm_86 is not compatible with the current PyTorch installation.The current PyTorch install supports CUDA capabilities sm_37 sm_50 sm_60 sm_61 sm_70 sm_75 compute_37.If you want to use the NVIDIA RTX A5000 Laptop GPU GPU with PyTorch, please check the instructions at https://pytorch.org/get-started/locally/warnings.warn(incompatible_device_warn.format(device_name, capability, " ".join(arch_list), device_name))
Following a suggestion from this PyTorch forum thread
https://discuss.pytorch.org/t/nvidia-nvidia-rtx-a5000-with-cuda-capability-sm-86-is-not-compatible-with-the-current-pytorch-installation/150593,
I updated my installation with
conda install pytorch torchvision torchaudio cudatoolkit=11.3 -c pytorch
Now,
print(torch.version)
displays 1.13.1, and
print(torch.cuda.is_available())
returns False.
As a result, the model starts training on the CPU, leaving the GPU idle
and unused.
I am relatively new to the field of machine learning and have been unable
to find a solution to make the model train using the GPU. If I cannot
resolve this, the training process will take an excessively long time.
For additional context, here are the outputs of
nvidia-smi && nvcc -V
+---------------------------------------------------------------------------------------+| NVIDIA-SMI 535.129.03             Driver Version: 535.129.03   CUDA Version: 12.2     ||-----------------------------------------+----------------------+----------------------+| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC || Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. ||                                         |                      |               MIG M. |
|=========================================+======================+======================||   0  NVIDIA RTX A5000 Laptop GPU    On  | 00000000:01:00.0 Off |                  N/A || N/A   47C    P8              17W / 115W |     10MiB / 16384MiB |      0%      Default ||                                         |                      |                  N/A |+-----------------------------------------+----------------------+----------------------+
+---------------------------------------------------------------------------------------+| Processes:                                                                            ||  GPU   GI   CI        PID   Type   Process name                            GPU Memory ||        ID   ID                                                             Usage      |
|=======================================================================================||    0   N/A  N/A      1816      G   /usr/lib/xorg/Xorg                            4MiB |+---------------------------------------------------------------------------------------+
nvcc: NVIDIA (R) Cuda compiler driverCopyright (c) 2005-2023 NVIDIA CorporationBuilt on Fri_Nov__3_17:16:49_PDT_2023Cuda compilation tools, release 12.3, V12.3.103Build cuda_12.3.r12.3/compiler.33492891_0
I would appreciate any guidance or suggestions you can provide to resolve
this issue and successfully run the model on my GPU.
Thank you for your time and assistance.
—
Reply to this email directly, view it on GitHub
https://github.com/xuebinqin/DIS/issues/96, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADSGORK4SX5SESLQL4MCDLDYFG5GBAVCNFSM6AAAAAA7RR74VGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYDANZUGY4DANI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Xuebin Qin
PhD
Department of Computing Science
University of Alberta, Edmonton, AB, Canada
Homepage: https://xuebinqin.github.io/

Hey @xuebinqin,
Thank you for your guidance - I've successfully managed to get everything up and running as it should. Now, it's working like a fast train. I didn't use the provided conda environment from pytorch18.yml, as updating the libraries to the required versions was almost a nightmare. I constantly faced version conflicts, and the resolution process (finding the correct versions) took ages.
I created a clean conda environment and, looking at the library dependency list, installed each one starting with Python and PyTorch. Everything installed smoothly, and now the model is also processing via the GPU.
Thanks again for your help!


Sort same ranked items alphabetically

What:

Sort same ranked items alphabetically rather than by the index they were inputted.
Updated tests.
One new test.

Why:
Currently, if items are the same rank with the same key based index, the items are sorted based on their index in the starting input. This is fine in general but I believe it makes more sense to sort them alphabetically when they have the same ranking and also by length allowing the smaller words to float to the top and make filtering a progressive act.
Example:
search: 'ap'
input: ['wrapped','snap', 'pap']
old output: ['wrapped','snap', 'pap']
new output: ['pap', 'snap', 'wrapped']

How:
We can take advantage of the base String.prototype.localeCompare() to do a comparison while still accepting diacritics.

Checklist:

[ ] Documentation
[x] Tests
[x] Ready to be merged
[ ] Added myself to contributors table

Comments
This may need discussion and you may not like the approach or the idea at all, just let me know or if you find any issues.
Thanks!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[5.8] Add support for typed eager loads

This PR adds support for eagerly loading relations of morphed models, based on their type.
An example:

Comment has a morph relation to commentable to Video or Post
Post has a relation to User

With this PR, you can load all these specific relation via queries, instead of using loadMorph on collections (#23626). Here's what the above example would look like:
Comment::query()
    ->with(['commentable' => function (MorphTo $morphTo) {
        $morphTo->withMorph(Post::class, ['user']);
    }])
    ->get();

The advantage of using this approach compared to loadMorph, is that nested relations are supported when using with on the query builder.
This PR is in draft, because I've got two questions still:

I chose the name withMorph to be similar to loadMorph, though maybe someone has a better idea?
~Can someone point me into the right direction on how to test this. I'm getting these errors: Call to a member function connection() when running DatabaseEloquentMorphToTest on its own, so I'm unable to try things out myself right now.~ Edit: figured out the right place to test this.

Can you explain the code example? I can't understand what it is doing from just reading it. Also show the alternative syntax to accomplish this in current Laravel 5.8 without this PR.

Is it desirable to use the same syntax as loadMorph()?
Comment::query()
    ->with(['commentable' => function (MorphTo $morphTo) {
        $morphTo->withMorph([Post::class => ['user']]);
    }])
    ->get();

@staudenmeir Sounds like a good idea! I changed it accordingly

Please remove $modelClass from the PHPDoc.
We could rename the $with parameter to $relations to be consistent with loadMorph().
I think we should also support single relations like loadMorph() does:
Comment::query()
    ->with(['commentable' => function (MorphTo $morphTo) {
        $morphTo->withMorph([Post::class => 'user']);
    }])                                     ^^^^^^
    ->get();

@staudenmeir I added support for single relations: https://github.com/laravel/framework/pull/28647/commits/a6700e5b8325e6de10fc0637d774853b7cc997c9#diff-4c052acf0022213a4cc23f53ba42720eR123
$morphTo->withMorph([Post::class => 'user']);

This has been merged but looks like GitHub didn't mark it as merged because of draft status. Thanks for the contribution! Could you send a PR to the docs when you get a chance?

PS I renamed the method morphWith.

Thanks! I'll send a PR to the docs later this week

morphWithCount would be great to add to accompany this

@brendt @taylorotwell morphWithCount?

@taylorotwell the test should clarify things further:
    public function test_with_morph_loading()
    {
        $comments = Comment::query()
            ->with(['commentable' => function (MorphTo $morphTo) {
                $morphTo->withMorph(Post::class, ['user']);
            }])
            ->get();

        $this->assertTrue($comments[0]->relationLoaded('commentable'));
        $this->assertTrue($comments[0]->commentable->relationLoaded('user'));
        $this->assertTrue($comments[1]->relationLoaded('commentable'));
    }

This example says "load all polymorphic commentable relations, and IF the commentable is a Post, also load its user relation"
Right now, you can use loadMorph on EloquentCollection, but it cannot handle nested relations. Take the previous example, but with the Comment model also belonging to a Feed.
$feeds = Feed::query()
    ->whereUser($user)
    ->with('comments.commentable')
    ->get();

$feeds->loadMorph('comments.commentable', [ // Nested relations don't work here
    Post::class => 'user'
]);

You cannot use loadMorph to load the post's user relation, without looping over each feed item individually. This causes n+1 issues with large data sets.
That's the issue this PR solves, as you can load the above example like so:
$feeds = Feed::query()
    ->whereUser($user)
    ->with('comments.commentable', function (MorphTo $morphTo) {
        $morphTo->withMorph(Post::class, ['user']);
    })
    ->get();

Is there way to use it with nested relationships?


Use string_tree module in favor of deprecated string_builder module of Gleam

Since release 1.6.0 of Gleam, string_builder has been deprecated in favor of string_tree.
This PR:

introduces BREAKING CHANGES:

Reasoning is that matcha is feature complete and stable. Whoever depends on string_builder just sticks with the current version and does not upgrade to the next/latest versions including this change. Reduces maintenance overhead for deprecated functionality – for example, in the case of a command line option.

Version 1.0.0 doesn't sound too bad, does it? ;)
In case you agree, this might need to be documented in README.md (including version/release numbers)

Updates gleam dependency (gleam_stdlib from version 0.38.0 to 0.43.0)
Uses StringTree instead of StringBuilder types in Refactor to use string_tree module instead of deprecated string_builder module of gleam
Renames public instances of render_builder to render_tree

In case the "builder" naming pattern should be kept, this commit just needs to be reverted.

Renames private instances of render to tree

In case the "builder" naming pattern should be kept, this commit just needs to be reverted.

Updates links to lustre and nakai in README.md

nakai just released a new version, adding support for the gleam string_tree module but dropping support for the gleam string_builder module completely.
lustre has an open PR (by me) to add support for the gleam string_tree module in addition to the gleam string_builder module.

introduces minor gleam related improvements:

Formats gleam code
Reorders gleam imports
Ignores gleam build folder (git)

Going through the individual commits should make it easier for you to review all changes in digestible chunks.
All tests are passing. Generated gleam code by a "from source" build of this branch has been deployed by a few projects to production already. :)

Thank you very much for this. Looks great. I appreciate the clear commit separation for the different aspects of the change.
It looks like our CI hasn't been run for a while and needs updating so I'll push some commits to try to do that but otherwise it looks great and I'd be happy merge and I'm grateful for your efforts!

The further changes are presumably associated with newer versions of the rust toolchain and compiler warnings, etc.

You make a fair point about going 1.0. Let's see how this set of changes settles in and then we can go 1.0 (though I realise there is a risk I'll forget about it entirely!)

Thank you very much for this. Looks great. I appreciate the clear commit separation for the different aspects of the change.

Oh, awesome – didn't expect for this to get merged that quick. Happy to contribute whenever I can. And thank you, for creating this in the first place! :)

You make a fair point about going 1.0.  I see it from the perspective of communicating the breaking changes of a dependency, less than a set of features. SemVer is great for that. When upgrading matcha from version 0.*.* to 0.*.* I would just yolo it without thinking. Seeing the version increase from 0.*.* to 1.*.* I would definitely check out the changelog first in order to decide whether I want to spend the next couple of hours refactoring my codebase.
Even though off-topic in the context of this PR: is there a specific set of features that you would like to see for 1.0.0?

(though I realise there is a risk I'll forget about it entirely!)

Let me create an issue (https://github.com/michaeljones/matcha/issues/32) as a reminder and you decide whatever to do with it... ;)


wasp encodes element sections differently than binaryen [typed function references]

The example func_ref_o.wat:
(module
  (func (export "main") (result i32)
    (call_ref (i32.const 10)
              (ref.func $foo)
    )
  )
  (func $foo (param $x i32) (result i32)
    (i32.add (local.get $x)
             (i32.const 19))
  )
  (elem declare funcref (ref.func $foo))
)

wasp wat2wasm --enable-function-references:
Contents of section element:
0000025: 0107 7001 d201 0b                        ..p....

binaryen wasm-as --enable-reference-types:
Contents of section element:
0000025: 0103 0001 01                             .....

wasp encodes element section as vec(expr) and binaryen encodes it as vec(func_idx), according to the https://github.com/WebAssembly/function-references/blob/master/proposals/function-references/Overview.md there is no any evidence that vec(expr) should be used.
Is it a bug?

If someone can confirm, I can make a fix.

IIRC, they are both allowed and equivalent. Has that changed recently? I suppose it would be best for tools to choose the smaller size, where possible.


Malwares

January 2020
processhacker-2.39-setup.exe
Check with VirusTotal: 18 l 67
Portable or full version same. Don't like malware and don't like to hear "false positive".
So I will not use your malware stuff and find pity "software" like that on github

.

So I will not use your malware stuff

Where on that page does it say malware?

Its a bunch of engines I've never even heard of, and they are all directly targeting this from the looks of the definition. PUP definitions are just dumb, even Kaspersky says its not a virus

When I scan Microsoft, Apple, HP, IBM, etc. fies, VirusTotal is clean,
meaning 0 (zero).
See a file without this result is suspect and never trust it.
Hope you will change the manner you code and so later (soon) when we scan
your application VirusTotal gives zero.
But sure if you want to "win" all time, like a politician, just continue to
lie to yourself and to others and you will win all time.
On Sat, Jan 15, 2022 at 11:35 PM dmex @.***> wrote:

So I will not use your malware stuff
Where on that page does it say malware?
—
Reply to this email directly, view it on GitHub
https://github.com/processhacker/processhacker/issues/1095#issuecomment-1013809364,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASPW4ADEPNHADDNZLCKTJ2DUWJDIBANCNFSM5MBO2MGA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

When I scan Microsoft, Apple, HP, IBM, etc. fies, VirusTotal is clean,
meaning 0 (zero).
See a file without this result is suspect and never trust it.
Hope you will change the manner you code and so later (soon) when we scan
your application VirusTotal gives zero.
But sure if you want to "win" all time, like a politician, just continue to
lie to yourself and to others and you will win all time.
On Sun, Jan 16, 2022 at 3:01 AM Padmasambhava sambhava <
@.***> wrote:

When I scan Microsoft, Apple, HP, IBM, etc. fies, VirusTotal is clean,
meaning 0 (zero).
See a file without this result is suspect and never trust it.
Hope you will change the manner you code and so later (soon) when we scan
your application VirusTotal gives zero.
But sure if you want to "win" all time, like a politician, just continue
to lie to yourself and to others and you will win all time.
On Sat, Jan 15, 2022 at 11:35 PM dmex @.***> wrote:

So I will not use your malware stuff
Where on that page does it say malware?
—
Reply to this email directly, view it on GitHub
https://github.com/processhacker/processhacker/issues/1095#issuecomment-1013809364,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASPW4ADEPNHADDNZLCKTJ2DUWJDIBANCNFSM5MBO2MGA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

It is borderline impossible to have 0 detections in a open source program, even changing nothing and just recompiling the code can cause engines to flag it as malicious since they haven't seen the file before and know nothing about it, It is quite literally nothing about the code that is causing this. Its called a heuristic engine, its basically educated guesses. A PUP is a potentially unwanted program, its how anti-virus companies tell their users that they don't think they should have that program on their computer. There is nothing malicious in this code, if there was it would be triggering on way more than just some no-name engines.

The only reason big companies like IBM and Microsoft get away with having 0 of their files flagged in any engines is they have the money and the manpower to constantly get their files validated. Open source projects are for the most part crowd-funded 90% of the time, we don't have the time and certainly don't have the money to go to every av engine in the world and get them to validate our files

That's because kaspersky like some other anti viruses will flag programs such as process hacker as "Unwanted programs" because they contain the ability to do things that normal programs do not.
Unwanted program does not automatically mean something is a virus/malware.

When I scan Microsoft, Apple, HP, IBM, etc. fies, VirusTotal is clean, meaning 0 (zero). See a file without this result is suspect and never trust it. Hope you will change the manner you code and so later (soon) when we scan your application VirusTotal gives zero. But sure if you want to "win" all time, like a politician, just continue to lie to yourself and to others and you will win all time. On Sun, Jan 16, 2022 at 3:01 AM Padmasambhava sambhava < @.> wrote:
…
When I scan Microsoft, Apple, HP, IBM, etc. fies, VirusTotal is clean, meaning 0 (zero). See a file without this result is suspect and never trust it. Hope you will change the manner you code and so later (soon) when we scan your application VirusTotal gives zero. But sure if you want to "win" all time, like a politician, just continue to lie to yourself and to others and you will win all time. On Sat, Jan 15, 2022 at 11:35 PM dmex @.> wrote: > So I will not use your malware stuff > > Where on that page does it say malware? > > — > Reply to this email directly, view it on GitHub > <#1095 (comment)>, > or unsubscribe > https://github.com/notifications/unsubscribe-auth/ASPW4ADEPNHADDNZLCKTJ2DUWJDIBANCNFSM5MBO2MGA > . > Triage notifications on the go with GitHub Mobile for iOS > https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 > or Android > https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. > > You are receiving this because you authored the thread.Message ID: > @.***> >

this, gentlemen is precisely how the Dunning-Kruger effect looks like.

Pretty much

I guess we can close this ticket.

some other anti viruses will flag programs such as process hacker as "Unwanted programs" because they contain the ability to do things that normal programs do not.

@senator715
Why do you see PH not like a "normal program"? Is there some feature or something that makes it different?

Hello,
First off, I totally understand your opinion and I probably will do the same for any other programs I don't basically trust (that isn't the case for me with Process Hacker).
Process Hacker can be used to inject DLLs into programs, if you inject a malicious DLL with this tool, your computer can be infected easily, I guess that's why for some antiviruses it's called "RiskWare" or "Potential Unwanted Program" ("PUA").
Process Hacker also have some features for process analyzing, for getting the memory of a program for example, I guess that can be used to get a not encrypted password, token, or anything else from other running programs. So I guess that's why it can be detected for other antiviruses as a "process hack" program. For verifying that, you still can ask the support of some antiviruses.
After knowing that, I recommend you to personally analyze the open-source code and if you think it's good, build it on your own computer. It's totally okay if you don't have the time to do that and don't want to run that program, as I said, I probably will do the same as you for any other programs.
PS: I don't have a lot of experience in malware analyzing, sorry.
Best regards,

Hylted_

I just want to add that this threads title alone isnt assiting this project at all paired with the website for it (https://processhacker.sourceforge.io/  doesnt even utilize HTTPS. First site of 2022 for me to trigger HTTPS everywhere.
also, is sourceforge.net now mirroring to a .io  via IPFS retention now? if so, why would they, of all people not use HTTPS. Maybe its on  the subdomain/project to supply it but I dont know, I am not looking any further because this is too suspecious for a program i dont want/need.
someitmes, If it looks like a duck, walks like a duck and quacks like a duck.....(if not, its sitll an annoying duck)

https://processhacker.sourceforge.io/ doesnt even utilize HTTPS.

Completely nonsensical, objectively wrong statement on all aspects. The website currently runs with Let's encrypt

First site of 2022 for me to trigger HTTPS everywhere.

Interesting ... how would you even know that HTTPS everywhere appears to be "triggered"? Is there a dialog for each website it successfully executes redirects?

also, is sourceforge.net now mirroring to a .io via IPFS retention now?

how is this in any way connected to PH?

if so, why would they, of all people not use HTTPS. Maybe its on the subdomain/project to supply it but I dont know, I am not looking any further because this is too suspecious for a program i dont want/need.

how is this in any way connected to PH?

someitmes, If it looks like a duck, walks like a duck and quacks like a duck.....(if not, its sitll an annoying duck)

what are you on, mate?

if you inject a malicious DLL with this tool, your computer can be infected easily

thats like saying "if you eat a banana someone could kill you with weaponized bananas"

no proper revision control or actual release since  Mar 28, 2016 on github, 88 open issues, about to cross 1k total and yet you proritize flaming your shame tracker's comment section.
thank you for addressing the security web security, now maybe focus on your emotional one.

You realize that isnt the owner of the repo, right? If you have so many issues that you deem it necessary to hold over someones head, either help out or get out

🤣
Whats with all the weird, confused and intoxicated people spouting nonsensicam BS? Is that some sort of paid campaign?

Its called the internet, mine as well get used to it, it doesn't stop

yes i get that - but this particular thread appears to be an idiot-magnet; much more than most other threads ... maybe because of google keywords and whatnot

This thread has diverged way off topic. The topic has been answered. I am closing this.
Please review our code of conduct. We will begin policing this strictly moving forward.


Invalid Haddock syntax in hsdev-<IP_ADDRESS>

src/HsDev/Database/Update.hs:303:9:
    parse error on input ‘-- ^ Read data from cache
’

See http://hydra.cryp.to/build/502397/nixlog/2/raw for a complete build log.

Would you care to share the reason for suddenly closing this issue after 1 year of inactivity?

Sure
Log is no more accesible.
cabal haddock doesn't return any errors and docs seems to be ok (this doc is present on hackage)
If I misunderstood something, feel free to reopen issue and, if possible, provide additional info


Add support for specifying account aliases in the allowed_accounts stack definition property

Add support for specifying account aliases in the allowed_accounts stack definition property.

@patrobinson @orien I added a useful error message when the iam:ListAccountAliases permission is missing in 8a528b7.
Please have a look 😄 .


eosd http_plugin exits and hence clients cannot connect

After cloning and building the latest codebase, eosc fails to connect to eosd. Upon closer inspection see this in the log files:
2469400ms thread-0   http_plugin.cpp:132           plugin_startup       ] start processing http thread
2469400ms thread-0   http_plugin.cpp:174           plugin_startup       ] start listening for http requests
2469400ms thread-0   http_plugin.cpp:179           plugin_startup       ] http io service exit

ubuntu@ip-172-31-23-80:~/eos/build/programs/eosd$ ./eosd --genesis-json data-dir/genesis.json --access-control-allow-origin "*"
2469397ms thread-0   chain_plugin.cpp:80           plugin_initialize    ] initializing chain plugin
2469397ms thread-0   http_plugin.cpp:112           plugin_initialize    ] host: <IP_ADDRESS> port: 8888
2469397ms thread-0   http_plugin.cpp:115           plugin_initialize    ] configured http to listen on <IP_ADDRESS>:8888
2469397ms thread-0   http_plugin.cpp:120           plugin_initialize    ] configured http with access-control-allow-origin : *
2469397ms thread-0   net_plugin.cpp:963            plugin_initialize    ] Initialize net plugin
2469397ms thread-0   net_plugin.cpp:969            plugin_initialize    ] host: <IP_ADDRESS> port: 9876
2469399ms thread-0   block_log.cpp:88              open                 ] Opening block log at /home/ubuntu/eos/build/programs/eosd/data-dir/blocks/blocks.log
2469400ms thread-0   chain_plugin.cpp:166          plugin_startup       ] starting chain in read/write mode
2469400ms thread-0   chain_plugin.cpp:171          plugin_startup       ] Blockchain started; head block is #0, genesis timestamp is 2017-03-30T12:00:00
2469400ms thread-0   http_plugin.cpp:132           plugin_startup       ] start processing http thread
2469400ms thread-0   http_plugin.cpp:174           plugin_startup       ] start listening for http requests
2469400ms thread-0   http_plugin.cpp:179           plugin_startup       ] http io service exit
2469400ms thread-0   net_plugin.cpp:1032           operator()           ] caught signal 0

If I launch eosd from launcher it works. It did not work when I launched eosd as ./eosd

Attached are the config.ini and genesis.json files.

No issues. The problem was that  chain_api_plugin was not enabled. Please ignore.


Parser error for channel named Channel

A channel named Channel leads to an parser error. The error only occurs for this exact keyword, i.e., there is no error for channel. Is there a good reason for that?
package Test is

   generic
      Channel : Channel with Readable, Writable;
   session Session with
      Initial => A,
      Final => A
   is
   begin
      state A is null state;
   end Session;

end Test;

```Console
$ rflx check test.rflx
Parsing /tmp/test.rflx
test.rflx:4:7: parser: error: Expected 'session', got 'Channel'

Is that something that is blocking us? Otherwise I'd move it to 0.5.1.

As the workaround is simple (just use another name), we can move it to 0.5.1.


Add custom probing URL

It makes the probing URL configurable via rally.ini instead of always using https://github.com/ as probing URL.
Closes #866

@elasticmachine test this please

@elasticmachine test this please

cla/check


Unable to select item

I seem to be unable to fetch the text from a HTML page with a valid selector.
If I run this in the console on chrome
#("#countdown > div.display.days > div.circle > div").text()
I receive the correct text I would expect.
However running
doc.Find("#countdown > div.display.days > div.circle > div").First().Text()
Brings back nothing.
The webpage is https://cardanoroadmap.com/  is this an issue to do with the selector?

Hello Nick,
That's because the page is generated dynamically with javascript. If you get the page via curl, you'll see that the html for #countdown is empty:

There are some community-provided tips on how to handle such pages in the wiki (https://github.com/PuerkitoBio/goquery/wiki/Tips-and-tricks#handle-javascript-based-pages) but by itself goquery works with whatever HTML it is provided with.
Hope that helps,
Martin


Duplicate DNS rCode?

When I look at: https://github.com/miekg/dns/blob/836bea2f8dffa00b74af2d505c04e1cde3a9739b/types.go#L138C2-L138C13
I see two times code 16 being used. 16 is used for both BADSIG and BADVERS. Is that on purpose, or is this some kind of typo?
Sorry for asking.

It's unfortunate but accurate, cf. https://www.rfc-editor.org/rfc/rfc6895#section-2.3

Someone from IETF was sleeping I think..


Flag a MOM6 run as a restart if using prior restart path

Using the mechanism to point to an external restart directory:
restart: /path/to/restart

doesn't modify the experiment counter, because as far as payu is concerned, this is the first run. This breaks the logic the MOM6 module was using to determine whether to flag a run as a restart or not. In the case that the prior restart path has been set, we want to explicitly perform a restart run.
Thanks to @julia-neme for (unfortunately) finding this!

Hello @angus-g! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file payu/models/mom6.py:

Line 70:80: E501 line too long (96 > 79 characters)

Coverage remained the same at 42.245% when pulling d011aba32cd0add735e18172c474eee648309ccf on angus-g:mom6-prior-restart into 3f00d4b72390053ab9182e340c582fbd0a67683f on payu-org:master.

Seems a straightforward change.
Just to be explicit, would this have let to different behaviour if input_type is set incorrectly?

That's right, input_type = 'r' will try to start the run from the restart files, and input_type = 'n' will ignore any restart files and start a fresh run.

Huh, interesting. Not the same behaviour as MOM5 and other FMS models I guess. I'll merge.

What do the other models do with that parameter?

MOM5 at least didn't use it. Just reads in restart files that are either initial conditions or restarts from a previous run. In some cases if the restarts don't exist then it initialises to an "ideal state".


Reproducible builds

Ideally two sequential builds should produce the exact same result. https://en.wikipedia.org/wiki/Reproducible_builds

Dropped baked file system in favor of own implementation.

One difference to baked_file_system is that this implementation doesn't compress the assets, but also doesn't have to decompress them each time they are served, increasing the binary size with about 3MB.


RDS Aurora I/O-Optimized not showing correctly in the  "Daily Storage Cost for Amazon Relational Database Service" view in CUDOS

When customers enable Aurora I/O-Optimized, the "Daily Storage Cost for Amazon Relational Database Service" replaces RDS  Aurora Storage with RDS Magnetic Storage.
To fix the issue, a new line should be added in the calculated field Databases Storage Type
Below an example:
{product_code} = 'AmazonRDS' and locate({usage_type}, 'Aurora:IO-OptimizedStorageUsage')> 0,
    'RDS Aurora I/O Optimized Storage',

Please note that the compute usage type also changes to InstanceUsageIOOptimized:<instance_type> and it could affect other visuals.

will be added in the next CUDOS release

Released in CUDOS v5 - https://github.com/aws-samples/aws-cudos-framework-deployment/blob/main/changes/CHANGELOG-cudos.md#cudos---500


mate.mate-desktop: 1.20.3 -> 1.21.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/mate-desktop/versions.
These checks were done:

built on NixOS
Warning: no invocation of /nix/store/dx51na6smf7cpbav7zgb2x5xyyfbpcbp-mate-desktop-1.21.0/bin/mate-color-select had a zero exit code or showed the expected version
/nix/store/dx51na6smf7cpbav7zgb2x5xyyfbpcbp-mate-desktop-1.21.0/bin/mate-about passed the binary check.
Warning: no invocation of /nix/store/dx51na6smf7cpbav7zgb2x5xyyfbpcbp-mate-desktop-1.21.0/bin/.mate-color-select-wrapped had a zero exit code or showed the expected version
/nix/store/dx51na6smf7cpbav7zgb2x5xyyfbpcbp-mate-desktop-1.21.0/bin/.mate-about-wrapped passed the binary check.
2 of 4 passed binary check by having a zero exit code.
0 of 4 passed binary check by having the new version present in output.
found 1.21.0 with grep in /nix/store/dx51na6smf7cpbav7zgb2x5xyyfbpcbp-mate-desktop-1.21.0
directory tree listing: https://gist.github.com/b54e2f1e430d08d273ba8dab30a7f562
du listing: https://gist.github.com/74e6289b7a86dee591389adc61e024ed

meta.description for mate.mate-desktop is: '"Library with common API for various MATE modules"'.
cc @romildo for testing.
Experimental: this build is cached with Cachix. To use the cache follow these experimental instructions:
One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout b9b991bf729e3db6c078cb4cc0295332582ba85b && nix-shell --pure -I nixpkgs=. -p mate.mate-desktop

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: mate.mate-desktop
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: mate.mate-desktop
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/dx51na6smf7cpbav7zgb2x5xyyfbpcbp-mate-desktop-1.21.0
shrinking /nix/store/dx51na6smf7cpbav7zgb2x5xyyfbpcbp-mate-desktop-1.21.0/bin/.mate-about-wrapped
shrinking /nix/store/dx51na6smf7cpbav7zgb2x5xyyfbpcbp-mate-desktop-1.21.0/bin/.mate-color-select-wrapped
shrinking /nix/store/dx51na6smf7cpbav7zgb2x5xyyfbpcbp-mate-desktop-1.21.0/lib/libmate-desktop-2.so.17.1.4
gzipping man pages under /nix/store/dx51na6smf7cpbav7zgb2x5xyyfbpcbp-mate-desktop-1.21.0/share/man/
strip is /nix/store/21ymadblbmsbb2bk4q7gl4kjasp8zmgd-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/dx51na6smf7cpbav7zgb2x5xyyfbpcbp-mate-desktop-1.21.0/lib  /nix/store/dx51na6smf7cpbav7zgb2x5xyyfbpcbp-mate-desktop-1.21.0/bin
patching script interpreter paths in /nix/store/dx51na6smf7cpbav7zgb2x5xyyfbpcbp-mate-desktop-1.21.0
checking for references to /build in /nix/store/dx51na6smf7cpbav7zgb2x5xyyfbpcbp-mate-desktop-1.21.0...
/nix/store/dx51na6smf7cpbav7zgb2x5xyyfbpcbp-mate-desktop-1.21.0

Success on aarch64-linux (full log)
Attempted: mate.mate-desktop
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/c5lzjxy8lxlrkprp62hc9h212400jwwr-mate-desktop-1.21.0
shrinking /nix/store/c5lzjxy8lxlrkprp62hc9h212400jwwr-mate-desktop-1.21.0/bin/.mate-color-select-wrapped
shrinking /nix/store/c5lzjxy8lxlrkprp62hc9h212400jwwr-mate-desktop-1.21.0/bin/.mate-about-wrapped
shrinking /nix/store/c5lzjxy8lxlrkprp62hc9h212400jwwr-mate-desktop-1.21.0/lib/libmate-desktop-2.so.17.1.4
gzipping man pages under /nix/store/c5lzjxy8lxlrkprp62hc9h212400jwwr-mate-desktop-1.21.0/share/man/
strip is /nix/store/qg2agrqkf240s656d207zqhipl0bc2id-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/c5lzjxy8lxlrkprp62hc9h212400jwwr-mate-desktop-1.21.0/lib  /nix/store/c5lzjxy8lxlrkprp62hc9h212400jwwr-mate-desktop-1.21.0/bin
patching script interpreter paths in /nix/store/c5lzjxy8lxlrkprp62hc9h212400jwwr-mate-desktop-1.21.0
checking for references to /build in /nix/store/c5lzjxy8lxlrkprp62hc9h212400jwwr-mate-desktop-1.21.0...
/nix/store/c5lzjxy8lxlrkprp62hc9h212400jwwr-mate-desktop-1.21.0


Update custom-date-and-time-format-strings.md

Summary
Change through to to when talking about number ranges
@sammie-p
Fixes #35550

Internal previews

📄 File
🔗 Preview link

docs/standard/base-types/custom-date-and-time-format-strings.md
Custom date and time format strings

@gewarren


Antrea Windows initContainer fails to load by cert import error

Antrea Windows container fails to load and CrashesLoopBackoff in our internal Windows 22H2 setup.
The install-ovs-driver container shows Access denied at Import-Certificate HRESULT 0x800700005 (E_ACCESSDENIED)

Hi @laozc , thanks for reporting it.
I observed the issue happened on a fresh Windows Server 2022 when it is the first time to import certificate into the trusted publisher store. But it would work if any cert was already added into the store. The issue only exists in "trusted publishers" store. Personally, I suspect it is related some security policy settings on Server 2022, unfortunately I didn't find the exact policy.
With some test, I found that this alternative should work for the trusted publisher store, I have made this PR #6529 to fix it.
$CertStore = Get-Item cert:\LocalMachine\TrustedPublisher
$CertStore.Open([System.Security.Cryptography.X509Certificates.OpenFlags]"ReadWrite")
$CertStore.Add($(Get-Item $CertificateFile).FullName)
 $CertStore.Close()


Indent on first line of code block

Obsidian 0.9.22, Obsidianite 1.1.3
In Preview Mode, there seems to be a small indent before the first line of code in a code block. Is there a way to remove this?
Obsidianite

No theme

Really enjoying the theme btw :)

I am experiencing the same issue, hope there is a fix coming soon.

@Snuzzn @ikelvinwoo Thanks for reporting I will look into this for sure!

Fixed in version 1.1.4


OPOLO Cold Wallet Integration

OPOLO Cold Wallet Integration
Grant category
Please select one:

Developer tools / services

Description
OPOLO Cold wallet can integrate the Flow blockchain and its features into its wallet so all the users can have a secure storage for their flow coins.
Problem statement
Secure cold wallet storage for flow coins.

Target audience

Crypto users

Evidence for the need

Hacks
Proposed solution
OPOLO Cold wallet
Impact

In what ways does this benefit the broader Flow developer ecosystem?
It benefit not only the developers but also all the Flow users who are going to secure their flow coins.

Milestones and funding
It depends on what features you want to be implemented in OPOLO Cold wallet.

Note: Please consider adoption and/or maintenance milestones at the end of your project.

Milestone
Deliverables
Timeline
Risks
USD proposal

1 - MVP
Smart Contract
2 weeks
-
1000

X - Adoption
5 team using this project
4 weeks
-
1000

X - Maintenance
Resolving issuing and fixing bugs
3 months
-
1000

Total funding proposed:  DEPENDS
Team

Name
Role
Bio
Contact

Alex
Full-Stack Engineer
...
<EMAIL_ADDRESS>

hey @faboulous1 - could you fill out the details as requested in the template, missing are the milestones, team, and details about the solution.

Your team can contact us on our email for discussion and details if they are interested to integrate into OPOLO Cold Wallet www.opolo.io. thanks

@faboulous1 please add all requested info to the issue if you want this proposal to be reviewed by the committee. this is purposefully a streamlined and public process. we cannot review a proposal without the details in here.
feel free to add details and re-open the issue if you want to continue. thanks!


Mathjax compilation problem under IE 11 "Symbol" undefined

Issue Summary
A summary of the issue and the browser/OS environment in which it occurs. If
suitable, include the steps required to reproduce the bug.
Steps to Reproduce:

ie 11
Dynamic loading data
Call a function  -- > MathJax.typeset();

Any other information you want to share that is relevant to the issue
being reported. Especially, why do you consider this to be a bug? What
do you expect to happen instead?

Browser exception
2.Formula unrendered

Have you included the polyfill library as recommended in the documentation?  This looks like the type of error you get in IE without it.

Which repository should I reference for polyfill library localization?

Which repository should I reference for polyfill library localization?

I'm not sure what you actually have in mind, but the polyfill library website is polyfill.io.  They have an issue tracker that you might be able to use to ask about localization.
If you mean localization or MathJax itself, we don't yet have localization ported to MathJax v3 yet (v2 has it), but it is on our list of features to include.

I'm not sure what you actually have in mind, but the polyfill library website is polyfill.io.  They have an issue tracker that you might be able to use to ask about localization.
If you mean localization or MathJax itself, we don't yet have localization ported to MathJax v3 yet (v2 has it), but it is on our list of features to include.


feat(npu): add Ascend 910B support

Motivation
Support Ascend 910B training, remove torch.cuda related code and introduce accelerator.py to manage different accelerator backends.
Modification
TODO
BC-breaking (Optional)
TODO
Use cases (Optional)
TODO
Checklist
Before PR:

[ ] Pre-commit or other linting tools are used to fix the potential lint issues.
[ ] Bug fixes are fully covered by unit tests, the case that causes the bug should be added in the unit tests.
[ ] The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
[ ] The documentation has been modified accordingly, like docstring or example tutorials.

After PR:

[ ] If the modification has potential influence on downstream or other related projects, this PR should be tested with those projects.
[ ] CLA has been signed and all committers have signed the CLA in this PR.

fix CI
maybe need to set a default backend
in some cases, use_flash_attn is bounded to GPU. For example, in the pipeline scheduler, when we set use_flash_attn, it actually required to be cuda backend and use packed data. So in these cases, maybe we need to set backend=="GPU" and use_flash_attn=true -> pack dataset


Pattern synonyms?

Hi, @konsumlamm, thanks for publishing rrb-vector. I'd like to try it out as a replacement for Seqs in a few projects I'm working on. When working with Seqs, I find using the bundled pattern synonyms quite convenient. Would you be interested in adding similar pattern synonyms for Vector (I didn't see any in the haddocks)? If you think it might be a good choice, I could try to implement them and open a PR. Thanks!

I intentionally didn't add pattern synonyms for viewing the front/back, since viewl/viewr and <|/|> don't run in truly constant time (as opposed to the Data.Sequence counterparts). This could lead to confusion, when people expect pattern matching to have negligible cost. As an alternative, you could use the ViewPatterns extension, for example:
updateHead :: (a -> a) -> Vector a -> Vector a
updateHead f (viewl -> Just (x, xs)) = f x <| xs
updateHead _ xs = xs

updateLast :: (a -> a) -> Vector a -> Vector a
updateLast f (viewr -> Just (xs, x)) = xs |> f x
updateLast _ xs = xs

However, if you're mostly using the Seqs as queue/deque (i.e. you're mostly using viewl/viewr and <|/|>), I don't recommend switching, my Vector will likely be slower. Feel free to share your experience with replacing Seq by Vector though!

Ah, I see, that makes a lot of sense. ViewPatterns are a great alternative, though, thanks for the suggestion. Anyway, I'll go ahead and close this now. Thanks again!


Feature/test geometry

Types of PR

[x] New Features
[ ] Upgrade of existing features
[ ] Bugfix

Link to the issue
Description
I have added tests to the geometry package.
Some tests do not pass, so I have removed them in the commit 5a50ead419ae0e1f36e86d180c4a813586e73f2c.
Almost all removed tests (with one exception) will pass after #1139 is merged. The one test that will not pass after the merge will require an additional fix that will be implemented later.
After all fixes are applied to master, the commit 5a50ead419ae0e1f36e86d180c4a813586e73f2c can be reverted.
How to review this PR.
Others

@TauTheLepton Please pass build test before sending review request.

@hakuturu583
I am very sorry for the trouble.
The failing tests have been removed with the intention of restoring them in the future.
Now the build test has passed.


Bootstrap Tool tip is not working

Hi this is blazor issue or i am doing something wrong. Even i tried working with Modal pop up even that did not work either.
Html code in one of the component.

this is in one of the js file test.js
$(function () {
    $('#idname').tooltip();
    console.log("tool tip added");
});

below is the sequence of  files in index.html

    <meta charset="utf-8" />
    <link rel="stylesheet" href="css/bootstrap.min.css">
    <link href="css/task.css" rel="stylesheet" />

    <app>Loading...</app>

Note:- bootstrap version is v3.3.7, jquery version is v1.12.4
I took the same files and same htmls to another project WebForm project for testing and it is working fine there.

Problem is with test.js, it binds to DOMReady event, but Blazor renders later.
You need to register your tooltip after blazor component renders, via javascript interop.
In your component, you can override OnAfterRender and call javascript function to initialize tooltips.
You can also look at how I solved showing bootstrap modals in ModalBase.cs and Modal.cshtml.
Note: It's built using Blazor v0.2.0, so there is no OnAfterRender.

Yes, that's a limitation of the Bootstrap JS, which affects all SPA frameworks not only Blazor.
I'd recommend following @maraf's advice.


feat: enable configuring a handler to listen to informers stopping

Requires https://github.com/fabric8io/kubernetes-client/pull/4412

chore: update to SNAPSHOT version of fabric8 client
feat: enable configuring a handler to listen to informers stopping

LGTM,
would it be possible to add an integration test? (not sure how though)

I'm not sure either apart from what we already test in this PR. Note also that the informer part is already tested in the fabric8 client, we just need to test our integration, which I believe we do somewhat in this PR.

LGTM,
would it be possible to add an integration test? (not sure how though)

I'm not sure either apart from what we already test in this PR. Note also that the informer part is already tested in the fabric8 client, we just need to test our integration, which I believe we do somewhat in this PR.

Yep, no doubt this is good enough. Just meatn in a way if that would be easy to do, would not harm,

cc @andreaTP
could you review this pls, should be support your use case.


Cannot start on MacOS 13.0.1

Fails to execute in user mode and sudo mode.
2022-11-14 08:53:45 INFO     discord.client logging in using static token
Traceback (most recent call last):
  File "aiohttp/connector.py", line 980, in _wrap_create_connection
  File "asyncio/base_events.py", line 1092, in create_connection
  File "asyncio/base_events.py", line 1122, in _create_connection_transport
  File "asyncio/sslproto.py", line 534, in data_received
  File "asyncio/sslproto.py", line 188, in feed_ssldata
  File "ssl.py", line 975, in do_handshake
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:997)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "index.py", line 81, in <module>
  File "discord/client.py", line 828, in run
  File "asyncio/runners.py", line 44, in run
  File "asyncio/base_events.py", line 649, in run_until_complete
  File "discord/client.py", line 817, in runner
  File "discord/client.py", line 745, in start
  File "discord/client.py", line 580, in login
  File "discord/http.py", line 801, in static_login
  File "discord/http.py", line 624, in request
  File "aiohttp/client.py", line 1141, in __aenter__
  File "aiohttp/client.py", line 536, in _request
  File "aiohttp/connector.py", line 540, in connect
  File "aiohttp/connector.py", line 901, in _create_connection
  File "aiohttp/connector.py", line 1206, in _create_direct_connection
  File "aiohttp/connector.py", line 1175, in _create_direct_connection
  File "aiohttp/connector.py", line 982, in _wrap_create_connection
aiohttp.client_exceptions.ClientConnectorCertificateError: Cannot connect to host discord.com:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:997)')]
[3962] Failed to execute script 'index' due to unhandled exception!

For some reason, a few machines are unable to verify SSL provided by Discord API. You can try one of the following methods:

Try running it using the Python method instead
Use https://discordactivedev.vercel.app/


AutoMigrate Belongs To Relationship always attempts to Alter table

GORM Playground Link
https://github.com/go-gorm/playground/pull/539
Description
When I use AutoMigrate a struct with Belongs to relationship with another struct, it will always ALTER TABLE when I restart the application.
 type Company struct {
 	ID   int
 	Name string
 }

Table Definition:
CREATE TABLE "companies" ("id" bigserial,"name" text,PRIMARY KEY ("id"))

type User struct {
	gorm.Model
	Name      string
	CompanyID int
	Company   Company
}

Table Definition:
CREATE TABLE "users" ("id" bigserial,"created_at" timestamptz,"updated_at" timestamptz,"deleted_at" timestamptz,"name" text,"company_id" bigint,PRIMARY KEY ("id"),CONSTRAINT "fk_users_company" FOREIGN KEY ("company_id") REFERENCES "companies"("id"))

This is so far correct.
Now when I kill my application and attempt to rerun with auto migration as one of the start up process. I see the following in the logs:
ALTER TABLE "users" ALTER COLUMN "company_id" TYPE bigint

This happens every time I restart the application. We have 15 structs with belongs to relationship among each other. This is issuing ~29 similar alter queries thats locking the DB instance when the clients attempt to read the data.
GORM.version: v1.23.8
GORM.driver.postgres.version: v1.3.9
Expected
When the schemas are applied, the alter statements should not be issued.

Upgrade gorm and postgres version. This issue has been fixed https://github.com/go-gorm/gorm/commit/62593cfad03ebf1e6cae30bac010655b4a28ff67

Thanks @a631807682. That worked.


About %Server_name%

Hello,I have a question:
I built a velocity server with this plugin and I used HuskChat in velocity.
I want huskchat to show the custom server name which I defined in placeholderAPI's config in my backend servers
So I used this placeholder: %Server_name%
but instead of showing the name in papi's config,it showed the name which I defined in velocity config,(e.g. It showed lobby,skyblock,etc.But not "主大厅","空岛")
So,What I want to ask is that is there have some method to make PAPIProxyBridge to show the server name I want OR is there have any other way to make same result?Thank you!
[✓]I installed PAPIProxyBridge both at velocity and my backend servers
[✓]I read the docs
Sorry,My English is not so well

Solved

aw


Runtime: Properly handle demangling nested generic typerefs with symbolic manglings.

The demangling tree for a symbolic reference doesn't indicate the generic context depth of the referenced type, so we have to form the type metadata from whole cloth without incrementally building up nested types as we do for concrete mangled types. Notice when DecodedMetadataBuilder is passed a context descriptor ref without a parent and directly form the entire type in this case. Fixes rdar://problem/38891999.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@DougGregor In those libraries IIRC we resolve symbolic mangling directly into their mangling tree, since there isn't as much performance win to be had preserving the direct pointer to the type descriptor, so I think they should be OK. I'll double check though, thanks for the suggestion!


Feature/landing page/mobile designs - hamburger menu

Description
This pull request is for the hamburger mobile menu for screens under 768px. This will help users on mobile move between different screens on the app. The menu icon will stay fixed at the top of the screen, so mobile users can always access the log in / sign up pages.
Type

[ ] This is a bugfix.
[ ] This is a new feature.
[X] This is part of a feature.

Organization

[X] Have you linked this pull request to a Trello card?
[X] Have you named the branch in the format of feature/describe_feature_or_change OR bug/describe_bug_this_is_fixing

Review

[X] Is this a work in progress? - Yes, there are a few more things to be done on this branch - need to fix image aspect ratios for smaller screens
[X]  Is this ready to be reviewed?
[X]  Have you added two reviewers to this pull request?

 As a user, I see a landing page when I visit the site that shows the features of the app before I decide whether or not to sign up.

 As a user, I see a landing page when I visit the site that shows the features of the app before I decide whether or not to sign up.


bump testing container to core 15.5.0

@sisuresh we should update the stable container too, right?

@bartekn Yeah you're right. Fixing now.