Received Vulnerabilities after Run npm install Command

Describe the bug
In client side after running npm install command, I received 13 moderate vulnerabilities. Any solutions to this problem?
To Reproduce
Steps to reproduce the behavior:

Open cmd and change directory to client
Run npm install to download all necessary dependency
See error

Screenshots

Desktop (please complete the following information):

OS: Windows 10 OS Version 2009 (Build 19043.1110)
Browser Chrome
Version 92.0.4515.107

In the latest commit, 47793b2471800313638d109d102ed5b78636e62b, on v0.1.3 branch we have successfully cope with almost 70% of the vulnerabilities. We will continue to fix the remaining 13 moderate severity vulnerabilities. The latest audit report details:
# npm audit report

browserslist  4.0.0 - 4.16.4
Severity: moderate
Regular Expression Denial of Service - https://npmjs.com/advisories/1747
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking
change
node_modules/react-dev-utils/node_modules/browserslist  react-dev-utils  >=6.0.0-next.03604a46
  Depends on vulnerable versions of browserslist
  node_modules/react-dev-utils
    react-scripts  >=0.10.0-alpha.328cb32e
    Depends on vulnerable versions of @pmmmwh/react-refresh-webpack-plugin
    Depends on vulnerable versions of react-dev-utils
    Depends on vulnerable versions of webpack-dev-server
    node_modules/react-scripts

glob-parent  <5.1.2
Severity: moderate
Regular expression denial of service - https://npmjs.com/advisories/1751
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking
change
node_modules/glob-parent
node_modules/watchpack-chokidar2/node_modules/glob-parent
node_modules/webpack-dev-server/node_modules/glob-parent
  chokidar  1.0.0-rc1 - 2.1.8
  Depends on vulnerable versions of glob-parent
  node_modules/watchpack-chokidar2/node_modules/chokidar
  node_modules/webpack-dev-server/node_modules/chokidar
    watchpack-chokidar2  *
    Depends on vulnerable versions of chokidar
    node_modules/watchpack-chokidar2
      watchpack  1.7.2 - 1.7.5
      Depends on vulnerable versions of watchpack-chokidar2
      node_modules/watchpack
        webpack  4.44.0 - 4.46.0
        Depends on vulnerable versions of watchpack
        node_modules/webpack
    webpack-dev-server  2.0.0-beta - 3.11.2
    Depends on vulnerable versions of chokidar
    node_modules/webpack-dev-server
      @pmmmwh/react-refresh-webpack-plugin  0.3.1 - 0.5.0-beta.4
      Depends on vulnerable versions of webpack-dev-server
      node_modules/react-scripts/node_modules/@pmmmwh/react-refresh-webpack-plugin
        react-scripts  >=0.10.0-alpha.328cb32e
        Depends on vulnerable versions of @pmmmwh/react-refresh-webpack-plugin
        Depends on vulnerable versions of react-dev-utils
        Depends on vulnerable versions of webpack-dev-server
        node_modules/react-scripts

postcss  7.0.0 - 7.0.35 || 8.0.0 - 8.2.9
Severity: moderate
Regular Expression Denial of Service - https://npmjs.com/advisories/1693
fix available via `npm audit fix`
node_modules/postcss
node_modules/resolve-url-loader/node_modules/postcss
  resolve-url-loader  3.0.1 - 3.1.3 || 4.0.0-alpha.1 - 4.0.0-beta.2
  Depends on vulnerable versions of postcss
  node_modules/resolve-url-loader

ws  5.0.0 - 5.2.2 || 6.0.0 - 6.2.1 || 7.0.0 - 7.4.5
Severity: moderate
Regular Expression Denial of Service - https://npmjs.com/advisories/1748
fix available via `npm audit fix`
node_modules/webpack-dev-server/node_modules/ws
node_modules/ws

13 moderate severity vulnerabilities

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force


Performance: Consider in-memory store default

We are currently store implicit data in an n3 store however, the match method is quite heavyweight; especially in that it creates a full array of the matches before asynchronously iterating over them. As such it would likely be quite valuable to use something else that does not take such a performance hit.

Updates:

n3 improved
graphy.js blocked


HHH-12780 - Re-allow native SQL queries that take a given resultClass to map the result set to the required type

https://hibernate.atlassian.net/browse/HHH-12780

@vladmihalcea so about this one, I also reverted the tests you added so you would have to add them back.

@vladmihalcea still requires the tests to be reintroduced: https://github.com/hibernate/hibernate-orm/commit/9fac6747ef22acff9c7350efca33286452a2c967#diff-8366ba4b8b14c099a596fe79b1ab7849

This will be implemented in 6.0.


TTL for Rego policies pulled from external registry

Adds support for authconfigs.spec.authorization.opa.externalRegistry.ttl (in seconds, default: 0– i.e. auto-refresh disabled).
Closes #221

Verification steps

Deploy an instance build based on this branch:

make local-setup DEPLOY_KEYCLOAK=1

Deploy an OPA server (it will work as external policy registry):

kubectl -n authorino apply -f -<<EOF
apiVersion: v1
kind: ConfigMap
metadata:
  name: opa-policies
data:
  allowed-methods.rego: |
    package talkerapi

    method = input.context.request.http.method

    allow { method == "GET" }
    allow { method == "POST" }
  allowed-paths.rego: |
    package talkerapi

    path = input.context.request.http.path

    allow { path == "/" }
EOF

kubectl -n authorino apply -f -<<EOF
apiVersion: apps/v1
kind: Deployment
metadata:
  name: opa
spec:
  selector:
    matchLabels:
      app: opa
  template:
    metadata:
      labels:
        app: opa
    spec:
      containers:
      - name: opa
        image: openpolicyagent/opa:0.38.1
        args:
        - "run"
        - "--server"
        - "--ignore=.*"
        - "--log-level=debug"
        - "--log-format=json-pretty"
        - "--set=decision_logs.console=true"
        - "/policies"
        ports:
        - name: http
          containerPort: 8181
        volumeMounts:
        - name: policies
          mountPath: /policies
          readOnly: true
      volumes:
      - name: policies
        configMap:
          name: opa-policies
EOF

kubectl -n authorino apply -f -<<EOF
apiVersion: v1
kind: Service
metadata:
  name: opa
  labels:
    app: opa
spec:
  selector:
    app: opa
  ports:
  - name: http
    port: 8181
    targetPort: 8181
    protocol: TCP
EOF

Deploy the AuthConfig:

kubectl -n authorino apply -f -<<EOF
apiVersion: authorino.kuadrant.io/v1beta1
kind: AuthConfig
metadata:
  name: talker-api-protection
spec:
  hosts:
  - talker-api-authorino.<IP_ADDRESS>.nip.io
  identity:
  - name: anonymous
    anonymous: {}
  - name: keycloak
    oidc:
      endpoint: http://keycloak.authorino.svc.cluster.local:8080/auth/realms/kuadrant
      ttl: 300
    priority: 1 # to never actually use this identity as we just want to test the auto-refresh of the config
  authorization:
  - name: always-allow
    opa:
      inlineRego: |
        allow = true
  - name: allowed-paths
    opa:
      externalRegistry:
        endpoint: http://opa.authorino.svc.cluster.local:8181/v1/policies/policies/allowed-paths.rego
  - name: allowed-methods
    opa:
      externalRegistry:
        endpoint: http://opa.authorino.svc.cluster.local:8181/v1/policies/policies/allowed-methods.rego
        ttl: 60
EOF

The OPA policy always-allow is based on inline Rego, therefore it will not change.
The OPA policy allowed-path does not have a ttl set, therefore it will not be be refreshed.
The OPA policy allowed-methods will be auto-refreshed from source every 60 seconds.

Watch the Authorino instance logs:

kubectl -n authorino logs -f $(kubectl -n authorino get pods -l authorino-resource=authorino -o name)

You should see an "openid connect configuration updated" at the beginning andevery 5 minutes.
You should also see an "auto-refresh of external policy disabled" message at the beginning, related to the allowed-paths policy.
Every 60 seconds, you should see an "external policy unchanged" message, related to the allowed-methods policy.

{"level":"debug","ts":1648029316.0687168,"logger":"authorino.controller-runtime.manager.controller.authconfig.identity.oidc","msg":"openid connect configuration updated","authconfig":"authorino/talker-api-protection","endpoint":"http://keycloak.authorino.svc.cluster.local:8080/auth/realms/kuadrant"}
{"level":"debug","ts":1648029316.3548667,"logger":"authorino.controller-runtime.manager.controller.authconfig.authorization.opa","msg":"auto-refresh of external policy disabled","authconfig":"authorino/talker-api-protection","policy":"authorino/talker-api-protection/allowed-paths","endpoint":"https://raw.githubusercontent.com/guicassolato/authorino-opa/main/allowed-paths.rego","reason":"interval must be greater than zero"}

[…]

{"level":"debug","ts":1648040290.1474848,"logger":"authorino.controller-runtime.manager.controller.authconfig.authorization.opa","msg":"external policy unchanged","authconfig":"authorino/talker-api-protection","policy":"authorino/talker-api-protection/allowed-methods","endpoint":"https://raw.githubusercontent.com/guicassolato/authorino-opa/main/allowed-methods.rego"}
{"level":"debug","ts":1648040350.0213318,"logger":"authorino.controller-runtime.manager.controller.authconfig.identity.oidc","msg":"openid connect configuration updated","authconfig":"authorino/talker-api-protection","endpoint":"http://keycloak.authorino.svc.cluster.local:8080/auth/realms/kuadrant"}

Send requests to the API:

curl http://talker-api-authorino.<IP_ADDRESS>.nip.io:8000 -i -X GET
# 200

curl http://talker-api-authorino.<IP_ADDRESS>.nip.io:8000 -i -X POST
# 200

curl http://talker-api-authorino.<IP_ADDRESS>.nip.io:8000 -i -X PUT
# 403

curl http://talker-api-authorino.<IP_ADDRESS>.nip.io:8000/hello -i -X GET
# 403

Modify the source Rego for the allowed-methods policy, allowing PUT:

curl http://localhost:8181/v1/policies/policies/allowed-methods.rego -X PUT --data $'package talkerapi\n\nmethod = input.context.request.http.method\n\nallow { method == "GET" }\nallow { method == "POST" }\nallow { method == "PUT" }\n' -H 'Content-Type: text/plain'
# {}

You should see a "policy updated from external registry" message in the logs after a few seconds:
{"level":"info","ts":1648050199.0521312,"logger":"authorino.controller-runtime.manager.controller.authconfig.authorization.opa","msg":"policy updated from external registry","authconfig":"authorino/talker-api-protection","policy":"authorino/talker-api-protection/allowed-methods","endpoint":"http://opa.authorino.svc.cluster.local:8181/v1/policies/policies/allowed-methods.rego"}

The PUT method should now be allowed:

curl http://talker-api-authorino.<IP_ADDRESS>.nip.io:8000 -i -X PUT
# 200

Now, try to update the Rego source for the allowed-paths policy, allowing /hello:

curl http://localhost:8181/v1/policies/policies/allowed-paths.rego -X PUT --data $'package talkerapi\n\npath = input.context.request.http.path\n\nallow { path == "/" }\nallow { path == "/hello" }' -H 'Content-Type: text/plain'
# {}

You will see that, even though the external source has changed, since Authorino is not refreshing this particular policy, no update shall be seen in the logs and the /hello path will remain forbidden:
curl http://talker-api-authorino.<IP_ADDRESS>.nip.io:8000/hello -i -X GET
# 403

(Optional) Try with a different policy registry
Alternatively to using an OPA server as external policy registry, you can use a Github repo, e.g.:
apiVersion: authorino.kuadrant.io/v1beta1
kind: AuthConfig
metadata:
  name: talker-api-protection
spec:
  hosts:
  - talker-api-authorino.<IP_ADDRESS>.nip.io
  identity:
  - name: anonymous
    anonymous: {}
  - name: keycloak
    oidc:
      endpoint: http://keycloak.authorino.svc.cluster.local:8080/auth/realms/kuadrant
      ttl: 300
    priority: 1 # to never actually use this identity as we just want to test the auto-refresh of the config
  authorization:
  - name: always-allow
    opa:
      inlineRego: |
        allow = true
  - name: allowed-paths
    opa:
      externalRegistry:
        endpoint: https://raw.githubusercontent.com/guicassolato/authorino-opa/main/allowed-paths.rego
  - name: allowed-methods
    opa:
      externalRegistry:
        endpoint: https://raw.githubusercontent.com/guicassolato/authorino-opa/main/allowed-methods.rego
        ttl: 60

Changes committed to the allowed-methods.rego file in Github will be reflected in Authorino. The update may take a little longer due to GitHub's cache policy Cache-Control: max-age=300.

Did you considered a different approach instead like the following?

I actually have a feeling that the approach proposed in the PR can scale better.
Imagine a number of requests per second sufficiently large and an instance of Authorino capable of serving multiple requests concurrently. Many concurrent goroutines may be checking the TTL of the policy "at the same time". The check itself is relatively cheap and doesn't require any concurrency control. However, those goroutines may also all decide to update the cache concurrently. So only one of the goroutines does it, we will need a lock.
Even if the other goroutines – i.e. the ones that fail to acquire the lock – give up and proceed right away using the existing version of the policy in the cache (rather than waiting for the update to happen by the one goroutine that succeeded to acquire the lock), acquiring the lock itself has a cost; the negotiation usually involves waiting and sometimes risk of deadlock (depending on implementation).
With the current approach, there is only one goroutine in charge of the updating the cache. I believe the number of concurrent requests in production in any reasonable deployment will beat the number of policies set to expire big time, making one goroutine a lot less expensive compared to the risk of throttling on every tick of cache expiry that coincides with many requests coming in.
Moreover, this goroutine will be idle most of the time, as authorization policies are not supposed to change very often. I imagine TTLs set in production to the order of hours.


1.7.4-3b Export Multiple files bug

Describe the bug
When exporting multiple files, it exports only the ones that were selected before - right click - export as html, even though I've clicked 'Select All
Operating System
Windows 10
To Reproduce
Steps to reproduce the behavior:

Go to filelist
Click on required folder to export
Scroll down to Export as Html, select all
See Export without all files included

Video: https://youtu.be/0FMF0eJSLSs

Thanks for the report, this should be fixed if you use the ribbon icon rather than right clicking on a file. I will look into fixing it when a file is right clicked as well. Thanks!

I was able to reproduce and fix this error, it will be fixed in the next release


Subdirectories in lib and debug/lib now errors

The commit 16ecddf is now causing certain packages to install with errors such as GLFW3, openal-soft and spdlog which copy their pkgconfig folder to share, but to remove it from lib and debug/lib folders.

Thanks for reporting this, we should come up with a good solution for pkgconfig files (which may be removing them) and apply this to all the existing ports before reenabling these checks.


[API] retrieve files from the raw_data for viewing in the frontend

/projects/{{projectId}/artifacts/content?filename={{filename}}

close at #1008


fix: don't update the Pod after it's been created

Closes #27.
The original code would createOrUpdate the Pod resource. The problem is that we were then overwriting the metadata.annotations field on updates.
The issue we ran into was this...

Oz creates the Pod
Istio's Webhook Endpoint mutates the Pod Labels and Annotations
Oz's secondary reconcile loop immediately comes in and replaces the metadata.annotations with the original empty annotations
Istio doesn't re-apply the annotations because the metadata.labels were mutated and indicate that the webhook has already happened.
Istio-validation container won't start up

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

20 of 23 (86.96%)  changed or added relevant lines in 1 file are covered.
6 unchanged lines in 1 file lost coverage.
Overall coverage increased (+4.3%) to 31.775%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

controllers/builders/base_builder.go
20
23
86.96%

Files with Coverage Reduction
New Missed Lines
%

controllers/builders/base_builder.go
6
37.31%

Totals

Change from base Build<PHONE_NUMBER>:
4.3%

Covered Lines:
496

Relevant Lines:
1561

💛  - Coveralls


[charts/redis-ha][BUG] Lost conectivity due to announce service

Description:
Lost connectivity first to master and then to slave.
Steps to reproduce the behavior:

Start minikube on debian VM.
Set hardAntiAffinity to false.
Setup redis-ha.
Wait until master<-> slave relationships are settled.
Check logs of sentinel.
Delete master with kubectl delete.
Wait until failover is complete and master<-> slave relationships are settled.
Check redis-cli role on each replica.

Actual behaviour
At step 5 there is a +sdown master mymaster <IP_ADDRESS> 6379 in master sentinel logs.
At step 8:
Pod 0 result of redis-cli role

"slave"
"<IP_ADDRESS>"
(integer) 6379
"connected"
(integer) 103726

Pod 1 result of redis-cli role

"master"
(integer) 104010

"<IP_ADDRESS>"
"6379"
"103868"

Pod 2 result of redis-cli role

"slave"
"<IP_ADDRESS>"
(integer) 6379
"connected"
(integer) 104010

Expected behaviour
There should no sdown reported, and there should be one master that reports two connected slaves, and two slaves that report connection to the master.
Additional context
Kubernetes version: v1.15.4
Helm version: v2.15.1
Minikube version: v1.6.2
Redis HA version: v4.5.2
Debian version: 9.11 (VM running on Windows 10)
I have tested with version Redis HA version 3.0.3 and there the same problem does not occur, but it appears on 3.0.4, thus the claim in the title that it depends on the announce service.
I have also been able to test in another environment where this problems does not occur, but in minikube it occurs almost every time I run the test.
Furthermore, when running this test I have also seen that the result have been three slaves that do not do a proper failover, and also split-brain, i.e. two masters and one slave, but I haven't analysed these issues further.
Is this a known issue or a bug?

@StefanKarlsson321 Can you throw some logs at me? The redis-cli commands look valid?
Does Minikube come with hairpining enabled? I know I've seen something like this happen my cluster wasn't allowing hairpinning which messed with the comms between the nodes.

The redis-cli command only shows one slave connected on master which is wrong. Correct output with two connected slaves should be:
1) "master"
2) (integer) 30847
3) 1) 1) "<IP_ADDRESS>"
      2) "6379"
      3) "30847"
   2) 1) "<IP_ADDRESS>"
      2) "6379"
      3) "30847"

No minikube does not have hairpin enabled it seems. I have actually found out also that it is the reason. redis-sentinel cannot contact redis-server on the same pod due to using the announce ip service. I have confirmed this by checking whether redis can reach itself through the announced ip, when source and destination is the same pod. It cannot. When the destinations are not the same it works however.
I have been sparse with logs since there are plenty of them. But I see something that looks wrong when master starts up, i.e. the last message +sdown. This is probably due to that redis-sentinel cannot reach redis-server from the same pod then:
(Sentinel logs of master pod server-0)
1:X 03 Apr 2020 09:39:24.765 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:X 03 Apr 2020 09:39:24.765 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:X 03 Apr 2020 09:39:24.765 # Configuration loaded
1:X 03 Apr 2020 09:39:24.767 * Running mode=sentinel, port=26379.
1:X 03 Apr 2020 09:39:24.767 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:X 03 Apr 2020 09:39:24.767 # Sentinel ID is 50ac74ff20de0efb51e8d72400e2a6365c394553
1:X 03 Apr 2020 09:39:24.767 # +monitor master mymaster <IP_ADDRESS> 6379 quorum 2
1:X 03 Apr 2020 09:39:34.773 # +sdown master mymaster <IP_ADDRESS> 6379

Similarly the slaves also report themselves to be down:
(Sentinel logs of slave pod server-1)
1:X 03 Apr 2020 09:39:29.875 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:X 03 Apr 2020 09:39:29.875 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:X 03 Apr 2020 09:39:29.875 # Configuration loaded
1:X 03 Apr 2020 09:39:29.877 * Running mode=sentinel, port=26379.
1:X 03 Apr 2020 09:39:29.877 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:X 03 Apr 2020 09:39:29.877 # Sentinel ID is 12ac0bdf6462de03e2d9ed378dea0ac96434d9cf
1:X 03 Apr 2020 09:39:29.877 # +monitor master mymaster <IP_ADDRESS> 6379 quorum 2
1:X 03 Apr 2020 09:39:29.878 * +slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:39:39.924 # +sdown slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:39:46.105 * +sentinel sentinel 7f3dd8c6941e6456bf071c702d42be93134af6c8 <IP_ADDRESS> 26379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:39:49.984 * +slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379

When I delete master  it wakes up and becomes a slave with basically the same logs as above sentinel logs of slave pod:
(Contnued sentinel logs of  pod server-0)
1:X 03 Apr 2020 09:44:37.923 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:X 03 Apr 2020 09:44:37.923 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:X 03 Apr 2020 09:44:37.923 # Configuration loaded
1:X 03 Apr 2020 09:44:37.925 * Running mode=sentinel, port=26379.
1:X 03 Apr 2020 09:44:37.925 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:X 03 Apr 2020 09:44:37.925 # Sentinel ID is 50ac74ff20de0efb51e8d72400e2a6365c394553
1:X 03 Apr 2020 09:44:37.925 # +monitor master mymaster <IP_ADDRESS> 6379 quorum 2
1:X 03 Apr 2020 09:44:37.926 * +slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:38.590 * +sentinel sentinel 7f3dd8c6941e6456bf071c702d42be93134af6c8 <IP_ADDRESS> 26379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:38.598 # +new-epoch 1
1:X 03 Apr 2020 09:44:42.045 * +sentinel sentinel 12ac0bdf6462de03e2d9ed378dea0ac96434d9cf <IP_ADDRESS> 26379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:47.980 # +sdown slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379

Following the new master will report the additional logs:
(Continued logs of slave that becomes master server-1)
1:X 03 Apr 2020 09:44:27.536 # +new-epoch 1
1:X 03 Apr 2020 09:44:27.536 # +config-update-from sentinel 7f3dd8c6941e6456bf071c702d42be93134af6c8 <IP_ADDRESS> 26379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:27.536 # +switch-master mymaster <IP_ADDRESS> 6379 <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:27.537 * +slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:27.537 * +slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:37.564 # +sdown master mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:37.564 # +sdown slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:38.034 # -sdown slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:39.997 * +sentinel sentinel 50ac74ff20de0efb51e8d72400e2a6365c394553 <IP_ADDRESS> 26379 @ mymaster <IP_ADDRESS> 6379

The slave that does not get promoted reports:
(Full logs of server-2)
1:X 03 Apr 2020 09:39:44.090 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:X 03 Apr 2020 09:39:44.090 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:X 03 Apr 2020 09:39:44.090 # Configuration loaded
1:X 03 Apr 2020 09:39:44.092 * Running mode=sentinel, port=26379.
1:X 03 Apr 2020 09:39:44.092 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:X 03 Apr 2020 09:39:44.092 # Sentinel ID is 7f3dd8c6941e6456bf071c702d42be93134af6c8
1:X 03 Apr 2020 09:39:44.092 # +monitor master mymaster <IP_ADDRESS> 6379 quorum 2
1:X 03 Apr 2020 09:39:44.093 * +slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:39:44.105 * +slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:39:44.158 * +sentinel sentinel 12ac0bdf6462de03e2d9ed378dea0ac96434d9cf <IP_ADDRESS> 26379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:39:54.138 # +sdown slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:27.159 # Executing user requested FAILOVER of 'mymaster'
1:X 03 Apr 2020 09:44:27.159 # +new-epoch 1
1:X 03 Apr 2020 09:44:27.159 # +try-failover master mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:27.207 # +vote-for-leader 7f3dd8c6941e6456bf071c702d42be93134af6c8 1
1:X 03 Apr 2020 09:44:27.207 # +elected-leader master mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:27.207 # +failover-state-select-slave master mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:27.263 # +selected-slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:27.263 * +failover-state-send-slaveof-noone slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:27.335 * +failover-state-wait-promotion slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:27.462 # +promoted-slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:27.462 # +failover-state-reconf-slaves master mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:27.529 * +slave-reconf-sent slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:27.529 # +failover-end master mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:27.529 # +switch-master mymaster <IP_ADDRESS> 6379 <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:27.529 * +slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:27.529 * +slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:37.553 # +sdown slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:37.553 # +sdown slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:38.040 # -sdown slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ mymaster <IP_ADDRESS> 6379
1:X 03 Apr 2020 09:44:39.997 * +sentinel sentinel 50ac74ff20de0efb51e8d72400e2a6365c394553 <IP_ADDRESS> 26379 @ mymaster <IP_ADDRESS> 6379

What I gather is that the extra +sdown messages are due to the hairpin problem, and can likely cause further issues. I see a workaround  at https://stackoverflow.com/questions/54911270/kubernetes-service-can-not-send-request-to-itself, but since I run the none vmdriver it is not possible for me.

@StefanKarlsson321 Sorry I didn't get back to you on this.
Are you suggestion that we find a workaround for this, or are you happy for this to be closed?

This can be closed. It is quite a small use case.


Select plugin refresh not triggered for datatable.row.add

Hi,
When I am adding rows to datatables, for filter_type multi_select, internal select box is updating the new values, but select plugin is not getting refreshed.

please provide a link to test case jsbin / jsfiddle / etc'

Hi Vedmack,
I am unable to create a jsbin/jsfiddle being a first time user of those services.
Am not able to include your latest js file in their resource library. Can you help me out with this.
Or if you can create a sample fiddle for me to work on. Apologies for the inconvenience.

Here are the latest versions on yadcf css/js
https://rawgit.com/vedmack/yadcf/7b37b3142059efc8e2d81c5f6d93d38d81a022bd/jquery.dataTables.yadcf.css
https://github.com/vedmack/yadcf/blob/9a6d7a7b97982da2cc72b2dd9f79299fdf71a825/jquery.dataTables.yadcf.js

Hi Vedmack
Please look at http://jsbin.com/bayuru/edit?html,js,console,output
Created 2 select box filters. Basic select box is updated with no value. MultiSelect plugin box is not getting refreshed.

Hi
There was an issue in your code - invalid use of the exFilterColumn <-- read docs,
See this jsbin sample , click on First Col / Second Col to see how the filters / table reacts...
As to the datatable.row.add, I don't see its use in the jsbin. You should extend that jsbin to reflect your issue...

Hi,
I was using someone else code, that's why the exFilterColumn. I have removed it as I am not using that.
I have not used datatable.row.add in this example as of now.
Issue can be seen what I clear datatables with
dataTableObjRedraw.clear();
dataTableObjRedraw.draw();
Multiselect plugin still reflects the old values but normal select box clears all previous values.
i.e. Multiselect is not able to refresh underlying values.
Hope I am clear this time.

If you made a new test sample please provide its code
On May 9, 2016 9:43 AM, "Gaurav Agarwal"<EMAIL_ADDRESS>wrote:

Hi,
I was using someone else code, that's why the exFilterColumn. I have
removed it as I am not using that.
I have not used datatable.row.add in this example as of now.
Issue can be seen what I clear datatables with
dataTableObjRedraw.clear();
dataTableObjRedraw.draw();
Multiselect plugin still reflects the old values but normal select box
clears all previous values.
i.e. Multiselect is not able to refresh underlying values.
Hope I am clear this time.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/vedmack/yadcf/issues/306#issuecomment-217787408

I have removed exFilterColumn. Please check jsbin http://jsbin.com/bayuru/edit?html,js,console,output

Sorry, but I really can't understand what are you trying to show in your jsbin sample?
You must provide a scenario with expected flow / and to explain whats the actual flow, the moment you will provide a jsbin sample with the expected  / actual flow I will be able to try and help you, untill then - I can't

I have made a button to clear data in Datatables.
Case 1: Load Datatable with initial data and load filters.
Expected : Table generated with proper filter values.
Case 2: Clear data present is datatables
Expected : Data rows is removed and all values in filters are removed.
Actual : Column 1 filter still retains old values(Should have cleared these values). Column 2 filter clears old Values (as expected)

Please see the jsbin http://jsbin.com/bayuru/edit?html,js,console,output with "Clear Datatables" button.

Hi Vedmack,
Were you able to figure out the issue?

Hi,
It looks more a multi select plugin issue than yadcf, it seems that when you init the multi select it does not clear its values, so the only possible solution I came with is to init it / destroy then init again
like this
yadcf.initSelectPluginCustomTriggers(
    function(selectBoxObj) {
      selectBoxObj.multiselect({});
      selectBoxObj.multiselect("destroy");
      selectBoxObj.multiselect({});
    },
    function(selectBoxObj) {
      selectBoxObj.multiselect('refresh');
    });

See working sample


nc_get_var_string and ncdump throw HDF error on an NC_STRING variable with one unlimited dimension and written with an offset

I am able to create this NC_STRING variable with one limited and one unlimited dimension, and write to it some data with an offset without issue. But when trying to read it back with nc_get_var_string, I am getting a NC_EHDFERR (-101). When trying to use ncdump on the file, I also see "NetCDF: HDF error".  However, I am able to read it fine with nc_get_vars_string.
Here are the repro steps (attached here as well: repro.cpp.zip):
#include <iostream>
#include <vector>
#include "netcdf.h"

void checkErrorCode(int status, const char* message){
    if (status != NC_NOERR){
        std::cout << "Error code: " << status << " from " << message << std::endl;
    }
}

int main(int argc, const char * argv[]) {

    // set up data

    const char** charPointers = new const char*[4];
    std::string* stringData = new std::string[4];

    stringData[0] = "a";
    charPointers[0] = stringData[0].c_str();

    stringData[1] = "aa";
    charPointers[1] = stringData[1].c_str();

    stringData[2] = "b";
    charPointers[2] = stringData[2].c_str();

    stringData[3] = "bb";
    charPointers[3] = stringData[3].c_str();

    int ncid;
    int retval;

    // -- WRITE --

    retval = nc_create("myfile.nc", NC_NETCDF4, &ncid);
    checkErrorCode(retval, "nc_create");

    // Define dimensions
    int dimid_a;
    retval = nc_def_dim(ncid, "a", NC_UNLIMITED, &dimid_a);
    checkErrorCode(retval, "nc_def_dim for 'a'");

    int dimid_b;
    retval = nc_def_dim(ncid, "b", 10, &dimid_b);
    checkErrorCode(retval, "nc_def_dim for 'b'");

    int dimids[2] = {dimid_b, dimid_a};

    // Define variable
    int varid;
    retval = nc_def_var(ncid, "var", NC_STRING, 2, dimids, &varid);
    checkErrorCode(retval, "nc_def_var");

    // Put variable
    size_t start[2] = {0, 1};
    size_t count[2] = {2, 2};
    ptrdiff_t stride[2] = {1, 1};

    retval = nc_put_vars_string(ncid, varid, start, count, stride, charPointers);
    checkErrorCode(retval, "nc_put_vars_string");

    retval = nc_close(ncid);
    checkErrorCode(retval, "nc_close(1)");

    // -- READ --
    retval = nc_open("myfile.nc", NC_NOWRITE, &ncid);
    checkErrorCode(retval, "nc_open");

    // get dimensions
    int ndims, dimids_read[NC_MAX_VAR_DIMS];
    retval = nc_inq_var(ncid, varid, NULL, NULL, &ndims, dimids_read, NULL);
    checkErrorCode(retval, "nc_inq_var");

    // calculate num elements to read
    size_t dimlen = 0;
    size_t num_items = 1;
    for ( int j = 0; j < ndims; ++j ) {
        retval = nc_inq_dimlen(ncid, dimids_read[j], &dimlen);
        checkErrorCode(retval, "nc_inq_dimlen");
        num_items *= dimlen;
    }

    // get var
    char** readStrings = new char*[num_items];
    retval = nc_get_var_string(ncid, varid, readStrings);
    checkErrorCode(retval, "nc_get_var_string");

    retval = nc_close(ncid);
    checkErrorCode(retval, "nc_close(2)");

    return retval;
}

The output when run:
$ ./a.out
Error code: -101 from nc_get_var_string
$ ls
a.out*		myfile.nc	repro.cpp
$ ncdump myfile.nc
netcdf myfile {
dimensions:
	a = UNLIMITED ; // (3 currently)
	b = 10 ;
variables:
	string var(b, a) ;
data:

 var =
NetCDF: HDF error
Location: file <..>/netcdf/ncdump/vardata.c; line 478

As far as I could tell, to reproduce the issue there has to be >1 dimension, one has to be unlimited, and when writing data the offset needs to be in the unlimited dimension. I also only see this with NC_STRING data.
I am seeing this with netcdf 4.7.4 and the above repro steps are run on macOS 10.15.6 (but we are seeing it on other platforms as well).
Is this a known bug or limitation? I know nc_get_var_string has a warning about using it with unlimited dimensions, but this issue seems specific to NC_STRING

I'm sorry but I suspect this is connected to some long-standing NC_STRING.
Can you instead use fixed length strings? Then turn on nc_def_var_deflate() for the variable, and it will compress away the extra empty characters?
That will work a lot more reliably.

Thank you for a quick response, Ed!  I guess it is one of those things with NC_STRINGs that you warned me to be careful about in the email...
By the fixed length strings do you mean switching to use NC_CHAR or avoiding using NC_STRING with unlimited dimensions? Is it a limitation that needs to be documented?

Using fixed length NC_CHAR works well and is simple to code. ;-)

Thanks, Ed - fair enough! But we just want to make sure we are handling this case correctly in case MATLAB users run into it. So any information (e.g. whether it should be treated as a bug or as a limitation) would be much appreciated!

I did an experiment in which I used char(*) t (i.e. VLEN of t) as the type of the variable.
This should be roughly equivalent to using NC_STRING type because internally
this is how NC_STRING is stored.
Assuming I got it right, then this works  to produce the file. However ncdump
crashes on it for some reason. I am investigating this latter problem separately.
But h5dump on myfile.nc appears correct.
I am attaching my program for verification (I converted it to C). It has extension .txt
instead of .c so that github will allow the attachment.
svlen.txt

The attached ncdump/dumplib.c file fixes the ncdump crash.
dumplib.txt

Thank you for taking a look, Dennis! I can confirm that svlen.c indeed writes and reads the file without any errors using NC_VLEN instead of NC_STRING. So there is some issue with NC_STRING implementation, even though it should be equivalent to vlen of chars?

That is my guess. So we need to look at the string code and look for ways it is handled
differently than vlen.

It only fixes the immediate crash. It does not fix the problem with NC_STRING that you
identified. That problem is still to be solved.

Thank you for clarification! I was a bit confused, since I did not observe ncdump crashing with my file from these repro steps :)
I am seeing an ncdump crash on another file though, so I am trying to see if this version of ncdump/dumplib.c makes a difference... looks like it is a bit different from dumplib.c included in netcdf-c 4.7.4 and 4.8.0

Hi,
Thanks for looking at this earlier! Just wanted to check - there have been no updates, and this is still an active bug, right? We can report that we still observe the issue in 4.8.1...

Unfortunately yes, that bug still exists.
No estimate on when I can look at it.

Thank you Dennis for the confirmation! No worries, I realize this is an edge-case-y issue...

Hi, just checking in on this - still planned for 4.8.2 for now? No worries, I understand it might be lower on the priority.

Sorry, doing a check-in again - looks like this is still an active issue, but it might get addressed in next release (v4.9.1)?

@krisfed thanks for checking in; we are working through.  It can be tricky to determine what will make it into the release, given the resources we have to work with, but we will try to have this in the 4.9.1 release :)

Thank you Ward! Yes I bet there are many things to juggle, thanks for taking a look!


Split Editor Script, Template, Style is missing in v1.0.11

First, thank you for this awesome extension. 🥳
Underneath my bug (?) report.
Should you need more information regarding this issue, please let me know.
Problem
After Volar upgraded from version v1.0.9 to version v1.0.10
The green button, allowing to split the current file into script/template (and style?) is missing for me.
Expected Behavior
The expected behavior is to see the button and be able to split the current vue file into script and template.

There are other extensions allowing to split files. But non (AFAIK) split within the same file.
It is super useful to be able to switch files and only have the split in said file and not have a split with several files.
Quick Fix
Manually downgrading to version v1.0.9

Duplicate of #2158
It was intentionally removed and replaced with command to save screen space.

Any chance of adding a setting to allow to toggle display of the button.
Might be a personal taste and heavily depending on my extensions/layout/...
But personally I prefer the button over a command/hotkey.

Would you mind to open a new feature request issue to collect feedback?

Due to this being an intentional change, Would you mind to open a new feature request issue to collect feedback?

I wouldn't mind at all. Will get to it right away.


Semantics.label in iOS creates a new Text rather than setting Semantic container's ID

Steps to Reproduce
Wrap a widget in a Semantics widget and set a value to its label. Note that the child widget must internally implement a Semantics and has container set to true.
Expected results:

On Android, a View is rendered and has contentDescription of Semantics.label.
On iOS, a UIAView is rendered and has accessibility ID and label value of Semantics.label .

Actual results:

On Android, a View is rendered and has contentDescription of Semantics.label.
On iOS, a UIAView is rendered, but has no accessibility label or id set. Instead, a new Text widget is created as a sibling widget of Semantics.child.

See screenshots attached below to visualize the issue.

Code sample
Tested on Flutter 3.3.10.
Semantics(
    label: 'CheckboxID',
    child: const CheckboxListTile(
      value: true,
      onChanged: null,
      title: Text('Checkbox'),
    ),
  ),

Sample app can be found on: https://github.com/leovinsen/flutter_semantics_inconsistency/blob/main/lib/main.dart

Screenshots
Screenshots taken using Appium IDE inspector. Using Xcode's Accessibility Inspector also yields a similar result.
Button
In these 2 images below, we can see that a UIAView is created but Semantics label is rendered as a new Text widget rather than setting the UIAView's accessibility ID and label.

For comparison, here's how it looks like in Android.

TextField
On a separate issue: in the case of TextField, weirdly on iOS it will properly set the TextField's ID and label and not modify the value. In Android, the TextField's value get merged with its Semantics label.

Logs
[✓] Flutter (Channel stable, 3.3.10, on macOS 13.1 22C65 darwin-x64, locale en-ID)
    • Flutter version 3.3.10 on channel stable at /Users/leonardov/fvm/versions/3.3.10
    • Upstream repository git@github.com:flutter/flutter.git
    • Framework revision 135454af32 (4 weeks ago), 2022-12-15 07:36:55 -0800
    • Engine revision 3316dd8728
    • Dart version 2.18.6
    • DevTools version 2.15.0

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/leonardov/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] VS Code (version 1.74.2)
    • VS Code at /Applications/Programming/Visual Studio Code.app/Contents
    • Flutter extension version 3.56.0

[✓] Connected device (4 available)
    • SM G900H (mobile)                   • 4d0081ca4ed04147                     • android-arm    • Android 6.0.1 (API 23)
    • iPhone SE (3rd generation) (mobile) • B8C03FD6-777B-4ED7-BA42-08121512F495 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-2 (simulator)
    • macOS (desktop)                     • macos                                • darwin-x64     • macOS 13.1 22C65 darwin-x64
    • Chrome (web)                        • chrome                               • web-javascript • Google Chrome 108.0.5359.124

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

For context I'm looking to implement UI automation using Appium. However, as described in https://github.com/flutter/flutter/issues/17988 it doesn't seem possible to set accessibility IDs of each widgets.
So as a workaround, I'm planning to wrap every widget in a custom Semantics with some additional logic to cater for finding elements by ID in Appium. And then stumbled into this issue.

Hello @leovinsen. Using Xcode's Accessibility Inspector, I see the following:

Now I am not very familiar with this tool, so I am not sure what I am looking at. Could you point out what the actual result should be when viewing this using this tool?

Hi @exaby73, thanks for your response!
Based on your example, I believe it works as intended because internally a Text widget does not have a Semantics with container set to true. As a result it would get merged into its parent Semantics node.
The issue only arises when we have a nested Semantics widget where the inner one has container set to true. Here I have nested 2 semantics widget:

Nested semantics
Semantics(
  label: 'OuterSemantics',
  child: Semantics(
    label: 'InnerSemantics',
    container: true,
    child: const Text('This is the content'),
  ),
)

and when inspected using Accessibility Inspector, here's the result. OuterSemantics should have been the last SemanticsObjectContainer's label, not a child static Text inside the container. Also it should not be InnerSemantics' sibling node.

Screenshot

The expected nodes should have been:
- <SemanticsObjectContainer> -- has value of `OuterSemantics`
   - <Text> -- has value of InnerSemantics \n This is the content

If we compare it with the Android screenshots above, in Android the label is correctly set as android.view.View content-desc.
It can be also reproduced on widgets that internally has a Semantics with container set to true, such as all subclasses of ButtonStyleButton.

@leovinsen Thanks for your response. Labeling the issue for further insights from the team.

cc @chunhtai

Have the same issue here. Any updates?

Hello @rotorgames. Please read https://github.com/flutter/flutter/wiki/Issue-hygiene#do-not-add-me-too-or-same-or-is-there-an-update-comments-to-bugs. Instead of posting "same here" or "any updates" comments, consider thumbs-up-ing the original post. Thank you


Don't slide in slides that haven't loaded yet

Would it be possible to either:

check that all images in a new slide have loaded before sliding it into view, or
provide slides with a callback to call when they are ready?

You have to implement custom slide component to meet this requirement
https://github.com/akiran/react-slick/blob/master/examples/CustomSlides.js

But, won't the slider keep showing next images, without waiting for the CustomSlide to complete loading? How can a CustomSlide preload images without being skipped?

Would it be possible to add preloading to the API so slides are first loaded with preload attribute, rendering off-screen, and they have to call onReady when the load completed?

@wmertens maybe it is not actual anymore :smiley:
There is a library https://github.com/mbrevda/react-image which can preload images before display component


Convert status to int

As we parse a TSV, everything is a string. Figure out what other fields should be non-strings and parse them accordingly.

isn't this already been fixed by https://github.com/axiomhq/axiom-cloudfront-lambda/pull/12?

yep


Test suite errors with 0.56.4

Describe the bug
I tried to build the Debian package of the last tagged release of cogent3 2022.10.31a1 with numba version 0.56.4.  Unfortunately this leads to build time test issues.
To Reproduce
There is a build log in Debian CI which shows several errors where I can see lots of references to numba.  If you want to see all involved versions you can look at the raw build log
Expected behavior
Enable passing the tests with numba 0.56.
Desktop (please complete the following information):

OS: Debian
Version: unstable

Additional context
Due to the issues with numba there is a problem with cogent3.  We are about to freeze Debian for the next release cycle and thus cogent3 would not be part of the next Debian release if this can't be fixed soon.
Kind regards, Andreas.

This seems to be an error in the Debian build system, trying to compile cogent3 for an unsupported Python version.
cogent3 does not yet support python 3.11 (version limits are defined in our pyproject.toml file and reflected in the pypi listing) because numba does not yet support that version.

Am Sun, Jan 15, 2023 at 03:01:04PM -0800 schrieb GavinHuttley:

This seems to be an error in the Debian build system, trying to compile cogent3 for an unsupported Python version.
cogent3 does not yet support python 3.11 (version limits are defined in our pyproject.toml file and reflected in the pypi listing) because numba does not yet support that version.

The Debian Python team has decided to set Python 3.11 as default and we are working really hard together with numba.  I admit I'm not happy about pushing/forcing 3.11 but we somehow need to deal with this.
Kind regards, Andreas.

I can't do anything until numba is on 3.11. As soon as they've released a 3.11 compatible version, I'll do another release.

Just letting you know that the closest I've been able to find regarding a release date for python 3.11 numba compatible is ~3 weeks away according to this comment on the numba issue tracker.

Closing this since numba updated


add ScriptInitializer

also add the default gradle wrapper
this is something tht came out of trying to kastree with kotlin-scripting
the KtFIle can be gotten during the evaluation of scripts and passed to the following function to convert:
   open fun convertScript(v: KtFile): Node.Script {
        val ktScript = v.declarations.firstIsInstanceOrNull<KtScript>()!!
        return Node.Script(
            anns = convertAnnotationSets(v),
            pkg = v.packageDirective?.takeIf { it.packageNames.isNotEmpty() }?.let(::convertPackage),
            imports = v.importDirectives.map(::convertImport),
            exprs = ktScript.blockExpression.statements.map(::convertExpr)
        ).map(v)
    }

i noticed later that kastree does not keep offset data andas such its useless for highlighting code, i still hope this might be useful

@NikkyAI When you say offset are you talking about being able to determine line/column?  Does this help? https://github.com/cretz/kastree/issues/16

@NikkyAI - Thanks! Will look when I can, not using this (or Kotlin) much lately. Also have been avoiding committing gradle wrapper a bit.
@impatient - I suggest an identity map there, but another option is each Node has a tag field that you can set w/ offset or PSI info or whatever.


Publish Test Result task: Discrepancy between reported Test results of NUnit2/NUnit3

Please tag as Question
Environment

Server - TFS on-prem 2017 Version 15.117.27024.0

Issue Description
I noticed an (intended?) discrepancy between published NUnit2 and NUnit3 verdicts.
In Test Run explorer they are reported as following:

NUnit2 (respective their NUnit3 counterparts)
Published NUnit2
Published NUnit3

Success/Passed
Passed
Passed

Failure/Failed
Failed
Failed

Error
Failed
Failed

Inconclusive
Passed
Inconclusive

Skipped
Passed
Failed

Ignored
NotExecuted
NotExecuted

Cancelled
Failed
Failed

NotRunnable
Passed
Failed

Mainly I am interested in the mismatches of skipped, inconclusive and not-runnable tests (see above).

Hi @GraueEminenz79,
We are working to correct this behaviour and changing for skipped and NotRunnable to be marked as NotExecuted for NUnit3 and NUnit2.
Can you please share if you have any concern with this? Although it changes the behaviour for exsisting customers as the test pass % wont be impacted this shouldn't be a breaking change. Love to hear your thoughts before we make the change.

NUnit2 (respective their   NUnit3 counterparts)
Published NUnit2
Published NUnit3
New Status

Success/Passed
Passed
Passed
Passed

Failure/Failed
Failed
Failed
Failed

Error
Failed
Failed
Failed

Inconclusive
Passed
Inconclusive
Inconclusive

Skipped
Passed
Failed
Not executed

Ignored
NotExecuted
NotExecuted
NotExecuted

Cancelled
Failed
Failed
Failed

NotRunnable
Passed
Failed
Not executed

Hi @divais,
I can't speak for the NUnit (dev) community but it seems plausible for me (and my team).
We support your efforts in harmonizing these test verdicts.
Thanks & kind regards
J

Hi @divais,
in my opinion the new states make a lot of sense. Especially that NUnit2 and 3 will now have consistent states is definitively a good idea 👍
Best regards,
Dom

Thanks @domischell , we are ON it!

This has been fixed. Closing this

Closing the issue.


Dynamically loading test blocks

Some progress made on issue #36
A bunch of tests are failing now because we are testing all blocks under /data/blocks, and some of them are giving errors
We might check them.

I've added your suggestions. Those are the blocks failing in tests:

All parsers › builder-render-block

SyntaxError: JSON5: invalid end of input at 1:1

      490 |   );
      491 |   try {
    > 492 |     return JSON5.parse(toParse);

All parsers › builder-render-content

SyntaxError: JSON5: invalid end of input at 1:1

      490 |   );
      491 |   try {
    > 492 |     return JSON5.parse(toParse);

Html parser › form

SyntaxError: unknown: Unexpected token, expected ";" (1:12)

    > 1 | let _ = get submissionState() {
        |             ^
      2 |   return Builder.isEditing && props.previewState || state.state;
      3 | }

Html parser › columns

SyntaxError: unknown: Unexpected token, expected ";" (3:13)

      1 | let _ = // TODO: These methods are not used right now, but they will be when
      2 | // support for dynamic CSS lands
    > 3 | getColumns() {
        |              ^

Thanks @luislpv22 I'll take another look later today :)

hey @mandx - any update here?

@luislpv22 Looks like this PR has diverged a lot from the main branch; I'll suggest two things to get this restarted:

Start over with a new/fresh branch, copy code as needed from this branch.
Try make additive changes, that is, let's introduce new unit-tests modules/files/snapshots instead of overwriting existing ones; worst case, we would be testing the same thing twice, but this will allow avoiding rebase/merge hell since the new PR will be mostly adding code instead of modifying existing code. We can always remove duplicated tests in a secondary PR.

closing out due to inactivity to keepour PR list clean, please feel free to reopen @luislpv22 if you'd like to continue on this


New Version: VMware.HorizonClient version <IP_ADDRESS>805

[x] Have you signed the Contributor License Agreement?

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

PR#87334 currently does not work and should be closed in favor of this PR.  See the screenshot below for this working package.

[x] Does your manifest conform to the 1.2 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@mdanish-kh - I've committed your suggestion.  should be good to go now.  Thanks!


[flutter_tools] Add support for web in plugin template.

Description

Migrate the example plugin to be instance-based instead of all static. Update usages.
Federate the sample plugin so web can be implemented:

Separate platform interface from implementations.
Core plugin uses only platform.
Web may override implementation of said platform.
Defaults to MethodChannel version.

Add web implementation of the plugin (when requested)
Add test.

Related Issues

https://github.com/flutter/flutter/issues/59562

Tests
I added the following tests:
flutter_tools/test/commands.shard/permeable/create_test.dart:

plugin project supports web
Asserted lib/src/flutter_project_web.dart is not created by default.

Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.

cc @jonahwilliams The web template is currently missing. So we can't really do flutter add-platform --platform web yet. This PR is to add the template.

We can add a web template with the existing design, but you can't change the existing template like this since it will need to work with add-platform.
Modifications would have to be in a  plugin_2 - an entirely separate template

"it will need to work with add-platform"
What needs to happen for that to be true? How do I test "add-platform"?

It looks like you're modifying the main platform file here: https://github.com/flutter/flutter/pull/59700/files#diff-7e8eece56f751946af82080aaa3d26a9 , right?

It looks like you're modifying the main platform file here: https://github.com/flutter/flutter/pull/59700/files#diff-7e8eece56f751946af82080aaa3d26a9 , right?

@jonahwilliams Yes, I guess this is not backwards compatible with plugins generated before this change.

I've redone this here, in a way that should be backwards compatible:
https://github.com/flutter/flutter/pull/60116


Filter List Does Not Populate After Inital Setup & Import

Just created a new MySQL database with a single file and after initial import the filter list does not populate my collection until both Server and Desktop are restarted.
Server Log
2016-07-14.txt
EDIT:
Seems to also happen with SQLite.

Recompiled JMM Server and Desktop and with new database do not have this problem.
I blame Gremlins.


More detailed documentation on email notifications triggered by certificate lifetime events

I can set certificate contracts from portal or powershell script. Can you include in the documentation for which events the certificate contracts get email notification and when? For example when should I expect the certificate expiration email?

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

ID: adde7541-5e77-17e0-5f7d-9690215b2064
Version Independent ID: 5888b1c0-7685-028e-7168-2a3bcdbdd514
Content: About Azure Key Vault certificate renewal
Content Source: articles/key-vault/certificates/overview-renew-certificate.md
Service: key-vault
Sub-service: certificates
GitHub Login: @msmbaldwin
Microsoft Alias: sebansal

@feroz-ahmmed Thank you for your feedback . We will investigate and update the thread.

The article does describe the events around certificate lifetime events in this section as following .
The notifications are sent if a certificate's policy is set to auto renewal .

Before certificate renewal
After certificate renewal, stating if the certificate was successfully renewed, or if there was an error, requiring manual renewal of the certificate.
When a certificate policy that is set to be manually renewed (email only), a notification is sent when it's time to renew the certificate.

Hope this helps.


Update ico package

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[x] No

Checklist

[ ] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[x] I have added a convincing reason for adding this feature, if necessary

Other information
ico version 0.1 requires png version 0.11, and is the only package in the Tauri project to require this old version. Recently, an update was pushed to ico which bumped the version to 0.2 and updated png to the latest version, 0.17 (the same version Tauri uses elsewhere.)
This change was 100% backward compatible with Tauri's usage of the ico package and no code in Tauri needs to be changed, just a version bump where the dependency is listed. I've confirmed by looking in the generated Cargo.lock that there is now only one version of png that needs to be built, version 0.17.
I'm not sure if there's a schedule for updating dependencies but this change is trivial and also won't be automatic just by running cargo update so I figured I'd open this PR and see what happens haha

We use renovate to update dependencies but it only runs Wednesdays and ico was released just 2 hours ago so it wasn't updated the last time it ran.

@FabianLars should I close this pr then?

leave it open for now, let's see what Lucas thinks

Fixed conflicts because the ico version in tauri-codegen was updated but not the optional dep in the main tauri package

We usually don't include dependency bumps in the changelog (too many damn dependencies) but we'll need to publish a patch for 1.2 soon anyway :)


update devdependency standard to v16

Update standard and fix linting issues.
Alternatively (if for some reason we want to use var) we could switch the linter to eslint and use eslint-config-standard and turn some rules off.

Ya I think the tests or other linting rules would have caught any issues. There were a few places I had to manually fix because --fix wouldn't fix them automatically.

⚠ This issue has been locked due to age. If you have encountered a recent
problem that seems to be covered by this issue, please open a new issue.
Please include a minimal reproducible example
when opening a new issue.


Use anonymous class

Could you see why Travis is failing?

hmm.. it's not worth the trouble and one of the tests is now removed...

Hm. Okey.


Compilation error for 0.8.1 with CUDA 11.2

The conda-forge bot is building the new deepspeed packages for 0.8.1. See https://github.com/conda-forge/deepspeed-feedstock/pull/6#issuecomment-1436120690 for context.
All the builds for CUDA 11.2 are failing because of the below error:
  /home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_build_env/bin/x86_64-conda-linux-gnu-c++ -shared -Wl,--allow-shlib-undefined -Wl,-rpath,/home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/lib -Wl,-rpath-link,/home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/lib -L/home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/lib -Wl,--allow-shlib-undefined -Wl,-rpath,/home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/lib -Wl,-rpath-link,/home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/lib -L/home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/lib -Wl,-O2 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -Wl,--disable-new-dtags -Wl,--gc-sections -Wl,--allow-shlib-undefined -Wl,-rpath,/home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/lib -Wl,-rpath-link,/home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/lib -L/home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/lib -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O2 -ffunction-sections -pipe -isystem /home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/include -fdebug-prefix-map=/home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/work=/usr/local/src/conda/deepspeed-0.8.1 -fdebug-prefix-map=/home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p=/usr/local/src/conda-prefix -isystem /usr/local/cuda/include -DNDEBUG -D_FORTIFY_SOURCE=2 -O2 -isystem /home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/include -isystem /usr/local/cuda/include build/temp.linux-x86_64-cpython-311/csrc/lamb/fused_lamb_cuda.o build/temp.linux-x86_64-cpython-311/csrc/lamb/fused_lamb_cuda_kernel.o -L/home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/lib/python3.11/site-packages/torch/lib -lc10 -ltorch -ltorch_cpu -ltorch_python -o build/lib.linux-x86_64-cpython-311/deepspeed/ops/lamb/fused_lamb_op.cpython-311-x86_64-linux-gnu.so
  building 'deepspeed.ops.quantizer.quantizer_op' extension
  creating build/temp.linux-x86_64-cpython-311/csrc/quantization
  /usr/local/cuda/bin/nvcc -Icsrc/includes -I/home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/lib/python3.11/site-packages/torch/include -I/home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/lib/python3.11/site-packages/torch/include/torch/csrc/api/include -I/home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/lib/python3.11/site-packages/torch/include/TH -I/home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/lib/python3.11/site-packages/torch/include/THC -I/home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/include/python3.11 -c csrc/quantization/dequantize.cu -o build/temp.linux-x86_64-cpython-311/csrc/quantization/dequantize.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-options '-fPIC' -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE=\"_gcc\" -DPYBIND11_STDLIB=\"_libstdcpp\" -DPYBIND11_BUILD_ABI=\"_cxxabi1014\" -DTORCH_EXTENSION_NAME=quantizer_op -D_GLIBCXX_USE_CXX11_ABI=1 -gencode=arch=compute_60,code=sm_60 -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_70,code=sm_70 -gencode=arch=compute_75,code=sm_75 -gencode=arch=compute_80,code=sm_80 -gencode=arch=compute_86,code=compute_86 -gencode=arch=compute_86,code=sm_86 -ccbin /home/conda/feedstock_root/build_artifacts/deepspeed_1676841729762/_build_env/bin/x86_64-conda-linux-gnu-cc -std=c++14
  csrc/includes/reduction_utils.h(170): error: no operator "+" matches these operands
              operand types are: const __half + const __half

  csrc/includes/reduction_utils.h(199): error: no operator "+" matches these operands
              operand types are: const __half2 + const __half2

  csrc/includes/dequantization_utils.h(165): warning: constexpr if statements are a C++17 feature
            detected during:
              instantiation of "void dequantize_kernel<T,numBits,qType,unroll,threads>(T *, const int8_t *, const float *, int, int) [with T=__half, numBits=8, qType=quantize::Type::Symmetric, unroll=8, threads=512]"
  csrc/quantization/dequantize.cu(45): here
              instantiation of "void launch_dequantize_kernel(T *, const int8_t *, const float *, quantize::Type, int, int, int, cudaStream_t) [with T=__half]"
  csrc/quantization/dequantize.cu(55): here

  csrc/includes/quantization_utils.h(124): error: no suitable conversion function from "__half" to "float" exists
            detected during:
              instantiation of "T quantize::Params<quantize::Type::Asymmetric, numBits>::dequantize<T>(int8_t) [with numBits=8, T=float]"
  csrc/includes/dequantization_utils.h(75): here
              instantiation of "void dequantize::chunk(T *, const int8_t *, dequantize::Params<qType, numBits>) [with T=float, numBits=8, qType=quantize::Type::Asymmetric]"
  csrc/includes/dequantization_utils.h(151): here
              instantiation of "void dequantize::_to_global<T,numBits,qType,unroll,threads>(T *, const int8_t *, const float *, int, int) [with T=float, numBits=8, qType=quantize::Type::Asymmetric, unroll=8, threads=512]"
  csrc/includes/dequantization_utils.h(167): here
              instantiation of "void dequantize::to_global<T,numBits,qType,unroll,threads>(T *, const int8_t *, const float *, int, int) [with T=float, numBits=8, qType=quantize::Type::Asymmetric, unroll=8, threads=512]"
  csrc/quantization/dequantize.cu(18): here
              instantiation of "void dequantize_kernel<T,numBits,qType,unroll,threads>(T *, const int8_t *, const float *, int, int) [with T=float, numBits=8, qType=quantize::Type::Asymmetric, unroll=8, threads=512]"
  csrc/quantization/dequantize.cu(47): here
              instantiation of "void launch_dequantize_kernel(T *, const int8_t *, const float *, quantize::Type, int, int, int, cudaStream_t) [with T=float]"
  csrc/quantization/dequantize.cu(64): here

  csrc/includes/quantization_utils.h(124): error: no suitable conversion function from "__half" to "float" exists
            detected during:
              instantiation of "T quantize::Params<quantize::Type::Asymmetric, numBits>::dequantize<T>(int8_t) [with numBits=4, T=float]"
  csrc/includes/dequantization_utils.h(78): here
              instantiation of "void dequantize::chunk(T *, const int8_t *, dequantize::Params<qType, numBits>) [with T=float, numBits=4, qType=quantize::Type::Asymmetric]"
  csrc/includes/dequantization_utils.h(151): here
              instantiation of "void dequantize::_to_global<T,numBits,qType,unroll,threads>(T *, const int8_t *, const float *, int, int) [with T=float, numBits=4, qType=quantize::Type::Asymmetric, unroll=8, threads=512]"
  csrc/includes/dequantization_utils.h(167): here
              instantiation of "void dequantize::to_global<T,numBits,qType,unroll,threads>(T *, const int8_t *, const float *, int, int) [with T=float, numBits=4, qType=quantize::Type::Asymmetric, unroll=8, threads=512]"
  csrc/quantization/dequantize.cu(18): here
              instantiation of "void dequantize_kernel<T,numBits,qType,unroll,threads>(T *, const int8_t *, const float *, int, int) [with T=float, numBits=4, qType=quantize::Type::Asymmetric, unroll=8, threads=512]"
  csrc/quantization/dequantize.cu(51): here
              instantiation of "void launch_dequantize_kernel(T *, const int8_t *, const float *, quantize::Type, int, int, int, cudaStream_t) [with T=float]"
  csrc/quantization/dequantize.cu(64): here

  4 errors detected in the compilation of "csrc/quantization/dequantize.cu".
  error: command '/usr/local/cuda/bin/nvcc' failed with exit code 1
  error: subprocess-exited-with-error

  × Running setup.py install for deepspeed did not run successfully.
  │ exit code: 1
  ╰─> See above for output

See also the build script below:
# Deepspeed ops cannot be built without CUDA
if [[ ${cuda_compiler_version} != "None" ]]; then
  export DS_BUILD_OPS=1

  # Set the CUDA arch list from
  # https://github.com/conda-forge/pytorch-cpu-feedstock/blob/2be0b38024b3b5601fcefce40596fc2a5fce4ab7/recipe/build_pytorch.sh#L94

  if [[ ${cuda_compiler_version} == 10.* ]]; then
    export TORCH_CUDA_ARCH_LIST="6.0;6.1;7.0;7.5+PTX"
  elif [[ ${cuda_compiler_version} == 11.0* ]]; then
    export TORCH_CUDA_ARCH_LIST="6.0;6.1;7.0;7.5;8.0+PTX"
  elif [[ ${cuda_compiler_version} == 11.1 ]]; then
    export TORCH_CUDA_ARCH_LIST="6.0;6.1;7.0;7.5;8.0;8.6+PTX"
  elif [[ ${cuda_compiler_version} == 11.2 ]]; then
    export TORCH_CUDA_ARCH_LIST="6.0;6.1;7.0;7.5;8.0;8.6+PTX"
  else
    echo "Unsupported cuda version. edit build.sh"
    exit 1
  fi

else
  export DS_BUILD_OPS=0
fi

# Disable sparse_attn since it requires an exact version of triton==1.0.0
export DS_BUILD_SPARSE_ATTN=0

python -m pip install . -vv

The conda builds were working fine for 0.8.0, so I wonder whether there could be any specific changes to 0.8.1 that could explain this error? Also is CUDA 11.2 officially supported (I could not find the information in this repo)?

I am also having issues:
I am using Ubuntu 20.04.  Compiling version 0.8.1 with my docker image as you can see here also leads to issues.
This works:
DS_BUILD_OPS=1 pip install<EMAIL_ADDRESS>
This does not:
DS_BUILD_OPS=1 pip install<EMAIL_ADDRESS>

Ok, so it does not seem to be conda-forge specific.

Just here to say I have the same issue compiling 0.8.1 on my repository: https://github.com/P2Enjoy/kohya_ss-docker

I also ran into the same issue compiling 0.8.1 with CUDA 11.7. It seems doesn't occur when compiling version 0.8.0
10 errors detected in the compilation of "csrc/quantization/dequantize.cu".
error: command '/usr/local/cuda/bin/nvcc' failed with exit code 1

same to me with 0.8.2 using cuda 11.3
building 'deepspeed.ops.quantizer.quantizer_op' extension
creating build/temp.linux-x86_64-3.9/csrc/quantization
/g/data/z00/yxs900/installation/cuda/11.3.0/bin/nvcc -Icsrc/includes -I/g/data/z00/yxs900/installation/pytorch/v1.12.1/lib/python3.9/site-packages/torch/include -I/g/data/z00/yxs900/installation/pytorch/v1.12.1/lib/python3.9/site-packag
es/torch/include/torch/csrc/api/include -I/g/data/z00/yxs900/installation/pytorch/v1.12.1/lib/python3.9/site-packages/torch/include/TH -I/g/data/z00/yxs900/installation/pytorch/v1.12.1/lib/python3.9/site-packages/torch/include/THC -I/ap
ps/python3/3.9.2/include/python3.9 -c csrc/quantization/dequantize.cu -o build/temp.linux-x86_64-3.9/csrc/quantization/dequantize.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_
NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-options '-fPIC' -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE="_gcc" -DPYBIND11_STDLIB="_libstdcpp" -DPYBIND11_BUILD_ABI="_cxxabi1013" -DTORCH_EXTENSION_NAME=quantizer_
op -D_GLIBCXX_USE_CXX11_ABI=1 -gencode=arch=compute_70,code=sm_70 -gencode=arch=compute_80,code=sm_80 -std=c++14
csrc/includes/reduction_utils.h(170): error: no operator "+" matches these operands
            operand types are: const __half + const __half

csrc/includes/reduction_utils.h(199): error: no operator "+" matches these operands
            operand types are: const __half2 + const __half2

csrc/includes/dequantization_utils.h(165): warning: constexpr if statements are a C++17 feature
          detected during:
            instantiation of "void dequantize_kernel<T,numBits,qType,unroll,threads>(T *, const int8_t *, const float *, int, int) [with T=__half, numBits=8, qType=quantize::Type::Symmetric, unroll=8, threads=512]"
csrc/quantization/dequantize.cu(45): here
            instantiation of "void launch_dequantize_kernel(T *, const int8_t *, const float *, quantize::Type, int, int, int, cudaStream_t) [with T=__half]"
csrc/quantization/dequantize.cu(55): here

csrc/includes/quantization_utils.h(124): error: no suitable conversion function from "__half" to "float" exists
          detected during:
            instantiation of "T quantize::Params<quantize::Type::Asymmetric, numBits>::dequantize<T>(int8_t) [with numBits=8, T=float]"
csrc/includes/dequantization_utils.h(75): here
            instantiation of "void dequantize::chunk(T *, const int8_t *, dequantize::Params<qType, numBits>) [with T=float, numBits=8, qType=quantize::Type::Asymmetric]"
csrc/includes/dequantization_utils.h(151): here
            instantiation of "void dequantize::_to_global<T,numBits,qType,unroll,threads>(T *, const int8_t *, const float *, int, int) [with T=float, numBits=8, qType=quantize::Type::Asymmetric, unroll=8, threads=512]"
csrc/includes/dequantization_utils.h(167): here
            instantiation of "void dequantize::to_global<T,numBits,qType,unroll,threads>(T *, const int8_t *, const float *, int, int) [with T=float, numBits=8, qType=quantize::Type::Asymmetric, unroll=8, threads=512]"
csrc/quantization/dequantize.cu(18): here
            instantiation of "void dequantize_kernel<T,numBits,qType,unroll,threads>(T *, const int8_t *, const float *, int, int) [with T=float, numBits=8, qType=quantize::Type::Asymmetric, unroll=8, threads=512]"
csrc/quantization/dequantize.cu(47): here
            instantiation of "void launch_dequantize_kernel(T *, const int8_t *, const float *, quantize::Type, int, int, int, cudaStream_t) [with T=float]"
csrc/quantization/dequantize.cu(64): here

csrc/includes/quantization_utils.h(124): error: no suitable conversion function from "__half" to "float" exists
          detected during:
            instantiation of "T quantize::Params<quantize::Type::Asymmetric, numBits>::dequantize<T>(int8_t) [with numBits=4, T=float]"
csrc/includes/dequantization_utils.h(78): here
            instantiation of "void dequantize::chunk(T *, const int8_t *, dequantize::Params<qType, numBits>) [with T=float, numBits=4, qType=quantize::Type::Asymmetric]"
csrc/includes/dequantization_utils.h(151): here
            instantiation of "void dequantize::_to_global<T,numBits,qType,unroll,threads>(T *, const int8_t *, const float *, int, int) [with T=float, numBits=4, qType=quantize::Type::Asymmetric, unroll=8, threads=512]"
csrc/includes/dequantization_utils.h(167): here
            instantiation of "void dequantize::to_global<T,numBits,qType,unroll,threads>(T *, const int8_t *, const float *, int, int) [with T=float, numBits=4, qType=quantize::Type::Asymmetric, unroll=8, threads=512]"
csrc/quantization/dequantize.cu(18): here
            instantiation of "void dequantize_kernel<T,numBits,qType,unroll,threads>(T *, const int8_t *, const float *, int, int) [with T=float, numBits=4, qType=quantize::Type::Asymmetric, unroll=8, threads=512]"
csrc/quantization/dequantize.cu(51): here
            instantiation of "void launch_dequantize_kernel(T *, const int8_t *, const float *, quantize::Type, int, int, int, cudaStream_t) [with T=float]"
csrc/quantization/dequantize.cu(64): here

4 errors detected in the compilation of "csrc/quantization/dequantize.cu".
error: command '/g/data/z00/yxs900/installation/cuda/11.3.0/bin/nvcc' failed with exit code 1

I met the same issue when compiling version 0.8.3. And after debugging, I found the reason.
I built the deepspeed on a machine without gpu, so the nvcc compilation arguments are ignored, but the quantizer need those arguments.
See  https://github.com/microsoft/DeepSpeed/blob/94f7da26b632f53b0a29ac54854cb8899e0d5b9e/op_builder/builder.py#L40-L41 https://github.com/microsoft/DeepSpeed/blob/94f7da26b632f53b0a29ac54854cb8899e0d5b9e/op_builder/builder.py#L91-L93 https://github.com/microsoft/DeepSpeed/blob/94f7da26b632f53b0a29ac54854cb8899e0d5b9e/op_builder/builder.py#L623-L631
After I commetted this, I can finish my compilation.
https://github.com/microsoft/DeepSpeed/blob/94f7da26b632f53b0a29ac54854cb8899e0d5b9e/op_builder/builder.py#L40-L41


During training, entities are disappearing in the training metrics

Hi, I have the following entities I want to extract. During the training, some entities are not shown in the table and keep disappearing. When I restart the training process, the number of entities shown in the metric table is also different. It gives me an inconsistent result. Do you know what I can do to fix it?
Entities_list = [
"invoice_date",
"tax_rate",
"subtotal",
"total"
]
For example,
+--------------+-------+-------+-------+-------+
| name         |   mEP |   mER |   mEF |   mEA |
+==============+=======+=======+=======+=======+
| total        |     0 |     0 |     0 |     0 |
+--------------+-------+-------+-------+-------+
| invoice_date |     0 |     0 |     0 |     0 |
+--------------+-------+-------+-------+-------+
| overall      |     0 |     0 |     0 |     0 |
+--------------+-------+-------+-------+-------+
+--------------+-------+-------+-------+-------+
| name         |   mEP |   mER |   mEF |   mEA |
+==============+=======+=======+=======+=======+
| invoice_date |     0 |     0 |     0 |     0 |
+--------------+-------+-------+-------+-------+
| overall      |     0 |     0 |     0 |     0 |

@sophiajwchoi One possible reason is that your train batch data don't contain the entity label provided in Entities_list. Make sure the input data has the corresponding entity value. Hope it can help you.


Values not populated when using hideExpression

I'm submitting a ...  (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request

Current behavior

When formModel is loaded asynchronously (eg. editing some data from server) and the form uses hideExpression on some of its fields, values for these fields don't get populated to form.
Expected behavior

Values from the model should be available in the form.
Minimal reproduction of the problem with instructions

https://stackblitz.com/edit/angular-jjhxfl
What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Angular version: 4.3.6 and 5.0.2

Browser: all

Language: TypeScript 2.4.2

Node (for AoT issues): node --version =   v9.2.0

neither model nor validation are applied when combining hideExpression  with the key, you can achieve your use case using fieldGroup:
    {
      hideExpression: 'model.group_id !== "3"',
      fieldGroup: [
        {
          type: 'input',
          key: 'group.demo_input',
          templateOptions: {
            label: 'Demo input'
          },
        }
      ]
    }

well I think this is bug and the new model value should be taken into account


[3.22.2][stable] Current included Dart SDK breaks pub.dev proxying due to security advisories

Hi,
The current stable Flutter version includes Dart 3.4.3, which currently breaks artifactory proxying.
As such, we are unable to update from Flutter 3.19.x to 3.22.x as flutter pub is broken due as we use an artifact proxy.
Building flutter tool...
Resolving dependencies...
Downloading packages...

This is fixed in Dart 3.4.4: https://github.com/dart-lang/pub/pull/4275
Can we get a 3.22.3 release with a Dart SDK bump? I assume we don't want the current stable to have breaking issues.
Thanks!

Can we get a 3.22.3 release with a Dart SDK bump? I assume we don't want the current stable to have breaking issues.

@thomas-stockx Maybe you can raise cherry-pick request using the template for team to review and decide.

Hi @darshankawar,
I'd love to but I have no idea what the process is to update the included Dart SDK in Flutter.
According to this comment, it's not trivial, so I just wanted to flag this for the team as I don't know how to proceed.

I will keep the issue open for team's input on this.
/cc @stuartmorgan for thoughts.

I'd love to but I have no idea what the process is to update the included Dart SDK in Flutter.
According to this comment, it's not trivial

That comment is about what would be involved if an end-user of Flutter wanted to try to combine wildly different versions of Dart and Flutter after the fact, not about the normal process of Dart updates.
@itsjustkevin Is picking up the latest Dart stable bugfix release a standard part of the process when cutting a Flutter stable bugfix release, or do we need an issue tracking it?

@stuartmorgan Flutter releases pick up the latest Dart stable releases.  The current release being built includes Dart 3.4.4.

That's what I thought, thanks for confirming!

Is there currently a bugfix release planned for Flutter 3.22.x? It seems there's nothing to be done in the flutter repo to resolve this issue, as it will be resolved automatically with a new Flutter stable release.
Thanks for looking into this so quickly!

Is there currently a bugfix release planned for Flutter 3.22.x? It seems there's nothing to be done in the flutter repo to resolve this issue, as it will be resolved automatically with a new Flutter stable release.
Thanks for looking into this so quickly!

The next Flutter SDK release will be include Dart 3.4.4 and will come out imminently (this is what I'm currently working on)


samba: fails with whitespace in attribute

Issue description
I configured it like the example from http://nixos.org/nixos/options.html#samba but it fails.
Steps to reproduce

configure samba

  services.samba = {
    enable = true;
    shares = {
      Backup = {
        browseable = "yes";
        comment = "Backup Share";
        guest ok = "yes";
        path = "/tmp";
        read only = true;
      };
    };
  };

rebuild and get error

# nixos-rebuild switch --show-trace
...
error: while evaluating the attribute ‘config.system.build.toplevel’ at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/nixos/lib/eval-config.nix:53:5:
while evaluating the attribute ‘config’ at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:87:25:
while evaluating ‘yieldConfig’ at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:74:29, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:73:16:
while evaluating ‘mergeModules’ at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:178:26, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:64:17:
while evaluating ‘mergeModules'’ at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:182:36, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:179:5:
while evaluating ‘concatMap’ at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/lists.nix:79:18, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:218:9:
while evaluating ‘reverseList’ at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/lists.nix:256:17, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:64:38:
while evaluating ‘closeModules’ at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:91:27, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:59:16:
while evaluating anonymous function at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/lists.nix:71:28, called from undefined position:
while evaluating anonymous function at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:93:49, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/lists.nix:71:31:
while evaluating ‘unifyModuleSyntax’ at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:108:34, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:99:11:
while evaluating ‘applyIfFunction’ at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:132:29, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:99:39:
syntax error, unexpected ID, expecting '.' or '=', at /root/nixos/nas/configuration.nix:78:15

line 78 is guest ok = "yes"; so i'm pretty sure the problem is the whitespace.
/cc @ehmry
Technical details

System: NixOS 17.03.1091.dc7dc77cde (Gorilla)
Nix version: nix-env (Nix) 1.11.8
Nixpkgs version: "17.03.1091.dc7dc77cde"

Whitespace is the problem, { guest ok = true; } is invalid but { "guest ok" = true; } works. The example encloses the attribute name in quotes as it is written but when it is rendered the quotes disappear. Unfortunately wrapping the example in literalExample does not fix this.
@davidak Do you think mentioning this whitespace issue in the description would be enough?

@ehmry thanks for the fast reply! i changed the title.

Workaround for this special case:
Use "public" and "writable" instead of "guest ok" and "read only".
To have a sane solution here we might get the doc to display the quotes somehow.

Rsync has the same problem with the read only option.
http://nixos.org/nixos/options.html#rsync

Any news on this issue?


How do I make SELECT ALL on checkboxes?

For Checkboxes, I want something like this:
http://jsfiddle.net/rebornlab/KHxcL/
A Select All button or Checkbox, which triggers to select or de-select all checkboxes within that group.
Hope that fiddle make more sense? I want to achieve this via jsonform.

I think that's out of the scope of the lib but you can try to use the  onClick event to insert your own javascript on a field to that avail, see https://github.com/jsonform/jsonform/wiki#using-event-handlers-to-react-on-fields-updates-in-real-time

Thank you. I was able to achieve it via JQuery. If you want, add this as a example may be?
{   "schema": {     "menu": {       "type": "array",       "title": "Options",       "items": {         "type": "string",         "title": "Option",         "enum": [           "starter",           "maincourse",           "cheese",           "dessert",           "keyur"         ]       }     }   },   "form": [     {       "key": "menu",       "type": "checkboxes",       "htmlClass": "custom-checkbox-name"     },     {       "type": "button",       "title": "SELECT ALL",       "onClick": function () {         $( ".custom-checkbox-name .controls :checkbox").prop("checked", true);       }     },     {       "type": "button",       "title": "UNSELECT ALL",       "onClick": function () {         $( ".custom-checkbox-name .controls :checkbox").prop("checked", false);       }     }   ] }


Docfix "docker search"

Most of the changes are to update the output of the example docker search command.  In only one instance was the output left intact and the command modified to insert --no-index.
As this is my first PR to projectatomic/docker, i'm taking the "baby steps" approach:

I have not squashed.
If/When the changes are approved, i will squash, aggregating the individual commit messages into a list of changes in the squashed commit message.
Is that OK?  Any hints on process/workflow very much appreciated.

bot, add author to whitelist

Could you put these all in one pull request.  Then I will merge.  Thanks.

@rhatdan Done.

I merged this change and combined it with the original patch.  @runcom Please add this to your patches also.

Will do thx Dan

The contents of this patch are now merged into branch rhel7-1.10  as of https://github.com/projectatomic/docker/commit/6013c2d2ccc3d9b10bb856de722a5bcd6d22193f so, deleting this branch.


Add page to encourage visitors to contribute

Add a page
Show it in the top menu bar

Content needs to be about

Please contribute, even if a little
If you can't code then help in documentation
Please, please contribute.
Please, please contribute.
Please, please contribute.

You get the idea.

https://pelican-elegant.github.io/contribute is already live, so I think we can close this.


Add all the subpackages for each microservice

Fixes #11391
Status
not-tested
Description
Lack of subpackages has been tracked down to the setup_build.py script, which looks for the + sign in the package name to decide whether to recursively look for packages or not. I fixed only a couple of pylints on that one.
Real change has been made to the setup_dependencies module, where we list the required packages for each of the microservices.
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
None. However, a different way to fix it would be by enabling all the subpackages to be added by default. It might be less error prone in the future, but it would remove one level of freedom that we have right now...
External dependencies / deployment changes
New Pypi packages need to be rebuilt.

@vkuznet I pushed in a second commit with a short documentation on this list of dependencies and how things are structured. Please have another look.

Unstable unit test, merging it.


⚠ RPC server - Conflux has degraded performance

In ade6fd5, RPC server - Conflux ($CONFLUX_RPC_URL) experienced degraded performance:

HTTP code: 0
Response time: 0 ms

Resolved: RPC server - Conflux performance has improved in 5ea2750 after 5 minutes.


In DB storage case, create metaprotocol and protocol tables properly

protocols  table isn't  created when database storage is chosen.
Even though, Migration.dataLocation is added to the migration creation (https://github.com/higherkindness/compendium/blob/c8da2e8bf74b76fa2211b1c67114d8f054341d53/src/main/scala/higherkindness/compendium/Main.scala#L52), it fails with the  exception:
[ioapp-compute-0] INFO org.flywaydb.core.internal.database.DatabaseFactory - Database: jdbc:postgresql://localhost:5432/postgres (PostgreSQL 10.8)
org.flywaydb.core.api.FlywayException: Validate failed:
Migration checksum mismatch for migration version 1
-> Applied to database :<PHONE_NUMBER>
-> Resolved locally    :<PHONE_NUMBER>

Each table should be created based on its own configuration.

Let's keep  metadata and data in separate databases. We should provide support for that even using the same Postgres instance. Let handle the connection for metadata and data databases separately.

I created this PR in order to make some tests for this issue. So, is it okay for you if I close the PR and delete the branch, @JesusMtnez ?

I'll handle that :wink:


[Feature Request] POI 5.x.x测试类

Checklist

[X] I searched exising issues and no one else requests similar feature.
[X] I think that 25%+ users are positive towards this feature.

Describe the feature
todo
Additional context
No response

Hello @unknowIfGuestInDream. This issue is marked as deprecated and closed.


Error while loading content of file theme1.xml.

When i write a data to the sheet for the first time it is working fine but for the second time i am getting below error. I am not getting this issue for all the sheet, Only for one particular sheet.  I am unable to identify what is in the excel sheet which is causing the error.  Please provide me your email so that I can share the excel sheet to you.
Error while loading content of file theme1.xml.
Error Domain=NSCocoaErrorDomain Code=260 "The operation couldn’t be completed. (Cocoa error 260.)" UserInfo=0x174660f80 {NSFilePath=/var/mobile/Containers/Data/Application/AAE85915-9D93-48E1-965B-8E2249AA149E/Library/Caches/fr.brae.spreadsheetdocument/test1-out.xlsx/xl/theme/theme1.xml, NSUnderlyingError=0x174243990 "The operation couldn’t be completed. No such file or directory"}
Thanks

Hi,
Maybe the file won't be necessary. I'll do some tests today.

Hello @karunakaran86,
you can send the file to rene[dot]bigot[at]brae[dot]fr

Hi,
I've just pushed some bug fixes. This bug may have been corrected.

Same here on OSX,Version is 2.0.1. Happens with every xlsx file

Hello,
Could you please send me the code a xlsx files by mail please ?
Thanx

the code "AND" the xlsx

Any XLSX example to post here ?


Propagated Parameters replaced Implicit Parameters

Changes

Propagated Parameters was designed and implemented to replace
Implicit Parameters to remove the mutation of specifications.
In this change, we update the alpha features table to remove the
Implicit Parameters and the broken link to its documentation,
and replace them with Propagated Parameters.
TEPs:

https://github.com/tektoncd/community/blob/main/teps/0107-propagating-parameters.md
https://github.com/tektoncd/community/blob/main/teps/0023-implicit-mapping.md

PRs:

https://github.com/tektoncd/pipeline/pull/4906
https://github.com/tektoncd/pipeline/pull/4845

/kind misc
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[n/a] Docs included if any changes are user facing
[n/a] Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Release notes block below has been filled in (if there are no user facing changes, use release note "NONE")

Release Notes

NONE

/lgtm

/test pull-tekton-pipeline-integration-tests

@afrittoli @abayer had to fix a merge conflict, please take a look

/lgtm