Build image - jenkins failure

plugins failed to download! Download integrity: credentials-binding
Logs
2020-05-10T05:43:18.0186982Z Step 11/13 : COPY init/plugins.txt /usr/share/jenkins/ref/plugins.txt
2020-05-10T05:43:19.0175401Z  ---> 10bbeddd9ca0
2020-05-10T05:43:19.0175879Z Step 12/13 : RUN /usr/local/bin/install-plugins.sh < /usr/share/jenkins/ref/plugins.txt
2020-05-10T05:43:19.0353897Z  ---> Running in 2bdbc19f771b
2020-05-10T05:43:19.4156495Z Creating initial locks...
2020-05-10T05:43:19.5171874Z Analyzing war /usr/share/jenkins/jenkins.war...
2020-05-10T05:43:19.6533518Z Registering preinstalled plugins...
2020-05-10T05:43:20.0458202Z Downloading plugins...
2020-05-10T05:43:20.0517616Z Downloading plugin: pam-auth from https://updates.jenkins.io/download/plugins/pam-auth/latest/pam-auth.hpi
2020-05-10T05:43:20.0589251Z Downloading plugin: ldap from https://updates.jenkins.io/download/plugins/ldap/latest/ldap.hpi
2020-05-10T05:43:20.0606290Z Downloading plugin: docker-workflow from https://updates.jenkins.io/download/plugins/docker-workflow/latest/docker-workflow.hpi
2020-05-10T05:43:20.0627173Z Downloading plugin: credentials-binding from https://updates.jenkins.io/download/plugins/credentials-binding/latest/credentials-binding.hpi
2020-05-10T05:43:20.0662002Z Downloading plugin: metrics from https://updates.jenkins.io/download/plugins/metrics/latest/metrics.hpi
2020-05-10T05:43:20.0736680Z Downloading plugin: workflow-aggregator from https://updates.jenkins.io/download/plugins/workflow-aggregator/latest/workflow-aggregator.hpi
2020-05-10T05:43:20.0745125Z Downloading plugin: momentjs from https://updates.jenkins.io/download/plugins/momentjs/latest/momentjs.hpi
2020-05-10T05:43:20.0756260Z Downloading plugin: pipeline-milestone-step from https://updates.jenkins.io/download/plugins/pipeline-milestone-step/latest/pipeline-milestone-step.hpi
2020-05-10T05:43:20.0766369Z Downloading plugin: google-oauth-plugin from https://updates.jenkins.io/download/plugins/google-oauth-plugin/latest/google-oauth-plugin.hpi
2020-05-10T05:43:20.0777851Z Downloading plugin: pipeline-rest-api from https://updates.jenkins.io/download/plugins/pipeline-rest-api/latest/pipeline-rest-api.hpi
2020-05-10T05:43:20.0784897Z Downloading plugin: git from https://updates.jenkins.io/download/plugins/git/latest/git.hpi
2020-05-10T05:43:20.0790074Z Downloading plugin: jdk-tool from https://updates.jenkins.io/download/plugins/jdk-tool/latest/jdk-tool.hpi
2020-05-10T05:43:20.0796737Z Downloading plugin: ws-cleanup from https://updates.jenkins.io/download/plugins/ws-cleanup/latest/ws-cleanup.hpi
2020-05-10T05:43:20.0806984Z Downloading plugin: pipeline-stage-step from https://updates.jenkins.io/download/plugins/pipeline-stage-step/latest/pipeline-stage-step.hpi
2020-05-10T05:43:20.0831034Z Downloading plugin: git-client from https://updates.jenkins.io/download/plugins/git-client/latest/git-client.hpi
2020-05-10T05:43:20.0846868Z Downloading plugin: jsch from https://updates.jenkins.io/download/plugins/jsch/latest/jsch.hpi
2020-05-10T05:43:20.0861875Z Downloading plugin: handlebars from https://updates.jenkins.io/download/plugins/handlebars/latest/handlebars.hpi
2020-05-10T05:43:20.0877879Z Downloading plugin: timestamper from https://updates.jenkins.io/download/plugins/timestamper/latest/timestamper.hpi
2020-05-10T05:43:20.0888718Z Downloading plugin: pipeline-build-step from https://updates.jenkins.io/download/plugins/pipeline-build-step/latest/pipeline-build-step.hpi
2020-05-10T05:43:20.0894951Z Downloading plugin: bouncycastle-api from https://updates.jenkins.io/download/plugins/bouncycastle-api/latest/bouncycastle-api.hpi
2020-05-10T05:43:20.0906337Z Downloading plugin: ssh-slaves from https://updates.jenkins.io/download/plugins/ssh-slaves/latest/ssh-slaves.hpi
2020-05-10T05:43:20.0918829Z Downloading plugin: pipeline-model-api from https://updates.jenkins.io/download/plugins/pipeline-model-api/latest/pipeline-model-api.hpi
2020-05-10T05:43:20.0924608Z Downloading plugin: branch-api from https://updates.jenkins.io/download/plugins/branch-api/latest/branch-api.hpi
2020-05-10T05:43:20.0986089Z Downloading plugin: workflow-cps from https://updates.jenkins.io/download/plugins/workflow-cps/latest/workflow-cps.hpi
2020-05-10T05:43:20.0992946Z Downloading plugin: workflow-api from https://updates.jenkins.io/download/plugins/workflow-api/latest/workflow-api.hpi
2020-05-10T05:43:20.1024742Z Downloading plugin: pipeline-github-lib from https://updates.jenkins.io/download/plugins/pipeline-github-lib/latest/pipeline-github-lib.hpi
2020-05-10T05:43:20.1060702Z Downloading plugin: github-branch-source from https://updates.jenkins.io/download/plugins/github-branch-source/latest/github-branch-source.hpi
2020-05-10T05:43:20.1068120Z Downloading plugin: cloudbees-folder from https://updates.jenkins.io/download/plugins/cloudbees-folder/latest/cloudbees-folder.hpi
2020-05-10T05:43:20.1096514Z Downloading plugin: workflow-cps-global-lib from https://updates.jenkins.io/download/plugins/workflow-cps-global-lib/latest/workflow-cps-global-lib.hpi
2020-05-10T05:43:20.1097332Z Downloading plugin: workflow-multibranch from https://updates.jenkins.io/download/plugins/workflow-multibranch/latest/workflow-multibranch.hpi
2020-05-10T05:43:20.1111378Z Downloading plugin: pipeline-model-extensions from https://updates.jenkins.io/download/plugins/pipeline-model-extensions/latest/pipeline-model-extensions.hpi
2020-05-10T05:43:20.1173967Z Downloading plugin: mapdb-api from https://updates.jenkins.io/download/plugins/mapdb-api/latest/mapdb-api.hpi
2020-05-10T05:43:20.1207164Z Downloading plugin: email-ext from https://updates.jenkins.io/download/plugins/email-ext/latest/email-ext.hpi
2020-05-10T05:43:20.1263423Z Downloading plugin: workflow-durable-task-step from https://updates.jenkins.io/download/plugins/workflow-durable-task-step/latest/workflow-durable-task-step.hpi
2020-05-10T05:43:20.1275816Z Downloading plugin: apache-httpcomponents-client-4-api from https://updates.jenkins.io/download/plugins/apache-httpcomponents-client-4-api/latest/apache-httpcomponents-client-4-api.hpi
2020-05-10T05:43:20.1346031Z Downloading plugin: variant from https://updates.jenkins.io/download/plugins/variant/latest/variant.hpi
2020-05-10T05:43:20.1726688Z Downloading plugin: workflow-step-api from https://updates.jenkins.io/download/plugins/workflow-step-api/latest/workflow-step-api.hpi
2020-05-10T05:43:20.1744002Z Downloading plugin: github from https://updates.jenkins.io/download/plugins/github/latest/github.hpi
2020-05-10T05:43:20.1759499Z Downloading plugin: workflow-scm-step from https://updates.jenkins.io/download/plugins/workflow-scm-step/latest/workflow-scm-step.hpi
2020-05-10T05:43:20.1778499Z Downloading plugin: lockable-resources from https://updates.jenkins.io/download/plugins/lockable-resources/latest/lockable-resources.hpi
2020-05-10T05:43:20.1822501Z Downloading plugin: junit from https://updates.jenkins.io/download/plugins/junit/latest/junit.hpi
2020-05-10T05:43:20.1835529Z Downloading plugin: matrix-project from https://updates.jenkins.io/download/plugins/matrix-project/latest/matrix-project.hpi
2020-05-10T05:43:20.1846964Z Downloading plugin: gradle from https://updates.jenkins.io/download/plugins/gradle/latest/gradle.hpi
2020-05-10T05:43:20.1864344Z Downloading plugin: resource-disposer from https://updates.jenkins.io/download/plugins/resource-disposer/latest/resource-disposer.hpi
2020-05-10T05:43:20.2148321Z Downloading plugin: structs from https://updates.jenkins.io/download/plugins/structs/latest/structs.hpi
2020-05-10T05:43:20.2297749Z Downloading plugin: pipeline-stage-tags-metadata from https://updates.jenkins.io/download/plugins/pipeline-stage-tags-metadata/latest/pipeline-stage-tags-metadata.hpi
2020-05-10T05:43:20.2512908Z Downloading plugin: kubernetes from https://updates.jenkins.io/download/plugins/kubernetes/latest/kubernetes.hpi
2020-05-10T05:43:20.2667083Z Downloading plugin: script-security from https://updates.jenkins.io/download/plugins/script-security/latest/script-security.hpi
2020-05-10T05:43:20.2781069Z Downloading plugin: ant from https://updates.jenkins.io/download/plugins/ant/latest/ant.hpi
2020-05-10T05:43:20.2817729Z Downloading plugin: github-api from https://updates.jenkins.io/download/plugins/github-api/latest/github-api.hpi
2020-05-10T05:43:20.3021732Z Downloading plugin: pipeline-model-definition from https://updates.jenkins.io/download/plugins/pipeline-model-definition/latest/pipeline-model-definition.hpi
2020-05-10T05:43:20.3060277Z Downloading plugin: kubernetes-client-api from https://updates.jenkins.io/download/plugins/kubernetes-client-api/latest/kubernetes-client-api.hpi
2020-05-10T05:43:20.3154380Z Downloading plugin: command-launcher from https://updates.jenkins.io/download/plugins/command-launcher/latest/command-launcher.hpi
2020-05-10T05:43:20.3190347Z Downloading plugin: jackson2-api from https://updates.jenkins.io/download/plugins/jackson2-api/latest/jackson2-api.hpi
2020-05-10T05:43:20.3581405Z Downloading plugin: scm-api from https://updates.jenkins.io/download/plugins/scm-api/latest/scm-api.hpi
2020-05-10T05:43:20.3746648Z Downloading plugin: build-timeout from https://updates.jenkins.io/download/plugins/build-timeout/latest/build-timeout.hpi
2020-05-10T05:43:20.3820339Z Downloading plugin: plain-credentials from https://updates.jenkins.io/download/plugins/plain-credentials/latest/plain-credentials.hpi
2020-05-10T05:43:20.4020748Z Downloading plugin: workflow-basic-steps from https://updates.jenkins.io/download/plugins/workflow-basic-steps/latest/workflow-basic-steps.hpi
2020-05-10T05:43:20.4057919Z Downloading plugin: antisamy-markup-formatter from https://updates.jenkins.io/download/plugins/antisamy-markup-formatter/latest/antisamy-markup-formatter.hpi
2020-05-10T05:43:20.4344883Z Downloading plugin: durable-task from https://updates.jenkins.io/download/plugins/durable-task/latest/durable-task.hpi
2020-05-10T05:43:20.4349637Z Downloading plugin: pipeline-model-declarative-agent from https://updates.jenkins.io/download/plugins/pipeline-model-declarative-agent/latest/pipeline-model-declarative-agent.hpi
2020-05-10T05:43:20.4419979Z Downloading plugin: jquery-detached from https://updates.jenkins.io/download/plugins/jquery-detached/latest/jquery-detached.hpi
2020-05-10T05:43:20.4540262Z Downloading plugin: pipeline-stage-view from https://updates.jenkins.io/download/plugins/pipeline-stage-view/latest/pipeline-stage-view.hpi
2020-05-10T05:43:20.4620398Z Downloading plugin: pipeline-input-step from https://updates.jenkins.io/download/plugins/pipeline-input-step/latest/pipeline-input-step.hpi
2020-05-10T05:43:20.4656548Z Downloading plugin: workflow-support from https://updates.jenkins.io/download/plugins/workflow-support/latest/workflow-support.hpi
2020-05-10T05:43:20.5131702Z Downloading plugin: oauth-credentials from https://updates.jenkins.io/download/plugins/oauth-credentials/latest/oauth-credentials.hpi
2020-05-10T05:43:20.5256427Z Downloading plugin: token-macro from https://updates.jenkins.io/download/plugins/token-macro/latest/token-macro.hpi
2020-05-10T05:43:20.5262894Z Downloading plugin: prometheus from https://updates.jenkins.io/download/plugins/prometheus/latest/prometheus.hpi
2020-05-10T05:43:20.5339448Z Downloading plugin: mailer from https://updates.jenkins.io/download/plugins/mailer/latest/mailer.hpi
2020-05-10T05:43:20.5505873Z Downloading plugin: trilead-api from https://updates.jenkins.io/download/plugins/trilead-api/latest/trilead-api.hpi
2020-05-10T05:43:20.5558695Z Downloading plugin: ace-editor from https://updates.jenkins.io/download/plugins/ace-editor/latest/ace-editor.hpi
2020-05-10T05:43:20.5621195Z Downloading plugin: git-server from https://updates.jenkins.io/download/plugins/git-server/latest/git-server.hpi
2020-05-10T05:43:20.5631388Z Downloading plugin: kubernetes-credentials from https://updates.jenkins.io/download/plugins/kubernetes-credentials/latest/kubernetes-credentials.hpi
2020-05-10T05:43:20.5889226Z Downloading plugin: subversion from https://updates.jenkins.io/download/plugins/subversion/latest/subversion.hpi
2020-05-10T05:43:20.6101265Z Downloading plugin: display-url-api from https://updates.jenkins.io/download/plugins/display-url-api/latest/display-url-api.hpi
2020-05-10T05:43:20.6340172Z Downloading plugin: credentials from https://updates.jenkins.io/download/plugins/credentials/latest/credentials.hpi
2020-05-10T05:43:20.6501139Z Downloading plugin: ssh-credentials from https://updates.jenkins.io/download/plugins/ssh-credentials/latest/ssh-credentials.hpi
2020-05-10T05:43:20.6574424Z Downloading plugin: pipeline-graph-analysis from https://updates.jenkins.io/download/plugins/pipeline-graph-analysis/latest/pipeline-graph-analysis.hpi
2020-05-10T05:43:20.6588628Z Downloading plugin: docker-commons from https://updates.jenkins.io/download/plugins/docker-commons/latest/docker-commons.hpi
2020-05-10T05:43:20.6598496Z Downloading plugin: workflow-job from https://updates.jenkins.io/download/plugins/workflow-job/latest/workflow-job.hpi
2020-05-10T05:43:20.6700535Z Downloading plugin: authentication-tokens from https://updates.jenkins.io/download/plugins/authentication-tokens/latest/authentication-tokens.hpi
2020-05-10T05:43:21.0892238Z  > workflow-aggregator depends on lockable-resources:2.3,pipeline-stage-view:2.10,workflow-api:2.29,workflow-basic-steps:2.11,workflow-cps-global-lib:2.11,workflow-cps:2.56,workflow-durable-task-step:2.22,workflow-job:2.25,workflow-multibranch:2.20,workflow-scm-step:2.6,workflow-step-api:2.16,workflow-support:2.20,cloudbees-folder:6.6,credentials:2.1.18,git-client:2.7.3,jackson2-api:<IP_ADDRESS>,pipeline-build-step:2.7,pipeline-input-step:2.8,pipeline-milestone-step:1.3.1,pipeline-stage-step:2.3,scm-api:2.2.8,structs:1.15,pipeline-model-definition:1.3.2
2020-05-10T05:43:21.1460186Z Downloaded file is not a valid ZIP: /usr/share/jenkins/ref/plugins/credentials-binding.jpi
2020-05-10T05:43:21.1671488Z  > pipeline-stage-step depends on workflow-api:2.15,workflow-step-api:2.11,scm-api:2.0.7,structs:1.6
2020-05-10T05:43:21.2042458Z  > pipeline-milestone-step depends on workflow-api:2.11,workflow-step-api:2.9
2020-05-10T05:43:21.2424734Z  > workflow-durable-task-step depends on workflow-api:2.33,workflow-step-api:2.20,workflow-support:3.3,durable-task:1.33,scm-api:2.2.6,script-security:1.58,structs:1.18
2020-05-10T05:43:21.2687145Z  > ssh-slaves depends on credentials:2.3.0,ssh-credentials:1.18,trilead-api:1.0.5
2020-05-10T05:43:21.3050808Z  > workflow-scm-step depends on workflow-step-api:2.9
2020-05-10T05:43:21.3225680Z Downloaded file is not a valid ZIP: /usr/share/jenkins/ref/plugins/junit.jpi
2020-05-10T05:43:21.3307081Z  > pipeline-stage-tags-metadata depends on workflow-api:2.36
2020-05-10T05:43:21.3382023Z Downloaded file is not a valid ZIP: /usr/share/jenkins/ref/plugins/github.jpi
2020-05-10T05:43:21.3424931Z  > ant depends on structs:1.17
2020-05-10T05:43:21.4405835Z  > gradle depends on structs:1.20,workflow-api:2.37,workflow-cps:2.74,workflow-job:2.35,workflow-basic-steps:2.16.1,workflow-durable-task-step:2.28,workflow-step-api:2.20
2020-05-10T05:43:21.4530199Z  > matrix-project depends on junit:1.20,script-security:1.54
2020-05-10T05:43:21.4585058Z  > jsch depends on ssh-credentials:1.14,trilead-api:1.0.5
2020-05-10T05:43:21.4786022Z Downloaded file is not a valid ZIP: /usr/share/jenkins/ref/plugins/jackson2-api.jpi
2020-05-10T05:43:21.4897835Z  > pipeline-github-lib depends on workflow-cps-global-lib:2.5,git:3.0.2
2020-05-10T05:43:21.4984381Z  > plain-credentials depends on credentials:2.2.0
2020-05-10T05:43:21.5309430Z  > pipeline-build-step depends on workflow-api:2.33,workflow-step-api:2.22,workflow-support:3.1,script-security:1.50
2020-05-10T05:43:21.5546689Z  > scm-api depends on structs:1.9
2020-05-10T05:43:21.5666794Z  > github-branch-source depends on github:1.29.3,github-api:1.110,jackson2-api:2.10.2
2020-05-10T05:43:21.5777723Z  > kubernetes-credentials depends on apache-httpcomponents-client-4-api:4.5.5-3.0,authentication-tokens:1.3,credentials:2.2.0,docker-commons:1.14,google-oauth-plugin:0.8,jackson2-api:2.9.9,kubernetes-client-api:1.0.0,plain-credentials:1.5
2020-05-10T05:43:21.5845682Z  > command-launcher depends on script-security:1.68
2020-05-10T05:43:21.6051727Z  > pipeline-rest-api depends on workflow-api:2.24,workflow-job:2.12,workflow-step-api:2.14,workflow-support:2.14,jackson2-api:<IP_ADDRESS>,pipeline-graph-analysis:1.4,pipeline-input-step:2.8,pipeline-stage-step:2.3
2020-05-10T05:43:21.6153793Z  > cloudbees-folder depends on credentials:2.2.0;resolution:=optional
2020-05-10T05:43:21.6301427Z  > workflow-api depends on workflow-step-api:2.16,scm-api:2.2.6,structs:1.17
2020-05-10T05:43:21.6392713Z  > pipeline-model-extensions depends on workflow-cps:2.76,workflow-job:2.33,credentials-binding:1.13,credentials:2.1.16,pipeline-stage-step:2.3,pipeline-model-api:1.6.0
2020-05-10T05:43:21.6458458Z  > lockable-resources depends on workflow-support:3.4,mailer:1.18,matrix-project:1.14,script-security:1.62,structs:1.20
2020-05-10T05:43:21.6490137Z  > workflow-step-api depends on structs:1.20
2020-05-10T05:43:21.6527932Z  > pipeline-model-declarative-agent depends on pipeline-model-extensions:1.1.1
2020-05-10T05:43:21.6741911Z  > pipeline-input-step depends on workflow-api:2.35,workflow-step-api:2.20,workflow-support:3.3,credentials:2.3.0
2020-05-10T05:43:21.6799153Z  > workflow-multibranch depends on workflow-api:2.27,workflow-cps:2.53,workflow-job:2.21,workflow-scm-step:2.4,workflow-step-api:2.13,workflow-support:2.17,branch-api:2.0.21,cloudbees-folder:6.1.2,scm-api:2.2.7,script-security:1.42,structs:1.17
2020-05-10T05:43:21.6869781Z  > authentication-tokens depends on credentials:1.22
2020-05-10T05:43:21.6874975Z  > git-server depends on git-client:2.7.6
2020-05-10T05:43:21.6960440Z  > workflow-basic-steps depends on workflow-api:2.40,workflow-durable-task-step:2.31,workflow-step-api:2.22,apache-httpcomponents-client-4-api:4.5.10-2.0,mailer:1.32,structs:1.20
2020-05-10T05:43:21.6985038Z  > git depends on configuration-as-code:1.35;resolution:=optional,workflow-scm-step:2.9,workflow-step-api:2.20,credentials:2.3.0,git-client:3.0.0,mailer:1.23,matrix-project:1.14;resolution:=optional,parameterized-trigger:2.33;resolution:=optional,promoted-builds:3.2;resolution:=optional,scm-api:2.6.3,script-security:1.66,ssh-credentials:1.17.3,structs:1.20,token-macro:2.10;resolution:=optional
2020-05-10T05:43:21.7019230Z  > pipeline-graph-analysis depends on workflow-api:2.34,workflow-cps:2.65,workflow-job:2.32,workflow-step-api:2.19,workflow-support:3.2,pipeline-input-step:2.8,pipeline-stage-step:2.3,scm-api:2.2.7,structs:1.17
2020-05-10T05:43:21.7175626Z  > oauth-credentials depends on credentials:2.3.0
2020-05-10T05:43:21.7393690Z  > email-ext depends on workflow-job:2.12;resolution:=optional,workflow-step-api:2.19;resolution:=optional,config-file-provider:2.15.6;resolution:=optional,junit:1.2,mailer:1.13,matrix-project:1.4,script-security:1.54,structs:1.17,token-macro:2.3,analysis-core:1.54;resolution:=optional
2020-05-10T05:43:21.7554150Z  > docker-commons depends on authentication-tokens:1.3,credentials-binding:1.18,credentials:2.1.18,pipeline-model-extensions:1.3.8;resolution:=optional
2020-05-10T05:43:21.7557248Z Skipping optional dependency credentials
2020-05-10T05:43:21.7641363Z  > ldap depends on mailer:1.20
2020-05-10T05:43:21.7724234Z  > mailer depends on display-url-api:2.3.1
2020-05-10T05:43:21.7853806Z  > token-macro depends on workflow-step-api:2.14,structs:1.14
2020-05-10T05:43:21.7906719Z Skipping optional dependency configuration-as-code
2020-05-10T05:43:21.7966708Z  > timestamper depends on workflow-api:2.39,workflow-step-api:2.19
2020-05-10T05:43:21.8148990Z Skipping optional dependency workflow-job
2020-05-10T05:43:21.8382210Z  > ssh-credentials depends on credentials:2.2.0,trilead-api:1.0.5
2020-05-10T05:43:21.8419003Z  > build-timeout depends on naginator:1.16;resolution:=optional,token-macro:1.5.1
2020-05-10T05:43:21.8481188Z  > docker-workflow depends on workflow-basic-steps:2.18,workflow-cps:2.76,workflow-durable-task-step:2.31,workflow-step-api:2.22,cloudbees-folder:6.9,docker-commons:1.14,pipeline-model-extensions:1.5.1
2020-05-10T05:43:21.8540423Z  > pipeline-stage-view depends on pipeline-rest-api:2.13,workflow-api:2.24,workflow-job:2.12,handlebars:1.1.1,jquery-detached:1.2.1,momentjs:1.1
2020-05-10T05:43:21.8632952Z Downloaded file is not a valid ZIP: /usr/share/jenkins/ref/plugins/kubernetes.jpi
2020-05-10T05:43:21.8694854Z  > workflow-support depends on workflow-api:2.36,workflow-step-api:2.20,scm-api:2.2.6,script-security:1.39
2020-05-10T05:43:21.8961459Z Skipping optional dependency workflow-step-api
2020-05-10T05:43:21.9144349Z  > branch-api depends on cloudbees-folder:6.11,scm-api:2.4.1,structs:1.18
2020-05-10T05:43:21.9201376Z Skipping optional dependency naginator
2020-05-10T05:43:21.9856011Z Skipping optional dependency config-file-provider
2020-05-10T05:43:21.9927289Z  > prometheus depends on workflow-api:2.15,workflow-job:2.15,junit:1.2,metrics:<IP_ADDRESS>
2020-05-10T05:43:22.0402060Z  > workflow-cps-global-lib depends on workflow-api:2.33,workflow-cps:2.71,workflow-scm-step:2.7,workflow-step-api:2.20,workflow-support:3.3,cloudbees-folder:6.1.2,credentials:2.1.18,git-server:1.7,scm-api:2.6.3,script-security:1.70,structs:1.19
2020-05-10T05:43:22.0861638Z  > workflow-cps depends on workflow-api:2.36,workflow-scm-step:2.4,workflow-step-api:2.21,workflow-support:3.3,scm-api:2.2.6,script-security:1.63,structs:1.20,support-core:2.43;resolution:=optional,ace-editor:1.0.1,jquery-detached:1.2.1
2020-05-10T05:43:22.0898996Z  > metrics depends on workflow-durable-task-step:2.15;resolution:=optional,jackson2-api:<IP_ADDRESS>,variant:1.1
2020-05-10T05:43:22.1202362Z  > pipeline-model-definition depends on workflow-api:2.36,workflow-basic-steps:2.18,workflow-cps-global-lib:2.9,workflow-cps:2.76,workflow-durable-task-step:2.31,workflow-multibranch:2.16,workflow-scm-step:2.9,workflow-support:3.3,credentials-binding:1.13,credentials:2.1.16,docker-workflow:1.22,git-client:2.7.0,mailer:1.20,pipeline-input-step:2.8,pipeline-stage-step:2.3,scm-api:2.4.1,pipeline-model-api:1.6.0,pipeline-model-declarative-agent:1.1.1,pipeline-model-extensions:1.6.0,pipeline-stage-tags-metadata:1.6.0
2020-05-10T05:43:22.1567368Z Skipping optional dependency workflow-durable-task-step
2020-05-10T05:43:22.1878157Z  > workflow-job depends on workflow-api:2.36,workflow-step-api:2.20,workflow-support:3.3
2020-05-10T05:43:22.2394584Z Skipping optional dependency pipeline-model-extensions
2020-05-10T05:43:22.4185623Z  > google-oauth-plugin depends on credentials:2.2.0,oauth-credentials:0.3
2020-05-10T05:43:22.4281596Z Skipping optional dependency matrix-project
2020-05-10T05:43:22.4681654Z Skipping optional dependency parameterized-trigger
2020-05-10T05:43:22.5106051Z Skipping optional dependency promoted-builds
2020-05-10T05:43:22.5338110Z  > pipeline-model-api depends on workflow-step-api:2.22,jackson2-api:2.9.8,structs:1.20
2020-05-10T05:43:22.5460635Z Skipping optional dependency analysis-core
2020-05-10T05:43:22.6307967Z Skipping optional dependency support-core
2020-05-10T05:43:22.6382351Z  > ws-cleanup depends on workflow-durable-task-step:2.4,matrix-project:1.7.1,resource-disposer:0.3,script-security:1.54,structs:1.19
2020-05-10T05:43:22.6848264Z Skipping optional dependency token-macro
2020-05-10T05:43:22.7886576Z  > subversion depends on workflow-scm-step:2.6,credentials:2.1.16,mapdb-api:<IP_ADDRESS>,scm-api:2.6.3,ssh-credentials:1.12,structs:1.9
2020-05-10T05:43:22.8654885Z  > git-client depends on configuration-as-code:1.35;resolution:=optional,apache-httpcomponents-client-4-api:4.5.10-2.0,credentials:2.3.0,jsch:<IP_ADDRESS>,script-security:1.66,ssh-credentials:1.17.3,structs:1.20
2020-05-10T05:43:22.8715010Z  > kubernetes-client-api depends on bouncycastle-api:2.17,jackson2-api:2.10.3
2020-05-10T05:43:22.8770793Z Skipping optional dependency configuration-as-code
2020-05-10T05:43:23.7196699Z  > credentials depends on configuration-as-code:1.35;resolution:=optional,structs:1.20
2020-05-10T05:43:23.7214534Z Skipping optional dependency configuration-as-code
2020-05-10T05:43:25.1183290Z  > github-api depends on jackson2-api:2.10.2
2020-05-10T05:43:25.1232116Z
2020-05-10T05:43:25.1232767Z WAR bundled plugins:
2020-05-10T05:43:25.1232925Z
2020-05-10T05:43:25.1233021Z
2020-05-10T05:43:25.1238328Z Installed plugins:
2020-05-10T05:43:25.1287569Z ace-editor:1.1
2020-05-10T05:43:25.1335568Z ant:1.11
2020-05-10T05:43:25.1380509Z antisamy-markup-formatter:2.0
2020-05-10T05:43:25.1431142Z apache-httpcomponents-client-4-api:4.5.10-2.0
2020-05-10T05:43:25.1483403Z authentication-tokens:1.3
2020-05-10T05:43:25.1534494Z bouncycastle-api:2.18
2020-05-10T05:43:25.1582058Z branch-api:2.5.6
2020-05-10T05:43:25.1631184Z build-timeout:1.19.1
2020-05-10T05:43:25.1681223Z cloudbees-folder:6.12
2020-05-10T05:43:25.1737298Z command-launcher:1.4
2020-05-10T05:43:25.1782337Z warning [/usr/share/jenkins/ref/plugins/credentials-binding.jpi]:  65345 extra bytes at beginning or within zipfile
2020-05-10T05:43:25.1782561Z   (attempting to process anyway)
2020-05-10T05:43:25.1782978Z error [/usr/share/jenkins/ref/plugins/credentials-binding.jpi]:  start of central directory not found;
2020-05-10T05:43:25.1783163Z   zipfile corrupt.
2020-05-10T05:43:25.1783330Z   (please check that you have transferred or created the zipfile in the
2020-05-10T05:43:25.1783797Z   appropriate BINARY mode and that you have compiled UnZip properly)
2020-05-10T05:43:25.1795161Z credentials-binding:
2020-05-10T05:43:25.1842753Z credentials:2.3.7
2020-05-10T05:43:25.1895603Z display-url-api:2.3.2
2020-05-10T05:43:25.1947601Z docker-commons:1.16
2020-05-10T05:43:25.1995077Z docker-workflow:1.23
2020-05-10T05:43:25.2041081Z durable-task:1.34
2020-05-10T05:43:25.2097526Z email-ext:2.69
2020-05-10T05:43:25.2140530Z git-client:3.2.1
2020-05-10T05:43:25.2189615Z git-server:1.9
2020-05-10T05:43:25.2233624Z git:4.2.2
2020-05-10T05:43:25.2278900Z github-api:1.111
2020-05-10T05:43:25.2322369Z github-branch-source:2.7.1
2020-05-10T05:43:25.2358060Z error [/usr/share/jenkins/ref/plugins/github.jpi]:  missing 916479765 bytes in zipfile
2020-05-10T05:43:25.2358331Z   (attempting to process anyway)
2020-05-10T05:43:25.2358503Z error [/usr/share/jenkins/ref/plugins/github.jpi]:  start of central directory not found;
2020-05-10T05:43:25.2358680Z   zipfile corrupt.
2020-05-10T05:43:25.2358845Z   (please check that you have transferred or created the zipfile in the
2020-05-10T05:43:25.2359030Z   appropriate BINARY mode and that you have compiled UnZip properly)
2020-05-10T05:43:25.2365861Z github:
2020-05-10T05:43:25.2415062Z google-oauth-plugin:1.0.0
2020-05-10T05:43:25.2460294Z gradle:1.36
2020-05-10T05:43:25.2505976Z handlebars:1.1.1
2020-05-10T05:43:25.2548199Z error [/usr/share/jenkins/ref/plugins/jackson2-api.jpi]:  missing<PHONE_NUMBER> bytes in zipfile
2020-05-10T05:43:25.2548394Z   (attempting to process anyway)
2020-05-10T05:43:25.2548808Z error [/usr/share/jenkins/ref/plugins/jackson2-api.jpi]:  start of central directory not found;
2020-05-10T05:43:25.2548980Z   zipfile corrupt.
2020-05-10T05:43:25.2549145Z   (please check that you have transferred or created the zipfile in the
2020-05-10T05:43:25.2549346Z   appropriate BINARY mode and that you have compiled UnZip properly)
2020-05-10T05:43:25.2560125Z jackson2-api:
2020-05-10T05:43:25.2606912Z jdk-tool:1.4
2020-05-10T05:43:25.2652735Z jquery-detached:1.2.1
2020-05-10T05:43:26.0293863Z jsch:<IP_ADDRESS>
2020-05-10T05:43:26.0295908Z error [/usr/share/jenkins/ref/plugins/junit.jpi]:  missing<PHONE_NUMBER> bytes in zipfile
2020-05-10T05:43:26.0296251Z   (attempting to process anyway)
2020-05-10T05:43:26.0296550Z error [/usr/share/jenkins/ref/plugins/junit.jpi]:  start of central directory not found;
2020-05-10T05:43:26.0296849Z   zipfile corrupt.
2020-05-10T05:43:26.0297134Z   (please check that you have transferred or created the zipfile in the
2020-05-10T05:43:26.0297455Z   appropriate BINARY mode and that you have compiled UnZip properly)
2020-05-10T05:43:26.0297985Z junit:
2020-05-10T05:43:26.0298486Z kubernetes-client-api:4.9.1-1
2020-05-10T05:43:26.0298982Z kubernetes-credentials:0.6.2
2020-05-10T05:43:26.0300060Z error [/usr/share/jenkins/ref/plugins/kubernetes.jpi]:  missing<PHONE_NUMBER> bytes in zipfile
2020-05-10T05:43:26.0300368Z   (attempting to process anyway)
2020-05-10T05:43:26.0300676Z error [/usr/share/jenkins/ref/plugins/kubernetes.jpi]:  attempt to seek before beginning of zipfile
2020-05-10T05:43:26.0300994Z   (please check that you have transferred or created the zipfile in the
2020-05-10T05:43:26.0301312Z   appropriate BINARY mode and that you have compiled UnZip properly)
2020-05-10T05:43:26.0301835Z kubernetes:
2020-05-10T05:43:26.0302077Z ldap:1.24
2020-05-10T05:43:26.0302566Z lockable-resources:2.8
2020-05-10T05:43:26.0302818Z mailer:1.32
2020-05-10T05:43:26.0303350Z mapdb-api:<IP_ADDRESS>
2020-05-10T05:43:26.0303816Z matrix-project:1.14
2020-05-10T05:43:26.0304063Z metrics:<IP_ADDRESS>
2020-05-10T05:43:26.0304303Z momentjs:1.1.1
2020-05-10T05:43:26.0304774Z oauth-credentials:0.4
2020-05-10T05:43:26.0305325Z pam-auth:1.6
2020-05-10T05:43:26.0305796Z pipeline-build-step:2.12
2020-05-10T05:43:26.0306281Z pipeline-github-lib:1.0
2020-05-10T05:43:26.0306771Z pipeline-graph-analysis:1.10
2020-05-10T05:43:26.0307258Z pipeline-input-step:2.11
2020-05-10T05:43:26.0307912Z pipeline-milestone-step:1.3.1
2020-05-10T05:43:26.0308396Z pipeline-model-api:1.6.0
2020-05-10T05:43:26.0308909Z pipeline-model-declarative-agent:1.1.1
2020-05-10T05:43:26.0309508Z pipeline-model-definition:1.6.0
2020-05-10T05:43:26.0310008Z pipeline-model-extensions:1.6.0
2020-05-10T05:43:26.0310493Z pipeline-rest-api:2.13
2020-05-10T05:43:26.0310966Z pipeline-stage-step:2.3
2020-05-10T05:43:26.0311461Z pipeline-stage-tags-metadata:1.6.0
2020-05-10T05:43:26.0311949Z pipeline-stage-view:2.13
2020-05-10T05:43:26.0312422Z plain-credentials:1.7
2020-05-10T05:43:26.0312672Z prometheus:2.0.6
2020-05-10T05:43:26.0313145Z resource-disposer:0.14
2020-05-10T05:43:26.0313599Z scm-api:2.6.3
2020-05-10T05:43:26.0314064Z script-security:1.71
2020-05-10T05:43:26.0314538Z ssh-credentials:1.18.1
2020-05-10T05:43:26.0315007Z ssh-slaves:1.31.2
2020-05-10T05:43:26.0315260Z structs:1.20
2020-05-10T05:43:26.0315507Z subversion:2.13.1
2020-05-10T05:43:26.0315753Z timestamper:1.11.3
2020-05-10T05:43:26.0316213Z token-macro:2.12
2020-05-10T05:43:26.0316682Z trilead-api:1.0.6
2020-05-10T05:43:26.0316924Z variant:1.3
2020-05-10T05:43:26.0317389Z workflow-aggregator:2.6
2020-05-10T05:43:26.0317849Z workflow-api:2.40
2020-05-10T05:43:26.0318316Z workflow-basic-steps:2.20
2020-05-10T05:43:26.0318802Z workflow-cps-global-lib:2.16
2020-05-10T05:43:26.0319265Z workflow-cps:2.80
2020-05-10T05:43:26.0319742Z workflow-durable-task-step:2.35
2020-05-10T05:43:26.0320205Z workflow-job:2.39
2020-05-10T05:43:26.0320672Z workflow-multibranch:2.21
2020-05-10T05:43:26.0321148Z workflow-scm-step:2.11
2020-05-10T05:43:26.0321617Z workflow-step-api:2.22
2020-05-10T05:43:26.0322080Z workflow-support:3.4
2020-05-10T05:43:26.0322540Z ws-cleanup:0.38
2020-05-10T05:43:26.0323127Z Some plugins failed to download! Download integrity: credentials-binding
2020-05-10T05:43:26.0323415Z Download integrity: junit
2020-05-10T05:43:26.0323678Z Download integrity: github
2020-05-10T05:43:26.0324168Z Download integrity: jackson2-api
2020-05-10T05:43:26.0324434Z Download integrity: kubernetes
2020-05-10T05:43:26.8394523Z The command '/bin/sh -c /usr/local/bin/install-plugins.sh < /usr/share/jenkins/ref/plugins.txt' returned a non-zero code: 1
2020-05-10T05:43:26.8445828Z
2020-05-10T05:43:26.8449980Z ##[error]Process completed with exit code 1.

Some plugins failed to download! Download integrity: matrix-auth

https://web.plus-idea.net/2019/07/plugin-pre-installed-jenkins-docker/

done.


Incorrect inheritance

Acording to this article, sql_logins should inherit server_principals, but it doesn't.
sql_logins fails to inherit the following two columns from server_principals:

owning_principal_id
is_fixed_role

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

ID: 7432bff9-69c5-181a-8f9e-5501d7c03807
Version Independent ID: bf59bcd2-80b2-53dd-060e-2575ac5c39d1
Content: sys.sql_logins (Transact-SQL) - SQL Server
Content Source: docs/relational-databases/system-catalog-views/sys-sql-logins-transact-sql.md
Product: sql
Technology: system-objects
GitHub Login: @VanMSFT
Microsoft Alias: vanto

@PawJershauge -- Paw, thank you for your feedback.
@VanMSFT -- Van, please look into this issue 3363.

Hello @PawJershauge! Thanks for submitting this issue. Sorry for the delay. I have changed the article to clarify that those 2 columns are not inherited.


Comprehensive JSON export

JSON Export with comprehensive details of box flags, graphics lists, etc etc.

JSON has issues dealing with mixing RTL and LTR text that Unicode doesn't solve. W3C has a proposed solution, or you can roll your own, or XML actually manages this.

Huh.  At the moment there is the larger issue that Boxer doesn't support left to right language support yet, though I have thought about it a bit.
Do you have any suggested reading on the issues with JSON mixing these and the proposed solution?

I'm closing this general purpose ticket, and will open a new one if any adjustments are needed to the export.


Defence Tracker showing maul %

After a recent update to the plugin, i think the one were it tracks maul first it nows shows a maul % on an info box, could this be added as a toggle so we can turn it off as we can already see the defence in another info box
Screenshot of the info boxes
https://i.imgur.com/3dStp4g.png

Someone in the discord already said they are going to fix this.


init.vim not loaded despite loadInitVim: true

Hello,
I have a very simple init.vim configuration:
set nonumber
set ignorecase
set smartcase
set norelativenumber
set expandtab
set tabstop=2
set shiftwidth=2

saved in ~/.config/nvim/init.vim,
and    "oni.loadInitVim": true, in config.tsx.
Still, my vim settings are not being imported unless I also set    "oni.useDefaultConfig": false, but then I lose the default Vim plugins.
I'm using Oni v.0.3.3

At a guess, your settings might be being loaded but being overwritten by our default settings which can be seen here : https://github.com/onivim/oni/blob/master/vim/default/bundle/oni-vim-defaults/plugin/init.vim.
We have #973 to improve this, and hopefully soon the tab settings will be removed.
I've commented on what I think is happening to your settings:
set nonumber         "Overwritten most likely by the default set number
set ignorecase       "Set smartcase will overwrite set ignorecase I think?
set smartcase        "You'd need to pick between this and ignorecase.
set norelativenumber "Should be fine?
set expandtab        "Should be fine? Set in the default.
set tabstop=2        "Both of these are being over written by the default config.
set shiftwidth=2     "The default config sets them to 4.

We do actually provide an Oni specific way of setting these values too, which shouldn't be overwritten.
That can be done with     "vim.setting.number": false, to set nonumber etc. That would look like:
    "vim.setting.number": false,
    "vim.setting.tabstop": 2,
    "vim.setting.softtabstop": 2,
    "vim.setting.shiftwidth": 2,

That said, the easiest way around this is like you've said with "oni.useDefaultConfig": false, and then installing the plugins Oni gives yourself.
That can either be done with a manual install to the plugin folder, use of a plugin manager like vim-plug, or soon Oni will be exposing a plugin API in the config.tsx that will automate the install to the plugin folder.

Thank you so much @CrossR, all that worked perfectly! I've set the options via the "vim.setting." properties so that I can still enjoy the rest of the default config.
So my init.vim was loaded but just all the settings overwritten either by itself (smartcase) or the default Oni config!
One more thing: I noticed that set shiftwidth=2 really helps a lot with the folding when it's set to indent. But it's probably because the way my files are indented...


Documentation unclear

Recently discovered that certain traffic is always allowed via VPN Gateway (onPrem to AKS API over tcp/443 for example) while other traffic (DNS Resolver to onPrem via tcp/53) is denied.  Lots of investigating finally led me to this Reddit post describing the exact symptoms.
Further investigation led me to this heading "Why are certain ports opened on my Virtual Network Gateway?" in the VPN Gateway FAQ.  My infosec team would love to know (A) what ports are "always open" and (B) why? Documentation is vague at best and very well hidden!
Thanks

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

ID: 98d7fd30-80a8-f690-6191-d97ae4cac174
Version Independent ID: 3e15f99b-2f2d-7adc-a2d9-0b2184989db7
Content: Azure VPN Gateway FAQ
Content Source: articles/vpn-gateway/vpn-gateway-vpn-faq.md
Service: vpn-gateway
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

@bandwiches
Thanks for your feedback! We will investigate and update as appropriate.

@bandwiches The ports that are always open on a Virtual Network Gateway are required for Azure infrastructure communication. These ports are protected by Azure certificates and are periodically scanned by Azure security audit. Without proper certificates, external entities, including the customers of those gateways, won't be able to cause any effect on those endpoints. The specific ports that are opened on a Virtual Network Gateway are not publicly disclosed for security reasons.
I'd recommend working closer with our support team via an Azure support request. Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.Teams Q&A forum for technical questions about the configuration and administration of Microsoft Teams on Windows.Microsoft Teams Community forum

These ports are protected by Azure certificates and are periodically scanned by Azure security audit. Without proper certificates, external entities, including the customers of those gateways, won't be able to cause any effect on those endpoints.

Pretty bold statement to make right before the next sentence:

The specific ports that are opened on a Virtual Network Gateway are not publicly disclosed for security reasons.

@SaibabaBalapur-MSFT If the endpoints are both public and secure, I guess I don't grasp why they can't be publicly disclosed? This sounds like security through obscurity except the ports can be scanned publicly, so it's not really a secret nor effective. I was just hoping for some official documentation. Nevertheless, thanks for your response.

@bandwiches Thanks so much for pointing this out. I've check with our internal team and work for this issue, which we'll track and resolve internally.


npm ERROR

What I'm trying to achieve
Able to access " localhost:3000"
Steps to reproduce the problem

After cloning my project from git
I run " npm i " as instruction
set environment variable as instruction
run "npm start"

What I expected to happen
able to access "localhost:3000"
Screenshots

System information
Operating system: Window 10
Browser: Chrome

Which version of Node and NPM are you using?

Hi @maarcingebala I use
Node : v12.14.1
npm : 6.13.6

Can you share the full error? Versions seem OK. Sometimes removing node_modules and reinstalling everything again also helps.

1st thing
I want to be the contributor of this project, i cloned all the repository

saleor branch (master)
saleor-storefront branch (master)
saleor-dashboard branch (master)
My environment
python 3.8.1, pip 20.0.2
Node 12.14.1, npm 6.13.7
Postgres 9.5
OS : Window 10
I follow all the instruction but still i cannot install on local success.(stuck on  installing python environment)

Question : Would u plz tell me every commit that the team push to master branch in (saleor, saleor-storefront,saleor-dashboard). Does it work synchronized all together ?
2nd thing
about saleor (2.9.1) is it the latest version ?(confirmation question)
+using python3.8.1 to install pip as this command "python -m pip install -r requirements.txt" not success.

Until i uninstall python 3.8.1 and install python 3.7.6 then i run "python -m pip install -r requirements.txt" it works.

Could u please explain more ?

Hi, how do you solve this problem?
18 verbose node v10.14.1 19 verbose npm  v6.13.7 20 error code ELIFECYCLE 21 error errno 1 22 error<EMAIL_ADDRESS>start: cross-env NODE_ENV=develop webpack-dev-server --history-api-fallback --watch --port 3000 --mode development --hotOnly 22 error Exit status 1 23 error Failed at the<EMAIL_ADDRESS>start script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ]
here my error log. I already check for the graphql API_URI and it is ok.. when hit the npm start the error came out.

same here with the same logs

Same here, full log:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'start' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
8 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/user/workspace/frontend/node_modules/.bin:/home/user/workspace/frontend/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
9 verbose lifecycle<EMAIL_ADDRESS>CWD: /home/user/workspace/frontend
10 silly lifecycle<EMAIL_ADDRESS>Args: [
10 silly lifecycle   '-c',
10 silly lifecycle   'cross-env NODE_ENV=develop webpack-dev-server --history-api-fallback --watch --port 3000 --mode development --hotOnly'
10 silly lifecycle ]
11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
12 info lifecycle<EMAIL_ADDRESS>Failed to exec start script
13 verbose stack Error<EMAIL_ADDRESS>start: `cross-env NODE_ENV=develop webpack-dev-server --history-api-fallback --watch --port 3000 --mode development --hotOnly`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:311:20)
13 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:311:20)
13 verbose stack     at maybeClose (internal/child_process.js:1021:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd /home/user/workspace/frontend
16 verbose Linux 4.19.0-8-amd64
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "start"
18 verbose node v12.16.1
19 verbose npm  v6.13.7
20 error code ELIFECYCLE
21 error errno 1
22 error<EMAIL_ADDRESS>start: `cross-env NODE_ENV=develop webpack-dev-server --history-api-fallback --watch --port 3000 --mode development --hotOnly`
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

same here

We've created the saleor-platform repo to set up all components of Saleor at once, can you see if this works for you?

@maarcingebala  thanks for your reply .
i wounder why salor-storefront has same dependency with two diffrent versions.
i can't install two diffret versions of same pckage
ok i will check saleor-platform !

I have the same issue

Getting the same error here. with default Dockerfile on storefront

I solved the problem by deleting the docker container and resetting it. Make sure all the components are available in the container before proceeding. You might be asked to use the ‘’ notation

@solafakhaled I've solved that for now. But now storefront(localhost:3000) returns error indicating graphql API(localhost:8000/graphql) isn't accessible. I've tried to give storefront the same network that api is on but no luck. api is running inside docker container and storefront and api are on the same network so I have no guess why it can't find graphql api

@solafakhaled I've solved that for now. But now storefront(localhost:3000) returns error indicating graphql API(localhost:8000/graphql) isn't accessible. I've tried to give storefront the same network that api is on but no luck. api is running inside docker container and storefront and api are on the same network so I have no guess why it can't find graphql api

@solafakhaled I've solved that for now. But now storefront(localhost:3000) returns error indicating graphql API(localhost:8000/graphql) isn't accessible. I've tried to give storefront the same network that api is on but no luck. api is running inside docker container and storefront and api are on the same network so I have no guess why it can't find graphql api

@solafakhaled I've solved that for now. But now storefront(localhost:3000) returns error indicating graphql API(localhost:8000/graphql) isn't accessible. I've tried to give storefront the same network that api is on but no luck. api is running inside docker container and storefront and api are on the same network so I have no guess why it can't find graphql api

I’ve seen someone trying to solve this issue by creating an .env file and
configuring the 8000/graphql in it. Others were trying by changing docker
config, hope you find a solution in the following link :
https://spectrum.chat/saleor/saleor-storefront/localhost-3000-not-working-on-initial-setup~7eb8da70-739b-40f7-b148-c80d08f121c5?authed=true
في ثلاثاء، ٦ يوليو، ٢٠٢١ في ٣:١٩ م، كتب Mehrdad Shokri <
@.***>:

@solafakhaled https://github.com/solafakhaled I've solved that for now.
But now storefront(localhost:3000) returns error indicating graphql
API(localhost:8000/graphql) isn't accessible. I've tried to give storefront
the same network that api is on but no luck. api is running inside docker
container and storefront and api are on the same network so I have no guess
why it can't find graphql api
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mirumee/saleor-storefront/issues/589#issuecomment-874710767,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALEXQNDQEZKQEVWLX2VNZ53TWLYEDANCNFSM4KOQSJCQ
.


[BUG] Hanging on SIGSEGV

Logging
Caught SIGSEGV
exec gdb failed: No such file or directory
Spinning.  Please run 'gdb gst-launch-1.0 8' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core.

Describe the bug
gstreamer is crashing and then hanging
To Reproduce
Happens occasionally after it's been running for a while and I don't have a specific reproducer yet
Expected behavior
It wouldn't crash, but at least if it did crash, then it wouldn't hang trying to start gdb
SDK version number
3.2.0
Platform (please complete the following information):

OS: Debian
Processor: x64
Version: Bullseye

Additional context
I think this might be related to #804

I doubt this is a related issue to the one mentioned. In this case, it's likely that your OS is failing to start the gdb due to memory pressures. Attempt to run the application under the gdb from the start in order to capture it. Alternatively, set your OS to capture the mini-dump so you can examine it later on a commodity platform instead of your device. As for the origin of the crash - unless you have a trace with the stack it would be impossible to trace.

It's running in a docker container and gdb isn't available, so I'll add it to see what info it can shed on this issue.

gdb is now inside of the docker container and this is the output that we see:
Caught SIGSEGV
Spinning.  Please run 'gdb gst-launch-1.0 7' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core.

Is there an ENV or flag we can set for it to do the core dump instead of spinning inside of gdb?

Any update on this? What can I do to help get this fixed?

Hi @daveisfera, it would be really difficult to investigate this without logs since we have not been able to reproduce it. Can you please share trace logs for this?

I'm looking to get it to at least not spin in gdb. How do I do that? It would be extra nice, if it would dump the stack trace and then exit, but for now, I'd take it just exiting rather than spinning and creating a zombie process.

Is there a way to make it not start gdb? Currently being stuck there is a much bigger problem than the crash itself, because the service would just restart and start working again, but being stuck in gdb incorrectly keeps it alive. Ideally, it gdb would dump the stack trace and exit, but I'll take it not starting or exiting immediately so things aren't totally stuck.

Any advice on this? I tried removing gdb to prevent it from spinning, but it still happens. This is the output when it happens:
Caught SIGSEGV
exec gdb failed: No such file or directory
Spinning.  Please run 'gdb gst-launch-1.0 8' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core.

There is not enough information for the team to assist you with. Please re-open the ticket with a stack trace, otherwise a reported crash in gstreamer with no steps to reproduce could be from any number of factors, even factors unrelated to the SDK.

How can I make it print a stacktrace when it happens?

I think I'm seeing the same thing here...
I'm running on an M1 pro mac using rancher desktop for docker incase that helps...

root@lima-rancher-desktop:/opt/amazon-kinesis-video-streams-producer-sdk-cpp/build# gst-launch-1.0 -v rtspsrc location=rtsp://localhost:8554/mystream short-header=TRUE ! rtph264depay ! h264parse ! kvssink stream-name=mystream storage-size=128 aws-region=eu-west-1 access-key=*** secret-key=***
Setting pipeline to PAUSED ...
[INFO ] [03-03-2023 15:39:39:445.813 GMT] createKinesisVideoClient(): Creating Kinesis Video Client
[INFO ] [03-03-2023 15:39:39:445.850 GMT] heapInitialize(): Initializing native heap with limit size 134217728, spill ratio 0% and flags 0x00000001
[INFO ] [03-03-2023 15:39:39:445.856 GMT] heapInitialize(): Creating AIV heap.
[INFO ] [03-03-2023 15:39:39:445.864 GMT] heapInitialize(): Heap is initialized OK
[DEBUG] [03-03-2023 15:39:39:445.948 GMT] getSecurityTokenHandler invoked
[DEBUG] [03-03-2023 15:39:39:445.956 GMT] Refreshing credentials. Force refreshing: 0 Now time is:<PHONE_NUMBER>445954854 Expiration: 0
[INFO ] [03-03-2023 15:39:39:445.964 GMT] createDeviceResultEvent(): Create device result event.
[DEBUG] [03-03-2023 15:39:39:445.974 GMT] clientReadyHandler invoked
[INFO ] [03-03-2023 15:39:39:445.994 GMT] try creating stream
[INFO ] [03-03-2023 15:39:39:446.023 GMT] Creating Kinesis Video Stream mystream
[INFO ] [03-03-2023 15:39:39:446.031 GMT] createKinesisVideoStream(): Creating Kinesis Video Stream.

[INFO ] [03-03-2023 15:39:39:853.670 GMT] writeHeaderCallback(): RequestId: 904b8eb1-f2e0-476d-a7b7-a0755a622b47
[DEBUG] [03-03-2023 15:39:39:854.397 GMT] getStreamingEndpointCurlHandler(): GetStreamingEndpoint API response: {"DataEndpoint":"https://s-5ac677c0.kinesisvideo.eu-west-1.amazonaws.com"}
[INFO ] [03-03-2023 15:39:39:859.535 GMT] getStreamingEndpointResultEvent(): Get streaming endpoint result event.
[DEBUG] [03-03-2023 15:39:39:860.403 GMT] getStreamingTokenHandler invoked
[DEBUG] [03-03-2023 15:39:39:860.473 GMT] Refreshing credentials. Force refreshing: 1 Now time is:<PHONE_NUMBER>860457105 Expiration:<PHONE_NUMBER>3709551615
[INFO ] [03-03-2023 15:39:39:860.574 GMT] getStreamingTokenResultEvent(): Get streaming token result event.
[DEBUG] [03-03-2023 15:39:39:860.686 GMT] streamReadyHandler invoked
Stream is ready
Pipeline is live and does not need PREROLL ...
Progress: (open) Opening Stream
Progress: (connect) Connecting to rtsp://localhost:8554/mystream
Progress: (open) Retrieving server options
Progress: (open) Retrieving media info
Progress: (request) SETUP stream 0
/GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstRtpBin:manager: latency = 2000
/GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstRtpBin:manager: ntp-sync = false
/GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstRtpBin:manager: rfc7273-sync = false
/GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstRtpBin:manager: ntp-time-source = NTP time based on realtime clock
/GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstRtpBin:manager: drop-on-latency = false
/GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstRtpBin:manager: max-rtcp-rtp-time-diff = 1000
/GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstRtpBin:manager: max-ts-offset-adjustment = 0
/GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstRtpBin:manager: buffer-mode = Slave receiver to sender clock
/GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstUDPSrc:udpsrc1: timeout =<PHONE_NUMBER>
/GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstUDPSrc:udpsrc1: caps = application/x-rtp, media=(string)audio, payload=(int)14, clock-rate=(int)90000, ssrc=(uint)2853391389
/GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstUDPSrc:udpsrc2: caps = application/x-rtcp
Progress: (request) SETUP stream 1
/GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstUDPSrc:udpsrc3: timeout =<PHONE_NUMBER>
/GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstUDPSrc:udpsrc3: caps = application/x-rtp, media=(string)video, payload=(int)97, clock-rate=(int)90000, encoding-name=(string)H264, packetization-mode=(string)1, sprop-parameter-sets=(string)"Z2QAKazKUB4AiflwEQAAAwABAAADADyPGDGW\,aOk7LIs\=", profile-level-id=(string)640029, ssrc=(uint)506171262
/GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstUDPSrc:udpsrc4: caps = application/x-rtcp
Progress: (open) Opened Stream
Setting pipeline to PLAYING ...
ERROR: pipeline doesn't want to play.

(gst-launch-1.0:17): GStreamer-CRITICAL **: 15:39:41.918: gst_message_parse_error: assertion 'GST_MESSAGE_TYPE (message) == GST_MESSAGE_ERROR' failed
Caught SIGSEGV
exec gdb failed: No such file or directory
Spinning.  Please run 'gdb gst-launch-1.0 17' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core.

@stephenhibbert, can you elaborate further on your setup? Are you trying to run an amd64 docker image on an arm64 system? I don't think that would work because the base architectures are different

Closing since this issue is stale. Feel free to open / reopen an issue

Definitely still an issue. Fixing the SIGSEGV would be nice, but really I'm just asking for a way to have it not hang forever waiting for user input. Is there a way to do that?

@stephenhibbert, can you elaborate further on your setup? Are you trying to run an amd64 docker image on an arm64 system? I don't think that would work because the base architectures are different

My setup is an arm64 M1 MacBook Pro. The Dockerfile is pasted in my original comment above - in summary the arm64 Ubuntu base image causes the SIGSEV. The amd64 image running on Rosetta works as expected. I would like to have the option to run on arm64 to enable Graviton or RPi support.

I see you mention multiple systems. I'm still not clear about your setup. What is your base system and which docker image are you trying to run on it? Are you able to reproduce this issue when using an Ubuntu image on an Ubuntu base system? Have you changed anything in the sample application?

Closing due to no response

For the benefit of future readers: the option to set is gst-launch-1.0 -f which disables the fault handler so it doesn't hang on GDB.
https://gstreamer.freedesktop.org/documentation/tools/gst-launch.html?gi-language=c


Intellisense in PyCharm does not work correctly with current code structure

Describe the bug
This only applies to commands. Code argument suggestions are all off by one, because self is considered to be an argument (which it shouldn't be). Additionally, should you Ctrl-click on a method, PyCharm takes you to the Commands class and you have to Ctrl-click again to get to the actual method. This isn't a huge issue but it hinders development.
I am not sure if this is PyCharm-exclusive or something experienced by other IDEs but I suspect it is not exclusive.

Hmm, I can't reproduce this issue. I downloaded the code from https://github.com/pyansys/pymapdl/tree/refactor/commands_to_classes and both argument suggestions and Ctrl-click work fine with mapdl.nplot() for me. Maybe the index-tree of PyCharm got messed up when you refactored the code? Its not working for e.g. mapdl.n()- but thats because the n-function has a parameter self while not being a class method.

... but with the (hopefully corect) code, I still can't reproduce the issues you mentioned. It might be due to the local pycharm index got messed up somehow during refactoring?

Argh, looks like I missunderstood this issue. The problem is with the current code, not with your pull request ^^? But thats not an issue of PyCharm - ctrl-click goes to the declaration of a label, what you want would be ctrl-Alt-Click (or ctrl-alt-B) which goes to the implementation (you could change that via Keymap->MainMenu->Navigate->Navigate in File ...). With your pull request both go to the same code position, thats why it "solves" the issue.

Unfortunately none of these solve the problem for me. Additionally, even if they did the argument documentation shifting wouldn't be fixed.

See here, self is highlighted as the first argument, which is incorrect, the first argument is npt. This is the case on all mapdl commands, all argument helpers are off by one.

Sorry I should clarify, I mean I tried Ctrl-Alt-Click and Ctrl-Alt-B and it just did the same thing as Ctrl-click. I haven't messed with the shortcuts in my PyCharm for this so I don't know how I'd get this to work.

Combining my comments into one coherent one:
Ctrl-Alt-Click and Ctrl-Alt-B do not take me to the method definition, they only go to the declaration exactly as Ctrl-click does and I should say I am using vanilla PyCharm for shortcuts.
Here is an additional image explaining the argument shifting more clearly:

self should not be highlighted as the first argument is npt.

Hmm, for me it goes to different code positions when using ctrl-click and or ctrl-alt-click (the latter gives me a context menu to choose).
The argument shift is something thats realy hard to catch (I think its a general problem not PyCharm alone), because if you would call e.g. Commands.n(0) the fist argument 0 would indead go to self. Its likely, that this would be fixed by changing class Commands and putting everthing in __init__(self) but your approach with seperate classes solves the issue too, so I guess thats all we need.

The ""more correct"" (more IDE-friendly? It all runs after all) way to do this is using inheritance like I do in the PR.

Imho its more pythonic at least, because right now we have functions with a self-parameter and its not clear what self in a function might be.

Agreed, it's more pythonic.  It wasn't clear what the self parameter was.  I'm going to merge.


Use public _registerService RPC in flutter_tools

Depends on this SDK CL. Will require a manual engine roll.

please ignore coverage failure


[Feature] support alluxio filesystem in paimon

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
alluxio is a data orchestration technology(https://docs.alluxio.io/os/user/stable/en/Overview.html),
we mainly use alluxio to speet up hot (hive/iceberg) tables which are frequenty accessed for lookup join or ad-hot query via trino.
similar to hdfs, we can create and  use paimon catalogs in alluxio,
alluxio releted configurations can be configured in hdfs core-site.xml or in catalog propreties
create catalog in flink:
CREATE CATALOG my_catalog WITH (
'type' = 'paimon',
'warehouse' = 'alluxio://path/to/warehouse'
);
USE CATALOG my_catalog;
then  wen can create/write to paimon tables in Flink/Spark, and read paimon tables  in Flink/Spark/Trino side
Solution
No response
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

Related PR: #797


import/export .pck files

Thanks for your wonderful program!
Do you have any plans to reverse .pck file format for Mafia 3 DE / Mafia DE?
This would be a very useful feature, since, unfortunately, several songs were cut in Mafia 3 DE, also many people would like to add classical music from original game to Mafia DE

pck export/import script (pck2.bms)
https://drive.google.com/file/d/113db_iZR_nI8soiNXQlprGH2KV_nT_77/view?usp=sharing

https://github.com/hpxro7/wwiseutil would be a good foundation i think

Wwise work has been merged, awaiting documentation and public release.


Create URL-parameters-2.md

A new snippet for getting all parameters ("key":"value") in an URL due to the old snippet not working.
Ref: #74
Here is the working proof:
https://jsfiddle.net/pl4gue/0g5vfjfz/5/

Please submit improvements and changes made to the original script. There should be no duplicates, unless they cover different use-cases. The current snippet is buggy, true, so we should figure out how to fix it.


remove outermost gob

...replacing it with length-prefix encoding.
Addresses part of #519.

Looks like it might end up with two identical lines in doIntroV1 and doIntroV2.

Ah, I see - they diverge again in the later commit, so no point in unifying them.

@dpw I have addressed all your feedback. Will squash the commits once you are happy.

That was all, squash away.

squash away

Done.


Possible to use pretrained models in quantization?

Hi,
Thanks for this. Is it possible to just use my own pretrained models for quantization?

Hi!
This is an implementation of this paper:
https://arxiv.org/abs/1612.01064.
Please read it to understand the code.
For now results are:
vanilla densenet: 48% accuracy,
quantized densenet: 40% accuracy.
Yes it is possible to use your own pretrained models.

You need to edit densenet_ternary_quantization/get_densenet.py
so it returns your pretrained model.
You need to edit utils/data_utils.py so it uses your dataset.
Then you need to use densenet_ternary_quantization/train.ipynb.

The main thing that you need to understand is densenet_ternary_quantization/utils.py.
It contains the main algorithm.
Please note that quantization may not work for your model.
For example, I tried also to quantize SqueezeNet but it didn't work.
Please let me know if you have any questions.

Thank you for the details. I will try with my model and see if it works

Hi , I made a few modifications and tried this using a custom model. Just wanted to ask, is this a normal out put especially my 2nd and 3rd outputs in all_losses?
0<PHONE_NUMBER>73841664.000<PHONE_NUMBER>9240.195  0.508 0.985  0.508 0.985  717.466
1<PHONE_NUMBER>592.859<PHONE_NUMBER>270.049  0.505 0.998  0.505 0.998  707.510
2<PHONE_NUMBER>30.435<PHONE_NUMBER>99.317  0.506 0.998  0.506 0.998  716.858
3<PHONE_NUMBER>05.375<PHONE_NUMBER>75.415  0.504 0.999  0.504 0.999  717.034
4<PHONE_NUMBER>50.184<PHONE_NUMBER>4.780  0.505 0.998  0.505 0.998  712.632
CPU times: user 1h 1min 10s, sys: 28min 18s, total: 1h 29min 29s
Wall time: 59min 31s

I believe you used it on a very easy dataset because val_accuracy is quite high.
It is not normal that 2nd and 3rd outputs are so high. Sometimes I get the same high losses.
It depends on hyperparameters you used. To solve this problem you need to tweak t and learning rates.
The size in MB of a quantized model will remain the same because weights are still stored as float32 values. But it will be much smaller if you store weights as 2-bit values and scaling factors.

Please understand that TTQ is an experimental method. It is not ready for production. It is a pure research. You need to try a lot of hyperparameters before it works.
Later, I will refactor the code so it will be easier to understand.

Yes, I actually took a pretrained vgg16 model from vision and performed transfer learning for the kaggle dogs_cats dataset so quite an easy dataset and got an accuracy of 0.97 so trying out the same finetuned model with the aim of reducing it's size using TTQ sort of improved the accuracy I guess.
Thank you for the suggestions .


replaceVars: init

Here's an attempt at making an easy-to-use variant of pkgs.substitute that suffers from none of the pitfalls of substituteAll. It's named replaceVars since this isn't the unrelated concept of Nix substitution.
Motivating transformation
From pkgs/applications/audio/curseradio/default.nix:
  patches = [
    (substituteAll {
      src = ./mpv.patch;
      inherit mpv;
    })
  ];

Into something like this, after nixfmt has its way:
  patches = [
    (replaceVars ./mpv.patch { inherit mpv; })
  ];

According to a quick grep, there's around 340 of these throughout the codebase, making up the majority of the roughly 430 uses of substituteAll.
Simple cases:

rg -A1 --no-heading --no-filename --no-line-number -tnix -F '(substituteAll {' | rg -F 'src = ./' | wc -l

All cases:

rg --no-heading --no-filename --no-line-number -tnix -F 'substituteAll {' | wc -l

Goals

Textually shorter than substituteAll for the majority case, where the thing being replaced lives in the repository rather that acquired through a fetcher or part of a more complicated substitution pipeline.
Uses --replace-fail exclusively. I think the ergonomics of normal-looking names in the .nix files makes me want to continue the name to @name@ substitution throughout the codebase.
Has a checkPhase: when there are remaining @...@ tokens in the output, will fail. This would be wrong for the general-purpose substitute function but net positive for the patch substitution use case. This is the main reason for wanting --replace-fail exclusively.
Has a name that reflects its main use case. The name I initially chose, substituteAttrs, didn't hit this mark. Perhaps replaceVars might.
Clean separation of derivation attrs and replacement attrs. The attrsets for the derivation itself and the attrset for the substitutions cannot be confused. This is the sin that substituteAll commits.

Description of changes

[x] Introduce replaceVars function.
[x] Test it

Things done

[x] Added tests in pkgs/test/replace-vars/default.nix (run with nix-build -A test.replaceVars)
[x] Fits CONTRIBUTING.md.

Has a name that reflects its main use case. The name I initially chose, substituteAttrs, didn't hit this mark. Perhaps substituteInPatch might.

I don't think it should be named for its main use case, but rather for what it does. It doesn't do anything specific to patching, so I don't think substituteInPatch is a good name, I'm in favor of keeping it as substituteAttrs.

What do you think about the name substituteInPatch or substituteInFile, both of which invite a file as the next parameter?

Actually substituteInFile seems decent, but then it couldn't support the use case of substituting files in an entire directory. Instead how about substituteInPath

Robert, I'm pretty set on the argument order (attrset last) and the semantics (name = value, where name in the source is @name@). They correspond the actual need and usecase in nixpkgs, and they're similar to other well-known functions like callPackage. Considering future additions other than maybe directories is, in my view, out of scope. My view: YAGNI.
On the other hand, I'm very open to other names than replaceInPath, especially if they help with the ill-at-ease feeling you have about name =><EMAIL_ADDRESS>What about replaceVarsInPath or replaceVarsByAttrs, following the name of --subst-var and --subst-var-by, both of which have the @name@ convention? Or replaceAllVarsInPath?

I don’t know if I like the name replaceInPath but I like that it is short and relatively snappy. “Use replaceAllVarsInPath, not substituteAll” feels like an unforced error in terms of “marketing”. Ideally we would somehow give it a name that is even nicer and more appealing than substituteAll. replaceVars?

the argument order (attrset last)

Whoops, didn't mean to relitigate this. I just find it natural to order positional arguments from least dynamic to most dynamic, and I consider the substitutions to be the more dynamic value.

My view: YAGNI.

We know we need all the functionality, because otherwise it wouldn't already exist in the bash functions.
The real question is how to turn all the functionality into nice interfaces.
I completely understand the need to scope things down, but by saying we won't need it, you're denying a clear need.
I'm probably just taking these five words too literally, but we wouldn't be doing any of this if words didn't matter.
Or maybe I missed something; is this part of a larger plan you have in mind?
Please take my comments with a grain of salt - I think you're more aware of the big picture here than I am.

FWIW I think having to write { variables = …; } would also be bad for user acceptance. Not that a more general interface would be bad to have, but we should have something simple for the common case of “script or patch that needs something parameterized”, and it’s okay to optimize for the common case even if we want to expose something more advanced too.

Fair enough then.
@emilazy makes a good point about "marketability", so if you could rename it to her suggestion replaceVars, that sounds good to me.
Sorry for my detour, but I think we're getting to a good place.

replaceVars?

I love replaceVars.

Without user facing docs (https://github.com/NixOS/nixpkgs/pull/301350#discussion_r1706246442) this may as well not exist :cry:

Without user facing docs (https://github.com/NixOS/nixpkgs/pull/301350#discussion_r1706246442) this may as well not exist :cry:

It needs some real life transformation experience. When I get back from camping I'm planning on doing a pass through nixpkgs on current substituteAll calls to see if it works or needs tweaks.
Then the marketing can ensue.

Awesome. Enjoy camping!

Docs are live on noogle at least: https://noogle.dev/f/pkgs/replaceVars

Things I've run into so far that might motivate a replaceVarsWith function:

isExecutable = true, so that the replacement has the executable bit set.
Exceptions for the check phase: if the replacements are done in two phases, that's a blocker.

I'm just skipping derivations that have these properties.

isExecutable = true, so that the replacement has the executable bit set.

What if we made the output have the same executable bit as the input?


use double instead of decimal128(38,9) to compute variance and stddev(#10425)

……
What type of PR is this：

[ ] bugfix
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

run starrocks_fe_unittest

run starrocks_fe_unittest


List view inside Expandable Linear Layout Not working

I have used a Expandable Linear Layout in recycler view and List view inside expandable layout but the list scroll isnt working and dynamic change of height has been a issue

@VinilChandra
I'm sorry for the delay fixed this issue.
This problem is fixed in #87.
But I don't check it in list view.


[Storage-Mover] az storage-mover endpoint create-for-storage-smb-file-share/create-for-smb: Add new endpoints for storage-smb-file-share and smb mount.

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Storage-Mover

/azp run

/azp run

Validation for Breaking Change Starting...
Thanks for your contribution!


Error Handling Preventing Script Termination

  File "/Applications/kindle2notion/kindle2notion.py", line 200, in <module>
    ch = KindleClippings(CLIPPINGS_FILE)
  File "/Applications/kindle2notion/kindle2notion.py", line 13, in __init__
    self.clippings = self._getAllClippings(clippingsFile)
  File "/Applications/kindle2notion/kindle2notion.py", line 18, in _getAllClippings
    return self._parseClippings(allClippings)
  File "/Applications/kindle2notion/kindle2notion.py", line 96, in _parseClippings
    self.addToNotion(lastClip)
  File "/Applications/kindle2notion/kindle2notion.py", line 185, in addToNotion
    title = "Page: " + lastClip['Page'] + "\tDate Added: " +  str(lastClip['Date Added'].strftime("%A, %d %B %Y %I:%M:%S %p"))
TypeError: can only concatenate str (not "NoneType") to str

Need error handling for such errors to prevent termination of script

Hi, this has been resolved in the latest commit. Retooled the program to prevent this error from happening and speed up the loading process.


"outE" and "outV" traversals don't work in "map" traversal

Edge travesal in map seems doesn't work:

Is this normal?
Originally posted by @NemoTR in https://github.com/joernio/joern/issues/1367#issuecomment-1120950693

@NemoTR Do you still need an answer for this?

@NemoTR Do you still need an answer for this?

No, thanks.


injecting code into rayon's thread startup and shutdown

I'm opening this issue because I'd like to explore the feasibility of being able to run code when a rayon thread starts and before it exits.
Background: We're using a Rayon thread pool to do parallel styling in the Stylo project.  As part of that work, we'd like to make Rayon threads profilable via the Gecko profiler so that work happening in the thread pool is visible to the profiler.  The profiler, for better or worse, will only profile threads that are explicitly registered with the profiler.
So, to make all of this come together, the threads Rayon creates need to be registered with the profiler.  And the best way that I can see of doing that is to have some sort of mechanism inside Rayon the provides a place where you can run code at thread startup or thread shutdown.  (You could register threads on-demand from the parallel styler, I think, but that would run into issues with potential thread-id re-use, and would add an undesirable amount of overhead to the styler.)
Is this a feasible thing to add?
cc @mstange @bholley

The simplest thing would probably be an API to run a function exactly once on each thread in the pool. But I suppose that might become problematic if the thread pool ever changes size dynamically.
I'll defer to @nikomatsakis on what he prefers here.

We might not need this if https://bugzilla.mozilla.org/show_bug.cgi?id=1341811 works out. But I don't know how feasible that one is.

I don't have a problem with having a fn that runs on thread startup -- would you also want one that runs on thread teardown?

I'm marking this as "help-wanted", as it seems like a relatively straightforward change. I think the basic gist of what I would do:

add a method to the Configuration type that stores a "execute on thread-start" closure, probably looking something like set_panic_handler
add code to the worker main loop to invoke this closure

we should invoke it using unwind::halt_unwinding and, if Err(e) is returned (i.e., if a panic occurs), invoke the panic handler from the configuration by calling registry.handle_panic(e)

@froydnj can you confirm whether you need something to run at thread teardown as well?

@bholley commented on Mar 6, 2017, 8:20 PM GMT+2:

@froydnj can you confirm whether you need something to run at thread teardown as well?

Is teardown somehow different from exiting? froydnj mentioned wanting to run code at start and at exit.

Yes, we'd need to run something both at the start and the end of the thread. These two functions, to be specific: http://searchfox.org/mozilla-central/rev/1bc7720a434af3c13b68b8d69f92078cae8890c4/tools/profiler/public/GeckoProfiler.h#268-271

Is teardown somehow different from exiting? froydnj mentioned wanting to run code at start and at exit.

At thread exit, yes.

The Stylo team is tracking the Gecko Profiler half of this work in Firefox bug 1322656.

So now that #271 landed, this is basically done, right? We just need to issue Rayon 0.7.

So now that #271 landed, this is basically done, right? We just need to issue Rayon 0.7.

That's correct.

Very good!


Within a Gamescope session, night mode is nonfunctional

Night mode works properly within Plasma, but has no effect in Gamescope Big Picture.

I suspect this is due to the name of the steam deck platform driver being different. SteamOS has it called jupiter or steamdeck_hwmon, and the one submitted upstream to the Linux kernel is just "steamdeck". Display controls are part of that driver.
We may need to rename the driver or build a patch for gamescope to use the name they gave upstream.

This may be resolved by 1386380a484adc44f1443148748491a853c25f3a

Closing this as a duplicate, it and https://github.com/ublue-os/bazzite/issues/62 are the same issue.

Hey there,
I'm currently working on an OS for the steam deck based on OpenSUSE. I face the same issue, does someone remeber what fixed it?


add support showing label for xAxis in LineChart

Description
Add ability to label xAxis in ChartView
LineView(
    data: [8,23,54,32,12,37,7,23,43],
    xAxisData: ["10-01-2013", "10-02-2013", "10-03-2013", "10-04-2013", "10-05-2013", "10-06-2013", "10-07-2013","10-08-2013","10-09-2013"], // New field
    title: "Line chart",
    legend: "Full screen"
)

Motivation and Context
In LineChart the data may contain not only yAxis but may contain xAxis that represents, for example, date of data
How Has This Been Tested?
Tested using examples project
Screenshots (if appropriate):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (Updating Documentation, CI automation, etc..)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Any chance that this PR would be merged ?

We are also in the process of selecting chart libraries and this is one of the libraries we are considering. I could not find a way to format xAxis labels (eg: date) and I find this PR probably aims to solve the issue. Can you guys confirm if there is a way to format xAxis labels or this PR is the way to go?


Custom navigation fail with more than one swiper in page

Check that this is really a bug

[X] I confirm

Reproduction link
https://codesandbox.io/s/swiper-navigation-react-forked-j7yyn0?file=/src/App.jsx
Bug description
When there are more than one Swiper component in the same page, each custom navigation elements trigger all carousel.
Even with different css selector.
Bug doesn't affect default navigation (nagivation={true})
Expected Behavior
No response
Actual Behavior
No response
Swiper version
8.0.7
Platform/Target and Browser Versions
Linux Ubuntu - Chrome 99
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

Ok I found a fix: move the custom element next/prev into  component.
(example in codesandbox updated)


Add CanceledOr

This will be used as a return type for symbol loading function that can
be cancelled.
Bug: part of http://b/202140068

Force push was necessary to resolve merge conflicts


Mexican Spanish Translation

A complete translation, in comparison with the other Spain spanish translation, it has all of the missing translation, fixes some weird translation and is more neutral

Thank you for translating the mod.


poetry not able to install psycopg2 dependency

@deanchanter thanks for flagging, can you try again with semantic-router==0.0.58 — we pushed what should be a fix with v0.0.58

Works!


Gitea hangs when starting

Gitea version (or commit ref): Gitea version 1.9.0+dev-314-g8eba27c79 built with GNU Make 4.2.1, go1.12.5 : bindata, sqlite, sqlite_unlock_notify
Git version: Shipped with the docker image
Operating system: Shipped with the docker image
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist: See below

Description
$ docker run --rm --name gitea -p 5000:3000 -v /home/gitea:/data gitea/gitea:latest
Server listening on :: port 22.
Server listening on <IP_ADDRESS> port 22.
2019/06/02 09:38:28 ...dules/setting/git.go:83:newGit() [I] Git Version: 2.20.1, Wire Protocol Version 2 Enabled
2019/06/02 09:38:28 routers/init.go:69:GlobalInit() [T] AppPath: /usr/local/bin/gitea
2019/06/02 09:38:28 routers/init.go:70:GlobalInit() [T] AppWorkPath: /usr/local/bin
2019/06/02 09:38:28 routers/init.go:71:GlobalInit() [T] Custom path: /data/gitea
2019/06/02 09:38:28 routers/init.go:72:GlobalInit() [T] Log path: /data/gitea/log

Then gitea hangs. Port 3000 is not listened in the container (docker exec gitea netstat -nltp). Waited hours but nothing happened. No error logs are produced.
A fresh installation (mounting an empty dir to /data) runs properly. My database is migrated from gogs, and it keeps working in gitea until yesterday. So I guess the problem might on the database. I tried the following:
$ docker run --rm --name gitea --user git -p 5000:3000 -v /home/gitea:/data gitea/gitea:latest gitea migrate
2019/06/02 09:45:50 ...dules/setting/git.go:83:newGit() [I] Git Version: 2.20.1, Wire Protocol Version 2 Enabled
2019/06/02 09:45:50 cmd/migrate.go:29:runMigrate() [T] AppPath: /usr/local/bin/gitea
2019/06/02 09:45:50 cmd/migrate.go:30:runMigrate() [T] AppWorkPath: /usr/local/bin
2019/06/02 09:45:50 cmd/migrate.go:31:runMigrate() [T] Custom path: /data/gitea
2019/06/02 09:45:50 cmd/migrate.go:32:runMigrate() [T] Log path: /data/gitea/log
2019/06/02 09:45:50 ...-xorm/xorm/engine.go:325:Ping() [I] PING DATABASE mysql
2019/06/02 09:45:52 .../xorm/session_raw.go:143:queryBytes() [I] [SQL] SELECT `TABLE_NAME` from `INFORMATION_SCHEMA`.`TABLES` WHERE `TABLE_SCHEMA`=? and `TABLE_NAME`=? []interface {}{"gitea", "version"}
2019/06/02 09:45:55 ...xorm/core/dialect.go:157:HasRecords() [I] [SQL] SELECT `COLUMN_NAME` FROM `INFORMATION_SCHEMA`.`COLUMNS` WHERE `TABLE_SCHEMA` = ? AND `TABLE_NAME` = ? AND `COLUMN_NAME` = ? [gitea version id]
2019/06/02 09:45:57 ...xorm/core/dialect.go:157:HasRecords() [I] [SQL] SELECT `COLUMN_NAME` FROM `INFORMATION_SCHEMA`.`COLUMNS` WHERE `TABLE_SCHEMA` = ? AND `TABLE_NAME` = ? AND `COLUMN_NAME` = ? [gitea version version]
2019/06/02 09:46:03 .../xorm/session_get.go:95:nocacheGet() [I] [SQL] SELECT `id`, `version` FROM `version` WHERE `id`=? LIMIT 1 []interface {}{1}
2019/06/02 09:46:06 ...ations/migrations.go:269:Migrate() [I] Migration[83]: add uploader id for table attachment
2019/06/02 09:46:06 ...orm/dialect_mysql.go:434:GetTables() [I] [SQL] SELECT `TABLE_NAME`, `ENGINE`, `TABLE_ROWS`, `AUTO_INCREMENT`, `TABLE_COMMENT` from `INFORMATION_SCHEMA`.`TABLES` WHERE `TABLE_SCHEMA`=? AND (`ENGINE`='MyISAM' OR `ENGINE` = 'InnoDB' OR `ENGINE` = 'TokuDB') [gitea]

Then it hangs too.
How I can dive deeper to check where the problem is produced? I've set log level to debug but there's still no logs containing useful information.

I've figured out that the problem is caused by insufficent network configurations, which add a huge latency to the connections from gitea to database. The issue has nothing concerning gitea. Sorry for disturbing.


WIP Customer display

@alexlevy0 You are pros! thanks for adding the extra functionality and for tidying up!... drop me an email if you want to chat more about this project!


Clarifies numbers on network status

The text of the Network status graphs is rather unclear as to what numbers are what (see picture below), this PR clarifies that.

Merging in favour of #126


RequestInterceptor converts GET to POST when adding headers

I'm using FeignClient to call service and a RequestInterceptor to add a header, no body change, but it still convert GET to POST. Is there an alternative way to fix this other than using httpclient as backend of Feign?
@FeignClient(name = "admin", url = "${feign.client.config.admin.url:}")
public interface AdminService {
    @RequestMapping(value = "/api/users/{username:.+}", method = RequestMethod.GET)
    User getUser(@PathVariable("username") String username, @RequestParam("appName") String appName);
}

@Bean
public RequestInterceptor requestInterceptor() {
    return requestTemplate -> {
        RequestAttributes requestAttributes = RequestContextHolder.getRequestAttributes();
        HttpServletRequest servletRequest = ((ServletRequestAttributes) requestAttributes).getRequest();
        String auth = servletRequest.getHeader("Authorization");

        if (StringUtils.isNotBlank(auth)) {
            requestTemplate.header("Authorization", servletRequest.getHeader("Authorization"));
        }
    };
}

After debugging and I found that it puts my "@PathVariable String username" into body which seems the reason of this happening.

I think this may duplicate #123

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Promote "Retriable and non-retriable pod failures for Jobs" to Beta

/ok-to-test

/retest

Do we need to change min-kubernetes-server-version in content/en/docs/tasks/job/pod-failure-policy.md?

I think the  min-kubernetes-server-version should stay as is, because 1.25 is the version in which this feature was introduced. In particular this tutorial would work both on 1.25 and 1.26. However, I updated the FEATURE STATE to 1.26 and beta.

I typically add some wording saying that if you're running an older version of Kubernetes, to switch to the docs for that version.

Where would be the appropriate place to mention that? Could you maybe point to an example?
Also, there are two main differences between 1.25 and 1.26:

there is a bug in 1.25: https://github.com/kubernetes/kubernetes/pull/112518
TerminationByKubelet is added in 1.26
Where do you think would be the right place to mention the diffrerences?

Do we need to change min-kubernetes-server-version in content/en/docs/tasks/job/pod-failure-policy.md?

Added a not the disruptions.md to refer to the older version of the docs for older versions of k8s. Please take a look.

/assign @bobbypage
could you please provide a technical review for the doc update from sig-node POV?

LGTM for SIG Docs.
Tech review LGTM needed from SIG Node.

@sftim The PR is now lgtm-ed by Sergey from SIG-Node.

Preview of updated pages:

https://deploy-preview-37242--kubernetes-io-vnext-staging.netlify.app/docs/concepts/workloads/controllers/job/
https://deploy-preview-37242--kubernetes-io-vnext-staging.netlify.app/docs/concepts/workloads/pods/disruptions/
https://deploy-preview-37242--kubernetes-io-vnext-staging.netlify.app/docs/reference/command-line-tools-reference/feature-gates/
https://deploy-preview-37242--kubernetes-io-vnext-staging.netlify.app/docs/tasks/job/pod-failure-policy/

/approve


Deployment commit for prod-beta

Merged stage-stable branch to prod-beta.
Use latest commit to update namespace ref in app-interface repo. Don't use merge commit, SHAs must be unique when images are created for each branch.

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

Project coverage is 70.00%. Comparing base (717691b) to head (152854f).

Additional details and impacted files
@@            Coverage Diff             @@
##           prod-beta     #360   +/-   ##
==========================================
  Coverage      70.00%   70.00%
==========================================
  Files             81       81
  Lines           1080     1080
  Branches         216      246   +30
==========================================
  Hits             756      756
+ Misses           324      313   -11
- Partials           0       11   +11

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


Bug with "residue_index" attribute

There are two bugs with the "residue_index" attributes:

it should be a long tensor, but it's a float tensor
PyG automatically increment attributes ending with an "index" by the number of nodes in the previous graphs in a batch. However, residue_index indicates the absolute positions of residues in each graph and should be affected by other graphs in the batch. A simple remedy could be rename it with "residue_idx" or "residue_position".

it's now "residue_number"


Error 401

Since today unlocking Bold is not working anymore for me.
I deleted my account and generated a new code but that didn’t help either.
Error log:
Error (401) while activating device (5324): Authentication is possible but has failed or not yet been provided.

I will look into it tomorrow when I have time. In the mean time I think you can restart the authentication process to fix it for now.

Didn’t read your message properly, recreating the login didn’t work, I’ll look into it soon.

The problem was caused by a change in the Bold API, which is internal (sort of), which means they don't warn me of breaking changes. This has been resolved in v1.0.11.
I will reach out to Bold to see if this plugin can get official API access, so that we can avoid stuff like this.

I just installed the new version however I still get the same message. Even after generating a new authentication code. Do I do something wrong?

I might've accidentally swapped tokens while testing, but version v1.0.12 should really fix this.

I've experienced the same problem since yesterday. v1.0.11 and v1.0.12 have both given the same issue.

Unfortunately still the same issue with 1.0.12.

Could you try logging in using this? https://stefannienhuis.github.io/homebridge-bold/

Could you try logging in using this? https://stefannienhuis.github.io/homebridge-bold/

I can login using that site and I also get an authentication code.

It works again! Thanks!

Thank you!


The deleted share snapshots do not auto disappear when deleting more than one share snapshot at one time

Storage Explorer Version: 1.26.0-dev
Build Number: 20220909.2
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Monterey 12.5 (Apple M1 Pro)
Architecture ia32\x64
How Found: From running test cases
Regression From: Previous release (1.25.1)
Steps to Reproduce

Expand one storage account -> File Shares.
Select one file share -> Create two snapshots for the file share.
Open the file share -> Click 'View Share Snapshots'.
Click 'Select All' -> Click 'Delete' -> Click 'Yes' on the prompt dialog.
There is a successful activity log.
Check whether the deleted snapshots auto disappear.

Expected Experience
The deleted snapshots auto disappear.
Actual Experience
The deleted snapshots do not auto disappear.
Additional Context

This issue doesn't reproduce when deleting only one share snapshot.
The deleted snapshots disappear after manually refreshing.
There is no refresh prompt when deleting share snapshots with the setting 'Auto-refresh on change' unchecked.

Verified this issue on the build main/20220914.3. Fixed. So, we are going to close it.


DayPlanner outline within a callout

At the moment the outline of the daily plan is only possible underneath a specific heading in a note. It would be wonderful if that would also be possible in a specific collapsable callout. Especially if you have visually structured your daily note with multiple callouts.

Hello, @ThomasMathoi, please update and re-check.

Oh, WOW! I will update as soon as it is available - at the moment I can't get the update :-(


Add the Consumption of an External Service to Your CAP Application

Tutorials: https://developers.sap.com/tutorials/btp-app-ext-service-add-consumption.html
It would be really helpfull to try a deep insert or the CRUD for external service, al of the tutorials are simple doing the get o READ.
kind regards,
Cesar

Hi Cesar,
Thank you for the feedback. These use cases are simple but these particular tutorials have been deprecated. I have noted your feedback and I am passing it on for use in other enablement materials, this tutorial however cannot be updated. For the documentation on this topic you can check here. If you have more information that you would like to add such as, what you're trying to achieve or what is not covered in the documentation, then that would be helpful and I can add that to the feedback.
Best regards,
Mahati

Hi Mahati,
Thanks for the feedback, when do you plan tu update this deprecated tutorial?
Regarding the topic you shared I did use it, but there are missing details, for example how should the destination in BTP should be created to avoid the 403 Forbidden because of x-csrf-token.
I'm having that issue right now. The other issue is that since cds version 8.3 they have created a validation.js and now the deep insert, here is the community forum link
kind regards,
Cesar

@binpath Thank you for the details, I'll check and update the topic.

Hi Cesar,
I see that the topic already includes information to create destinations on SAP BTP. For bugs like the one you linked will have to be fixed by development teams.
Best regards,
Mahati

@smahati did you want to close this issue?

@smahati Thanks for your feedback!
Regarding the destination, I saw the link, the problem basically is the "Manually create destinations" where it doesn't specify in detail the use case based on additional parameters if needed for the x-csrf-token. I guess is not needed.
Thanks you very much I know that the CAP team on the developer side should fix it. Never the less the "Delegate requests to external services" section in this tutorial needs adjustment, for update and delete. It would be nicely appreciated and easier for the CRUD example.
kind regards,
Cesar


Restore the reputation penalty for timeouts

The reputation penalty for timing out a block request was accidentally removed. This restores it.
This should hopefully prevent the PSM from connecting again to the same node we just had a timeout with.

bot merge

(I have no idea whether the bot is enabled)

enabled yes, running no.


Write a readme

A readme file is pretty valuable when someone is trying to get a brief understanding of what an app might do, or what technologies that it might use. This information is pretty important if you want contributors to your project, or, more importantly, want people to see what your app actually does.
Some suggestions for this:

Write a description of what your project does
Take some screenshots of your project in action
Briefly talk about what technologies you used
Set up a protocol people can use to contribute

This is a valuable project, and I think with a good Readme it will get more exposure

This*1,000,000

I'll update the readme soon


Fix issues with translation deployment script

Summary
During the 0.25.1/0.44.1 release the translation publishing step failed. This was because of a parsing error with the ssh private key during the decryption step. This seems to be due to how the action was configured to load the private key post decryption into an env variable that github actions would then use for it's checkout action to handle cloning with authentication via ssh. This commit switches back to just using a standalone bash script that has proven to be reliable historically and also gives us tighter control on how commands get executed. As part of this a new encrypted private key is added to the repo as the previous key has been revoked and invalidated since the job failure during the release.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.02%) to 87.267%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/expr.rs
1
93.76%

crates/qasm2/src/lex.rs
4
91.14%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
74360

Relevant Lines:
85210

💛  - Coveralls


Getting error Missing attribute value for attribute runUser of element TestRun in Docker container

When run locally it works fine. The .trx file is created where I expect it to.
The same tests run in docker causes the error
Missing attribute value for attribute runUser of element TestRun

So the locally created trx file is fine?

It could be caused by the docker image you use does not set any of the values we check when determining the user, see https://github.com/no23reason/jest-trx-results-processor/blob/master/src/utils.ts#L59

It could be caused by the docker image you use does not set any of the values we check when determining the user, see https://github.com/no23reason/jest-trx-results-processor/blob/master/src/utils.ts#L59

Yup this is the issue. I found that bit going through my error logs.
Shouldn't it set the user to 'anonymous' or something if a user name isn't found instead of throwing an error?

We can make that change, sure :) PR would be welcome, otherwise I'll look into it when I have the time

:tada: This issue has been resolved in version 0.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


kubernetes-dashboard-certs created with no data

I'm following this tutorial:
https://ubuntu.com/tutorials/install-a-local-kubernetes-with-microk8s#2-deploying-microk8s
So far, I installed the snap, and enable dns and dashboard addons.
When I try to access the dashboard throw the web browser, I get an error about Invalid Certificate, but not because it's self signed, but because it's absolutely empty.
$ microk8s.kubectl describe secret/kubernetes-dashboard-certs -n kube-system

Name:         kubernetes-dashboard-certs
Namespace:    kube-system
Labels:       k8s-app=kubernetes-dashboard
Annotations:
Type:         Opaque

Data
====

inspection-report-20200206_160734.tar.gz
Not sure if this is a bug, or I'm doing something wrong in the setup. Thanks

Hi @schoren
This has been reported in the upstream kubernetes dashboard project and based on discussion at https://github.com/kubernetes/dashboard/issues/4684#issuecomment-567276867 it is like this by design.
Feel free to reopen this issue if you would like us to further investigate and/or imporve the user experience.
Thanks.