When PVC used in pipeline run is deleted before any tasks start, task run will be just stuck

When pipeline run uses pvc, either with volumeClaimTemplate or pre-created persistentVolumeClaim,
and you run the pipeline run and right after PVC is created (bound) you delete it (before any tasks start), it will be in 'terminating' state, and the task run will be just stuck.

@rcerven could you give a bit more context on the situation that results in a PVC being deleted just as a Task is starting?

@sbwsg it was just for my testing, but it can happen if you will have PVC pruner

the task run will be just stuck

@rcerven does this mean that the taskrun will not timeout, or is it stuck until timeout?

the task run will be just stuck

@rcerven does this mean that the taskrun will not timeout, or is it stuck until timeout?

how long is the timeout? I was waiting just for few minutes

how long is the timeout? I was waiting just for few minutes

By default PipelineRuns timeout after 60 min - https://github.com/tektoncd/pipeline/blob/main/docs/pipelineruns.md#configuring-a-failure-timeout. The default value can be modified in config-defaults.


Concurrent user creation issues

Triggering batch user creations (from the Enterprise API at least) fails for some users.
Related traces
Main issue: an script is too fast (and big) got route64 limits:
[ALERT] USER 'BARUCH29' SETUP FAILED (SERVER ID: 239371)
Exception: Fog::DNS::AWS::Error
Throttling => Rate exceeded

Server attributes:
#<Server id: 239371, user_id: 247569, subdomain: "baruch29", ip_address: "useb.ep.carto.com", port: 443, state: "creating_user", server_type: "dedicated", remote_user_id: "d68e20a6-874b-4e26-8b19-3898acca8faa", created_at: "2016-10-07 00:12:59", updated_at: "2016-10-07 00:13:20", setup_failed_at: "2016-10-07 00:13:20", database_host: "<IP_ADDRESS>">

/home/ubuntu/www/production.cartodb.com/shared/bundle/ruby/2.2.0/gems/excon-0.49.0/lib/excon/middlewares/expects.rb:6:in `response_call'
/home/ubuntu/www/production.cartodb.com/shared/bundle/ruby/2.2.0/gems/excon-0.49.0/lib/excon/middlewares/response_parser.rb:8:in `response_call'
/home/ubuntu/www/production.cartodb.com/shared/bundle/ruby/2.2.0/gems/excon-0.49.0/lib/excon/connection.rb:389:in `response'
/home/ubuntu/www/production.cartodb.com/shared/bundle/ruby/2.2.0/gems/excon-0.49.0/lib/excon/connection.rb:253:in `request'
/home/ubuntu/www/production.cartodb.com/shared/bundle/ruby/2.2.0/gems/excon-0.49.0/lib/excon/middlewares/idempotent.rb:26:in `error_call'
/home/ubuntu/www/production.cartodb.com/shared/bundle/ruby/2.2.0/gems/excon-0.49.0/lib/excon/middlewares/base.rb:10:in `error_call'

Trace:
PG::Error: ERROR: tuple concurrently updated

+ 18 non-project frames
19
File "/home/ubuntu/www/production.cartodb.com/releases/20160928141817/app/models/user/db_service.rb", line 925 in add_python
20
File "/home/ubuntu/www/production.cartodb.com/releases/20160928141817/app/models/user/db_service.rb", line 179 in load_cartodb_functions
21
File "/home/ubuntu/www/production.cartodb.com/releases/20160928141817/app/models/user/db_service.rb", line 1011 in create_own_schema
22
File "/home/ubuntu/www/production.cartodb.com/releases/20160928141817/app/models/user/db_service.rb", line 118 in new_organization_user_main_db_setup
23
File "/home/ubuntu/www/production.cartodb.com/releases/20160928141817/app/models/user.rb", line 1404 in setup_user
24
File "/home/ubuntu/www/production.cartodb.com/releases/20160928141817/app/models/user.rb", line 248 in after_create
+ 17 non-project frames
42
File "/home/ubuntu/www/production.cartodb.com/releases/20160928141817/app/models/carto/user_creation.rb", line 238 in save_user
+ 51 non-project frames
94
File "/home/ubuntu/www/production.cartodb.com/releases/20160928141817/lib/resque/user_jobs.rb", line 54 in perform
+ 26 non-project frames

Trace:
PG::Error: ERROR: duplicate key value violates unique constraint "pg_proc_proname_args_nsp_index"
DETAIL: Key (proname, proargtypes, pronamespace)=(_cdb_userquotainbytes, , 2200) already exists.
CONTEXT: SQL statement "CREATE OR REPLACE FUNCTION "public"._CDB_UserQuotaInBytes() RETURNS int8 AS $X$ SELECT 524288000::int8 $X$ LANGUAGE sql IMMUTABLE"
PL/pgSQL function cdb_setuserquotainbytes(text,bigint) line 12 at EXECUTE

+ 18 non-project frames
19
File "/home/ubuntu/www/production.cartodb.com/releases/20161006160014/app/models/user/db_service.rb", line 228 in block in rebuild_quota_trigger_with_database
+ 6 non-project frames
26
File "/home/ubuntu/www/production.cartodb.com/releases/20161006160014/app/models/user/db_service.rb", line 218 in rebuild_quota_trigger_with_database
27
File "/home/ubuntu/www/production.cartodb.com/releases/20161006160014/app/models/user/db_service.rb", line 209 in block in rebuild_quota_trigger
28
File "/home/ubuntu/www/production.cartodb.com/releases/20161006160014/app/models/user.rb", line 616 in in_database
29
File "/home/ubuntu/www/production.cartodb.com/releases/20161006160014/app/models/user/db_service.rb", line 208 in rebuild_quota_trigger
30
File "/home/ubuntu/www/production.cartodb.com/releases/20161006160014/app/models/user/db_service.rb", line 204 in load_cartodb_functions
31
File "/home/ubuntu/www/production.cartodb.com/releases/20161006160014/app/models/user/db_service.rb", line 1023 in create_own_schema
32
File "/home/ubuntu/www/production.cartodb.com/releases/20161006160014/app/models/user/db_service.rb", line 118 in new_organization_user_main_db_setup
33
File "/home/ubuntu/www/production.cartodb.com/releases/20161006160014/app/models/user.rb", line 1404 in setup_user
34
File "/home/ubuntu/www/production.cartodb.com/releases/20161006160014/app/models/user.rb", line 248 in after_create
+ 17 non-project frames
52
File "/home/ubuntu/www/production.cartodb.com/releases/20161006160014/app/models/carto/user_creation.rb", line 238 in save_user
+ 51 non-project frames
104
File "/home/ubuntu/www/production.cartodb.com/releases/20161006160014/lib/resque/user_jobs.rb", line 54 in perform

Trace:
    #<Sequel::DatabaseError: PG::Error: ERROR: duplicate key value violates unique constraint "cdb_conf_pkey"
DETAIL: Key (key)=(geocoder_server_config) already exists.
CONTEXT: SQL statement "INSERT INTO cartodb.CDB_CONF (KEY, VALUE) VALUES ($1, $2);"
PL/pgSQL function cdb_conf_setconf(text,json) line 4 at EXECUTE

Consider using resque-throttle, at least for Route64 rate limit.
Related: CartoDB/cartodb/issues/9791
cc @CartoDB/builder-backend @xavijam @jsanz

Closing automatically because of inactivity. If anybody considers that this still important, please reopen and it'll be prioritized.


Fix tuple number of fields warning

┌ Warning: Type does not have a definite number of fields
│   T = Tuple
└ @ Enzyme ~/.julia/packages/GPUCompiler/U36Ed/src/utils.jl:59


[dashboard] should be exposed via ingress

When running microk8s on the server, rather than doing port forwarding it should be possible to access the dashboard via ingress (similar to kubeflow dashboard)

Thank you for this request, it is brought up frequently. We need to address the need for easy access to the dashboard in a secure way. Until we do so, to access the dashboard have a look at the MicroK8s docs [1] and the dashboard upstream wiki [2]
[1] https://microk8s.io/docs/addon-dashboard
[2] https://github.com/kubernetes/dashboard/blob/master/docs/user/accessing-dashboard/1.7.x-and-above.md

So it's 2020 and this still hasn't been solved yet? Great go Kubernetes...

Enable the ingress addon:
microk8s enable ingress
and create an ingress ressource:
`
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
annotations:
kubernetes.io/ingress.class: nginx
nginx.ingress.kubernetes.io/rewrite-target: /$1
nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
name: dashboard
namespace: kube-system
spec:
rules:

http:
paths:

path: "/dashboard/?(.*)"
pathType: Prefix
backend:
service:
name: kubernetes-dashboard
port:
number: 443
`

Now you can access the dashboard with http://<Microk8s-IP>/dashboard/

Enable the ingress addon:
microk8s enable ingress
and create an ingress ressource:
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/rewrite-target: /$1
    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
  name: dashboard
  namespace: kube-system
spec:
  rules:
  - http:
      paths:
      - path: "/dashboard/?(.*)"
        pathType: Prefix
        backend:
          service:
            name: kubernetes-dashboard
            port:
              number: 443

Now you can access the dashboard with http://<Microk8s-IP>/dashboard/

Following these instructions I can access http:///dashboard/ but the page doesn't load correctly because the assets (styling, js, images) cannot be resolved correctly (404).

Manually appending /dashboard/ to the asset path fixes this issue. Any workaround?

This works for me (microk8s 1.19):
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: dashboard
  namespace: kube-system
  annotations:
    # use the shared ingress-nginx
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
    nginx.ingress.kubernetes.io/rewrite-target: /$2
    nginx.ingress.kubernetes.io/configuration-snippet: |
      rewrite ^(/dashboard)$ $1/ redirect;
spec:
  # https://kubernetes.io/docs/concepts/services-networking/ingress/
  # https://kubernetes.github.io/ingress-nginx/user-guide/tls/
  rules:
  - http:
      paths:
      - path: /dashboard(/|$)(.*)
        pathType: ImplementationSpecific
        backend:
          service:
            name: kubernetes-dashboard
            port:
              number: 443

Thanks Rom888, works for me too. Other than in my microk8s I need to use Ingress class: public
I1225 18:15:43.940765       6 flags.go:205] Watching for Ingress class: public
W1225 18:15:43.940833       6 flags.go:208] Only Ingresses with class "public" will be processed by this Ingress controller

Stop working after upgrading to 1.20
Empty ADDRESS:
kubectl get ing -n kube-system
NAME        CLASS    HOSTS   ADDRESS   PORTS   AGE
dashboard   <none>   *                 80      27m

@wuzhuoqing where should it be specified: "Ingress class: public"?

Stop working after upgrading to 1.20
Empty ADDRESS:
kubectl get ing -n kube-system
NAME        CLASS    HOSTS   ADDRESS   PORTS   AGE
dashboard   <none>   *                 80      27m

@wuzhuoqing where should it be specified: "Ingress class: public"?

This isn't working in my 1.20.2 version:
root@mkube1:~# cat ingress-dashboard.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: dashboard
  namespace: ingress
  annotations:
    # use the shared ingress-nginx
    kubernetes.io/ingress.class: public
    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
    nginx.ingress.kubernetes.io/rewrite-target: /$2
    nginx.ingress.kubernetes.io/configuration-snippet: |
      rewrite ^(/dashboard)$ $1/ redirect;
spec:
  # https://kubernetes.io/docs/concepts/services-networking/ingress/
  # https://kubernetes.github.io/ingress-nginx/user-guide/tls/
  rules:
  - http:
      paths:
      - path: /dashboard(/|$)(.*)
        pathType: ImplementationSpecific
        backend:
          service:
            name: kubernetes-dashboard
            port:
              number: 443

root@mkube1:~# microk8s kubectl apply -f ingress-dashboard.yaml
ingress.networking.k8s.io/dashboard created
root@mkube1:~# microk8s kubectl get ing -A
NAMESPACE     NAME        CLASS    HOSTS   ADDRESS   PORTS   AGE
kube-system   dashboard   <none>   *                 80      11s

Last lines of the ingress container logs:
I0225 21:04:04.660923       6 event.go:278] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"kube-system", Name:"dashboard", UID:"6a654f27-e98d-4c64-87be-03bbdf621ee5", APIVersion:"networking.k8s.io/v1beta1", ResourceVersion:"8583555", FieldPath:""}): type: 'Normal' reason: 'CREATE' Ingress kube-system/dashboard
I0225 21:04:04.661260       6 controller.go:141] Configuration changes detected, backend reload required.
I0225 21:04:04.745626       6 controller.go:157] Backend successfully reloaded.
I0225 21:04:28.628083       6 status.go:275] updating Ingress kube-system/dashboard status from [] to [{<IP_ADDRESS> }]
I0225 21:04:28.641134       6 event.go:278] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"kube-system", Name:"dashboard", UID:"6a654f27-e98d-4c64-87be-03bbdf621ee5", APIVersion:"networking.k8s.io/v1beta1", ResourceVersion:"8583595", FieldPath:""}): type: 'Normal' reason: 'UPDATE' Ingress kube-system/dashboard

What am I doing wrong here?

This isn't working in my 1.20.2 version:
root@mkube1:~# cat ingress-dashboard.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: dashboard
  namespace: ingress
  annotations:
    # use the shared ingress-nginx
    kubernetes.io/ingress.class: public
    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
    nginx.ingress.kubernetes.io/rewrite-target: /$2
    nginx.ingress.kubernetes.io/configuration-snippet: |
      rewrite ^(/dashboard)$ $1/ redirect;
spec:
  # https://kubernetes.io/docs/concepts/services-networking/ingress/
  # https://kubernetes.github.io/ingress-nginx/user-guide/tls/
  rules:
  - http:
      paths:
      - path: /dashboard(/|$)(.*)
        pathType: ImplementationSpecific
        backend:
          service:
            name: kubernetes-dashboard
            port:
              number: 443

root@mkube1:~# microk8s kubectl apply -f ingress-dashboard.yaml
ingress.networking.k8s.io/dashboard created
root@mkube1:~# microk8s kubectl get ing -A
NAMESPACE     NAME        CLASS    HOSTS   ADDRESS   PORTS   AGE
kube-system   dashboard   <none>   *                 80      11s

Last lines of the ingress container logs:
I0225 21:04:04.660923       6 event.go:278] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"kube-system", Name:"dashboard", UID:"6a654f27-e98d-4c64-87be-03bbdf621ee5", APIVersion:"networking.k8s.io/v1beta1", ResourceVersion:"8583555", FieldPath:""}): type: 'Normal' reason: 'CREATE' Ingress kube-system/dashboard
I0225 21:04:04.661260       6 controller.go:141] Configuration changes detected, backend reload required.
I0225 21:04:04.745626       6 controller.go:157] Backend successfully reloaded.
I0225 21:04:28.628083       6 status.go:275] updating Ingress kube-system/dashboard status from [] to [{<IP_ADDRESS> }]
I0225 21:04:28.641134       6 event.go:278] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"kube-system", Name:"dashboard", UID:"6a654f27-e98d-4c64-87be-03bbdf621ee5", APIVersion:"networking.k8s.io/v1beta1", ResourceVersion:"8583595", FieldPath:""}): type: 'Normal' reason: 'UPDATE' Ingress kube-system/dashboard

Browser gets nothing by Connection Refused errors.
What am I doing wrong here?

check your TCP port.  You appear to have an ingress listening on port 80 but you have HTTPS setup for your listener.

kubernetes.io/ingress.class: nginx change to public. @Rom888

Hi there,
thanks for posting the ingress configuration file.
I followed, however on WSL2 (windows 10). It does looks okay:
$ microk8s kubectl get ingress -n kube-system NAME        CLASS    HOSTS   ADDRESS     PORTS   AGE dashboard   <none>   *       <IP_ADDRESS>   80      53s
However, neither "https://<IP_ADDRESS>/dashboard" nor "http://<IP_ADDRESS>/dashboard" work. ===> <IP_ADDRESS> refused to connect.
What did I miss? Is this WSL2 thing?
I would really appreciate your help.
many thanks!!!

@jlettman  I see that you already have the fix for this issue . When are you going to submit it to upstream?

When are you going to submit it to upstream?

@yanivpaz It's submitted for microk8s in PR #2478. I believe that is still under review.

@Fischlein18  you can try as WA for WSL2:
 microk8s kubectl delete svc kubernetes-dashboard -n kube-system
 microk8s kubectl expose deployment kubernetes-dashboard -n kube-system --type=LoadBalancer --port 8443 --name=kubernetes-dashboard
nodePort=`microk8s kubectl get svc kubernetes-dashboard -n kube-system -o=jsonpath='{.spec.ports[].nodePort}'`
echo https://localhost:$nodePort

use the URL above to access the dashboard

option 3

Define the ingress as mentioned here
Run in WSL2 :

sudo apt install openssh-server
sudo systemctl start sshd
sudo ssh -L <IP_ADDRESS>:443:<IP_ADDRESS>:443 username@hostname

add to windows host file
<IP_ADDRESS>   kubernetes-dashboard.<IP_ADDRESS>.nip.io

open https://kubernetes-dashboard.<IP_ADDRESS>.nip.io from the browser

@yanivpaz Could you explain what is the reasoning for running sudo ssh -L <IP_ADDRESS>:443:<IP_ADDRESS>:443 username@hostname ?

I got it working with microk8s version v1.24.0-2+59bbb3530b6769 and Ubuntu-Server 22.04 LTS.
My ingress-dashboard.yaml looks like this.
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: dashboard
  namespace: kube-system
  annotations:
    # use the shared ingress-nginx
    kubernetes.io/ingress.class: public
    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
    nginx.ingress.kubernetes.io/rewrite-target: /$2
    nginx.ingress.kubernetes.io/configuration-snippet: |
      rewrite ^(/dashboard)$ $1/ redirect;
spec:
  # https://kubernetes.io/docs/concepts/services-networking/ingress/
  # https://kubernetes.github.io/ingress-nginx/user-guide/tls/
  rules:
  - http:
      paths:
      - path: /dashboard(/|$)(.*)
        pathType: ImplementationSpecific
        backend:
          service:
            name: kubernetes-dashboard
            port:
              number: 443

Simpler solution
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: dashboard.loc
  namespace: kube-system
  annotations:
    kubernetes.io/ingress.class: public
    nginx.ingress.kubernetes.io/rewrite-target: /
    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
spec:
  rules:
  - host: dashboard.loc
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: kubernetes-dashboard
            port:
              number: 443


Seems like a bug in jsii-diff

- CLASS @aws-cdk/aws-iam.CfnAccessKey initializer <initializer> argument props, takes @aws-cdk/aws-iam.CfnAccessKeyProps: none of number | @aws-cdk/cdk.Token are assignable to number | @aws-cdk/cdk.Token, number | @aws-cdk/cdk.Token is not assignable to number, some of number | @aws-cdk/cdk.Token are not assignable to @aws-cdk/cdk.Token, number is not assignable to @aws-cdk/cdk.Token

@rix0rrr can you look into this? I am seeing a lot of them

Was because jsii-diff wasn't updated to the latest version.


Translate help/faq/traffic-management into Chinese

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: rootsongjc
If they are not already assigned, you can assign the PR to them by writing /assign @rootsongjc in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content_zh/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @DavadDi. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

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

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rootsongjc
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content_zh/OWNERS [rootsongjc]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


node test timeout: "Client malformed response handling.should get an INTERNAL status with a server stream call"

https://grpc-testing.appspot.com/job/gRPC_master/15404/config=dbg,language=node,platform=macos/testReport/junit/(root)/Client malformed response handling/should_get_an_INTERNAL_status_with_a_server_stream_call/

https://grpc-testing.appspot.com/job/gRPC_master/15402/config=tsan,language=node,platform=linux/testReport/junit/(root)/Client malformed response handling/should_get_an_INTERNAL_status_with_a_server_stream_call/

and possibly related: https://grpc-testing.appspot.com/job/gRPC_master/15402/config=tsan,language=node,platform=linux/testReport/junit/(root)/Client malformed response handling/should_get_an_INTERNAL_status_with_a_bidi_stream_call/

This seems to have been fixed by #5610.


squid:S2325 - "private" methods that don't access instance data should be "static"

This pull request is focused on resolving occurrences of Sonar rule squid:S2325 - "private" methods that don't access instance data should be "static".
You can find more information about the issue here:
https://dev.eclipse.org/sonar/coding_rules#q=squid%3AS2325
Please let me know if you have any questions.
George Kankava

We'll consider merging this

Closing due to conflicts - please reopen against HEAD


cd.. produces a blank white screen

[X] I am on the latest Hyper.app version
[X] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: MacOS 10.12.2
Hyper.app version: <IP_ADDRESS>3
Link of a Gist with the contents of your .hyper.js:
Relevent information from devtools (CMD+SHIFT+I on Mac OS, CTRL+SHIFT+I elsewhere):

Uncaught NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
Uncaught TypeError: Failed to execute 'removeChild' on 'Node': parameter 1 is not of type 'Node'.
Uncaught TypeError: Failed to execute 'removeChild' on 'Node': parameter 1 is not of type 'Node'.
Unknown OSC code: "1"
Uncaught TypeError: Failed to execute 'removeChild' on 'Node': parameter 1 is not of type 'Node'.
Unknown OSC code: "133"
Unknown OSC code: "1337"
Uncaught TypeError: Failed to execute 'removeChild' on 'Node': parameter 1 is not of type 'Node'.
Unknown OSC code: "133"
Uncaught TypeError: Failed to execute 'removeChild' on 'Node': parameter 1 is not of type 'Node'.
Unknown OSC code: "133"
Uncaught TypeError: Failed to execute 'removeChild' on 'Node': parameter 1 is not of type 'Node'.
Unknown OSC code: "133"
Uncaught TypeError: Failed to execute 'removeChild' on 'Node': parameter 1 is not of type 'Node'.

The issue is reproducible in vanilla Hyper.app: Yes

Issue
Open Hyper.app and type the following:
cd..

You will get a blank white screen.

Oh wow... Can reproduce.

I recorded the symptom here: http://recordit.co/z5IgNy5KgR

I just noticed that is actually no related with the "cd", it seems to be related with two dots ".." after any character or word.
Example:
...
d..
bagre..

It happens the same with cd ..ll

Got the same issue when typed дд instead of ll (in Russian layout). Exceptions are similar

URL handling has been vastly improved on 1.0.1! Thanks for the reports 🙏


Compile openh264_release failed

I used Crossbridge to compile openh264_release on Mac OS
PATH=~/Projects/Crossbridge/sdk/usr/bin:$PATH make openh264_release FLASCC=~/Projects/Crossbridge/sdk
,these is the error:
-> Compile the C into abc - RELEASE "/Users/tsubasa/Projects/Crossbridge/sdk/usr/bin/g++" -DBOOST_ALL_NO_LIB -D__STDC_CONSTANT_MACROS -D__AVM2 -c -pthread -O4 -Wall ../common/boost_atomic/libs/atomic/src/lockpool.cpp -o lockpool.abc -I../common/boost_atomic/ ../common/boost_atomic/libs/atomic/src/lockpool.cpp:83: warning: missing braces around initializer for 'boost::atomics::detail::<unnamed>::padded_lock' ../common/boost_atomic/libs/atomic/src/lockpool.cpp:83: warning: missing braces around initializer for 'boost::atomics::detail::<unnamed>::padding<60u>' ../common/boost_atomic/libs/atomic/src/lockpool.cpp:83: warning: missing braces around initializer for 'char [60]' "/Users/tsubasa/Projects/Crossbridge/sdk/usr/bin/g++" -DBOOST_ALL_NO_LIB -D__STDC_CONSTANT_MACROS -D__AVM2 -c -pthread -O4 -Wall ../common/FW_exception.cpp -o fw_exception.abc "/Users/tsubasa/Projects/Crossbridge/sdk/usr/bin/g++" -DBOOST_ALL_NO_LIB -D__STDC_CONSTANT_MACROS -D__AVM2 -c -pthread -O4 -Wall ../common/FW_ffmpeg_IO.cpp -o fw_ffmpeg_IO.abc -I./ffmpeg_mp4_openh264_aac/include/ ../common/FW_ffmpeg_IO.cpp: In function 'int64_t seekFunction(void*, int64_t, int)': ../common/FW_ffmpeg_IO.cpp:39: warning: format '%d' expects type 'int', but argument 3 has type 'int64_t' "/Users/tsubasa/Projects/Crossbridge/sdk/usr/bin/g++" -DBOOST_ALL_NO_LIB -D__STDC_CONSTANT_MACROS -D__AVM2 -c -pthread -O4 -Wall ../common/FW_ffmpeg_encode.cpp -o fw_ffmpeg_encode_release.abc -I../common/boost_atomic/ -I./ffmpeg_mp4_openh264_aac/include/ ../common/FW_ffmpeg_encode.cpp: In member function 'void FW_ffmpeg_encode::write_audio_frame(AVFormatContext*, const uint8_t*, int, AVStream*)': ../common/FW_ffmpeg_encode.cpp:270: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:286: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:331: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:337: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:343: warning: comparison between signed and unsigned integer expressions ../common/FW_ffmpeg_encode.cpp:350: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:353: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:356: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:377: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:382: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:394: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp: In member function 'void FW_ffmpeg_encode::write_video_frame(AVFormatContext*, unsigned char*, AVStream*)': ../common/FW_ffmpeg_encode.cpp:494: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp: In member function 'void FW_ffmpeg_encode::encode_it()': ../common/FW_ffmpeg_encode.cpp:641: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:646: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:653: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:666: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:678: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp: In member function 'int FW_ffmpeg_encode::finishInit()': ../common/FW_ffmpeg_encode.cpp:887: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:930: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp: In member function 'void FW_ffmpeg_encode::configureRAMAdjuster(double, double)': ../common/FW_ffmpeg_encode.cpp:936: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp: In member function 'int FW_ffmpeg_encode::ffmpeg_init(unsigned char*, unsigned char*, unsigned char*, int, int, int, int, int, int, int, int, int, int, long unsigned int, int, int)': ../common/FW_ffmpeg_encode.cpp:960: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:989: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp: In member function 'void FW_ffmpeg_encode::ffmpeg_finish()': ../common/FW_ffmpeg_encode.cpp:1039: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp: In member function 'std::stringstream* FW_ffmpeg_encode::ffmpeg_getStream()': ../common/FW_ffmpeg_encode.cpp:1049: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp: In member function 'bool FW_ffmpeg_encode::flush_intermediate_frames()': ../common/FW_ffmpeg_encode.cpp:1137: warning: comparison between signed and unsigned integer expressions ../common/FW_ffmpeg_encode.cpp:1143: warning: comparison between signed and unsigned integer expressions ../common/FW_ffmpeg_encode.cpp: In member function 'int FW_ffmpeg_encode::ffmpeg_addVideoData(unsigned char*, int)': ../common/FW_ffmpeg_encode.cpp:1191: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:1205: warning: comparison between signed and unsigned integer expressions ../common/FW_ffmpeg_encode.cpp:1207: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:1210: warning: comparison between signed and unsigned integer expressions ../common/FW_ffmpeg_encode.cpp:1211: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:1214: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:1230: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp: In member function 'bool FW_ffmpeg_encode::try_flushAndThread()': ../common/FW_ffmpeg_encode.cpp:1261: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:1276: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp: In static member function 'static void* FW_ffmpeg_encode::runencoderthread(void*)': ../common/FW_ffmpeg_encode.cpp:1298: warning: no return statement in function returning non-void ../common/FW_ffmpeg_encode.cpp: In static member function 'static void* FW_ffmpeg_encode::runInitThread(void*)': ../common/FW_ffmpeg_encode.cpp:1310: warning: no return statement in function returning non-void ../common/FW_ffmpeg_encode.cpp: In member function 'void FW_ffmpeg_encode::ffmpeg_addAudioData(unsigned char*, int)': ../common/FW_ffmpeg_encode.cpp:1355: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:1366: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:1382: warning: deprecated conversion from string constant to 'char*' ../common/FW_ffmpeg_encode.cpp:1316: warning: unused variable 'millis2' ../common/FW_ffmpeg_encode.cpp: In static member function 'static void* FW_ffmpeg_encode::runInitThread(void*)': ../common/FW_ffmpeg_encode.cpp:1310: warning: control reaches end of non-void function ../common/FW_ffmpeg_encode.cpp: In static member function 'static void* FW_ffmpeg_encode::runencoderthread(void*)': ../common/FW_ffmpeg_encode.cpp:1298: warning: control reaches end of non-void function ../common/FW_ffmpeg_encode.cpp: In member function 'int FW_ffmpeg_encode::finishInit()': ../common/FW_ffmpeg_encode.cpp:931: warning: control reaches end of non-void function "/Users/tsubasa/Projects/Crossbridge/sdk/usr/bin/g++" -DBOOST_ALL_NO_LIB -D__STDC_CONSTANT_MACROS -D__AVM2 -c -pthread -O4 -Wall ../common/FW_ffmpeg_decode.cpp -o fw_ffmpeg_decode_release.abc -I../common/boost_atomic/ -I./ffmpeg_mp4_openh264_aac/include/ ../common/FW_ffmpeg_decode.cpp: In static member function 'static void* FW_ffmpeg_decode::rundecoderthread(void*)': ../common/FW_ffmpeg_decode.cpp:58: warning: no return statement in function returning non-void ../common/FW_ffmpeg_decode.cpp: In member function 'int FW_ffmpeg_decode::get_format_from_sample_fmt(const char**, AVSampleFormat)': ../common/FW_ffmpeg_decode.cpp:184: warning: comparison between signed and unsigned integer expressions ../common/FW_ffmpeg_decode.cpp: In member function 'int FW_ffmpeg_decode::bufferFrames()': ../common/FW_ffmpeg_decode.cpp:491: warning: control reaches end of non-void function ../common/FW_ffmpeg_decode.cpp: In static member function 'static void* FW_ffmpeg_decode::rundecoderthread(void*)': ../common/FW_ffmpeg_decode.cpp:58: warning: control reaches end of non-void function "/Users/tsubasa/Projects/Crossbridge/sdk/usr/bin/g++" -DBOOST_ALL_NO_LIB -D__STDC_CONSTANT_MACROS -D__AVM2 -c -pthread -O4 -Wall FW_wrapper.cpp -o fw_ffmpeg_encode_wrapper_release.abc -I../common/boost_atomic/ -I./ffmpeg_mp4_openh264_aac/include/ make link_openh264_release make[1]: Entering directory '/Volumes/C/Users/Administrator/Documents/Project/FlashyWrappers/FlasCC' -> Compiling openh264 encoder SWC "/Users/tsubasa/Projects/Crossbridge/sdk/usr/bin/g++" -D__STDC_CONSTANT_MACROS -D__AVM2 -O4 -Wall -pthread -O4 -Wall VFS.abc lockpool.abc fw_exception.abc fw_ffmpeg_encode_wrapper_release.abc fw_ffmpeg_encode_release.abc fw_ffmpeg_decode_release.abc fw_ffmpeg_IO.abc -emit-swc=com.fw_flascc -swf-version=17 -o fw_ffmpeg_encode_mp4_release.swc -L./ffmpeg_mp4_openh264_aac/lib/ -lswscale -lavformat -lavcodec -lavutil -lopenh264 -liconv /Users/tsubasa/Projects/Crossbridge/sdk/usr/bin/ld: warning: SWF version must be at least 18 to use pthreads, your SWF version will be forced to 18. /Users/tsubasa/Projects/Crossbridge/sdk/usr/bin/ld: error: cannot find -lopenh264 ./ffmpeg_mp4_openh264_aac/lib//libavcodec.a: error: undefined reference to '_WelsDestroySVCEncoder' ./ffmpeg_mp4_openh264_aac/lib//libavcodec.a: error: undefined reference to '_WelsGetCodecVersion' ./ffmpeg_mp4_openh264_aac/lib//libavcodec.a: error: undefined reference to '_WelsCreateSVCEncoder' collect2: ld returned 1 exit status Makefile:115: recipe for target 'link_openh264_release' failed make[1]: *** [link_openh264_release] Error 1 make[1]: Leaving directory '/Volumes/C/Users/Administrator/Documents/Project/FlashyWrappers/FlasCC' Makefile:18: recipe for target 'openh264_release' failed make: *** [openh264_release] Error 2

This explains it:
error: cannot find -lopenh264
I don't remember the details, but you must install libopenh264 (as part of ffmpeg I believe, similar to how they've got x264). If you'll be still interested in this I can take a look at more details when I'm near my old laptop.


fix: Ensure there is a visible button in the Existing photos screen

Hi everyone,
In the "Existing photos" screen, the back button is invisible (black on black).
This PR ensure we force a white color

Thanks @g123k @monsieurtanuki 👍


After the master branch of Tarsramework is compiled, if I need to upgrade the tarsnode, will I just replace the tarsnode execution file or allthe tarsnodes be replaced?

E：The result of tarsnode compilation is a binary file, just replace the tarsnode executable file.
C：tarsnode编译的结果就是一个bin，只替换这个tarsnode的执行文件即可。

After restarting the service, tarsnode restarted.

But the management page shows off, and there is no log.

E：Check the operation and maintenance management, node management, and check whether the node is normal. If inactive is displayed（see note Figure 3）, the node is not connected to the frame.
C：查看运维管理，节点管理，检查节点是否正常。如果显示inactive（见备注图三），说明节点没有连接到框架。

E：Check whether the node configuration file exists (see note Figure).
C：检查节点配置文件是否存在（见备注图）。


feat(backend): use fewer histogram buckets for request latency

Default buckets cover up to 10 seconds, which is unnecessarily wide.
Checking our installation, highest p99.9 among all endpoints is 0.34s (somewhat unexpectedly, the notFound handler).

Thanks!


Grammar pass on readme.md

I removed all the unnecessary new lines, which means each paragraph is on a single line. Hope you don't mind.

Thanks Trevor, much appreciated!


corrected pom.xml to generate sources and javadoc, completed javadoc

according to https://github.com/xspec/xspec/issues/563
This commit has been used to deploy to sonatype.
Merge this one to master and modify /project/version

Travis/AppVeyor failure was detected by #296. .class file needs to be recompiled.
For fixing it, I committed the recompiled XSLTCoverageTraceListener.class file directly to this PR repository.


Tip: "Type f to move your cursor to the filter box " incorrect, shortcut does not work

It looks like the shortcut documented by the Tip starting "Type f to move your cursor to the filter box" does not work.
Per this page: https://docs.microsoft.com/en-us/azure/devops/boards/boards/kanban-board-keyboard-shortcuts?view=azure-devops
it should be "Ctrl+Shift+f"
Also, the text "To move the focus up or down within a column, enter the up/down arrows. " appears to be incorrect. CTRL +Shift +f places the cursor in the filter text input. (You can press Tab to the move the focus to the filter drop downs)

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

ID: b5017884-bcc0-3fa7-6bfd-73bb04ab7524
Version Independent ID: cadea453-739a-6498-268a-ad3391a4f65b
Content: Filter your Kanban board - Azure Boards
Content Source: docs/boards/boards/filter-kanban-board.md
Product: devops
Technology: devops-agile
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@SamHasler  Thank you for the feedback.
The documentation has been updated and is pending review.


Add credential provider for JDBC connectors

This enables the JDBC connector to pass credentials as a seperate file
or as a part of the existing connector properties

Thanks for doing this! Looks nice.

@kokosing , @electrum Thanks for your insights. Have applied the above comments.

Some context -- https://cwiki.apache.org/confluence/display/Hive/JdbcStorageHandler
Securing Password

Some context -- https://cwiki.apache.org/confluence/display/Hive/JdbcStorageHandler

Securing Password
In most cases, we don’t want to store jdbc password in clear text in table property "hive.sql.dbcp.password". Instead, user can store password in a Java keystore file on HDFS using the following command:
hadoop credential create host1.password -provider jceks://hdfs/user/foo/test.jceks -v passwd1
hadoop credential create host2.password -provider jceks://hdfs/user/foo/test.jceks -v passwd2

This will create a keystore file located on hdfs://user/foo/test.jceks which contains two keys: host1.password and host2.password. When creating table in Hive, you will need to specify “hive.sql.dbcp.password.keystore” and “hive.sql.dbcp.password.key” instead of “hive.sql.dbcp.password” in create table statement
...

Some thought to some context:
As it was pointed by @Praveen2112 , using hadoop credential brings additional hadoop (possibly non trivial) dependencies into jdbc connector. It would be nice to have a way to wrap hadoop credential CredentialProvider as some kind of plugin (plugin for plugin?).

Is there an HTTP interface for HDFS that could be used in this case?

@dain do you mean webhdfs?

@findepi I mean is there an interface to HDFS via a standard HTTP client that can be used in cases like this?  Specifically, cases where we only need to download a rare single file.

@dain webhdfs fits your description, see https://hadoop.apache.org/docs/r1.0.4/webhdfs.html#FsURIvsHTTP_URL
of course, authentication might be challenging, e.g. when HDFS is kerberized.

@findepi If we use the airlift http client kerberos support is built in.

@dain @findepi Isn't java keystores not good enough here? I don't think there is a reason to go with hadoop credential provider. Is it all about storing credentials in distributed file system?

Merged, thanks!

https://prestosql.io/docs/current/connector/mysql.html does not mention how to use this? Also will the credentials still be in plaintext in the other file?


Change database engine

Since sqlite3 package devs arent going to fix the issue with their package and node 10.x i want to know if is there any option/alternative database to use with the bot. H2 or other text-based can be good, or the old mysql/mariadb.
Or even change the package from sqlite3 to sqlite because in that the issue was resolved.
Thanks in advance!

Try the dev branch!
That uses mongodb!
In the future everyone is gonna move to that so.

Sadly mongodb stopped being updated for raspbian (due to this OS being an ARM32 one, and raspberry team arent willing to port it to 64).
The version on apt is 2.4 and the most recent i found to install on internet was 3.2. So, other alternative actively developed for raspbian would be appreciated, because i know more people would use a pi as a "bot box" (to self-host discord bots cheaply).

Mhm.. what about a free cloud solution? That you use a mongodb that’s in the cloud?
I assume that the developers don’t support your architecture due to age maybe? I’ve Never heard about the ARM32, so I assume it’s abit aged.
I don’t know any cloud service that fast what offers a mongodb. But I’m pretty sure there is one that’s free and workable :-)
Side note: users can always host for free in heroku with my instruction. For enough hours you would need a cc for activation.

The question of ARM32 is the raspberry developers aren't willing to build raspbian into 64 because "switching to 64-bit brings almost nothing, not much more speed for example" (aka laziness?).
In fact the processor of raspberry is an ARM64, only the OS is compiled for 32.
Anyway, for a self-hosted home project i didnt see any advantages to using an external database (that's why i begin to self-host in first place: to run from third party hosting and to give more control over the bot).
Also i fear if i got an internet outage cuttting connection between the pi and DB it could corrupt it somehow.

The first part of your message is something we can't do, if enough users would suggest the devs to make the move, they probably would spent their time to it.
If the OS is compiled for 32, maybe you could use debian jessie (8), that one runs on quite low specs (few mb's only!)
The advantages you get is that you host completley free, and it's on a system that has probably more memory, cpu en bandwith.
If you have maybe another device that could support a mongodb, you could connect to that locally.
Also, if the internet is out, then i don't think your bot can recieve a input (like adding a rss-feed) in the first place.

Thanks @synzen , will test this night!

There's now a version of the next major release that does not require mongo, please see https://github.com/synzen/Discord.RSS/wiki/Setup and follow the directions for a databaseless configuration.

@synzen should i clone the master or dev branch?

The dev branch

Thank you! Will close the issue as soon i can test this on my pi.
And just FYI: seems like sqlite3 guys just updated it to be supported by node 10.

3.0.0 has been marked and the SQL version is now unsupported - please use the newest version and report any problems in a new issue. Thanks.


TypeScript cannot auto-complete keyword extends

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.76.2
OS Version: macOS 13.1 (22C65)

Steps to Reproduce:

there is an interface A
want to create another interface B base on A
keyword extends not showing auto-complete

Thank you @a-tarasyuk!


Python client for Genie 3.0 Jobs API

Coverage remained the same at 88.896% when pulling 707ac310507e9c9af17e1b411b721df26bd43c7e on irontable:develop into d9634a48b0638bb8bfbb443b1448ac418986efe9 on Netflix:develop.

Part of #163

Coverage remained the same at 88.934% when pulling b9ef6a6f71a891079413cc01aa31b1d29424756e on irontable:develop into 909691ebb133caafb7dae7c871a075bad22d883d on Netflix:develop.

Coverage remained the same at 88.934% when pulling b9ef6a6f71a891079413cc01aa31b1d29424756e on irontable:develop into 909691ebb133caafb7dae7c871a075bad22d883d on Netflix:develop.

Coverage remained the same at 88.934% when pulling b9ef6a6f71a891079413cc01aa31b1d29424756e on irontable:develop into 909691ebb133caafb7dae7c871a075bad22d883d on Netflix:develop.


[BUG] add friend color in chams-Wireframe?

Should this be a bug?
'_'

may be it can consider as a feature


Missing ComponentType in MethodInfo.getParameterTypeStrs()

public void method(@ParamAnnotation0 final List<String> annotatedValue0,
            @ParamAnnotation1 @ParamAnnotation2 final String annotatedValue1) {
    }

MethodInfo.getParameterTypeStrs() simply returns [List, String]. But annotatedValue0 is a List<String>.
This problem seems also exists in other types returned like FieldInfo#getTypeStr or MethodInfo.getReturnTypeStr ...

Parameter types are much harder to obtain from the classfile (the type parameters are stored in a different place from the types), and they are often not even present in the classfile (due to type erasure, or in earlier versions of the VM). But let me see what can be done for cases where the info does exist.

I am not an expert on JVM class format. I am not sure if you need this or not. But here is my two cents.
https://stackoverflow.com/questions/937933/where-are-generic-types-stored-in-java-class-files

Yes, correct, it's in the Signature attribute. But it's a bit more complicated for method parameters, I think. I'll look into it.

Fixed and released in version 2.8.2.


DIsable swiping next prev slide when swiper is zoomed

If swiper slide is zoomed, i need to disable prev next slide swiping, cuz thats unreal to use zoom. U try to zoom, but swiper go to next slide. How to disable swiping next prev when swiper is zooming?

Your issue is closed because it is not filled correctly. Before you open an issue please review the contributing guideline.
Please fill the issue template correctly and:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with isssue

It will save a lot of time for other contributors to check your issue and fix it.


Tracker aware interpreter

Proposed changes:

...

Status (please check what you already did):

[ ] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog

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


Issue while generating tweet

Error while generating a reply for this tweet: Rate limit reached for gpt-3.5-turbo in organization org-gkOpuNhdF16oQJPCM1VAsca4 on requests per min (RPM): Limit 3, Used 3, Requested 1. Please try again in 20s. Visit https://platform.openai.com/account/rate-limits to learn more. You can increase your rate limit by adding a payment method to your account at https://platform.openai.com/account/billing.

Hi @XaheerINC this is an error from OpenAI you have to increase to a higher tier to have more RPM. It is not an issue from XReplyGPT


[BUG] Specify cloudevents metadata

Expected Behavior
I expect that it's possible to specify the desired traceid and traceparent values, using the pulish_event method with data_content_type="application/cloudevents+json".
Actual Behavior
Some Dapr CloudEvent fields can be specify (ex. source and type) as expected from documentation. But other fields are ignored (ex. traceid, traceparent).
Steps to Reproduce the Problem
dapr version: dapr==1.12.1
The following code:
MY_DATA = {
    "source":"MY_SOURCE",
    "type":"MY_TYPE",
    "data": {
        "x": 1,
        "y": 2
    },
    "traceid":"00-20fb8e95782a3548a903dd43c83396b4-c39ddb6ef445b8e3-01",
    "traceparent":"00-20fb8e95782a3548a903dd43c83396b4-c39ddb6ef445b8e3-01",
    }

dapr_client.publish_event(
    pubsub_name=MY_PUBSUB_NAME,
    topic_name=MY_TOPIC_NAME,
    data=json.dumps(MY_DATA),
    data_content_type="application/cloudevents+json",
)

produces this message:
{
    "data": {
        "x": 1,
        "y": 2
    },
    "pubsubname": "kafka-pubsub",
    "source": "MY_SOURCE",
    "specversion": "1.0",
    "time": "2024-01-23T14:04:23Z",
    "topic": "test",
    "traceid": "00-d258f97bef8a57285dd19490337d4b35-a179d57fa4846794-01",
    "traceparent": "00-d258f97bef8a57285dd19490337d4b35-a179d57fa4846794-01",
    "tracestate": "",
    "type": "MY_TYPE"
}

instead of the desired traceid and traceparent value (00-20fb8e95782a3548a903dd43c83396b4-c39ddb6ef445b8e3-01).

Moving this to Dapr Runtime because this is not Python specific. It occurs at the runtime level.


feat(rust): improve ockam vault list to mark the default vault

Closes #6137
This commit will:

create the VaultListOutput struct in ockam_command/src/vault/list.rs to represent the output for vault list
implement output() for VaultListOutput to be called in build_list() for rendering
suffix the default vault with '(default)' on the ockam vault list command

Current behavior
ockam vault list doesn't mark the default vault

Proposed changes
mark the default vault in ockam vault list.
Tests:

First vault created set to default

2) Additional vaults created are not default

3) Changing default vault

Checks

[ ] All commits in this Pull Request are signed and Verified by Github.
[ ] All commits in this Pull Request follow the Ockam commit message convention.
[ ] There are no Merge commits in this Pull Request. Ockam repo maintains a linear commit history. We merge Pull Requests by rebasing them onto the develop branch. Rebasing to the latest develop branch and force pushing to your Pull Request branch is okay.
[ ] I have read and accept the Ockam Community Code of Conduct.
[ ] I have read and accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a separate Pull Request, this will mark the commit as verified.

@adrianbenavides Thanks for the review and letting me know how to run the bats test!  My local changes didn't appear in the tests until I did OCKAM=./target/debug/ockam like you said
I made some of the changes you recommended, plus some additional changes so that it's usable in the json output too.  I'm a bit unsure if it's the right way to go about it though, because I did v.config().clone() to get the config into VaultListOutput so it can be used in the json. Is this the right approach + ok to use clone here?

I made some of the changes you recommended, plus some additional changes so that it's usable in the json output too. I'm a bit unsure if it's the right way to go about it though, because I did v.config().clone() to get the config into VaultListOutput so it can be used in the json. Is this the right approach + ok to use clone here?

No problem with cloning in this case, as the VaultConfig only contains a bool 👍


MaxConcurrentConnections reached

It would be useful if the dashboard would report if the max number of connections is reached.  Currently it just shows as "loading...", whereas the http request is responding with "MaxConcurrentConnections reached: 5"
Mitchell

Does this work properly? If I hit refresh a fee times in the UI I reach the limit and it stays there

Does this work properly? If I hit refresh a few times in the UI I reach the limit and it stays there

@davidkarlsen Here's how I tested:

Open up the dashboard in a browser and verify that it behaves normally
Use curl to open a connection to a direct metrics stream
Repeat 2) until I get a 503.  This implies the metrics stream supports no more listeners.
Open the dashboard in a new tab and verify I see the new error messages.
Shut down all curls still open from 2).
Open dashboard in a new tab and verify that the metrics show up (and the error messages do not).

This sequence worked for me with master.
If you've got a specific set of steps for me to try, I'm happy to try to replicate.

Seems like I can refresh and it recovers on recent versions. Sorry for the noise. I'll be back if I can make it fail consistently.

No problem - I'm always happy to have confirmation that a new feature is being used and whether it works as I expected.

Closed due to inactivity

I still encounter "MaxConcurrentConnections reached: 5" even though I am using Hystrix 1.4.12. It works in the beginning but when I load the Hystrix Dashboard and refresh the browser window 4 times, it stops working wit the above mentioned message. The setup is using Spring Boot with the @EnableHystrix annotation.

I'm seeing similar issue as @draxly. com.netflix.hystrix:hystrix-metrics-event-stream:1.4.22
curl 5x curl http://localhost/app/hystrix.stream
stream is outputted
ctrl+C
on the 6th curl
{"timestamp":1460728335392,"status":503,"error":"Service Unavailable","message":"MaxConcurrentConnections reached: 5","path":"/app/hystrix.stream"}
It doesn't seem to be releasing the connections when they are closed

I just attempted to replicate this, but could not.  Here's what I did (from tip-of-master):

Run the hystrix-examples-webapp (../gradlew clean jettyRun from Hystrix/hystrix-examples-webapp)
Load the demo page to get commands executing (Visit http://localhost:8989/hystrix-examples-webapp/ in a browser)
In a single terminal window, get the metrics stream and close it repeatedly (I did it 10x).  This was a curl -v -G "http://localhost:8989/hystrix-examples-webapp/hystrix.stream" followed by a Ctrl+C.

Since this works, it looks to me like connections are getting cleaned up properly.  Can you see if there's anything materially different in your setup from the experiment above?

@mattrjacobs Thanks! I've managed to narrow the issue down to the web server now.

@andrewe123 Have you found out what it is? I'm facing the same issue.

@matheus208 it appeared to be a WebSphere bug, we switched to Tomcat and couldn't reproduce the issue.


ImportError: No module named tensorflow_probability

Hi, I run into a problem about some environmental problem ...
I could not run your demo either on Colab on my local pc. All of them reports ModuleNotFoundError with respect to 'tensorflow_probability'.
For Colab of shortest_path.ipynb, change the install setting to be install_graph_nets_library = "yes", it just reports error like:
ImportErrorTraceback (most recent call last)
<ipython-input-5-c414b43b0fe0> in <module>()
      8 import time
      9
---> 10 from graph_nets import graphs
     11 from graph_nets import utils_np
     12 from graph_nets import utils_tf

/usr/local/lib/python2.7/dist-packages/graph_nets/__init__.py in <module>()
     19 from __future__ import print_function
     20
---> 21 from graph_nets import blocks
     22 from graph_nets import graphs
     23 from graph_nets import modules

/usr/local/lib/python2.7/dist-packages/graph_nets/blocks.py in <module>()
     36 from graph_nets import graphs
     37 from graph_nets import utils_tf
---> 38 import sonnet as snt
     39 import tensorflow as tf
     40

/usr/local/lib/python2.7/dist-packages/sonnet/__init__.py in <module>()
     40 import semantic_version
     41
---> 42 from sonnet.python import custom_getters
     43 from sonnet.python.modules import experimental
     44 from sonnet.python.modules import nets

/usr/local/lib/python2.7/dist-packages/sonnet/python/custom_getters/__init__.py in <module>()
     19 from __future__ import print_function
     20
---> 21 from sonnet.python.custom_getters import bayes_by_backprop
     22 from sonnet.python.custom_getters.context import Context
     23 from sonnet.python.custom_getters.non_trainable import non_trainable

/usr/local/lib/python2.7/dist-packages/sonnet/python/custom_getters/bayes_by_backprop.py in <module>()
     92
     93 import tensorflow as tf
---> 94 import tensorflow_probability as tfp
     95
     96 _DEFAULT_SCALE_TRANSFORM = tf.nn.softplus

ImportError: No module named tensorflow_probability

Similar error is witnessed locally.
Thank you for you help!

Thanks for catching this! It looks like the version of sonnet changed right after we tested and released this, and there is apparently an upstream bug in either tensorflow or tensorflow_probability. In the meantime, try installing the previous version of sonnet:
pip install -U dm-sonnet==1.23

And that should work for now.

That works now. Thanks! : -)

That also solves the import error:
ModuleNotFoundError: No module named 'Graph'


how to specify regex endpoints?

I'm trying to configure an endpoint that handles requests matching a regex.
Is there a sample configuration using this feature?

Could you put an example of that you're looking for? To prepare a proper example :D?

thanks; I believe I found a way, perhaps you can confirm if this is correct.
If I understood correctly, gorilla is being used for routing, which already describes using parameters in the URLs (https://github.com/gorilla/mux#examples)
In my case, I wanted something like "/api/v1/customers/{any_customer_id}" to return the same json file.
Something like this did the trick
  {
    "request": {
      "method": "GET",
      "endpoint": "/api/v1/customers/{customer_id}"
    },
    "response": {
      "status": 200,
      "headers": {
        "Content-Type": "application/json"
      },
      "bodyFile": "samplecustomer.json"
    }
  }

According to gorilla:
They are defined using the format {name} or {name:pattern}. If a regular expression pattern is not defined, the matched variable will be anything until the next slash.

Yes, we're using gorilla mux for the regex, in the urls and the query params, for that reason you'll need to use his structure, in your case should be something like:
  {
    "request": {
      "method": "GET",
      "endpoint": "/api/v1/customers/{customer_id:[0-9]+}"
    },
    "response": {
      "status": 200,
      "headers": {
        "Content-Type": "application/json"
      },
      "bodyFile": "samplecustomer.json"
    }
  }

As you put, you need to declare a variable in the first step and then a pattern that is your regex. {name:pattern}.
For more information in the creation of the endpoints you could check the issue: https://github.com/friendsofgo/killgrave/issues/51 because for now the documentation is a little poor, but in a future we hope to have a web with all the documentation.
anything that you need, feel free to ask :)

awesome, thanks for the fast response!


Master merge

This brings the fixes from the release branch onto master. Untested.

SITL CI test this please

SITL CI test this please

Awesome! Merging.


Enrich kubectl edit with OpenAPI data

[WIP] Scoping this out for 1.20
What would you like to be added:
Why is this needed:

/assign @eddiezane @Xercoy
/priority backlog


Fix TypeError: Illegal invocation

Fix an error that is occurring when toggling the wide screen mode on and off in Chrome 66 (probably many versions earlier too)

Thanks for the contriution!


API/release status?

Hello there and thank you for this wrapper!
I want to know how stable the API is and whether you are planning to do any versioned releases?
I intend to use the audio library and would like to extend it to support multiple operations in parallel; Right now for instance there's only one callback possible at a time. Changing this would require API-breaking changes.
Hence my question whether you are planning to do a v1 release after such a contribution, or a v1 release now, followed by a v2 release.

Hello,
I don't think there are many users of this lib who will complain, so that change is really welcomed.
What I wanted to do is to make this current package a sub package named mini_al, and then mal package on root to be a higher level interface to that package, simple to use and with only io.Reader and io.Writer like in this package https://github.com/hajimehoshi/oto .
I can add tags every time mini_al.h is updated, but there is no need for v1, v2 etc.

Hm, interesting - I didn't know about oto so much so far.
The approach with their Writer interface is interesting, though the crucial benefit (and difference) for malgo that I see is the event-driven nature. So, instead of packing the (malgo) player behind a Writer interface, I now had the idea to pass that high-level API you proposed a Reader interface for playback, and a Writer interface for capturing. The respective callbacks would use these interfaces in a blocking manner.
Should the user still want to have a Writer interface for playback (or a Reader for capturing), then there's io.Pipe() which can be used to reverse the nature.
I'll have a go at this.

OK, I tried some stuff, did some refactoring with a promising API - and ended up in various access violations, scribbling around in random memory. And now, thanks to a mishap, I've just lost a few files. (PSA: git stash does not store untracked files...)
This is going to take a little longer :)

API looks much better now, thanks! I will close this issue, if you have more ideas or suggestions they are welcomed.


Add Caleb to Apps team

Not sure if he should also be added to https://developers.mattermost.com/contribute/getting-started/core-committers/

Oh yeah, I'll add him there too


IDVA6-1141 TypeError: Cannot read properties of null (reading 'addEventListener')

Link to Jira:
https://companieshouse.atlassian.net/browse/IDVA6-1141
Changes:

trackEvent calls for the button and link related to search made optional
Vulnerabilities in dependencies fixed

CI: No security warnings found


build is not automated via rpm specfile

Current status
Instructions in current rpm specfile expects that the source tarball (specified via Source0: %{name}-%{version}.tar.gz) contains the build of dashboard already.
To perform this build, one needs manually follow information in README file (installing npm, gulp, ... configuration and build itself).
Latest COPR build of tendrl-dashboard doesn't do the build either: the srpm file pushed into COPR contains "source" tarball with the build and spec file from this repository, with a minor change:
$ diff tendrl-dashboard.spec tendrl-dashboard.git.spec
3c3
< Release: 02_20_2017_19_24_15
---
> Release: 1%{?dist}

Description of the problem
The most important problem with the current state are:

build is not completely automated
entire build process is not specified in specfile, rpmbuild doesn't do the build

This also means that (just listing few obvious consequences here):

source tarball is not in fact source, but it contains actual build
rpm rebuild of source rpm file would no nothing
actual build process is done outside of build system

Expected status
The specfile contains:

list of all build requirements (javascript build tools such as npm ...)
commands to generate html pages (the build process) are specified in %build section

This way, the whole build process is done via rpmbuild.
Note: for this to work, you would need to create a mock environment which will have required javascript dev tools available.

@dahorak @mkudlej (fyi)

@TimothyAsir please explore the path to resolve this once you are back from PTO

Is this on-going or, are we done? If yes, can we close it with a comment?

Is this on-going or, are we done? If yes, can we close it with a comment?

This is on going.

This is already taken care. @mbukatov  please close this issue

If this can be verified as complete, please provide update on this.

@mbukatov , do you agree with what is implemented? I am planning to close this issue

The change looks good, thank you for fixing this, it will make the maintenance much easier!
I was trying to rebuild the package step by step myself to check the process. First I need to get source tarballs and I decided to generate them based on current source from git repo:
[makerpm@telesto projects]$ git clone https://github.com/Tendrl/dashboard.git tendrl-dashboard
[makerpm@telesto projects]$ cd tendrl-dashboard
[makerpm@telesto tendrl-dashboard]$ make build-pkgs-dist
[makerpm@telesto tendrl-dashboard]$ make dist

At this point, I have both source tarballs listed in the spec file:
$ ls -lh tendrl-*tar.gz
-rw-rw-r--. 1 makerpm makerpm 220K May 25 15:59 tendrl-dashboard-1.3.0.tar.gz
-rw-rw-r--. 1 makerpm makerpm  91M May 25 15:57 tendrl-dashboard-build-pkgs.tar.gz

Then I generated source rpm file:
[makerpm@telesto projects]$ cp tendrl-*tar.gz ~/rpmbuild/SOURCES
[makerpm@telesto projects]$ cp tendrl-dashboard.spec ~/rpmbuild/SPECS
[makerpm@telesto projects]$ cd ~/rpmbuild/SPECS
[makerpm@telesto SPECS]$ rpmbuild -bs tendrl-dashboard.spec

So that I can run mock rpmbuild:
[makerpm@telesto tendrl-dashboard]$ mock -r epel-7-x86_64 ~/rpmbuild/SRPMS/tendrl-dashboard-1.3.0-1.fc25.src.rpm

And all looks good:
$ ls -lh /var/lib/mock/epel-7-x86_64/result
total 97M
-rw-rw-r--. 1 makerpm mock 3.6M May 25 16:09 build.log
-rw-rw-r--. 1 makerpm mock 1.7K May 25 16:07 hw_info.log
-rw-rw-r--. 1 makerpm mock 180K May 25 16:09 root.log
-rw-rw-r--. 1 makerpm mock  839 May 25 16:09 state.log
-rw-rw-r--. 1 makerpm mock 3.7M May 25 16:09 tendrl-dashboard-1.3.0-1.el7.centos.noarch.rpm
-rw-rw-r--. 1 makerpm mock  89M May 25 16:08 tendrl-dashboard-1.3.0-1.el7.centos.src.rpm

I used Fedora 25 with:
$ rpm -q nodejs npm
nodejs-6.10.3-1.fc25.x86_64
npm-3.10.10-<IP_ADDRESS>.1.fc25.x86_64

One note though, I would expect that both tarballs tendrl-dashboard-1.3.0.tar.gz and tendrl-dashboard-build-pkgs.tar.gz would be released as a part of upstream tendrl release.


'Error when opening file: open ~/.cache/nvim/nvim-texlabconfig.json: no such file or directory' but it exists

I am trying to get inverse search and forward search to work with skim on MacOS with neovim. Forward search works perfectly, but when I try to do an inverse search, skim seems to do nothing. When I run the built executable that is passed to skim, it gives the error Error when opening file: open ~/.cache/nvim/nvim-texlabconfig.json: no such file or directory. However, when I run ls ~/.cache/nvim/ it should that nvim-texlabconfig.json exists. Even if I copy the path from the error and paste it as an argument to vim it opens properly and has text in it. How can I fix this?

Ok passing in absolute paths make it work properly, but how am I supposed to do this through Skim as its still not doing anything?

but how am I supposed to do this through Skim as its still not doing anything?

I do not have a mac, so I cannot help you directly.
In theory, Inverse search is activated by pressing Shift and Command, then clicking the text you want to search. For more info on inverse search.
You should look for synctex in its documentation.

@f3fora That is what I am currently doing, but it does nothing.

Looks like the same problem I had while writing #21


Environment variable prefix

Reason: The environment variables were too generic for example: DATA, this could cause conflicts in shared environments with other applications.
What PR does: It adds a "CEDAR_AGENT_" prefix to all cedar agent environment variables, this resolves possible conflicts with other applications that use this same variable, in addition to maintaining support for those using variables in the format without the prefix, that is, old users of the system can apply this update without any problem.
NOTE: As mentioned earlier, I've added support for those using environment variables without the prefix, but I've changed the README for variables with the prefix to enforce usage with the prefix for new users of the system.

Sorry for the delay, will address this next week


Feature/added background color

Just realized this package doesn't come with background color out of the box

Thank you for your contribution, I have added backgroundColor propertie to version 1.3.0


how to use string interpolation with InlineSVG

I want to load 500+ svg image so I use *ngFor to loop over them, but unfortunately hadn't success with doing so using interpolation
 <div *ngFor='let icon of icons'>
        <div  [inlineSVG]="'/img/{{icon}}.svg'"></div>
</div>

it raises error in "'/img/{{icon}}.svg'"

sure I should have wrote the exact error message pardon me. But I didn't have access to my development pc so I wrote the issue with out the technical details out of the memory.
I researched it a little further and found that it is not ng-inline-svg specific issue, but rather it is something related to how angular treat the property binding:
https://stackoverflow.com/questions/42456459/got-interpolation-where-expression-was-expected
thanks for your work


[#164987516] Enable all RDS extensions

What
This PR enables all RDS supported Postgres extensions to be enabled by tenants without the involvement of support.
How to review
Code review and deploy this branch and try enabling some new extensions
Before merging
Update the tmp commit with the generated sha of the final boshrelease
Who can review
anyone

Rebased this onto master and amended the last commit to update the SHA1

Review
After my typo fix commit
Create a service
 ~/Code/paas-cf  ⑂ wip-tlwr  Mon 15 Apr 2019 13:00:58 BST (tlwr) ✅
🧢   cf cs  postgres tiny-unencrypted-9.5 tlwr-test-extensions -c '{"enable_extensions": ["citext", "hstore", "pg_trgm"]}'
Creating service instance tlwr-test-extensions in org admin / space assets as admin...
OK

Create in progress. Use 'cf services' or 'cf service tlwr-test-extensions' to check operation status.

It creates successfully
 ~/Code/paas-cf  ⑂ wip-tlwr  Mon 15 Apr 2019 13:01:05 BST (tlwr) ✅
🧢   cf service tlwr-test-extensions
Showing info of service tlwr-test-extensions in org admin / space assets as admin...

name:            tlwr-test-extensions
service:         postgres
tags:
plan:            tiny-unencrypted-9.5
description:     AWS RDS PostgreSQL service
documentation:   https://aws.amazon.com/documentation/rds/
dashboard:

Showing status of last operation from service tlwr-test-extensions...

status:    create in progress
message:   DB Instance 'rdsbroker-4111f023-f5a1-4c8c-9eee-413111db6986' status is 'creating'
started:   2019-04-15T12:01:05Z
updated:   2019-04-15T12:01:08Z

There are no bound apps for this service.

Create succeeds
 ~/Code/paas-cf  ⑂ wip-tlwr  Mon 15 Apr 2019 13:01:45 BST (tlwr) ✅
🧢   cf service tlwr-test-extensions
Showing info of service tlwr-test-extensions in org admin / space assets as admin...

name:            tlwr-test-extensions
service:         postgres
tags:
plan:            tiny-unencrypted-9.5
description:     AWS RDS PostgreSQL service
documentation:   https://aws.amazon.com/documentation/rds/
dashboard:

Showing status of last operation from service tlwr-test-extensions...

status:    create succeeded
message:   DB Instance 'rdsbroker-4111f023-f5a1-4c8c-9eee-413111db6986' status is 'available'
started:   2019-04-15T12:01:05Z
updated:   2019-04-15T12:06:20Z

There are no bound apps for this service.

Update the service to enable UUIDs
 ~/Code/paas-cf  ⑂ wip-tlwr  Mon 15 Apr 2019 13:20:22 BST (tlwr) ✅
🧢   cf update-service  tlwr-test-extensions -c '{"enable_extensions": ["uuid-ossp"]}'
Updating service instance tlwr-test-extensions as admin...
OK

Update in progress. Use 'cf services' or 'cf service tlwr-test-extensions' to check operation status.

Update succeeds
 ~/Code/paas-cf  ⑂ wip-tlwr  Mon 15 Apr 2019 13:22:33 BST (tlwr) ✅
🧢   cf service tlwr-test-extensions
Showing info of service tlwr-test-extensions in org admin / space assets as admin...

name:            tlwr-test-extensions
service:         postgres
tags:
plan:            tiny-unencrypted-9.5
description:     AWS RDS PostgreSQL service
documentation:   https://aws.amazon.com/documentation/rds/
dashboard:

Showing status of last operation from service tlwr-test-extensions...

status:    update succeeded
message:   DB Instance 'rdsbroker-4111f023-f5a1-4c8c-9eee-413111db6986' status is 'available'
started:   2019-04-15T12:20:28Z
updated:   2019-04-15T12:22:45Z

There are no bound apps for this service.

cf conduit to check UUID functions work
 ~/Code/paas-cf  ⑂ wip-tlwr  Mon 15 Apr 2019 13:23:05 BST (tlwr) ✅
🧢   cf conduit tlwr-test-extensions -- psql
OK Connecting client
OK Targeting org admin
OK Targeting space assets
OK Deploying __conduit_25602__
OK Uploading __conduit_25602__ bits
OK Starting __conduit_25602__
OK Waiting for conduit app to become available
OK Fetching service infomation
OK Binding tlwr-test-extensions
OK Fetching environment
OK Starting port forwarding
OK Waiting for port forwarding
OK Preparing command: psql
psql (11.2, server 9.5.15)
SSL connection (protocol: TLSv1.2, cipher: ECDHE-RSA-AES256-GCM-SHA384, bits: 256, compression: off)
Type "help" for help.

rdsbroker_4111f023_f5a1_4c8c_9eee_413111db6986=> select * from uuid_generate_v4();
           uuid_generate_v4
--------------------------------------
 1a58c844-dd24-4bb3-a05b-4725b923fe3c
(1 row)


release version 1.1.0

Contains the following fixes:

joyent/node-lomstream#3 limits above 1000 should be supported
joyent/node-lomstream#5 assertion in _read prevents usage of datacb()
joyent/node-lomstream#6 tst.badarg.js does not detect an unexpected success
joyent/node-lomstream#7 "limit" argument must be an integer

<EMAIL_ADDRESS>published to npm.


Add chart index to support installing the released chart

The addition of a chart index detailing released versions of federation will allow the following installation workflow:
helm repo add fedv2-charts https://raw.githubusercontent.com/marun/federation-v2/add-chart-repo-index/charts/
helm install fedv2-charts/federation-v2 --name=federation-v2 --version=0.0.8 --namespace federation-system

This PR is intended to merge ahead of the update to the helm instructions proposed in #751.

LGTM

/lgtm


How is the result compared to the paper realistic evaluation of deep ssl learning algorithms

Good question, I updated and run the baseline but I had to stop the training. I need to run for 1200 epochs? With 35 I was having good results on CIFAR-10

python train.py -a=wideresnet -m=baseline -o=adam -b=225 --dataset=cifar10_zca --gpu=6,7 --lr=0.003 --boundary=0

I have just finished running the baseline code, and the top precision is 77.95% (I would expect around 80% according to the paper result). I suspect the L1 regularization has little effect since it is averaged over millions of parameters.
Dear @heitorrapela , what is the result you've got?

@Jongchan , I didn't finish the training. But seems to be good the result that you got.

WRN-28-2 (not 3!)
@heitorrapela Just got the result over the weekend.
Mean Teacher
python train.py -a=wideresnet -m=mt -o=adam -b=225 --dataset=cifar10_zca --gpu=6,7 --lr=0.0004 --boundary=0

Last log
Learning rate schedule for Adam
Learning rate: 0.000080
Mean Teacher model
Epoch: [1199][0/367]    Time 1.057 (1.057)  Data 0.948 (0.948)  Loss 0.0087 (0.0087)    LossCL 0.0040 (0.0040)  Prec@1 100.000 (100.000)    Prec@5 100.000 (100.000)    PrecT@1 100.000 (100.000)   PrecT@5 100.000 (100.000)
Epoch: [1199][100/367]  Time 0.091 (0.119)  Data 0.000 (0.023)  Loss 0.0083 (0.0083)    LossCL 0.0052 (0.0063)  Prec@1 100.000 (99.982) Prec@5 100.000 (100.000)    PrecT@1 100.000 (99.973)    PrecT@5 100.000 (100.000)
Epoch: [1199][200/367]  Time 0.096 (0.115)  Data 0.000 (0.020)  Loss 0.0063 (0.0086)    LossCL 0.0054 (0.0068)  Prec@1 100.000 (99.978) Prec@5 100.000 (99.996) PrecT@1 100.000 (99.973)    PrecT@5 100.000 (100.000)
Epoch: [1199][300/367]  Time 0.098 (0.115)  Data 0.000 (0.020)  Loss 0.0075 (0.0084)    LossCL 0.0043 (0.0065)  Prec@1 100.000 (99.982) Prec@5 100.000 (99.997) PrecT@1 100.000 (99.982)    PrecT@5 100.000 (100.000)
Valid: [0/23]   Time 0.471 (0.471)  Loss 0.7086 (0.7086)    Prec@1 84.889 (84.889)  Prec@5 97.333 (97.333)
 ****** Prec@1 78.800 Prec@5 96.380 Loss 1.038
Test: [0/45]    Time 0.483 (0.483)  Loss 0.8086 (0.8086)    Prec@1 82.667 (82.667)  Prec@5 96.000 (96.000)
 ****** Prec@1 77.630 Prec@5 96.810 Loss 1.077
Valid: [0/23]   Time 0.467 (0.467)  Loss 0.7076 (0.7076)    Prec@1 84.444 (84.444)  Prec@5 96.444 (96.444)
 ****** Prec@1 78.820 Prec@5 96.440 Loss 1.033
Test: [0/45]    Time 0.437 (0.437)  Loss 0.8259 (0.8259)    Prec@1 81.333 (81.333)  Prec@5 96.444 (96.444)
 ****** Prec@1 77.920 Prec@5 96.690 Loss 1.073
Best test precision: 79.490

PI model
python train.py -a=wideresnet -m=pi -o=adam -b=225 --dataset=cifar10_zca --gpu=6,7 --lr=0.0003 --boundary=0

Last log
Learning rate schedule for Adam
Learning rate: 0.000060
Pi model
Epoch: [1199][0/367]    Time 1.046 (1.046)  Data 0.924 (0.924)  Loss 0.0090 (0.0090)    LossPi 0.0022 (0.0022)  Prec@1 100.000 (100.000)    Prec@5 100.000 (100.000)
Epoch: [1199][100/367]  Time 0.146 (0.138)  Data 0.000 (0.024)  Loss 0.0109 (0.0089)    LossPi 0.0018 (0.0028)  Prec@1 100.000 (99.982) Prec@5 100.000 (100.000)
Epoch: [1199][200/367]  Time 0.119 (0.141)  Data 0.000 (0.022)  Loss 0.0072 (0.0085)    LossPi 0.0009 (0.0030)  Prec@1 100.000 (99.987) Prec@5 100.000 (100.000)
Epoch: [1199][300/367]  Time 0.123 (0.141)  Data 0.000 (0.021)  Loss 0.0079 (0.0084)    LossPi 0.0011 (0.0029)  Prec@1 100.000 (99.991) Prec@5 100.000 (100.000)
Valid: [0/23]   Time 0.509 (0.509)  Loss 0.7784 (0.7784)    Prec@1 84.000 (84.000)  Prec@5 96.889 (96.889)
 ****** Prec@1 79.180 Prec@5 97.220 Loss 0.947
Test: [0/45]    Time 0.463 (0.463)  Loss 0.9564 (0.9564)    Prec@1 80.444 (80.444)  Prec@5 97.333 (97.333)
 ****** Prec@1 78.330 Prec@5 97.420 Loss 1.002
Best test precision: 78.650

Haven't run the baseline WRN 28-2, but it seems far away from the numbers reported in the paper.
On the positive side, the results must be better than WRN28-2, because they are already better than WRN28-3 performance.
Wonder if the official TensorFlow code can reproduce the paper result.. :(

In the TensorFlow version, I was able to get the numbers reported in the paper. I can safely think the official code works well with SSL methods, too. I will validate that after, tho.
One thing to notice in the official code is that they don't use any regularizations. Kinda different from the NeurIPS paper (and suppl).
It may take a while to thoroughly go over the code, but currently I suspect that the inferior result in this repository is due to possibly different normalization or different split. I will report back after running with the same data and split.

@Jongchan Hi， i am working on the reproduction of the paper in pytorch too. I've check the wideresnet implementation and find "activation before res" set wrong in comparison with the TF code. I think you have a try on this issue.

@CheukNgai  Hi, currently I am not using the code from this repository.
But as you pointed out, it seems they are using the opposite settings from TF implementation. I missed that point. I am currently using codes from https://github.com/xternalz/WideResNet-pytorch/blob/master/wideresnet.py and changed ReLU to LeakyReLU.
Now I can safely achieve baseline performance in the NeurIPS paper, around 20.2~20.4% error rate with plain WRN28-2. Mostly I've changed data pre-processing (the normalization part), and removed L1 / L2 regularization.
Counter-intuitively, removing L1/L2 regularizations improves top-1 accuracy, even if CIFAR-10 is a highly-overfittable dataset.

@Jongchan could you give more details on the your implementation on preprocessing? It would help me a lot! Thank you!

@CheukNgai Sorry, my comment must have mislead you.
I just used the same preprocessing as mentioned in this repository's readme (GCN and ZCA) with gaussian noise with std 0.15. I used mean-std normalization before.
Anyways, try removing L1/L2, or set L1 as a very very small number.


Update index.ts

Add export of toggle-selector

Is there any problem in merging this PR to master?!


sc2: Fixing some incorrect unlocks for Blood Hunter, Energizer, and Protoss Air Upgrades

See issues on the main AP repo, #90 - energizer, #95 - Blood Hunter, and #88 - stargate unlock from air upgrades.
I tested the fixes by manually re-applying them to the triggers file after I did a /download_data, and checking I could build energizers and blood hunters with the items in my inventory. I did not do extra checking for the stargate, though I still tested things loaded with the stargate changes applied to the trigger file.
I noticed when I copy-pasted the whole file that the triggers failed to initialize; I'm not sure why, I think it's related to other issues that are in the repo but aren't in the published triggers file.

Picked just unit fixes. The Stargate is for being able to build Cybercore


Use driver for RegexpParser tests

Which issue(s) this PR fixes:
( https://github.com/fluent/fluentd/pull/4066#discussion_r1118388855 )
What this PR does / why we need it:
I didn't know why it was commented out, but it looked good on Fluent::Test::Driver::Parser.new(...).
https://github.com/fluent/fluentd/pull/1286
Docs Changes:
None
Release Note:
None

Thanks!

Thanks for the merge!


[Creators] Add a detailed data analysis activity

MicroByte Title: Linear Regression with Regularization
Improvement Proposal:
Make an activity preceding the first activity in the micro-byte, which does the following:

Performs a detailed Data Analysis for the given dataset.
Perform outlier detection and removal.
Perform Feature Engineering.
Perform Feature Selection.
Save the preprocessed data frame along with the original dataset.

After you have the preprocessed form of the dataset, you can extend Activity 1 by using a different linear regression model trained on new preprocessed data and show the reduction in error which a simple preprocessing can lead to.
Benefits of proposed improvements:
Users will get a practical intuition of the increase in the performance or reduction in the error, to which a carefully preprocessed dataset can lead to

Can I take up this issue?

Sure. Go Ahead.

Hey, @Aditya-Gupta1 Should I need to add the data analysis on the jupyter notebook in the activity 1 folder?

@rutujak24 Assigning this to you !
Waiting for your contribution 🎉

Thanks, @sudhanshutiwari264
I have made the contribution and resolved this issue, here it is: https://github.com/Crio-Bytes/Miscellaneous/pull/65

@rutujak24 Great Work!! But additionally, I also mentioned preprocessing data and applying linear regression to that preprocessed dataset. This will demonstrate a low test error on the same dataset and learners can have a practical example of how preprocessing can lead to effective modeling.
You can add this part in activity 5 itself.

@rutujak24 Great Work!! But additionally, I also mentioned preprocessing data and applying linear regression to that preprocessed dataset. This will demonstrate a low test error on the same dataset and learners can have a practical example of how preprocessing can lead to effective modeling.
You can add this part in activity 5 itself.

Thanks @Aditya-Gupta1
I guess whatever I have done is pretty much enough the data analysis, the regression part which you are speaking about can be added to activity 5 where the modelling would be described. So it should be included in activity 4.
Hence I guess tge PR satisfies all the requirements for detailed data analysis, so should be merged.


Deprecate DockerSELinuxMCS feature gate and provide an alternative configuration

Add annotation for DockerSELinuxMCS bug workaround
Deprecate DockerSELinuxMCS feature Gate
This introduces an annotation in the KubeVirt CR to
handle the DockerSELinuxMCS bug: https://github.com/moby/moby/issues/41370.
Using an annotation instead of a dedicated field avoids
locking this workaround into the v1 API, as the bug will
likely be fixed in the future.
Once resolved, we can simply remove the annotation
without impacting the API.
What this PR does
Before this PR:
Workaround to the bug could be done through DockerSELinuxMCS Feature Gate
After this PR:
DockerSELinuxMCS Feature Gate is deprecated
Workaround to the bug can be done through DockerSELinuxMCS Feature Gate or DockerSELinuxMCS annotation

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
If we add a new field to the KubeVirt CR spec, we won’t be able to remove it easily since it will be part of the v1 API. By using an annotation for the bug workaround, we can simply remove the annotation code once the bug is fixed, and that's it.
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a remA doc PR for User Guide will be created soon.
inder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

Add annotation for DockerSELinuxMCS bug workaround

/hold
@Barakmor1 I think this implementation is wrong, this patch unconditionally enables DockerSELinuxMCSWorkaround which then instructs virt-launcher to always change the pod's SELinux MCS.
What we want to do instead is to never do this unless the annotation is set as we never want to remove the MCS of the containers unless we're dealing with docker as a cri.
@jean-edouard can you please double check as well?
Holding as a safety measure, until we're sure the PR does the correct thing.

I think this is true only when we set a feature gate to be GA.

@acardace I believe @EdDev changed this behavior and as @Barakmor1  points out the deprecated will not be enabled ...

/unhold
sorry I missed that change, thanks @Barakmor1 @xpivarc, all good then.
@Barakmor1 one comment before I do a full review, I'd adhere to the convention of having annotations in kebab case instead of camel case.

/unhold
sorry I missed that change, thanks @Barakmor1 @xpivarc, all good then.
@Barakmor1 one comment before I do a full review, I'd adhere to the convention of having annotations in kebab case instead of camel case.

Thanks for the note. Yes, that makes sense since all the other annotations are in kebab case.
It's done.

Using an annotation instead of a dedicated field avoids
locking this workaround into the v1 API, as the bug will
likely be fixed in the future.
Once resolved, we can simply remove the annotation
without impacting the API.

I heard about this with the morning coffee.
I find it hard to understand how adding an annotation instead of a FG is a valid thing.
The FG has attempted to provide a solution to a temporary problem.
The problem has not been resolved at the source and the FG also reached a timeout on which it needs to be removed.
Users who are effected, need to pressure the project that has this issue to solve it.
Kubevirt tries its best to overcome issues like this, but cannot commit to keep them forever.
If we do want to keep it, then I suggest to provide a solution out-of-tree to this.
Please try to avoid hacks like this, IMO it is worse than a FG.

If we do want to keep it, then I suggest to provide a solution out-of-tree to this.

In that case we could just document that Docker users must not enable SELinux in /etc/docker/daemon.json (it is disabled by default) or VMs will not start.

I agree with @EdDev on this, if we want to be accommodating we can delay removing the annotation in 1 release just to give time to people to be aware of this but I wouldn't disagree on removing all of this immediately.
Essentially it just tells that people using docker do not care about this or don't use SELinux (very likely).

@xpivarc @EdDev I agree that it should probably be removed. This feature gate was created to give more time to fix a bug in another project. Since it's been a long time, I don't think we need to support it anymore. I’ve updated the PR to remove the workaround, and I’ll add documentation, as @jean-edouard  suggested, if the PR gets merged.

Why are we deleting the related code if we are just deprecating the FG?


Missing items: [ITEMS]

Does not find any IDs of shadow priest gear when importing using WowSimsExporter addon - 40287, 44657, 40450, 39425, 40602, 37884, 39519, 40271, 40448, 40326, 40433, 40108, 42132, 42988, 40395, 40192, 40245

Kel'Thuzad's Reach is missing

I definitely see those items in the sim. Perhaps your page failed to properly load?

Hey James, thanks for the reply. I have tried multiple times, I export my current gear using WowSimsExporter addon (current version) and insert the string into Import -> Addon window. It says that the import was successful but none of the item IDs was found. Not sure what am I doing wrong tbh.

Seemed to have been a browser problem. Fixed =)

Thanks for confirming!


[NuGet Symbol Server] Egress through integration with Microsoft Symbol Server

Work with MSDL team to ensure the egress of symbols work. This is ongoing until all the environments are set and working

End of sprint 135: Dev environment is created. Symbols cannot yet be retrieved,

This item is done. Verified on int, dev and prod.


Convert NetworkTask to sync style & add message delete task

We always assumed we would get a 200 OK from the server and it was a proper JSON api response. The NetworkTask also was built to be asynchronous with callbacks, however its never used in an asynchronous way.
HttpResponse is also included which holds a simplified class of what the response was like. This gives us the ability to check status codes + headers.

Closes #83


Properly shade com.google.code.gson:gson

The "shaded" JAR of closure-compiler includes all the classes in com.google.gson without shading (renaming). This can lead to confusing errors far downstream - for example, I came upon this issue when sbt-dependency-check raised a NoMethodError, which turned out to be caused by my project using scala-js. I am definitely not the first one to experience this.
Is there a reason why com.google.gson is bundled rather than shaded? What is the "preferred" way to deal with such problems downstream?

I'm not sure, I expect it can be shaded but no one noticed.  Perhaps a PR is appropriate


Remove DBClusterNotFoundFault as a terminal condition for GlobalCluster.

Issue #, if available: aws-controllers-k8s/community#1027
Description of changes:
Remove DBClusterNotFoundFault as a terminal condition for GlobalCluster.
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license.

/retest

Thanks @A-Hilaly


create swift template

Needs checking and editing.
Anyone is free to take this over and complete it.
Resolves #14

Maybe use fastlane?
https://semaphoreci.com/blog/tutorial-ios-cicd

Maybe use fastlane? https://semaphoreci.com/blog/tutorial-ios-cicd

Fastlane's tooling and workflow is quite different. I think it'd be good to keep this folder a vanilla Swift template.
I raised a separate PR for Fastlane + iOS https://github.com/buildkite/templates/pull/42
We could also create another template for Fastlane + Android. I've raised a separate issue https://github.com/buildkite/templates/issues/43


Next challenge

Has completed the challenge of adding a color red to the h2 element but it has refuse to go to the next challenge.

@Esetessy thanks for the issue. Can you give us more information about your issue? Like challenge name and your code? Please fill out the issue template next time. This provides us important information to be able to help.

Please refer to this issue: https://github.com/FreeCodeCamp/FreeCodeCamp/issues/12376#issuecomment-270673036

Closing, please help us with more clarification on the issue you are facing.


python310Packages.watchdog: 2.3.0 -> 2.3.1

https://github.com/gorakhargosh/watchdog/blob/v2.3.1/changelog.rst
less risky than #225406
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Looking at https://github.com/gorakhargosh/watchdog/blob/master/changelog.rst#300 I don't see too much to be concerned about. Largely just code quality changes and dropping Python 3.6. I would suggest #225406 be merged instead.

I don't know.  Say, the less risky one now for 23.05.

Looking at<EMAIL_ADDRESS>I don't see too much to be concerned about. Largely just code quality changes and dropping Python 3.6. I would suggest #225406 be merged instead.

Yeah, but projects will have pins that say <3, which will ripple through the package set, and I'm not in a position to resolve these right now.

Oh, the conditional patch doesn't apply:
https://hydra.nixos.org/build/217596281

Dropping the patch doesn't resolve the original issue described in PR #171388

Planning to go with #225406 instead. It has the updated patch.


Settlement report refactor

Features

Refactoring out aggregate settlement reports.

Delivers #130356905

@srleach please pre-review

@srleach

@00eadeyemi


ActionView::Template::Error: undefined method next_id for nil:NilClass

Fixes #3734

Frontend tests were OK :+1: (details)

retest this please

Frontend tests were OK :+1: (details)


[Popover] Not working well with onMouseLeave

Problem description
When I use onMouseEnter and onMouseLeave to show a popup (tooltip behavior), the popup does not appear.
Link to minimal working code that reproduces the issue
https://codesandbox.io/s/wpjvm86AM
Versions

Material-UI: 0.18.2
React: 15.5.3
Browser: N/A

I suspect the issue is that when the popup is open it adds an overlay to the screen, so that the button is no longer on top, resulting in immediate onMouseLeave.
Is there a way to overcome this? I thought that maybe setting a different zIndex to the popup might fix this, but I'm not sure.

The solution was to add useLayerForClickAway={false}:
https://codesandbox.io/s/M8gnnOzmQ

https://stackoverflow.com/questions/54965013/onmouseleave-for-popover-with-hiderbackdrop-parameter-material-ui

Ran into this issue today. Some searching told me that the useLayerForClickAway isn't a supported attribute anymore.
Adding style={{ pointerEvents: 'none'}} as an attribute on the Popover solved the issue for me.
Solution found here: https://gitmemory.com/issue/mui-org/material-ui/7680/512825747'
I hope this helps anyone else running into this issue that stumbles on this page.

Ran into this issue today. Some searching told me that the useLayerForClickAway isn't a supported attribute anymore.
Adding style={{ pointerEvents: 'none'}} as an attribute on the Popover solved the issue for me.
Solution found here: https://gitmemory.com/issue/mui-org/material-ui/7680/512825747'
I hope this helps anyone else running into this issue that stumbles on this page.

This worked!
The documentation should mention this..
https://material-ui.com/components/popover/#mouse-over-interaction

Duplicate of #7680


Not AN Issue But Still DOes not know how to use plz put vieo and plz and Nintendo DS

Nintendo DS: #15
Video: don't count on it


Is PEP 541 proper approach to dealing with sniped project name?

Describe the bug
Attempted to push package to https://pypi.org/ and received the error:
The user 'aws-icpsh' isn't allowed to upload to project 'awsiot-credentialhelper'

When I checked the URL https://pypi.org/project/awsiot-credentialhelper/ I saw that it was a spam package with no content or source URL. I opened an issue for PEP 541, but am not sure if that's the right approach.
After that, the package looks to be removed (404 now) so thought it might have been cleared. But still getting the same Forbidden 403 error. I understand the error is on our side as we made the repo public prior to pushing the first release. Just curious if opening the PEP 541 is the correct way to go and gain access, or if there is any recourse.
Issue we're tracking right now.
First time running into this, so apologies if I'm asking in the wrong setting.

Hey @gadams999, no worries. PEP 541 is the right approach here, the project name is still owned by the original owner, it just has no releases so doesn't show up on PyPI.


Add a chapter that explains borsh serialization in an easier-to-understand way than borsh.io does

whats most important is how much space each type takes so instead of this

we should just say
u8 -> 1,
u16 -> 2

and instead of this

we should have this
Option<T> -> 1 + <Space that T takes>


Update Write_ChckOutLst.m for AeroDyn multi-rotor

Update Write_ChckOutLst.m to correctly generate I/O code for AeroDyn, considering changes needed to support multiple rotors (i.e., variables passing and declarations).

Hi Hannah, I'm waiting for the branches to be merged in OpenFAST before merging your pull request in that repo, I hope that 's fine with you!

I think all relevant branches have been merged into openfast/dev, so this can probably be merged now as well.