Istio 1.6 Istiod error messages

Bug description
After installing the Istio 1.6, these warning messages are flooding in Istiod pods. I don't know the impact of these error messages though my initial test to the applications are working fine.
2020-05-28T21:39:57.965601Z	warn	k8s.io/client-go@v0.18.0/tools/cache/reflector.go:125: watch of *v1.PartialObjectMetadata ended with: an error on the server ("unable to decode an event from the watch stream: unable to decode watch event: no kind \"Node\" is registered for version \"v1\" in scheme \"pkg/runtime/scheme.go:101\"") has prevented the request from succeeding
2020-05-28T21:40:37.973025Z	warn	k8s.io/client-go@v0.18.0/tools/cache/reflector.go:125: watch of *v1.PartialObjectMetadata ended with: an error on the server ("unable to decode an event from the watch stream: unable to decode watch event: no kind \"Node\" is registered for version \"v1\" in scheme \"pkg/runtime/scheme.go:101\"") has prevented the request from succeeding

[ ] Configuration Infrastructure
[ ] Docs
[X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
No error/warning messages on Istiod deployment.
Steps to reproduce the bug

Get the IstioOperator manifest

# manifest.yaml
---
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  addonComponents:
    kiali:
      enabled: true
      k8s:
        replicaCount: 3
    prometheus:
      enabled: false
    prometheusOperator:
      enabled: true
  components:
    base:
      enabled: true
    pilot:
      enabled: true
      k8s:
        env:
          - name: POD_NAME
            valueFrom:
              fieldRef:
                apiVersion: v1
                fieldPath: metadata.name
          - name: POD_NAMESPACE
            valueFrom:
              fieldRef:
                apiVersion: v1
                fieldPath: metadata.namespace
        hpaSpec:
          maxReplicas: 6
          metrics:
            - resource:
                name: cpu
                targetAverageUtilization: 80
              type: Resource
          minReplicas: 3
          scaleTargetRef:
            apiVersion: apps/v1
            kind: Deployment
            name: istiod
        readinessProbe:
          httpGet:
            path: /ready
            port: 8080
          initialDelaySeconds: 1
          periodSeconds: 3
          timeoutSeconds: 5
        strategy:
          rollingUpdate:
            maxSurge: 100%
            maxUnavailable: 25%
    ingressGateways:
      - enabled: true
        k8s:
          env:
            - name: ISTIO_META_ROUTER_MODE
              value: sni-dnat
          hpaSpec:
            maxReplicas: 6
            metrics:
              - resource:
                  name: cpu
                  targetAverageUtilization: 80
                type: Resource
            minReplicas: 3
            scaleTargetRef:
              apiVersion: apps/v1
              kind: Deployment
              name: istio-ingressgateway
          resources:
            limits:
              cpu: 2000m
              memory: 1024Mi
            requests:
              cpu: 100m
              memory: 128Mi
          overlays:
            - apiVersion: v1
              kind: Service
              name: istio-ingressgateway
              patches:
                - path: spec.type
                  value: NodePort
                - path: spec.ports.[name:status-port].nodePort
                  value: 32717
                - path: spec.ports.[name:http2].nodePort
                  value: 32715
                - path: spec.ports.[name:https].nodePort
                  value: 32716
        name: istio-ingressgateway
    telemetry:
      enabled: true
      k8s:
        env:
          - name: POD_NAMESPACE
            valueFrom:
              fieldRef:
                apiVersion: v1
                fieldPath: metadata.namespace
          - name: GOMAXPROCS
            value: "6"
        hpaSpec:
          maxReplicas: 6
          metrics:
            - resource:
                name: cpu
                targetAverageUtilization: 80
              type: Resource
          minReplicas: 3
          scaleTargetRef:
            apiVersion: apps/v1
            kind: Deployment
            name: istio-telemetry
  meshConfig:
    rootNamespace: istio-system
    enableAutoMtls: true
  values:
    global:
      defaultPodDisruptionBudget:
        enabled: true
    kiali:
      dashboard:
        viewOnlyMode: true

Install Istio with istioctl install -f manifest.yaml

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
# istioctl version --remote
client version: 1.6.0
control plane version: 1.6.0
data plane version: 1.6.0 (7 proxies)
# kubectl version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.1", GitCommit:"d224476cd0730baca2b6e357d144171ed74192d6", GitTreeState:"clean", BuildDate:"2020-01-15T15:50:25Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.9-eks-f459c0", GitCommit:"f459c0672169dd35e77af56c24556530a05e9ab1", GitTreeState:"clean", BuildDate:"2020-03-18T04:24:17Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}

How was Istio installed?
IstioOperator API
Environment where bug was observed (cloud vendor, OS, etc)
AWS EKS

I doubt this is because of version mismatch
And i have filed an issue in kubernetes https://github.com/kubernetes/kubernetes/issues/91582

So the conclusion is the v0.18 client-go mismatch with k8s 1.14 and lower. Because of the PartialObjectMetadata .

If we want to support 1.14, i can file a fix. @howardjohn

I see , thanks for figuring this out. We officially support 1.15+ so anything blow then is not high priority I think but ok to fix if it's easy?

I think it is a simple fix. Will do that.

@hzxuzhonghu the prior agreement within T&R and TOC was that the project would hard pin on the bottom supported version of K8s and issue a warning if the top pin was out of bounds.
The K8s support matrix describes in detail why the project does not want to support Kubernetes 1.14.

unintentionally pressed close and comment button.

Happy to consider upgrading our EKS cluster if that is the supported version for Istio 1.6.

This can be closed


Change hardcoded service url

This is a quick and dirty fix to use the dataset access service that is deployed as a part of the eda stack. I had started to make the service url configurable, but it's not trivial and I'm not confident I can complete that work before build 55 is release. It should be done as a follow-up, however.

This is no longer relevant


Log large bcrypt costs, error if password-hash comparison takes > 10s

server: log bcrypt cost if > 12, error on runtime > 10s
The bcrypt hashing algorithm runtime grows exponentially with cost, and might cause a timeout if the cost is too high. Notifying the user of high cost and of long running calculations will help with parameter tuning and debugging.
Tests: added test cases for both additions
Fixes #962
Review after #1005 is merged

ok to test


Update_online_migration_armaha.md

Since we got to know that Online migrations to Azure SQL DB are replaced, it would be great to update the customer.
The original article has a section about "for online migrations" , and it points to itself.. so would be great to update it there..

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

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

@aravindmahadevan-ms @pochiraju Could you review my proposed edits? Thanks.

Thanks @pochiraju


Channel indexing after masking

Note
The data module has a masking feature, but the channel indexing needs to be preserved for later usage. We can have an explicit index map stored separately, while re-define getter returns a masked signal.

Decided to keep the masking under Spikestamps to keep the analysis consistent.


Blueprint module does not accept ResourceGroup.Name values with long computed expressions

Describe the bug
Receiving a validation error through the Az.BluePrint powershell module regarding the importing of a Blueprint with a computed ResourceGroup.name value. The error indicates only 90 characters are supported in the resource group name. However, this is not actually true as the value allows [] expansion values exceeding 90 characters.
Expected behavior
The computable value should be accepted.
Actual behavior (include Exception or Stack Trace)
Import-AzBlueprintWithArtifact : 'Name' exceeds maximum length of '90'.
To Reproduce
    "resourceGroups": {
            "ApplicationResourceGroup": {
                "location": "[parameters('l')]",
                "name": "[concat(parameters('u'),'-',parameters('e'),'-',parameters('d'),'-',parameters('a'),'-rg')]"
            }
        }

Attempt to import the Blueprint, and receive the error.

#https://github.com/Azure/azure-powershell/issues/11552

Azure/azure-sdk-for-net#11257

The error is in blueprint/Microsoft.Azure.Management.Blueprint/src/Generated/Models/ResourceGroupDefinition.cs:Validate. I would love to fix it, but since the file is generated, I'm not sure of the best way to approach it. I do not know how it was generated, or what the proper procedure to override it is.

closing this issue as it is not related to the SDK

I'm running into the same issue while running Az.Blueprint module version 0.2.13. I didn't try every older version of the module/cmdlet, but I did install these older versions and ran into the same problem with each attempt:

0.2.10
0.2.6
0.2.0

The cmdlet doesn't exist in versions 0.1.1 nor 0.1.0, so, no point in trying them ☹

This is an issue with our APIs, not with the SDK. With the planned changes to move blueprint definitions to template specs, this is not likely something we are going to fix. We just announced templateSpecs at build, so details are a bit scarce, but we should have more info to share in 1-2 months.

Thanks for the information @alex-frankel; I caught that announcement and look forward to template specs!
As a workaround, I simply shortened some parameter names to get the string value of the function at or below 90 characters in length.. works fine otherwise.


feat: trailing-slash proxy to parsed path with same request

https://hono.dev/docs/middleware/builtin/trailing-slash
This is a proposal for a built-in middleware trailing-slash.
Currently, when a 404 and method is GET, the user is redirected to the parsed path.
But for methods other than GET, or include GET as well. Or if it is specified as an option.
I think we should pass a request object with only the path changed, like app.fetch(parsedRequest), and return the response as is.

draft


[Bug]: KafkaIO pulls dependency vulnerable to CVE-2024-26308 and CVE-2024-25710

What happened?
Add KafkaIO as dependency to pom.
https://mvnrepository.com/artifact/io.confluent/kafka-schema-registry-client/7.6.0 has 2 vulnerabilities.
There is 7.6.3 available.
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components

[ ] Component: Python SDK
[X] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Infrastructure
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

.take-issue


Added itemRenderFunction option

With new option available simple logic-based item rendering.
var options = {
    valueNames: [ 'name', 'city' ],
    itemRenderFunction: function(values, item){
        if (values.available){
            return '

 Enabled
';
        } else {
            return '

 Disabled
';
        }
    }
};

var listEntry = {
   "name": "Artem",
   "city": "Minsk",
   "available": true
};

hackerList.add([ listEntry ]);

Codecov Report

Merging #693 into master will decrease coverage by 0.34%.
The diff coverage is 57.14%.

@@            Coverage Diff             @@
##           master     #693      +/-   ##
==========================================
- Coverage   94.74%   94.39%   -0.35%
==========================================
  Files          19       19
  Lines         799      803       +4
  Branches      187      189       +2
==========================================
+ Hits          757      758       +1
- Misses         29       31       +2
- Partials       13       14       +1

Impacted Files
Coverage Δ

src/templater.js
97.34% <57.14%> (-2.66%)
:arrow_down:

Continue to review full report at Codecov.

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

Duplicate of #634 which was just merged 🎊
Thanks anyways 🙌


add support for custom object in tuf targets metadata

Description
TUF targets metadata objects support an optional custom object, which can be used to specify additional information about the individual target files.
From the TUF spec:

CUSTOM
An object. If defined, the elements and values of the CUSTOM object will be made available to the client application. The format of the CUSTOM object is opaque to the framework, which only needs to know that the "custom" attribute maps to an object. The CUSTOM object may include version numbers, dependencies, requirements, or any other data that the application wants to include to describe the file at TARGETPATH. The application may use this information to guide download decisions.

This offers endless possibilities, for example:

include information about the update that can be displayed to the user, e.g. a summary of changes
include information for verifying the integrity of reconstructed archives after patch application
specify additional actions to be taken during an update
...

Implementation
This requires changes both on the repo side and on the client side:

Repo: Ability to specify custom metadata when adding a new target. This implies we need a custom metadata arg in Repository.add_bundle().
Client: Ability to retrieve the custom metadata when checking for updates. The Client.check_for_updates() method returns a TargetMeta, which looks like the perfect place to include the custom metadata. DO NOTE: the TargetMeta object returned is always that of the full archive, even if a patch update will be applied. So, on the repo-side, any custom metadata required by the user application would need to be added to the archive target, not the patch target.

Notes
In python-tuf (tuf.api.metadata), the custom object is represented by the TargetFile.custom property.
Judging from the source, the custom property can be set by adding a 'custom' member to the TargetFile.unrecognized_fields dictionary. For example:
target = TargetFile.from_file(...)
target.unrecognized_fields['custom'] = dict(...)

EDIT:
Actually, all unrecognized_fields are included in the metadata, as can be seen in the source.
So, custom is nothing special in that respect, but it's the only "unrecognized field" that's defined in the spec and has a corresponding property.
Also note that python-tuf does not check whether the value assigned to custom is actually a dict (which maps to a JSON object). The spec does not provide an explicit definition of the term object, but it uses "a subset of the JSON object format", so we'll assume object implies the equivalent of a JSON object (which is a dict in Python).

Although #100 works, it would probably be more convenient only to allow custom metadata for archives.
This would simplify the interface, and it makes more sense, because all the client app will ever see is the TargetMeta for the archive (not for the patch).
Perhaps keep the patch option for internal use?

In some cases it is convenient to store custom metadata for tufup's internal use.
Examples are the tar size and hash data from #105 and the "required" flag from #111.
To prevent key clashes, it would be preferable to separate this internal custom metadata from any user-specified custom metadata.
Moreover, the internal metadata should be hidden from casual users, to prevent confusion.
The cleanest approach would probably be to separate the TUF CUSTOM object into a TUFUP object and a USER object, as follows:
{
  "custom": {
    "tufup": {},
    "user": {}
  }
}

Methods need to be updated to ensure the casual user is only aware of the USER object.


Batch block requests

Currently, when we fetch blocks from the node, we do this as multiple requests all sent in parallel, which typically results in 100 RPC calls done in parallel (as 100 is the default value for DEFAULT_FUNNEL_GROUP_SIZE)
https://github.com/PaimaStudios/paima-engine/blob/a0987398bbd6ad67280de28b6825c4ef3b240d25/paima-funnel/src/reading.ts#L48-L71
However, this leads to issues where RPC endpoints will throttle Paima for making too many requests. We've seen this with people trying to build on BNB Chain, and we're seeing it with Arbitrum as well.
Geth actually supports batching these requests together, and you can see them talk about exactly this use-case here. This can be done through the web3 library using BatchRequest

This should be fixed in the latest version


Disabled outline on button

Hi,
I was having an issue where I got a black outline around the Zoom btn, disabling the outline was the fix, so I am making this PR.

@dougg0k disabling the outline reduces the accessibility of the component, so that's not something I am willing to do. However, consuming projects can decide what to do for themselves with these tools / concepts:

https://github.com/ten1seven/what-input
https://developer.mozilla.org/en-US/docs/Web/CSS/:focus-visible
https://css-tricks.com/keyboard-only-focus-styles/
https://github.com/WICG/focus-visible

Thank you for taking the time to make a pull request, though!
I'll be sure to add you to the All Contributors list soon for your ideas and reports.

I clearly wasn't aware, thanks for the links.


Laravel 11 - doctrine/dbla req

Hi,
I'm tring to install the package in a new project created with L11 ( sail + pgsql + redis )
But the composer need doctrine/dbal that is removed in L11, any plan to replace that request or suggest ?
I'm wrong with any step?  the new clean install it's a basic install 😖

There are no plans to remove the doctrine/dbal dependency currently as that would break support for any Laravel installation below 11. And I don't want to maintain two different versions.

Hi @tpetry! Pardon the ping on a closed issue.
To get around the composer installation error, I'm passing the --with-all-dependencies flag.
This works, but it looks like it involves downgrading a framework package:
- Downgrading carbonphp/carbon-doctrine-types (3.2.0 => 2.1.0)

Just wanted to verify that this is correct / the recommended way to do it?

Hey Gringo. The former request was about dropping Doctrine because Laravel 11 doesn‘t need it anymore. Can you share when and where the downgrade is happening? Because as Laravel 11 just removed the dependency and my package still requires it, there won‘t be any difference in the installed packages.

@GringoDotDev The issue about needing to downgrade has been fixed with version 0.40.0 😉

I totally forgot to follow up on this, thank you so much for the update!!


ulauncher: 5.15.4 -> 5.15.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for ulauncher is: A fast application launcher for Linux, written in Python, using GTK
meta.homepage for ulauncher is: https://ulauncher.io/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.15.6 with grep in /nix/store/d8r0g0mmbdjqbd6krgsmb3d9xayqrial-ulauncher-5.15.6
found 5.15.6 in filename of file in /nix/store/d8r0g0mmbdjqbd6krgsmb3d9xayqrial-ulauncher-5.15.6

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
ulauncher

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d8r0g0mmbdjqbd6krgsmb3d9xayqrial-ulauncher-5.15.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ulauncher https://github.com/r-ryantm/nixpkgs/archive/fa2c5abe85869575d7e63158453bc7bf9f9960ae.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/fa2c5abe85869575d7e63158453bc7bf9f9960ae#ulauncher

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d8r0g0mmbdjqbd6krgsmb3d9xayqrial-ulauncher-5.15.6
ls -la /nix/store/d8r0g0mmbdjqbd6krgsmb3d9xayqrial-ulauncher-5.15.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

ulauncher

Maintainer pings
cc @aaronjanse @SebTM for testing.

Result of nixpkgs-review pr 267591 run on x86_64-linux 1

2 packages built:

ulauncher
ulauncher.dist


length not working when we run jsonpath query with SelectTokens

Sample JSON:
{
"firstName": "John",
"lastName": "doe",
"age": 26,
"address": {
"streetAddress": "naist street",
"city": "Nara",
"postalCode": "630-0192"
},
"phoneNumbers": [
{
"type": "iPhone",
"number": "0123-4567-8888"
},
{
"type": "home",
"number": "0123-4567-8910"
}
]
}
Query:
$.phoneNumbers.length
On using the 'SelectTokens' to run the query I am not able to get the length value from the query.
Expcted:
[
2
]
IMPORTANT NOTE:
https://github.com/json-path/JsonPath#functions
Can be Functions like length() supported here.

FYI: duplicate of https://github.com/JamesNK/Newtonsoft.Json/issues/1318


cMD3 taxonomy names

Need to account for new naming in metaphlan3.  Ideally keep the NCBI IDs in rowData, but this is not critical because we can provide a map separately.

Examples at https://storage.cloud.google.com/data-curatedmetagenomics. E.g.

small: https://storage.googleapis.com/data-curatedmetagenomics/AsnicarF_2017.tar.gz
big: https://storage.googleapis.com/data-curatedmetagenomics/AsnicarF_2021.tar.gz

New simplified function for reading files and creating list of matrices: https://github.com/schifferl/curatedmetagenomicdatapipeline

See https://github.com/waldronlab/curatedMetagenomicData/tree/remodel branch

The NCBI Taxonomy IDs were removed from the the tsv inputs, but could be mapped again. I am closing this for now because it would rather be a feature request.

Dropping the NCBI IDs is a significant loss of annotation that makes it more difficult to find taxa or do microbe set analysis, making it a high priority and an open feature request, but not critical to the cMD 3.0 release. If you prefer I'll post it as a separate feature request though.


added chai aur react youtube channel for webdev #hacktoberfest2023

Fixes Issue

Changes proposed

Added Chai aur React Youtube channel for awesome content around React and Javascript
Screenshots

Note to reviewers

Hi @pratikkumar399. Welcome to LinksHub! :) We don't accept spam pull requests, so I'm putting yours in draft mode for now. In the future, please wait until your issue has been approved and assigned to you before you submit a pull request. Refer to our Contributing Guide to learn how to effectively contribute to the project. Happy Contributing! 😊

@pratikkumar399
Please do it properly, if you need to know anything let us know. We will remove the spam label if you do things properly.

Removing the spam label. He has created #2018

Removing the spam label. He has created #2018

I can't reopen the PR @Anmol-Baranwal

@CBID2
He has deleted the branch, he will create a new one.


clone_node() doesn't duplicate nonstandard tag names

While investigating #3098, I noticed that Gumbo's clone_node() function doesn't make a copy of nonstandard tag names.
I think this is the fix
diff --git a/gumbo-parser/src/parser.c b/gumbo-parser/src/parser.c
index 67812b23..c3e5e038 100644
--- a/gumbo-parser/src/parser.c
+++ b/gumbo-parser/src/parser.c
@@ -1377,6 +1377,9 @@ static GumboNode* clone_node (
   *new_node = *node;
   new_node->parent = NULL;
   new_node->index_within_parent = -1;
+
+  if (node->v.element.tag == GUMBO_TAG_UNKNOWN)
+    new_node->v.element.name = gumbo_strdup(node->v.element.name);
   // Clear the GUMBO_INSERTION_IMPLICIT_END_TAG flag, as the cloned node may
   // have a separate end tag.
   new_node->parse_flags &= ~GUMBO_INSERTION_IMPLICIT_END_TAG;

but I'd like to understand why this hasn't been causing a bunch of memory leaks first.

@stevecheckoway It looks like clone_node isn't being called for an unknown tag in the test suite.
Here's the patch I used:
diff --git a/gumbo-parser/src/parser.c b/gumbo-parser/src/parser.c
index 06f096f8..180ee746 100644
--- a/gumbo-parser/src/parser.c
+++ b/gumbo-parser/src/parser.c
@@ -20,6 +20,7 @@
 #include <stdint.h>
 #include <stdlib.h>
 #include <string.h>
+#include <stdio.h>

 #include "ascii.h"
 #include "attribute.h"
@@ -1396,6 +1397,11 @@ static GumboNode* clone_node (
   *new_node = *node;
   new_node->parent = NULL;
   new_node->index_within_parent = -1;
+
+  if (node->v.element.tag == GUMBO_TAG_UNKNOWN) {
+    fprintf(stderr, "MIKE: unknown tag %s\n", node->v.element.name);
+  }
+
   // Clear the GUMBO_INSERTION_IMPLICIT_END_TAG flag, as the cloned node may
   // have a separate end tag.
   new_node->parse_flags &= ~GUMBO_INSERTION_IMPLICIT_END_TAG;

and it never prints anything!


Semi visible toolbar and PagerTitleStrip

Semi visible toolbar and PagerTitleStrip when scrolling horizontally with not fully scrolled vertically..
hard to explain :D just check the video and screenshot
https://www.youtube.com/watch?v=72jkSSGzekg

i have this problem too....


Responsive & Mobile interactions should be implemented.

Expected behavior and actual behavior:
Doesn't seem like the mobile interactions have been implemented per design.  Opening this issue so we can track the future effort.
There also seems to be an issue with responsive behavior. CB doesn't quite fit in the iphone view and doesn't resize to fit as expected.
Steps to reproduce the problem:
Open the local instance in a chrome screen size simulator.
Environment:
CB: Redesign branch, latest pull
Browser: Chrome simulator
Screenshot:

/cc @davidrleonard

Implemented in 08f93a728a49f6e34016ce581e21918bbb9791b7


Parameter 'osDisk.name' is not allowed

I tried a snippet from the sample as follows:
"storageProfile": {
  "imageReference": {
    "publisher": "MicrosoftWindowsServer",
    "offer": "WindowsServer",
    "sku": "2019-datacenter",
    "version": "latest"
  },
  "osDisk": {
    "name": "osdisk",
    "vhd": {
      "uri": "[concat(reference(concat('Microsoft.Resources/deployments/', 'Storage-', variables('diskStorageAccountName'))).outputs.storageAccount.value.primaryEndpoints.blob, 'vhds/mydisk.vhd')]"
    },
    "caching": "ReadWrite",
    "createOption": "FromImage"
  }
}

and got the following error:
{
    "status": "Failed",
    "error": {
        "code": "InvalidParameter",
        "target": "osDisk.name",
        "message": "Parameter 'osDisk.name' is not allowed."
    }
}

The API version was 2019-06-01.
Please check with the PG and update the example.

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

ID: f54a1dea-9a23-a032-33c8-060aa893a957
Version Independent ID: bc24822f-2075-cdec-ccd6-2a74a61a372a
Content: Deploying disks with Azure Resource Manager templates - Azure Virtual Machines
Content Source: articles/virtual-machines/using-managed-disks-template-deployments.md
Service: virtual-machines
Sub-service: disks
GitHub Login: @jboeshart
Microsoft Alias: jaboes

Once I removed name I'm got another error:
{
    "status": "Failed",
    "error": {
        "code": "InvalidParameter",
        "target": "osDisk.vhd",
        "message": "Parameter 'osDisk.vhd' is not allowed."
    }
}

@abatishchev Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate. We will update you accordingly.

@jboeshart Can you please check and add your comments on this doc update request as applicable

Here's a quick start template which looks very different, first creates a resource of type Compute/images and references it, namely:
"osProfile": {
                    "computerName": "[parameters('vmName')]",
                    "adminUsername": "[parameters('adminUsername')]",
                    "adminPassword": "[parameters('adminPasswordOrKey')]",
                    "linuxConfiguration": "[if(equals(parameters('authenticationType'), 'password'), json('null'), variables('linuxConfiguration'))]"
                },
                "storageProfile": {
                    "imageReference": {
                        "id": "[resourceId('Microsoft.Compute/images', variables('imageName'))]"
                    }
                }

I'm seeing that this is still a valid property and there are a number of quickstart templates that use it, so I'm not sure why you are getting that error. What is the full contents of your template that you're deploying?
https://docs.microsoft.com/en-us/rest/api/compute/virtualmachines/createorupdate#osdisk

Sure, it's still a valid property but it can be used only in particular cases. Custom VHD images doesn't seem to be one of them.

@jboeshart:

https://docs.microsoft.com/en-us/rest/api/compute/virtualmachines/createorupdate#osdisk

Not sure if it matters or not but the link is for VMs not VMSS

From what I tried and read I can say that the template in the doc is incorrect as it mixes up mutually exclusive properties.
However per @jboeshart it's by design: it's not a deployable sample, it's just a sample.
I believe this is a correct approach and goes against other articles for ARM templates and the idea of documentation in general.

@abatishchev can you please elaborate on the mutually exclusive properties? As I've looked through this, I don't believe that there are any inaccuracies in the examples for both unmanaged and managed disks. All the properties look to be supported in the current API's. It appears your issue is related to using images in VMSS, both of which aren't really in scope for this document.
I've deployed this template and added in the osDisk.name parameter and the VM deployed successfully.
We have other documentation that uses the same approach of using examples of templates to demonstrate how to use them, but they aren't deployable. We also link to deployable examples in the introduction if the reader would like to deploy an example and look through a full template.
https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-mvss-custom-image
https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-mvss-start
If you have specific updates you feel would improve this document, please feel free to submit a PR with those updates.

VMSS doesn't support VHD over SAS since API version 2018-06-01.
The only way I managed to get it working was this:
{
  "type": "Microsoft.Compute/images",
  "name": "[variables('imageName')]",
  "apiVersion": "[variables('computeApiVersion')]",
  "location": "[variables('clusterLocation')]",
  "properties": {
    "storageProfile": {
      "osDisk": {
        "osType": "Windows",
        "blobUri": "[concat(reference(concat('Microsoft.Resources/deployments/', 'Storage-', variables('diskStorageAccountName'))).outputs.storageAccount.value.primaryEndpoints.blob, variables('imageFolderName'), '/', variables('imageName'), '.vhd')]"
      }
    },
    "hyperVGeneration": "V1"
  }
}

and then
"storageProfile": {
  "imageReference": {
    "id": "[resourceId('Microsoft.Compute/images', parameters('imageName'))]"
  }
}

I see the same issue for VMSS. It looks like the "name" property isn't allowed on VMSS disks, only VM disks.

I see the same issue for VMSS. It looks like the "name" property isn't allowed on VMSS disks, only VM disks.

@psmanhas can you please have this reassigned to the owner of the VMSS documentation?
#reassign: @psmanhas

@psmanhas can you please have this reassigned to the owner of the VMSS documentation?
#reassign: @psmanhas

@mimckitt Can you please check and add your comments on this doc update request as applicable.
Thanks

@mimckitt Can you please check and add your comments on this doc update request as applicable.
Thanks

@mimckitt Can you please check and add your comments on this doc update request as applicable.
Thanks

@mimckitt Can you please check and add your comments on this doc update request as applicable.
Thanks

While we're here, let me point out the following issues I had while converting my VM template to a VMSS one:

the name issue also exists for dataDisks.
osProfile.computerNamePrefix says "Computer name prefixes must be 1 to 15 characters long", but I get verification errors stating that the max is 9 characters. Please make that consistent, one way or another.
The "id" parameter of networkProfile.networkInterfaceConfigurations is very underdocumented (and I still don't know how to use it).

I can create separate issues for all of these if that would be more helpful.

While we're here, let me point out the following issues I had while converting my VM template to a VMSS one:

the name issue also exists for dataDisks.
osProfile.computerNamePrefix says "Computer name prefixes must be 1 to 15 characters long", but I get verification errors stating that the max is 9 characters. Please make that consistent, one way or another.
The "id" parameter of networkProfile.networkInterfaceConfigurations is very underdocumented (and I still don't know how to use it).

I can create separate issues for all of these if that would be more helpful.

#reassign: @roygara

@roygara since this is in the disks section, can you take a look with the storage PMs to see how we might fix this?
#reassing: @roygara

@roygara since this is in the disks section, can you take a look with the storage PMs to see how we might fix this?
#reassign: @roygara

This issue seems to persist on many API versions going back to 2017-12-01.
We are attempting to deploy a VMSS using the virtual-environments repo, which produces VHD disks, and MS has stated there is no plans to convert to managed disks: https://github.com/actions/virtual-environments/discussions/5104. This is to work in conjunction with a Devops VMSS agent.
First tried to convert to a managed image, which worked for the linux instance, but fails for the windows instance. Upon deployment, the windows instance cannot find a bootable disk after the VHD was imported into an image gallery. The Linux instance worked after being imported.
The partial resource configuration (removed network profile to shorten)
"resources": [
        {
            "type": "Microsoft.Compute/virtualMachineScaleSets",
            "name": "[parameters('vmssName')]",
            "location": "[parameters('location')]",
            "apiVersion": "2017-12-01",
            "tags": "[parameters('tagValues')]",
            "identity": {
                "type": "SystemAssigned"
            },
            "sku": {
                "name": "[parameters('vmSku')]",
                "capacity": "[parameters('instanceCount')]"
            },
            "properties": {
                "overprovision": false,
                "upgradePolicy": {
                    "mode": "Manual"
                },
                "virtualMachineProfile": {
                    "diagnosticsProfile": {
                        "bootDiagnostics": {
                            "enabled": true
                        }
                    },
                    "osProfile": {
                        "computerNamePrefix": "[parameters('vmssNamePrefix')]",
                        "adminUsername": "[parameters('adminUsername')]",
                        "adminPassword": "[parameters('adminPassword')]"
                    },
                    "storageProfile": {
                        "osDisk": {
                            "osType": "Windows",
                            "createOption": "FromImage",
                            "name": "myvhd",
                            "image": {
                                "uri": "[concat(parameters('storageAccountUri'),parameters('storageAccountImagePath'))]"
                            },
                            "vhd": {
                                "uri": "[concat(parameters('storageAccountUri'),'/',parameters('vmssname'),'-disk0.vhd')]"
                            }                        }
                    }
                }
            }
        }
    ]

And resulting deployment error:
New-AzResourceGroupDeployment: 5:37:34 PM - The deployment 'azuredeploywin' failed with error(s). Showing 1 out of 1 error(s).
Status Message: Parameter 'osDisk.vhd' is not allowed. (Code:InvalidParameter)
CorrelationId: fa841a31-8417-4e70-b8ab-75d240b0c37a

If name is an empty string or omitted, the following error appears instead:
New-AzResourceGroupDeployment: 5:44:28 PM - The deployment 'azuredeploywin' failed with error(s). Showing 1 out of 1 error(s).
Status Message: The entity name 'osDisk.name' is invalid according to its validation rule: ^[^_\W][\w-._]{0,79}(?<![-.])$. (Code:InvalidParameter)
CorrelationId: 3b16399d-a072-49bc-b514-7b41c3022ada

Thank you all for reaching out. This article has been updated and no longer contains any VMSS scripts, including any of the scripts identified in this issue. Because of this, I'm closing out this issue.
#please-close


Build failures after (re)moving a package

I'm working on #10175 and need to move the fttpack c/fortran sources as part of the transition from scipy.fftpack to scipy.fft. However, whenever I try to do this, the build always fails; even for packages unrelated to fftpack.
I think this is related to the build definitions for native extensions. Are these declared somewhere seperately from setup.py?
Minimum example:
Comment out this line:
https://github.com/scipy/scipy/blob/be97f1a038ef6e3055cfbc83b9550492052ba76b/scipy/setup.py#L11
Error message:

building 'scipy.spatial.qhull' extension
compiling C sources
C compiler: x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC

compile options: '-DHAVE_CBLAS -I/usr/include/python3.6m -I/home/peter/.local/lib/python3.6/site-packages/numpy/core/include -Iscipy/_lib -I/home/peter/.local/lib/python3.6/site-packages/numpy/core/include -I/usr/include/python3.6m -c'
x86_64-linux-gnu-gcc: scipy/spatial/qhull_src/src/mem_r.c
x86_64-linux-gnu-gcc: scipy/spatial/qhull_src/src/qset_r.c
x86_64-linux-gnu-gcc: scipy/spatial/qhull_src/src/random_r.c
x86_64-linux-gnu-gcc: scipy/spatial/qhull_src/src/rboxlib_r.c
scipy/spatial/qhull_src/src/qset_r.c: In function ‘qh_setfree’:
scipy/spatial/qhull_src/src/qset_r.c:718:10: warning: variable ‘freelistp’ set but not used [-Wunused-but-set-variable]
   void **freelistp;  /* used if !qh_NOmem by qh_memfree_() */
          ^~~~~~~~~
scipy/spatial/qhull_src/src/qset_r.c: In function ‘qh_setnew’:
scipy/spatial/qhull_src/src/qset_r.c:928:10: warning: variable ‘freelistp’ set but not used [-Wunused-but-set-variable]
   void **freelistp; /* used if !qh_NOmem by qh_memalloc_() */
          ^~~~~~~~~
x86_64-linux-gnu-gcc: scipy/spatial/qhull_src/src/usermem_r.c
scipy/spatial/qhull_src/src/random_r.c: In function ‘qh_argv_to_command’:
scipy/spatial/qhull_src/src/random_r.c:84:6: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation]
     }else
      ^~~~
scipy/spatial/qhull_src/src/random_r.c:86:7: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘else’
       strcat(command, s);
       ^~~~~~
x86_64-linux-gnu-gcc: scipy/spatial/qhull_src/src/userprintf_r.c
x86_64-linux-gnu-gcc: scipy/spatial/qhull_src/src/userprintf_rbox_r.c
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-Bsymbolic-functions -Wl,-z,relro -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.6/scipy/spatial/qhull.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/geom2_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/geom_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/global_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/io_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/libqhull_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/mem_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/merge_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/poly2_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/poly_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/qset_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/random_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/rboxlib_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/stat_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/user_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/usermem_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/userprintf_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/userprintf_rbox_r.o -Lbuild/temp.linux-x86_64-3.6 -lopenblas -lopenblas -o build/lib.linux-x86_64-3.6/scipy/spatial/qhull.cpython-36m-x86_64-linux-gnu.so -Wl,--version-script=build/temp.linux-x86_64-3.6/link-version-scipy.spatial.qhull.map
build/temp.linux-x86_64-3.6/scipy/spatial/qhull.o: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
Running from scipy source directory.
/home/peter/.local/lib/python3.6/site-packages/numpy/distutils/system_info.py:730: UserWarning: Specified path /usr/local/include/python3.6m is invalid.
  return self.get_paths(self.section, key)
error: Command "x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-Bsymbolic-functions -Wl,-z,relro -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.6/scipy/spatial/qhull.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/geom2_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/geom_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/global_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/io_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/libqhull_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/mem_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/merge_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/poly2_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/poly_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/qset_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/random_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/rboxlib_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/stat_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/user_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/usermem_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/userprintf_r.o build/temp.linux-x86_64-3.6/scipy/spatial/qhull_src/src/userprintf_rbox_r.o -Lbuild/temp.linux-x86_64-3.6 -lopenblas -lopenblas -o build/lib.linux-x86_64-3.6/scipy/spatial/qhull.cpython-36m-x86_64-linux-gnu.so -Wl,--version-script=build/temp.linux-x86_64-3.6/link-version-scipy.spatial.qhull.map" failed with exit status 1

Important parts:
qhull.o: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
Running from scipy source directory.
/home/peter/.local/lib/python3.6/site-packages/numpy/distutils/system_info.py:730: UserWarning: Specified path /usr/local/include/python3.6m is invalid.
  return self.get_paths(self.section, key)

This message is for qhull but if I build in parallel, every extention will fail to build with similar "File format not recognized" errors.

I'm working on #10175 and need to move the fttpack c/fortran sources as part of the transition from scipy.fftpack to scipy.fft.

Given that scipy.fftpack needs to stay working, I don't think you should move the fftpack sources. Just import the parts that are needed (i.e. the ones not in Pocketfft) from scipy.fftpack.

However, whenever I try to do this, the build always fails; even for packages unrelated to fftpack.
I think this is related to the build definitions for native extensions. Are these declared somewhere seperately from setup.py?

Each submodule has its own setup.py. All the extension build config is in those files, there's nothing else.

Given that scipy.fftpack needs to stay working, I don't think you should move the fftpack sources. Just import the parts that are needed (i.e. the ones not in Pocketfft) from scipy.fftpack.

The plan is to eventually remove the fortran code entirely so that scipy.fftpack use the same implementation as scipy.fft.  But for the time being, scipy.fft needs to used to fortran code for DST, DCT and other functionality.  To avoid a cyclic dependency, I move everything into scipy.fft and scipy.fftpack calls into scipy.fft. Does that make sense?

Okay, it could make sense. You may avoid indeed a cyclic dependency if scipy.fftpack is halfway through a transition to Pocketfft. I was more thinking the plan was to leave scipy.fftpack completely alone though. I'm not remembering a particular reason for not moving it to Pocketfft right now. And deleting Fortran code would be quite nice:)
For moving the code, think about how to preserve git history. The easiest would probably be to (starting from master) rename fftpack to fft in the source in a single commit (should just have to touch 2 setup.py files and one directory name), and then add back a new fftpack module in following commits.

For moving the code, think about how to preserve git history.

:+1: that's exactly what I'm trying to do.

Great. Also, this is a good opportunity to put underscores in all the names that are nonpublic for scipy.fft. Which is pretty much everything. So all Python file names - scipy.fftpack.realtransforms should become scipy.fft._realtransforms (if you're moving that file).

I was actually thinking that (in anticipation of backend support) it would be better to put everything in a subpackage scipy.fft._fftpack and setup __all__ as if they were directly in scipy.fft.  Doing it this way I shouldn't need undersores, correct?

Oh yes, that works too. No need for underscores inside _fftpack then.

I managed to get scipy to build again after uninstalling python and reinstalling with the latest version. Not sure what went wrong but I it seems the issue wasn't with scipy itself.


Check in poetry.lock into source control (PACMAN-637)

Related area
git
Is your feature request related to a problem?
There is no lock file in source control. This makes packaging this tool difficult (I do update this environment https://github.com/mirrexagon/nixpkgs-esp-dev)
Describe the solution you'd like
I see .gitignore says poetry.lock was removed because of tests. Maybe this could be done during test environment preparation?
Describe alternatives you've considered
No response
Additional context
No response
I have checked existing list of Feature requests and I have provided enough information.

[X] I confirm I have checked existing list of Feature requests and I have provided enough information.

Thanks for the reply!
I think I could, will try, thank you for the explanation!

@corpix In a coming release of 2.0.0 we will remove setup.py, but still won't add a lock file. What is the main problem of packaging without a lock file?

@corpix I would like to close this issue now, however you are welcome to reopen if you want to discuss this topic further.


Master

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: hekuangsheng:x: singgelhekuangsheng seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Conda availability

I was going to update to the new version of lava. I am curious whether lava-dl will be available to be installed from conda ?

Objective of issue:

Lava DL version:

[ ] 0.3.0 (feature release)
[ ] 0.2.1 (bug fixes)
[x] 0.2.0 (current version)
[ ] 0.1.2

Lava version:

[ ] 0.4.0 (feature release)
[ ] 0.3.1 (bug fixes)
[x] 0.3.0 (current version)
[ ] 0.2.0
[ ] 0.1.2

I'm submitting a ...

[ ] bug report
[ ] feature request
[ ] documentation request

Current behavior:

Expected behavior:

Steps to reproduce:

Related code:

insert short code snippets here

Other information:

insert the output from lava debug here

Hi @ahmetakman, yes lava-dl is available on conda: https://github.com/conda-forge/lava-dl-feedstock. I have not tried it personally though. I think Prof. Tobias Fischer is the maintainer of it.

got it, thanks


add support for .fi tld

Codecov Report

Merging #20 into master will decrease coverage by 0.23%.
The diff coverage is 90.9%.

@@            Coverage Diff             @@
##           master      #20      +/-   ##
==========================================
- Coverage     100%   99.76%   -0.24%
==========================================
  Files           3        3
  Lines         834      855      +21
==========================================
+ Hits          834      853      +19
- Misses          0        1       +1
- Partials        0        1       +1

Impacted Files
Coverage Δ

parser.go
100% <100%> (ø)
:arrow_up:

prepare.go
99.68% <90.47%> (-0.32%)
:arrow_down:

Continue to review full report at Codecov.

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

Hello @jawr
Thanks for your PR, but it seems that the Holder is not correctly parsed.

My bad, I didn't realise fi_google.fi.out was being overwritten so assumed the tests were working against my hand generated version! Will fix


[BUG] Elasticsearch Curator version out of date

Describe the bug
Elastic Curator version out of date for Ubuntu/Redhat/Centos (5.8.1)
We should upgrade Elasticsearch Curator to version which is available on all supported os distributions (5.8.3)
How to reproduce
Run the normal build regression test daily
Expected behavior
Build passed
Additional context
PR has been created please see https://github.com/epiphany-platform/epiphany/pull/1960

✅ Installation with enabled elasticsearch-curator component tested. No issues found.

✅ Installation with enabled elasticsearch-curator component tested. No issues found.


Circle 2.0

Use the CircleCI 2.0 API, allowing builds to run in parallel.
See https://circleci.com/workflow-run/3cc34799-f1af-4977-8549-e04d3331f1e9

Note that there is an older attempt by me:
https://github.com/nponeccop/haskell-ide-engine/tree/master/.circleci
I'll review it and check if there are any features in my code worth integrating


Enhanced Error Code Flag Support

Adding Flags to disable/enable test with  enhanced error code in UT.

merged to develop


[openwrt] fix leaderpartitionid

@simonlingoogle , the openwrt-check on Travis is currently failing.

@simonlingoogle , the openwrt-check on Travis is currently failing.

I am aware of that.
Discussed with @bukepo, we agreed that we can change preferredpartitionid to partitionid because 1) otThreadGetPreferredLeaderPartitionId is only available for reference device, and 2) displaying preferred partition id makes less sense than the actual partition id.

WIP :Unable to pass LGTM C++ check and the error log seems not provide any meaningful information.

Should we disable LGTM.com check for now to unblock PRs? @jwhui

A fix has been submitted https://github.com/github/codeql/issues/4809#issuecomment-743142125. I kicked LGTM.com to see if it will pass now.


$this.router.push() gives 404 in deployment but works locally

Description
Hi there - i've used git to push my dist folded to my hosting site - however the page routing is now not working.
(I have used this host to display other Vue.js websites which use the same principle to reroute below, which has worked so I don't think the error is in the method.... this being said, i might be wrong) -
Any help would be great
I use router.push to change the page - this works locally
methods: {
        reroutePage(route){
            this.$router.push(route)
        }
    }

Argument above is the route name - which is the same as the Pages name i.e.
pages/Clients.vue
reroutePage('Clients')
Steps to reproduce
I have pushed Gridsome dist to Namecheap (shared hosting) - this might be the issue?
but I was under the impression that Gridsome generated static files.
Expected result
routing should change the current page to the desired page
Actual result
404 error is shown that page cannot be found

locally this works

Environment
Paste the information here as shown by gridsome info

I have uploaded a fresh copy of gridsome to my host (nameCheap) - the linking here is working so I assume that this is caused by my code - or how gridsome handles the $router ?

Issue located -
The dist folder changed the router from "Clients" to "clients"
not sure what to make of that at current


setTimeout throws 500 exception while using cortana with bot framework

Bot Info

Bot handle: EchoTestHandle
App ID: bf7c0616-9744-424e-b71f-ab7c3b1cdacc
SDK Platform: Node.js
SDK Version: 3.11
Active Channels: Cortana, WebChat
Deployment Environment: ngrok

Issue Description
setTimeout throws 500 exception while using cortana with bot framework. It works fine with the web chat, and emulator
Code Example

var bot = new builder.UniversalBot(connector, function (session) {
session.send("Hello");
setTimeout(function () {
session.send("This does not execute in Cortana");
}, 1000);
});
Expected Behavior
I should be able to make async requests
Actual Results
Error: Request to 'https://CortanaBFChannelWestUS.azurewebsites.net/v3/conversations/978fef30-343f-4e97-8b1c-61142f2071cf/activities/DAc2oW4tPca' failed: [500] Internal Server Error
at Request._callback (/Users/ayushgera/Development/Hack2017/cortanaBot/node_modules/botbuilder/lib/bots/ChatConnector.js:532:46)
at Request.self.callback (/Users/ayushgera/Development/Hack2017/cortanaBot/node_modules/request/request.js:186:22)
at emitTwo (events.js:87:13)
at Request.emit (events.js:172:7)
at Request. (/Users/ayushgera/Development/Hack2017/cortanaBot/node_modules/request/request.js:1163:10)
at emitOne (events.js:77:13)
at Request.emit (events.js:169:7)
at IncomingMessage. (/Users/ayushgera/Development/Hack2017/cortanaBot/node_modules/request/request.js:1085:12)
at IncomingMessage.g (events.js:260:16)
at emitNone (events.js:72:20)
at IncomingMessage.emit (events.js:166:7)
at endReadableNT (_stream_readable.js:893:12)
at doNTCallback2 (node.js:429:9)
at process._tickDomainCallback (node.js:384:17)

@potatoParadox
The Cortana channel does not currently accept proactive messages. It is a highly requested feature, and should be available sometime soon. However, there is currently no timeline.


Sietse and Johannes should be moved?

AFAIK They graduated, should they be moved to the Alumni section?

Are you sure that this is the right repo to report that? I cannot see any mention of their names in here...


[docs] Link Material UI from the landing page

Problem
Take https://search.google.com/search-console/performance/search-analytics, developers were quick to jump into the opportunity to replace their search for "material ui" to "mui", I imagine because it's faster to type:

Noooo
Solution

Make landing on https://mui.com/material-ui/ from Google a faster way to reach Material UI docs than landing on https://mui.com/. So reduce the advantage of the shorter "mui" search query over typing "material ui".
Break the narrative of MUI homepage hosting the installation instructions of Material UI

Preview: https://deploy-preview-37971--material-ui.netlify.app/
It will be even better with #37608

It will be even better with https://github.com/mui/material-ui/pull/37608

@oliviertassinari were you thinking of linking the Core page instead? Something like "Discover the Core products"?

Were you thinking of linking the Core page instead? Something like "Discover the Core products"?

@danilo-leal Not necessarily but it sounds like a good option. Do you have a preference?

It's tricky as we don't have anything immediately better to link to, but maybe directing to the Core page is better than having the main call to action of the homepage directing to the Material UI docs, which, to me, only reinforces the "MUI equals to Material UI" confusion.
Definitely looking forward to revamping the homepage soon so it better exposes everything we have to offer and then possibly coming up with another destination for the main cta but, for the time being, maybe that's a bit better? It doesn't necessarily make getting to the Material UI docs faster, though.


No error shown when typescript.tsdk points to invalid path

Testing #31785
/usr/local/lib/node_modules/typescript/bin2 doesn't exist.
But the version selector doesn't seem to mind

According to the below, it should fall back to the bundled one, but it doesn't

Set typescript.tsdk to an invalid path. An error message should be shown and we should fallback to the bundled ts version

The currently behavior is that we only show an error when you try to pick that item. Do you see a warning message about using the bundled version of TS when you open a JS or TS file?

Yes, I see the error after picking the item. But it is helpful if we can indicate something is wrong, before the user chooses the item.
One thing to do is when we can't figure out the version, then show a warning/message next to the label instead of showing the whole path again

Ok, here's the UI for presenting this as an error:

In 1.14 I got a warning popup when I set the tsdk path to something invalid, The path /foo/bar doesn't point to a valid tsserver install. Falling back to bundled TypeScript version. In 1.15 I get the warning above, but not the notification. Is that expected? It seems worth a notification.

@roblourens It should still show the warning. Can we take a look at this?

NVM, I do see it.


Add sanity checks to check for full path or check for local dir

If a user does not provide a full path, either add a path sanity check or a check for a local dir.
Example below: I entered "temp" as the directory name instead of a full path name. This causes a crash and a stale github lockfile.
If you specify a relative path "./temp" then the mrcli will work as expected.
? It appears you'd like to create a new interaction, right? Yes
Checking if the mediumroast.io app is ready to add interactions ... Ok
? Which company are these interaction(s) associated to? ProductPlan
? What's the full path to the directory (e.g., /dir/subdir)? temp  <--- this will cause an error and leave a stale github lock

Fixed


Expose NullableTokens and ThemeVars types

This facilitates a use case described in #309 where user wants to create their own version of createThemeContract to make var names predictable.

Closing in favor of #319


Add documentation warnings for experimental use cases

It would be valuable to introduce a flexible documentation process to add visual callouts (like Warning, experimental, this will delete your DID, etc).
I like the visuals proposed by @alexfornuto on Slack:

@Flaxscrip let me make sure I understand this issue.
We already have the ability to make these callouts ad-hoc. What I described out-of-band was an a way to quickly add repeatable callouts about things like experimental, alpha, and beta stage features to either the entire site or the top of a specific pages.
For site-wide notes, we can add a key/value combo to docusaurus.config setting the release stage of the project. I'm leaning towards page=-specific front-matter. While that would be more effort early on, it's more future-proof methodology when the project becomes stable and we introduce experimental/alpha/beta features ad-hoc.
Thoughts?

Thank you for clarifying. I like your callouts in the documentation. It allows us to excuse the low-security kc client; the calliuts help future wallet developers (like SelfID) to pay particular attention to the functionality.
tldr: up to your judgement. It's OK to spend some time building functionality we will reuse.


also sanitize results, attributes, owned_regions, and successors.

hopefully fixes https://github.com/JuliaLabs/MLIR.jl/issues/40

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

Comparison is base (c370d5c) 1.90% compared to head (b0df877) 1.90%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@          Coverage Diff          @@
##            main     #43   +/-   ##
=====================================
  Coverage   1.90%   1.90%
=====================================
  Files        107     107
  Lines      26054   26054
=====================================
  Hits         496     496
  Misses     25558   25558

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


Add support for Windows and update GitHub Actions

yarn.lock must be in source control (read this)
Use cross-env to allow the compilation on Windows environments
Update the GitHub Actions to make it to work with our new GitHub environment
Add CodeQL to analyze source code on build

@FabienLavocat I will close this PR and incorporate the changes based on the upcoming set of changes.


Minor: Improve PruningPredicate documentation

Which issue does this PR close?
Related to https://github.com/apache/arrow-datafusion/issues/8376
Rationale for this change
As part of https://github.com/apache/arrow-datafusion/issues/8376 I have been rereading the code and familiarizing myself with how it works, which I wanted to include as comments for the future.
Since this doesn't make any code changes, I broke it into its own PR for easier review
What changes are included in this PR?
Update doc comments
Are these changes tested?
N/A

Are there any user-facing changes?
Better documentation, no functional changes

Thank you for the review @viirya


Cursor Position Lost on Hot Reload (Live)

When I try to change code in the reval editor for komentify the cursor in the inline editor jumps out as soon as the file is hot reloaded.
Expected: The cursor stays in the editor.

For additional context, I'm using the useraccounts package which for some reason seems to autofocus into the email / username input field.

Have you tried disabling the focusFirstInput option?
https://github.com/meteor-useraccounts/core/blob/e5bb229fa7c87d3f275c3c822af47a674284b382/lib/templates_helpers/at_input.js#L7

No I didn't, thanks for the hint! Since this issue has to do with the user accounts having some focus logic I'll close this ticket.


 They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
Package bzip2 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Unable to locate package wget
E: Unable to locate package git
E: Unable to locate package libxrender1
E: Unable to locate package libsm6
E: Package 'bzip2' has no installation candidate
The command '/bin/sh -c apt-get update &&     apt-get install -y -q wget git libxrender1 libsm6 bzip2 &&     apt-get clean' returned a non-zero code: 100


Windows update killed Superputty (think)

Describe the bug
After a Window 7 update Superputty begins to start then after a minute it's back to icon. part of the Windows log in my user Appdata folders is below.
System.ComponentModel.Win32Exception: The parameter is incorrect
at System.Drawing.Icon.Initialize(Int32 width, Int32 height)
To Reproduce
Steps to reproduce the behavior:

Go to Windows
Click on Superputty
Scroll down to NA
See error NA

Expected behavior
Superputty launches with all my store sessions
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
I had IT support "help" me but they couldn't get it working, updated .NET and reinstalled.

Same issue here, updated win 7 last night, and now superputty does not open.  This looks to be terminal, time to find a new terminal :/

2020-02-22 10:26:35,665 [1] INFO  SuperPutty.Program - Starting
2020-02-22 10:26:35,679 [1] INFO  SuperPutty.SuperPuTTY - Initializing.  Version=<IP_ADDRESS>, UserSettings=C:\Users\blajoie\SuperPuTTY.settings, SettingsFolder=C:\Users\blajoie\Documents\SuperPuTTY
2020-02-22 10:26:35,696 [1] WARN  SuperPutty.SuperPuTTY - theme directory not found, no images loaded. dir=C:\windows\system32\themes\default\icons
2020-02-22 10:26:35,704 [1] INFO  SuperPutty.SuperPuTTY - Loaded 0 layouts
2020-02-22 10:26:35,707 [1] INFO  SuperPutty.SuperPuTTY - Loading all sessions.  file=C:\Users\blajoie\Documents\SuperPuTTY\Sessions.XML
2020-02-22 10:26:35,828 [1] INFO  SuperPutty.Data.SessionData - Loaded 10 sessions from C:\Users\blajoie\Documents\SuperPuTTY\Sessions.XML
2020-02-22 10:26:35,829 [1] INFO  SuperPutty.SuperPuTTY - Added Session, id=asus
2020-02-22 10:26:35,829 [1] INFO  SuperPutty.SuperPuTTY - Added Session, id=ukch-prd-brln
2020-02-22 10:26:35,829 [1] INFO  SuperPutty.SuperPuTTY - Added Session, id=usfc-prd-brln
2020-02-22 10:26:35,829 [1] INFO  SuperPutty.SuperPuTTY - Added Session, id=ussd-dev-cldg01
2020-02-22 10:26:35,829 [1] INFO  SuperPutty.SuperPuTTY - Added Session, id=ussd-dev-lnbl01
2020-02-22 10:26:35,829 [1] INFO  SuperPutty.SuperPuTTY - Added Session, id=ussd-dev-lnbl02
2020-02-22 10:26:35,830 [1] INFO  SuperPutty.SuperPuTTY - Added Session, id=ussd-rnd
2020-02-22 10:26:35,830 [1] INFO  SuperPutty.SuperPuTTY - Added Session, id=ussd-sccs
2020-02-22 10:26:35,830 [1] INFO  SuperPutty.SuperPuTTY - Added Session, id=ussd-services
2020-02-22 10:26:35,830 [1] INFO  SuperPutty.SuperPuTTY - Added Session, id=ussd-tst-drgn37
2020-02-22 10:26:35,831 [1] INFO  SuperPutty.SuperPuTTY - Starting with default layout, <Auto Restore>
2020-02-22 10:26:35,833 [1] INFO  SuperPutty.Utils.SingleInstanceHelper - Registered IpcChannel and Service: [ipc://SuperPuTTY/SingleInstance]
2020-02-22 10:26:35,835 [1] INFO  SuperPutty.SuperPuTTY - Initialized
2020-02-22 10:26:36,045 [1] ERROR SuperPutty.Program - Error in Main
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ComponentModel.Win32Exception: The parameter is incorrect
   at System.Drawing.Icon.Initialize(Int32 width, Int32 height)
   at System.Drawing.Icon..ctor(SerializationInfo info, StreamingContext context)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._SerializationInvoke(Object target, SignatureStruct& declaringTypeSig, SerializationInfo info, StreamingContext context)
   at System.Runtime.Serialization.ObjectManager.CompleteISerializableObject(Object obj, SerializationInfo info, StreamingContext context)
   at System.Runtime.Serialization.ObjectManager.FixupSpecialObject(ObjectHolder holder)
   at System.Runtime.Serialization.ObjectManager.DoFixups()
   at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Resources.ResourceReader.DeserializeObject(Int32 typeIndex)
   at System.Resources.ResourceReader.LoadObjectV2(Int32 pos, ResourceTypeCode& typeCode)
   at System.Resources.RuntimeResourceSet.GetObject(String key, Boolean ignoreCase, Boolean isString)
   at System.Resources.ResourceManager.GetObject(String name, CultureInfo culture, Boolean wrapUnmanagedMemStream)
   at SuperPutty.frmSuperPutty.InitializeComponent()
   at SuperPutty.frmSuperPutty..ctor()
   at SuperPutty.Program.Main(String[] args)
2020-02-22 10:26:36,050 [1] INFO  SuperPutty.Program - Shutdown

p.s. for any others affected.  A windows restore does fix this issue.

I had the same thing when this update was installed
https://support.microsoft.com/en-ca/help/4537813/windows-7-update-kb4537813

I had the same thing when this update was installed
https://support.microsoft.com/en-ca/help/4537813/windows-7-update-kb4537813

Just found this reference in the MSDN forums, seems to be an issue with an icon definition in the resx file for the frmSuperPutty form (if I read this correctly)
https://social.msdn.microsoft.com/Forums/en-US/b7cdcdc6-522f-4ea3-9764-cbaa9715d595/kb4537820-causes-systemcomponentmodelwin32exception-in-net-framework-systemdrawingicon-for?forum=clr

Has anyone found a way to launch SuperPuTTY with the patch installed?

I think this is DOA... RIP superPutty :/

Nope.  I think this is DOA... RIP superPutty.
On Thu, Mar 5, 2020 at 7:26 AM Tim<EMAIL_ADDRESS>wrote:

Has anyone found a way to launch SuperPuTTY with the patch installed?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jimradford/superputty/issues/782?email_source=notifications&email_token=ACD2ITGLATWDQKFTIOPGI2LRF7ACHA5CNFSM4KX7KHY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEN5WBWA#issuecomment-595288280,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACD2ITF5K5RVEAIY6IEIZATRF7ACHANCNFSM4KX7KHYQ
.

Is the trouble you are having launcing SuperPutty or is it opening up new terminals?
I am pretty sure I can fix this with a little help from you guys. What patch / update are you referring to?
Jim

I have having the same issue. It happens when launching SuperPutty. However, I tried deleting the SuperPuTTY.settings file and it will open the window to setup putty etc. After that SuperPutty will not work.

The issue is with opening super-putty.  See above for the error message.
https://github.com/jimradford/superputty/issues/782#issuecomment-589984648
Something to do with a .NET update ?
I have tried <IP_ADDRESS> & <IP_ADDRESS> - both have the same issue.

Is the trouble you are having launcing SuperPutty or is it opening up new terminals?
I am pretty sure I can fix this with a little help from you guys. What patch / update are you referring to?
Jim

Hey Jim,
I posted the update link and a reference to the possible issue above:
https://github.com/jimradford/superputty/issues/782#issuecomment-590861263

Any way to launch SuperPUTTY without uninstalling that patch? I am facing the same issue.

Any way to launch SuperPUTTY without uninstalling that patch? I am facing the same issue.

Same situation here; patched Win7 not able to start SuperPuTTY with the same messages in the log file as mentioned above. My neighbor is running SuperPuTTY on Windows 10 with no issue, so that may be an option for you (your mileage may vary).

Gents, same issue, vote +1 - after latest Windows Update on top of Windows 7 (on OS or on .NET Framework - not sure, but can find, if needed) - SuperPutty (v.<IP_ADDRESS>) failed to start. Log file %TEMP%\SuperPutty_[date]_[time].log shows same error as in above posted Comment #782:
System.Reflection.TargetInvocationException:
Exception has been thrown by the target of an invocation.
---> System.ComponentModel.Win32Exception: The parameter is incorrect

Trying to delete all existing conf. files:
%APP_FOLDER%\SuperPutty.exe.config
%APP_FOLDER%\Settings\Layout\Sessions.XML
%USERPROFILE%\SuperPutty\Sessions.XML
%USERPROFILE%\SuperPutty.settings

... result is the same, i.e. no difference. In logilfe (in %TEMP% folder) I can see messages that particular conf. file not found - during load of Layout or during load of Sessions - but on overall situation that does not have any effect - at the end same errror "The parameter is incorrect".
Maybe one interesting finding, even not important within current investigation - "just to know": attempt to delete %USERPROFILE%\Sessions.XML file - during start of application, SuperPutty.exe detects that Sessions.XML does not exists - and prints into log following confusing message:
Exception has been thrown by the target of invocation.
< ... cut ... >
The operation completed successfully.

I.e. in one row - "Exception encountered" and "Completed successfully". How to interpret such behavior - don't know. Subsequent starts of SuperPutty.exe - continued "standard" error, i.e. "The parameter is incorrect".

Hi! Same issue here. One thing I see is that SuperPutty says it has loaded 38 icons from the icons folder -- however there are only 36 files in the folder. So unless some files have multiple icons that looks like an error.
thanks!

Hi.
We have the same situation here, some users are not able to use SuperPuTTY any more.
I stressed several Windows 7 based test environments to figure out, what makes the difference between the one where it still works and where not.
All machines have this Win7 update, but most of the users can still use SuperPuTTY without any problem, but some not.

Same here, after upgrading my laptop at work.

10 :)
We are several co-worker having the same issue

started observing same issue....is anyone working on it?

I'm experiencing the same issue as are handful of my colleagues who use the application regularly.  Happy to provide any information that might aid in finding a fix.  Seems to be the same scenario as many other commenters, after installing a .NET update in Win7 64-bit machines.

someone is working on it ?
thanks.

Hey there,
OK....MSFT might have actually fixed something.  My machine updated with a number of patches last night and today, when I started SuperPutty, it came up!  One of the patches was called:
March 10, 2020—KB4541500 (Security-only update)
This is the only one that matches the one that seemed to cause the issue that I mentioned above.  Has anyone else installed the latest patches from Microsoft and if so, does SuperPutty work again for them?
Thanks,
Sean

Same here...boo-hoo. Struggled through all the steps everyone else tried and now ended up here.
Thanks MSFT!
I cannot install the security update myself - its a company laptop.
Will have to wait for them to catch up with the latest update.
Friends laugh at me when I tell them I disable all updates because they are more trouble than they are worth! I wait for everyone else to be the guinea pigs! In this case I had no choice.
SuperPuTTY.20200324_112728.log

@jimradford - can you take a look at this PR?  Is this the fix?
https://github.com/jimradford/superputty/pull/786

Hey there,
OK....MSFT might have actually fixed something. My machine updated with a number of patches last night and today, when I started SuperPutty, it came up! One of the patches was called:
March 10, 2020—KB4541500 (Security-only update)
This is the only one that matches the one that seemed to cause the issue that I mentioned above. Has anyone else installed the latest patches from Microsoft and if so, does SuperPutty work again for them?
Thanks,
Sean

This may be the one that fixed it. Checked my PC, which received this update on 3/26, and I can happily report SuperPuTTY works again!

@jimradford - can you take a look at this PR? Is this the fix?
#786

Egads! yes, I somehow missed this.

getting "couldn't agree key exchange algorithm" Error using SUperPutty. Any fix for this.

@dariyappa Please open a new issue as what you mention does not seem to be related. (Hint: Your server is probably not supporting any of the ciphers in putty. 1) can you connect to that host with putty all by itself? 2) try upgrading to putty 0.65 or later)

I might be facing this in Windows 10 as well. More details in #815 .
Do you think it is the same issue?


Implement Salvaging

Implement the salvaging economy, surrounding the new Salvage good, the scavenging buildings and the the sorting building.

See changed approach described in #20


[#5066] refactor(drop-catalog): re-define drop catalog

What changes were proposed in this pull request?

Add an in-use property to the catalog with the default value of true.
Only empty catalog with in-use=false can be dropped.
User can use dorce option to drop catalog
More drop catalog limitations please see the JavaDoc of dropCatalog in API module

Why are the changes needed?
Fix: #5066
Does this PR introduce any user-facing change?
yes, users now can not drop an in used catalog
How was this patch tested?
tests added

Do you also need to update the doc?

Doc will be updated in final PR

All comments are resolved, plz help to review again, thx! @yuqi1129 @jerryshao

Can you please fix the CI failure?


Audio & Bullet images added to enemies

Closes #144
Close #143

@BrandonPacewic No ready to merge

I'm getting ready to merge and updating the change log - please @me if any other changes are pushed.


Tab completion for --target uses rustup but fallsback to rustc

What does this PR try to resolve?
Fixes #12585
Currently, not only is the tab completion for --target inconsistent between bash and zsh, it depends on rustup and rustc respectively.
As discussed in the issue at hand, we'll use rustup if it is available and fallback to rustc if it is not, even if it is unfriendly.
How should we test and review this PR?
Source the respective completion functions and test it out with cargo build --target [TAB].
I would appreciate if someone that regularly uses zsh would test this. I did basic testing, but since I don't use zsh commonly I am unsure if everything is as it should be.
Additional information
I switched to using rustup target list --installed instead of grabbing lines that contain "default" or "installed". I believe that any "default" target should be installed too, right?

Tested both with and without rustup in bash and zsh. Everything goes well on my side.
Thank you for the contribution :)
@bors r+

:hourglass: Testing commit b5c97d458113705e3639c36bd40021543f32cd49 with merge 11966a498fd4d8322bc3170d311f611a3bd909bb...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 11966a498fd4d8322bc3170d311f611a3bd909bb to master...


Remove managed InProcess code

https://github.com/aspnet/IISIntegration/issues/807

Change itself looks good. Will thoroughly investigate once Shiproom approved.

Build failure due to an obsolete namespace.


PostgreSQL Hyperscale Deployment on EKS - data controller deployment failure

Scenario which you are working on
https://azurearcjumpstart.io/azure_arc_jumpstart/azure_arc_data/eks/eks_postgres_hs_terraform/
Describe the bug
At "Windows Login & Post Deployment" stage when script is running inside windows client machine there is an error during deployment of Azure data controller:
{"error":{"code":"InvalidTemplateDeployment","message":"The template deployment 'dataController' is not valid according to the validation procedure. The tracking id is '1dd0e5aa-a47e-49a4-86dd-1cb8918d35d2'. See inner errors for details.","details":[{"code":"OpenAPISpecValidationFailedForTemplateDeploymentResources","message":"One or more resources in template deployment preflight validation request failed during OpenApi spec (swagger) validation. Please check error details for the resource identifiers.","details":[{"code":"HttpRequestPayloadAPISpecValidationFailed","target":"/subscriptions/a088ac12-28e0-48d5-a00d-9f5d48c7cfbb/resourceGroups/RG/providers/Microsoft.AzureArcData/dataControllers/jumpstart-dc","message":"HTTP request payload failed validation against API specification with one or more errors. Please see details for more information.","details":[{"code":"InvalidFormat","message":"Object didn't pass validation for format uuid: . Paths in payload: '$.properties.logAnalyticsWorkspaceConfig.workspaceId'"}]}]}]}}
As a result, data controller is not deployed and script waits for it indefinitely. I tried the entire scenario from scratch and got the same error.
To Reproduce
Steps to reproduce the behavior:

Follow steps from "Deploy an Azure PostgreSQL Hyperscale Deployment on EKS using Terraform" scenario

Expected behavior
Data controller is deployed
Script output
arc.txt

Thanks @ischepin.
It looks like this scenario doesnt have the same guidance to show how to create the user and attach correct permissions. In the Azure Arc-enabled servers AWS scenarios we do show this, so we should mirror our approach from those scenarios in the AWS data services scenarios.
I also notice that we have the same missing explanation in the EKS kubernetes-only scenario.

Thanks for flagging this @ischepin - I was able to repro the issue.
This PR should fix it: https://github.com/microsoft/azure_arc/pull/744 - I've validated on EKS.
The issue was ARM added an extra layer of validation in to check for Log Analytics WS Params - which weren't being passed in via Terraform.
You have 2 options to proceed with the scenario:

Wait for the PR to get merged. Tear down your existing env, refresh your fork from main
Look at the PR - in your existing env, run the cli commands from the PR to deploy the WS. Replace the DC deployment ARM templates from main, run this portion to update the placeholder in the ARM templates. Redeploy the DC ARM templates, and you should be able to deploy Postgres after that.

I'm going to keep the issue open until the PR is merged in.


[Snyk] Security upgrade org.testng:testng from 6.14.3 to 7.7.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `maven` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

pom.xml

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

539/1000  Why? Has a fix available, CVSS 6.5
Arbitrary File Write via Archive Extraction (Zip Slip) SNYK-JAVA-ORGTESTNG-3040285
org.testng:testng:  6.14.3 -> 7.7.0
Yes
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

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


Version 1.3.0 is not available on maven central

The latest version available via maven is the old 1.2.0 version.
Also, the current version of the README still mentions 1.2.0 instead of the latest release, which is 1.3.0.

Hi @martinschickbichlerspie, thanks for reporting! We're internally tracking this issue as INFRA-1556.

Sorry for the long wait, I've redeployed release 1.3.0. Can you please check that it's working for you?


move ParallelLinuxPerfScriptStackSource to TraceEvent, fixes #1103

cc @brianrob

Please excuse me, but for some reason the build succeded on my machine while it should have failed.
It turns out that .NET Standard 1.6 is missing some very basic APIs and types like ApplicationException or Stream.Close:

https://apisof.net/catalog/System.ApplicationException
https://apisof.net/catalog/System.IO.Stream.Close()
https://apisof.net/catalog/System.Threading.Thread.CurrentCulture
https://apisof.net/catalog/System.Text.Encoding.Default
https://apisof.net/catalog/System.Diagnostics.Contracts.Contract.Requires(Boolean,String)

@brianrob I've added a rule to the project file to not compile these types for .NET Standard 1.6. I hope that it's OK.

namespace Diagnostics.Tracing.StackSources

As part of the move, let's change the namespace for these classes to be Microsoft.Diagnostics.Tracing.StackSources.

Refers to: src/TraceEvent/Stacks/Linux/LinuxPerfScriptEventParser.cs:15 in e3658a4. [](commit_id = e3658a44869cf778926d14c51d2b7dcdbd3ec563, deletion_comment = False)

namespace PerfView.Utilities

Let's put this one into Microsoft.Diagnostics.Tracing.Utilities.

Refers to: src/TraceEvent/Utilities/FastStream.cs:6 in e3658a4. [](commit_id = e3658a44869cf778926d14c51d2b7dcdbd3ec563, deletion_comment = False)

@adamsitnik I think it will be fine to not compile these types for the netstandard1.6 target.  I believe this is around for users of older runtimes (e.g. older desktop and .NET Core 1.x).  It's actually probably safe to remove the netstandard1.6 target entirely, but we don't need to do that now.

@brianrob thanks for the review! I've changed the namespaces (which was a good idea BTW)


Failed to load the preview-plus package

install following instructions from here: https://atom.io/packages/preview-plus#install
launch Atom

Fedora 21
Atom Version: 0.187.0
System: linux 3.17.4-301.fc21.x86_64
Thrown From: preview-plus package, v1.1.19
Stack Trace
Failed to load the preview-plus package
At Cannot find module 'event-kit'

Error: Cannot find module 'event-kit'
    at Module._resolveFilename (module.js:351:15)
    at Function.Module._resolveFilename (/usr/share/atom/resources/app/src/module-cache.js:383:52)
    at Function.Module._load (module.js:293:25)
    at Module.require (module.js:380:17)
    at require (module.js:399:17)
    at Object.<anonymous> (/home/tehardt/.atom/packages/preview-plus/lib/watch.coffee:6:13)
    at Object.<anonymous> (/home/tehardt/.atom/packages/preview-plus/lib/watch.coffee:40:4)
    at Module._compile (module.js:475:26)
    at Object.requireCoffeeScript (/usr/share/atom/resources/app/node_modules/coffee-cash/lib/coffee-cash.js:85:19)
    at Module.load (module.js:370:32)

Commands

Config
{
  "core": {}
}

Installed Packages
# User
preview-plus, v1.1.19

# Dev
No dev packages

updated with the new release. Please try

I installed v1.1.20 and this error is gone but now I am getting cannot find module 'lodash' - will open a new ticket for that

The package.json is updated..Check the latest Version


Document how to show parts of a page or component based on data

From support:
Need to know how to show parts of a page or component based on data, for example:
{% if data['over-18'] %}
  [ Over 18 content here ]
{% else %}
  [ Under 18 content here ]
{% endif %}

and
{{ govukRadios({
  idPrefix: "where-do-you-live",
  name: "where-do-you-live",
  fieldset: {
    legend: {
      text: "Where do you live?",
      isPageHeading: true,
      classes: "govuk-fieldset__legend--l"
    }
  },
  items: [
    {
      value: "england",
      text: "England"
    },
    {
      value: "scotland",
      text: "Scotland"
    },
    {
      value: "wales",
      text: "Wales"
    },
    {
      value: "northern-ireland",
      text: "Northern Ireland"
    } if (data['example'] == true)
  ]
}) }}

with the key part being if (data['example'] == true)
Related documentation
Not sure we have any
Suggestion
None yet apart from covering the topics as above
Evidence (where applicable)
From multiple support requests

related: #107

https://github.com/alphagov/govuk-prototype-kit-docs/pull/234

Moving to done as this PR has been merged.


In a channel with many playlists, how to include/exclude specific ones?

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
Lets say you archive a musical channel. The channel has playlists about music, shows, talks, events, and musicvideos.
How i can run yt-dlp https://www.youtube.com/@CHANNEL/playlists exclude:"shows,talks,events" include:"music". Iclude / exclude must work on the NAME of playlists. This can solve situation when a channel has many playlists eg. 200 playlists and you know what to include / exclude.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

See docs of --match-filters. Since multiple filters act as logical OR, you can add a --match-filter _type!=playlist to apply all other filters to only the playlists and not any videos. Something like
--match-filter "_type!=playlist" --match-filter "title!~=shows|talks"

thanks!


Wall-to-wall example

A few months ago @brendancol created a very nice example of running Datashader full screen with data covering the entire area, which is great for exploring data:
https://github.com/brendancol/simple-react-map
Here he runs a Python server for Datashader in one process in a terminal:
python server.py

and runs a JavaScript-based client (using React and Leaftlet) in another:
webpack-dev-server

Now that HoloViews supports Bokeh Server, I think it should be feasible to port this application to a pure Python approach, though I believe that would require packaging up a few key bits of JavaScript as Python objects.  This seems like a good way to show off what's possible with Bokeh Server + HoloViews + Datashader...

I've done another example. Hope it would help.
open-nyc-visualization

Cool, thanks!


Create SQL Server Scripts

Create the SQLServer Create and DefaultData scripts.

All database scripts have been completed and are part of v7.17.0-BETA-2.


refactor swipeGesture, remove swipeMargin

should be changed later if swipeListener wont pleasure users

thank god, no conflict anymore


cmd/compile: internal compiler error for new version of absdiff.go, failure during noding

Issue for Go 1.18 (generics)
I created a new version of the test test/typeparam/absdiff.go that works fully, now that we've disallowed using a type param on the right-hand-side of a type declaration.  (Thanks to @perillo for posting a possible new implementation in #45639  that encouraged me to experiment with getting the test fully working again.)
With the new version, we get an assertion failure in typ0, caused while doing deferred processing of a function body.
Here's the new test case:
package main

import (
	"fmt"
	"math"
)

type Numeric interface {
	~int | ~int8 | ~int16 | ~int32 | ~int64 |
		~uint | ~uint8 | ~uint16 | ~uint32 | ~uint64 | ~uintptr |
		~float32 | ~float64 |
		~complex64 | ~complex128
}

// numericAbs matches a struct containing a numeric type that has an Abs method.
type numericAbs[T Numeric] interface {
	~struct{ Value T }
	Abs() T
}

// AbsDifference computes the absolute value of the difference of
// a and b, where the absolute value is determined by the Abs method.
func absDifference[T Numeric, U numericAbs[T]](a, b U) T {
	d := a.Value - b.Value
	dt := U{Value: d}
	return dt.Abs()
}

// orderedNumeric matches numeric types that support the < operator.
type orderedNumeric interface {
	~int | ~int8 | ~int16 | ~int32 | ~int64 |
		~uint | ~uint8 | ~uint16 | ~uint32 | ~uint64 | ~uintptr |
		~float32 | ~float64
}

// Complex matches the two complex types, which do not have a < operator.
type Complex interface {
	~complex64 | ~complex128
}

// orderedAbs is a helper type that defines an Abs method for
// a struct containing an ordered numeric type.
type orderedAbs[T orderedNumeric] struct {
	Value T
}

func (a orderedAbs[T]) Abs() T {
	if a.Value < 0 {
		return -a.Value
	}
	return a.Value
}

// complexAbs is a helper type that defines an Abs method for
// a struct containing a complex type.
type complexAbs[T Complex] struct {
	Value T
}

func (a complexAbs[T]) Abs() T {
	r := float64(real(a.Value))
	i := float64(imag(a.Value))
	d := math.Sqrt(r*r + i*i)
	return T(complex(d, 0))
}

// OrderedAbsDifference returns the absolute value of the difference
// between a and b, where a and b are of an ordered type.
func OrderedAbsDifference[T orderedNumeric](a, b T) T {
	return absDifference(orderedAbs[T]{a}, orderedAbs[T]{b})
}

// ComplexAbsDifference returns the absolute value of the difference
// between a and b, where a and b are of a complex type.
func ComplexAbsDifference[T Complex](a, b T) T {
	return absDifference(complexAbs[T]{a}, complexAbs[T]{b})
}

func main() {
	if got, want := OrderedAbsDifference(1.0, -2.0), 3.0; got != want {
		panic(fmt.Sprintf("got = %v, want = %v", got, want))
	}
	if got, want := OrderedAbsDifference(-1.0, 2.0), 3.0; got != want {
		panic(fmt.Sprintf("got = %v, want = %v", got, want))
	}
	if got, want := OrderedAbsDifference(-20, 15), 35; got != want {
		panic(fmt.Sprintf("got = %v, want = %v", got, want))
	}

	if got, want := ComplexAbsDifference(5.0+2.0i, 2.0-2.0i), 5+0i; got != want {
		panic(fmt.Sprintf("got = %v, want = %v", got, want))
	}
	if got, want := ComplexAbsDifference(2.0-2.0i, 5.0+2.0i), 5+0i; got != want {
		panic(fmt.Sprintf("got = %v, want = %v", got, want))
	}
}

I have a fix already, which I'll post immediately.    We were not properly setting g.curDecl in the deferred function processing, so type params of generic functions were not being made as unique as they should be.  This is definitely worth getting in for beta-2 (but not completely required if we miss the cutoff).
@randall77

Thanks @perillo I will incorporate a fix to that typo into the next checkin that I need to make.


feat: amv/res/desktop-virtualization/scaling-plan API updates

Description

Updating API version for desktop virtualization scaling plans, this will enable the use of the feature with pooled and personal host pools.

Fixes #2308
Closes #2308
Pipeline Reference

Pipeline

Type of Change

[ x] Update to CI Environment or utilities (Non-module affecting changes)
[ x] Azure Verified Module updates:

[ ] Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:

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

[x ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] Breaking changes and I have bumped the MAJOR version in version.json.
[ x] Update to documentation

Checklist

[ x] I'm sure there are no other open Pull Requests for the same update/change
[ ] I have run Set-AVMModule locally to generate the supporting module files.
[ x] My corresponding pipelines / checks run clean and green without any errors or warnings

Hey @danycontre, merge at will - unless @moisesjgomez has something to add :)
However if you do, please keep an eye on the workflow to ensure it runs all the way through to publishing.