Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1
value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3
values | title stringlengths 1 1k | labels stringlengths 4 1.38k | body stringlengths 1 262k | index stringclasses 16
values | text_combine stringlengths 96 262k | label stringclasses 2
values | text stringlengths 96 252k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
243,728 | 7,861,219,645 | IssuesEvent | 2018-06-21 23:05:18 | hassio-addons/addon-tasmoadmin | https://api.github.com/repos/hassio-addons/addon-tasmoadmin | closed | Rename SonWEB to TasmoAdmin | Accepted Closed: Done Priority: High Type: Maintaince | Hai @frenck
SonWeb has been renamed to TasmoAdmin.
Also the SelfUpdate feature is going to be disabled a little different from your proposal (see https://github.com/reloxx13/TasmoAdmin/issues/105)
Also new releases will be pushed to https://github.com/reloxx13/TasmoAdmin/releases where .tar.gz or .zip can be used to update the hassio addon.
Greets,
Ray | 1.0 | Rename SonWEB to TasmoAdmin - Hai @frenck
SonWeb has been renamed to TasmoAdmin.
Also the SelfUpdate feature is going to be disabled a little different from your proposal (see https://github.com/reloxx13/TasmoAdmin/issues/105)
Also new releases will be pushed to https://github.com/reloxx13/TasmoAdmin/releases where .tar.gz or .zip can be used to update the hassio addon.
Greets,
Ray | priority | rename sonweb to tasmoadmin hai frenck sonweb has been renamed to tasmoadmin also the selfupdate feature is going to be disabled a little different from your proposal see also new releases will be pushed to where tar gz or zip can be used to update the hassio addon greets ray | 1 |
41,061 | 2,868,969,699 | IssuesEvent | 2015-06-05 22:16:48 | dart-lang/pub | https://api.github.com/repos/dart-lang/pub | opened | Pub's version resolution goes exponential on a simple pubspec | bug Priority-Medium Started | <a href="https://github.com/nex3"><img src="https://avatars.githubusercontent.com/u/188?v=3" align="left" width="96" height="96"hspace="10"></img></a> **Issue by [nex3](https://github.com/nex3)**
_Originally opened as dart-lang/sdk#16961_
----
The following pubspec causes pub's version resolution to go exponential:
name: app
dependencies:
intl: 0.9.0
polymer: "<=0.9.5"
This happens as of 1.2.0-edge.32615; the exponential churn involves pub's barback constraint, so it may change in future versions. The same pattern should persist, though.
This is caused by a conflicting constraint (intl and recent stack_trace versions have disjoint constraints on path), and compounded by the fact that pub tries to backtrack through every archived version of polymer. We may be able to mitigate this behavior by more aggressively checking for disjoint constraints; we may not be able to avoid checking all older polymer versions, but we can quickly discard them by noticing that their barback constraint is disjoint with pub's. | 1.0 | Pub's version resolution goes exponential on a simple pubspec - <a href="https://github.com/nex3"><img src="https://avatars.githubusercontent.com/u/188?v=3" align="left" width="96" height="96"hspace="10"></img></a> **Issue by [nex3](https://github.com/nex3)**
_Originally opened as dart-lang/sdk#16961_
----
The following pubspec causes pub's version resolution to go exponential:
name: app
dependencies:
intl: 0.9.0
polymer: "<=0.9.5"
This happens as of 1.2.0-edge.32615; the exponential churn involves pub's barback constraint, so it may change in future versions. The same pattern should persist, though.
This is caused by a conflicting constraint (intl and recent stack_trace versions have disjoint constraints on path), and compounded by the fact that pub tries to backtrack through every archived version of polymer. We may be able to mitigate this behavior by more aggressively checking for disjoint constraints; we may not be able to avoid checking all older polymer versions, but we can quickly discard them by noticing that their barback constraint is disjoint with pub's. | priority | pub s version resolution goes exponential on a simple pubspec issue by originally opened as dart lang sdk the following pubspec causes pub s version resolution to go exponential nbsp nbsp name app nbsp nbsp dependencies nbsp nbsp nbsp nbsp intl nbsp nbsp nbsp nbsp polymer quot lt quot this happens as of edge the exponential churn involves pub s barback constraint so it may change in future versions the same pattern should persist though this is caused by a conflicting constraint intl and recent stack trace versions have disjoint constraints on path and compounded by the fact that pub tries to backtrack through every archived version of polymer we may be able to mitigate this behavior by more aggressively checking for disjoint constraints we may not be able to avoid checking all older polymer versions but we can quickly discard them by noticing that their barback constraint is disjoint with pub s | 1 |
70,776 | 30,733,679,214 | IssuesEvent | 2023-07-28 05:27:39 | MicrosoftDocs/azure-docs | https://api.github.com/repos/MicrosoftDocs/azure-docs | closed | Value should be true in CLI example | Change sent to author triaged cxp doc-enhancement Pri1 azure-kubernetes-service/svc |
The Azure CLI command after the line "Use the Azure portal or Azure CLI to verify Azure AD integration with Kubernetes RBAC is enabled." seems to be having a wrong value. If it's enabled, the output shows the value for enableAzureRbac is 'false' --> should be If it's enabled, the output shows the value for enableAzureRbac is 'true'.
Kind regards
Anton
---
#### Document Details
⚠ *Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.*
* ID: 84495e76-eca6-ddc9-989f-01c844aaa29d
* Version Independent ID: de2a46f6-59c7-f4bd-c409-ea8d04741a6d
* Content: [Use Azure AD and Kubernetes RBAC for clusters - Azure Kubernetes Service](https://learn.microsoft.com/en-us/azure/aks/azure-ad-rbac?tabs=portal)
* Content Source: [articles/aks/azure-ad-rbac.md](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/aks/azure-ad-rbac.md)
* Service: **azure-kubernetes-service**
* GitHub Login: @MGoedtel
* Microsoft Alias: **magoedte** | 1.0 | Value should be true in CLI example -
The Azure CLI command after the line "Use the Azure portal or Azure CLI to verify Azure AD integration with Kubernetes RBAC is enabled." seems to be having a wrong value. If it's enabled, the output shows the value for enableAzureRbac is 'false' --> should be If it's enabled, the output shows the value for enableAzureRbac is 'true'.
Kind regards
Anton
---
#### Document Details
⚠ *Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.*
* ID: 84495e76-eca6-ddc9-989f-01c844aaa29d
* Version Independent ID: de2a46f6-59c7-f4bd-c409-ea8d04741a6d
* Content: [Use Azure AD and Kubernetes RBAC for clusters - Azure Kubernetes Service](https://learn.microsoft.com/en-us/azure/aks/azure-ad-rbac?tabs=portal)
* Content Source: [articles/aks/azure-ad-rbac.md](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/aks/azure-ad-rbac.md)
* Service: **azure-kubernetes-service**
* GitHub Login: @MGoedtel
* Microsoft Alias: **magoedte** | non_priority | value should be true in cli example the azure cli command after the line use the azure portal or azure cli to verify azure ad integration with kubernetes rbac is enabled seems to be having a wrong value if it s enabled the output shows the value for enableazurerbac is false should be if it s enabled the output shows the value for enableazurerbac is true kind regards anton document details ⚠ do not edit this section it is required for learn microsoft com ➟ github issue linking id version independent id content content source service azure kubernetes service github login mgoedtel microsoft alias magoedte | 0 |
88,928 | 11,172,228,790 | IssuesEvent | 2019-12-29 03:55:11 | AtomLinter/atomlinter.github.io | https://api.github.com/repos/AtomLinter/atomlinter.github.io | closed | Cards | design | The current version of the page occupies by default the whole width of the page, making the cards too wide to scan through and leaving too much space between them.
I managed to reduce the width of the cards without squeezing them too tight, and you can refer to this screenshot:
I wanted to change the background color of the page to light gray since white cards with drop shadows does not look good on the white background, but a gray background does not cope well with the beige banner. I am still working on that, and I shall come with some other solutions later.
If you are happy with this, I can just put this on.
| 1.0 | Cards - The current version of the page occupies by default the whole width of the page, making the cards too wide to scan through and leaving too much space between them.
I managed to reduce the width of the cards without squeezing them too tight, and you can refer to this screenshot:
I wanted to change the background color of the page to light gray since white cards with drop shadows does not look good on the white background, but a gray background does not cope well with the beige banner. I am still working on that, and I shall come with some other solutions later.
If you are happy with this, I can just put this on.
| non_priority | cards the current version of the page occupies by default the whole width of the page making the cards too wide to scan through and leaving too much space between them i managed to reduce the width of the cards without squeezing them too tight and you can refer to this screenshot i wanted to change the background color of the page to light gray since white cards with drop shadows does not look good on the white background but a gray background does not cope well with the beige banner i am still working on that and i shall come with some other solutions later if you are happy with this i can just put this on | 0 |
85,707 | 3,697,651,919 | IssuesEvent | 2016-02-27 20:28:34 | kubernetes/kubernetes | https://api.github.com/repos/kubernetes/kubernetes | reopened | e2e flake: ConfigMap updates should be reflected in volume timed out | kind/flake priority/P0 team/control-plane team/node | Test logs at https://console.cloud.google.com/storage/browser/kubernetes-jenkins/pr-logs/pull/21110/kubernetes-pull-build-test-e2e-gce/28558/
```
------------------------------
[BeforeEach] ConfigMap
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework.go:82
STEP: Creating a kubernetes client
Feb 14 22:27:25.162: INFO: >>> testContext.KubeConfig: /var/lib/jenkins/workspace/kubernetes-pull-build-test-e2e-gce/.kube/config
STEP: Building a namespace api object
Feb 14 22:27:25.348: INFO: Waiting up to 2m0s for service account default to be provisioned in ns e2e-tests-configmap-iibco
Feb 14 22:27:25.359: INFO: Get service account default in ns e2e-tests-configmap-iibco failed, ignoring for 2s: serviceaccounts "default" not found
Feb 14 22:27:27.362: INFO: Service account default in ns e2e-tests-configmap-iibco with secrets found. (2.013966058s)
STEP: Waiting for a default service account to be provisioned in namespace
Feb 14 22:27:27.362: INFO: Waiting up to 2m0s for service account default to be provisioned in ns e2e-tests-configmap-iibco
Feb 14 22:27:27.364: INFO: Service account default in ns e2e-tests-configmap-iibco with secrets found. (2.152421ms)
[It] updates should be reflected in volume [Conformance]
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/configmap.go:271
STEP: Creating configMap with name configmap-test-upd-2edc0b4e-d3ad-11e5-8393-42010af00003
STEP: Creating the pod
Feb 14 22:27:27.372: INFO: Waiting up to 5m0s for pod pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003 status to be running
Feb 14 22:27:27.380: INFO: Waiting for pod pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003 in namespace 'e2e-tests-configmap-iibco' status to be 'running'(found phase: "Pending", readiness: false) (7.523359ms elapsed)
Feb 14 22:27:29.383: INFO: Waiting for pod pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003 in namespace 'e2e-tests-configmap-iibco' status to be 'running'(found phase: "Pending", readiness: false) (2.010728843s elapsed)
Feb 14 22:27:31.388: INFO: Found pod 'pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003' on node 'e2e-gce-builder-2-0-minion-64es'
STEP: Updating configmap configmap-test-upd-2edc0b4e-d3ad-11e5-8393-42010af00003
STEP: Deleting the pod
STEP: Cleaning up the configMap
[AfterEach] ConfigMap
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework.go:83
STEP: Collecting events from namespace "e2e-tests-configmap-iibco".
Feb 14 22:29:01.583: INFO: event for pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003: {default-scheduler } Scheduled: Successfully assigned pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003 to e2e-gce-builder-2-0-minion-64es
Feb 14 22:29:01.583: INFO: event for pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003: {kubelet e2e-gce-builder-2-0-minion-64es} Pulling: pulling image "gcr.io/google_containers/mounttest:0.6"
Feb 14 22:29:01.583: INFO: event for pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003: {kubelet e2e-gce-builder-2-0-minion-64es} Pulled: Successfully pulled image "gcr.io/google_containers/mounttest:0.6"
Feb 14 22:29:01.583: INFO: event for pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003: {kubelet e2e-gce-builder-2-0-minion-64es} Created: Created container with docker id d6dce9ce8aa8
Feb 14 22:29:01.583: INFO: event for pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003: {kubelet e2e-gce-builder-2-0-minion-64es} Started: Started container with docker id d6dce9ce8aa8
Feb 14 22:29:01.651: INFO: POD NODE PHASE GRACE CONDITIONS
Feb 14 22:29:01.651: INFO: downwardapi-volume-3516c9fc-d3ad-11e5-b7b8-42010af00003 e2e-gce-builder-2-0-minion-64es Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:39 -0800 PST }]
Feb 14 22:29:01.651: INFO: foo-yswqv e2e-gce-builder-2-0-minion-qlb8 Running 30s [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:28:59 -0800 PST }]
Feb 14 22:29:01.651: INFO: update-demo-kitten-15bfi e2e-gce-builder-2-0-minion-s2tm Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:28:46 -0800 PST }]
Feb 14 22:29:01.651: INFO: update-demo-kitten-cr05m e2e-gce-builder-2-0-minion-qlb8 Pending [{Ready False 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:29:01 -0800 PST ContainersNotReady containers with unready status: [update-demo]}]
Feb 14 22:29:01.651: INFO: nginx e2e-gce-builder-2-0-minion-43a8 Running [{Ready False 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:28:56 -0800 PST ContainersNotReady containers with unready status: [nginx]}]
Feb 14 22:29:01.651: INFO: update-demo-nautilus-q2jms e2e-gce-builder-2-0-minion-qlb8 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:28:58 -0800 PST }]
Feb 14 22:29:01.651: INFO: update-demo-nautilus-vn45c e2e-gce-builder-2-0-minion-bo4h Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:28:58 -0800 PST }]
Feb 14 22:29:01.651: INFO: liveness-exec e2e-gce-builder-2-0-minion-qlb8 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:29 -0800 PST }]
Feb 14 22:29:01.651: INFO: liveness-http e2e-gce-builder-2-0-minion-64es Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:41 -0800 PST }]
Feb 14 22:29:01.651: INFO: proxy-service-n6w5j-exzdq e2e-gce-builder-2-0-minion-bo4h Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:35 -0800 PST }]
Feb 14 22:29:01.651: INFO: mutability-test-pyldw e2e-gce-builder-2-0-minion-lloc Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:28:05 -0800 PST }]
Feb 14 22:29:01.651: INFO: mutability-test-94yvp e2e-gce-builder-2-0-minion-64es Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:55 -0800 PST }]
Feb 14 22:29:01.651: INFO: elasticsearch-logging-v1-8a3oc e2e-gce-builder-2-0-minion-s2tm Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:21 -0800 PST }]
Feb 14 22:29:01.651: INFO: elasticsearch-logging-v1-xhinl e2e-gce-builder-2-0-minion-qlb8 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:06 -0800 PST }]
Feb 14 22:29:01.651: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-43a8 e2e-gce-builder-2-0-minion-43a8 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:55 -0800 PST }]
Feb 14 22:29:01.651: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-64es e2e-gce-builder-2-0-minion-64es Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:46 -0800 PST }]
Feb 14 22:29:01.651: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-bo4h e2e-gce-builder-2-0-minion-bo4h Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:57 -0800 PST }]
Feb 14 22:29:01.651: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-lloc e2e-gce-builder-2-0-minion-lloc Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:50 -0800 PST }]
Feb 14 22:29:01.651: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-qlb8 e2e-gce-builder-2-0-minion-qlb8 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:50 -0800 PST }]
Feb 14 22:29:01.651: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-s2tm e2e-gce-builder-2-0-minion-s2tm Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:06 -0800 PST }]
Feb 14 22:29:01.651: INFO: heapster-v14-jfo48 e2e-gce-builder-2-0-minion-43a8 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:55 -0800 PST }]
Feb 14 22:29:01.651: INFO: kibana-logging-v1-yurqd e2e-gce-builder-2-0-minion-s2tm Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:25 -0800 PST }]
Feb 14 22:29:01.651: INFO: kube-dns-v10-lh264 e2e-gce-builder-2-0-minion-lloc Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:05 -0800 PST }]
Feb 14 22:29:01.651: INFO: kube-proxy-e2e-gce-builder-2-0-minion-43a8 e2e-gce-builder-2-0-minion-43a8 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:40 -0800 PST }]
Feb 14 22:29:01.651: INFO: kube-proxy-e2e-gce-builder-2-0-minion-64es e2e-gce-builder-2-0-minion-64es Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:31 -0800 PST }]
Feb 14 22:29:01.651: INFO: kube-proxy-e2e-gce-builder-2-0-minion-bo4h e2e-gce-builder-2-0-minion-bo4h Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:35 -0800 PST }]
Feb 14 22:29:01.651: INFO: kube-proxy-e2e-gce-builder-2-0-minion-lloc e2e-gce-builder-2-0-minion-lloc Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:34 -0800 PST }]
Feb 14 22:29:01.651: INFO: kube-proxy-e2e-gce-builder-2-0-minion-qlb8 e2e-gce-builder-2-0-minion-qlb8 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:35 -0800 PST }]
Feb 14 22:29:01.651: INFO: kube-proxy-e2e-gce-builder-2-0-minion-s2tm e2e-gce-builder-2-0-minion-s2tm Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:38 -0800 PST }]
Feb 14 22:29:01.651: INFO: kubernetes-dashboard-v0.1.0-wzxv0 e2e-gce-builder-2-0-minion-lloc Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:51 -0800 PST }]
Feb 14 22:29:01.651: INFO: l7-lb-controller-1dba6 e2e-gce-builder-2-0-minion-64es Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:56 -0800 PST }]
Feb 14 22:29:01.651: INFO: monitoring-influxdb-grafana-v3-lo2u2 e2e-gce-builder-2-0-minion-bo4h Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:12 -0800 PST }]
Feb 14 22:29:01.651: INFO:
Feb 14 22:29:01.658: INFO:
Logging node info for node e2e-gce-builder-2-0-minion-43a8
Feb 14 22:29:01.675: INFO: Node Info: &{{ } {e2e-gce-builder-2-0-minion-43a8 /api/v1/nodes/e2e-gce-builder-2-0-minion-43a8 f0e7849f-d3ac-11e5-a51a-42010af00002 4118 0 2016-02-14 22:25:43 -0800 PST <nil> <nil> map[failure-domain.alpha.kubernetes.io/region:us-central1 failure-domain.alpha.kubernetes.io/zone:us-central1-f kubernetes.io/hostname:e2e-gce-builder-2-0-minion-43a8 beta.kubernetes.io/instance-type:n1-standard-2] map[]} {10.245.5.0/24 17041295563895084226 gce://kubernetes-jenkins-pull/us-central1-f/e2e-gce-builder-2-0-minion-43a8 false} {map[memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI} cpu:{2.000 DecimalSI}] map[cpu:{2.000 DecimalSI} memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI}] [{OutOfDisk False 2016-02-14 22:29:00 -0800 PST 2016-02-14 22:25:43 -0800 PST KubeletHasSufficientDisk kubelet has sufficient disk space available} {Ready True 2016-02-14 22:29:00 -0800 PST 2016-02-14 22:26:19 -0800 PST KubeletReady kubelet is posting ready status}] [{InternalIP 10.240.0.8} {ExternalIP 104.197.241.72}] {{10250}} { 2C7D58A8-D843-A5B0-5D92-DA52823CB342 b9ccff52-9a49-4e13-82d1-6db42ec1f178 3.16.0-4-amd64 Debian GNU/Linux 7 (wheezy) docker://1.9.1 v1.2.0-alpha.7.841+ac65cc782a86d6 v1.2.0-alpha.7.841+ac65cc782a86d6} [{[gcr.io/google_containers/kube-proxy:de983c4f408a7e53b0f8807e1ef9a0b0] 164588349} {[gcr.io/google_containers/heapster:v0.20.0-alpha6] 85929942} {[gcr.io/google_containers/nettest:1.7] 24051275} {[nginx:latest] 134581595} {[gcr.io/google_containers/fluentd-elasticsearch:1.14] 562034622} {[gcr.io/google_containers/netexec:1.4] 7297019} {[gcr.io/google_containers/fakegitserver:0.1] 5007469} {[gcr.io/google_containers/busybox:1.24] 1113554} {[gcr.io/google_containers/mounttest:0.6] 2084693} {[gcr.io/google_containers/mounttest-user:0.3] 1718853} {[gcr.io/google_containers/pause:2.0] 350164} {[gcr.io/google_containers/portforwardtester:1.0] 2296329} {[gcr.io/google_containers/jessie-dnsutils:latest] 190148402} {[gcr.io/google_containers/mounttest:0.2] 1752375} {[gcr.io/google_containers/dnsutils:latest] 141895666} {[gcr.io/google_containers/pause:0.8.0] 241656} {[b.gcr.io/k8s_authenticated_test/serve_hostname:1.1 gcr.io/google_containers/serve_hostname:1.1] 4522409} {[gcr.io/google_containers/test-webserver:latest] 4534272}]}}
Feb 14 22:29:01.675: INFO:
Logging kubelet events for node e2e-gce-builder-2-0-minion-43a8
Feb 14 22:29:01.687: INFO:
Logging pods the kubelet thinks is on node e2e-gce-builder-2-0-minion-43a8
Feb 14 22:29:01.700: INFO: nginx started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.700: INFO: pd-test-322d4b85-d3ad-11e5-82fd-42010af00003 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.700: INFO: dns-test-52483d00-d3ad-11e5-a4f1-42010af00003 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.700: INFO: heapster-v14-jfo48 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.700: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-43a8 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.700: INFO: kube-proxy-e2e-gce-builder-2-0-minion-43a8 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.802: INFO: ERROR kubelet_docker_errors{operation_type="info"} => 1 @[0]
Feb 14 22:29:01.802: INFO: ERROR kubelet_docker_errors{operation_type="inspect_image"} => 23 @[0]
Feb 14 22:29:01.803: INFO: ERROR kubelet_docker_errors{operation_type="list_containers"} => 32 @[0]
Feb 14 22:29:01.803: INFO: ERROR kubelet_docker_errors{operation_type="list_images"} => 5 @[0]
Feb 14 22:29:01.803: INFO: ERROR kubelet_docker_errors{operation_type="pull_image"} => 1 @[0]
Feb 14 22:29:01.803: INFO: ERROR kubelet_docker_errors{operation_type="stop_container"} => 7 @[0]
Feb 14 22:29:01.803: INFO: ERROR kubelet_docker_errors{operation_type="version"} => 22 @[0]
Feb 14 22:29:01.803: INFO:
Latency metrics for node e2e-gce-builder-2-0-minion-43a8
Feb 14 22:29:01.803: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:51.903836s}
Feb 14 22:29:01.803: INFO: {Operation: Method:pod_worker_start_latency_microseconds Quantile:0.99 Latency:35.065574s}
Feb 14 22:29:01.803: INFO: {Operation:stop_container Method:docker_operations_latency_microseconds Quantile:0.99 Latency:30.187015s}
Feb 14 22:29:01.803: INFO: {Operation:stop_container Method:docker_operations_latency_microseconds Quantile:0.9 Latency:30.072055s}
Feb 14 22:29:01.803: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:20.955617s}
Feb 14 22:29:01.803: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.99 Latency:20.299898s}
Feb 14 22:29:01.803: INFO: {Operation:SyncPod Method:container_manager_latency_microseconds Quantile:0.99 Latency:20.271071s}
Feb 14 22:29:01.803: INFO: {Operation:sync Method:pod_worker_latency_microseconds Quantile:0.99 Latency:19.612563s}
Feb 14 22:29:01.803: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.99 Latency:18.489781s}
Feb 14 22:29:01.803: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.9 Latency:18.35431s}
Feb 14 22:29:01.803: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.9 Latency:10.275054s}
Feb 14 22:29:01.803: INFO:
Logging node info for node e2e-gce-builder-2-0-minion-64es
Feb 14 22:29:01.812: INFO: Node Info: &{{ } {e2e-gce-builder-2-0-minion-64es /api/v1/nodes/e2e-gce-builder-2-0-minion-64es ecd16025-d3ac-11e5-a51a-42010af00002 4018 0 2016-02-14 22:25:36 -0800 PST <nil> <nil> map[beta.kubernetes.io/instance-type:n1-standard-2 failure-domain.alpha.kubernetes.io/region:us-central1 failure-domain.alpha.kubernetes.io/zone:us-central1-f kubernetes.io/hostname:e2e-gce-builder-2-0-minion-64es] map[]} {10.245.0.0/24 14005317376642251118 gce://kubernetes-jenkins-pull/us-central1-f/e2e-gce-builder-2-0-minion-64es false} {map[cpu:{2.000 DecimalSI} memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI}] map[cpu:{2.000 DecimalSI} memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI}] [{OutOfDisk False 2016-02-14 22:28:54 -0800 PST 2016-02-14 22:25:36 -0800 PST KubeletHasSufficientDisk kubelet has sufficient disk space available} {Ready True 2016-02-14 22:28:54 -0800 PST 2016-02-14 22:26:12 -0800 PST KubeletReady kubelet is posting ready status}] [{InternalIP 10.240.0.7} {ExternalIP 104.197.255.191}] {{10250}} { 26F65CB0-D3FD-B18E-8138-0AD8059AF12C 1e07dec8-fa5b-45ab-87b7-bac9f729e95b 3.16.0-4-amd64 Debian GNU/Linux 7 (wheezy) docker://1.9.1 v1.2.0-alpha.7.841+ac65cc782a86d6 v1.2.0-alpha.7.841+ac65cc782a86d6} [{[gcr.io/google_containers/kube-proxy:de983c4f408a7e53b0f8807e1ef9a0b0] 164588349} {[gcr.io/google_containers/nettest:1.7] 24051275} {[gcr.io/google_containers/fluentd-elasticsearch:1.14] 562034622} {[gcr.io/google_containers/netexec:1.4] 7297019} {[redis:latest] 151289204} {[gcr.io/google_containers/glbc:0.5.2] 226351998} {[gcr.io/google_containers/busybox:1.24] 1113554} {[gcr.io/google_containers/mounttest:0.6] 2084693} {[gcr.io/google_containers/hostexec:1.2] 13209617} {[gcr.io/google_containers/defaultbackend:1.0] 7513643} {[gcr.io/google_containers/mounttest:0.5] 1718853} {[gcr.io/google_containers/pause:2.0] 350164} {[gcr.io/google_containers/pause:0.8.0] 241656} {[gcr.io/google_containers/eptest:0.1] 2970692} {[gcr.io/google_containers/serve_hostname:1.1] 4522409} {[gcr.io/google_containers/update-demo:nautilus] 4555533} {[gcr.io/google_containers/test-webserver:latest] 4534272}]}}
Feb 14 22:29:01.812: INFO:
Logging kubelet events for node e2e-gce-builder-2-0-minion-64es
Feb 14 22:29:01.822: INFO:
Logging pods the kubelet thinks is on node e2e-gce-builder-2-0-minion-64es
Feb 14 22:29:01.923: INFO: downwardapi-volume-3516c9fc-d3ad-11e5-b7b8-42010af00003 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.923: INFO: l7-lb-controller-1dba6 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.923: INFO: mutability-test-94yvp started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.924: INFO: liveness-http started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.924: INFO: pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.924: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-64es started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.924: INFO: kube-proxy-e2e-gce-builder-2-0-minion-64es started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.924: INFO: pd-test-322e11bc-d3ad-11e5-abad-42010af00003 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.924: INFO: pd-test-322d4bd8-d3ad-11e5-82fd-42010af00003 started at <nil> (0 container statuses recorded)
Feb 14 22:29:02.230: INFO: ERROR kubelet_docker_errors{operation_type="info"} => 1 @[0]
Feb 14 22:29:02.230: INFO: ERROR kubelet_docker_errors{operation_type="inspect_image"} => 20 @[0]
Feb 14 22:29:02.230: INFO: ERROR kubelet_docker_errors{operation_type="list_containers"} => 32 @[0]
Feb 14 22:29:02.230: INFO: ERROR kubelet_docker_errors{operation_type="list_images"} => 5 @[0]
Feb 14 22:29:02.230: INFO: ERROR kubelet_docker_errors{operation_type="pull_image"} => 1 @[0]
Feb 14 22:29:02.230: INFO: ERROR kubelet_docker_errors{operation_type="stop_container"} => 12 @[0]
Feb 14 22:29:02.230: INFO: ERROR kubelet_docker_errors{operation_type="version"} => 22 @[0]
Feb 14 22:29:02.230: INFO:
Latency metrics for node e2e-gce-builder-2-0-minion-64es
Feb 14 22:29:02.230: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:1m1.879215s}
Feb 14 22:29:02.230: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:35.02703s}
Feb 14 22:29:02.230: INFO: {Operation: Method:pod_worker_start_latency_microseconds Quantile:0.99 Latency:35.026932s}
Feb 14 22:29:02.231: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.99 Latency:28.569405s}
Feb 14 22:29:02.231: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.9 Latency:20.501721s}
Feb 14 22:29:02.231: INFO: {Operation:SyncPod Method:container_manager_latency_microseconds Quantile:0.99 Latency:20.4838s}
Feb 14 22:29:02.231: INFO: {Operation:sync Method:pod_worker_latency_microseconds Quantile:0.99 Latency:11.423451s}
Feb 14 22:29:02.231: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.99 Latency:11.138902s}
Feb 14 22:29:02.231: INFO:
Logging node info for node e2e-gce-builder-2-0-minion-bo4h
Feb 14 22:29:02.317: INFO: Node Info: &{{ } {e2e-gce-builder-2-0-minion-bo4h /api/v1/nodes/e2e-gce-builder-2-0-minion-bo4h ee19a4c8-d3ac-11e5-a51a-42010af00002 4098 0 2016-02-14 22:25:38 -0800 PST <nil> <nil> map[beta.kubernetes.io/instance-type:n1-standard-2 failure-domain.alpha.kubernetes.io/region:us-central1 failure-domain.alpha.kubernetes.io/zone:us-central1-f kubernetes.io/hostname:e2e-gce-builder-2-0-minion-bo4h] map[]} {10.245.2.0/24 9550812584030539242 gce://kubernetes-jenkins-pull/us-central1-f/e2e-gce-builder-2-0-minion-bo4h false} {map[memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI} cpu:{2.000 DecimalSI}] map[pods:{110.000 DecimalSI} cpu:{2.000 DecimalSI} memory:{7864139776.000 BinarySI}] [{OutOfDisk False 2016-02-14 22:28:57 -0800 PST 2016-02-14 22:25:38 -0800 PST KubeletHasSufficientDisk kubelet has sufficient disk space available} {Ready True 2016-02-14 22:28:57 -0800 PST 2016-02-14 22:26:16 -0800 PST KubeletReady kubelet is posting ready status}] [{InternalIP 10.240.0.4} {ExternalIP 104.197.242.28}] {{10250}} { 46A6AB8D-5EA9-904C-891F-88F72D6ECEBD e5e73f32-d546-44dd-82cf-174505489c34 3.16.0-4-amd64 Debian GNU/Linux 7 (wheezy) docker://1.9.1 v1.2.0-alpha.7.841+ac65cc782a86d6 v1.2.0-alpha.7.841+ac65cc782a86d6} [{[gcr.io/google_containers/kube-proxy:de983c4f408a7e53b0f8807e1ef9a0b0] 164588349} {[gcr.io/google_containers/nettest:1.7] 24051275} {[gcr.io/google_containers/fluentd-elasticsearch:1.14] 562034622} {[busybox:latest gcr.io/google_containers/busybox:1.24] 1113554} {[gcr.io/google_containers/mounttest:0.6] 2084693} {[gcr.io/google_containers/hostexec:1.2] 13209617} {[gcr.io/google_containers/mounttest:0.5] 1718853} {[gcr.io/google_containers/heapster_grafana:v2.1.1] 206641132} {[gcr.io/google_containers/pause:2.0] 350164} {[gcr.io/google_containers/porter:cd5cb5791ebaa8641955f0e8c2a9bed669b1eaab] 5010921} {[gcr.io/google_containers/heapster_influxdb:v0.5] 251005705} {[gcr.io/google_containers/jessie-dnsutils:latest] 190148402} {[gcr.io/google_containers/dnsutils:latest] 141895666} {[gcr.io/google_containers/pause:0.8.0] 241656} {[gcr.io/google_containers/serve_hostname:1.1] 4522409} {[gcr.io/google_containers/update-demo:nautilus] 4555533} {[gcr.io/google_containers/nginx:1.7.9] 91664166} {[gcr.io/google_containers/test-webserver:latest] 4534272}]}}
Feb 14 22:29:02.317: INFO:
Logging kubelet events for node e2e-gce-builder-2-0-minion-bo4h
Feb 14 22:29:02.523: INFO:
Logging pods the kubelet thinks is on node e2e-gce-builder-2-0-minion-bo4h
Feb 14 22:29:02.723: INFO: hostexec started at <nil> (0 container statuses recorded)
Feb 14 22:29:02.723: INFO: proxy-service-n6w5j-exzdq started at <nil> (0 container statuses recorded)
Feb 14 22:29:02.723: INFO: monitoring-influxdb-grafana-v3-lo2u2 started at <nil> (0 container statuses recorded)
Feb 14 22:29:02.723: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-bo4h started at <nil> (0 container statuses recorded)
Feb 14 22:29:02.723: INFO: kube-proxy-e2e-gce-builder-2-0-minion-bo4h started at <nil> (0 container statuses recorded)
Feb 14 22:29:02.723: INFO: update-demo-nautilus-vn45c started at <nil> (0 container statuses recorded)
Feb 14 22:29:03.020: INFO: ERROR kubelet_docker_errors{operation_type="info"} => 1 @[0]
Feb 14 22:29:03.020: INFO: ERROR kubelet_docker_errors{operation_type="inspect_image"} => 20 @[0]
Feb 14 22:29:03.020: INFO: ERROR kubelet_docker_errors{operation_type="list_containers"} => 32 @[0]
Feb 14 22:29:03.020: INFO: ERROR kubelet_docker_errors{operation_type="list_images"} => 5 @[0]
Feb 14 22:29:03.020: INFO: ERROR kubelet_docker_errors{operation_type="pull_image"} => 1 @[0]
Feb 14 22:29:03.020: INFO: ERROR kubelet_docker_errors{operation_type="stop_container"} => 9 @[0]
Feb 14 22:29:03.020: INFO: ERROR kubelet_docker_errors{operation_type="version"} => 22 @[0]
Feb 14 22:29:03.020: INFO:
Latency metrics for node e2e-gce-builder-2-0-minion-bo4h
Feb 14 22:29:03.020: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:49.794469s}
Feb 14 22:29:03.020: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.99 Latency:36.497124s}
Feb 14 22:29:03.020: INFO: {Operation:SyncPod Method:container_manager_latency_microseconds Quantile:0.99 Latency:36.487992s}
Feb 14 22:29:03.020: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:35.03492s}
Feb 14 22:29:03.020: INFO: {Operation: Method:pod_worker_start_latency_microseconds Quantile:0.99 Latency:35.034832s}
Feb 14 22:29:03.020: INFO: {Operation:stop_container Method:docker_operations_latency_microseconds Quantile:0.99 Latency:30.119192s}
Feb 14 22:29:03.020: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.99 Latency:25.025646s}
Feb 14 22:29:03.020: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.9 Latency:20.460683s}
Feb 14 22:29:03.020: INFO: {Operation:sync Method:pod_worker_latency_microseconds Quantile:0.99 Latency:11.826527s}
Feb 14 22:29:03.020: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.9 Latency:11.401707s}
Feb 14 22:29:03.020: INFO:
Logging node info for node e2e-gce-builder-2-0-minion-lloc
Feb 14 22:29:03.116: INFO: Node Info: &{{ } {e2e-gce-builder-2-0-minion-lloc /api/v1/nodes/e2e-gce-builder-2-0-minion-lloc ee85f672-d3ac-11e5-a51a-42010af00002 4064 0 2016-02-14 22:25:39 -0800 PST <nil> <nil> map[beta.kubernetes.io/instance-type:n1-standard-2 failure-domain.alpha.kubernetes.io/region:us-central1 failure-domain.alpha.kubernetes.io/zone:us-central1-f kubernetes.io/hostname:e2e-gce-builder-2-0-minion-lloc] map[]} {10.245.3.0/24 10789933251084181977 gce://kubernetes-jenkins-pull/us-central1-f/e2e-gce-builder-2-0-minion-lloc false} {map[cpu:{2.000 DecimalSI} memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI}] map[memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI} cpu:{2.000 DecimalSI}] [{OutOfDisk False 2016-02-14 22:28:56 -0800 PST 2016-02-14 22:25:39 -0800 PST KubeletHasSufficientDisk kubelet has sufficient disk space available} {Ready True 2016-02-14 22:28:56 -0800 PST 2016-02-14 22:26:14 -0800 PST KubeletReady kubelet is posting ready status}] [{InternalIP 10.240.0.6} {ExternalIP 104.197.253.82}] {{10250}} { 1FAA9E19-7503-D8E7-AC9A-CAA9E15742D5 a4767d54-3ea1-41af-a647-89f99ad67407 3.16.0-4-amd64 Debian GNU/Linux 7 (wheezy) docker://1.9.1 v1.2.0-alpha.7.841+ac65cc782a86d6 v1.2.0-alpha.7.841+ac65cc782a86d6} [{[gcr.io/google_containers/kube-proxy:de983c4f408a7e53b0f8807e1ef9a0b0] 164588349} {[gcr.io/google_containers/nettest:1.7] 24051275} {[nginx:latest] 134581595} {[gcr.io/google_containers/fluentd-elasticsearch:1.14] 562034622} {[gcr.io/google_containers/kubernetes-dashboard-amd64:v0.1.0] 35409795} {[gcr.io/google_containers/netexec:1.4] 7297019} {[redis:latest] 151289204} {[gcr.io/google_containers/busybox:1.24] 1113554} {[gcr.io/google_containers/kube2sky:1.12] 24482187} {[gcr.io/google_containers/skydns:2015-10-13-8c72f8c] 40551394} {[gcr.io/google_containers/pause:2.0] 350164} {[gcr.io/google_containers/exechealthz:1.0] 7099444} {[gcr.io/google_containers/etcd:2.0.9] 12819040} {[gcr.io/google_containers/pause:0.8.0] 241656} {[gcr.io/google_containers/serve_hostname:1.1] 4522409} {[gcr.io/google_containers/nginx:1.7.9] 91664166}]}}
Feb 14 22:29:03.117: INFO:
Logging kubelet events for node e2e-gce-builder-2-0-minion-lloc
Feb 14 22:29:03.324: INFO:
Logging pods the kubelet thinks is on node e2e-gce-builder-2-0-minion-lloc
Feb 14 22:29:03.526: INFO: mutability-test-pyldw started at <nil> (0 container statuses recorded)
Feb 14 22:29:03.526: INFO: kube-dns-v10-lh264 started at <nil> (0 container statuses recorded)
Feb 14 22:29:03.526: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-lloc started at <nil> (0 container statuses recorded)
Feb 14 22:29:03.526: INFO: kubernetes-dashboard-v0.1.0-wzxv0 started at <nil> (0 container statuses recorded)
Feb 14 22:29:03.526: INFO: kube-proxy-e2e-gce-builder-2-0-minion-lloc started at <nil> (0 container statuses recorded)
Feb 14 22:29:03.803: INFO: ERROR kubelet_docker_errors{operation_type="info"} => 1 @[0]
Feb 14 22:29:03.803: INFO: ERROR kubelet_docker_errors{operation_type="inspect_image"} => 18 @[0]
Feb 14 22:29:03.803: INFO: ERROR kubelet_docker_errors{operation_type="list_containers"} => 32 @[0]
Feb 14 22:29:03.803: INFO: ERROR kubelet_docker_errors{operation_type="list_images"} => 5 @[0]
Feb 14 22:29:03.803: INFO: ERROR kubelet_docker_errors{operation_type="pull_image"} => 1 @[0]
Feb 14 22:29:03.803: INFO: ERROR kubelet_docker_errors{operation_type="stop_container"} => 7 @[0]
Feb 14 22:29:03.803: INFO: ERROR kubelet_docker_errors{operation_type="version"} => 22 @[0]
Feb 14 22:29:03.803: INFO:
Latency metrics for node e2e-gce-builder-2-0-minion-lloc
Feb 14 22:29:03.803: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:50.664034s}
Feb 14 22:29:03.803: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:35.064854s}
Feb 14 22:29:03.803: INFO: {Operation: Method:pod_worker_start_latency_microseconds Quantile:0.99 Latency:35.064743s}
Feb 14 22:29:03.803: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.99 Latency:22.179206s}
Feb 14 22:29:03.803: INFO: {Operation:SyncPod Method:container_manager_latency_microseconds Quantile:0.99 Latency:22.167655s}
Feb 14 22:29:03.803: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.9 Latency:15.237909s}
Feb 14 22:29:03.803: INFO: {Operation:sync Method:pod_worker_latency_microseconds Quantile:0.99 Latency:14.464511s}
Feb 14 22:29:03.803: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.99 Latency:14.253852s}
Feb 14 22:29:03.803: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.9 Latency:13.393135s}
Feb 14 22:29:03.803: INFO:
Logging node info for node e2e-gce-builder-2-0-minion-qlb8
Feb 14 22:29:03.917: INFO: Node Info: &{{ } {e2e-gce-builder-2-0-minion-qlb8 /api/v1/nodes/e2e-gce-builder-2-0-minion-qlb8 ece12aa8-d3ac-11e5-a51a-42010af00002 4040 0 2016-02-14 22:25:36 -0800 PST <nil> <nil> map[kubernetes.io/hostname:e2e-gce-builder-2-0-minion-qlb8 beta.kubernetes.io/instance-type:n1-standard-2 failure-domain.alpha.kubernetes.io/region:us-central1 failure-domain.alpha.kubernetes.io/zone:us-central1-f] map[]} {10.245.1.0/24 11535097332819972334 gce://kubernetes-jenkins-pull/us-central1-f/e2e-gce-builder-2-0-minion-qlb8 false} {map[cpu:{2.000 DecimalSI} memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI}] map[cpu:{2.000 DecimalSI} memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI}] [{OutOfDisk False 2016-02-14 22:28:55 -0800 PST 2016-02-14 22:25:36 -0800 PST KubeletHasSufficientDisk kubelet has sufficient disk space available} {Ready True 2016-02-14 22:28:55 -0800 PST 2016-02-14 22:26:13 -0800 PST KubeletReady kubelet is posting ready status}] [{InternalIP 10.240.0.5} {ExternalIP 104.197.238.173}] {{10250}} { 91ACE89F-D1E2-F446-FC9D-7EB4FAA6B102 14adb070-84c7-4e11-ab64-c947160e5a02 3.16.0-4-amd64 Debian GNU/Linux 7 (wheezy) docker://1.9.1 v1.2.0-alpha.7.841+ac65cc782a86d6 v1.2.0-alpha.7.841+ac65cc782a86d6} [{[gcr.io/google_containers/kube-proxy:de983c4f408a7e53b0f8807e1ef9a0b0] 164588349} {[gcr.io/google_containers/nettest:1.7] 24051275} {[nginx:latest] 134581595} {[gcr.io/google_containers/fluentd-elasticsearch:1.14] 562034622} {[gcr.io/google_containers/netexec:1.4] 7297019} {[redis:latest] 151289204} {[gcr.io/google_containers/busybox:1.24 busybox:latest] 1113554} {[gcr.io/google_containers/elasticsearch:1.8] 410989305} {[gcr.io/google_containers/mounttest:0.6] 2084693} {[gcr.io/google_containers/hostexec:1.2] 13209617} {[gcr.io/google_containers/mounttest-user:0.3] 1718853} {[gcr.io/google_containers/mounttest:0.5] 1718853} {[gcr.io/google_containers/pause:2.0] 350164} {[gcr.io/google_containers/portforwardtester:1.0] 2296329} {[gcr.io/google_containers/pause:0.8.0] 241656} {[gcr.io/google_containers/eptest:0.1] 2970692} {[b.gcr.io/k8s_authenticated_test/serve_hostname:1.1 gcr.io/google_containers/serve_hostname:1.1] 4522409} {[gcr.io/google_containers/update-demo:nautilus] 4555533} {[gcr.io/google_containers/test-webserver:latest] 4534272}]}}
Feb 14 22:29:03.917: INFO:
Logging kubelet events for node e2e-gce-builder-2-0-minion-qlb8
Feb 14 22:29:04.121: INFO:
Logging pods the kubelet thinks is on node e2e-gce-builder-2-0-minion-qlb8
Feb 14 22:29:04.324: INFO: run-test-3-vl7eh started at <nil> (0 container statuses recorded)
Feb 14 22:29:04.324: INFO: liveness-exec started at <nil> (0 container statuses recorded)
Feb 14 22:29:04.324: INFO: elasticsearch-logging-v1-xhinl started at <nil> (0 container statuses recorded)
Feb 14 22:29:04.324: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-qlb8 started at <nil> (0 container statuses recorded)
Feb 14 22:29:04.324: INFO: kube-proxy-e2e-gce-builder-2-0-minion-qlb8 started at <nil> (0 container statuses recorded)
Feb 14 22:29:04.324: INFO: update-demo-kitten-cr05m started at <nil> (0 container statuses recorded)
Feb 14 22:29:04.324: INFO: foo-yswqv started at <nil> (0 container statuses recorded)
Feb 14 22:29:04.324: INFO: update-demo-nautilus-q2jms started at <nil> (0 container statuses recorded)
Feb 14 22:29:04.658: INFO: ERROR kubelet_docker_errors{operation_type="info"} => 1 @[0]
Feb 14 22:29:04.659: INFO: ERROR kubelet_docker_errors{operation_type="inspect_image"} => 24 @[0]
Feb 14 22:29:04.659: INFO: ERROR kubelet_docker_errors{operation_type="list_containers"} => 31 @[0]
Feb 14 22:29:04.659: INFO: ERROR kubelet_docker_errors{operation_type="list_images"} => 5 @[0]
Feb 14 22:29:04.659: INFO: ERROR kubelet_docker_errors{operation_type="pull_image"} => 1 @[0]
Feb 14 22:29:04.659: INFO: ERROR kubelet_docker_errors{operation_type="stop_container"} => 21 @[0]
Feb 14 22:29:04.659: INFO: ERROR kubelet_docker_errors{operation_type="version"} => 22 @[0]
Feb 14 22:29:04.659: INFO:
Latency metrics for node e2e-gce-builder-2-0-minion-qlb8
Feb 14 22:29:04.659: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:53.380754s}
Feb 14 22:29:04.659: INFO: {Operation: Method:pod_worker_start_latency_microseconds Quantile:0.99 Latency:35.023248s}
Feb 14 22:29:04.659: INFO: {Operation:sync Method:pod_worker_latency_microseconds Quantile:0.99 Latency:30.19793s}
Feb 14 22:29:04.659: INFO: {Operation:stop_container Method:docker_operations_latency_microseconds Quantile:0.99 Latency:30.065551s}
Feb 14 22:29:04.659: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.99 Latency:30.019178s}
Feb 14 22:29:04.659: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.99 Latency:28.806406s}
Feb 14 22:29:04.659: INFO: {Operation:SyncPod Method:container_manager_latency_microseconds Quantile:0.99 Latency:18.393164s}
Feb 14 22:29:04.659: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:16.179337s}
Feb 14 22:29:04.659: INFO:
Logging node info for node e2e-gce-builder-2-0-minion-s2tm
Feb 14 22:29:04.717: INFO: Node Info: &{{ } {e2e-gce-builder-2-0-minion-s2tm /api/v1/nodes/e2e-gce-builder-2-0-minion-s2tm eddbdf1f-d3ac-11e5-a51a-42010af00002 4065 0 2016-02-14 22:25:38 -0800 PST <nil> <nil> map[kubernetes.io/hostname:e2e-gce-builder-2-0-minion-s2tm beta.kubernetes.io/instance-type:n1-standard-2 failure-domain.alpha.kubernetes.io/region:us-central1 failure-domain.alpha.kubernetes.io/zone:us-central1-f] map[]} {10.245.4.0/24 3822123003318812276 gce://kubernetes-jenkins-pull/us-central1-f/e2e-gce-builder-2-0-minion-s2tm false} {map[memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI} cpu:{2.000 DecimalSI}] map[pods:{110.000 DecimalSI} cpu:{2.000 DecimalSI} memory:{7864139776.000 BinarySI}] [{OutOfDisk False 2016-02-14 22:28:56 -0800 PST 2016-02-14 22:25:38 -0800 PST KubeletHasSufficientDisk kubelet has sufficient disk space available} {Ready True 2016-02-14 22:28:56 -0800 PST 2016-02-14 22:26:14 -0800 PST KubeletReady kubelet is posting ready status}] [{InternalIP 10.240.0.3} {ExternalIP 104.154.75.54}] {{10250}} { A996ECE6-745A-EE76-876D-08D85C5D0136 d8bbbc85-9561-4ea7-b056-c4ae3e0be4da 3.16.0-4-amd64 Debian GNU/Linux 7 (wheezy) docker://1.9.1 v1.2.0-alpha.7.841+ac65cc782a86d6 v1.2.0-alpha.7.841+ac65cc782a86d6} [{[gcr.io/google_containers/kube-proxy:de983c4f408a7e53b0f8807e1ef9a0b0] 164588349} {[gcr.io/google_containers/nettest:1.7] 24051275} {[nginx:latest] 134581595} {[gcr.io/google_containers/fluentd-elasticsearch:1.14] 562034622} {[gcr.io/google_containers/netexec:1.4] 7297019} {[redis:latest] 151289204} {[gcr.io/google_containers/busybox:1.24 busybox:latest] 1113554} {[gcr.io/google_containers/elasticsearch:1.8] 410989305} {[gcr.io/google_containers/mounttest:0.6] 2084693} {[gcr.io/google_containers/mounttest:0.5] 1718853} {[gcr.io/google_containers/pause:2.0] 350164} {[gcr.io/google_containers/kibana:1.3] 396897764} {[gcr.io/google_containers/pause:0.8.0] 241656} {[b.gcr.io/k8s_authenticated_test/serve_hostname:1.1 gcr.io/google_containers/serve_hostname:1.1] 4522409} {[gcr.io/google_containers/update-demo:nautilus] 4555533} {[gcr.io/google_containers/update-demo:kitten] 4549069} {[gcr.io/google_containers/nginx:1.7.9] 91664166}]}}
Feb 14 22:29:04.717: INFO:
Logging kubelet events for node e2e-gce-builder-2-0-minion-s2tm
Feb 14 22:29:04.923: INFO:
Logging pods the kubelet thinks is on node e2e-gce-builder-2-0-minion-s2tm
Feb 14 22:29:05.122: INFO: foo-63zhd started at <nil> (0 container statuses recorded)
Feb 14 22:29:05.122: INFO: update-demo-kitten-15bfi started at <nil> (0 container statuses recorded)
Feb 14 22:29:05.122: INFO: kibana-logging-v1-yurqd started at <nil> (0 container statuses recorded)
Feb 14 22:29:05.122: INFO: elasticsearch-logging-v1-8a3oc started at <nil> (0 container statuses recorded)
Feb 14 22:29:05.123: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-s2tm started at <nil> (0 container statuses recorded)
Feb 14 22:29:05.123: INFO: kube-proxy-e2e-gce-builder-2-0-minion-s2tm started at <nil> (0 container statuses recorded)
Feb 14 22:29:05.418: INFO: ERROR kubelet_docker_errors{operation_type="info"} => 1 @[0]
Feb 14 22:29:05.418: INFO: ERROR kubelet_docker_errors{operation_type="inspect_image"} => 21 @[0]
Feb 14 22:29:05.418: INFO: ERROR kubelet_docker_errors{operation_type="list_containers"} => 32 @[0]
Feb 14 22:29:05.418: INFO: ERROR kubelet_docker_errors{operation_type="list_images"} => 5 @[0]
Feb 14 22:29:05.418: INFO: ERROR kubelet_docker_errors{operation_type="logs"} => 1 @[0]
Feb 14 22:29:05.418: INFO: ERROR kubelet_docker_errors{operation_type="pull_image"} => 1 @[0]
Feb 14 22:29:05.418: INFO: ERROR kubelet_docker_errors{operation_type="stop_container"} => 16 @[0]
Feb 14 22:29:05.418: INFO: ERROR kubelet_docker_errors{operation_type="version"} => 22 @[0]
Feb 14 22:29:05.418: INFO:
Latency metrics for node e2e-gce-builder-2-0-minion-s2tm
Feb 14 22:29:05.418: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:54.3937s}
Feb 14 22:29:05.418: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.99 Latency:46.94785s}
Feb 14 22:29:05.418: INFO: {Operation:SyncPod Method:container_manager_latency_microseconds Quantile:0.99 Latency:46.933443s}
Feb 14 22:29:05.418: INFO: {Operation:sync Method:pod_worker_latency_microseconds Quantile:0.99 Latency:46.724749s}
Feb 14 22:29:05.418: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.99 Latency:45.137388s}
Feb 14 22:29:05.418: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.9 Latency:43.134663s}
Feb 14 22:29:05.419: INFO: {Operation: Method:pod_worker_start_latency_microseconds Quantile:0.99 Latency:35.117599s}
Feb 14 22:29:05.419: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:33.538877s}
Feb 14 22:29:05.419: INFO: {Operation:stop_container Method:docker_operations_latency_microseconds Quantile:0.99 Latency:30.083542s}
Feb 14 22:29:05.419: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.9 Latency:21.043204s}
STEP: Destroying namespace "e2e-tests-configmap-iibco" for this suite.
Feb 14 22:29:05.916: INFO: Waiting up to 1m0s for all nodes to be ready
• Failure [100.958 seconds]
ConfigMap
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/configmap.go:332
updates should be reflected in volume [Conformance] [It]
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/configmap.go:271
Timed out after 90.000s.
Expected
<string>: content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
to contain substring
<string>: value-2
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/configmap.go:270
------------------------------
``` | 1.0 | e2e flake: ConfigMap updates should be reflected in volume timed out - Test logs at https://console.cloud.google.com/storage/browser/kubernetes-jenkins/pr-logs/pull/21110/kubernetes-pull-build-test-e2e-gce/28558/
```
------------------------------
[BeforeEach] ConfigMap
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework.go:82
STEP: Creating a kubernetes client
Feb 14 22:27:25.162: INFO: >>> testContext.KubeConfig: /var/lib/jenkins/workspace/kubernetes-pull-build-test-e2e-gce/.kube/config
STEP: Building a namespace api object
Feb 14 22:27:25.348: INFO: Waiting up to 2m0s for service account default to be provisioned in ns e2e-tests-configmap-iibco
Feb 14 22:27:25.359: INFO: Get service account default in ns e2e-tests-configmap-iibco failed, ignoring for 2s: serviceaccounts "default" not found
Feb 14 22:27:27.362: INFO: Service account default in ns e2e-tests-configmap-iibco with secrets found. (2.013966058s)
STEP: Waiting for a default service account to be provisioned in namespace
Feb 14 22:27:27.362: INFO: Waiting up to 2m0s for service account default to be provisioned in ns e2e-tests-configmap-iibco
Feb 14 22:27:27.364: INFO: Service account default in ns e2e-tests-configmap-iibco with secrets found. (2.152421ms)
[It] updates should be reflected in volume [Conformance]
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/configmap.go:271
STEP: Creating configMap with name configmap-test-upd-2edc0b4e-d3ad-11e5-8393-42010af00003
STEP: Creating the pod
Feb 14 22:27:27.372: INFO: Waiting up to 5m0s for pod pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003 status to be running
Feb 14 22:27:27.380: INFO: Waiting for pod pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003 in namespace 'e2e-tests-configmap-iibco' status to be 'running'(found phase: "Pending", readiness: false) (7.523359ms elapsed)
Feb 14 22:27:29.383: INFO: Waiting for pod pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003 in namespace 'e2e-tests-configmap-iibco' status to be 'running'(found phase: "Pending", readiness: false) (2.010728843s elapsed)
Feb 14 22:27:31.388: INFO: Found pod 'pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003' on node 'e2e-gce-builder-2-0-minion-64es'
STEP: Updating configmap configmap-test-upd-2edc0b4e-d3ad-11e5-8393-42010af00003
STEP: Deleting the pod
STEP: Cleaning up the configMap
[AfterEach] ConfigMap
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework.go:83
STEP: Collecting events from namespace "e2e-tests-configmap-iibco".
Feb 14 22:29:01.583: INFO: event for pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003: {default-scheduler } Scheduled: Successfully assigned pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003 to e2e-gce-builder-2-0-minion-64es
Feb 14 22:29:01.583: INFO: event for pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003: {kubelet e2e-gce-builder-2-0-minion-64es} Pulling: pulling image "gcr.io/google_containers/mounttest:0.6"
Feb 14 22:29:01.583: INFO: event for pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003: {kubelet e2e-gce-builder-2-0-minion-64es} Pulled: Successfully pulled image "gcr.io/google_containers/mounttest:0.6"
Feb 14 22:29:01.583: INFO: event for pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003: {kubelet e2e-gce-builder-2-0-minion-64es} Created: Created container with docker id d6dce9ce8aa8
Feb 14 22:29:01.583: INFO: event for pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003: {kubelet e2e-gce-builder-2-0-minion-64es} Started: Started container with docker id d6dce9ce8aa8
Feb 14 22:29:01.651: INFO: POD NODE PHASE GRACE CONDITIONS
Feb 14 22:29:01.651: INFO: downwardapi-volume-3516c9fc-d3ad-11e5-b7b8-42010af00003 e2e-gce-builder-2-0-minion-64es Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:39 -0800 PST }]
Feb 14 22:29:01.651: INFO: foo-yswqv e2e-gce-builder-2-0-minion-qlb8 Running 30s [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:28:59 -0800 PST }]
Feb 14 22:29:01.651: INFO: update-demo-kitten-15bfi e2e-gce-builder-2-0-minion-s2tm Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:28:46 -0800 PST }]
Feb 14 22:29:01.651: INFO: update-demo-kitten-cr05m e2e-gce-builder-2-0-minion-qlb8 Pending [{Ready False 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:29:01 -0800 PST ContainersNotReady containers with unready status: [update-demo]}]
Feb 14 22:29:01.651: INFO: nginx e2e-gce-builder-2-0-minion-43a8 Running [{Ready False 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:28:56 -0800 PST ContainersNotReady containers with unready status: [nginx]}]
Feb 14 22:29:01.651: INFO: update-demo-nautilus-q2jms e2e-gce-builder-2-0-minion-qlb8 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:28:58 -0800 PST }]
Feb 14 22:29:01.651: INFO: update-demo-nautilus-vn45c e2e-gce-builder-2-0-minion-bo4h Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:28:58 -0800 PST }]
Feb 14 22:29:01.651: INFO: liveness-exec e2e-gce-builder-2-0-minion-qlb8 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:29 -0800 PST }]
Feb 14 22:29:01.651: INFO: liveness-http e2e-gce-builder-2-0-minion-64es Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:41 -0800 PST }]
Feb 14 22:29:01.651: INFO: proxy-service-n6w5j-exzdq e2e-gce-builder-2-0-minion-bo4h Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:35 -0800 PST }]
Feb 14 22:29:01.651: INFO: mutability-test-pyldw e2e-gce-builder-2-0-minion-lloc Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:28:05 -0800 PST }]
Feb 14 22:29:01.651: INFO: mutability-test-94yvp e2e-gce-builder-2-0-minion-64es Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:55 -0800 PST }]
Feb 14 22:29:01.651: INFO: elasticsearch-logging-v1-8a3oc e2e-gce-builder-2-0-minion-s2tm Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:21 -0800 PST }]
Feb 14 22:29:01.651: INFO: elasticsearch-logging-v1-xhinl e2e-gce-builder-2-0-minion-qlb8 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:06 -0800 PST }]
Feb 14 22:29:01.651: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-43a8 e2e-gce-builder-2-0-minion-43a8 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:55 -0800 PST }]
Feb 14 22:29:01.651: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-64es e2e-gce-builder-2-0-minion-64es Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:46 -0800 PST }]
Feb 14 22:29:01.651: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-bo4h e2e-gce-builder-2-0-minion-bo4h Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:57 -0800 PST }]
Feb 14 22:29:01.651: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-lloc e2e-gce-builder-2-0-minion-lloc Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:50 -0800 PST }]
Feb 14 22:29:01.651: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-qlb8 e2e-gce-builder-2-0-minion-qlb8 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:50 -0800 PST }]
Feb 14 22:29:01.651: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-s2tm e2e-gce-builder-2-0-minion-s2tm Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:06 -0800 PST }]
Feb 14 22:29:01.651: INFO: heapster-v14-jfo48 e2e-gce-builder-2-0-minion-43a8 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:55 -0800 PST }]
Feb 14 22:29:01.651: INFO: kibana-logging-v1-yurqd e2e-gce-builder-2-0-minion-s2tm Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:25 -0800 PST }]
Feb 14 22:29:01.651: INFO: kube-dns-v10-lh264 e2e-gce-builder-2-0-minion-lloc Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:05 -0800 PST }]
Feb 14 22:29:01.651: INFO: kube-proxy-e2e-gce-builder-2-0-minion-43a8 e2e-gce-builder-2-0-minion-43a8 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:40 -0800 PST }]
Feb 14 22:29:01.651: INFO: kube-proxy-e2e-gce-builder-2-0-minion-64es e2e-gce-builder-2-0-minion-64es Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:31 -0800 PST }]
Feb 14 22:29:01.651: INFO: kube-proxy-e2e-gce-builder-2-0-minion-bo4h e2e-gce-builder-2-0-minion-bo4h Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:35 -0800 PST }]
Feb 14 22:29:01.651: INFO: kube-proxy-e2e-gce-builder-2-0-minion-lloc e2e-gce-builder-2-0-minion-lloc Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:34 -0800 PST }]
Feb 14 22:29:01.651: INFO: kube-proxy-e2e-gce-builder-2-0-minion-qlb8 e2e-gce-builder-2-0-minion-qlb8 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:35 -0800 PST }]
Feb 14 22:29:01.651: INFO: kube-proxy-e2e-gce-builder-2-0-minion-s2tm e2e-gce-builder-2-0-minion-s2tm Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:38 -0800 PST }]
Feb 14 22:29:01.651: INFO: kubernetes-dashboard-v0.1.0-wzxv0 e2e-gce-builder-2-0-minion-lloc Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:51 -0800 PST }]
Feb 14 22:29:01.651: INFO: l7-lb-controller-1dba6 e2e-gce-builder-2-0-minion-64es Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:26:56 -0800 PST }]
Feb 14 22:29:01.651: INFO: monitoring-influxdb-grafana-v3-lo2u2 e2e-gce-builder-2-0-minion-bo4h Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-02-14 22:27:12 -0800 PST }]
Feb 14 22:29:01.651: INFO:
Feb 14 22:29:01.658: INFO:
Logging node info for node e2e-gce-builder-2-0-minion-43a8
Feb 14 22:29:01.675: INFO: Node Info: &{{ } {e2e-gce-builder-2-0-minion-43a8 /api/v1/nodes/e2e-gce-builder-2-0-minion-43a8 f0e7849f-d3ac-11e5-a51a-42010af00002 4118 0 2016-02-14 22:25:43 -0800 PST <nil> <nil> map[failure-domain.alpha.kubernetes.io/region:us-central1 failure-domain.alpha.kubernetes.io/zone:us-central1-f kubernetes.io/hostname:e2e-gce-builder-2-0-minion-43a8 beta.kubernetes.io/instance-type:n1-standard-2] map[]} {10.245.5.0/24 17041295563895084226 gce://kubernetes-jenkins-pull/us-central1-f/e2e-gce-builder-2-0-minion-43a8 false} {map[memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI} cpu:{2.000 DecimalSI}] map[cpu:{2.000 DecimalSI} memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI}] [{OutOfDisk False 2016-02-14 22:29:00 -0800 PST 2016-02-14 22:25:43 -0800 PST KubeletHasSufficientDisk kubelet has sufficient disk space available} {Ready True 2016-02-14 22:29:00 -0800 PST 2016-02-14 22:26:19 -0800 PST KubeletReady kubelet is posting ready status}] [{InternalIP 10.240.0.8} {ExternalIP 104.197.241.72}] {{10250}} { 2C7D58A8-D843-A5B0-5D92-DA52823CB342 b9ccff52-9a49-4e13-82d1-6db42ec1f178 3.16.0-4-amd64 Debian GNU/Linux 7 (wheezy) docker://1.9.1 v1.2.0-alpha.7.841+ac65cc782a86d6 v1.2.0-alpha.7.841+ac65cc782a86d6} [{[gcr.io/google_containers/kube-proxy:de983c4f408a7e53b0f8807e1ef9a0b0] 164588349} {[gcr.io/google_containers/heapster:v0.20.0-alpha6] 85929942} {[gcr.io/google_containers/nettest:1.7] 24051275} {[nginx:latest] 134581595} {[gcr.io/google_containers/fluentd-elasticsearch:1.14] 562034622} {[gcr.io/google_containers/netexec:1.4] 7297019} {[gcr.io/google_containers/fakegitserver:0.1] 5007469} {[gcr.io/google_containers/busybox:1.24] 1113554} {[gcr.io/google_containers/mounttest:0.6] 2084693} {[gcr.io/google_containers/mounttest-user:0.3] 1718853} {[gcr.io/google_containers/pause:2.0] 350164} {[gcr.io/google_containers/portforwardtester:1.0] 2296329} {[gcr.io/google_containers/jessie-dnsutils:latest] 190148402} {[gcr.io/google_containers/mounttest:0.2] 1752375} {[gcr.io/google_containers/dnsutils:latest] 141895666} {[gcr.io/google_containers/pause:0.8.0] 241656} {[b.gcr.io/k8s_authenticated_test/serve_hostname:1.1 gcr.io/google_containers/serve_hostname:1.1] 4522409} {[gcr.io/google_containers/test-webserver:latest] 4534272}]}}
Feb 14 22:29:01.675: INFO:
Logging kubelet events for node e2e-gce-builder-2-0-minion-43a8
Feb 14 22:29:01.687: INFO:
Logging pods the kubelet thinks is on node e2e-gce-builder-2-0-minion-43a8
Feb 14 22:29:01.700: INFO: nginx started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.700: INFO: pd-test-322d4b85-d3ad-11e5-82fd-42010af00003 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.700: INFO: dns-test-52483d00-d3ad-11e5-a4f1-42010af00003 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.700: INFO: heapster-v14-jfo48 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.700: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-43a8 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.700: INFO: kube-proxy-e2e-gce-builder-2-0-minion-43a8 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.802: INFO: ERROR kubelet_docker_errors{operation_type="info"} => 1 @[0]
Feb 14 22:29:01.802: INFO: ERROR kubelet_docker_errors{operation_type="inspect_image"} => 23 @[0]
Feb 14 22:29:01.803: INFO: ERROR kubelet_docker_errors{operation_type="list_containers"} => 32 @[0]
Feb 14 22:29:01.803: INFO: ERROR kubelet_docker_errors{operation_type="list_images"} => 5 @[0]
Feb 14 22:29:01.803: INFO: ERROR kubelet_docker_errors{operation_type="pull_image"} => 1 @[0]
Feb 14 22:29:01.803: INFO: ERROR kubelet_docker_errors{operation_type="stop_container"} => 7 @[0]
Feb 14 22:29:01.803: INFO: ERROR kubelet_docker_errors{operation_type="version"} => 22 @[0]
Feb 14 22:29:01.803: INFO:
Latency metrics for node e2e-gce-builder-2-0-minion-43a8
Feb 14 22:29:01.803: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:51.903836s}
Feb 14 22:29:01.803: INFO: {Operation: Method:pod_worker_start_latency_microseconds Quantile:0.99 Latency:35.065574s}
Feb 14 22:29:01.803: INFO: {Operation:stop_container Method:docker_operations_latency_microseconds Quantile:0.99 Latency:30.187015s}
Feb 14 22:29:01.803: INFO: {Operation:stop_container Method:docker_operations_latency_microseconds Quantile:0.9 Latency:30.072055s}
Feb 14 22:29:01.803: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:20.955617s}
Feb 14 22:29:01.803: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.99 Latency:20.299898s}
Feb 14 22:29:01.803: INFO: {Operation:SyncPod Method:container_manager_latency_microseconds Quantile:0.99 Latency:20.271071s}
Feb 14 22:29:01.803: INFO: {Operation:sync Method:pod_worker_latency_microseconds Quantile:0.99 Latency:19.612563s}
Feb 14 22:29:01.803: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.99 Latency:18.489781s}
Feb 14 22:29:01.803: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.9 Latency:18.35431s}
Feb 14 22:29:01.803: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.9 Latency:10.275054s}
Feb 14 22:29:01.803: INFO:
Logging node info for node e2e-gce-builder-2-0-minion-64es
Feb 14 22:29:01.812: INFO: Node Info: &{{ } {e2e-gce-builder-2-0-minion-64es /api/v1/nodes/e2e-gce-builder-2-0-minion-64es ecd16025-d3ac-11e5-a51a-42010af00002 4018 0 2016-02-14 22:25:36 -0800 PST <nil> <nil> map[beta.kubernetes.io/instance-type:n1-standard-2 failure-domain.alpha.kubernetes.io/region:us-central1 failure-domain.alpha.kubernetes.io/zone:us-central1-f kubernetes.io/hostname:e2e-gce-builder-2-0-minion-64es] map[]} {10.245.0.0/24 14005317376642251118 gce://kubernetes-jenkins-pull/us-central1-f/e2e-gce-builder-2-0-minion-64es false} {map[cpu:{2.000 DecimalSI} memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI}] map[cpu:{2.000 DecimalSI} memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI}] [{OutOfDisk False 2016-02-14 22:28:54 -0800 PST 2016-02-14 22:25:36 -0800 PST KubeletHasSufficientDisk kubelet has sufficient disk space available} {Ready True 2016-02-14 22:28:54 -0800 PST 2016-02-14 22:26:12 -0800 PST KubeletReady kubelet is posting ready status}] [{InternalIP 10.240.0.7} {ExternalIP 104.197.255.191}] {{10250}} { 26F65CB0-D3FD-B18E-8138-0AD8059AF12C 1e07dec8-fa5b-45ab-87b7-bac9f729e95b 3.16.0-4-amd64 Debian GNU/Linux 7 (wheezy) docker://1.9.1 v1.2.0-alpha.7.841+ac65cc782a86d6 v1.2.0-alpha.7.841+ac65cc782a86d6} [{[gcr.io/google_containers/kube-proxy:de983c4f408a7e53b0f8807e1ef9a0b0] 164588349} {[gcr.io/google_containers/nettest:1.7] 24051275} {[gcr.io/google_containers/fluentd-elasticsearch:1.14] 562034622} {[gcr.io/google_containers/netexec:1.4] 7297019} {[redis:latest] 151289204} {[gcr.io/google_containers/glbc:0.5.2] 226351998} {[gcr.io/google_containers/busybox:1.24] 1113554} {[gcr.io/google_containers/mounttest:0.6] 2084693} {[gcr.io/google_containers/hostexec:1.2] 13209617} {[gcr.io/google_containers/defaultbackend:1.0] 7513643} {[gcr.io/google_containers/mounttest:0.5] 1718853} {[gcr.io/google_containers/pause:2.0] 350164} {[gcr.io/google_containers/pause:0.8.0] 241656} {[gcr.io/google_containers/eptest:0.1] 2970692} {[gcr.io/google_containers/serve_hostname:1.1] 4522409} {[gcr.io/google_containers/update-demo:nautilus] 4555533} {[gcr.io/google_containers/test-webserver:latest] 4534272}]}}
Feb 14 22:29:01.812: INFO:
Logging kubelet events for node e2e-gce-builder-2-0-minion-64es
Feb 14 22:29:01.822: INFO:
Logging pods the kubelet thinks is on node e2e-gce-builder-2-0-minion-64es
Feb 14 22:29:01.923: INFO: downwardapi-volume-3516c9fc-d3ad-11e5-b7b8-42010af00003 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.923: INFO: l7-lb-controller-1dba6 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.923: INFO: mutability-test-94yvp started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.924: INFO: liveness-http started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.924: INFO: pod-configmaps-2edc829f-d3ad-11e5-8393-42010af00003 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.924: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-64es started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.924: INFO: kube-proxy-e2e-gce-builder-2-0-minion-64es started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.924: INFO: pd-test-322e11bc-d3ad-11e5-abad-42010af00003 started at <nil> (0 container statuses recorded)
Feb 14 22:29:01.924: INFO: pd-test-322d4bd8-d3ad-11e5-82fd-42010af00003 started at <nil> (0 container statuses recorded)
Feb 14 22:29:02.230: INFO: ERROR kubelet_docker_errors{operation_type="info"} => 1 @[0]
Feb 14 22:29:02.230: INFO: ERROR kubelet_docker_errors{operation_type="inspect_image"} => 20 @[0]
Feb 14 22:29:02.230: INFO: ERROR kubelet_docker_errors{operation_type="list_containers"} => 32 @[0]
Feb 14 22:29:02.230: INFO: ERROR kubelet_docker_errors{operation_type="list_images"} => 5 @[0]
Feb 14 22:29:02.230: INFO: ERROR kubelet_docker_errors{operation_type="pull_image"} => 1 @[0]
Feb 14 22:29:02.230: INFO: ERROR kubelet_docker_errors{operation_type="stop_container"} => 12 @[0]
Feb 14 22:29:02.230: INFO: ERROR kubelet_docker_errors{operation_type="version"} => 22 @[0]
Feb 14 22:29:02.230: INFO:
Latency metrics for node e2e-gce-builder-2-0-minion-64es
Feb 14 22:29:02.230: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:1m1.879215s}
Feb 14 22:29:02.230: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:35.02703s}
Feb 14 22:29:02.230: INFO: {Operation: Method:pod_worker_start_latency_microseconds Quantile:0.99 Latency:35.026932s}
Feb 14 22:29:02.231: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.99 Latency:28.569405s}
Feb 14 22:29:02.231: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.9 Latency:20.501721s}
Feb 14 22:29:02.231: INFO: {Operation:SyncPod Method:container_manager_latency_microseconds Quantile:0.99 Latency:20.4838s}
Feb 14 22:29:02.231: INFO: {Operation:sync Method:pod_worker_latency_microseconds Quantile:0.99 Latency:11.423451s}
Feb 14 22:29:02.231: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.99 Latency:11.138902s}
Feb 14 22:29:02.231: INFO:
Logging node info for node e2e-gce-builder-2-0-minion-bo4h
Feb 14 22:29:02.317: INFO: Node Info: &{{ } {e2e-gce-builder-2-0-minion-bo4h /api/v1/nodes/e2e-gce-builder-2-0-minion-bo4h ee19a4c8-d3ac-11e5-a51a-42010af00002 4098 0 2016-02-14 22:25:38 -0800 PST <nil> <nil> map[beta.kubernetes.io/instance-type:n1-standard-2 failure-domain.alpha.kubernetes.io/region:us-central1 failure-domain.alpha.kubernetes.io/zone:us-central1-f kubernetes.io/hostname:e2e-gce-builder-2-0-minion-bo4h] map[]} {10.245.2.0/24 9550812584030539242 gce://kubernetes-jenkins-pull/us-central1-f/e2e-gce-builder-2-0-minion-bo4h false} {map[memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI} cpu:{2.000 DecimalSI}] map[pods:{110.000 DecimalSI} cpu:{2.000 DecimalSI} memory:{7864139776.000 BinarySI}] [{OutOfDisk False 2016-02-14 22:28:57 -0800 PST 2016-02-14 22:25:38 -0800 PST KubeletHasSufficientDisk kubelet has sufficient disk space available} {Ready True 2016-02-14 22:28:57 -0800 PST 2016-02-14 22:26:16 -0800 PST KubeletReady kubelet is posting ready status}] [{InternalIP 10.240.0.4} {ExternalIP 104.197.242.28}] {{10250}} { 46A6AB8D-5EA9-904C-891F-88F72D6ECEBD e5e73f32-d546-44dd-82cf-174505489c34 3.16.0-4-amd64 Debian GNU/Linux 7 (wheezy) docker://1.9.1 v1.2.0-alpha.7.841+ac65cc782a86d6 v1.2.0-alpha.7.841+ac65cc782a86d6} [{[gcr.io/google_containers/kube-proxy:de983c4f408a7e53b0f8807e1ef9a0b0] 164588349} {[gcr.io/google_containers/nettest:1.7] 24051275} {[gcr.io/google_containers/fluentd-elasticsearch:1.14] 562034622} {[busybox:latest gcr.io/google_containers/busybox:1.24] 1113554} {[gcr.io/google_containers/mounttest:0.6] 2084693} {[gcr.io/google_containers/hostexec:1.2] 13209617} {[gcr.io/google_containers/mounttest:0.5] 1718853} {[gcr.io/google_containers/heapster_grafana:v2.1.1] 206641132} {[gcr.io/google_containers/pause:2.0] 350164} {[gcr.io/google_containers/porter:cd5cb5791ebaa8641955f0e8c2a9bed669b1eaab] 5010921} {[gcr.io/google_containers/heapster_influxdb:v0.5] 251005705} {[gcr.io/google_containers/jessie-dnsutils:latest] 190148402} {[gcr.io/google_containers/dnsutils:latest] 141895666} {[gcr.io/google_containers/pause:0.8.0] 241656} {[gcr.io/google_containers/serve_hostname:1.1] 4522409} {[gcr.io/google_containers/update-demo:nautilus] 4555533} {[gcr.io/google_containers/nginx:1.7.9] 91664166} {[gcr.io/google_containers/test-webserver:latest] 4534272}]}}
Feb 14 22:29:02.317: INFO:
Logging kubelet events for node e2e-gce-builder-2-0-minion-bo4h
Feb 14 22:29:02.523: INFO:
Logging pods the kubelet thinks is on node e2e-gce-builder-2-0-minion-bo4h
Feb 14 22:29:02.723: INFO: hostexec started at <nil> (0 container statuses recorded)
Feb 14 22:29:02.723: INFO: proxy-service-n6w5j-exzdq started at <nil> (0 container statuses recorded)
Feb 14 22:29:02.723: INFO: monitoring-influxdb-grafana-v3-lo2u2 started at <nil> (0 container statuses recorded)
Feb 14 22:29:02.723: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-bo4h started at <nil> (0 container statuses recorded)
Feb 14 22:29:02.723: INFO: kube-proxy-e2e-gce-builder-2-0-minion-bo4h started at <nil> (0 container statuses recorded)
Feb 14 22:29:02.723: INFO: update-demo-nautilus-vn45c started at <nil> (0 container statuses recorded)
Feb 14 22:29:03.020: INFO: ERROR kubelet_docker_errors{operation_type="info"} => 1 @[0]
Feb 14 22:29:03.020: INFO: ERROR kubelet_docker_errors{operation_type="inspect_image"} => 20 @[0]
Feb 14 22:29:03.020: INFO: ERROR kubelet_docker_errors{operation_type="list_containers"} => 32 @[0]
Feb 14 22:29:03.020: INFO: ERROR kubelet_docker_errors{operation_type="list_images"} => 5 @[0]
Feb 14 22:29:03.020: INFO: ERROR kubelet_docker_errors{operation_type="pull_image"} => 1 @[0]
Feb 14 22:29:03.020: INFO: ERROR kubelet_docker_errors{operation_type="stop_container"} => 9 @[0]
Feb 14 22:29:03.020: INFO: ERROR kubelet_docker_errors{operation_type="version"} => 22 @[0]
Feb 14 22:29:03.020: INFO:
Latency metrics for node e2e-gce-builder-2-0-minion-bo4h
Feb 14 22:29:03.020: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:49.794469s}
Feb 14 22:29:03.020: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.99 Latency:36.497124s}
Feb 14 22:29:03.020: INFO: {Operation:SyncPod Method:container_manager_latency_microseconds Quantile:0.99 Latency:36.487992s}
Feb 14 22:29:03.020: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:35.03492s}
Feb 14 22:29:03.020: INFO: {Operation: Method:pod_worker_start_latency_microseconds Quantile:0.99 Latency:35.034832s}
Feb 14 22:29:03.020: INFO: {Operation:stop_container Method:docker_operations_latency_microseconds Quantile:0.99 Latency:30.119192s}
Feb 14 22:29:03.020: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.99 Latency:25.025646s}
Feb 14 22:29:03.020: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.9 Latency:20.460683s}
Feb 14 22:29:03.020: INFO: {Operation:sync Method:pod_worker_latency_microseconds Quantile:0.99 Latency:11.826527s}
Feb 14 22:29:03.020: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.9 Latency:11.401707s}
Feb 14 22:29:03.020: INFO:
Logging node info for node e2e-gce-builder-2-0-minion-lloc
Feb 14 22:29:03.116: INFO: Node Info: &{{ } {e2e-gce-builder-2-0-minion-lloc /api/v1/nodes/e2e-gce-builder-2-0-minion-lloc ee85f672-d3ac-11e5-a51a-42010af00002 4064 0 2016-02-14 22:25:39 -0800 PST <nil> <nil> map[beta.kubernetes.io/instance-type:n1-standard-2 failure-domain.alpha.kubernetes.io/region:us-central1 failure-domain.alpha.kubernetes.io/zone:us-central1-f kubernetes.io/hostname:e2e-gce-builder-2-0-minion-lloc] map[]} {10.245.3.0/24 10789933251084181977 gce://kubernetes-jenkins-pull/us-central1-f/e2e-gce-builder-2-0-minion-lloc false} {map[cpu:{2.000 DecimalSI} memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI}] map[memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI} cpu:{2.000 DecimalSI}] [{OutOfDisk False 2016-02-14 22:28:56 -0800 PST 2016-02-14 22:25:39 -0800 PST KubeletHasSufficientDisk kubelet has sufficient disk space available} {Ready True 2016-02-14 22:28:56 -0800 PST 2016-02-14 22:26:14 -0800 PST KubeletReady kubelet is posting ready status}] [{InternalIP 10.240.0.6} {ExternalIP 104.197.253.82}] {{10250}} { 1FAA9E19-7503-D8E7-AC9A-CAA9E15742D5 a4767d54-3ea1-41af-a647-89f99ad67407 3.16.0-4-amd64 Debian GNU/Linux 7 (wheezy) docker://1.9.1 v1.2.0-alpha.7.841+ac65cc782a86d6 v1.2.0-alpha.7.841+ac65cc782a86d6} [{[gcr.io/google_containers/kube-proxy:de983c4f408a7e53b0f8807e1ef9a0b0] 164588349} {[gcr.io/google_containers/nettest:1.7] 24051275} {[nginx:latest] 134581595} {[gcr.io/google_containers/fluentd-elasticsearch:1.14] 562034622} {[gcr.io/google_containers/kubernetes-dashboard-amd64:v0.1.0] 35409795} {[gcr.io/google_containers/netexec:1.4] 7297019} {[redis:latest] 151289204} {[gcr.io/google_containers/busybox:1.24] 1113554} {[gcr.io/google_containers/kube2sky:1.12] 24482187} {[gcr.io/google_containers/skydns:2015-10-13-8c72f8c] 40551394} {[gcr.io/google_containers/pause:2.0] 350164} {[gcr.io/google_containers/exechealthz:1.0] 7099444} {[gcr.io/google_containers/etcd:2.0.9] 12819040} {[gcr.io/google_containers/pause:0.8.0] 241656} {[gcr.io/google_containers/serve_hostname:1.1] 4522409} {[gcr.io/google_containers/nginx:1.7.9] 91664166}]}}
Feb 14 22:29:03.117: INFO:
Logging kubelet events for node e2e-gce-builder-2-0-minion-lloc
Feb 14 22:29:03.324: INFO:
Logging pods the kubelet thinks is on node e2e-gce-builder-2-0-minion-lloc
Feb 14 22:29:03.526: INFO: mutability-test-pyldw started at <nil> (0 container statuses recorded)
Feb 14 22:29:03.526: INFO: kube-dns-v10-lh264 started at <nil> (0 container statuses recorded)
Feb 14 22:29:03.526: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-lloc started at <nil> (0 container statuses recorded)
Feb 14 22:29:03.526: INFO: kubernetes-dashboard-v0.1.0-wzxv0 started at <nil> (0 container statuses recorded)
Feb 14 22:29:03.526: INFO: kube-proxy-e2e-gce-builder-2-0-minion-lloc started at <nil> (0 container statuses recorded)
Feb 14 22:29:03.803: INFO: ERROR kubelet_docker_errors{operation_type="info"} => 1 @[0]
Feb 14 22:29:03.803: INFO: ERROR kubelet_docker_errors{operation_type="inspect_image"} => 18 @[0]
Feb 14 22:29:03.803: INFO: ERROR kubelet_docker_errors{operation_type="list_containers"} => 32 @[0]
Feb 14 22:29:03.803: INFO: ERROR kubelet_docker_errors{operation_type="list_images"} => 5 @[0]
Feb 14 22:29:03.803: INFO: ERROR kubelet_docker_errors{operation_type="pull_image"} => 1 @[0]
Feb 14 22:29:03.803: INFO: ERROR kubelet_docker_errors{operation_type="stop_container"} => 7 @[0]
Feb 14 22:29:03.803: INFO: ERROR kubelet_docker_errors{operation_type="version"} => 22 @[0]
Feb 14 22:29:03.803: INFO:
Latency metrics for node e2e-gce-builder-2-0-minion-lloc
Feb 14 22:29:03.803: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:50.664034s}
Feb 14 22:29:03.803: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:35.064854s}
Feb 14 22:29:03.803: INFO: {Operation: Method:pod_worker_start_latency_microseconds Quantile:0.99 Latency:35.064743s}
Feb 14 22:29:03.803: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.99 Latency:22.179206s}
Feb 14 22:29:03.803: INFO: {Operation:SyncPod Method:container_manager_latency_microseconds Quantile:0.99 Latency:22.167655s}
Feb 14 22:29:03.803: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.9 Latency:15.237909s}
Feb 14 22:29:03.803: INFO: {Operation:sync Method:pod_worker_latency_microseconds Quantile:0.99 Latency:14.464511s}
Feb 14 22:29:03.803: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.99 Latency:14.253852s}
Feb 14 22:29:03.803: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.9 Latency:13.393135s}
Feb 14 22:29:03.803: INFO:
Logging node info for node e2e-gce-builder-2-0-minion-qlb8
Feb 14 22:29:03.917: INFO: Node Info: &{{ } {e2e-gce-builder-2-0-minion-qlb8 /api/v1/nodes/e2e-gce-builder-2-0-minion-qlb8 ece12aa8-d3ac-11e5-a51a-42010af00002 4040 0 2016-02-14 22:25:36 -0800 PST <nil> <nil> map[kubernetes.io/hostname:e2e-gce-builder-2-0-minion-qlb8 beta.kubernetes.io/instance-type:n1-standard-2 failure-domain.alpha.kubernetes.io/region:us-central1 failure-domain.alpha.kubernetes.io/zone:us-central1-f] map[]} {10.245.1.0/24 11535097332819972334 gce://kubernetes-jenkins-pull/us-central1-f/e2e-gce-builder-2-0-minion-qlb8 false} {map[cpu:{2.000 DecimalSI} memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI}] map[cpu:{2.000 DecimalSI} memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI}] [{OutOfDisk False 2016-02-14 22:28:55 -0800 PST 2016-02-14 22:25:36 -0800 PST KubeletHasSufficientDisk kubelet has sufficient disk space available} {Ready True 2016-02-14 22:28:55 -0800 PST 2016-02-14 22:26:13 -0800 PST KubeletReady kubelet is posting ready status}] [{InternalIP 10.240.0.5} {ExternalIP 104.197.238.173}] {{10250}} { 91ACE89F-D1E2-F446-FC9D-7EB4FAA6B102 14adb070-84c7-4e11-ab64-c947160e5a02 3.16.0-4-amd64 Debian GNU/Linux 7 (wheezy) docker://1.9.1 v1.2.0-alpha.7.841+ac65cc782a86d6 v1.2.0-alpha.7.841+ac65cc782a86d6} [{[gcr.io/google_containers/kube-proxy:de983c4f408a7e53b0f8807e1ef9a0b0] 164588349} {[gcr.io/google_containers/nettest:1.7] 24051275} {[nginx:latest] 134581595} {[gcr.io/google_containers/fluentd-elasticsearch:1.14] 562034622} {[gcr.io/google_containers/netexec:1.4] 7297019} {[redis:latest] 151289204} {[gcr.io/google_containers/busybox:1.24 busybox:latest] 1113554} {[gcr.io/google_containers/elasticsearch:1.8] 410989305} {[gcr.io/google_containers/mounttest:0.6] 2084693} {[gcr.io/google_containers/hostexec:1.2] 13209617} {[gcr.io/google_containers/mounttest-user:0.3] 1718853} {[gcr.io/google_containers/mounttest:0.5] 1718853} {[gcr.io/google_containers/pause:2.0] 350164} {[gcr.io/google_containers/portforwardtester:1.0] 2296329} {[gcr.io/google_containers/pause:0.8.0] 241656} {[gcr.io/google_containers/eptest:0.1] 2970692} {[b.gcr.io/k8s_authenticated_test/serve_hostname:1.1 gcr.io/google_containers/serve_hostname:1.1] 4522409} {[gcr.io/google_containers/update-demo:nautilus] 4555533} {[gcr.io/google_containers/test-webserver:latest] 4534272}]}}
Feb 14 22:29:03.917: INFO:
Logging kubelet events for node e2e-gce-builder-2-0-minion-qlb8
Feb 14 22:29:04.121: INFO:
Logging pods the kubelet thinks is on node e2e-gce-builder-2-0-minion-qlb8
Feb 14 22:29:04.324: INFO: run-test-3-vl7eh started at <nil> (0 container statuses recorded)
Feb 14 22:29:04.324: INFO: liveness-exec started at <nil> (0 container statuses recorded)
Feb 14 22:29:04.324: INFO: elasticsearch-logging-v1-xhinl started at <nil> (0 container statuses recorded)
Feb 14 22:29:04.324: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-qlb8 started at <nil> (0 container statuses recorded)
Feb 14 22:29:04.324: INFO: kube-proxy-e2e-gce-builder-2-0-minion-qlb8 started at <nil> (0 container statuses recorded)
Feb 14 22:29:04.324: INFO: update-demo-kitten-cr05m started at <nil> (0 container statuses recorded)
Feb 14 22:29:04.324: INFO: foo-yswqv started at <nil> (0 container statuses recorded)
Feb 14 22:29:04.324: INFO: update-demo-nautilus-q2jms started at <nil> (0 container statuses recorded)
Feb 14 22:29:04.658: INFO: ERROR kubelet_docker_errors{operation_type="info"} => 1 @[0]
Feb 14 22:29:04.659: INFO: ERROR kubelet_docker_errors{operation_type="inspect_image"} => 24 @[0]
Feb 14 22:29:04.659: INFO: ERROR kubelet_docker_errors{operation_type="list_containers"} => 31 @[0]
Feb 14 22:29:04.659: INFO: ERROR kubelet_docker_errors{operation_type="list_images"} => 5 @[0]
Feb 14 22:29:04.659: INFO: ERROR kubelet_docker_errors{operation_type="pull_image"} => 1 @[0]
Feb 14 22:29:04.659: INFO: ERROR kubelet_docker_errors{operation_type="stop_container"} => 21 @[0]
Feb 14 22:29:04.659: INFO: ERROR kubelet_docker_errors{operation_type="version"} => 22 @[0]
Feb 14 22:29:04.659: INFO:
Latency metrics for node e2e-gce-builder-2-0-minion-qlb8
Feb 14 22:29:04.659: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:53.380754s}
Feb 14 22:29:04.659: INFO: {Operation: Method:pod_worker_start_latency_microseconds Quantile:0.99 Latency:35.023248s}
Feb 14 22:29:04.659: INFO: {Operation:sync Method:pod_worker_latency_microseconds Quantile:0.99 Latency:30.19793s}
Feb 14 22:29:04.659: INFO: {Operation:stop_container Method:docker_operations_latency_microseconds Quantile:0.99 Latency:30.065551s}
Feb 14 22:29:04.659: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.99 Latency:30.019178s}
Feb 14 22:29:04.659: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.99 Latency:28.806406s}
Feb 14 22:29:04.659: INFO: {Operation:SyncPod Method:container_manager_latency_microseconds Quantile:0.99 Latency:18.393164s}
Feb 14 22:29:04.659: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:16.179337s}
Feb 14 22:29:04.659: INFO:
Logging node info for node e2e-gce-builder-2-0-minion-s2tm
Feb 14 22:29:04.717: INFO: Node Info: &{{ } {e2e-gce-builder-2-0-minion-s2tm /api/v1/nodes/e2e-gce-builder-2-0-minion-s2tm eddbdf1f-d3ac-11e5-a51a-42010af00002 4065 0 2016-02-14 22:25:38 -0800 PST <nil> <nil> map[kubernetes.io/hostname:e2e-gce-builder-2-0-minion-s2tm beta.kubernetes.io/instance-type:n1-standard-2 failure-domain.alpha.kubernetes.io/region:us-central1 failure-domain.alpha.kubernetes.io/zone:us-central1-f] map[]} {10.245.4.0/24 3822123003318812276 gce://kubernetes-jenkins-pull/us-central1-f/e2e-gce-builder-2-0-minion-s2tm false} {map[memory:{7864139776.000 BinarySI} pods:{110.000 DecimalSI} cpu:{2.000 DecimalSI}] map[pods:{110.000 DecimalSI} cpu:{2.000 DecimalSI} memory:{7864139776.000 BinarySI}] [{OutOfDisk False 2016-02-14 22:28:56 -0800 PST 2016-02-14 22:25:38 -0800 PST KubeletHasSufficientDisk kubelet has sufficient disk space available} {Ready True 2016-02-14 22:28:56 -0800 PST 2016-02-14 22:26:14 -0800 PST KubeletReady kubelet is posting ready status}] [{InternalIP 10.240.0.3} {ExternalIP 104.154.75.54}] {{10250}} { A996ECE6-745A-EE76-876D-08D85C5D0136 d8bbbc85-9561-4ea7-b056-c4ae3e0be4da 3.16.0-4-amd64 Debian GNU/Linux 7 (wheezy) docker://1.9.1 v1.2.0-alpha.7.841+ac65cc782a86d6 v1.2.0-alpha.7.841+ac65cc782a86d6} [{[gcr.io/google_containers/kube-proxy:de983c4f408a7e53b0f8807e1ef9a0b0] 164588349} {[gcr.io/google_containers/nettest:1.7] 24051275} {[nginx:latest] 134581595} {[gcr.io/google_containers/fluentd-elasticsearch:1.14] 562034622} {[gcr.io/google_containers/netexec:1.4] 7297019} {[redis:latest] 151289204} {[gcr.io/google_containers/busybox:1.24 busybox:latest] 1113554} {[gcr.io/google_containers/elasticsearch:1.8] 410989305} {[gcr.io/google_containers/mounttest:0.6] 2084693} {[gcr.io/google_containers/mounttest:0.5] 1718853} {[gcr.io/google_containers/pause:2.0] 350164} {[gcr.io/google_containers/kibana:1.3] 396897764} {[gcr.io/google_containers/pause:0.8.0] 241656} {[b.gcr.io/k8s_authenticated_test/serve_hostname:1.1 gcr.io/google_containers/serve_hostname:1.1] 4522409} {[gcr.io/google_containers/update-demo:nautilus] 4555533} {[gcr.io/google_containers/update-demo:kitten] 4549069} {[gcr.io/google_containers/nginx:1.7.9] 91664166}]}}
Feb 14 22:29:04.717: INFO:
Logging kubelet events for node e2e-gce-builder-2-0-minion-s2tm
Feb 14 22:29:04.923: INFO:
Logging pods the kubelet thinks is on node e2e-gce-builder-2-0-minion-s2tm
Feb 14 22:29:05.122: INFO: foo-63zhd started at <nil> (0 container statuses recorded)
Feb 14 22:29:05.122: INFO: update-demo-kitten-15bfi started at <nil> (0 container statuses recorded)
Feb 14 22:29:05.122: INFO: kibana-logging-v1-yurqd started at <nil> (0 container statuses recorded)
Feb 14 22:29:05.122: INFO: elasticsearch-logging-v1-8a3oc started at <nil> (0 container statuses recorded)
Feb 14 22:29:05.123: INFO: fluentd-elasticsearch-e2e-gce-builder-2-0-minion-s2tm started at <nil> (0 container statuses recorded)
Feb 14 22:29:05.123: INFO: kube-proxy-e2e-gce-builder-2-0-minion-s2tm started at <nil> (0 container statuses recorded)
Feb 14 22:29:05.418: INFO: ERROR kubelet_docker_errors{operation_type="info"} => 1 @[0]
Feb 14 22:29:05.418: INFO: ERROR kubelet_docker_errors{operation_type="inspect_image"} => 21 @[0]
Feb 14 22:29:05.418: INFO: ERROR kubelet_docker_errors{operation_type="list_containers"} => 32 @[0]
Feb 14 22:29:05.418: INFO: ERROR kubelet_docker_errors{operation_type="list_images"} => 5 @[0]
Feb 14 22:29:05.418: INFO: ERROR kubelet_docker_errors{operation_type="logs"} => 1 @[0]
Feb 14 22:29:05.418: INFO: ERROR kubelet_docker_errors{operation_type="pull_image"} => 1 @[0]
Feb 14 22:29:05.418: INFO: ERROR kubelet_docker_errors{operation_type="stop_container"} => 16 @[0]
Feb 14 22:29:05.418: INFO: ERROR kubelet_docker_errors{operation_type="version"} => 22 @[0]
Feb 14 22:29:05.418: INFO:
Latency metrics for node e2e-gce-builder-2-0-minion-s2tm
Feb 14 22:29:05.418: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:54.3937s}
Feb 14 22:29:05.418: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.99 Latency:46.94785s}
Feb 14 22:29:05.418: INFO: {Operation:SyncPod Method:container_manager_latency_microseconds Quantile:0.99 Latency:46.933443s}
Feb 14 22:29:05.418: INFO: {Operation:sync Method:pod_worker_latency_microseconds Quantile:0.99 Latency:46.724749s}
Feb 14 22:29:05.418: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.99 Latency:45.137388s}
Feb 14 22:29:05.418: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.9 Latency:43.134663s}
Feb 14 22:29:05.419: INFO: {Operation: Method:pod_worker_start_latency_microseconds Quantile:0.99 Latency:35.117599s}
Feb 14 22:29:05.419: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:33.538877s}
Feb 14 22:29:05.419: INFO: {Operation:stop_container Method:docker_operations_latency_microseconds Quantile:0.99 Latency:30.083542s}
Feb 14 22:29:05.419: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.9 Latency:21.043204s}
STEP: Destroying namespace "e2e-tests-configmap-iibco" for this suite.
Feb 14 22:29:05.916: INFO: Waiting up to 1m0s for all nodes to be ready
• Failure [100.958 seconds]
ConfigMap
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/configmap.go:332
updates should be reflected in volume [Conformance] [It]
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/configmap.go:271
Timed out after 90.000s.
Expected
<string>: content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
content of file "/etc/configmap-volume/data-1": value-1
to contain substring
<string>: value-2
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/configmap.go:270
------------------------------
``` | priority | flake configmap updates should be reflected in volume timed out test logs at configmap go src io kubernetes output dockerized go src io kubernetes test framework go step creating a kubernetes client feb info testcontext kubeconfig var lib jenkins workspace kubernetes pull build test gce kube config step building a namespace api object feb info waiting up to for service account default to be provisioned in ns tests configmap iibco feb info get service account default in ns tests configmap iibco failed ignoring for serviceaccounts default not found feb info service account default in ns tests configmap iibco with secrets found step waiting for a default service account to be provisioned in namespace feb info waiting up to for service account default to be provisioned in ns tests configmap iibco feb info service account default in ns tests configmap iibco with secrets found updates should be reflected in volume go src io kubernetes output dockerized go src io kubernetes test configmap go step creating configmap with name configmap test upd step creating the pod feb info waiting up to for pod pod configmaps status to be running feb info waiting for pod pod configmaps in namespace tests configmap iibco status to be running found phase pending readiness false elapsed feb info waiting for pod pod configmaps in namespace tests configmap iibco status to be running found phase pending readiness false elapsed feb info found pod pod configmaps on node gce builder minion step updating configmap configmap test upd step deleting the pod step cleaning up the configmap configmap go src io kubernetes output dockerized go src io kubernetes test framework go step collecting events from namespace tests configmap iibco feb info event for pod configmaps default scheduler scheduled successfully assigned pod configmaps to gce builder minion feb info event for pod configmaps kubelet gce builder minion pulling pulling image gcr io google containers mounttest feb info event for pod configmaps kubelet gce builder minion pulled successfully pulled image gcr io google containers mounttest feb info event for pod configmaps kubelet gce builder minion created created container with docker id feb info event for pod configmaps kubelet gce builder minion started started container with docker id feb info pod node phase grace conditions feb info downwardapi volume gce builder minion running feb info foo yswqv gce builder minion running feb info update demo kitten gce builder minion running feb info update demo kitten gce builder minion pending feb info nginx gce builder minion running feb info update demo nautilus gce builder minion running feb info update demo nautilus gce builder minion running feb info liveness exec gce builder minion running feb info liveness http gce builder minion running feb info proxy service exzdq gce builder minion running feb info mutability test pyldw gce builder minion lloc running feb info mutability test gce builder minion running feb info elasticsearch logging gce builder minion running feb info elasticsearch logging xhinl gce builder minion running feb info fluentd elasticsearch gce builder minion gce builder minion running feb info fluentd elasticsearch gce builder minion gce builder minion running feb info fluentd elasticsearch gce builder minion gce builder minion running feb info fluentd elasticsearch gce builder minion lloc gce builder minion lloc running feb info fluentd elasticsearch gce builder minion gce builder minion running feb info fluentd elasticsearch gce builder minion gce builder minion running feb info heapster gce builder minion running feb info kibana logging yurqd gce builder minion running feb info kube dns gce builder minion lloc running feb info kube proxy gce builder minion gce builder minion running feb info kube proxy gce builder minion gce builder minion running feb info kube proxy gce builder minion gce builder minion running feb info kube proxy gce builder minion lloc gce builder minion lloc running feb info kube proxy gce builder minion gce builder minion running feb info kube proxy gce builder minion gce builder minion running feb info kubernetes dashboard gce builder minion lloc running feb info lb controller gce builder minion running feb info monitoring influxdb grafana gce builder minion running feb info feb info logging node info for node gce builder minion feb info node info gce builder minion api nodes gce builder minion pst map map gce kubernetes jenkins pull us f gce builder minion false map map debian gnu linux wheezy docker alpha alpha feb info logging kubelet events for node gce builder minion feb info logging pods the kubelet thinks is on node gce builder minion feb info nginx started at container statuses recorded feb info pd test started at container statuses recorded feb info dns test started at container statuses recorded feb info heapster started at container statuses recorded feb info fluentd elasticsearch gce builder minion started at container statuses recorded feb info kube proxy gce builder minion started at container statuses recorded feb info error kubelet docker errors operation type info feb info error kubelet docker errors operation type inspect image feb info error kubelet docker errors operation type list containers feb info error kubelet docker errors operation type list images feb info error kubelet docker errors operation type pull image feb info error kubelet docker errors operation type stop container feb info error kubelet docker errors operation type version feb info latency metrics for node gce builder minion feb info operation method pod start latency microseconds quantile latency feb info operation method pod worker start latency microseconds quantile latency feb info operation stop container method docker operations latency microseconds quantile latency feb info operation stop container method docker operations latency microseconds quantile latency feb info operation method pod start latency microseconds quantile latency feb info operation create method pod worker latency microseconds quantile latency feb info operation syncpod method container manager latency microseconds quantile latency feb info operation sync method pod worker latency microseconds quantile latency feb info operation pull image method docker operations latency microseconds quantile latency feb info operation create method pod worker latency microseconds quantile latency feb info operation pull image method docker operations latency microseconds quantile latency feb info logging node info for node gce builder minion feb info node info gce builder minion api nodes gce builder minion pst map map gce kubernetes jenkins pull us f gce builder minion false map map debian gnu linux wheezy docker alpha alpha feb info logging kubelet events for node gce builder minion feb info logging pods the kubelet thinks is on node gce builder minion feb info downwardapi volume started at container statuses recorded feb info lb controller started at container statuses recorded feb info mutability test started at container statuses recorded feb info liveness http started at container statuses recorded feb info pod configmaps started at container statuses recorded feb info fluentd elasticsearch gce builder minion started at container statuses recorded feb info kube proxy gce builder minion started at container statuses recorded feb info pd test abad started at container statuses recorded feb info pd test started at container statuses recorded feb info error kubelet docker errors operation type info feb info error kubelet docker errors operation type inspect image feb info error kubelet docker errors operation type list containers feb info error kubelet docker errors operation type list images feb info error kubelet docker errors operation type pull image feb info error kubelet docker errors operation type stop container feb info error kubelet docker errors operation type version feb info latency metrics for node gce builder minion feb info operation method pod start latency microseconds quantile latency feb info operation method pod start latency microseconds quantile latency feb info operation method pod worker start latency microseconds quantile latency feb info operation create method pod worker latency microseconds quantile latency feb info operation create method pod worker latency microseconds quantile latency feb info operation syncpod method container manager latency microseconds quantile latency feb info operation sync method pod worker latency microseconds quantile latency feb info operation pull image method docker operations latency microseconds quantile latency feb info logging node info for node gce builder minion feb info node info gce builder minion api nodes gce builder minion pst map map gce kubernetes jenkins pull us f gce builder minion false map map debian gnu linux wheezy docker alpha alpha feb info logging kubelet events for node gce builder minion feb info logging pods the kubelet thinks is on node gce builder minion feb info hostexec started at container statuses recorded feb info proxy service exzdq started at container statuses recorded feb info monitoring influxdb grafana started at container statuses recorded feb info fluentd elasticsearch gce builder minion started at container statuses recorded feb info kube proxy gce builder minion started at container statuses recorded feb info update demo nautilus started at container statuses recorded feb info error kubelet docker errors operation type info feb info error kubelet docker errors operation type inspect image feb info error kubelet docker errors operation type list containers feb info error kubelet docker errors operation type list images feb info error kubelet docker errors operation type pull image feb info error kubelet docker errors operation type stop container feb info error kubelet docker errors operation type version feb info latency metrics for node gce builder minion feb info operation method pod start latency microseconds quantile latency feb info operation create method pod worker latency microseconds quantile latency feb info operation syncpod method container manager latency microseconds quantile latency feb info operation method pod start latency microseconds quantile latency feb info operation method pod worker start latency microseconds quantile latency feb info operation stop container method docker operations latency microseconds quantile latency feb info operation pull image method docker operations latency microseconds quantile latency feb info operation create method pod worker latency microseconds quantile latency feb info operation sync method pod worker latency microseconds quantile latency feb info operation pull image method docker operations latency microseconds quantile latency feb info logging node info for node gce builder minion lloc feb info node info gce builder minion lloc api nodes gce builder minion lloc pst map map gce kubernetes jenkins pull us f gce builder minion lloc false map map debian gnu linux wheezy docker alpha alpha feb info logging kubelet events for node gce builder minion lloc feb info logging pods the kubelet thinks is on node gce builder minion lloc feb info mutability test pyldw started at container statuses recorded feb info kube dns started at container statuses recorded feb info fluentd elasticsearch gce builder minion lloc started at container statuses recorded feb info kubernetes dashboard started at container statuses recorded feb info kube proxy gce builder minion lloc started at container statuses recorded feb info error kubelet docker errors operation type info feb info error kubelet docker errors operation type inspect image feb info error kubelet docker errors operation type list containers feb info error kubelet docker errors operation type list images feb info error kubelet docker errors operation type pull image feb info error kubelet docker errors operation type stop container feb info error kubelet docker errors operation type version feb info latency metrics for node gce builder minion lloc feb info operation method pod start latency microseconds quantile latency feb info operation method pod start latency microseconds quantile latency feb info operation method pod worker start latency microseconds quantile latency feb info operation create method pod worker latency microseconds quantile latency feb info operation syncpod method container manager latency microseconds quantile latency feb info operation create method pod worker latency microseconds quantile latency feb info operation sync method pod worker latency microseconds quantile latency feb info operation pull image method docker operations latency microseconds quantile latency feb info operation pull image method docker operations latency microseconds quantile latency feb info logging node info for node gce builder minion feb info node info gce builder minion api nodes gce builder minion pst map map gce kubernetes jenkins pull us f gce builder minion false map map debian gnu linux wheezy docker alpha alpha feb info logging kubelet events for node gce builder minion feb info logging pods the kubelet thinks is on node gce builder minion feb info run test started at container statuses recorded feb info liveness exec started at container statuses recorded feb info elasticsearch logging xhinl started at container statuses recorded feb info fluentd elasticsearch gce builder minion started at container statuses recorded feb info kube proxy gce builder minion started at container statuses recorded feb info update demo kitten started at container statuses recorded feb info foo yswqv started at container statuses recorded feb info update demo nautilus started at container statuses recorded feb info error kubelet docker errors operation type info feb info error kubelet docker errors operation type inspect image feb info error kubelet docker errors operation type list containers feb info error kubelet docker errors operation type list images feb info error kubelet docker errors operation type pull image feb info error kubelet docker errors operation type stop container feb info error kubelet docker errors operation type version feb info latency metrics for node gce builder minion feb info operation method pod start latency microseconds quantile latency feb info operation method pod worker start latency microseconds quantile latency feb info operation sync method pod worker latency microseconds quantile latency feb info operation stop container method docker operations latency microseconds quantile latency feb info operation create method pod worker latency microseconds quantile latency feb info operation pull image method docker operations latency microseconds quantile latency feb info operation syncpod method container manager latency microseconds quantile latency feb info operation method pod start latency microseconds quantile latency feb info logging node info for node gce builder minion feb info node info gce builder minion api nodes gce builder minion pst map map gce kubernetes jenkins pull us f gce builder minion false map map debian gnu linux wheezy docker alpha alpha feb info logging kubelet events for node gce builder minion feb info logging pods the kubelet thinks is on node gce builder minion feb info foo started at container statuses recorded feb info update demo kitten started at container statuses recorded feb info kibana logging yurqd started at container statuses recorded feb info elasticsearch logging started at container statuses recorded feb info fluentd elasticsearch gce builder minion started at container statuses recorded feb info kube proxy gce builder minion started at container statuses recorded feb info error kubelet docker errors operation type info feb info error kubelet docker errors operation type inspect image feb info error kubelet docker errors operation type list containers feb info error kubelet docker errors operation type list images feb info error kubelet docker errors operation type logs feb info error kubelet docker errors operation type pull image feb info error kubelet docker errors operation type stop container feb info error kubelet docker errors operation type version feb info latency metrics for node gce builder minion feb info operation method pod start latency microseconds quantile latency feb info operation create method pod worker latency microseconds quantile latency feb info operation syncpod method container manager latency microseconds quantile latency feb info operation sync method pod worker latency microseconds quantile latency feb info operation pull image method docker operations latency microseconds quantile latency feb info operation pull image method docker operations latency microseconds quantile latency feb info operation method pod worker start latency microseconds quantile latency feb info operation method pod start latency microseconds quantile latency feb info operation stop container method docker operations latency microseconds quantile latency feb info operation create method pod worker latency microseconds quantile latency step destroying namespace tests configmap iibco for this suite feb info waiting up to for all nodes to be ready • failure configmap go src io kubernetes output dockerized go src io kubernetes test configmap go updates should be reflected in volume go src io kubernetes output dockerized go src io kubernetes test configmap go timed out after expected content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value content of file etc configmap volume data value to contain substring value go src io kubernetes output dockerized go src io kubernetes test configmap go | 1 |
169,952 | 20,841,990,693 | IssuesEvent | 2022-03-21 02:02:15 | michaeldotson/home-inventory-vue-app | https://api.github.com/repos/michaeldotson/home-inventory-vue-app | opened | CVE-2022-24771 (High) detected in node-forge-0.7.5.tgz | security vulnerability | ## CVE-2022-24771 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-forge-0.7.5.tgz</b></p></summary>
<p>JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-forge/-/node-forge-0.7.5.tgz">https://registry.npmjs.org/node-forge/-/node-forge-0.7.5.tgz</a></p>
<p>Path to dependency file: /home-inventory-vue-app/package.json</p>
<p>Path to vulnerable library: /node_modules/node-forge/package.json</p>
<p>
Dependency Hierarchy:
- cli-service-3.5.1.tgz (Root Library)
- webpack-dev-server-3.2.1.tgz
- selfsigned-1.10.4.tgz
- :x: **node-forge-0.7.5.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code is lenient in checking the digest algorithm structure. This can allow a crafted structure that steals padding bytes and uses unchecked portion of the PKCS#1 encoded message to forge a signature when a low public exponent is being used. The issue has been addressed in `node-forge` version 1.3.0. There are currently no known workarounds.
<p>Publish Date: 2022-03-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24771>CVE-2022-24771</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24771">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24771</a></p>
<p>Release Date: 2022-03-18</p>
<p>Fix Resolution: node-forge - 1.3.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-24771 (High) detected in node-forge-0.7.5.tgz - ## CVE-2022-24771 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-forge-0.7.5.tgz</b></p></summary>
<p>JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-forge/-/node-forge-0.7.5.tgz">https://registry.npmjs.org/node-forge/-/node-forge-0.7.5.tgz</a></p>
<p>Path to dependency file: /home-inventory-vue-app/package.json</p>
<p>Path to vulnerable library: /node_modules/node-forge/package.json</p>
<p>
Dependency Hierarchy:
- cli-service-3.5.1.tgz (Root Library)
- webpack-dev-server-3.2.1.tgz
- selfsigned-1.10.4.tgz
- :x: **node-forge-0.7.5.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code is lenient in checking the digest algorithm structure. This can allow a crafted structure that steals padding bytes and uses unchecked portion of the PKCS#1 encoded message to forge a signature when a low public exponent is being used. The issue has been addressed in `node-forge` version 1.3.0. There are currently no known workarounds.
<p>Publish Date: 2022-03-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24771>CVE-2022-24771</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24771">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24771</a></p>
<p>Release Date: 2022-03-18</p>
<p>Fix Resolution: node-forge - 1.3.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in node forge tgz cve high severity vulnerability vulnerable library node forge tgz javascript implementations of network transports cryptography ciphers pki message digests and various utilities library home page a href path to dependency file home inventory vue app package json path to vulnerable library node modules node forge package json dependency hierarchy cli service tgz root library webpack dev server tgz selfsigned tgz x node forge tgz vulnerable library vulnerability details forge also called node forge is a native implementation of transport layer security in javascript prior to version rsa pkcs signature verification code is lenient in checking the digest algorithm structure this can allow a crafted structure that steals padding bytes and uses unchecked portion of the pkcs encoded message to forge a signature when a low public exponent is being used the issue has been addressed in node forge version there are currently no known workarounds publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution node forge step up your open source security game with whitesource | 0 |
243,313 | 26,278,035,865 | IssuesEvent | 2023-01-07 01:48:22 | Symbolk/Code2Graph | https://api.github.com/repos/Symbolk/Code2Graph | opened | CVE-2022-1471 (High) detected in snakeyaml-1.30.jar, snakeyaml-1.29.jar | security vulnerability | ## CVE-2022-1471 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>snakeyaml-1.30.jar</b>, <b>snakeyaml-1.29.jar</b></p></summary>
<p>
<details><summary><b>snakeyaml-1.30.jar</b></p></summary>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p>
<p>Path to dependency file: /mining/build.gradle</p>
<p>Path to vulnerable library: /dle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.30/8fde7fe2586328ac3c68db92045e1c8759125000/snakeyaml-1.30.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.30/8fde7fe2586328ac3c68db92045e1c8759125000/snakeyaml-1.30.jar</p>
<p>
Dependency Hierarchy:
- :x: **snakeyaml-1.30.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.29.jar</b></p></summary>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="http://www.snakeyaml.org">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dist/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar,/dle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar</p>
<p>
Dependency Hierarchy:
- :x: **snakeyaml-1.29.jar** (Vulnerable Library)
</details>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization.
<p>Publish Date: 2022-12-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-1471>CVE-2022-1471</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-1471 (High) detected in snakeyaml-1.30.jar, snakeyaml-1.29.jar - ## CVE-2022-1471 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>snakeyaml-1.30.jar</b>, <b>snakeyaml-1.29.jar</b></p></summary>
<p>
<details><summary><b>snakeyaml-1.30.jar</b></p></summary>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p>
<p>Path to dependency file: /mining/build.gradle</p>
<p>Path to vulnerable library: /dle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.30/8fde7fe2586328ac3c68db92045e1c8759125000/snakeyaml-1.30.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.30/8fde7fe2586328ac3c68db92045e1c8759125000/snakeyaml-1.30.jar</p>
<p>
Dependency Hierarchy:
- :x: **snakeyaml-1.30.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.29.jar</b></p></summary>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="http://www.snakeyaml.org">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dist/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar,/dle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar</p>
<p>
Dependency Hierarchy:
- :x: **snakeyaml-1.29.jar** (Vulnerable Library)
</details>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization.
<p>Publish Date: 2022-12-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-1471>CVE-2022-1471</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in snakeyaml jar snakeyaml jar cve high severity vulnerability vulnerable libraries snakeyaml jar snakeyaml jar snakeyaml jar yaml parser and emitter for java library home page a href path to dependency file mining build gradle path to vulnerable library dle caches modules files org yaml snakeyaml snakeyaml jar home wss scanner gradle caches modules files org yaml snakeyaml snakeyaml jar dependency hierarchy x snakeyaml jar vulnerable library snakeyaml jar yaml parser and emitter for java library home page a href path to dependency file dist build gradle path to vulnerable library home wss scanner gradle caches modules files org yaml snakeyaml snakeyaml jar home wss scanner gradle caches modules files org yaml snakeyaml snakeyaml jar home wss scanner gradle caches modules files org yaml snakeyaml snakeyaml jar home wss scanner gradle caches modules files org yaml snakeyaml snakeyaml jar home wss scanner gradle caches modules files org yaml snakeyaml snakeyaml jar home wss scanner gradle caches modules files org yaml snakeyaml snakeyaml jar home wss scanner gradle caches modules files org yaml snakeyaml snakeyaml jar dle caches modules files org yaml snakeyaml snakeyaml jar home wss scanner gradle caches modules files org yaml snakeyaml snakeyaml jar dependency hierarchy x snakeyaml jar vulnerable library found in base branch main vulnerability details snakeyaml s constructor class does not restrict types which can be instantiated during deserialization deserializing yaml content provided by an attacker can lead to remote code execution we recommend using snakeyaml s safeconsturctor when parsing untrusted content to restrict deserialization publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href step up your open source security game with mend | 0 |
175,931 | 13,617,586,525 | IssuesEvent | 2020-09-23 17:13:36 | pandas-dev/pandas | https://api.github.com/repos/pandas-dev/pandas | closed | TST: split up tests/frame/test_indexing.py | Refactor Testing | Based on [review](https://github.com/pandas-dev/pandas/pull/25633#pullrequestreview-216493057) of @jreback in #25633:
> frame/test_indexing.py is actually pretty huge. so pls change according to my comments, and open an issue to split this to separate smaller files (after) | 1.0 | TST: split up tests/frame/test_indexing.py - Based on [review](https://github.com/pandas-dev/pandas/pull/25633#pullrequestreview-216493057) of @jreback in #25633:
> frame/test_indexing.py is actually pretty huge. so pls change according to my comments, and open an issue to split this to separate smaller files (after) | non_priority | tst split up tests frame test indexing py based on of jreback in frame test indexing py is actually pretty huge so pls change according to my comments and open an issue to split this to separate smaller files after | 0 |
413,393 | 12,066,555,623 | IssuesEvent | 2020-04-16 11:58:49 | threefoldtech/home | https://api.github.com/repos/threefoldtech/home | opened | 3bot.connect issue with capital letter | priority_critical type_bug | I could not start any of the solutions in my 3bot.connect. Had always an error "User not found".
Jo has done some digging and found out that the email address stored has a capital first letter (probably done in the 3bot connect app by the app and I missed it when I type it).
This results in an error when deploying the chat flow solutions. As capital letters have no meaning in email addresses they should not be stored like that... (That's what I think;-).
Also hard to detect when the app does not show the capital letters in the "settings" screen.
<img width="1396" alt="Screen Shot 2020-04-16 at 1 46 18 PM" src="https://user-images.githubusercontent.com/13766992/79453102-79746480-7fe9-11ea-8829-de92e07da846.png">
| 1.0 | 3bot.connect issue with capital letter - I could not start any of the solutions in my 3bot.connect. Had always an error "User not found".
Jo has done some digging and found out that the email address stored has a capital first letter (probably done in the 3bot connect app by the app and I missed it when I type it).
This results in an error when deploying the chat flow solutions. As capital letters have no meaning in email addresses they should not be stored like that... (That's what I think;-).
Also hard to detect when the app does not show the capital letters in the "settings" screen.
<img width="1396" alt="Screen Shot 2020-04-16 at 1 46 18 PM" src="https://user-images.githubusercontent.com/13766992/79453102-79746480-7fe9-11ea-8829-de92e07da846.png">
| priority | connect issue with capital letter i could not start any of the solutions in my connect had always an error user not found jo has done some digging and found out that the email address stored has a capital first letter probably done in the connect app by the app and i missed it when i type it this results in an error when deploying the chat flow solutions as capital letters have no meaning in email addresses they should not be stored like that that s what i think also hard to detect when the app does not show the capital letters in the settings screen img width alt screen shot at pm src | 1 |
4,790 | 3,081,724,674 | IssuesEvent | 2015-08-23 01:16:51 | Chisel-2/Chisel-2 | https://api.github.com/repos/Chisel-2/Chisel-2 | closed | Crash in server start | code complete | Hello. Server: Cauldron 1.7.10-1492.150,
Chisel2_DEV-2.5.0.154, crash-reports:
https://gist.github.com/Bogdan-G/e0432d76c11724e36292 | https://gist.github.com/Bogdan-G/3e38be2802d371833317
Chisel2_DEV-2.5.0.151: normal start.
Client MC 1.7.10, Forge 1492, both versions normal start. | 1.0 | Crash in server start - Hello. Server: Cauldron 1.7.10-1492.150,
Chisel2_DEV-2.5.0.154, crash-reports:
https://gist.github.com/Bogdan-G/e0432d76c11724e36292 | https://gist.github.com/Bogdan-G/3e38be2802d371833317
Chisel2_DEV-2.5.0.151: normal start.
Client MC 1.7.10, Forge 1492, both versions normal start. | non_priority | crash in server start hello server cauldron dev crash reports dev normal start client mc forge both versions normal start | 0 |
441,754 | 12,731,762,427 | IssuesEvent | 2020-06-25 09:19:58 | cloudfoundry-incubator/kubecf | https://api.github.com/repos/cloudfoundry-incubator/kubecf | opened | Move Workload to a GCP Project | Priority: High Type: CI Type: Maintenance | **Is your feature request related to a problem? Please describe.**
The workload that we current have on GCP project ( SUSE-CAP) must be moved to another GCP project (SUSE-CSS-Platform).
**Describe the solution you'd like**
All the workload migrated to the new project.
**Describe alternatives you've considered**
N/A
**Additional context**
N/A
| 1.0 | Move Workload to a GCP Project - **Is your feature request related to a problem? Please describe.**
The workload that we current have on GCP project ( SUSE-CAP) must be moved to another GCP project (SUSE-CSS-Platform).
**Describe the solution you'd like**
All the workload migrated to the new project.
**Describe alternatives you've considered**
N/A
**Additional context**
N/A
| priority | move workload to a gcp project is your feature request related to a problem please describe the workload that we current have on gcp project suse cap must be moved to another gcp project suse css platform describe the solution you d like all the workload migrated to the new project describe alternatives you ve considered n a additional context n a | 1 |
766,457 | 26,884,118,486 | IssuesEvent | 2023-02-06 00:14:28 | openservicemesh/osm | https://api.github.com/repos/openservicemesh/osm | closed | Fix metric count for inner domain resources | kind/bug size/L priority/P3 stale | The current count of resources (as presented by metrics) rely on counting API notifications received over Kubernetes informers. Based on that, it can be discerned a count for certain objects on the mesh.
The model currently suffers from inaccuracy when the namespace can be unmonitored (as for example, delete notifications for services won't be accounted for, as the namespace will no longer be monitored).
There are several ways to fix this:
- Formal recount after every event (easiest, but likely expensive/overkill as needs a walk on all data on caches)
- Keep some formal state to understand when an object was added and was monitored, and when is not.
- Force individual synchronization per monitored namespace, wipe out data when namespace becomes unmonitored. (Most correct, at the expense of potential bad scalability of informer count)
Solution TBD.
- Metrics [X]
| 1.0 | Fix metric count for inner domain resources - The current count of resources (as presented by metrics) rely on counting API notifications received over Kubernetes informers. Based on that, it can be discerned a count for certain objects on the mesh.
The model currently suffers from inaccuracy when the namespace can be unmonitored (as for example, delete notifications for services won't be accounted for, as the namespace will no longer be monitored).
There are several ways to fix this:
- Formal recount after every event (easiest, but likely expensive/overkill as needs a walk on all data on caches)
- Keep some formal state to understand when an object was added and was monitored, and when is not.
- Force individual synchronization per monitored namespace, wipe out data when namespace becomes unmonitored. (Most correct, at the expense of potential bad scalability of informer count)
Solution TBD.
- Metrics [X]
| priority | fix metric count for inner domain resources the current count of resources as presented by metrics rely on counting api notifications received over kubernetes informers based on that it can be discerned a count for certain objects on the mesh the model currently suffers from inaccuracy when the namespace can be unmonitored as for example delete notifications for services won t be accounted for as the namespace will no longer be monitored there are several ways to fix this formal recount after every event easiest but likely expensive overkill as needs a walk on all data on caches keep some formal state to understand when an object was added and was monitored and when is not force individual synchronization per monitored namespace wipe out data when namespace becomes unmonitored most correct at the expense of potential bad scalability of informer count solution tbd metrics | 1 |
485,129 | 13,961,644,910 | IssuesEvent | 2020-10-25 04:45:58 | be5invis/Iosevka | https://api.github.com/repos/be5invis/Iosevka | closed | Line-height is broken | Priority 0 🐞 Bug 📐 Metrics | Describe your problem here. Provide pictures and files if necessary.
Hello! So I am having a problem with the line-height for my editor, Visual Studio Code. As seen below it the line-height is very large and isn't centered.
<img width="473" alt="Screen Shot 2020-10-24 at 10 14 50 PM" src="https://user-images.githubusercontent.com/43759105/97097492-6bae3480-1647-11eb-97d2-a10ccd019100.png">
It is also broken in Font Book (the macOS font explorer):
Iosevka font:
<img width="999" alt="Screen Shot 2020-10-24 at 10 23 17 PM" src="https://user-images.githubusercontent.com/43759105/97097502-84b6e580-1647-11eb-983a-0c4f7f97aac6.png">
Normal font:
<img width="999" alt="Screen Shot 2020-10-24 at 10 23 36 PM" src="https://user-images.githubusercontent.com/43759105/97097506-900a1100-1647-11eb-93e2-28d74e3d7e9a.png">
Everything was working fine until I upgraded to v3.7.0 via homebrew cask. It works fine in iTerm2 but seems to be broken for everything else. This is happening for all versions of Iosevka. Thanks for making this font by the way :)
---
* Your font version: 3.7.0
* Your font variant: Extralight
* Your operating system (name and version): macOS Catalina 10.15.7
* Your application using Iosevka: Visual Studio Code & Font Book
| 1.0 | Line-height is broken - Describe your problem here. Provide pictures and files if necessary.
Hello! So I am having a problem with the line-height for my editor, Visual Studio Code. As seen below it the line-height is very large and isn't centered.
<img width="473" alt="Screen Shot 2020-10-24 at 10 14 50 PM" src="https://user-images.githubusercontent.com/43759105/97097492-6bae3480-1647-11eb-97d2-a10ccd019100.png">
It is also broken in Font Book (the macOS font explorer):
Iosevka font:
<img width="999" alt="Screen Shot 2020-10-24 at 10 23 17 PM" src="https://user-images.githubusercontent.com/43759105/97097502-84b6e580-1647-11eb-983a-0c4f7f97aac6.png">
Normal font:
<img width="999" alt="Screen Shot 2020-10-24 at 10 23 36 PM" src="https://user-images.githubusercontent.com/43759105/97097506-900a1100-1647-11eb-93e2-28d74e3d7e9a.png">
Everything was working fine until I upgraded to v3.7.0 via homebrew cask. It works fine in iTerm2 but seems to be broken for everything else. This is happening for all versions of Iosevka. Thanks for making this font by the way :)
---
* Your font version: 3.7.0
* Your font variant: Extralight
* Your operating system (name and version): macOS Catalina 10.15.7
* Your application using Iosevka: Visual Studio Code & Font Book
| priority | line height is broken describe your problem here provide pictures and files if necessary hello so i am having a problem with the line height for my editor visual studio code as seen below it the line height is very large and isn t centered img width alt screen shot at pm src it is also broken in font book the macos font explorer iosevka font img width alt screen shot at pm src normal font img width alt screen shot at pm src everything was working fine until i upgraded to via homebrew cask it works fine in but seems to be broken for everything else this is happening for all versions of iosevka thanks for making this font by the way your font version your font variant extralight your operating system name and version macos catalina your application using iosevka visual studio code font book | 1 |
61,870 | 3,155,421,815 | IssuesEvent | 2015-09-17 08:44:42 | sainteos/project-spero | https://api.github.com/repos/sainteos/project-spero | closed | The window needs to react to resolution changes and fullscreen | enhancement medpriority | Currently, if you fullscreen or change window resolution, the viewport stays the same and the rest of the window just fills with black. The app should react to these resolution changes. | 1.0 | The window needs to react to resolution changes and fullscreen - Currently, if you fullscreen or change window resolution, the viewport stays the same and the rest of the window just fills with black. The app should react to these resolution changes. | priority | the window needs to react to resolution changes and fullscreen currently if you fullscreen or change window resolution the viewport stays the same and the rest of the window just fills with black the app should react to these resolution changes | 1 |
210,885 | 7,195,390,981 | IssuesEvent | 2018-02-04 16:41:20 | ZetaGlest/zetaglest-source | https://api.github.com/repos/ZetaGlest/zetaglest-source | closed | start_zetaglest_gameserver: Segfaults | bug good first issue help wanted priority: normal | I never use this script but tried it recently. Here's the output:
```
andy@oceanus:~/src/ZetaGlest/zetaglest-source/mk/linux$ ./start_zetaglest_gameserver
Notice: Detected processor with 4 cores.
Starting server...
ERROR: Server has quit unexpectedly.
Please inspect /home/andy/.zetaglest/server.log.
Segmentation fault
```
```
andy@oceanus:~/src/ZetaGlest/zetaglest-source/mk/linux$ cat ~/.zetaglest/server.log
Fri Feb 2 12:33:21 CST 2018
Starting server...
./start_zetaglest_gameserver: 331: ./start_zetaglest_gameserver: : Permission denied
``` | 1.0 | start_zetaglest_gameserver: Segfaults - I never use this script but tried it recently. Here's the output:
```
andy@oceanus:~/src/ZetaGlest/zetaglest-source/mk/linux$ ./start_zetaglest_gameserver
Notice: Detected processor with 4 cores.
Starting server...
ERROR: Server has quit unexpectedly.
Please inspect /home/andy/.zetaglest/server.log.
Segmentation fault
```
```
andy@oceanus:~/src/ZetaGlest/zetaglest-source/mk/linux$ cat ~/.zetaglest/server.log
Fri Feb 2 12:33:21 CST 2018
Starting server...
./start_zetaglest_gameserver: 331: ./start_zetaglest_gameserver: : Permission denied
``` | priority | start zetaglest gameserver segfaults i never use this script but tried it recently here s the output andy oceanus src zetaglest zetaglest source mk linux start zetaglest gameserver notice detected processor with cores starting server error server has quit unexpectedly please inspect home andy zetaglest server log segmentation fault andy oceanus src zetaglest zetaglest source mk linux cat zetaglest server log fri feb cst starting server start zetaglest gameserver start zetaglest gameserver permission denied | 1 |
116,135 | 24,864,680,707 | IssuesEvent | 2022-10-27 10:58:07 | Onelinerhub/onelinerhub | https://api.github.com/repos/Onelinerhub/onelinerhub | closed | Short solution needed: "How to change pixel color" (python-pillow) | help wanted good first issue code python-pillow | Please help us write most modern and shortest code solution for this issue:
**How to change pixel color** (technology: [python-pillow](https://onelinerhub.com/python-pillow))
### Fast way
Just write the code solution in the comments.
### Prefered way
1. Create [pull request](https://github.com/Onelinerhub/onelinerhub/blob/main/how-to-contribute.md) with a new code file inside [inbox folder](https://github.com/Onelinerhub/onelinerhub/tree/main/inbox).
2. Don't forget to [use comments](https://github.com/Onelinerhub/onelinerhub/blob/main/how-to-contribute.md#code-file-md-format) explain solution.
3. Link to this issue in comments of pull request. | 1.0 | Short solution needed: "How to change pixel color" (python-pillow) - Please help us write most modern and shortest code solution for this issue:
**How to change pixel color** (technology: [python-pillow](https://onelinerhub.com/python-pillow))
### Fast way
Just write the code solution in the comments.
### Prefered way
1. Create [pull request](https://github.com/Onelinerhub/onelinerhub/blob/main/how-to-contribute.md) with a new code file inside [inbox folder](https://github.com/Onelinerhub/onelinerhub/tree/main/inbox).
2. Don't forget to [use comments](https://github.com/Onelinerhub/onelinerhub/blob/main/how-to-contribute.md#code-file-md-format) explain solution.
3. Link to this issue in comments of pull request. | non_priority | short solution needed how to change pixel color python pillow please help us write most modern and shortest code solution for this issue how to change pixel color technology fast way just write the code solution in the comments prefered way create with a new code file inside don t forget to explain solution link to this issue in comments of pull request | 0 |
630,279 | 20,103,683,289 | IssuesEvent | 2022-02-07 08:20:36 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.reddit.com - see bug description | priority-critical browser-focus-geckoview engine-gecko | <!-- @browser: Firefox Mobile 96.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 10; Mobile; rv:96.0) Gecko/96.0 Firefox/96.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/99172 -->
<!-- @extra_labels: browser-focus-geckoview -->
**URL**: https://www.reddit.com/r/AskReddit/comments/skjc3x/in_case_of_an_apocalypse_what_could_function_as_a/
**Browser / Version**: Firefox Mobile 96.0
**Operating System**: Android 10
**Tested Another Browser**: Yes Chrome
**Problem type**: Something else
**Description**: Comments don't load
**Steps to Reproduce**:
The comments section does not load
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2022/2/11d44793-e914-421a-a875-50c4dbd56ffc.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20220126154723</li><li>channel: release</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2022/2/ca6b162f-85a7-45b2-8cf6-d8cc92105941)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.reddit.com - see bug description - <!-- @browser: Firefox Mobile 96.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 10; Mobile; rv:96.0) Gecko/96.0 Firefox/96.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/99172 -->
<!-- @extra_labels: browser-focus-geckoview -->
**URL**: https://www.reddit.com/r/AskReddit/comments/skjc3x/in_case_of_an_apocalypse_what_could_function_as_a/
**Browser / Version**: Firefox Mobile 96.0
**Operating System**: Android 10
**Tested Another Browser**: Yes Chrome
**Problem type**: Something else
**Description**: Comments don't load
**Steps to Reproduce**:
The comments section does not load
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2022/2/11d44793-e914-421a-a875-50c4dbd56ffc.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20220126154723</li><li>channel: release</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2022/2/ca6b162f-85a7-45b2-8cf6-d8cc92105941)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | see bug description url browser version firefox mobile operating system android tested another browser yes chrome problem type something else description comments don t load steps to reproduce the comments section does not load view the screenshot img alt screenshot src browser configuration gfx webrender all false gfx webrender blob images true gfx webrender enabled false image mem shared true buildid channel release hastouchscreen true mixed active content blocked false mixed passive content blocked false tracking content blocked false from with ❤️ | 1 |
437,816 | 12,602,864,163 | IssuesEvent | 2020-06-11 12:31:26 | magento/magento2 | https://api.github.com/repos/magento/magento2 | opened | [Issue] 'Ship Here' in CamelCase as that's how it is written elsewhere | Component: Checkout Priority: P3 Severity: S3 | This issue is automatically created based on existing pull request: magento/magento2#28547: 'Ship Here' in CamelCase as that's how it is written elsewhere
---------
<!---
Thank you for contributing to Magento.
To help us process this pull request we recommend that you add the following information:
- Summary of the pull request,
- Issue(s) related to the changes made,
- Manual testing scenarios
Fields marked with (*) are required. Please don't remove the template.
-->
<!--- Please provide a general summary of the Pull Request in the Title above -->
### Description (*)
<!---
Please provide a description of the changes proposed in the pull request.
Letting us know what has changed and why it needed changing will help us validate this pull request.
-->
In the checkout shipping address modal the text in the primary button was written with a lowercase 'h'. On all other places, and in the translation files, it is written with a capital: 'Ship Here'. As a result, the button with the lowercase version 'Ship here' isn't translated.
### Related Pull Requests
<!-- related pull request placeholder -->
### Fixed Issues (if relevant)
<!---
If relevant, please provide a list of fixed issues in the format magento/magento2#<issue_number>.
There could be 1 or more issues linked here and it will help us find some more information about the reasoning behind this change.
-->
### Manual testing scenarios (*)
<!---
Please provide a set of unambiguous steps to test the proposed code change.
Giving us manual testing scenarios will help with the processing and validation process.
-->
### Questions or comments
<!---
If relevant, here you can ask questions or provide comments on your pull request for the reviewer
For example if you need assistance with writing tests or would like some feedback on one of your development ideas
-->
### Contribution checklist (*)
- [ ] Pull request has a meaningful description of its purpose
- [ ] All commits are accompanied by meaningful commit messages
- [ ] All new or changed code is covered with unit/integration tests (if applicable)
- [ ] All automated tests passed successfully (all builds are green)
| 1.0 | [Issue] 'Ship Here' in CamelCase as that's how it is written elsewhere - This issue is automatically created based on existing pull request: magento/magento2#28547: 'Ship Here' in CamelCase as that's how it is written elsewhere
---------
<!---
Thank you for contributing to Magento.
To help us process this pull request we recommend that you add the following information:
- Summary of the pull request,
- Issue(s) related to the changes made,
- Manual testing scenarios
Fields marked with (*) are required. Please don't remove the template.
-->
<!--- Please provide a general summary of the Pull Request in the Title above -->
### Description (*)
<!---
Please provide a description of the changes proposed in the pull request.
Letting us know what has changed and why it needed changing will help us validate this pull request.
-->
In the checkout shipping address modal the text in the primary button was written with a lowercase 'h'. On all other places, and in the translation files, it is written with a capital: 'Ship Here'. As a result, the button with the lowercase version 'Ship here' isn't translated.
### Related Pull Requests
<!-- related pull request placeholder -->
### Fixed Issues (if relevant)
<!---
If relevant, please provide a list of fixed issues in the format magento/magento2#<issue_number>.
There could be 1 or more issues linked here and it will help us find some more information about the reasoning behind this change.
-->
### Manual testing scenarios (*)
<!---
Please provide a set of unambiguous steps to test the proposed code change.
Giving us manual testing scenarios will help with the processing and validation process.
-->
### Questions or comments
<!---
If relevant, here you can ask questions or provide comments on your pull request for the reviewer
For example if you need assistance with writing tests or would like some feedback on one of your development ideas
-->
### Contribution checklist (*)
- [ ] Pull request has a meaningful description of its purpose
- [ ] All commits are accompanied by meaningful commit messages
- [ ] All new or changed code is covered with unit/integration tests (if applicable)
- [ ] All automated tests passed successfully (all builds are green)
| priority | ship here in camelcase as that s how it is written elsewhere this issue is automatically created based on existing pull request magento ship here in camelcase as that s how it is written elsewhere thank you for contributing to magento to help us process this pull request we recommend that you add the following information summary of the pull request issue s related to the changes made manual testing scenarios fields marked with are required please don t remove the template description please provide a description of the changes proposed in the pull request letting us know what has changed and why it needed changing will help us validate this pull request in the checkout shipping address modal the text in the primary button was written with a lowercase h on all other places and in the translation files it is written with a capital ship here as a result the button with the lowercase version ship here isn t translated related pull requests fixed issues if relevant if relevant please provide a list of fixed issues in the format magento there could be or more issues linked here and it will help us find some more information about the reasoning behind this change manual testing scenarios please provide a set of unambiguous steps to test the proposed code change giving us manual testing scenarios will help with the processing and validation process questions or comments if relevant here you can ask questions or provide comments on your pull request for the reviewer for example if you need assistance with writing tests or would like some feedback on one of your development ideas contribution checklist pull request has a meaningful description of its purpose all commits are accompanied by meaningful commit messages all new or changed code is covered with unit integration tests if applicable all automated tests passed successfully all builds are green | 1 |
717,373 | 24,673,227,221 | IssuesEvent | 2022-10-18 15:05:54 | netdata/netdata-cloud | https://api.github.com/repos/netdata/netdata-cloud | closed | [Bug]: Area chart showing only one of the two areas | bug priority/medium cloud-frontend | ### Bug description
Below you see two dimensions that are supposed to have a value of 5 each, but only one is properly drawn in the area chart. Dunno what happened to the other:
<img width="638" alt="image" src="https://user-images.githubusercontent.com/43294513/194118655-7f397d41-84d1-4e32-804f-5107115bd9b4.png">
### Expected behavior
-
### Steps to reproduce
Set up fping and try it? I'll provide access to my room if needed.
### Screenshots
_No response_
### Error Logs
_No response_
### Desktop
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Browser Version [e.g. 22]
### Additional context
_No response_ | 1.0 | [Bug]: Area chart showing only one of the two areas - ### Bug description
Below you see two dimensions that are supposed to have a value of 5 each, but only one is properly drawn in the area chart. Dunno what happened to the other:
<img width="638" alt="image" src="https://user-images.githubusercontent.com/43294513/194118655-7f397d41-84d1-4e32-804f-5107115bd9b4.png">
### Expected behavior
-
### Steps to reproduce
Set up fping and try it? I'll provide access to my room if needed.
### Screenshots
_No response_
### Error Logs
_No response_
### Desktop
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Browser Version [e.g. 22]
### Additional context
_No response_ | priority | area chart showing only one of the two areas bug description below you see two dimensions that are supposed to have a value of each but only one is properly drawn in the area chart dunno what happened to the other img width alt image src expected behavior steps to reproduce set up fping and try it i ll provide access to my room if needed screenshots no response error logs no response desktop os browser browser version additional context no response | 1 |
40,942 | 5,284,838,881 | IssuesEvent | 2017-02-08 01:55:20 | tor4kichi/Hohoema | https://api.github.com/repos/tor4kichi/Hohoema | opened | アカウントページの作成 | ui_design | これまであったログインページをアカウントページとしてリファインします。
紆余曲折あって今はログインページをアカウントダイアログの形に変更していますので、アカウントダイアログは一旦削除します。
アカウント情報の入力ページを１ページ使って表示することで、入力時の不安を多少でも解消したいです。
アカウント情報の入力の前と後でページの表示状態を切り替えたいです。
アカウント情報入力前では、グローバルメニューの表示をOFFにして、アカウントの入力を必ず行ってもらえるようにします。
入力後はメニューを表示して、ログインユーザー情報を表示します。ここでログアウトが選択されたら、アカウント情報入力前の表示状態に戻します。
| 1.0 | アカウントページの作成 - これまであったログインページをアカウントページとしてリファインします。
紆余曲折あって今はログインページをアカウントダイアログの形に変更していますので、アカウントダイアログは一旦削除します。
アカウント情報の入力ページを１ページ使って表示することで、入力時の不安を多少でも解消したいです。
アカウント情報の入力の前と後でページの表示状態を切り替えたいです。
アカウント情報入力前では、グローバルメニューの表示をOFFにして、アカウントの入力を必ず行ってもらえるようにします。
入力後はメニューを表示して、ログインユーザー情報を表示します。ここでログアウトが選択されたら、アカウント情報入力前の表示状態に戻します。
| non_priority | アカウントページの作成 これまであったログインページをアカウントページとしてリファインします。 紆余曲折あって今はログインページをアカウントダイアログの形に変更していますので、アカウントダイアログは一旦削除します。 、入力時の不安を多少でも解消したいです。 アカウント情報の入力の前と後でページの表示状態を切り替えたいです。 アカウント情報入力前では、グローバルメニューの表示をoffにして、アカウントの入力を必ず行ってもらえるようにします。 入力後はメニューを表示して、ログインユーザー情報を表示します。ここでログアウトが選択されたら、アカウント情報入力前の表示状態に戻します。 | 0 |
401,923 | 11,800,015,198 | IssuesEvent | 2020-03-18 16:49:09 | mozilla/addons | https://api.github.com/repos/mozilla/addons | closed | Automatically flag add-ons using native messaging for admin review | component: reviewer tools needs: issues filing priority: p3 state: stale | Add-ons that use native messaging should be automatically flagged for admin-review during submission.
This probably involves both `addons-linter` and `addons-server` work.
This is related to https://github.com/mozilla/addons-server/issues/4533. We need to expose in the linter whether the add-on uses native messaging. This is important for the auto-approval. On top of that, such add-ons should only be reviewed by admin reviewers. I think once we have the permission exposure, adding the admin-flag in `addons-server` should be fairly easy.
| 1.0 | Automatically flag add-ons using native messaging for admin review - Add-ons that use native messaging should be automatically flagged for admin-review during submission.
This probably involves both `addons-linter` and `addons-server` work.
This is related to https://github.com/mozilla/addons-server/issues/4533. We need to expose in the linter whether the add-on uses native messaging. This is important for the auto-approval. On top of that, such add-ons should only be reviewed by admin reviewers. I think once we have the permission exposure, adding the admin-flag in `addons-server` should be fairly easy.
| priority | automatically flag add ons using native messaging for admin review add ons that use native messaging should be automatically flagged for admin review during submission this probably involves both addons linter and addons server work this is related to we need to expose in the linter whether the add on uses native messaging this is important for the auto approval on top of that such add ons should only be reviewed by admin reviewers i think once we have the permission exposure adding the admin flag in addons server should be fairly easy | 1 |
130,489 | 27,713,234,235 | IssuesEvent | 2023-03-14 15:25:26 | openfoodfacts/openfoodfacts-server | https://api.github.com/repos/openfoodfacts/openfoodfacts-server | opened | Allow to login automatically to your openfoodfacts account using a QR-Code in the website | feature user-management crossplatform integration qrcode | ### What
- Allow to login automatically to your openfoodfacts account using a QR-Code in the website.
| 1.0 | Allow to login automatically to your openfoodfacts account using a QR-Code in the website - ### What
- Allow to login automatically to your openfoodfacts account using a QR-Code in the website.
| non_priority | allow to login automatically to your openfoodfacts account using a qr code in the website what allow to login automatically to your openfoodfacts account using a qr code in the website | 0 |
670,753 | 22,702,797,661 | IssuesEvent | 2022-07-05 12:16:38 | teogor/teogor.github.io | https://api.github.com/repos/teogor/teogor.github.io | opened | Add `TikTok` account | @UI @priority-low | Add the tiktok account in the 'connect with me section'.
Account -> @teogor.dev | 1.0 | Add `TikTok` account - Add the tiktok account in the 'connect with me section'.
Account -> @teogor.dev | priority | add tiktok account add the tiktok account in the connect with me section account teogor dev | 1 |
181,944 | 14,085,158,872 | IssuesEvent | 2020-11-05 00:15:49 | umrover/mrover-workspace | https://api.github.com/repos/umrover/mrover-workspace | closed | Quick-fix: have nav verify obstacle detection from perception | C/C++ nav percep testing | - [ ] add new state in which rover slows down and perception data is collected
- [ ] collect x amount of perception lcm's (5,7,9)
- [ ] take majority or use a threshold to determine yes/no obstacle
- [ ] if yes, proceed to obstacle state machine. if no, return to regular state machine
| 1.0 | Quick-fix: have nav verify obstacle detection from perception - - [ ] add new state in which rover slows down and perception data is collected
- [ ] collect x amount of perception lcm's (5,7,9)
- [ ] take majority or use a threshold to determine yes/no obstacle
- [ ] if yes, proceed to obstacle state machine. if no, return to regular state machine
| non_priority | quick fix have nav verify obstacle detection from perception add new state in which rover slows down and perception data is collected collect x amount of perception lcm s take majority or use a threshold to determine yes no obstacle if yes proceed to obstacle state machine if no return to regular state machine | 0 |
500,685 | 14,504,242,145 | IssuesEvent | 2020-12-12 00:29:47 | NuGet/Home | https://api.github.com/repos/NuGet/Home | reopened | Pack includes content brought in through dependency packages into the current project's package (SDK based projects only) | Area:ContentFiles Functionality:Pack Priority:2 Product:dotnet.exe Type:Bug UpForGrabs | ## Details about Problem
NuGet product used (NuGet.exe | VS UI | Package Manager Console | dotnet.exe): VS 2019
NuGet version (x.x.x.xxx):
dotnet.exe --version (if appropriate): 3.0.100
VS version (if appropriate): 16.3.8
OS version (i.e. win10 v1607 (14393.321)): Windows 10.0.14393 x64
Worked before? If so, with which NuGet version: -
## Detailed repro steps so we can see the same problem
I have been using the `PrivateAssets="all"` option for a long time. It works great for `PackageReference`. Now I needed to use some content file in my project and I could not achieve the desired behavior with `PrivateAssets="all"`. I want to build "base" package with one file `data.json` which should be consumed in "top" package but should not be exposed further to consumers of the "top" package.
My "base" package:
```xml
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>netstandard2.0</TargetFramework>
<IncludeBuildOutput>false</IncludeBuildOutput>
<GeneratePackageOnBuild>true</GeneratePackageOnBuild>
</PropertyGroup>
<ItemGroup>
<Content Include="data.json">
<PackagePath>contentFiles/any/any/data.json</PackagePath>
</Content>
</ItemGroup>
</Project>
```
The result seems to be good for me:
My "top" package:
```xml
<Project>
<ItemGroup>
<PackageReference Include="BasePackage" Version="1.0.0">
<PrivateAssets>all</PrivateAssets>
</PackageReference>
</ItemGroup>
</Project>
```
The Result is unexpected for me:
Why is the file again in the content section? This file is a development dependency, some sort of settings file. The "base" package is a package with Roslyn analyzers and the settings file - `data.json`. I do not present the analyzers used for clarity. For them, `PrivateAssets` works as it should - they do not fall into the dependencies of the "base" package. But for the settings file - `data.json`, I can’t get the same behavior.
I spent a lot of time resolving this issue and it seems to me that I do not see any obvious solution, which is somewhere nearby. I will be very grateful for the advice.
| 1.0 | Pack includes content brought in through dependency packages into the current project's package (SDK based projects only) - ## Details about Problem
NuGet product used (NuGet.exe | VS UI | Package Manager Console | dotnet.exe): VS 2019
NuGet version (x.x.x.xxx):
dotnet.exe --version (if appropriate): 3.0.100
VS version (if appropriate): 16.3.8
OS version (i.e. win10 v1607 (14393.321)): Windows 10.0.14393 x64
Worked before? If so, with which NuGet version: -
## Detailed repro steps so we can see the same problem
I have been using the `PrivateAssets="all"` option for a long time. It works great for `PackageReference`. Now I needed to use some content file in my project and I could not achieve the desired behavior with `PrivateAssets="all"`. I want to build "base" package with one file `data.json` which should be consumed in "top" package but should not be exposed further to consumers of the "top" package.
My "base" package:
```xml
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>netstandard2.0</TargetFramework>
<IncludeBuildOutput>false</IncludeBuildOutput>
<GeneratePackageOnBuild>true</GeneratePackageOnBuild>
</PropertyGroup>
<ItemGroup>
<Content Include="data.json">
<PackagePath>contentFiles/any/any/data.json</PackagePath>
</Content>
</ItemGroup>
</Project>
```
The result seems to be good for me:
My "top" package:
```xml
<Project>
<ItemGroup>
<PackageReference Include="BasePackage" Version="1.0.0">
<PrivateAssets>all</PrivateAssets>
</PackageReference>
</ItemGroup>
</Project>
```
The Result is unexpected for me:
Why is the file again in the content section? This file is a development dependency, some sort of settings file. The "base" package is a package with Roslyn analyzers and the settings file - `data.json`. I do not present the analyzers used for clarity. For them, `PrivateAssets` works as it should - they do not fall into the dependencies of the "base" package. But for the settings file - `data.json`, I can’t get the same behavior.
I spent a lot of time resolving this issue and it seems to me that I do not see any obvious solution, which is somewhere nearby. I will be very grateful for the advice.
| priority | pack includes content brought in through dependency packages into the current project s package sdk based projects only details about problem nuget product used nuget exe vs ui package manager console dotnet exe vs nuget version x x x xxx dotnet exe version if appropriate vs version if appropriate os version i e windows worked before if so with which nuget version detailed repro steps so we can see the same problem i have been using the privateassets all option for a long time it works great for packagereference now i needed to use some content file in my project and i could not achieve the desired behavior with privateassets all i want to build base package with one file data json which should be consumed in top package but should not be exposed further to consumers of the top package my base package xml false true contentfiles any any data json the result seems to be good for me my top package xml all the result is unexpected for me why is the file again in the content section this file is a development dependency some sort of settings file the base package is a package with roslyn analyzers and the settings file data json i do not present the analyzers used for clarity for them privateassets works as it should they do not fall into the dependencies of the base package but for the settings file data json i can’t get the same behavior i spent a lot of time resolving this issue and it seems to me that i do not see any obvious solution which is somewhere nearby i will be very grateful for the advice | 1 |
5,423 | 12,491,650,126 | IssuesEvent | 2020-06-01 04:53:52 | MicrosoftDocs/architecture-center | https://api.github.com/repos/MicrosoftDocs/architecture-center | closed | KEDA | Pri1 architecture-center/svc cxp solution-idea/subsvc triaged | As article named "elastic", maybe KEDA (event driven auto-scaling) can be at least mentioned here?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 46ad00f8-c495-75e6-4f12-7555fce7f92f
* Version Independent ID: e2d14901-6be8-cae3-93ab-76d28edb5653
* Content: [Elastic demand handling with AKS - Azure Solution Ideas](https://docs.microsoft.com/en-us/azure/architecture/solution-ideas/articles/aks-demand-spikes)
* Content Source: [docs/solution-ideas/articles/aks-demand-spikes.md](https://github.com/microsoftdocs/architecture-center/blob/master/docs/solution-ideas/articles/aks-demand-spikes.md)
* Service: **architecture-center**
* Sub-service: **solution-idea**
* GitHub Login: @adamboeglin
* Microsoft Alias: **stellal** | 1.0 | KEDA - As article named "elastic", maybe KEDA (event driven auto-scaling) can be at least mentioned here?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 46ad00f8-c495-75e6-4f12-7555fce7f92f
* Version Independent ID: e2d14901-6be8-cae3-93ab-76d28edb5653
* Content: [Elastic demand handling with AKS - Azure Solution Ideas](https://docs.microsoft.com/en-us/azure/architecture/solution-ideas/articles/aks-demand-spikes)
* Content Source: [docs/solution-ideas/articles/aks-demand-spikes.md](https://github.com/microsoftdocs/architecture-center/blob/master/docs/solution-ideas/articles/aks-demand-spikes.md)
* Service: **architecture-center**
* Sub-service: **solution-idea**
* GitHub Login: @adamboeglin
* Microsoft Alias: **stellal** | non_priority | keda as article named elastic maybe keda event driven auto scaling can be at least mentioned here document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service architecture center sub service solution idea github login adamboeglin microsoft alias stellal | 0 |
556,556 | 16,485,847,447 | IssuesEvent | 2021-05-24 17:50:14 | bounswe/2021SpringGroup12 | https://api.github.com/repos/bounswe/2021SpringGroup12 | closed | Initialize the practice-app base files. | practice-app priority: high | Deadline: 25.05.2021 @09:00
I will create and push the base python file for our practice app. Then, other members will make their branches and start to develop.
| 1.0 | Initialize the practice-app base files. - Deadline: 25.05.2021 @09:00
I will create and push the base python file for our practice app. Then, other members will make their branches and start to develop.
| priority | initialize the practice app base files deadline i will create and push the base python file for our practice app then other members will make their branches and start to develop | 1 |
57,576 | 14,165,883,330 | IssuesEvent | 2020-11-12 08:02:57 | dotnet/aspnetcore | https://api.github.com/repos/dotnet/aspnetcore | closed | Shared cookie not being read by SignalR server. | area-security area-signalr | Im trying to share a cookie between a SignalR server and a ASP Core project using Identity cookies.
### Describe the bug
When I make a request with an Identity Cookie from my ASP Core project to the SignalR server, I get an exception regarding authentication.
```
fail: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[1]
An unhandled exception has occurred while executing the request.
System.InvalidOperationException: No authenticationScheme was specified, and there was no DefaultChallengeScheme found.
at Microsoft.AspNetCore.Authentication.AuthenticationService.ChallengeAsync(HttpContext context, String scheme, AuthenticationProperties properties)
at Microsoft.AspNetCore.Http.Connections.Internal.AuthorizeHelper.AuthorizeAsync(HttpContext context, IList`1 policies)
at Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionDispatcher.ExecuteNegotiateAsync(HttpContext context, HttpConnectionDispatcherOptions options)
at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)
at Microsoft.AspNetCore.Cors.Infrastructure.CorsMiddleware.InvokeCore(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)
```
### To Reproduce
Steps to reproduce the behavior:
1. Using this version of ASP.NET Core 2.2
2. Clone this repo: https://github.com/KieranDevvs/SignalRCoreSharedCookies
3. Run both projects and insert the absolute directory to the shared singing key e.g
`C:\Users\KieranDevlin\Documents\git\sources\SignalRCoreSharedCookies\KeyRing`
4. Register a new user & login (registering logs you in) to obtain a cookie.
5. Visit the contact page (the page that has authorisation) to initialze the SignalR connection.
6. Open the browser console to see the handshake failed and see the SignalR server console to see the exception thrown.
### Expected behavior
I expect the cookie to be read and to have `Context.User` populated with the identity of the cookie.
| True | Shared cookie not being read by SignalR server. - Im trying to share a cookie between a SignalR server and a ASP Core project using Identity cookies.
### Describe the bug
When I make a request with an Identity Cookie from my ASP Core project to the SignalR server, I get an exception regarding authentication.
```
fail: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[1]
An unhandled exception has occurred while executing the request.
System.InvalidOperationException: No authenticationScheme was specified, and there was no DefaultChallengeScheme found.
at Microsoft.AspNetCore.Authentication.AuthenticationService.ChallengeAsync(HttpContext context, String scheme, AuthenticationProperties properties)
at Microsoft.AspNetCore.Http.Connections.Internal.AuthorizeHelper.AuthorizeAsync(HttpContext context, IList`1 policies)
at Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionDispatcher.ExecuteNegotiateAsync(HttpContext context, HttpConnectionDispatcherOptions options)
at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)
at Microsoft.AspNetCore.Cors.Infrastructure.CorsMiddleware.InvokeCore(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)
```
### To Reproduce
Steps to reproduce the behavior:
1. Using this version of ASP.NET Core 2.2
2. Clone this repo: https://github.com/KieranDevvs/SignalRCoreSharedCookies
3. Run both projects and insert the absolute directory to the shared singing key e.g
`C:\Users\KieranDevlin\Documents\git\sources\SignalRCoreSharedCookies\KeyRing`
4. Register a new user & login (registering logs you in) to obtain a cookie.
5. Visit the contact page (the page that has authorisation) to initialze the SignalR connection.
6. Open the browser console to see the handshake failed and see the SignalR server console to see the exception thrown.
### Expected behavior
I expect the cookie to be read and to have `Context.User` populated with the identity of the cookie.
| non_priority | shared cookie not being read by signalr server im trying to share a cookie between a signalr server and a asp core project using identity cookies describe the bug when i make a request with an identity cookie from my asp core project to the signalr server i get an exception regarding authentication fail microsoft aspnetcore diagnostics developerexceptionpagemiddleware an unhandled exception has occurred while executing the request system invalidoperationexception no authenticationscheme was specified and there was no defaultchallengescheme found at microsoft aspnetcore authentication authenticationservice challengeasync httpcontext context string scheme authenticationproperties properties at microsoft aspnetcore http connections internal authorizehelper authorizeasync httpcontext context ilist policies at microsoft aspnetcore http connections internal httpconnectiondispatcher executenegotiateasync httpcontext context httpconnectiondispatcheroptions options at microsoft aspnetcore builder routermiddleware invoke httpcontext httpcontext at microsoft aspnetcore cors infrastructure corsmiddleware invokecore httpcontext context at microsoft aspnetcore diagnostics developerexceptionpagemiddleware invoke httpcontext context to reproduce steps to reproduce the behavior using this version of asp net core clone this repo run both projects and insert the absolute directory to the shared singing key e g c users kierandevlin documents git sources signalrcoresharedcookies keyring register a new user login registering logs you in to obtain a cookie visit the contact page the page that has authorisation to initialze the signalr connection open the browser console to see the handshake failed and see the signalr server console to see the exception thrown expected behavior i expect the cookie to be read and to have context user populated with the identity of the cookie | 0 |
563,302 | 16,679,608,381 | IssuesEvent | 2021-06-07 21:06:51 | kotlingang/kds | https://api.github.com/repos/kotlingang/kds | closed | Add `ExperimentalKDSApi()` annotation | flaw priority:normal | This annotation required to mark some APIs as unstable and give users the ability to choose which part of API they will use | 1.0 | Add `ExperimentalKDSApi()` annotation - This annotation required to mark some APIs as unstable and give users the ability to choose which part of API they will use | priority | add experimentalkdsapi annotation this annotation required to mark some apis as unstable and give users the ability to choose which part of api they will use | 1 |
3,469 | 2,538,465,572 | IssuesEvent | 2015-01-27 07:06:26 | newca12/gapt | https://api.github.com/repos/newca12/gapt | closed | program an auto proposition completion tool in LK | 1 star Component-TheoremProvers duplicate imported Milestone-Release3.0 Priority-High Type-Feature | _From [shaoli...@gmail.com](https://code.google.com/u/113190107447576027220/) on October 07, 2010 11:36:30_
Given a sequent (and maybe additional axioms other than the trivial ones), the method should return a Option[LKProof] object representing an LKProof of the sequent, if exist, using only propositional rules.
_Original issue: http://code.google.com/p/gapt/issues/detail?id=83_ | 1.0 | program an auto proposition completion tool in LK - _From [shaoli...@gmail.com](https://code.google.com/u/113190107447576027220/) on October 07, 2010 11:36:30_
Given a sequent (and maybe additional axioms other than the trivial ones), the method should return a Option[LKProof] object representing an LKProof of the sequent, if exist, using only propositional rules.
_Original issue: http://code.google.com/p/gapt/issues/detail?id=83_ | priority | program an auto proposition completion tool in lk from on october given a sequent and maybe additional axioms other than the trivial ones the method should return a option object representing an lkproof of the sequent if exist using only propositional rules original issue | 1 |
22,052 | 3,591,014,997 | IssuesEvent | 2016-02-01 09:44:26 | Stripeberry/unlabeled | https://api.github.com/repos/Stripeberry/unlabeled | closed | Сделать возможность использования 2 тэговых полей и более у справочника | auto-migrated Priority-Medium Type-Defect | ```
Сделать возможность использования 2
тэговых полей и более у справочника
```
Original issue reported on code.google.com by `stripeberry@gmail.com` on 6 Jul 2011 at 2:00 | 1.0 | Сделать возможность использования 2 тэговых полей и более у справочника - ```
Сделать возможность использования 2
тэговых полей и более у справочника
```
Original issue reported on code.google.com by `stripeberry@gmail.com` on 6 Jul 2011 at 2:00 | non_priority | сделать возможность использования тэговых полей и более у справочника сделать возможность использования тэговых полей и более у справочника original issue reported on code google com by stripeberry gmail com on jul at | 0 |
316,452 | 23,632,638,817 | IssuesEvent | 2022-08-25 10:38:40 | appsmithorg/appsmith | https://api.github.com/repos/appsmithorg/appsmith | opened | [Docs]: console logs feature documentation | Documentation | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Documentation Link
_No response_
### Describe the problem
We are adding the new console log feature to our platform. This issue is to track the documentation for the same.
### Describe the improvement
This is a new feature so we will need to add the documentation for the same. | 1.0 | [Docs]: console logs feature documentation - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Documentation Link
_No response_
### Describe the problem
We are adding the new console log feature to our platform. This issue is to track the documentation for the same.
### Describe the improvement
This is a new feature so we will need to add the documentation for the same. | non_priority | console logs feature documentation is there an existing issue for this i have searched the existing issues documentation link no response describe the problem we are adding the new console log feature to our platform this issue is to track the documentation for the same describe the improvement this is a new feature so we will need to add the documentation for the same | 0 |
120,262 | 17,644,075,194 | IssuesEvent | 2021-08-20 01:37:36 | DavidSpek/pipelines | https://api.github.com/repos/DavidSpek/pipelines | opened | CVE-2021-29573 (Medium) detected in tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl | security vulnerability | ## CVE-2021-29573 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/ec/98/f968caf5f65759e78873b900cbf0ae20b1699fb11268ecc0f892186419a7/tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl">https://files.pythonhosted.org/packages/ec/98/f968caf5f65759e78873b900cbf0ae20b1699fb11268ecc0f892186419a7/tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl</a></p>
<p>Path to dependency file: pipelines/contrib/components/openvino/ovms-deployer/containers/requirements.txt</p>
<p>Path to vulnerable library: pipelines/contrib/components/openvino/ovms-deployer/containers/requirements.txt,pipelines/samples/core/ai_platform/training</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.MaxPoolGradWithArgmax` is vulnerable to a division by 0. The implementation(https://github.com/tensorflow/tensorflow/blob/279bab6efa22752a2827621b7edb56a730233bd8/tensorflow/core/kernels/maxpooling_op.cc#L1033-L1034) fails to validate that the batch dimension of the tensor is non-zero, before dividing by this quantity. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
<p>Publish Date: 2021-05-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29573>CVE-2021-29573</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9vpm-rcf4-9wqw">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9vpm-rcf4-9wqw</a></p>
<p>Release Date: 2021-05-14</p>
<p>Fix Resolution: tensorflow - 2.5.0, tensorflow-cpu - 2.5.0, tensorflow-gpu - 2.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-29573 (Medium) detected in tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl - ## CVE-2021-29573 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/ec/98/f968caf5f65759e78873b900cbf0ae20b1699fb11268ecc0f892186419a7/tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl">https://files.pythonhosted.org/packages/ec/98/f968caf5f65759e78873b900cbf0ae20b1699fb11268ecc0f892186419a7/tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl</a></p>
<p>Path to dependency file: pipelines/contrib/components/openvino/ovms-deployer/containers/requirements.txt</p>
<p>Path to vulnerable library: pipelines/contrib/components/openvino/ovms-deployer/containers/requirements.txt,pipelines/samples/core/ai_platform/training</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.MaxPoolGradWithArgmax` is vulnerable to a division by 0. The implementation(https://github.com/tensorflow/tensorflow/blob/279bab6efa22752a2827621b7edb56a730233bd8/tensorflow/core/kernels/maxpooling_op.cc#L1033-L1034) fails to validate that the batch dimension of the tensor is non-zero, before dividing by this quantity. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
<p>Publish Date: 2021-05-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29573>CVE-2021-29573</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9vpm-rcf4-9wqw">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9vpm-rcf4-9wqw</a></p>
<p>Release Date: 2021-05-14</p>
<p>Fix Resolution: tensorflow - 2.5.0, tensorflow-cpu - 2.5.0, tensorflow-gpu - 2.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in tensorflow whl cve medium severity vulnerability vulnerable library tensorflow whl tensorflow is an open source machine learning framework for everyone library home page a href path to dependency file pipelines contrib components openvino ovms deployer containers requirements txt path to vulnerable library pipelines contrib components openvino ovms deployer containers requirements txt pipelines samples core ai platform training dependency hierarchy x tensorflow whl vulnerable library found in base branch master vulnerability details tensorflow is an end to end open source platform for machine learning the implementation of tf raw ops maxpoolgradwithargmax is vulnerable to a division by the implementation fails to validate that the batch dimension of the tensor is non zero before dividing by this quantity the fix will be included in tensorflow we will also cherrypick this commit on tensorflow tensorflow tensorflow and tensorflow as these are also affected and still in supported range publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tensorflow tensorflow cpu tensorflow gpu step up your open source security game with whitesource | 0 |
97,610 | 11,018,833,566 | IssuesEvent | 2019-12-05 11:19:29 | georchestra/mapstore2-georchestra | https://api.github.com/repos/georchestra/mapstore2-georchestra | closed | Create documentation for developer | Accepted Priority: Medium documentation | Indicate how to setup the development environment and links to dev external documentation (MapStore, General purpose resoures, georchestra doc...) | 1.0 | Create documentation for developer - Indicate how to setup the development environment and links to dev external documentation (MapStore, General purpose resoures, georchestra doc...) | non_priority | create documentation for developer indicate how to setup the development environment and links to dev external documentation mapstore general purpose resoures georchestra doc | 0 |
465,134 | 13,357,274,733 | IssuesEvent | 2020-08-31 09:32:51 | DIAGNijmegen/website-content | https://api.github.com/repos/DIAGNijmegen/website-content | opened | AI for health home page restructering | Priority: Medium content enhancement | - [ ] Vacancies in cards
- [ ] PhD projects in cards (with fixed max number, active only)
- [ ] Master projects in cards (with fixed max number, active only)
| 1.0 | AI for health home page restructering - - [ ] Vacancies in cards
- [ ] PhD projects in cards (with fixed max number, active only)
- [ ] Master projects in cards (with fixed max number, active only)
| priority | ai for health home page restructering vacancies in cards phd projects in cards with fixed max number active only master projects in cards with fixed max number active only | 1 |
180,600 | 21,625,797,590 | IssuesEvent | 2022-05-05 01:50:50 | mihorsky/Ghost | https://api.github.com/repos/mihorsky/Ghost | opened | CVE-2022-21227 (High) detected in sqlite3-4.2.0.tgz | security vulnerability | ## CVE-2022-21227 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>sqlite3-4.2.0.tgz</b></p></summary>
<p>Asynchronous, non-blocking SQLite3 bindings</p>
<p>Library home page: <a href="https://registry.npmjs.org/sqlite3/-/sqlite3-4.2.0.tgz">https://registry.npmjs.org/sqlite3/-/sqlite3-4.2.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/sqlite3/package.json</p>
<p>
Dependency Hierarchy:
- knex-migrator-3.5.0.tgz (Root Library)
- :x: **sqlite3-4.2.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package sqlite3 before 5.0.3 are vulnerable to Denial of Service (DoS) which will invoke the toString function of the passed parameter. If passed an invalid Function object it will throw and crash the V8 engine.
<p>Publish Date: 2022-05-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-21227>CVE-2022-21227</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-9qrh-qjmc-5w2p">https://github.com/advisories/GHSA-9qrh-qjmc-5w2p</a></p>
<p>Release Date: 2022-05-01</p>
<p>Fix Resolution: sqlite3 - 5.0.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-21227 (High) detected in sqlite3-4.2.0.tgz - ## CVE-2022-21227 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>sqlite3-4.2.0.tgz</b></p></summary>
<p>Asynchronous, non-blocking SQLite3 bindings</p>
<p>Library home page: <a href="https://registry.npmjs.org/sqlite3/-/sqlite3-4.2.0.tgz">https://registry.npmjs.org/sqlite3/-/sqlite3-4.2.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/sqlite3/package.json</p>
<p>
Dependency Hierarchy:
- knex-migrator-3.5.0.tgz (Root Library)
- :x: **sqlite3-4.2.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package sqlite3 before 5.0.3 are vulnerable to Denial of Service (DoS) which will invoke the toString function of the passed parameter. If passed an invalid Function object it will throw and crash the V8 engine.
<p>Publish Date: 2022-05-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-21227>CVE-2022-21227</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-9qrh-qjmc-5w2p">https://github.com/advisories/GHSA-9qrh-qjmc-5w2p</a></p>
<p>Release Date: 2022-05-01</p>
<p>Fix Resolution: sqlite3 - 5.0.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in tgz cve high severity vulnerability vulnerable library tgz asynchronous non blocking bindings library home page a href path to dependency file package json path to vulnerable library node modules package json dependency hierarchy knex migrator tgz root library x tgz vulnerable library found in base branch master vulnerability details the package before are vulnerable to denial of service dos which will invoke the tostring function of the passed parameter if passed an invalid function object it will throw and crash the engine publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
486,891 | 14,016,309,844 | IssuesEvent | 2020-10-29 14:22:44 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.xnxx.com - see bug description | browser-fenix engine-gecko priority-important | <!-- @browser: Firefox Mobile 84.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.1.0; Mobile; rv:84.0) Gecko/84.0 Firefox/84.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/60698 -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://www.xnxx.com/video-t0wwt42/get_here_and_fuck_your_stepmom_you_little_shit_
**Browser / Version**: Firefox Mobile 84.0
**Operating System**: Android 8.1.0
**Tested Another Browser**: Yes Chrome
**Problem type**: Something else
**Description**: video is not playing properly. video crashes
**Steps to Reproduce**:
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2020/10/43e82dbb-63e0-427a-9483-4744117cc428.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20201026092834</li><li>channel: nightly</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2020/10/762e0a17-5d1b-4388-ae97-b69dca5e6fc7)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.xnxx.com - see bug description - <!-- @browser: Firefox Mobile 84.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.1.0; Mobile; rv:84.0) Gecko/84.0 Firefox/84.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/60698 -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://www.xnxx.com/video-t0wwt42/get_here_and_fuck_your_stepmom_you_little_shit_
**Browser / Version**: Firefox Mobile 84.0
**Operating System**: Android 8.1.0
**Tested Another Browser**: Yes Chrome
**Problem type**: Something else
**Description**: video is not playing properly. video crashes
**Steps to Reproduce**:
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2020/10/43e82dbb-63e0-427a-9483-4744117cc428.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20201026092834</li><li>channel: nightly</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2020/10/762e0a17-5d1b-4388-ae97-b69dca5e6fc7)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | see bug description url browser version firefox mobile operating system android tested another browser yes chrome problem type something else description video is not playing properly video crashes steps to reproduce view the screenshot img alt screenshot src browser configuration gfx webrender all false gfx webrender blob images true gfx webrender enabled false image mem shared true buildid channel nightly hastouchscreen true mixed active content blocked false mixed passive content blocked false tracking content blocked false from with ❤️ | 1 |
9,317 | 24,411,897,717 | IssuesEvent | 2022-10-05 13:04:19 | Ivy-Apps/ivy-wallet | https://api.github.com/repos/Ivy-Apps/ivy-wallet | closed | [Architecture] Migrate Customer Journey string resources from `:app-base` to `:customer-journey` | dev easy good first issue architecture | ### Please confirm the following
- [X] I checked [the current issues](https://github.com/ILIYANGERMANOV/ivy-wallet/issues) for duplicate problems
### What would you like to improve?
Architecture **[ADR#1: Modularization](https://github.com/ILIYANGERMANOV/ivy-wallet/blob/develop/docs/architecture/ADR%231:%20Modularization%20(Passed).md)**.
**Goal:** Simplify `app-base` and de-couple resources.
$MODULE = `:customer-journey`
**How to:**
1. Find the strings that are used only in $MODULE
2. Create `res` folder in $MODULE
3. Create value folders for all locales:
- `value`
- `value-en`
- `value-it`
- ...
4. Move the strings used only in $MODULE to its newly created string resources folder.
5. Delete the strings resources from `:app-base` strings.
6. Run all tests and verify that everything works.
### Because...
- refactoring
- isolation
- reduces complexity
- reduces coupling
### Other
_No response_
### Logs
_No response_ | 1.0 | [Architecture] Migrate Customer Journey string resources from `:app-base` to `:customer-journey` - ### Please confirm the following
- [X] I checked [the current issues](https://github.com/ILIYANGERMANOV/ivy-wallet/issues) for duplicate problems
### What would you like to improve?
Architecture **[ADR#1: Modularization](https://github.com/ILIYANGERMANOV/ivy-wallet/blob/develop/docs/architecture/ADR%231:%20Modularization%20(Passed).md)**.
**Goal:** Simplify `app-base` and de-couple resources.
$MODULE = `:customer-journey`
**How to:**
1. Find the strings that are used only in $MODULE
2. Create `res` folder in $MODULE
3. Create value folders for all locales:
- `value`
- `value-en`
- `value-it`
- ...
4. Move the strings used only in $MODULE to its newly created string resources folder.
5. Delete the strings resources from `:app-base` strings.
6. Run all tests and verify that everything works.
### Because...
- refactoring
- isolation
- reduces complexity
- reduces coupling
### Other
_No response_
### Logs
_No response_ | non_priority | migrate customer journey string resources from app base to customer journey please confirm the following i checked for duplicate problems what would you like to improve architecture goal simplify app base and de couple resources module customer journey how to find the strings that are used only in module create res folder in module create value folders for all locales value value en value it move the strings used only in module to its newly created string resources folder delete the strings resources from app base strings run all tests and verify that everything works because refactoring isolation reduces complexity reduces coupling other no response logs no response | 0 |
767,552 | 26,931,298,731 | IssuesEvent | 2023-02-07 17:01:00 | WEKIT-ECS/MIRAGE-XR | https://api.github.com/repos/WEKIT-ECS/MIRAGE-XR | closed | Mobile: augmentation controls for rotate / resize are too fiddly | improvement mobile priority: high | In GitLab by @wild on Nov 2, 2021, 16:02
The bounding boxes for rotation/resizing are in some cases almost impossible to use on a mobile device (e.g., for the character model) - even on a big iPad it can still be tricky. Participants today were struggling a lot with the controls - can't we use some screen space rotation/resize controls alternatively? | 1.0 | Mobile: augmentation controls for rotate / resize are too fiddly - In GitLab by @wild on Nov 2, 2021, 16:02
The bounding boxes for rotation/resizing are in some cases almost impossible to use on a mobile device (e.g., for the character model) - even on a big iPad it can still be tricky. Participants today were struggling a lot with the controls - can't we use some screen space rotation/resize controls alternatively? | priority | mobile augmentation controls for rotate resize are too fiddly in gitlab by wild on nov the bounding boxes for rotation resizing are in some cases almost impossible to use on a mobile device e g for the character model even on a big ipad it can still be tricky participants today were struggling a lot with the controls can t we use some screen space rotation resize controls alternatively | 1 |
523,575 | 15,185,500,026 | IssuesEvent | 2021-02-15 11:01:21 | FAIRsharing/fairsharing.github.io | https://api.github.com/repos/FAIRsharing/fairsharing.github.io | opened | mocking alert in an alert box | Medium priority | Due to multiple alerts can take up too much space, task should resolve the issue by defining a way to show alerts in a more compact way.. | 1.0 | mocking alert in an alert box - Due to multiple alerts can take up too much space, task should resolve the issue by defining a way to show alerts in a more compact way.. | priority | mocking alert in an alert box due to multiple alerts can take up too much space task should resolve the issue by defining a way to show alerts in a more compact way | 1 |
801,157 | 28,454,871,990 | IssuesEvent | 2023-04-17 06:05:17 | masastack/MASA.Auth | https://api.github.com/repos/masastack/MASA.Auth | closed | Custom Login - Register, action button newline, should be displayed in one line | type/bug status/resolved severity/medium site/staging priority/p2 | 自定义登录-注册，操作按钮换行，应显示在一行，背景偏移了
| 1.0 | Custom Login - Register, action button newline, should be displayed in one line - 自定义登录-注册，操作按钮换行，应显示在一行，背景偏移了
| priority | custom login register action button newline should be displayed in one line 自定义登录 注册，操作按钮换行，应显示在一行，背景偏移了 | 1 |
50,483 | 21,112,162,083 | IssuesEvent | 2022-04-05 03:47:52 | dotnet/fsharp | https://api.github.com/repos/dotnet/fsharp | closed | Increase interleaving of long-running FCS requests | Area-LangService Feature Improvement | #### Summary
We should increase the interleaving of FCS requests. This will have the effect of increasing IDE responsiveness.
Based on discussions in F# Compiler Office Hours and with @auduchinok
#### Description
It is by design that FCS requests can take a long time, because they bring the whole build up-to-date in order to get latest results. The aim is to make sure
1. that these requests respect timely cancellation
2. that other requests get serviced while those requests are being processed.
In dev15 we did work to make sure that (1) is generally true, though we are not yet perfect.
However, (2) is not true. Take an FCS `CheckFileInProject` for example. This is made up of
1. [getOrCreateBuilderAndKeepAlive](https://github.com/Microsoft/visualfsharp/blob/master/src/fsharp/service/service.fs#L2624)
2. [GetCheckResultsBeforeFileInProject](https://github.com/Microsoft/visualfsharp/blob/master/src/fsharp/service/service.fs#L2636)
3. including multiple [ParseAndCheckProjectImpl](https://github.com/Microsoft/visualfsharp/blob/master/src/fsharp/service/service.fs#L2333) for in-memory cross-project references
4. [CheckOneFileImpl](https://github.com/Microsoft/visualfsharp/blob/master/src/fsharp/service/service.fs#L2636) which is really [CheckOneFile](https://github.com/Microsoft/visualfsharp/blob/master/src/fsharp/service/service.fs#L2555)
Of these, all respect relatively timely cancellation, but only (4) is broken into multiple reactor requests. 1-3 are executed as one single reactor request, meaning nothing else will get serviced until 1-3 either complete or are cancelled.
We should improve this and make (1) - (3) interleaved.
| 1.0 | Increase interleaving of long-running FCS requests - #### Summary
We should increase the interleaving of FCS requests. This will have the effect of increasing IDE responsiveness.
Based on discussions in F# Compiler Office Hours and with @auduchinok
#### Description
It is by design that FCS requests can take a long time, because they bring the whole build up-to-date in order to get latest results. The aim is to make sure
1. that these requests respect timely cancellation
2. that other requests get serviced while those requests are being processed.
In dev15 we did work to make sure that (1) is generally true, though we are not yet perfect.
However, (2) is not true. Take an FCS `CheckFileInProject` for example. This is made up of
1. [getOrCreateBuilderAndKeepAlive](https://github.com/Microsoft/visualfsharp/blob/master/src/fsharp/service/service.fs#L2624)
2. [GetCheckResultsBeforeFileInProject](https://github.com/Microsoft/visualfsharp/blob/master/src/fsharp/service/service.fs#L2636)
3. including multiple [ParseAndCheckProjectImpl](https://github.com/Microsoft/visualfsharp/blob/master/src/fsharp/service/service.fs#L2333) for in-memory cross-project references
4. [CheckOneFileImpl](https://github.com/Microsoft/visualfsharp/blob/master/src/fsharp/service/service.fs#L2636) which is really [CheckOneFile](https://github.com/Microsoft/visualfsharp/blob/master/src/fsharp/service/service.fs#L2555)
Of these, all respect relatively timely cancellation, but only (4) is broken into multiple reactor requests. 1-3 are executed as one single reactor request, meaning nothing else will get serviced until 1-3 either complete or are cancelled.
We should improve this and make (1) - (3) interleaved.
| non_priority | increase interleaving of long running fcs requests summary we should increase the interleaving of fcs requests this will have the effect of increasing ide responsiveness based on discussions in f compiler office hours and with auduchinok description it is by design that fcs requests can take a long time because they bring the whole build up to date in order to get latest results the aim is to make sure that these requests respect timely cancellation that other requests get serviced while those requests are being processed in we did work to make sure that is generally true though we are not yet perfect however is not true take an fcs checkfileinproject for example this is made up of including multiple for in memory cross project references which is really of these all respect relatively timely cancellation but only is broken into multiple reactor requests are executed as one single reactor request meaning nothing else will get serviced until either complete or are cancelled we should improve this and make interleaved | 0 |
35,652 | 6,487,152,505 | IssuesEvent | 2017-08-20 04:01:23 | gravitational/teleport | https://api.github.com/repos/gravitational/teleport | closed | Document an official example of an upstart script | documentation | This is probably related to #514 but for the interim can we at least have an official example of an upstart script in the documentation.
There is already an official example of a [systemd unit file](http://gravitational.com/teleport/docs/2.0/admin-guide/#teleport-daemon). Can we also please include an upstart/init.d file equivalent to this.
This will be especially for those that have to deploy Teleport to OSes that have not yet moved to systemd yet - biggest example is the latest Amazon Linux AMI still uses init.d.
I have been using the example of https://github.com/jaxxstorm/puppet-teleport at https://github.com/jaxxstorm/puppet-teleport/blob/master/templates/teleport.init.erb but I'd like verification if this could be officially documented for others?
The init.d script I am currently using is here - https://gist.github.com/mechastorm/ff4add694afada6ff6b4647aa2cb5797 | 1.0 | Document an official example of an upstart script - This is probably related to #514 but for the interim can we at least have an official example of an upstart script in the documentation.
There is already an official example of a [systemd unit file](http://gravitational.com/teleport/docs/2.0/admin-guide/#teleport-daemon). Can we also please include an upstart/init.d file equivalent to this.
This will be especially for those that have to deploy Teleport to OSes that have not yet moved to systemd yet - biggest example is the latest Amazon Linux AMI still uses init.d.
I have been using the example of https://github.com/jaxxstorm/puppet-teleport at https://github.com/jaxxstorm/puppet-teleport/blob/master/templates/teleport.init.erb but I'd like verification if this could be officially documented for others?
The init.d script I am currently using is here - https://gist.github.com/mechastorm/ff4add694afada6ff6b4647aa2cb5797 | non_priority | document an official example of an upstart script this is probably related to but for the interim can we at least have an official example of an upstart script in the documentation there is already an official example of a can we also please include an upstart init d file equivalent to this this will be especially for those that have to deploy teleport to oses that have not yet moved to systemd yet biggest example is the latest amazon linux ami still uses init d i have been using the example of at but i d like verification if this could be officially documented for others the init d script i am currently using is here | 0 |
312,951 | 23,448,635,002 | IssuesEvent | 2022-08-15 22:43:16 | Devslopes-Herd/BaseCamp-LandingPage | https://api.github.com/repos/Devslopes-Herd/BaseCamp-LandingPage | closed | Update Figma File | documentation enhancement | ## Action
- As a member I want to be able to access an editable Figma file.
- As a member I want to be able to view specific css and stylings of the components in Figma.
## Acceptance Criteria
- Figma project has been created and can be access
- not editable if possible
- Figma project is linked in the README.md of the BaseCamp-LandingPage repo | 1.0 | Update Figma File - ## Action
- As a member I want to be able to access an editable Figma file.
- As a member I want to be able to view specific css and stylings of the components in Figma.
## Acceptance Criteria
- Figma project has been created and can be access
- not editable if possible
- Figma project is linked in the README.md of the BaseCamp-LandingPage repo | non_priority | update figma file action as a member i want to be able to access an editable figma file as a member i want to be able to view specific css and stylings of the components in figma acceptance criteria figma project has been created and can be access not editable if possible figma project is linked in the readme md of the basecamp landingpage repo | 0 |
71,615 | 30,913,878,517 | IssuesEvent | 2023-08-05 03:13:31 | Zahlungsmittel/Zahlungsmittel | https://api.github.com/repos/Zahlungsmittel/Zahlungsmittel | opened | [CLOSED] login_call_updateUserInfos | refactor service: login server service: backend imported | <a href="https://github.com/ulfgebhardt"><img src="https://avatars.githubusercontent.com/u/1238238?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [ulfgebhardt](https://github.com/ulfgebhardt)**
_Sunday Nov 07, 2021 at 05:24 GMT_
_Originally opened as https://github.com/gradido/gradido/pull/1084_
----
<!-- You can find the latest issue templates here https://github.com/ulfgebhardt/issue-templates -->
## 🍰 Pullrequest
<!-- Describe the Pullrequest. Use Screenshots if possible. -->
This implements the call `updateUserInfos` on Apollo where it was implemented on the `login_server` beforehand.
Remarks:
- setting the `disabled` flag was removed
- `publisherId` is now set on login directly, not in updateUserInfos
### Issues
<!-- Which Issues does this fix, which are related?
- fixes #XXX
- relates #XXX
-->
- fixes #838
### Todo
<!-- In case some parts are still missing, list them here. -->
- [x] Transactions for the new settings table
- [x] Change password
----
_**[ulfgebhardt](https://github.com/ulfgebhardt)** included the following code: https://github.com/gradido/gradido/pull/1084/commits_
| 2.0 | [CLOSED] login_call_updateUserInfos - <a href="https://github.com/ulfgebhardt"><img src="https://avatars.githubusercontent.com/u/1238238?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [ulfgebhardt](https://github.com/ulfgebhardt)**
_Sunday Nov 07, 2021 at 05:24 GMT_
_Originally opened as https://github.com/gradido/gradido/pull/1084_
----
<!-- You can find the latest issue templates here https://github.com/ulfgebhardt/issue-templates -->
## 🍰 Pullrequest
<!-- Describe the Pullrequest. Use Screenshots if possible. -->
This implements the call `updateUserInfos` on Apollo where it was implemented on the `login_server` beforehand.
Remarks:
- setting the `disabled` flag was removed
- `publisherId` is now set on login directly, not in updateUserInfos
### Issues
<!-- Which Issues does this fix, which are related?
- fixes #XXX
- relates #XXX
-->
- fixes #838
### Todo
<!-- In case some parts are still missing, list them here. -->
- [x] Transactions for the new settings table
- [x] Change password
----
_**[ulfgebhardt](https://github.com/ulfgebhardt)** included the following code: https://github.com/gradido/gradido/pull/1084/commits_
| non_priority | login call updateuserinfos issue by sunday nov at gmt originally opened as 🍰 pullrequest this implements the call updateuserinfos on apollo where it was implemented on the login server beforehand remarks setting the disabled flag was removed publisherid is now set on login directly not in updateuserinfos issues which issues does this fix which are related fixes xxx relates xxx fixes todo transactions for the new settings table change password included the following code | 0 |
34,467 | 7,836,630,466 | IssuesEvent | 2018-06-17 21:56:12 | joomla/joomla-cms | https://api.github.com/repos/joomla/joomla-cms | closed | [4.0] this.parentNode is null (alerts) | J4 Issue No Code Attached Yet | ### Steps to reproduce the issue
- Fresh install of J4
- Click `Never` on the Stats alert
- Console error `this.parentNode is null [joomla-alert.js:84:9]`
```
close() {
this.dispatchCustomEvent('joomla.alert.close');
this.addEventListener("transitionend", function () {
this.dispatchCustomEvent('joomla.alert.closed');
this.parentNode.removeChild(this); <<<<<<<<<<< this line causing the error
}, false);
this.classList.remove('joomla-alert--show');
}
``` | 1.0 | [4.0] this.parentNode is null (alerts) - ### Steps to reproduce the issue
- Fresh install of J4
- Click `Never` on the Stats alert
- Console error `this.parentNode is null [joomla-alert.js:84:9]`
```
close() {
this.dispatchCustomEvent('joomla.alert.close');
this.addEventListener("transitionend", function () {
this.dispatchCustomEvent('joomla.alert.closed');
this.parentNode.removeChild(this); <<<<<<<<<<< this line causing the error
}, false);
this.classList.remove('joomla-alert--show');
}
``` | non_priority | this parentnode is null alerts steps to reproduce the issue fresh install of click never on the stats alert console error this parentnode is null close this dispatchcustomevent joomla alert close this addeventlistener transitionend function this dispatchcustomevent joomla alert closed this parentnode removechild this this line causing the error false this classlist remove joomla alert show | 0 |
128,370 | 17,512,212,591 | IssuesEvent | 2021-08-11 00:11:29 | lucasmedeiros/game-slot | https://api.github.com/repos/lucasmedeiros/game-slot | closed | [DESIGN] Prototipação da tela de perfil de usuário | design | ### Descrição
Criar protótipo inicial da tela de perfil de usuário utilizando Figma.
### Referências
| 1.0 | [DESIGN] Prototipação da tela de perfil de usuário - ### Descrição
Criar protótipo inicial da tela de perfil de usuário utilizando Figma.
### Referências
| non_priority | prototipação da tela de perfil de usuário descrição criar protótipo inicial da tela de perfil de usuário utilizando figma referências | 0 |
793,931 | 28,017,298,526 | IssuesEvent | 2023-03-28 00:27:29 | AY2223S2-CS2103T-W12-1/tp | https://api.github.com/repos/AY2223S2-CS2103T-W12-1/tp | closed | Storing age in FriendlyLink may be a feature flaw | type.Enhancement priority.High severity.Medium | Currently, age of the person is stored in FriendlyLink.
This makes it very troublesome for users, since age need to be updated yearly
Let's keep the date of birth of each person instead of their age. | 1.0 | Storing age in FriendlyLink may be a feature flaw - Currently, age of the person is stored in FriendlyLink.
This makes it very troublesome for users, since age need to be updated yearly
Let's keep the date of birth of each person instead of their age. | priority | storing age in friendlylink may be a feature flaw currently age of the person is stored in friendlylink this makes it very troublesome for users since age need to be updated yearly let s keep the date of birth of each person instead of their age | 1 |
403,861 | 27,438,725,057 | IssuesEvent | 2023-03-02 09:29:59 | alexpdev/torrentfile | https://api.github.com/repos/alexpdev/torrentfile | closed | Add configuration file feature | documentation enhancement question | Suggested enhancement to the CLI.
- Add an option to the CLI `--config` that looks for a configuration file with prefilled keys and values for other options available on the command line.
For example, the command `torrentfile create --config /path/to/content` would create a new torrentfile from the content using the information listed in a configuration file in the users current working directory called `torrentfile.ini`.
An example of the ini file:
```
[config]
announce = http://tracker1.net/21323announce
http://tracker2.net/23423announce
http://tracker3.org/349089dannounce
private = false
comment = comment to embed in torrent file metadata
source = Tracker3
piece-length = 21
http-seed = https://webpage.com/path/to/content
meta-version = 2
out = /path/to/newly_created.torrent
```
The cli can then automatically parse the contents of the config file, use preset defaults for any options that are not listed in the config file or on the command line, and consider options specified on the command line to have a higher priority than those indicated in the config file. | 1.0 | Add configuration file feature - Suggested enhancement to the CLI.
- Add an option to the CLI `--config` that looks for a configuration file with prefilled keys and values for other options available on the command line.
For example, the command `torrentfile create --config /path/to/content` would create a new torrentfile from the content using the information listed in a configuration file in the users current working directory called `torrentfile.ini`.
An example of the ini file:
```
[config]
announce = http://tracker1.net/21323announce
http://tracker2.net/23423announce
http://tracker3.org/349089dannounce
private = false
comment = comment to embed in torrent file metadata
source = Tracker3
piece-length = 21
http-seed = https://webpage.com/path/to/content
meta-version = 2
out = /path/to/newly_created.torrent
```
The cli can then automatically parse the contents of the config file, use preset defaults for any options that are not listed in the config file or on the command line, and consider options specified on the command line to have a higher priority than those indicated in the config file. | non_priority | add configuration file feature suggested enhancement to the cli add an option to the cli config that looks for a configuration file with prefilled keys and values for other options available on the command line for example the command torrentfile create config path to content would create a new torrentfile from the content using the information listed in a configuration file in the users current working directory called torrentfile ini an example of the ini file announce private false comment comment to embed in torrent file metadata source piece length http seed meta version out path to newly created torrent the cli can then automatically parse the contents of the config file use preset defaults for any options that are not listed in the config file or on the command line and consider options specified on the command line to have a higher priority than those indicated in the config file | 0 |
288,262 | 21,693,011,446 | IssuesEvent | 2022-05-09 17:08:38 | fleetdm/fleet | https://api.github.com/repos/fleetdm/fleet | closed | Fleet REST API documentation includes invalid examples of JSON | :improve documentation | Some examples in our REST API documentation include invalid JSON. For instance: https://fleetdm.com/docs/using-fleet/rest-api#example78 includes a spurious comma at the end. If a user were to follow the instructions and copy/paste the example Fleet would reject the payload.
We should take a lint pass against our REST API examples to make sure we have valid JSON. | 1.0 | Fleet REST API documentation includes invalid examples of JSON - Some examples in our REST API documentation include invalid JSON. For instance: https://fleetdm.com/docs/using-fleet/rest-api#example78 includes a spurious comma at the end. If a user were to follow the instructions and copy/paste the example Fleet would reject the payload.
We should take a lint pass against our REST API examples to make sure we have valid JSON. | non_priority | fleet rest api documentation includes invalid examples of json some examples in our rest api documentation include invalid json for instance includes a spurious comma at the end if a user were to follow the instructions and copy paste the example fleet would reject the payload we should take a lint pass against our rest api examples to make sure we have valid json | 0 |
593,499 | 18,009,489,508 | IssuesEvent | 2021-09-16 06:47:43 | YangCatalog/sdo_analysis | https://api.github.com/repos/YangCatalog/sdo_analysis | opened | Results should include the validation date | enhancement Priority: Low | IF POSSIBLE, then the pages like https://yangcatalog.org/results/ietf-l2-topology@2020-06-29_ietf.html should also display the date when the validation was executed.
Perhaps based on the file creation date ? | 1.0 | Results should include the validation date - IF POSSIBLE, then the pages like https://yangcatalog.org/results/ietf-l2-topology@2020-06-29_ietf.html should also display the date when the validation was executed.
Perhaps based on the file creation date ? | priority | results should include the validation date if possible then the pages like should also display the date when the validation was executed perhaps based on the file creation date | 1 |
258,785 | 19,573,667,863 | IssuesEvent | 2022-01-04 13:05:52 | TeamLEGWORK/LEGWORK | https://api.github.com/repos/TeamLEGWORK/LEGWORK | closed | license question | documentation | **Which documentation page is causing an issue?**
[LICENSE.rst](https://github.com/TeamLEGWORK/LEGWORK/blob/main/LICENSE.rst)
**What is the problem?**
Hi @katiebreivik @TomWagg getting started with the JOSS review ( -> https://github.com/openjournals/joss-reviews/issues/3998 ), I noticed that your license file only lists Katie as the `(c)` holder, while the code report gives roughly similarl contributions from the two of you and the paper submission has 3 authors (also Selma). Maybe it should be updated?
I know very little about licensing and copyright law though, so this is a purely optional suggestion.
| 1.0 | license question - **Which documentation page is causing an issue?**
[LICENSE.rst](https://github.com/TeamLEGWORK/LEGWORK/blob/main/LICENSE.rst)
**What is the problem?**
Hi @katiebreivik @TomWagg getting started with the JOSS review ( -> https://github.com/openjournals/joss-reviews/issues/3998 ), I noticed that your license file only lists Katie as the `(c)` holder, while the code report gives roughly similarl contributions from the two of you and the paper submission has 3 authors (also Selma). Maybe it should be updated?
I know very little about licensing and copyright law though, so this is a purely optional suggestion.
| non_priority | license question which documentation page is causing an issue what is the problem hi katiebreivik tomwagg getting started with the joss review i noticed that your license file only lists katie as the c holder while the code report gives roughly similarl contributions from the two of you and the paper submission has authors also selma maybe it should be updated i know very little about licensing and copyright law though so this is a purely optional suggestion | 0 |
634,934 | 20,374,679,033 | IssuesEvent | 2022-02-21 14:33:06 | teamforus/general | https://api.github.com/repos/teamforus/general | closed | CR: Redesign csv upload page | Priority: Should have Todo: Move to Productboard | Learn more about change requests here: https://bit.ly/39CWeEE
### Requested by:
- @SjoerdHilhorst
### Change description
- Currently there are 3 upload buttons, with two different functions:
Improvement proposal:
https://www.figma.com/file/VAVSBCaMLFGl7tS8qkG73x/Upload-.csv?node-id=1%3A80
Proposal is to automatically generate the vouchers when the csv is uploaded, without an extra button. | 1.0 | CR: Redesign csv upload page - Learn more about change requests here: https://bit.ly/39CWeEE
### Requested by:
- @SjoerdHilhorst
### Change description
- Currently there are 3 upload buttons, with two different functions:
Improvement proposal:
https://www.figma.com/file/VAVSBCaMLFGl7tS8qkG73x/Upload-.csv?node-id=1%3A80
Proposal is to automatically generate the vouchers when the csv is uploaded, without an extra button. | priority | cr redesign csv upload page learn more about change requests here requested by sjoerdhilhorst change description currently there are upload buttons with two different functions improvement proposal proposal is to automatically generate the vouchers when the csv is uploaded without an extra button | 1 |
237,024 | 7,755,059,921 | IssuesEvent | 2018-05-31 08:59:03 | palantir/atlasdb | https://api.github.com/repos/palantir/atlasdb | closed | Dynamic columns sort order | component: usability priority: P2 | Hi,
As it stands, dynamic columns are unordered when retrieved through the schema API, although they are presumably ordered in the (Cassandra) backend. RowResult still maintains a SortedMap for columns, but this gets flattened into a HashMap in schema-generated code. Can we export the sort order all the way?
R.
| 1.0 | Dynamic columns sort order - Hi,
As it stands, dynamic columns are unordered when retrieved through the schema API, although they are presumably ordered in the (Cassandra) backend. RowResult still maintains a SortedMap for columns, but this gets flattened into a HashMap in schema-generated code. Can we export the sort order all the way?
R.
| priority | dynamic columns sort order hi as it stands dynamic columns are unordered when retrieved through the schema api although they are presumably ordered in the cassandra backend rowresult still maintains a sortedmap for columns but this gets flattened into a hashmap in schema generated code can we export the sort order all the way r | 1 |
654,365 | 21,648,975,771 | IssuesEvent | 2022-05-06 07:15:33 | Blackoutburst/Wally | https://api.github.com/repos/Blackoutburst/Wally | opened | help command | feature easy low priority | Create a help command with a main help menu displaying the sub menu in embed messages like
- help Hypixel
- help practice
- help misc
- help staff
- help admin
Help staff and admin only display if the user does have the required permission | 1.0 | help command - Create a help command with a main help menu displaying the sub menu in embed messages like
- help Hypixel
- help practice
- help misc
- help staff
- help admin
Help staff and admin only display if the user does have the required permission | priority | help command create a help command with a main help menu displaying the sub menu in embed messages like help hypixel help practice help misc help staff help admin help staff and admin only display if the user does have the required permission | 1 |
520,548 | 15,087,980,129 | IssuesEvent | 2021-02-05 23:24:18 | jcsnorlax97/rentr | https://api.github.com/repos/jcsnorlax97/rentr | opened | Implement apartment listings in the back end | High Priority dev-task | This is to implement apartment listings in the back end.
This will require the creation of some listing object.
- This object will be expanded later.
I am guessing we will want some sort of "listing ID" system so we can track listings.
Relates to #23 | 1.0 | Implement apartment listings in the back end - This is to implement apartment listings in the back end.
This will require the creation of some listing object.
- This object will be expanded later.
I am guessing we will want some sort of "listing ID" system so we can track listings.
Relates to #23 | priority | implement apartment listings in the back end this is to implement apartment listings in the back end this will require the creation of some listing object this object will be expanded later i am guessing we will want some sort of listing id system so we can track listings relates to | 1 |
28,957 | 4,454,672,296 | IssuesEvent | 2016-08-23 02:10:08 | mautic/mautic | https://api.github.com/repos/mautic/mautic | closed | When using sparkpost placeholders end up empty | Bug Ready To Test | What type of report is this:
| Q | A
| ---| ---
| Bug report? | Y
| Feature request? | N
| Enhancement? | N
## Description:
After updating to 2.1 I've tried to switch to the Sparkpost API instead of the Sparkpost SMTP method.
This results on placeholders being replaced by nothing.
## If a bug:
| Q | A
| Mautic version | 2.1
| PHP version | 7.0.8
### Steps to reproduce:
1. Get a mautic 2.1 install
2. Create a regular SMTP connection with your sparkpost account
3. Create a form with an action "send results" or create an email to send after form submission. Use some placeholders in this mail, like {leadfield:First name} for example
4. Fill in the form
5. See the resulting email works with the placeholders substituded correctly when sending through SMTP.
6. Change to use the sparkpost API instead of regular SMTP
7. Try the form again and conclude the placeholders are replaced by empties.
### Log errors:
No errors in the log
| 1.0 | When using sparkpost placeholders end up empty - What type of report is this:
| Q | A
| ---| ---
| Bug report? | Y
| Feature request? | N
| Enhancement? | N
## Description:
After updating to 2.1 I've tried to switch to the Sparkpost API instead of the Sparkpost SMTP method.
This results on placeholders being replaced by nothing.
## If a bug:
| Q | A
| Mautic version | 2.1
| PHP version | 7.0.8
### Steps to reproduce:
1. Get a mautic 2.1 install
2. Create a regular SMTP connection with your sparkpost account
3. Create a form with an action "send results" or create an email to send after form submission. Use some placeholders in this mail, like {leadfield:First name} for example
4. Fill in the form
5. See the resulting email works with the placeholders substituded correctly when sending through SMTP.
6. Change to use the sparkpost API instead of regular SMTP
7. Try the form again and conclude the placeholders are replaced by empties.
### Log errors:
No errors in the log
| non_priority | when using sparkpost placeholders end up empty what type of report is this q a bug report y feature request n enhancement n description after updating to i ve tried to switch to the sparkpost api instead of the sparkpost smtp method this results on placeholders being replaced by nothing if a bug q a mautic version php version steps to reproduce get a mautic install create a regular smtp connection with your sparkpost account create a form with an action send results or create an email to send after form submission use some placeholders in this mail like leadfield first name for example fill in the form see the resulting email works with the placeholders substituded correctly when sending through smtp change to use the sparkpost api instead of regular smtp try the form again and conclude the placeholders are replaced by empties log errors no errors in the log | 0 |
53,804 | 13,262,339,842 | IssuesEvent | 2020-08-20 21:34:59 | icecube-trac/tix4 | https://api.github.com/repos/icecube-trac/tix4 | closed | [CascadeVariables] review branch by mjurkovic (Trac #2118) | Migrated from Trac analysis defect | http://code.icecube.wisc.edu/projects/icecube/browser/IceCube/sandbox/mjurkovic/projects/CascadeVariables/trunk
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/2118">https://code.icecube.wisc.edu/projects/icecube/ticket/2118</a>, reported by kjmeagherand owned by kjmeagher</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2019-02-12T22:16:55",
"_ts": "1550009815229985",
"description": "http://code.icecube.wisc.edu/projects/icecube/browser/IceCube/sandbox/mjurkovic/projects/CascadeVariables/trunk",
"reporter": "kjmeagher",
"cc": "",
"resolution": "insufficient resources",
"time": "2017-11-30T09:01:47",
"component": "analysis",
"summary": "[CascadeVariables] review branch by mjurkovic",
"priority": "normal",
"keywords": "",
"milestone": "Vernal Equinox 2019",
"owner": "kjmeagher",
"type": "defect"
}
```
</p>
</details>
| 1.0 | [CascadeVariables] review branch by mjurkovic (Trac #2118) - http://code.icecube.wisc.edu/projects/icecube/browser/IceCube/sandbox/mjurkovic/projects/CascadeVariables/trunk
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/2118">https://code.icecube.wisc.edu/projects/icecube/ticket/2118</a>, reported by kjmeagherand owned by kjmeagher</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2019-02-12T22:16:55",
"_ts": "1550009815229985",
"description": "http://code.icecube.wisc.edu/projects/icecube/browser/IceCube/sandbox/mjurkovic/projects/CascadeVariables/trunk",
"reporter": "kjmeagher",
"cc": "",
"resolution": "insufficient resources",
"time": "2017-11-30T09:01:47",
"component": "analysis",
"summary": "[CascadeVariables] review branch by mjurkovic",
"priority": "normal",
"keywords": "",
"milestone": "Vernal Equinox 2019",
"owner": "kjmeagher",
"type": "defect"
}
```
</p>
</details>
| non_priority | review branch by mjurkovic trac migrated from json status closed changetime ts description reporter kjmeagher cc resolution insufficient resources time component analysis summary review branch by mjurkovic priority normal keywords milestone vernal equinox owner kjmeagher type defect | 0 |
43,082 | 23,107,456,805 | IssuesEvent | 2022-07-27 10:01:53 | Kong/insomnia | https://api.github.com/repos/Kong/insomnia | closed | First request took very long? | N-investigation B-performance B-bug S-unverified | ### Expected Behavior
I am testing an API and the procedure is:
1. get token from POST request A
2. get json from POST request B with the token returned by POST request A
When I call POST request B, the first trial should perform as similarly as the other trials i.e. second one, third one, ...
### Actual Behavior
Below is the history of POST request B I called. Note that the first attempt took 35.6s and the later one were fast. I then stopped calling for a while and restarted, the first attempt took 37s. Later ones were fast. Stopped calling for while and restarted, the first attempt took 35.8s.
<img width="443" alt="Untitled 3" src="https://user-images.githubusercontent.com/63767886/159103033-9a69ba2f-d25d-455d-ba6c-05a2b6889ebc.png">
At first I thought it must be the API's problem because I have never encountered such problem with Insomina before and the performance of calling POST request A was consistent.
But then I tried using Postman to call POST Request B and found no such issue. I tried to start the POST request B with Postman and then Insomnia and the result is, Postman got the response pretty quick while Insomina stuck in the loading screen and got the response after dozens of seconds just like the behaviour I described above.
Here is one of the Timeline info of the very long POST request B (sensitive information is masked):
```
* Preparing request to https://xxx
* Current time is 2022-03-19T01:56:38.484Z
* Using libcurl/7.73.0 OpenSSL/1.1.1k zlib/1.2.11 brotli/1.0.9 zstd/1.4.9 libidn2/2.1.1 libssh2/1.9.0 nghttp2/1.42.0
* Using default HTTP version
* Disable timeout
* Enable automatic URL encoding
* Enable SSL validation
* Enable cookie sending with jar of 3 cookies
* Too old connection (129 seconds), disconnect it
* Connection 62 seems to be dead!
* Closing connection 62
* TLSv1.2 (OUT), TLS alert, close notify (256):
* Hostname in DNS cache was stale, zapped
* Trying xxx:443...
* Connected to xxx.com (xxx) port 443 (#63)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /var/folders/d3/k2by8htd2fl9b5bfs0hn46z40000gn/T/insomnia_2021.7.2/ca-certs.pem
* CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
* subject: OU=Domain Control Validated; CN=*.xxx.com
* start date: Jul 8 04:51:09 2020 GMT
* expire date: Jul 8 04:51:09 2022 GMT
* subjectAltName: host "xxx.com" matched cert's "*.xxx.com"
* issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7ffb460b4e00)
> POST /xxx HTTP/2
> Host: xxx.com
> user-agent: insomnia/2021.7.2
> cookie: xxx=yyy
> content-type: application/json
> authorization: Bearer xxx
> accept: */*
> content-length: 39
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
| {
| "xxx": "yyy"
| }
* We are completely uploaded and fine
< HTTP/2 200
< date: Sat, 19 Mar 2022 01:57:21 GMT
< content-type: application/json; charset=utf-8
< content-length: 452
< cache-control: No-Cache
< pragma: no-cache
< expires: -1
< x-xxx-request-id: yyy
* Replaced cookie xxx="yyy" for domain xxx.com, path /, expire 0
< set-cookie: xxx=yyy;Path=/
* Received 452 B chunk
* Connection #63 to host xxx.com left intact
* Saved 1 cookie
```
### Reproduction Steps
_No response_
### Is there an existing issue for this?
- [X] I have searched the [issue tracker](https://www.github.com/Kong/insomnia/issues) for this problem.
### Additional Information
_No response_
### Insomnia Version
2021.7.2
### What operating system are you using?
macOS
### Operating System Version
Catalina 10.15.6 (19G2021)
### Installation method
https://insomnia.rest/download
### Last Known Working Insomnia version
_No response_ | True | First request took very long? - ### Expected Behavior
I am testing an API and the procedure is:
1. get token from POST request A
2. get json from POST request B with the token returned by POST request A
When I call POST request B, the first trial should perform as similarly as the other trials i.e. second one, third one, ...
### Actual Behavior
Below is the history of POST request B I called. Note that the first attempt took 35.6s and the later one were fast. I then stopped calling for a while and restarted, the first attempt took 37s. Later ones were fast. Stopped calling for while and restarted, the first attempt took 35.8s.
<img width="443" alt="Untitled 3" src="https://user-images.githubusercontent.com/63767886/159103033-9a69ba2f-d25d-455d-ba6c-05a2b6889ebc.png">
At first I thought it must be the API's problem because I have never encountered such problem with Insomina before and the performance of calling POST request A was consistent.
But then I tried using Postman to call POST Request B and found no such issue. I tried to start the POST request B with Postman and then Insomnia and the result is, Postman got the response pretty quick while Insomina stuck in the loading screen and got the response after dozens of seconds just like the behaviour I described above.
Here is one of the Timeline info of the very long POST request B (sensitive information is masked):
```
* Preparing request to https://xxx
* Current time is 2022-03-19T01:56:38.484Z
* Using libcurl/7.73.0 OpenSSL/1.1.1k zlib/1.2.11 brotli/1.0.9 zstd/1.4.9 libidn2/2.1.1 libssh2/1.9.0 nghttp2/1.42.0
* Using default HTTP version
* Disable timeout
* Enable automatic URL encoding
* Enable SSL validation
* Enable cookie sending with jar of 3 cookies
* Too old connection (129 seconds), disconnect it
* Connection 62 seems to be dead!
* Closing connection 62
* TLSv1.2 (OUT), TLS alert, close notify (256):
* Hostname in DNS cache was stale, zapped
* Trying xxx:443...
* Connected to xxx.com (xxx) port 443 (#63)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /var/folders/d3/k2by8htd2fl9b5bfs0hn46z40000gn/T/insomnia_2021.7.2/ca-certs.pem
* CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
* subject: OU=Domain Control Validated; CN=*.xxx.com
* start date: Jul 8 04:51:09 2020 GMT
* expire date: Jul 8 04:51:09 2022 GMT
* subjectAltName: host "xxx.com" matched cert's "*.xxx.com"
* issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7ffb460b4e00)
> POST /xxx HTTP/2
> Host: xxx.com
> user-agent: insomnia/2021.7.2
> cookie: xxx=yyy
> content-type: application/json
> authorization: Bearer xxx
> accept: */*
> content-length: 39
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
| {
| "xxx": "yyy"
| }
* We are completely uploaded and fine
< HTTP/2 200
< date: Sat, 19 Mar 2022 01:57:21 GMT
< content-type: application/json; charset=utf-8
< content-length: 452
< cache-control: No-Cache
< pragma: no-cache
< expires: -1
< x-xxx-request-id: yyy
* Replaced cookie xxx="yyy" for domain xxx.com, path /, expire 0
< set-cookie: xxx=yyy;Path=/
* Received 452 B chunk
* Connection #63 to host xxx.com left intact
* Saved 1 cookie
```
### Reproduction Steps
_No response_
### Is there an existing issue for this?
- [X] I have searched the [issue tracker](https://www.github.com/Kong/insomnia/issues) for this problem.
### Additional Information
_No response_
### Insomnia Version
2021.7.2
### What operating system are you using?
macOS
### Operating System Version
Catalina 10.15.6 (19G2021)
### Installation method
https://insomnia.rest/download
### Last Known Working Insomnia version
_No response_ | non_priority | first request took very long expected behavior i am testing an api and the procedure is get token from post request a get json from post request b with the token returned by post request a when i call post request b the first trial should perform as similarly as the other trials i e second one third one actual behavior below is the history of post request b i called note that the first attempt took and the later one were fast i then stopped calling for a while and restarted the first attempt took later ones were fast stopped calling for while and restarted the first attempt took img width alt untitled src at first i thought it must be the api s problem because i have never encountered such problem with insomina before and the performance of calling post request a was consistent but then i tried using postman to call post request b and found no such issue i tried to start the post request b with postman and then insomnia and the result is postman got the response pretty quick while insomina stuck in the loading screen and got the response after dozens of seconds just like the behaviour i described above here is one of the timeline info of the very long post request b sensitive information is masked preparing request to current time is using libcurl openssl zlib brotli zstd using default http version disable timeout enable automatic url encoding enable ssl validation enable cookie sending with jar of cookies too old connection seconds disconnect it connection seems to be dead closing connection out tls alert close notify hostname in dns cache was stale zapped trying xxx connected to xxx com xxx port alpn offering alpn offering http successfully set certificate verify locations cafile var folders t insomnia ca certs pem capath none out tls handshake client hello in tls handshake server hello in tls handshake certificate in tls handshake server key exchange in tls handshake server finished out tls handshake client key exchange out tls change cipher change cipher spec out tls handshake finished in tls handshake finished ssl connection using ecdhe rsa gcm alpn server accepted to use server certificate subject ou domain control validated cn xxx com start date jul gmt expire date jul gmt subjectaltname host xxx com matched cert s xxx com issuer c us st arizona l scottsdale o godaddy com inc ou cn go daddy secure certificate authority ssl certificate verify ok using server supports multi use connection state changed http confirmed copying http data in stream buffer to connection buffer after upgrade len using stream id easy handle post xxx http host xxx com user agent insomnia cookie xxx yyy content type application json authorization bearer xxx accept content length connection state changed max concurrent streams xxx yyy we are completely uploaded and fine http date sat mar gmt content type application json charset utf content length cache control no cache pragma no cache expires x xxx request id yyy replaced cookie xxx yyy for domain xxx com path expire set cookie xxx yyy path received b chunk connection to host xxx com left intact saved cookie reproduction steps no response is there an existing issue for this i have searched the for this problem additional information no response insomnia version what operating system are you using macos operating system version catalina installation method last known working insomnia version no response | 0 |
659,055 | 21,915,725,719 | IssuesEvent | 2022-05-21 19:48:20 | JRSofty/personal-webpage | https://api.github.com/repos/JRSofty/personal-webpage | opened | Make the site accessable | enhancement Priority | Provide the following items:
[ ] Attributes used by screen readers
[ ] Alt text for any images
[ ] Check that fonts are easily read for those with vision issues
[ ] Ensure colors do not cause problems with vision issues | 1.0 | Make the site accessable - Provide the following items:
[ ] Attributes used by screen readers
[ ] Alt text for any images
[ ] Check that fonts are easily read for those with vision issues
[ ] Ensure colors do not cause problems with vision issues | priority | make the site accessable provide the following items attributes used by screen readers alt text for any images check that fonts are easily read for those with vision issues ensure colors do not cause problems with vision issues | 1 |
720,023 | 24,776,299,601 | IssuesEvent | 2022-10-23 19:24:40 | sjdv1982/seamless | https://api.github.com/repos/sjdv1982/seamless | closed | Mounts in library argument contexts lead to spurious error messages | bug low priority | Tested with a context mapped with map_list
Of the kind:
```
Undestroyed Seamless context: <toplevel> (0x7f0194f3bee0), mount points may remain
```
a long list, when the program exits.
Ignore mounts in context arguments? | 1.0 | Mounts in library argument contexts lead to spurious error messages - Tested with a context mapped with map_list
Of the kind:
```
Undestroyed Seamless context: <toplevel> (0x7f0194f3bee0), mount points may remain
```
a long list, when the program exits.
Ignore mounts in context arguments? | priority | mounts in library argument contexts lead to spurious error messages tested with a context mapped with map list of the kind undestroyed seamless context mount points may remain a long list when the program exits ignore mounts in context arguments | 1 |
309,775 | 9,480,121,763 | IssuesEvent | 2019-04-20 15:07:08 | ff-notes/ff | https://api.github.com/repos/ff-notes/ff | closed | Comprehensible tracked task error message | component_CLI level_Research priority_High type_Bug | This error message is not comprehensible:
```
$ ff done 4710P17JRPQ-1333OPN2L
ff: Error "A tracked note must be modified in its source." []
```
Should be something like
```
ff: error: A tracked note must be edited in its source: https://github.com/ff-notes/ff/issues/83
``` | 1.0 | Comprehensible tracked task error message - This error message is not comprehensible:
```
$ ff done 4710P17JRPQ-1333OPN2L
ff: Error "A tracked note must be modified in its source." []
```
Should be something like
```
ff: error: A tracked note must be edited in its source: https://github.com/ff-notes/ff/issues/83
``` | priority | comprehensible tracked task error message this error message is not comprehensible ff done ff error a tracked note must be modified in its source should be something like ff error a tracked note must be edited in its source | 1 |
459,427 | 13,192,980,699 | IssuesEvent | 2020-08-13 14:34:02 | Warcraft-GoA-Development-Team/Warcraft-Guardians-of-Azeroth | https://api.github.com/repos/Warcraft-GoA-Development-Team/Warcraft-Guardians-of-Azeroth | closed | Celestial religious revolt leader title is written in all caps | :beetle: bug - localisation :scroll: :exclamation: priority high | <!--
**DO NOT REMOVE PRE-EXISTING LINES**
------------------------------------------------------------------------------------------------------------
-->
**Mod version:**
d2df6541e
**Are you using any submods/mods? If so, which?**
No
**Please explain your issue in as much detail as possible:**
Celestial religious revolt leader title is written in all caps
M O N K
**Upload screenshots of the problem localization:**
<details>
<summary>Click to expand</summary>
</details> | 1.0 | Celestial religious revolt leader title is written in all caps - <!--
**DO NOT REMOVE PRE-EXISTING LINES**
------------------------------------------------------------------------------------------------------------
-->
**Mod version:**
d2df6541e
**Are you using any submods/mods? If so, which?**
No
**Please explain your issue in as much detail as possible:**
Celestial religious revolt leader title is written in all caps
M O N K
**Upload screenshots of the problem localization:**
<details>
<summary>Click to expand</summary>
</details> | priority | celestial religious revolt leader title is written in all caps do not remove pre existing lines mod version are you using any submods mods if so which no please explain your issue in as much detail as possible celestial religious revolt leader title is written in all caps m o n k upload screenshots of the problem localization click to expand | 1 |
91,975 | 3,863,915,516 | IssuesEvent | 2016-04-08 11:40:29 | CoderDojo/community-platform | https://api.github.com/repos/CoderDojo/community-platform | opened | Map Issue when you search fir "EGYPT" | bug dojo listings low priority up-for-grabs | I search for Egypt and it gives me a Dojo in Cyprus. This seems to only happen with this country at the moment.
<img width="1162" alt="screen shot 2016-04-08 at 11 49 25" src="https://cloud.githubusercontent.com/assets/10957621/14382450/c653042c-fd85-11e5-82f8-9c27cda462b2.png">
| 1.0 | Map Issue when you search fir "EGYPT" - I search for Egypt and it gives me a Dojo in Cyprus. This seems to only happen with this country at the moment.
<img width="1162" alt="screen shot 2016-04-08 at 11 49 25" src="https://cloud.githubusercontent.com/assets/10957621/14382450/c653042c-fd85-11e5-82f8-9c27cda462b2.png">
| priority | map issue when you search fir egypt i search for egypt and it gives me a dojo in cyprus this seems to only happen with this country at the moment img width alt screen shot at src | 1 |
707,988 | 24,326,513,868 | IssuesEvent | 2022-09-30 15:13:05 | geosolutions-it/MapStore2 | https://api.github.com/repos/geosolutions-it/MapStore2 | opened | Simplified query params issues | bug Priority: High C169-Rennes-Métropole-2021-GeOrchestra3 | ## Description
<!-- Add here a few sentences describing the bug. -->
Issues found during functional testing in DEV
*Expected Result*
<!-- Describe here the expected result -->
https://github.com/geosolutions-it/MapStore2/wiki/%5BProposal%5D-MapStore-query-parameters-simplification
*Current Result*
<!-- Describe here the current behavior -->
`?featureinfo=42.212,-108.369
working
`?addLayers=gs:us_states`
working
`?addLayers=gs:us_states&bbox=-117,43,-101,49`
working
`?addLayers=gs:us_states¢er=-106.458,45.699&zoom=5&mapInfo=gs:us_states&mapInfoFilter=STATE_FIPS=30`
Identify not triggered
`?addLayers=gs:us_states&bbox=-117,43,-101,49&mapInfo=gs:us_states&mapInfoFilter=STATE_FIPS=30`
not working, identify not showing up (without _bbox_ works)
`?addLayers=gs:spearfish_roads,gs:spearfish_bugsites;gs_stable_csw,gs:spearfish_archsites;gs_stable_csw,gs:spearfish_restricted&mapInfo=gs:spearfish_restricted&mapInfoFilter=cat=3`
working
`?addLayers=gs:spearfish_roads,gs:spearfish_bugsites;gs_stable_csw,gs:spearfish_archsites;gs_stable_csw,gs:spearfish_restricted&mapInfo=gs:spearfish_restricted&mapInfoFilter=cat=3&bbox=-103.882,44.374,-103.618,44.501`
Identify not working
`?addLayers=gs:spearfish_roads,gs:spearfish_bugsites;gs_stable_csw,gs:spearfish_archsites;gs_stable_csw,gs:spearfish_restricted&mapInfo=gs:spearfish_restricted&mapInfoFilter=cat=3&layerFilters=cat='4',str1='Beetle site',str1='Bob Miller',cat='3'`
_layerFilters_ is not processed as expected if multiple filters are present (one for each layer in the list) it works only if one filter is defined
`?addLayers=gs:spearfish_roads,gs:spearfish_bugsites;gs_stable_csw,gs:spearfish_archsites;gs_stable_csw,gs:spearfish_restricted&mapInfo=gs:spearfish_restricted&mapInfoFilter=cat=3&layerFilters=cat='4'&background=gs:spearfish_dem;gs_stable_wms`
not working as expected _background_ only works if the source is specified while it should work also without specifying it with the default source
`?addLayers=gs:spearfish_roads,gs:us_states,gs:spearfish_bugsites;gs_stable_csw,gs:spearfish_archsites;gs_stable_csw,gs:spearfish_restricted&layerFilters=cat='4'&background=gs:us_states;gs_stable_wms&actions=[{"type":"SEARCH:SEARCH_WITH_FILTER","cql_filter":"STATE_FIPS=34","layer":"gs:us_states"}] `
layer _gs:us_states_ seems not queryable (but it should be) and a MS notofication appears. Why?
- [x] Not browser related
<details><summary> <b>Browser info</b> </summary>
<!-- If browser related, please compile the following table -->
<!-- If your browser is not in the list please add a new row to the table with the version -->
(use this site: <a href="https://www.whatsmybrowser.org/">https://www.whatsmybrowser.org/</a> for non expert users)
| Browser Affected | Version |
|---|---|
|Internet Explorer| |
|Edge| |
|Chrome| |
|Firefox| |
|Safari| |
</details>
## Other useful information
<!-- error stack trace, screenshot, videos, or link to repository code are welcome -->
| 1.0 | Simplified query params issues - ## Description
<!-- Add here a few sentences describing the bug. -->
Issues found during functional testing in DEV
*Expected Result*
<!-- Describe here the expected result -->
https://github.com/geosolutions-it/MapStore2/wiki/%5BProposal%5D-MapStore-query-parameters-simplification
*Current Result*
<!-- Describe here the current behavior -->
`?featureinfo=42.212,-108.369
working
`?addLayers=gs:us_states`
working
`?addLayers=gs:us_states&bbox=-117,43,-101,49`
working
`?addLayers=gs:us_states¢er=-106.458,45.699&zoom=5&mapInfo=gs:us_states&mapInfoFilter=STATE_FIPS=30`
Identify not triggered
`?addLayers=gs:us_states&bbox=-117,43,-101,49&mapInfo=gs:us_states&mapInfoFilter=STATE_FIPS=30`
not working, identify not showing up (without _bbox_ works)
`?addLayers=gs:spearfish_roads,gs:spearfish_bugsites;gs_stable_csw,gs:spearfish_archsites;gs_stable_csw,gs:spearfish_restricted&mapInfo=gs:spearfish_restricted&mapInfoFilter=cat=3`
working
`?addLayers=gs:spearfish_roads,gs:spearfish_bugsites;gs_stable_csw,gs:spearfish_archsites;gs_stable_csw,gs:spearfish_restricted&mapInfo=gs:spearfish_restricted&mapInfoFilter=cat=3&bbox=-103.882,44.374,-103.618,44.501`
Identify not working
`?addLayers=gs:spearfish_roads,gs:spearfish_bugsites;gs_stable_csw,gs:spearfish_archsites;gs_stable_csw,gs:spearfish_restricted&mapInfo=gs:spearfish_restricted&mapInfoFilter=cat=3&layerFilters=cat='4',str1='Beetle site',str1='Bob Miller',cat='3'`
_layerFilters_ is not processed as expected if multiple filters are present (one for each layer in the list) it works only if one filter is defined
`?addLayers=gs:spearfish_roads,gs:spearfish_bugsites;gs_stable_csw,gs:spearfish_archsites;gs_stable_csw,gs:spearfish_restricted&mapInfo=gs:spearfish_restricted&mapInfoFilter=cat=3&layerFilters=cat='4'&background=gs:spearfish_dem;gs_stable_wms`
not working as expected _background_ only works if the source is specified while it should work also without specifying it with the default source
`?addLayers=gs:spearfish_roads,gs:us_states,gs:spearfish_bugsites;gs_stable_csw,gs:spearfish_archsites;gs_stable_csw,gs:spearfish_restricted&layerFilters=cat='4'&background=gs:us_states;gs_stable_wms&actions=[{"type":"SEARCH:SEARCH_WITH_FILTER","cql_filter":"STATE_FIPS=34","layer":"gs:us_states"}] `
layer _gs:us_states_ seems not queryable (but it should be) and a MS notofication appears. Why?
- [x] Not browser related
<details><summary> <b>Browser info</b> </summary>
<!-- If browser related, please compile the following table -->
<!-- If your browser is not in the list please add a new row to the table with the version -->
(use this site: <a href="https://www.whatsmybrowser.org/">https://www.whatsmybrowser.org/</a> for non expert users)
| Browser Affected | Version |
|---|---|
|Internet Explorer| |
|Edge| |
|Chrome| |
|Firefox| |
|Safari| |
</details>
## Other useful information
<!-- error stack trace, screenshot, videos, or link to repository code are welcome -->
| priority | simplified query params issues description issues found during functional testing in dev expected result current result featureinfo working addlayers gs us states working addlayers gs us states bbox working addlayers gs us states center zoom mapinfo gs us states mapinfofilter state fips identify not triggered addlayers gs us states bbox mapinfo gs us states mapinfofilter state fips not working identify not showing up without bbox works addlayers gs spearfish roads gs spearfish bugsites gs stable csw gs spearfish archsites gs stable csw gs spearfish restricted mapinfo gs spearfish restricted mapinfofilter cat working addlayers gs spearfish roads gs spearfish bugsites gs stable csw gs spearfish archsites gs stable csw gs spearfish restricted mapinfo gs spearfish restricted mapinfofilter cat bbox identify not working addlayers gs spearfish roads gs spearfish bugsites gs stable csw gs spearfish archsites gs stable csw gs spearfish restricted mapinfo gs spearfish restricted mapinfofilter cat layerfilters cat beetle site bob miller cat layerfilters is not processed as expected if multiple filters are present one for each layer in the list it works only if one filter is defined addlayers gs spearfish roads gs spearfish bugsites gs stable csw gs spearfish archsites gs stable csw gs spearfish restricted mapinfo gs spearfish restricted mapinfofilter cat layerfilters cat background gs spearfish dem gs stable wms not working as expected background only works if the source is specified while it should work also without specifying it with the default source addlayers gs spearfish roads gs us states gs spearfish bugsites gs stable csw gs spearfish archsites gs stable csw gs spearfish restricted layerfilters cat background gs us states gs stable wms actions layer gs us states seems not queryable but it should be and a ms notofication appears why not browser related browser info use this site a href for non expert users browser affected version internet explorer edge chrome firefox safari other useful information | 1 |
126,118 | 16,978,637,568 | IssuesEvent | 2021-06-30 05:23:13 | woocommerce/woocommerce-android | https://api.github.com/repos/woocommerce/woocommerce-android | closed | Update snackbars flow on order update | category: design feature: order details type: enhancement | Parent: #4248
We should align to iOS implementation for showing snackbars on order's update:
1. Do not show "Order completed 🎉 " when an order has been marked as completed. Show it only when the user updated the state via `Mark as done` button.
2. Do not show to which state the user updated the order. Show only "Order status updated" label.
p1624022453321700-slack-CGPNUU63E | 1.0 | Update snackbars flow on order update - Parent: #4248
We should align to iOS implementation for showing snackbars on order's update:
1. Do not show "Order completed 🎉 " when an order has been marked as completed. Show it only when the user updated the state via `Mark as done` button.
2. Do not show to which state the user updated the order. Show only "Order status updated" label.
p1624022453321700-slack-CGPNUU63E | non_priority | update snackbars flow on order update parent we should align to ios implementation for showing snackbars on order s update do not show order completed 🎉 when an order has been marked as completed show it only when the user updated the state via mark as done button do not show to which state the user updated the order show only order status updated label slack | 0 |
512,969 | 14,913,419,560 | IssuesEvent | 2021-01-22 14:07:07 | wazuh/wazuh-documentation | https://api.github.com/repos/wazuh/wazuh-documentation | opened | Installation Guide - Open Distro - Rephrase | priority: medium type: refactor | Hi! This issue aims to change the text in the Wazuh documentation - Installation Guide - Open Distro
Regards,
Pilar | 1.0 | Installation Guide - Open Distro - Rephrase - Hi! This issue aims to change the text in the Wazuh documentation - Installation Guide - Open Distro
Regards,
Pilar | priority | installation guide open distro rephrase hi this issue aims to change the text in the wazuh documentation installation guide open distro regards pilar | 1 |
124,630 | 4,928,565,588 | IssuesEvent | 2016-11-27 11:35:23 | fommil/foolish-football | https://api.github.com/repos/fommil/foolish-football | opened | fix the tests | Bug Priority | tests are popping up the UI... bit of a weird regression. I guess this is what accepting PRs without a CI does. | 1.0 | fix the tests - tests are popping up the UI... bit of a weird regression. I guess this is what accepting PRs without a CI does. | priority | fix the tests tests are popping up the ui bit of a weird regression i guess this is what accepting prs without a ci does | 1 |
6,227 | 5,319,331,305 | IssuesEvent | 2017-02-14 06:29:37 | golang/go | https://api.github.com/repos/golang/go | closed | cmd/compile: remove inl cost toolstash hacks | Performance | [CL 31674](https://go-review.googlesource.com/c/31674/) was reverted because it caused a Google internal test to fail. It really should not have; it probably indicates an existing latent compiler bug. And I'd like to remove these hacks for 1.9. I don't have access to the test; this is a request to extract a public version of the test so I can try to fix it.
cc @mdempsky @dsnet
| True | cmd/compile: remove inl cost toolstash hacks - [CL 31674](https://go-review.googlesource.com/c/31674/) was reverted because it caused a Google internal test to fail. It really should not have; it probably indicates an existing latent compiler bug. And I'd like to remove these hacks for 1.9. I don't have access to the test; this is a request to extract a public version of the test so I can try to fix it.
cc @mdempsky @dsnet
| non_priority | cmd compile remove inl cost toolstash hacks was reverted because it caused a google internal test to fail it really should not have it probably indicates an existing latent compiler bug and i d like to remove these hacks for i don t have access to the test this is a request to extract a public version of the test so i can try to fix it cc mdempsky dsnet | 0 |
180,830 | 13,961,377,309 | IssuesEvent | 2020-10-25 02:54:34 | dart-lang/sdk | https://api.github.com/repos/dart-lang/sdk | reopened | observatory_ui_2 and service_2 tests failing | area-observatory area-test type-bug | [165420](https://dart-review.googlesource.com/c/sdk/+/165420) introduced two new *_2 duplicate test sets, which largely passes with the exception of:
- [ ] service_2/dds_log_history_size_simple_test/dds
- [ ] observatory_ui_2/app_test
- [ ] service_2/get_cpu_samples_rpc_test/service
- [x] service_2/get_isolate_after_language_error_test/dds
- [x] service_2/get_isolate_after_language_error_test/service
- [x] service_2/get_version_rpc_test/dds
- [x] service_2/get_version_rpc_test/service
- [x] service_2/library_dependency_test/dds
- [x] service_2/library_dependency_test/service
- [x] service_2/mirror_references_test/dds
- [x] service_2/mirror_references_test/service
- [x] service_2/weak_properties_test/dds
- [x] service_2/weak_properties_test/service
- [ ] service_2/get_cpu_profile_timeline_rpc_test/service
- [ ] service_2/next_through_simple_async_test_0
as seen in:
- [ ] [app-kernel-linux-debug-x64/7204](https://ci.chromium.org/p/dart/builders/ci.sandbox/app-kernel-linux-debug-x64/7204)
- [ ] [vm-kernel-precomp-win-release-x64/10491](https://ci.chromium.org/p/dart/builders/ci.sandbox/vm-kernel-precomp-win-release-x64/10491)
- [ ] [vm-kernel-precomp-win-release-x64/10494](https://ci.chromium.org/p/dart/builders/ci.sandbox/vm-kernel-precomp-win-release-x64/10494)
- [ ] [vm-kernel-mac-debug-x64/9603](https://ci.chromium.org/p/dart/builders/ci.sandbox/vm-kernel-mac-debug-x64/9603)
I'm creating this issue to track fixing these failing tests, but I'll approve the failures to unblock the bots for now. | 1.0 | observatory_ui_2 and service_2 tests failing - [165420](https://dart-review.googlesource.com/c/sdk/+/165420) introduced two new *_2 duplicate test sets, which largely passes with the exception of:
- [ ] service_2/dds_log_history_size_simple_test/dds
- [ ] observatory_ui_2/app_test
- [ ] service_2/get_cpu_samples_rpc_test/service
- [x] service_2/get_isolate_after_language_error_test/dds
- [x] service_2/get_isolate_after_language_error_test/service
- [x] service_2/get_version_rpc_test/dds
- [x] service_2/get_version_rpc_test/service
- [x] service_2/library_dependency_test/dds
- [x] service_2/library_dependency_test/service
- [x] service_2/mirror_references_test/dds
- [x] service_2/mirror_references_test/service
- [x] service_2/weak_properties_test/dds
- [x] service_2/weak_properties_test/service
- [ ] service_2/get_cpu_profile_timeline_rpc_test/service
- [ ] service_2/next_through_simple_async_test_0
as seen in:
- [ ] [app-kernel-linux-debug-x64/7204](https://ci.chromium.org/p/dart/builders/ci.sandbox/app-kernel-linux-debug-x64/7204)
- [ ] [vm-kernel-precomp-win-release-x64/10491](https://ci.chromium.org/p/dart/builders/ci.sandbox/vm-kernel-precomp-win-release-x64/10491)
- [ ] [vm-kernel-precomp-win-release-x64/10494](https://ci.chromium.org/p/dart/builders/ci.sandbox/vm-kernel-precomp-win-release-x64/10494)
- [ ] [vm-kernel-mac-debug-x64/9603](https://ci.chromium.org/p/dart/builders/ci.sandbox/vm-kernel-mac-debug-x64/9603)
I'm creating this issue to track fixing these failing tests, but I'll approve the failures to unblock the bots for now. | non_priority | observatory ui and service tests failing introduced two new duplicate test sets which largely passes with the exception of service dds log history size simple test dds observatory ui app test service get cpu samples rpc test service service get isolate after language error test dds service get isolate after language error test service service get version rpc test dds service get version rpc test service service library dependency test dds service library dependency test service service mirror references test dds service mirror references test service service weak properties test dds service weak properties test service service get cpu profile timeline rpc test service service next through simple async test as seen in i m creating this issue to track fixing these failing tests but i ll approve the failures to unblock the bots for now | 0 |
485,671 | 13,997,010,213 | IssuesEvent | 2020-10-28 07:07:49 | wso2/product-is | https://api.github.com/repos/wso2/product-is | opened | [consoleApp] Single Page Application Registration needs to have a proper validation for redirect url to deny incorrect urls | Priority/Normal Severity/Major bug console | **Describe the issue:**
As redirect url of a single page application is a mandatory field if a user just input the url and does not adhere to the correct url format still application registration gets succesful.
**How to reproduce:**
1.Access https://localhost:9443/console
2.Login as super admin
3.Navigate to Develop > Applications > New Application > Single Page Application
4.In the edit view
5. Input a application name
6. Input a Redirect URL which is not upto correct format (http:test)
7. Click on Register
**Observation**
Application registration gets succesful
**Expected Behaviour**
Requested url should need to have a proper validation
**Environment information**
Mssql 2019
uniqueid jdbc primary US
IS 5.11.0 beta3
ubuntu 16.04
Chrome Version 85.0.4183.121
| 1.0 | [consoleApp] Single Page Application Registration needs to have a proper validation for redirect url to deny incorrect urls - **Describe the issue:**
As redirect url of a single page application is a mandatory field if a user just input the url and does not adhere to the correct url format still application registration gets succesful.
**How to reproduce:**
1.Access https://localhost:9443/console
2.Login as super admin
3.Navigate to Develop > Applications > New Application > Single Page Application
4.In the edit view
5. Input a application name
6. Input a Redirect URL which is not upto correct format (http:test)
7. Click on Register
**Observation**
Application registration gets succesful
**Expected Behaviour**
Requested url should need to have a proper validation
**Environment information**
Mssql 2019
uniqueid jdbc primary US
IS 5.11.0 beta3
ubuntu 16.04
Chrome Version 85.0.4183.121
| priority | single page application registration needs to have a proper validation for redirect url to deny incorrect urls describe the issue as redirect url of a single page application is a mandatory field if a user just input the url and does not adhere to the correct url format still application registration gets succesful how to reproduce access login as super admin navigate to develop applications new application single page application in the edit view input a application name input a redirect url which is not upto correct format http test click on register observation application registration gets succesful expected behaviour requested url should need to have a proper validation environment information mssql uniqueid jdbc primary us is ubuntu chrome version | 1 |
280,233 | 21,214,404,107 | IssuesEvent | 2022-04-11 05:19:56 | AY2122S2-CS2103T-T11-2/tp | https://api.github.com/repos/AY2122S2-CS2103T-T11-2/tp | closed | [PE-D] Able to have appointment at same time with buyers/sellers | documentation | You are able to set the appointments on the same date and time with multiple buyers and sellers which in my opinion should not be possible. It may be possible that you have a single appointment session for multiple buyers (e.g. viewings) but I don't think overlapping appointments should be allowed between sellers and buyers, and also between 2 sellers.
<!--session: 1648793009662-eae6d417-6d46-43c2-bc45-e3ed9e306d16-->
<!--Version: Web v3.4.2-->
-------------
Labels: `type.FeatureFlaw` `severity.Medium`
original: Ryan-L98/ped#2 | 1.0 | [PE-D] Able to have appointment at same time with buyers/sellers - You are able to set the appointments on the same date and time with multiple buyers and sellers which in my opinion should not be possible. It may be possible that you have a single appointment session for multiple buyers (e.g. viewings) but I don't think overlapping appointments should be allowed between sellers and buyers, and also between 2 sellers.
<!--session: 1648793009662-eae6d417-6d46-43c2-bc45-e3ed9e306d16-->
<!--Version: Web v3.4.2-->
-------------
Labels: `type.FeatureFlaw` `severity.Medium`
original: Ryan-L98/ped#2 | non_priority | able to have appointment at same time with buyers sellers you are able to set the appointments on the same date and time with multiple buyers and sellers which in my opinion should not be possible it may be possible that you have a single appointment session for multiple buyers e g viewings but i don t think overlapping appointments should be allowed between sellers and buyers and also between sellers labels type featureflaw severity medium original ryan ped | 0 |
123,253 | 4,859,334,844 | IssuesEvent | 2016-11-13 16:08:29 | concrete5/concrete5 | https://api.github.com/repos/concrete5/concrete5 | closed | /dashboard/system/seo/searchindex formatting | accepted:ready to start priority:love to have type:ux | Change bold to bluecaps
tweak the dropdown text:
Blacklist - skip the selected areas below when searching content.
Whitelist - only use the selected areas below when searching content.
| 1.0 | /dashboard/system/seo/searchindex formatting - Change bold to bluecaps
tweak the dropdown text:
Blacklist - skip the selected areas below when searching content.
Whitelist - only use the selected areas below when searching content.
| priority | dashboard system seo searchindex formatting change bold to bluecaps tweak the dropdown text blacklist skip the selected areas below when searching content whitelist only use the selected areas below when searching content | 1 |
236,393 | 18,095,644,916 | IssuesEvent | 2021-09-22 08:43:35 | usnistgov/REFPROP-issues | https://api.github.com/repos/usnistgov/REFPROP-issues | closed | GUI Tips: Adding points from a graph into a table to calculate other properties. | documentation GUI | A bug report came in about a region in the two phase where calculations with h and s as inputs failed due to problems in the iterative scheme in the code. As I fixed the problem, instead of writing test code to check the full surface for other failures, I used an option in the GUI to simply click on the graph and have it calculate other properties for that state. I'll share here some of the ideas from the process since they might be useful to others.
Once you make a plot, in my case for entropy vs. enthalpy, bring up a Specified State Points table, making sure it contains the properties you have selected in the plot for the x and y axes. You can then right click on the graph and it will transfer the coordinates into the cells in the table. Since the table only needs two entries to calculate everything else, the h and s transfer that I made by right clicking automatically triggered the calculation.
Below is the window I used to test things for water. After I made the plot, I then calculated an isotherm with density as my variable in order to pass through the two phase region. I then overlaid those calculations on the plot. The values are shown as the red line. I then right clicked in the region between this line and the saturation lines. The table on the left shows the random states for each right click, and three points I found that failed. I then used those to fix the Fortran code to improve the iteration scheme for two-phase h,s inputs. Once done, I restarted the GUI, made the identical plot, brought up a table, and then started right clicking again. This time all worked and I did not find any state that failed.
If you are playing with something similar in order to plot a thermodynamic cycle or whatever, once you have placed your points in the graph by right-clicking, double click on the plot with the left mouse button to bring up the Modify Plot menu. There you can select the option to add a line that connects all the points. Any further right-clicking will result in a new set in the Modify Plot screen so that you can connect them with a different line or change the symbols or colors.
| 1.0 | GUI Tips: Adding points from a graph into a table to calculate other properties. - A bug report came in about a region in the two phase where calculations with h and s as inputs failed due to problems in the iterative scheme in the code. As I fixed the problem, instead of writing test code to check the full surface for other failures, I used an option in the GUI to simply click on the graph and have it calculate other properties for that state. I'll share here some of the ideas from the process since they might be useful to others.
Once you make a plot, in my case for entropy vs. enthalpy, bring up a Specified State Points table, making sure it contains the properties you have selected in the plot for the x and y axes. You can then right click on the graph and it will transfer the coordinates into the cells in the table. Since the table only needs two entries to calculate everything else, the h and s transfer that I made by right clicking automatically triggered the calculation.
Below is the window I used to test things for water. After I made the plot, I then calculated an isotherm with density as my variable in order to pass through the two phase region. I then overlaid those calculations on the plot. The values are shown as the red line. I then right clicked in the region between this line and the saturation lines. The table on the left shows the random states for each right click, and three points I found that failed. I then used those to fix the Fortran code to improve the iteration scheme for two-phase h,s inputs. Once done, I restarted the GUI, made the identical plot, brought up a table, and then started right clicking again. This time all worked and I did not find any state that failed.
If you are playing with something similar in order to plot a thermodynamic cycle or whatever, once you have placed your points in the graph by right-clicking, double click on the plot with the left mouse button to bring up the Modify Plot menu. There you can select the option to add a line that connects all the points. Any further right-clicking will result in a new set in the Modify Plot screen so that you can connect them with a different line or change the symbols or colors.
| non_priority | gui tips adding points from a graph into a table to calculate other properties a bug report came in about a region in the two phase where calculations with h and s as inputs failed due to problems in the iterative scheme in the code as i fixed the problem instead of writing test code to check the full surface for other failures i used an option in the gui to simply click on the graph and have it calculate other properties for that state i ll share here some of the ideas from the process since they might be useful to others once you make a plot in my case for entropy vs enthalpy bring up a specified state points table making sure it contains the properties you have selected in the plot for the x and y axes you can then right click on the graph and it will transfer the coordinates into the cells in the table since the table only needs two entries to calculate everything else the h and s transfer that i made by right clicking automatically triggered the calculation below is the window i used to test things for water after i made the plot i then calculated an isotherm with density as my variable in order to pass through the two phase region i then overlaid those calculations on the plot the values are shown as the red line i then right clicked in the region between this line and the saturation lines the table on the left shows the random states for each right click and three points i found that failed i then used those to fix the fortran code to improve the iteration scheme for two phase h s inputs once done i restarted the gui made the identical plot brought up a table and then started right clicking again this time all worked and i did not find any state that failed if you are playing with something similar in order to plot a thermodynamic cycle or whatever once you have placed your points in the graph by right clicking double click on the plot with the left mouse button to bring up the modify plot menu there you can select the option to add a line that connects all the points any further right clicking will result in a new set in the modify plot screen so that you can connect them with a different line or change the symbols or colors | 0 |
461,519 | 13,231,592,424 | IssuesEvent | 2020-08-18 11:57:38 | mozilla/addons-server | https://api.github.com/repos/mozilla/addons-server | closed | Multiple Homepage shelves can occupy the same shelf Position at the same time | component: admin tools priority: p4 | Follow up for #14874
### Describe the problem and steps to reproduce it:
1. Open the [Homepage shelves](https://addons-internal.dev.mozaws.net/en-US/admin/models/discovery/homepageshelves/add/) admin tool with an admin account
2. Select one of the available shelves from the list and set a Position
3. Save this homepage shelf and add another one, selecting the same Position as for the previous shelf
4. Save the second homepage shelf
### What happened?
The second shelf is successfully saved
### What did you expect to happen?
The form should not allow for the enabling of multiple homepage shelves with the same Position
example of multiple [homepage shelves](https://addons-internal.dev.mozaws.net/en-US/admin/models/discovery/homepageshelves/), all with Position 1
| 1.0 | Multiple Homepage shelves can occupy the same shelf Position at the same time - Follow up for #14874
### Describe the problem and steps to reproduce it:
1. Open the [Homepage shelves](https://addons-internal.dev.mozaws.net/en-US/admin/models/discovery/homepageshelves/add/) admin tool with an admin account
2. Select one of the available shelves from the list and set a Position
3. Save this homepage shelf and add another one, selecting the same Position as for the previous shelf
4. Save the second homepage shelf
### What happened?
The second shelf is successfully saved
### What did you expect to happen?
The form should not allow for the enabling of multiple homepage shelves with the same Position
example of multiple [homepage shelves](https://addons-internal.dev.mozaws.net/en-US/admin/models/discovery/homepageshelves/), all with Position 1
| priority | multiple homepage shelves can occupy the same shelf position at the same time follow up for describe the problem and steps to reproduce it open the admin tool with an admin account select one of the available shelves from the list and set a position save this homepage shelf and add another one selecting the same position as for the previous shelf save the second homepage shelf what happened the second shelf is successfully saved what did you expect to happen the form should not allow for the enabling of multiple homepage shelves with the same position example of multiple all with position | 1 |
133,926 | 10,867,170,422 | IssuesEvent | 2019-11-14 23:06:00 | mozilla-mobile/android-components | https://api.github.com/repos/mozilla-mobile/android-components | closed | Intermittent test failure in DownloadsFeatureTest - onPermissionsResult | <download> E1 intermittent-test ✅ testing | Saw this in TC runs for https://github.com/mozilla-mobile/android-components/pull/4937.
Failing test was last touched in #4282. cc @pocmo
```
[task 2019-11-02T00:26:32.347Z] TEST: onPermissionsResult will consume download if permissions were not granted
[task 2019-11-02T00:26:32.347Z] [Robolectric] mozilla.components.feature.downloads.DownloadsFeatureTest.onPermissionsResult will consume download if permissions were not granted: sdk=28; resources=binary
[task 2019-11-02T00:26:32.426Z] I/MonitoringInstr: Instrumentation started!
[task 2019-11-02T00:26:32.426Z] I/MonitoringInstr: Setting context classloader to 'org.robolectric.internal.bytecode.SandboxClassLoader@ba107ab', Original: 'org.robolectric.internal.bytecode.SandboxClassLoader@ba107ab'
[task 2019-11-02T00:26:32.426Z] TabSessionState(id=test-tab, content=ContentState(url=https://www.mozilla.org, private=false, title=, progress=0, loading=false, searchTerms=, securityInfo=SecurityInfoState(secure=false, host=, issuer=), thumbnail=null, icon=null, download=null, hitResult=null, promptRequest=null, findResults=[], windowRequest=null), trackingProtection=TrackingProtectionState(enabled=false, blockedTrackers=[], loadedTrackers=[], ignoredOnTrackingProtection=false), engineState=EngineState(engineSession=null, engineSessionState=null), parentId=null, extensionState={})
[task 2019-11-02T00:26:32.426Z] FAILURE
[task 2019-11-02T00:26:32.426Z]
[task 2019-11-02T00:26:32.426Z] java.lang.AssertionError
[task 2019-11-02T00:26:32.426Z] at org.junit.Assert.fail(Assert.java:86)
[task 2019-11-02T00:26:32.426Z] at org.junit.Assert.assertTrue(Assert.java:41)
[task 2019-11-02T00:26:32.426Z] at org.junit.Assert.assertNotNull(Assert.java:712)
[task 2019-11-02T00:26:32.426Z] at org.junit.Assert.assertNotNull(Assert.java:722)
[task 2019-11-02T00:26:32.426Z] at mozilla.components.feature.downloads.DownloadsFeatureTest.onPermissionsResult will consume download if permissions were not granted(DownloadsFeatureTest.kt:286)
[task 2019-11-02T00:26:32.426Z] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[task 2019-11-02T00:26:32.426Z] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[task 2019-11-02T00:26:32.426Z] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[task 2019-11-02T00:26:32.426Z] at java.lang.reflect.Method.invoke(Method.java:498)
[task 2019-11-02T00:26:32.426Z] at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
[task 2019-11-02T00:26:32.426Z] at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
[task 2019-11-02T00:26:32.426Z] at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
[task 2019-11-02T00:26:32.426Z] at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
[task 2019-11-02T00:26:32.426Z] at org.robolectric.RobolectricTestRunner$HelperTestRunner$1.evaluate(RobolectricTestRunner.java:601)
[task 2019-11-02T00:26:32.426Z] at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
[task 2019-11-02T00:26:32.426Z] at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
[task 2019-11-02T00:26:32.426Z] at org.robolectric.internal.SandboxTestRunner$2.evaluate(SandboxTestRunner.java:260)
[task 2019-11-02T00:26:32.426Z] at org.robolectric.internal.SandboxTestRunner.runChild(SandboxTestRunner.java:130)
[task 2019-11-02T00:26:32.426Z] at org.robolectric.internal.SandboxTestRunner.runChild(SandboxTestRunner.java:42)
[task 2019-11-02T00:26:32.426Z] at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
[task 2019-11-02T00:26:32.426Z] at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
[task 2019-11-02T00:26:32.426Z] at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
[task 2019-11-02T00:26:32.427Z] at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
[task 2019-11-02T00:26:32.427Z] at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
[task 2019-11-02T00:26:32.427Z] at org.robolectric.internal.SandboxTestRunner$1.evaluate(SandboxTestRunner.java:84)
[task 2019-11-02T00:26:32.427Z] at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
[task 2019-11-02T00:26:32.427Z] at androidx.test.ext.junit.runners.AndroidJUnit4.run(AndroidJUnit4.java:104)
[task 2019-11-02T00:26:32.427Z] at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
[task 2019-11-02T00:26:32.427Z] at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
[task 2019-11-02T00:26:32.427Z] at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
[task 2019-11-02T00:26:32.427Z] at org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
[task 2019-11-02T00:26:32.427Z] at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
[task 2019-11-02T00:26:32.427Z] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[task 2019-11-02T00:26:32.427Z] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[task 2019-11-02T00:26:32.427Z] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[task 2019-11-02T00:26:32.427Z] at java.lang.reflect.Method.invoke(Method.java:498)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
[task 2019-11-02T00:26:32.427Z] at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
[task 2019-11-02T00:26:32.427Z] at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:118)
[task 2019-11-02T00:26:32.427Z] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[task 2019-11-02T00:26:32.427Z] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[task 2019-11-02T00:26:32.427Z] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[task 2019-11-02T00:26:32.427Z] at java.lang.reflect.Method.invoke(Method.java:498)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:175)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:157)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:404)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
[task 2019-11-02T00:26:32.427Z] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[task 2019-11-02T00:26:32.427Z] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
[task 2019-11-02T00:26:32.427Z] at java.lang.Thread.run(Thread.java:748)
``` | 2.0 | Intermittent test failure in DownloadsFeatureTest - onPermissionsResult - Saw this in TC runs for https://github.com/mozilla-mobile/android-components/pull/4937.
Failing test was last touched in #4282. cc @pocmo
```
[task 2019-11-02T00:26:32.347Z] TEST: onPermissionsResult will consume download if permissions were not granted
[task 2019-11-02T00:26:32.347Z] [Robolectric] mozilla.components.feature.downloads.DownloadsFeatureTest.onPermissionsResult will consume download if permissions were not granted: sdk=28; resources=binary
[task 2019-11-02T00:26:32.426Z] I/MonitoringInstr: Instrumentation started!
[task 2019-11-02T00:26:32.426Z] I/MonitoringInstr: Setting context classloader to 'org.robolectric.internal.bytecode.SandboxClassLoader@ba107ab', Original: 'org.robolectric.internal.bytecode.SandboxClassLoader@ba107ab'
[task 2019-11-02T00:26:32.426Z] TabSessionState(id=test-tab, content=ContentState(url=https://www.mozilla.org, private=false, title=, progress=0, loading=false, searchTerms=, securityInfo=SecurityInfoState(secure=false, host=, issuer=), thumbnail=null, icon=null, download=null, hitResult=null, promptRequest=null, findResults=[], windowRequest=null), trackingProtection=TrackingProtectionState(enabled=false, blockedTrackers=[], loadedTrackers=[], ignoredOnTrackingProtection=false), engineState=EngineState(engineSession=null, engineSessionState=null), parentId=null, extensionState={})
[task 2019-11-02T00:26:32.426Z] FAILURE
[task 2019-11-02T00:26:32.426Z]
[task 2019-11-02T00:26:32.426Z] java.lang.AssertionError
[task 2019-11-02T00:26:32.426Z] at org.junit.Assert.fail(Assert.java:86)
[task 2019-11-02T00:26:32.426Z] at org.junit.Assert.assertTrue(Assert.java:41)
[task 2019-11-02T00:26:32.426Z] at org.junit.Assert.assertNotNull(Assert.java:712)
[task 2019-11-02T00:26:32.426Z] at org.junit.Assert.assertNotNull(Assert.java:722)
[task 2019-11-02T00:26:32.426Z] at mozilla.components.feature.downloads.DownloadsFeatureTest.onPermissionsResult will consume download if permissions were not granted(DownloadsFeatureTest.kt:286)
[task 2019-11-02T00:26:32.426Z] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[task 2019-11-02T00:26:32.426Z] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[task 2019-11-02T00:26:32.426Z] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[task 2019-11-02T00:26:32.426Z] at java.lang.reflect.Method.invoke(Method.java:498)
[task 2019-11-02T00:26:32.426Z] at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
[task 2019-11-02T00:26:32.426Z] at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
[task 2019-11-02T00:26:32.426Z] at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
[task 2019-11-02T00:26:32.426Z] at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
[task 2019-11-02T00:26:32.426Z] at org.robolectric.RobolectricTestRunner$HelperTestRunner$1.evaluate(RobolectricTestRunner.java:601)
[task 2019-11-02T00:26:32.426Z] at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
[task 2019-11-02T00:26:32.426Z] at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
[task 2019-11-02T00:26:32.426Z] at org.robolectric.internal.SandboxTestRunner$2.evaluate(SandboxTestRunner.java:260)
[task 2019-11-02T00:26:32.426Z] at org.robolectric.internal.SandboxTestRunner.runChild(SandboxTestRunner.java:130)
[task 2019-11-02T00:26:32.426Z] at org.robolectric.internal.SandboxTestRunner.runChild(SandboxTestRunner.java:42)
[task 2019-11-02T00:26:32.426Z] at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
[task 2019-11-02T00:26:32.426Z] at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
[task 2019-11-02T00:26:32.426Z] at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
[task 2019-11-02T00:26:32.427Z] at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
[task 2019-11-02T00:26:32.427Z] at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
[task 2019-11-02T00:26:32.427Z] at org.robolectric.internal.SandboxTestRunner$1.evaluate(SandboxTestRunner.java:84)
[task 2019-11-02T00:26:32.427Z] at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
[task 2019-11-02T00:26:32.427Z] at androidx.test.ext.junit.runners.AndroidJUnit4.run(AndroidJUnit4.java:104)
[task 2019-11-02T00:26:32.427Z] at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
[task 2019-11-02T00:26:32.427Z] at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
[task 2019-11-02T00:26:32.427Z] at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
[task 2019-11-02T00:26:32.427Z] at org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
[task 2019-11-02T00:26:32.427Z] at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
[task 2019-11-02T00:26:32.427Z] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[task 2019-11-02T00:26:32.427Z] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[task 2019-11-02T00:26:32.427Z] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[task 2019-11-02T00:26:32.427Z] at java.lang.reflect.Method.invoke(Method.java:498)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
[task 2019-11-02T00:26:32.427Z] at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
[task 2019-11-02T00:26:32.427Z] at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:118)
[task 2019-11-02T00:26:32.427Z] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[task 2019-11-02T00:26:32.427Z] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[task 2019-11-02T00:26:32.427Z] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[task 2019-11-02T00:26:32.427Z] at java.lang.reflect.Method.invoke(Method.java:498)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:175)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:157)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:404)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
[task 2019-11-02T00:26:32.427Z] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[task 2019-11-02T00:26:32.427Z] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[task 2019-11-02T00:26:32.427Z] at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
[task 2019-11-02T00:26:32.427Z] at java.lang.Thread.run(Thread.java:748)
``` | non_priority | intermittent test failure in downloadsfeaturetest onpermissionsresult saw this in tc runs for failing test was last touched in cc pocmo test onpermissionsresult will consume download if permissions were not granted mozilla components feature downloads downloadsfeaturetest onpermissionsresult will consume download if permissions were not granted sdk resources binary i monitoringinstr instrumentation started i monitoringinstr setting context classloader to org robolectric internal bytecode sandboxclassloader original org robolectric internal bytecode sandboxclassloader tabsessionstate id test tab content contentstate url private false title progress loading false searchterms securityinfo securityinfostate secure false host issuer thumbnail null icon null download null hitresult null promptrequest null findresults windowrequest null trackingprotection trackingprotectionstate enabled false blockedtrackers loadedtrackers ignoredontrackingprotection false enginestate enginestate enginesession null enginesessionstate null parentid null extensionstate failure java lang assertionerror at org junit assert fail assert java at org junit assert asserttrue assert java at org junit assert assertnotnull assert java at org junit assert assertnotnull assert java at mozilla components feature downloads downloadsfeaturetest onpermissionsresult will consume download if permissions were not granted downloadsfeaturetest kt at sun reflect nativemethodaccessorimpl native method at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org junit runners model frameworkmethod runreflectivecall frameworkmethod java at org junit internal runners model reflectivecallable run reflectivecallable java at org junit runners model frameworkmethod invokeexplosively frameworkmethod java at org junit internal runners statements invokemethod evaluate invokemethod java at org robolectric robolectrictestrunner helpertestrunner evaluate robolectrictestrunner java at org junit internal runners statements runbefores evaluate runbefores java at org junit internal runners statements runafters evaluate runafters java at org robolectric internal sandboxtestrunner evaluate sandboxtestrunner java at org robolectric internal sandboxtestrunner runchild sandboxtestrunner java at org robolectric internal sandboxtestrunner runchild sandboxtestrunner java at org junit runners parentrunner run parentrunner java at org junit runners parentrunner schedule parentrunner java at org junit runners parentrunner runchildren parentrunner java at org junit runners parentrunner access parentrunner java at org junit runners parentrunner evaluate parentrunner java at org robolectric internal sandboxtestrunner evaluate sandboxtestrunner java at org junit runners parentrunner run parentrunner java at androidx test ext junit runners run java at org gradle api internal tasks testing junit junittestclassexecutor runtestclass junittestclassexecutor java at org gradle api internal tasks testing junit junittestclassexecutor execute junittestclassexecutor java at org gradle api internal tasks testing junit junittestclassexecutor execute junittestclassexecutor java at org gradle api internal tasks testing junit abstractjunittestclassprocessor processtestclass abstractjunittestclassprocessor java at org gradle api internal tasks testing suitetestclassprocessor processtestclass suitetestclassprocessor java at sun reflect nativemethodaccessorimpl native method at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org gradle internal dispatch reflectiondispatch dispatch reflectiondispatch java at org gradle internal dispatch reflectiondispatch dispatch reflectiondispatch java at org gradle internal dispatch contextclassloaderdispatch dispatch contextclassloaderdispatch java at org gradle internal dispatch proxydispatchadapter dispatchinginvocationhandler invoke proxydispatchadapter java at com sun proxy processtestclass unknown source at org gradle api internal tasks testing worker testworker processtestclass testworker java at sun reflect nativemethodaccessorimpl native method at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org gradle internal dispatch reflectiondispatch dispatch reflectiondispatch java at org gradle internal dispatch reflectiondispatch dispatch reflectiondispatch java at org gradle internal remote internal hub messagehubbackedobjectconnection dispatchwrapper dispatch messagehubbackedobjectconnection java at org gradle internal remote internal hub messagehubbackedobjectconnection dispatchwrapper dispatch messagehubbackedobjectconnection java at org gradle internal remote internal hub messagehub handler run messagehub java at org gradle internal concurrent executorpolicy catchandrecordfailures onexecute executorpolicy java at org gradle internal concurrent managedexecutorimpl run managedexecutorimpl java at java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java util concurrent threadpoolexecutor worker run threadpoolexecutor java at org gradle internal concurrent threadfactoryimpl managedthreadrunnable run threadfactoryimpl java at java lang thread run thread java | 0 |
16,498 | 2,615,117,394 | IssuesEvent | 2015-03-01 05:42:43 | chrsmith/google-api-java-client | https://api.github.com/repos/chrsmith/google-api-java-client | opened | Google Calendar Data API Android Insert/Edit/Delete Repeating Event | auto-migrated Priority-Low Type-Sample | ```
Which API and version (e.g. Google Calendar Data API version 2)?
Google Calendar Data API 2
What format (e.g. JSON, Atom)?
Atom
What Authentation (e.g. OAuth, OAuth 2, Android, ClientLogin)?
Android
Java environment (e.g. Java 6, Android 2.2, App Engine 1.3.7)?
Android 2.2
External references, such as API reference guide?
Please provide any additional information below.
```
Original issue reported on code.google.com by `andyh...@gmail.com` on 10 Nov 2010 at 12:31 | 1.0 | Google Calendar Data API Android Insert/Edit/Delete Repeating Event - ```
Which API and version (e.g. Google Calendar Data API version 2)?
Google Calendar Data API 2
What format (e.g. JSON, Atom)?
Atom
What Authentation (e.g. OAuth, OAuth 2, Android, ClientLogin)?
Android
Java environment (e.g. Java 6, Android 2.2, App Engine 1.3.7)?
Android 2.2
External references, such as API reference guide?
Please provide any additional information below.
```
Original issue reported on code.google.com by `andyh...@gmail.com` on 10 Nov 2010 at 12:31 | priority | google calendar data api android insert edit delete repeating event which api and version e g google calendar data api version google calendar data api what format e g json atom atom what authentation e g oauth oauth android clientlogin android java environment e g java android app engine android external references such as api reference guide please provide any additional information below original issue reported on code google com by andyh gmail com on nov at | 1 |
289,078 | 24,957,399,027 | IssuesEvent | 2022-11-01 13:01:00 | FTBTeam/FTB-Modpack-Issues | https://api.github.com/repos/FTBTeam/FTB-Modpack-Issues | closed | [Bug]: Entity distance | state: Testing required FTB Inferno | ### Modpack
FTB Inferno
### Modpack version
1.0.3
### Log Files
_No response_
### Describe the bug
Mobs only become visible to me if they are in a 48 (or 47 not realy sure) block radius no matter how high i set the options for entitys visibility
my options for Render Distance and simulation Distance are both at 32
Entity Distance is at 500%
i notice this in FTB inferno i did tests in the latest direwolf20 pack aswell but same issue, in vanilla i had no issue
is that normal and i have to deal with it ?
( I asked the question in the discord, where the assumption was made that there was a problem with an optimization mod but either the problem is with everyone and no one cares or only I have the problem
### Steps to reproduce
1. open a new world
2. set the options for Entitys visibility higher
### Expected behaviour
If i set the option for Entitys high i expect that the game follow the options i set in the option window
### Screenshots
### Additional information
_No response_ | 1.0 | [Bug]: Entity distance - ### Modpack
FTB Inferno
### Modpack version
1.0.3
### Log Files
_No response_
### Describe the bug
Mobs only become visible to me if they are in a 48 (or 47 not realy sure) block radius no matter how high i set the options for entitys visibility
my options for Render Distance and simulation Distance are both at 32
Entity Distance is at 500%
i notice this in FTB inferno i did tests in the latest direwolf20 pack aswell but same issue, in vanilla i had no issue
is that normal and i have to deal with it ?
( I asked the question in the discord, where the assumption was made that there was a problem with an optimization mod but either the problem is with everyone and no one cares or only I have the problem
### Steps to reproduce
1. open a new world
2. set the options for Entitys visibility higher
### Expected behaviour
If i set the option for Entitys high i expect that the game follow the options i set in the option window
### Screenshots
### Additional information
_No response_ | non_priority | entity distance modpack ftb inferno modpack version log files no response describe the bug mobs only become visible to me if they are in a or not realy sure block radius no matter how high i set the options for entitys visibility my options for render distance and simulation distance are both at entity distance is at i notice this in ftb inferno i did tests in the latest pack aswell but same issue in vanilla i had no issue is that normal and i have to deal with it i asked the question in the discord where the assumption was made that there was a problem with an optimization mod but either the problem is with everyone and no one cares or only i have the problem steps to reproduce open a new world set the options for entitys visibility higher expected behaviour if i set the option for entitys high i expect that the game follow the options i set in the option window screenshots additional information no response | 0 |
472,798 | 13,631,524,564 | IssuesEvent | 2020-09-24 18:08:59 | oppia/oppia-android | https://api.github.com/repos/oppia/oppia-android | opened | Throughly test `TexInputStartsWithRuleClassifier` | Priority: Important SLoP 2020 Status: Not started Type: Improvement good first issue | Since the `TexInputStartsWithRuleClassifier` was copied from Oppia web, it didn't have corresponding tests added to verify correctness. These should be ported over from Oppia web as well to ensure that each classifier has working functionality.
Useful reference - https://github.com/oppia/oppia-android/tree/develop/domain/src/test/java/org/oppia/domain/classify | 1.0 | Throughly test `TexInputStartsWithRuleClassifier` - Since the `TexInputStartsWithRuleClassifier` was copied from Oppia web, it didn't have corresponding tests added to verify correctness. These should be ported over from Oppia web as well to ensure that each classifier has working functionality.
Useful reference - https://github.com/oppia/oppia-android/tree/develop/domain/src/test/java/org/oppia/domain/classify | priority | throughly test texinputstartswithruleclassifier since the texinputstartswithruleclassifier was copied from oppia web it didn t have corresponding tests added to verify correctness these should be ported over from oppia web as well to ensure that each classifier has working functionality useful reference | 1 |
709,223 | 24,371,058,149 | IssuesEvent | 2022-10-03 19:19:58 | onulstore/Onulstore-BE | https://api.github.com/repos/onulstore/Onulstore-BE | opened | Feat Order | Priority : High Type: Feature Status : In Progress | ## 설명
Order관련 기능 추가
## 할일
- [ ] 주문 상태 추가
- [ ] 주문 상태 변경
- [ ] 배송 방법 추가
- [ ] 결제 수단 추
| 1.0 | Feat Order - ## 설명
Order관련 기능 추가
## 할일
- [ ] 주문 상태 추가
- [ ] 주문 상태 변경
- [ ] 배송 방법 추가
- [ ] 결제 수단 추
| priority | feat order 설명 order관련 기능 추가 할일 주문 상태 추가 주문 상태 변경 배송 방법 추가 결제 수단 추 | 1 |
771,354 | 27,081,659,771 | IssuesEvent | 2023-02-14 14:25:16 | bigbluebutton/bigbluebutton | https://api.github.com/repos/bigbluebutton/bigbluebutton | closed | [2.4] Race condition in (many) users joining from waiting room | priority: normal module: client | <!--PLEASE DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS.
This issue tracker is only for bbb development related issues.-->
**Describe the bug**
When there are many users waiting in the waiting room (150), many of them can't load the HTML5 client. Failed clients see a blue screen without dots and get a stacktrace similar to this one:
~~~
Exception in queued task TypeError: i[h.meetingID][h.userID] is undefined
T https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:375
El https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
Ys https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
unstable_runWithPriority https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:79
ci https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
Xs https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
Rs https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
hi https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
unstable_runWithPriority https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:79
ci https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
hi https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
di https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
Es https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
La https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
added https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:375
added https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:307
added https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:307
a https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:307
runTask https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:1
flush https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:1
drain https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:1
resumeObservers https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:307
endUpdate https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:331
e https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:321
_performWrites https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:321
_performWrites https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:321
_flushBufferedWrites https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:321
bindEnvironment https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:1
~~~
**To Reproduce**
Steps to reproduce the behavior:
1. Open a meeting, set guest policy to ask moderator
2. Join many bots as viewer
3. Join in a different browser as viewer to later see the error
4. let all guests join.
In my tests all bots are connected in a gigabit network, server has more bandwidth. Having more bots increases the probablility to see the error. I got the following results:
| total bots | failed bots |
| ------------ | --------------|
| 40 | 8 |
| 90 | 30 |
| 140 | 130 |
**Expected behavior**
Everyone should be able to participate
**BBB version:**
BBB 2.4.4 + Patch from PR #14334
**Desktop (please complete the following information):**
- OS: Linux
- Browser Chrome, Firefox
- Version Chrome 99, Firefox 91 ESR
| 1.0 | [2.4] Race condition in (many) users joining from waiting room - <!--PLEASE DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS.
This issue tracker is only for bbb development related issues.-->
**Describe the bug**
When there are many users waiting in the waiting room (150), many of them can't load the HTML5 client. Failed clients see a blue screen without dots and get a stacktrace similar to this one:
~~~
Exception in queued task TypeError: i[h.meetingID][h.userID] is undefined
T https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:375
El https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
Ys https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
unstable_runWithPriority https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:79
ci https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
Xs https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
Rs https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
hi https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
unstable_runWithPriority https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:79
ci https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
hi https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
di https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
Es https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
La https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:61
added https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:375
added https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:307
added https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:307
a https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:307
runTask https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:1
flush https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:1
drain https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:1
resumeObservers https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:307
endUpdate https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:331
e https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:321
_performWrites https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:321
_performWrites https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:321
_flushBufferedWrites https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:321
bindEnvironment https://bbb-server/html5client/d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:1
~~~
**To Reproduce**
Steps to reproduce the behavior:
1. Open a meeting, set guest policy to ask moderator
2. Join many bots as viewer
3. Join in a different browser as viewer to later see the error
4. let all guests join.
In my tests all bots are connected in a gigabit network, server has more bandwidth. Having more bots increases the probablility to see the error. I got the following results:
| total bots | failed bots |
| ------------ | --------------|
| 40 | 8 |
| 90 | 30 |
| 140 | 130 |
**Expected behavior**
Everyone should be able to participate
**BBB version:**
BBB 2.4.4 + Patch from PR #14334
**Desktop (please complete the following information):**
- OS: Linux
- Browser Chrome, Firefox
- Version Chrome 99, Firefox 91 ESR
| priority | race condition in many users joining from waiting room please do not file issues for general support questions this issue tracker is only for bbb development related issues describe the bug when there are many users waiting in the waiting room many of them can t load the client failed clients see a blue screen without dots and get a stacktrace similar to this one exception in queued task typeerror i is undefined t el ys unstable runwithpriority ci xs rs hi unstable runwithpriority ci hi di es la added added added a runtask flush drain resumeobservers endupdate e performwrites performwrites flushbufferedwrites bindenvironment to reproduce steps to reproduce the behavior open a meeting set guest policy to ask moderator join many bots as viewer join in a different browser as viewer to later see the error let all guests join in my tests all bots are connected in a gigabit network server has more bandwidth having more bots increases the probablility to see the error i got the following results total bots failed bots expected behavior everyone should be able to participate bbb version bbb patch from pr desktop please complete the following information os linux browser chrome firefox version chrome firefox esr | 1 |
121,987 | 12,138,575,485 | IssuesEvent | 2020-04-23 17:28:01 | mikemc/metacal | https://api.github.com/repos/mikemc/metacal | opened | Fix formatting for @param field in function docs | documentation | E.g. in `center()`, I must have used dashes which are getting interpreted as markdown bullets | 1.0 | Fix formatting for @param field in function docs - E.g. in `center()`, I must have used dashes which are getting interpreted as markdown bullets | non_priority | fix formatting for param field in function docs e g in center i must have used dashes which are getting interpreted as markdown bullets | 0 |
117,171 | 15,057,958,621 | IssuesEvent | 2021-02-03 22:33:14 | ZcashFoundation/zebra | https://api.github.com/repos/ZcashFoundation/zebra | opened | Verify mempool transactions using a block height | A-consensus A-docs A-rust C-bug P-Medium S-needs-design S-needs-triage | ## Motivation
Currently, Zebra's transaction verifier passes a `NetworkUpgrade` with `Mempool` transaction validation requests.
But multiple Zcash transaction consensus rules depend on the specific block height, not just the network upgrade:
* https://zips.z.cash/zip-0203
* https://raw.githubusercontent.com/zcash/zips/master/protocol/protocol.pdf , "Transaction Encoding and Consensus"
Mempool transactions should be validated based on the **next** block height, after the current tip.
If syncing is still downloading large numbers of blocks, Zebra might want to perform Mempool validation based on the greatest of:
* the current tip + 1
* the maximum checkpoint height + 1
Or simply ignore the mempool entirely.
We still need to create an overall design for the mempool (#936). | 1.0 | Verify mempool transactions using a block height - ## Motivation
Currently, Zebra's transaction verifier passes a `NetworkUpgrade` with `Mempool` transaction validation requests.
But multiple Zcash transaction consensus rules depend on the specific block height, not just the network upgrade:
* https://zips.z.cash/zip-0203
* https://raw.githubusercontent.com/zcash/zips/master/protocol/protocol.pdf , "Transaction Encoding and Consensus"
Mempool transactions should be validated based on the **next** block height, after the current tip.
If syncing is still downloading large numbers of blocks, Zebra might want to perform Mempool validation based on the greatest of:
* the current tip + 1
* the maximum checkpoint height + 1
Or simply ignore the mempool entirely.
We still need to create an overall design for the mempool (#936). | non_priority | verify mempool transactions using a block height motivation currently zebra s transaction verifier passes a networkupgrade with mempool transaction validation requests but multiple zcash transaction consensus rules depend on the specific block height not just the network upgrade transaction encoding and consensus mempool transactions should be validated based on the next block height after the current tip if syncing is still downloading large numbers of blocks zebra might want to perform mempool validation based on the greatest of the current tip the maximum checkpoint height or simply ignore the mempool entirely we still need to create an overall design for the mempool | 0 |
53,980 | 6,358,286,671 | IssuesEvent | 2017-07-31 00:45:32 | QubesOS/updates-status | https://api.github.com/repos/QubesOS/updates-status | closed | manager v4.0.3 (r4.0) | r4.0-dom0-testing | Update of manager to v4.0.3 for Qubes r4.0, see comments below for details.
Built from: https://github.com/QubesOS/qubes-manager/commit/3d32bd8cbc139df8bb31cf6bbedaf2033602f9dd
[Changes since previous version](https://github.com/QubesOS/qubes-manager/compare/v4.0.2...v4.0.3):
QubesOS/qubes-manager@3d32bd8 version 4.0.3
QubesOS/qubes-manager@693e134 'rename VM' button in VM Settings
QubesOS/qubes-manager@2dda433 'refresh available apps' button in VM Setting
Referenced issues:
If you're release manager, you can issue GPG-inline signed command:
* `Upload manager 3d32bd8cbc139df8bb31cf6bbedaf2033602f9dd r4.0 current repo` (available 7 days from now)
* `Upload manager 3d32bd8cbc139df8bb31cf6bbedaf2033602f9dd r4.0 current (dists) repo`, you can choose subset of distributions, like `vm-fc24 vm-fc25` (available 7 days from now)
* `Upload manager 3d32bd8cbc139df8bb31cf6bbedaf2033602f9dd r4.0 security-testing repo`
Above commands will work only if packages in current-testing repository were built from given commit (i.e. no new version superseded it).
| 1.0 | manager v4.0.3 (r4.0) - Update of manager to v4.0.3 for Qubes r4.0, see comments below for details.
Built from: https://github.com/QubesOS/qubes-manager/commit/3d32bd8cbc139df8bb31cf6bbedaf2033602f9dd
[Changes since previous version](https://github.com/QubesOS/qubes-manager/compare/v4.0.2...v4.0.3):
QubesOS/qubes-manager@3d32bd8 version 4.0.3
QubesOS/qubes-manager@693e134 'rename VM' button in VM Settings
QubesOS/qubes-manager@2dda433 'refresh available apps' button in VM Setting
Referenced issues:
If you're release manager, you can issue GPG-inline signed command:
* `Upload manager 3d32bd8cbc139df8bb31cf6bbedaf2033602f9dd r4.0 current repo` (available 7 days from now)
* `Upload manager 3d32bd8cbc139df8bb31cf6bbedaf2033602f9dd r4.0 current (dists) repo`, you can choose subset of distributions, like `vm-fc24 vm-fc25` (available 7 days from now)
* `Upload manager 3d32bd8cbc139df8bb31cf6bbedaf2033602f9dd r4.0 security-testing repo`
Above commands will work only if packages in current-testing repository were built from given commit (i.e. no new version superseded it).
| non_priority | manager update of manager to for qubes see comments below for details built from qubesos qubes manager version qubesos qubes manager rename vm button in vm settings qubesos qubes manager refresh available apps button in vm setting referenced issues if you re release manager you can issue gpg inline signed command upload manager current repo available days from now upload manager current dists repo you can choose subset of distributions like vm vm available days from now upload manager security testing repo above commands will work only if packages in current testing repository were built from given commit i e no new version superseded it | 0 |
314,641 | 9,600,872,692 | IssuesEvent | 2019-05-10 10:30:05 | WoWManiaUK/Blackwing-Lair | https://api.github.com/repos/WoWManiaUK/Blackwing-Lair | closed | Cataclysm Zone Mob XP | Fixed Confirmed Fixed in Dev Priority-High Regression zone 80-85 Cata | Here are the mob XP formulas from wiki
XP = (Char Level * 5) + 45, where Char Level = Mob Level, for mobs in Azeroth
XP = (Char Level * 5) + 235, where Char Level = Mob Level, for mobs in Outland
XP = (Char Level * 5) + 580, where Char Level = Mob Level, for mobs in Northrend
**XP = (Char Level * 5) + 1878, where Char Level = Mob Level, for mobs in Cataclysm**
With that calculation, a level 80 player killing a level 80 mob in a cataclysm zone would receive 2278 exp on x1 rates,, 9,1k with x2 + double xp weekend and 27k+ with x12 VIP.
Currently players experience that with the weekend x4 exp they get about 2-3k, and even the vip guys with x12 only get 7-10k depending on zone and char level.
The cataclysm formula must apply in cata zones, I think currently it uses one of the lesser formulas. | 1.0 | Cataclysm Zone Mob XP - Here are the mob XP formulas from wiki
XP = (Char Level * 5) + 45, where Char Level = Mob Level, for mobs in Azeroth
XP = (Char Level * 5) + 235, where Char Level = Mob Level, for mobs in Outland
XP = (Char Level * 5) + 580, where Char Level = Mob Level, for mobs in Northrend
**XP = (Char Level * 5) + 1878, where Char Level = Mob Level, for mobs in Cataclysm**
With that calculation, a level 80 player killing a level 80 mob in a cataclysm zone would receive 2278 exp on x1 rates,, 9,1k with x2 + double xp weekend and 27k+ with x12 VIP.
Currently players experience that with the weekend x4 exp they get about 2-3k, and even the vip guys with x12 only get 7-10k depending on zone and char level.
The cataclysm formula must apply in cata zones, I think currently it uses one of the lesser formulas. | priority | cataclysm zone mob xp here are the mob xp formulas from wiki xp char level where char level mob level for mobs in azeroth xp char level where char level mob level for mobs in outland xp char level where char level mob level for mobs in northrend xp char level where char level mob level for mobs in cataclysm with that calculation a level player killing a level mob in a cataclysm zone would receive exp on rates with double xp weekend and with vip currently players experience that with the weekend exp they get about and even the vip guys with only get depending on zone and char level the cataclysm formula must apply in cata zones i think currently it uses one of the lesser formulas | 1 |
21,019 | 4,656,486,979 | IssuesEvent | 2016-10-04 05:49:45 | zfsonlinux/zfs | https://api.github.com/repos/zfsonlinux/zfs | closed | Documentation, how to build with --enable-debug | Documentation | I had to resort to asking in IRC to get instructions on how to build SPL and ZFS with `--enable-debug`. This should be documented somewhere. | 1.0 | Documentation, how to build with --enable-debug - I had to resort to asking in IRC to get instructions on how to build SPL and ZFS with `--enable-debug`. This should be documented somewhere. | non_priority | documentation how to build with enable debug i had to resort to asking in irc to get instructions on how to build spl and zfs with enable debug this should be documented somewhere | 0 |
52,961 | 6,667,201,816 | IssuesEvent | 2017-10-03 11:34:47 | blockstack/designs | https://api.github.com/repos/blockstack/designs | closed | Design new placeholder image for blockstack.org home page video | design production | Design new placeholder image for blockstack.org home page video | 1.0 | Design new placeholder image for blockstack.org home page video - Design new placeholder image for blockstack.org home page video | non_priority | design new placeholder image for blockstack org home page video design new placeholder image for blockstack org home page video | 0 |
269,349 | 8,435,013,623 | IssuesEvent | 2018-10-17 11:59:35 | giftdibs/giftdibs-browser | https://api.github.com/repos/giftdibs/giftdibs-browser | closed | Wish List Detail > Create a "received" tab | priority: high | Maybe allowing people to archive their list will accomplish the same thing? | 1.0 | Wish List Detail > Create a "received" tab - Maybe allowing people to archive their list will accomplish the same thing? | priority | wish list detail create a received tab maybe allowing people to archive their list will accomplish the same thing | 1 |
146,165 | 11,728,290,224 | IssuesEvent | 2020-03-10 17:18:00 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | ccl/changefeedccl: TestChangefeedDiff failed | C-test-failure O-robot branch-master | [(ccl/changefeedccl).TestChangefeedDiff failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=1800347&tab=buildLog) on [master@1d2541c9b536a5023a3785f8d1facd77c96303e7](https://github.com/cockroachdb/cockroach/commits/1d2541c9b536a5023a3785f8d1facd77c96303e7):
```
github.com/cockroachdb/cockroach/pkg/rpc.NewServerWithInterceptor.func2()
/go/src/github.com/cockroachdb/cockroach/pkg/rpc/context.go:223 +0x10e
github.com/cockroachdb/cockroach/pkg/rpc.NewServerWithInterceptor.func4()
/go/src/github.com/cockroachdb/cockroach/pkg/rpc/context.go:253 +0xe9
github.com/cockroachdb/cockroach/pkg/server/serverpb._Status_ListLocalSessions_Handler()
/go/src/github.com/cockroachdb/cockroach/pkg/server/serverpb/status.pb.go:4094 +0x1d8
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).processUnaryRPC()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:999 +0x994
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).handleStream()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:1279 +0x1343
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).serveStreams.func1.1()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:717 +0xc8
Goroutine 318 (running) created at:
github.com/cockroachdb/cockroach/pkg/sql.(*InternalExecutor).initConnEx()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/internal.go:157 +0x5c9
github.com/cockroachdb/cockroach/pkg/sql.(*InternalExecutor).execInternal()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/internal.go:427 +0x950
github.com/cockroachdb/cockroach/pkg/sql.(*InternalExecutor).ExecEx()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/internal.go:295 +0x14f
github.com/cockroachdb/cockroach/pkg/sqlmigrations.populateVersionSetting()
/go/src/github.com/cockroachdb/cockroach/pkg/sqlmigrations/migrations.go:392 +0x3bf
github.com/cockroachdb/cockroach/pkg/sqlmigrations.(*Manager).EnsureMigrations()
/go/src/github.com/cockroachdb/cockroach/pkg/sqlmigrations/migrations.go:634 +0xc3c
github.com/cockroachdb/cockroach/pkg/server.(*Server).Start()
/go/src/github.com/cockroachdb/cockroach/pkg/server/server.go:1758 +0x4c69
github.com/cockroachdb/cockroach/pkg/server.(*TestServer).Start()
/go/src/github.com/cockroachdb/cockroach/pkg/server/testserver.go:384 +0x2e8
github.com/cockroachdb/cockroach/pkg/testutils/serverutils.StartServerRaw()
/go/src/github.com/cockroachdb/cockroach/pkg/testutils/serverutils/test_server_shim.go:228 +0x15f
github.com/cockroachdb/cockroach/pkg/testutils/serverutils.StartServer()
/go/src/github.com/cockroachdb/cockroach/pkg/testutils/serverutils/test_server_shim.go:196 +0x65
github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl.cloudStorageTest.func1()
/go/src/github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl/helpers_test.go:303 +0x3f6
testing.tRunner()
/usr/local/go/src/testing/testing.go:909 +0x199
Goroutine 316 (finished) created at:
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).serveStreams.func1()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:715 +0xb8
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/internal/transport.(*http2Server).operateHeaders()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/internal/transport/http2_server.go:421 +0x1596
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/internal/transport.(*http2Server).HandleStreams()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/internal/transport/http2_server.go:461 +0x39f
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).serveStreams()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:713 +0x19a
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).handleRawConn.func1()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:675 +0x50
==================
FAIL github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl 17.897s
```
<details><summary>More</summary><p>
Parameters:
- GOFLAGS=-json
```
make stressrace TESTS=TestChangefeedDiff PKG=./pkg/ccl/changefeedccl TESTTIMEOUT=5m STRESSFLAGS='-timeout 5m' 2>&1
```
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2ATestChangefeedDiff.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
| 1.0 | ccl/changefeedccl: TestChangefeedDiff failed - [(ccl/changefeedccl).TestChangefeedDiff failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=1800347&tab=buildLog) on [master@1d2541c9b536a5023a3785f8d1facd77c96303e7](https://github.com/cockroachdb/cockroach/commits/1d2541c9b536a5023a3785f8d1facd77c96303e7):
```
github.com/cockroachdb/cockroach/pkg/rpc.NewServerWithInterceptor.func2()
/go/src/github.com/cockroachdb/cockroach/pkg/rpc/context.go:223 +0x10e
github.com/cockroachdb/cockroach/pkg/rpc.NewServerWithInterceptor.func4()
/go/src/github.com/cockroachdb/cockroach/pkg/rpc/context.go:253 +0xe9
github.com/cockroachdb/cockroach/pkg/server/serverpb._Status_ListLocalSessions_Handler()
/go/src/github.com/cockroachdb/cockroach/pkg/server/serverpb/status.pb.go:4094 +0x1d8
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).processUnaryRPC()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:999 +0x994
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).handleStream()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:1279 +0x1343
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).serveStreams.func1.1()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:717 +0xc8
Goroutine 318 (running) created at:
github.com/cockroachdb/cockroach/pkg/sql.(*InternalExecutor).initConnEx()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/internal.go:157 +0x5c9
github.com/cockroachdb/cockroach/pkg/sql.(*InternalExecutor).execInternal()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/internal.go:427 +0x950
github.com/cockroachdb/cockroach/pkg/sql.(*InternalExecutor).ExecEx()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/internal.go:295 +0x14f
github.com/cockroachdb/cockroach/pkg/sqlmigrations.populateVersionSetting()
/go/src/github.com/cockroachdb/cockroach/pkg/sqlmigrations/migrations.go:392 +0x3bf
github.com/cockroachdb/cockroach/pkg/sqlmigrations.(*Manager).EnsureMigrations()
/go/src/github.com/cockroachdb/cockroach/pkg/sqlmigrations/migrations.go:634 +0xc3c
github.com/cockroachdb/cockroach/pkg/server.(*Server).Start()
/go/src/github.com/cockroachdb/cockroach/pkg/server/server.go:1758 +0x4c69
github.com/cockroachdb/cockroach/pkg/server.(*TestServer).Start()
/go/src/github.com/cockroachdb/cockroach/pkg/server/testserver.go:384 +0x2e8
github.com/cockroachdb/cockroach/pkg/testutils/serverutils.StartServerRaw()
/go/src/github.com/cockroachdb/cockroach/pkg/testutils/serverutils/test_server_shim.go:228 +0x15f
github.com/cockroachdb/cockroach/pkg/testutils/serverutils.StartServer()
/go/src/github.com/cockroachdb/cockroach/pkg/testutils/serverutils/test_server_shim.go:196 +0x65
github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl.cloudStorageTest.func1()
/go/src/github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl/helpers_test.go:303 +0x3f6
testing.tRunner()
/usr/local/go/src/testing/testing.go:909 +0x199
Goroutine 316 (finished) created at:
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).serveStreams.func1()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:715 +0xb8
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/internal/transport.(*http2Server).operateHeaders()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/internal/transport/http2_server.go:421 +0x1596
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/internal/transport.(*http2Server).HandleStreams()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/internal/transport/http2_server.go:461 +0x39f
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).serveStreams()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:713 +0x19a
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).handleRawConn.func1()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:675 +0x50
==================
FAIL github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl 17.897s
```
<details><summary>More</summary><p>
Parameters:
- GOFLAGS=-json
```
make stressrace TESTS=TestChangefeedDiff PKG=./pkg/ccl/changefeedccl TESTTIMEOUT=5m STRESSFLAGS='-timeout 5m' 2>&1
```
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2ATestChangefeedDiff.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
| non_priority | ccl changefeedccl testchangefeeddiff failed on github com cockroachdb cockroach pkg rpc newserverwithinterceptor go src github com cockroachdb cockroach pkg rpc context go github com cockroachdb cockroach pkg rpc newserverwithinterceptor go src github com cockroachdb cockroach pkg rpc context go github com cockroachdb cockroach pkg server serverpb status listlocalsessions handler go src github com cockroachdb cockroach pkg server serverpb status pb go github com cockroachdb cockroach vendor google golang org grpc server processunaryrpc go src github com cockroachdb cockroach vendor google golang org grpc server go github com cockroachdb cockroach vendor google golang org grpc server handlestream go src github com cockroachdb cockroach vendor google golang org grpc server go github com cockroachdb cockroach vendor google golang org grpc server servestreams go src github com cockroachdb cockroach vendor google golang org grpc server go goroutine running created at github com cockroachdb cockroach pkg sql internalexecutor initconnex go src github com cockroachdb cockroach pkg sql internal go github com cockroachdb cockroach pkg sql internalexecutor execinternal go src github com cockroachdb cockroach pkg sql internal go github com cockroachdb cockroach pkg sql internalexecutor execex go src github com cockroachdb cockroach pkg sql internal go github com cockroachdb cockroach pkg sqlmigrations populateversionsetting go src github com cockroachdb cockroach pkg sqlmigrations migrations go github com cockroachdb cockroach pkg sqlmigrations manager ensuremigrations go src github com cockroachdb cockroach pkg sqlmigrations migrations go github com cockroachdb cockroach pkg server server start go src github com cockroachdb cockroach pkg server server go github com cockroachdb cockroach pkg server testserver start go src github com cockroachdb cockroach pkg server testserver go github com cockroachdb cockroach pkg testutils serverutils startserverraw go src github com cockroachdb cockroach pkg testutils serverutils test server shim go github com cockroachdb cockroach pkg testutils serverutils startserver go src github com cockroachdb cockroach pkg testutils serverutils test server shim go github com cockroachdb cockroach pkg ccl changefeedccl cloudstoragetest go src github com cockroachdb cockroach pkg ccl changefeedccl helpers test go testing trunner usr local go src testing testing go goroutine finished created at github com cockroachdb cockroach vendor google golang org grpc server servestreams go src github com cockroachdb cockroach vendor google golang org grpc server go github com cockroachdb cockroach vendor google golang org grpc internal transport operateheaders go src github com cockroachdb cockroach vendor google golang org grpc internal transport server go github com cockroachdb cockroach vendor google golang org grpc internal transport handlestreams go src github com cockroachdb cockroach vendor google golang org grpc internal transport server go github com cockroachdb cockroach vendor google golang org grpc server servestreams go src github com cockroachdb cockroach vendor google golang org grpc server go github com cockroachdb cockroach vendor google golang org grpc server handlerawconn go src github com cockroachdb cockroach vendor google golang org grpc server go fail github com cockroachdb cockroach pkg ccl changefeedccl more parameters goflags json make stressrace tests testchangefeeddiff pkg pkg ccl changefeedccl testtimeout stressflags timeout powered by | 0 |
307,948 | 9,424,266,115 | IssuesEvent | 2019-04-11 13:46:45 | deep-compute/gitkanban | https://api.github.com/repos/deep-compute/gitkanban | opened | Bug: Escalation hierarchy bug. | about-halfday-effort bug-type high-impact high-priority inprogress-status | * We observed an issue in the production without escalating to `repo-group/repo-group-label` it directly goes to `system-owner` even though we specified the ownership hierarchy in the config file. | 1.0 | Bug: Escalation hierarchy bug. - * We observed an issue in the production without escalating to `repo-group/repo-group-label` it directly goes to `system-owner` even though we specified the ownership hierarchy in the config file. | priority | bug escalation hierarchy bug we observed an issue in the production without escalating to repo group repo group label it directly goes to system owner even though we specified the ownership hierarchy in the config file | 1 |
218,434 | 7,331,328,303 | IssuesEvent | 2018-03-05 13:09:25 | wso2/product-is | https://api.github.com/repos/wso2/product-is | closed | Include a step by step sample on how we can use consent api in documentation | Affected/5.5.0-M4 Priority/High Type/Docs | Include a step by step sample on how we can use consent api in documentation [1]. It does not explain much in the doc.
[1] https://docs.wso2.com/display/IS550/Consent+Management+Using+REST+APIs#ConsentManagementUsingRESTAPIs-Definitionsforconsentmanagement | 1.0 | Include a step by step sample on how we can use consent api in documentation - Include a step by step sample on how we can use consent api in documentation [1]. It does not explain much in the doc.
[1] https://docs.wso2.com/display/IS550/Consent+Management+Using+REST+APIs#ConsentManagementUsingRESTAPIs-Definitionsforconsentmanagement | priority | include a step by step sample on how we can use consent api in documentation include a step by step sample on how we can use consent api in documentation it does not explain much in the doc | 1 |
712,658 | 24,502,783,293 | IssuesEvent | 2022-10-10 14:02:35 | AY2223S1-CS2103T-W10-2/tp | https://api.github.com/repos/AY2223S1-CS2103T-W10-2/tp | closed | As a FA, I want to view all my contacts and the details of my contacts, | priority.High type.Story | so that I can get an overview of all of my contacts at once. | 1.0 | As a FA, I want to view all my contacts and the details of my contacts, - so that I can get an overview of all of my contacts at once. | priority | as a fa i want to view all my contacts and the details of my contacts so that i can get an overview of all of my contacts at once | 1 |
181,958 | 21,664,470,510 | IssuesEvent | 2022-05-07 01:27:30 | haeli05/source | https://api.github.com/repos/haeli05/source | closed | WS-2019-0291 (High) detected in handlebars-4.2.0.tgz - autoclosed | security vulnerability | ## WS-2019-0291 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.2.0.tgz</b></p></summary>
<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-4.2.0.tgz">https://registry.npmjs.org/handlebars/-/handlebars-4.2.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/source/FrontEnd/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/source/FrontEnd/node_modules/handlebars/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.1.1.tgz (Root Library)
- jest-24.8.0.tgz
- jest-cli-24.9.0.tgz
- core-24.9.0.tgz
- reporters-24.9.0.tgz
- istanbul-reports-2.2.6.tgz
- :x: **handlebars-4.2.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/haeli05/source/commit/cd3dfb369e611687baef858fdd1cf268baed1b52">cd3dfb369e611687baef858fdd1cf268baed1b52</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
handlebars before 4.3.0 is vulnerable to Prototype Pollution leading to Remote Code Execution. Templates may alter an Objects' __proto__ and __defineGetter__ properties, which may allow an attacker to execute arbitrary code through crafted payloads.
<p>Publish Date: 2019-10-06
<p>URL: <a href=https://github.com/wycats/handlebars.js/issues/1558>WS-2019-0291</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>7.3</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1164">https://www.npmjs.com/advisories/1164</a></p>
<p>Release Date: 2019-10-06</p>
<p>Fix Resolution: 4.3.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2019-0291 (High) detected in handlebars-4.2.0.tgz - autoclosed - ## WS-2019-0291 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.2.0.tgz</b></p></summary>
<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-4.2.0.tgz">https://registry.npmjs.org/handlebars/-/handlebars-4.2.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/source/FrontEnd/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/source/FrontEnd/node_modules/handlebars/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.1.1.tgz (Root Library)
- jest-24.8.0.tgz
- jest-cli-24.9.0.tgz
- core-24.9.0.tgz
- reporters-24.9.0.tgz
- istanbul-reports-2.2.6.tgz
- :x: **handlebars-4.2.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/haeli05/source/commit/cd3dfb369e611687baef858fdd1cf268baed1b52">cd3dfb369e611687baef858fdd1cf268baed1b52</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
handlebars before 4.3.0 is vulnerable to Prototype Pollution leading to Remote Code Execution. Templates may alter an Objects' __proto__ and __defineGetter__ properties, which may allow an attacker to execute arbitrary code through crafted payloads.
<p>Publish Date: 2019-10-06
<p>URL: <a href=https://github.com/wycats/handlebars.js/issues/1558>WS-2019-0291</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>7.3</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1164">https://www.npmjs.com/advisories/1164</a></p>
<p>Release Date: 2019-10-06</p>
<p>Fix Resolution: 4.3.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | ws high detected in handlebars tgz autoclosed ws high severity vulnerability vulnerable library handlebars tgz handlebars provides the power necessary to let you build semantic templates effectively with no frustration library home page a href path to dependency file tmp ws scm source frontend package json path to vulnerable library tmp ws scm source frontend node modules handlebars package json dependency hierarchy react scripts tgz root library jest tgz jest cli tgz core tgz reporters tgz istanbul reports tgz x handlebars tgz vulnerable library found in head commit a href vulnerability details handlebars before is vulnerable to prototype pollution leading to remote code execution templates may alter an objects proto and definegetter properties which may allow an attacker to execute arbitrary code through crafted payloads publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
16,581 | 4,065,176,707 | IssuesEvent | 2016-05-26 10:06:12 | Kinto/kinto-client | https://api.github.com/repos/Kinto/kinto-client | closed | Document timeout option | documentation easy-pick | The HTTP class supports a `timeout` option. We should document how to leverage it :) (and maybe its limitation)
See https://github.com/Kinto/kinto.js/issues/280 | 1.0 | Document timeout option - The HTTP class supports a `timeout` option. We should document how to leverage it :) (and maybe its limitation)
See https://github.com/Kinto/kinto.js/issues/280 | non_priority | document timeout option the http class supports a timeout option we should document how to leverage it and maybe its limitation see | 0 |
711,929 | 24,479,904,516 | IssuesEvent | 2022-10-08 17:35:39 | pystardust/ani-cli | https://api.github.com/repos/pystardust/ani-cli | closed | How to Play anime on VLC on Termux (android) | type: feature request priority 4: wishlist | Hi,
I was having this issue of not getting to play anime on Vlc on Termux on android
ani-cli had mentioned that they had vlc working but I can't seem to figure out if it's there on android yet
If not, I would highly request you to add this feature on termux android.
If yes, then could please help how to properly set it up on termux android
Thanking you in anticipation.
PS: Ani cli is just amazing
| 1.0 | How to Play anime on VLC on Termux (android) - Hi,
I was having this issue of not getting to play anime on Vlc on Termux on android
ani-cli had mentioned that they had vlc working but I can't seem to figure out if it's there on android yet
If not, I would highly request you to add this feature on termux android.
If yes, then could please help how to properly set it up on termux android
Thanking you in anticipation.
PS: Ani cli is just amazing
| priority | how to play anime on vlc on termux android hi i was having this issue of not getting to play anime on vlc on termux on android ani cli had mentioned that they had vlc working but i can t seem to figure out if it s there on android yet if not i would highly request you to add this feature on termux android if yes then could please help how to properly set it up on termux android thanking you in anticipation ps ani cli is just amazing | 1 |
366,861 | 10,831,631,661 | IssuesEvent | 2019-11-11 08:47:57 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | mobile.williamhill.com - site is not usable | browser-firefox-mobile engine-gecko priority-normal | <!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://mobile.williamhill.com/android
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android
**Tested Another Browser**: Yes
**Problem type**: Site is not usable
**Description**: site keeps timing out and I'm trying to place a bet for over 30 minutes now.
**Steps to Reproduce**:
[](https://webcompat.com/uploads/2019/11/92cba71d-9247-4ee6-b171-f6d8d2841e28.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20191024175008</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | mobile.williamhill.com - site is not usable - <!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://mobile.williamhill.com/android
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android
**Tested Another Browser**: Yes
**Problem type**: Site is not usable
**Description**: site keeps timing out and I'm trying to place a bet for over 30 minutes now.
**Steps to Reproduce**:
[](https://webcompat.com/uploads/2019/11/92cba71d-9247-4ee6-b171-f6d8d2841e28.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20191024175008</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | mobile williamhill com site is not usable url browser version firefox mobile operating system android tested another browser yes problem type site is not usable description site keeps timing out and i m trying to place a bet for over minutes now steps to reproduce browser configuration gfx webrender all false gfx webrender blob images true gfx webrender enabled false image mem shared true buildid channel beta hastouchscreen true mixed active content blocked false mixed passive content blocked false tracking content blocked false from with ❤️ | 1 |
41,643 | 5,382,232,468 | IssuesEvent | 2017-02-24 00:42:12 | coreos/etcd | https://api.github.com/repos/coreos/etcd | opened | TestNodeTick: elapsed = 0, want 1 | area/testing | via https://semaphoreci.com/coreos/etcd/branches/pull-request-7373/builds/3
```
--- FAIL: TestNodeTick (0.03s)
node_test.go:408: elapsed = 0, want 1
```
| 1.0 | TestNodeTick: elapsed = 0, want 1 - via https://semaphoreci.com/coreos/etcd/branches/pull-request-7373/builds/3
```
--- FAIL: TestNodeTick (0.03s)
node_test.go:408: elapsed = 0, want 1
```
| non_priority | testnodetick elapsed want via fail testnodetick node test go elapsed want | 0 |
723,551 | 24,901,369,211 | IssuesEvent | 2022-10-28 21:19:22 | QuiltMC/quiltflower | https://api.github.com/repos/QuiltMC/quiltflower | closed | Support decompiling jars embedded into executables | enhancement Subsystem: IO Priority: Low | ## Why?
Sometimes it's convenient that when you know an executable contains a valid JAR or ZIP to just run the decompiler pointing to the executable directly. An older Minecraft launcher or server JAR-as-EXE maybe a good candidate to test the implementation. It maybe possible to extend this to jlink images if they share a similar format, perhaps ignoring the bundled stdlib where applicable unless a flag is passed.
## Expected behaviour
`java -jar quiltflower-1.7.0.jar Minecraft.exe ./output`
The above command to be able to find the JAR in the executable and to be able to decompile it.
Of course, when there's no valid JAR to be found, it can exit with an error.
## Actual behaviour
Right now, it just prints the current JVM version and immediately exits without any error or warning. | 1.0 | Support decompiling jars embedded into executables - ## Why?
Sometimes it's convenient that when you know an executable contains a valid JAR or ZIP to just run the decompiler pointing to the executable directly. An older Minecraft launcher or server JAR-as-EXE maybe a good candidate to test the implementation. It maybe possible to extend this to jlink images if they share a similar format, perhaps ignoring the bundled stdlib where applicable unless a flag is passed.
## Expected behaviour
`java -jar quiltflower-1.7.0.jar Minecraft.exe ./output`
The above command to be able to find the JAR in the executable and to be able to decompile it.
Of course, when there's no valid JAR to be found, it can exit with an error.
## Actual behaviour
Right now, it just prints the current JVM version and immediately exits without any error or warning. | priority | support decompiling jars embedded into executables why sometimes it s convenient that when you know an executable contains a valid jar or zip to just run the decompiler pointing to the executable directly an older minecraft launcher or server jar as exe maybe a good candidate to test the implementation it maybe possible to extend this to jlink images if they share a similar format perhaps ignoring the bundled stdlib where applicable unless a flag is passed expected behaviour java jar quiltflower jar minecraft exe output the above command to be able to find the jar in the executable and to be able to decompile it of course when there s no valid jar to be found it can exit with an error actual behaviour right now it just prints the current jvm version and immediately exits without any error or warning | 1 |
31,410 | 5,950,099,194 | IssuesEvent | 2017-05-26 15:50:16 | lodash/lodash | https://api.github.com/repos/lodash/lodash | closed | Better documentation for lodash/fp | documentation wontfix | I really like how `lodash/fp` promotes functional programming.
Unfortunately, the documentation is not very friendly to new users, especially if they are also not that familiar with lodash itself, as it is relative to the 'normal' lodash docu.
This gives me a hard time promoting its usefulness.
Would it be possible to have a stand alone `lodash/fp` documentation, with full descriptions and signatures? Maybe by programmatically merging the two? | 1.0 | Better documentation for lodash/fp - I really like how `lodash/fp` promotes functional programming.
Unfortunately, the documentation is not very friendly to new users, especially if they are also not that familiar with lodash itself, as it is relative to the 'normal' lodash docu.
This gives me a hard time promoting its usefulness.
Would it be possible to have a stand alone `lodash/fp` documentation, with full descriptions and signatures? Maybe by programmatically merging the two? | non_priority | better documentation for lodash fp i really like how lodash fp promotes functional programming unfortunately the documentation is not very friendly to new users especially if they are also not that familiar with lodash itself as it is relative to the normal lodash docu this gives me a hard time promoting its usefulness would it be possible to have a stand alone lodash fp documentation with full descriptions and signatures maybe by programmatically merging the two | 0 |
449,746 | 31,859,355,668 | IssuesEvent | 2023-09-15 09:46:02 | aws-powertools/powertools-lambda-python | https://api.github.com/repos/aws-powertools/powertools-lambda-python | opened | Docs: Twitch videos are broken in the "we-made-this" section | documentation triage | ### What were you searching in the docs?
After moving our website to a new domain, some Twitch videos are broken because they refer to the old domain
Example:
<iframe src="https://player.twitch.tv/?video=1034744364&parent=awslabs.github.io&autoplay=false" frameborder="0" allowfullscreen="true" scrolling="no" height="378" width="620"></iframe>
### Is this related to an existing documentation section?
https://docs.powertools.aws.dev/lambda/python/latest/we_made_this/
### How can we improve?
Fixing the domain reference.
### Got a suggestion in mind?
_No response_
### Acknowledgment
- [X] I understand the final update might be different from my proposed suggestion, or refused. | 1.0 | Docs: Twitch videos are broken in the "we-made-this" section - ### What were you searching in the docs?
After moving our website to a new domain, some Twitch videos are broken because they refer to the old domain
Example:
<iframe src="https://player.twitch.tv/?video=1034744364&parent=awslabs.github.io&autoplay=false" frameborder="0" allowfullscreen="true" scrolling="no" height="378" width="620"></iframe>
### Is this related to an existing documentation section?
https://docs.powertools.aws.dev/lambda/python/latest/we_made_this/
### How can we improve?
Fixing the domain reference.
### Got a suggestion in mind?
_No response_
### Acknowledgment
- [X] I understand the final update might be different from my proposed suggestion, or refused. | non_priority | docs twitch videos are broken in the we made this section what were you searching in the docs after moving our website to a new domain some twitch videos are broken because they refer to the old domain example is this related to an existing documentation section how can we improve fixing the domain reference got a suggestion in mind no response acknowledgment i understand the final update might be different from my proposed suggestion or refused | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.