Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 4 112 | repo_url stringlengths 33 141 | action stringclasses 3 values | title stringlengths 1 1.02k | labels stringlengths 4 1.54k | body stringlengths 1 262k | index stringclasses 17 values | text_combine stringlengths 95 262k | label stringclasses 2 values | text stringlengths 96 252k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
62,029 | 6,773,886,680 | IssuesEvent | 2017-10-27 08:16:35 | uccser/cs-unplugged | https://api.github.com/repos/uccser/cs-unplugged | closed | test_makeresources_command appears to not run | research needed testing | The test passes but produces no output compared to `test_updatedata_command`. However there is probably a better way to test these commands, and run smoke tests elsewhere. | 1.0 | test_makeresources_command appears to not run - The test passes but produces no output compared to `test_updatedata_command`. However there is probably a better way to test these commands, and run smoke tests elsewhere. | test | test makeresources command appears to not run the test passes but produces no output compared to test updatedata command however there is probably a better way to test these commands and run smoke tests elsewhere | 1 |
407,784 | 27,631,424,990 | IssuesEvent | 2023-03-10 11:08:22 | KinsonDigital/Velaptor | https://api.github.com/repos/KinsonDigital/Velaptor | closed | 🚧Update twitter link | medium priority preview 📝documentation/product | ### Complete The Item Below
- [X] I have updated the title without removing the 🚧 emoji.
### Description
Update URL section of the markdown links in the _**README.md**_ file to point to the twitter logo located in the **_.github_** org repo.
[Here](https://github.com/KinsonDigital/.github/tree/master/Images) is the location of the logo.
The link URL section below is what you should update the URLs to _**https://raw.githubusercontent.com/KinsonDigital/.github/master/Images/twitter-logo-16x16.svg**_.
### Acceptance Criteria
- [x] twitter logo removed from the repo (if it exists)
> **Note** Usually it exists in the _**./Documentation/Images/**_ folder
- [x] twitter link updated
> **Note** There should be 2 twitter logos to update. One for _**Calvin**_ and one for **Kristen** and is located in the _**README.md**_ file.
### ToDo Items
- [X] Change type labels added to this issue. Refer to the _**Change Type Labels**_ section below.
- [X] Priority label added to this issue. Refer to the _**Priority Type Labels**_ section below.
- [X] Issue linked to the correct project _(if applicable)_.
- [X] Issue linked to the correct milestone _(if applicable)_.
- [x] Draft pull request created and linked to this issue _(only required with code changes)_.
### Issue Dependencies
_No response_
### Related Work
_No response_
### Additional Information:
**_<details closed><summary>Change Type Labels</summary>_**
| Change Type | Label |
|---------------------|----------------------|
| Bug Fixes | `🐛bug` |
| Breaking Changes | `🧨breaking changes` |
| New Feature | `✨new feature` |
| Workflow Changes | `workflow` |
| Code Doc Changes | `🗒️documentation/code` |
| Product Doc Changes | `📝documentation/product` |
</details>
**_<details closed><summary>Priority Type Labels</summary>_**
| Priority Type | Label |
|---------------------|-------------------|
| Low Priority | `low priority` |
| Medium Priority | `medium priority` |
| High Priority | `high priority` |
</details>
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct. | 1.0 | 🚧Update twitter link - ### Complete The Item Below
- [X] I have updated the title without removing the 🚧 emoji.
### Description
Update URL section of the markdown links in the _**README.md**_ file to point to the twitter logo located in the **_.github_** org repo.
[Here](https://github.com/KinsonDigital/.github/tree/master/Images) is the location of the logo.
The link URL section below is what you should update the URLs to _**https://raw.githubusercontent.com/KinsonDigital/.github/master/Images/twitter-logo-16x16.svg**_.
### Acceptance Criteria
- [x] twitter logo removed from the repo (if it exists)
> **Note** Usually it exists in the _**./Documentation/Images/**_ folder
- [x] twitter link updated
> **Note** There should be 2 twitter logos to update. One for _**Calvin**_ and one for **Kristen** and is located in the _**README.md**_ file.
### ToDo Items
- [X] Change type labels added to this issue. Refer to the _**Change Type Labels**_ section below.
- [X] Priority label added to this issue. Refer to the _**Priority Type Labels**_ section below.
- [X] Issue linked to the correct project _(if applicable)_.
- [X] Issue linked to the correct milestone _(if applicable)_.
- [x] Draft pull request created and linked to this issue _(only required with code changes)_.
### Issue Dependencies
_No response_
### Related Work
_No response_
### Additional Information:
**_<details closed><summary>Change Type Labels</summary>_**
| Change Type | Label |
|---------------------|----------------------|
| Bug Fixes | `🐛bug` |
| Breaking Changes | `🧨breaking changes` |
| New Feature | `✨new feature` |
| Workflow Changes | `workflow` |
| Code Doc Changes | `🗒️documentation/code` |
| Product Doc Changes | `📝documentation/product` |
</details>
**_<details closed><summary>Priority Type Labels</summary>_**
| Priority Type | Label |
|---------------------|-------------------|
| Low Priority | `low priority` |
| Medium Priority | `medium priority` |
| High Priority | `high priority` |
</details>
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct. | non_test | 🚧update twitter link complete the item below i have updated the title without removing the 🚧 emoji description update url section of the markdown links in the readme md file to point to the twitter logo located in the github org repo is the location of the logo the link url section below is what you should update the urls to acceptance criteria twitter logo removed from the repo if it exists note usually it exists in the documentation images folder twitter link updated note there should be twitter logos to update one for calvin and one for kristen and is located in the readme md file todo items change type labels added to this issue refer to the change type labels section below priority label added to this issue refer to the priority type labels section below issue linked to the correct project if applicable issue linked to the correct milestone if applicable draft pull request created and linked to this issue only required with code changes issue dependencies no response related work no response additional information change type labels change type label bug fixes 🐛bug breaking changes 🧨breaking changes new feature ✨new feature workflow changes workflow code doc changes 🗒️documentation code product doc changes 📝documentation product priority type labels priority type label low priority low priority medium priority medium priority high priority high priority code of conduct i agree to follow this project s code of conduct | 0 |
182,599 | 14,143,470,583 | IssuesEvent | 2020-11-10 15:18:45 | backend-br/vagas | https://api.github.com/repos/backend-br/vagas | closed | [Rio de Janeiro/Remoto] JAVA Back-end Developer @ MPRJ | Alocado Arquiteto Docker Especialista Java Kubernetes MongoDB MySQL Remoto Rest Scrum Spring TDD Testes automatizados | > Vaga Remota durante a pandemia
## Nossa empresa
O Ministério Público do Estado do Rio de Janeiro (MPRJ) é a instância no Estado do Rio de Janeiro do Ministério Público, que tem como objetivo defender os direitos dos cidadãos e os interesses da sociedade.
## Descrição da vaga
Esta posição é para atuar como Dev Backend nos projetos da Gerência de Sistema de Informação, responsável por desenvolver e manter os principais sistemas do MPRJ.
É um local de trabalho descontraído, composto por servidores públicos efetivos (concursados) e extra quadro (cargo de nomeação), que trabalham para permitir que a atuação do MPRJ na sociedade tenha cada vez mais valor para a sociedade brasileira.
Trabalhamos com práticas ágeis de gestão e desenvolvimento de softwares, incluindo frameworks como Scrum e Kanban e práticas como Pair Programming, TDD, XP e Code Review.
Algumas tecnologias utilizadas em nossos sistemas: AngularJS, Angular, Javascript, Typescript, Java 8, OpenShift, Oracle, MongoDB, Elasticsearch, Kibana, Spring Boot, Spring Framework, JBoss, JMS, JSF, React, Redis
## Local
Rio de Janeiro, RJ (Remoto, pelo menos, até o final de 2020)
## Requisitos
**Obrigatórios:**
- Orientação a resultados
- Compromisso com qualidade
- Senso de trabalho em equipe
- Proatividade
- Organização
- Experiência com linguagem Java
- Experiência com Spring Framework
- Experiência com testes automatizados
- Experiência com banco de dados relacional (Ex: Oracle, MySQL, Postgres)
- Experiência com APIs REST
- Experiência com Maven
**Desejáveis:**
- Hibernate
- SpringBoot
- OpenShift
- Docker
- Kubernetes
- Redis
- Elasticsearch
- Kibana
- MongoDB
- JMS
- Jenkins
- Gitlab
- Modelagem de Dados
**Diferenciais:**
- Horário flexível
- Workstation Dell Intel Xeon 32 GB RAM SSD Monitor 27"
## Benefícios
- auxílio alimentação
- auxílio creche/escola (para os filhos)
- auxílio saúde
- décimo terceiro salário
- férias remuneradas
- horário flexível
- trabalho remoto (pelo menos até o fim de 2020)
## Contratação
Servidor Extra Quadro
## Como se candidatar
Por favor, preencha o cadastro no link https://bit.ly/JavaBackendMPRJ
## Tempo médio de feedbacks
Costumamos enviar feedbacks em até 14 dias após cada processo.
## Labels
- Java
- JavaEE
- Sênior
- Arquiteto
- Remoto
- Hibernate
- SpringBoot
- OpenShift
- Docker
- Kubernetes
- Redis
- Elasticsearch
- Kibana
- MongoDB
- JMS
- Jenkins
- Gitlab
- Rio de Janeiro
#### Alocação
- Alocado
- Remoto
#### Regime
- Servidor Extra Quadro
#### Nível
- Sênior
- Especialista
| 1.0 | [Rio de Janeiro/Remoto] JAVA Back-end Developer @ MPRJ - > Vaga Remota durante a pandemia
## Nossa empresa
O Ministério Público do Estado do Rio de Janeiro (MPRJ) é a instância no Estado do Rio de Janeiro do Ministério Público, que tem como objetivo defender os direitos dos cidadãos e os interesses da sociedade.
## Descrição da vaga
Esta posição é para atuar como Dev Backend nos projetos da Gerência de Sistema de Informação, responsável por desenvolver e manter os principais sistemas do MPRJ.
É um local de trabalho descontraído, composto por servidores públicos efetivos (concursados) e extra quadro (cargo de nomeação), que trabalham para permitir que a atuação do MPRJ na sociedade tenha cada vez mais valor para a sociedade brasileira.
Trabalhamos com práticas ágeis de gestão e desenvolvimento de softwares, incluindo frameworks como Scrum e Kanban e práticas como Pair Programming, TDD, XP e Code Review.
Algumas tecnologias utilizadas em nossos sistemas: AngularJS, Angular, Javascript, Typescript, Java 8, OpenShift, Oracle, MongoDB, Elasticsearch, Kibana, Spring Boot, Spring Framework, JBoss, JMS, JSF, React, Redis
## Local
Rio de Janeiro, RJ (Remoto, pelo menos, até o final de 2020)
## Requisitos
**Obrigatórios:**
- Orientação a resultados
- Compromisso com qualidade
- Senso de trabalho em equipe
- Proatividade
- Organização
- Experiência com linguagem Java
- Experiência com Spring Framework
- Experiência com testes automatizados
- Experiência com banco de dados relacional (Ex: Oracle, MySQL, Postgres)
- Experiência com APIs REST
- Experiência com Maven
**Desejáveis:**
- Hibernate
- SpringBoot
- OpenShift
- Docker
- Kubernetes
- Redis
- Elasticsearch
- Kibana
- MongoDB
- JMS
- Jenkins
- Gitlab
- Modelagem de Dados
**Diferenciais:**
- Horário flexível
- Workstation Dell Intel Xeon 32 GB RAM SSD Monitor 27"
## Benefícios
- auxílio alimentação
- auxílio creche/escola (para os filhos)
- auxílio saúde
- décimo terceiro salário
- férias remuneradas
- horário flexível
- trabalho remoto (pelo menos até o fim de 2020)
## Contratação
Servidor Extra Quadro
## Como se candidatar
Por favor, preencha o cadastro no link https://bit.ly/JavaBackendMPRJ
## Tempo médio de feedbacks
Costumamos enviar feedbacks em até 14 dias após cada processo.
## Labels
- Java
- JavaEE
- Sênior
- Arquiteto
- Remoto
- Hibernate
- SpringBoot
- OpenShift
- Docker
- Kubernetes
- Redis
- Elasticsearch
- Kibana
- MongoDB
- JMS
- Jenkins
- Gitlab
- Rio de Janeiro
#### Alocação
- Alocado
- Remoto
#### Regime
- Servidor Extra Quadro
#### Nível
- Sênior
- Especialista
| test | java back end developer mprj vaga remota durante a pandemia nossa empresa o ministério público do estado do rio de janeiro mprj é a instância no estado do rio de janeiro do ministério público que tem como objetivo defender os direitos dos cidadãos e os interesses da sociedade descrição da vaga esta posição é para atuar como dev backend nos projetos da gerência de sistema de informação responsável por desenvolver e manter os principais sistemas do mprj é um local de trabalho descontraído composto por servidores públicos efetivos concursados e extra quadro cargo de nomeação que trabalham para permitir que a atuação do mprj na sociedade tenha cada vez mais valor para a sociedade brasileira trabalhamos com práticas ágeis de gestão e desenvolvimento de softwares incluindo frameworks como scrum e kanban e práticas como pair programming tdd xp e code review algumas tecnologias utilizadas em nossos sistemas angularjs angular javascript typescript java openshift oracle mongodb elasticsearch kibana spring boot spring framework jboss jms jsf react redis local rio de janeiro rj remoto pelo menos até o final de requisitos obrigatórios orientação a resultados compromisso com qualidade senso de trabalho em equipe proatividade organização experiência com linguagem java experiência com spring framework experiência com testes automatizados experiência com banco de dados relacional ex oracle mysql postgres experiência com apis rest experiência com maven desejáveis hibernate springboot openshift docker kubernetes redis elasticsearch kibana mongodb jms jenkins gitlab modelagem de dados diferenciais horário flexível workstation dell intel xeon gb ram ssd monitor benefícios auxílio alimentação auxílio creche escola para os filhos auxílio saúde décimo terceiro salário férias remuneradas horário flexível trabalho remoto pelo menos até o fim de contratação servidor extra quadro como se candidatar por favor preencha o cadastro no link tempo médio de feedbacks costumamos enviar feedbacks em até dias após cada processo labels java javaee sênior arquiteto remoto hibernate springboot openshift docker kubernetes redis elasticsearch kibana mongodb jms jenkins gitlab rio de janeiro alocação alocado remoto regime servidor extra quadro nível sênior especialista | 1 |
426,135 | 12,367,930,641 | IssuesEvent | 2020-05-18 13:05:06 | jenkins-x/jx | https://api.github.com/repos/jenkins-x/jx | closed | Unable to update resources for webhook change during `jx upgrade ingress` | area/ingress kind/needs-validation lifecycle/rotten priority/awaiting-more-evidence | ### Summary
`jx upgrade ingress` removes ingress configurations and doesn't recreate them.
### Steps to reproduce the behavior
```
jx upgrade ingress
Existing ingress rules found in current namespace. Confirm to delete and recreate them Yes
```
Choose: Yes
### Expected behavior
Upgrade successful
### Actual behavior
```
? Existing ingress rules found in current namespace. Confirm to delete and recreate them Yes
? Expose type Ingress
? Domain: ****
? If your network is publicly available would you like to enable cluster wide TLS? Yes
If testing LetsEncrypt you should use staging as you may be rate limited using production.
? Use LetsEncrypt staging or production? production
? Email address to register with LetsEncrypt: ****@****
? URLTemplate (press <Enter> to keep the current value): "{{.Service}}.{{.Domain}}"
? Using config values {****@***** ***** letsencrypt-prod false Ingress "{{.Service}}.{{.Domain}}" true}, ok? Yes
Looking for "cert-manager" deployment in namespace "cert-manager"...
Deleting ingress geeoz/deck
Deleting ingress geeoz/hook
Deleting ingress geeoz/tide
...
Ingress rules recreated
error: unable to update resources for webhook change: retrieving the webhook endpoint: getting ingress for service "hook" in namespace geeoz: ingresses.extensions "hook" not found
```
### Jx version
The output of `jx version` is:
```
NAME VERSION
jx 2.0.886
jenkins x platform 2.0.1480
Kubernetes cluster v1.15.3
kubectl v1.16.2
helm client Client: v2.14.3+g0e7f3b6
git 2.23.0
Operating System Mac OS X 10.15.1 build 19B77a
```
### Jenkins type
<!--
Select which installation type are you using.
-->
- [x] Serverless Jenkins X Pipelines (Tekton + Prow)
- [ ] Classic Jenkins
### Kubernetes cluster
<!--
What kind of Kubernetes cluster are you using & how did you create it?
-->
Self-created with kubespray
### Operating system / Environment
<!--
In which environment are you running the jx CLI?
-->
Running the CLI on my MacBook Pro (OS X)
| 1.0 | Unable to update resources for webhook change during `jx upgrade ingress` - ### Summary
`jx upgrade ingress` removes ingress configurations and doesn't recreate them.
### Steps to reproduce the behavior
```
jx upgrade ingress
Existing ingress rules found in current namespace. Confirm to delete and recreate them Yes
```
Choose: Yes
### Expected behavior
Upgrade successful
### Actual behavior
```
? Existing ingress rules found in current namespace. Confirm to delete and recreate them Yes
? Expose type Ingress
? Domain: ****
? If your network is publicly available would you like to enable cluster wide TLS? Yes
If testing LetsEncrypt you should use staging as you may be rate limited using production.
? Use LetsEncrypt staging or production? production
? Email address to register with LetsEncrypt: ****@****
? URLTemplate (press <Enter> to keep the current value): "{{.Service}}.{{.Domain}}"
? Using config values {****@***** ***** letsencrypt-prod false Ingress "{{.Service}}.{{.Domain}}" true}, ok? Yes
Looking for "cert-manager" deployment in namespace "cert-manager"...
Deleting ingress geeoz/deck
Deleting ingress geeoz/hook
Deleting ingress geeoz/tide
...
Ingress rules recreated
error: unable to update resources for webhook change: retrieving the webhook endpoint: getting ingress for service "hook" in namespace geeoz: ingresses.extensions "hook" not found
```
### Jx version
The output of `jx version` is:
```
NAME VERSION
jx 2.0.886
jenkins x platform 2.0.1480
Kubernetes cluster v1.15.3
kubectl v1.16.2
helm client Client: v2.14.3+g0e7f3b6
git 2.23.0
Operating System Mac OS X 10.15.1 build 19B77a
```
### Jenkins type
<!--
Select which installation type are you using.
-->
- [x] Serverless Jenkins X Pipelines (Tekton + Prow)
- [ ] Classic Jenkins
### Kubernetes cluster
<!--
What kind of Kubernetes cluster are you using & how did you create it?
-->
Self-created with kubespray
### Operating system / Environment
<!--
In which environment are you running the jx CLI?
-->
Running the CLI on my MacBook Pro (OS X)
| non_test | unable to update resources for webhook change during jx upgrade ingress summary jx upgrade ingress removes ingress configurations and doesn t recreate them steps to reproduce the behavior jx upgrade ingress existing ingress rules found in current namespace confirm to delete and recreate them yes choose yes expected behavior upgrade successful actual behavior existing ingress rules found in current namespace confirm to delete and recreate them yes expose type ingress domain if your network is publicly available would you like to enable cluster wide tls yes if testing letsencrypt you should use staging as you may be rate limited using production use letsencrypt staging or production production email address to register with letsencrypt urltemplate press to keep the current value service domain using config values letsencrypt prod false ingress service domain true ok yes looking for cert manager deployment in namespace cert manager deleting ingress geeoz deck deleting ingress geeoz hook deleting ingress geeoz tide ingress rules recreated error unable to update resources for webhook change retrieving the webhook endpoint getting ingress for service hook in namespace geeoz ingresses extensions hook not found jx version the output of jx version is name version jx jenkins x platform kubernetes cluster kubectl helm client client git operating system mac os x build jenkins type select which installation type are you using serverless jenkins x pipelines tekton prow classic jenkins kubernetes cluster what kind of kubernetes cluster are you using how did you create it self created with kubespray operating system environment in which environment are you running the jx cli running the cli on my macbook pro os x | 0 |
149,433 | 11,900,801,263 | IssuesEvent | 2020-03-30 11:19:02 | open-xchange/ox-coi | https://api.github.com/repos/open-xchange/ox-coi | closed | Add tests for flagged messages per chat | enhancement testing | **Is your feature request related to a problem? Please describe.**
We have now the possibility to show all flagged messages for one chat. The view can be opened via the chat profile view (tap on the name of the chat in the chat view to open). A "Flagged messages" entry should be available.
**Describe the solution you'd like**
Please implement this test similar to the general flagged view tests. | 1.0 | Add tests for flagged messages per chat - **Is your feature request related to a problem? Please describe.**
We have now the possibility to show all flagged messages for one chat. The view can be opened via the chat profile view (tap on the name of the chat in the chat view to open). A "Flagged messages" entry should be available.
**Describe the solution you'd like**
Please implement this test similar to the general flagged view tests. | test | add tests for flagged messages per chat is your feature request related to a problem please describe we have now the possibility to show all flagged messages for one chat the view can be opened via the chat profile view tap on the name of the chat in the chat view to open a flagged messages entry should be available describe the solution you d like please implement this test similar to the general flagged view tests | 1 |
326,418 | 27,989,793,787 | IssuesEvent | 2023-03-27 02:01:32 | kubernetes-sigs/cloud-provider-azure | https://api.github.com/repos/kubernetes-sigs/cloud-provider-azure | opened | Image building job is failure for not found image | kind/failing-test | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
post-cloud-provider-azure-push-images
#### Which test(s) are failing:
#### Since when has it been failing:
The time this PR is merged.
https://github.com/kubernetes-sigs/cloud-provider-azure/pull/3555
#### Testgrid link:
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/post-provider-azure-push-images/1640148615437488128
#### Reason for failure:
gcr.io/k8s-staging-e2e-test-images/windows-servercore-cache:1.0-linux-amd64-ltsc2019 not found.
#### Anything else we need to know:
| 1.0 | Image building job is failure for not found image - <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
post-cloud-provider-azure-push-images
#### Which test(s) are failing:
#### Since when has it been failing:
The time this PR is merged.
https://github.com/kubernetes-sigs/cloud-provider-azure/pull/3555
#### Testgrid link:
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/post-provider-azure-push-images/1640148615437488128
#### Reason for failure:
gcr.io/k8s-staging-e2e-test-images/windows-servercore-cache:1.0-linux-amd64-ltsc2019 not found.
#### Anything else we need to know:
| test | image building job is failure for not found image which jobs are failing post cloud provider azure push images which test s are failing since when has it been failing the time this pr is merged testgrid link reason for failure gcr io staging test images windows servercore cache linux not found anything else we need to know | 1 |
267,506 | 28,509,069,789 | IssuesEvent | 2023-04-19 01:32:41 | dpteam/RK3188_TABLET | https://api.github.com/repos/dpteam/RK3188_TABLET | closed | CVE-2016-6187 (High) detected in kvmarmv3.1 - autoclosed | Mend: dependency security vulnerability | ## CVE-2016-6187 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>kvmarmv3.1</b></p></summary>
<p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git>https://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/dpteam/RK3188_TABLET/commit/0c501f5a0fd72c7b2ac82904235363bd44fd8f9e">0c501f5a0fd72c7b2ac82904235363bd44fd8f9e</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (3)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/security/apparmor/lsm.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/security/apparmor/lsm.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/security/apparmor/lsm.c</b>
</p>
</details>
<p></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 apparmor_setprocattr function in security/apparmor/lsm.c in the Linux kernel before 4.6.5 does not validate the buffer size, which allows local users to gain privileges by triggering an AppArmor setprocattr hook.
<p>Publish Date: 2016-08-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-6187>CVE-2016-6187</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.8</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: 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>
<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://nvd.nist.gov/vuln/detail/CVE-2016-6187">https://nvd.nist.gov/vuln/detail/CVE-2016-6187</a></p>
<p>Release Date: 2016-08-06</p>
<p>Fix Resolution: 4.6.5</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2016-6187 (High) detected in kvmarmv3.1 - autoclosed - ## CVE-2016-6187 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>kvmarmv3.1</b></p></summary>
<p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git>https://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/dpteam/RK3188_TABLET/commit/0c501f5a0fd72c7b2ac82904235363bd44fd8f9e">0c501f5a0fd72c7b2ac82904235363bd44fd8f9e</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (3)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/security/apparmor/lsm.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/security/apparmor/lsm.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/security/apparmor/lsm.c</b>
</p>
</details>
<p></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 apparmor_setprocattr function in security/apparmor/lsm.c in the Linux kernel before 4.6.5 does not validate the buffer size, which allows local users to gain privileges by triggering an AppArmor setprocattr hook.
<p>Publish Date: 2016-08-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-6187>CVE-2016-6187</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.8</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: 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>
<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://nvd.nist.gov/vuln/detail/CVE-2016-6187">https://nvd.nist.gov/vuln/detail/CVE-2016-6187</a></p>
<p>Release Date: 2016-08-06</p>
<p>Fix Resolution: 4.6.5</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve high detected in autoclosed cve high severity vulnerability vulnerable library library home page a href found in head commit a href found in base branch master vulnerable source files security apparmor lsm c security apparmor lsm c security apparmor lsm c vulnerability details the apparmor setprocattr function in security apparmor lsm c in the linux kernel before does not validate the buffer size which allows local users to gain privileges by triggering an apparmor setprocattr hook 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 high integrity impact high 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 mend | 0 |
257,613 | 22,196,944,296 | IssuesEvent | 2022-06-07 07:50:18 | Tencent/bk-ci | https://api.github.com/repos/Tencent/bk-ci | closed | bug: 归档报告插件找不到文件夹时运行失败 | kind/bug for gray for test area/ci/backend kind/version/sample streams/for gray streams/done | 归档报告插件当找不到文件夹时，会抛javax.ws.rs.core.Response.NotFoundException异常
因为移除了jersey-common依赖，导致运行失败
Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: org.glassfish.jersey.internal.RuntimeDelegateImpl
at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:152)
at javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:120)
at javax.ws.rs.core.Response$ResponseBuilder.newInstance(Response.java:848)
at javax.ws.rs.core.Response.status(Response.java:590)
at javax.ws.rs.core.Response.status(Response.java:601)
at javax.ws.rs.ClientErrorException.<init>(ClientErrorException.java:79)
at javax.ws.rs.NotFoundException.<init>(NotFoundException.java:70)
at com.tencent.devops.plugin.worker.task.archive.ReportArchiveTask.execute(ReportArchiveTask.kt:82)
at com.tencent.devops.worker.common.task.ITask.run(ITask.kt:81)
at com.tencent.devops.worker.common.task.TaskDaemon.call(TaskDaemon.kt:53)
at com.tencent.devops.worker.common.task.TaskDaemon.call(TaskDaemon.kt:45)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:812) | 1.0 | bug: 归档报告插件找不到文件夹时运行失败 - 归档报告插件当找不到文件夹时，会抛javax.ws.rs.core.Response.NotFoundException异常
因为移除了jersey-common依赖，导致运行失败
Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: org.glassfish.jersey.internal.RuntimeDelegateImpl
at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:152)
at javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:120)
at javax.ws.rs.core.Response$ResponseBuilder.newInstance(Response.java:848)
at javax.ws.rs.core.Response.status(Response.java:590)
at javax.ws.rs.core.Response.status(Response.java:601)
at javax.ws.rs.ClientErrorException.<init>(ClientErrorException.java:79)
at javax.ws.rs.NotFoundException.<init>(NotFoundException.java:70)
at com.tencent.devops.plugin.worker.task.archive.ReportArchiveTask.execute(ReportArchiveTask.kt:82)
at com.tencent.devops.worker.common.task.ITask.run(ITask.kt:81)
at com.tencent.devops.worker.common.task.TaskDaemon.call(TaskDaemon.kt:53)
at com.tencent.devops.worker.common.task.TaskDaemon.call(TaskDaemon.kt:45)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:812) | test | bug 归档报告插件找不到文件夹时运行失败 归档报告插件当找不到文件夹时，会抛javax ws rs core response notfoundexception异常 因为移除了jersey common依赖，导致运行失败 caused by java lang runtimeexception java lang classnotfoundexception org glassfish jersey internal runtimedelegateimpl at javax ws rs ext runtimedelegate finddelegate runtimedelegate java at javax ws rs ext runtimedelegate getinstance runtimedelegate java at javax ws rs core response responsebuilder newinstance response java at javax ws rs core response status response java at javax ws rs core response status response java at javax ws rs clienterrorexception clienterrorexception java at javax ws rs notfoundexception notfoundexception java at com tencent devops plugin worker task archive reportarchivetask execute reportarchivetask kt at com tencent devops worker common task itask run itask kt at com tencent devops worker common task taskdaemon call taskdaemon kt at com tencent devops worker common task taskdaemon call taskdaemon kt at java util concurrent futuretask run futuretask java at java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java lang thread run thread java | 1 |
226,024 | 17,935,420,332 | IssuesEvent | 2021-09-10 14:45:19 | istio/istio | https://api.github.com/repos/istio/istio | opened | istio/base CI job should build arm64 image as well | area/test and release | Job should set `DOCKER_ARCHITECTURES="linux/amd64,linux/arm64"`. There are some additional setup steps needed as well, described in the build script | 1.0 | istio/base CI job should build arm64 image as well - Job should set `DOCKER_ARCHITECTURES="linux/amd64,linux/arm64"`. There are some additional setup steps needed as well, described in the build script | test | istio base ci job should build image as well job should set docker architectures linux linux there are some additional setup steps needed as well described in the build script | 1 |
137,610 | 11,147,180,826 | IssuesEvent | 2019-12-23 11:50:56 | inspire-eu-validation/community | https://api.github.com/repos/inspire-eu-validation/community | reopened | Typo error in code: Expected "harmonished" instead of "harmonised" for conformance Class 7 | ready for testing | In the "Conformance Class 7 - Harmonised Spatial Data Services Metadata" the online validator expects the value "harmonished" instead of "harmonised" in the title of the CI_Citation of the domain consistency specification.
It expects:
<gmx:Anchor xlink:href="http://inspire.ec.europa.eu/id/ats/metadata/2.0/sds-harmonised">harmonished</gmx:Anchor>
While correct is
<gmx:Anchor xlink:href="http://inspire.ec.europa.eu/id/ats/metadata/2.0/sds-harmonised">harmonised</gmx:Anchor>
I expect that correct should be also:
<gmx:Anchor xlink:href="http://inspire.ec.europa.eu/id/ats/metadata/2.0/sds-harmonised"/>
This is a minor error, very easy to fix in the code, just delete the second "h" letter in the word "harmonis**h**ed". | 1.0 | Typo error in code: Expected "harmonished" instead of "harmonised" for conformance Class 7 - In the "Conformance Class 7 - Harmonised Spatial Data Services Metadata" the online validator expects the value "harmonished" instead of "harmonised" in the title of the CI_Citation of the domain consistency specification.
It expects:
<gmx:Anchor xlink:href="http://inspire.ec.europa.eu/id/ats/metadata/2.0/sds-harmonised">harmonished</gmx:Anchor>
While correct is
<gmx:Anchor xlink:href="http://inspire.ec.europa.eu/id/ats/metadata/2.0/sds-harmonised">harmonised</gmx:Anchor>
I expect that correct should be also:
<gmx:Anchor xlink:href="http://inspire.ec.europa.eu/id/ats/metadata/2.0/sds-harmonised"/>
This is a minor error, very easy to fix in the code, just delete the second "h" letter in the word "harmonis**h**ed". | test | typo error in code expected harmonished instead of harmonised for conformance class in the conformance class harmonised spatial data services metadata the online validator expects the value harmonished instead of harmonised in the title of the ci citation of the domain consistency specification it expects gmx anchor xlink href while correct is gmx anchor xlink href i expect that correct should be also gmx anchor xlink href this is a minor error very easy to fix in the code just delete the second h letter in the word harmonis h ed | 1 |
263,481 | 23,061,379,437 | IssuesEvent | 2022-07-25 10:14:32 | WEC-Sim/WEC-Sim | https://api.github.com/repos/WEC-Sim/WEC-Sim | opened | [BUG] Unable to resolve the name 'clock_out.time' (Desalination) | Bug WEC-Sim Application Tests/CI | **Describe the bug**
There is a CI failure for the desalination application case e.g. [here](https://github.com/WEC-Sim/WEC-Sim_Applications/actions/runs/2707787456).
**WEC-Sim file(s)**
Seems to be related to [this line](https://github.com/WEC-Sim/WEC-Sim/blob/fceb0a8318465b1b0bcdf02d9b13b3b5ae9bc22a/source/functions/postProcessWecSim.m#L7) in `postProcessWecSim.m`. I guess the global `clock_out` or it's field `time` is not being set in this case.
Here is the trace:
```
================================================================================
Error occurred in TestDesalination/testDesalination and it did not run to completion.
---------
Error ID:
---------
'MATLAB:undefinedVarOrClass'
--------------
Error Details:
--------------
Unable to resolve the name 'clock_out.time'.
Error in postProcessWecSim (line 7)
simu.time = clock_out.time;
Error in stopWecSim (line 21)
postProcessWecSim
Error in run (line [91](https://github.com/WEC-Sim/WEC-Sim_Applications/runs/7438361219?check_suite_focus=true#step:10:93))
evalin('caller', strcat(script, ';'));
Error in wecSim (line 48)
run('stopWecSim');
Error in TestDesalination/testDesalination (line 54)
wecSim
================================================================================
```
**Additional context**
This [commit](https://github.com/WEC-Sim/WEC-Sim_Applications/commit/56851c578c49e8190e25576033331943379bc959) was made by @kmruehl in an attempt to correct the issue, but it didn't work.
| 1.0 | [BUG] Unable to resolve the name 'clock_out.time' (Desalination) - **Describe the bug**
There is a CI failure for the desalination application case e.g. [here](https://github.com/WEC-Sim/WEC-Sim_Applications/actions/runs/2707787456).
**WEC-Sim file(s)**
Seems to be related to [this line](https://github.com/WEC-Sim/WEC-Sim/blob/fceb0a8318465b1b0bcdf02d9b13b3b5ae9bc22a/source/functions/postProcessWecSim.m#L7) in `postProcessWecSim.m`. I guess the global `clock_out` or it's field `time` is not being set in this case.
Here is the trace:
```
================================================================================
Error occurred in TestDesalination/testDesalination and it did not run to completion.
---------
Error ID:
---------
'MATLAB:undefinedVarOrClass'
--------------
Error Details:
--------------
Unable to resolve the name 'clock_out.time'.
Error in postProcessWecSim (line 7)
simu.time = clock_out.time;
Error in stopWecSim (line 21)
postProcessWecSim
Error in run (line [91](https://github.com/WEC-Sim/WEC-Sim_Applications/runs/7438361219?check_suite_focus=true#step:10:93))
evalin('caller', strcat(script, ';'));
Error in wecSim (line 48)
run('stopWecSim');
Error in TestDesalination/testDesalination (line 54)
wecSim
================================================================================
```
**Additional context**
This [commit](https://github.com/WEC-Sim/WEC-Sim_Applications/commit/56851c578c49e8190e25576033331943379bc959) was made by @kmruehl in an attempt to correct the issue, but it didn't work.
| test | unable to resolve the name clock out time desalination describe the bug there is a ci failure for the desalination application case e g wec sim file s seems to be related to in postprocesswecsim m i guess the global clock out or it s field time is not being set in this case here is the trace error occurred in testdesalination testdesalination and it did not run to completion error id matlab undefinedvarorclass error details unable to resolve the name clock out time error in postprocesswecsim line simu time clock out time error in stopwecsim line postprocesswecsim error in run line evalin caller strcat script error in wecsim line run stopwecsim error in testdesalination testdesalination line wecsim additional context this was made by kmruehl in an attempt to correct the issue but it didn t work | 1 |
24,116 | 4,058,915,879 | IssuesEvent | 2016-05-25 07:29:23 | Microsoft/vscode | https://api.github.com/repos/Microsoft/vscode | closed | Installing extensions from command line does not prompt for restart | question v-test | - VSCode Version: 1.1.0-alpha
- OS Version: Windows 10
Steps to Reproduce:
1. Open Code
2. Install an extension from the command line (e.g. `--install-extension ms-vscode.csharp`)
3. Go back to Code
Does installing from the command line not require restarting Code?
| 1.0 | Installing extensions from command line does not prompt for restart - - VSCode Version: 1.1.0-alpha
- OS Version: Windows 10
Steps to Reproduce:
1. Open Code
2. Install an extension from the command line (e.g. `--install-extension ms-vscode.csharp`)
3. Go back to Code
Does installing from the command line not require restarting Code?
| test | installing extensions from command line does not prompt for restart vscode version alpha os version windows steps to reproduce open code install an extension from the command line e g install extension ms vscode csharp go back to code does installing from the command line not require restarting code | 1 |
712,680 | 24,503,605,434 | IssuesEvent | 2022-10-10 14:36:40 | AY2223S1-CS2103T-W16-1/tp | https://api.github.com/repos/AY2223S1-CS2103T-W16-1/tp | closed | As a hotel manager, I want to add the details of a new guest when they are staying at my hotel | type.Story priority.High | ... so that I know who is staying at my hotel. | 1.0 | As a hotel manager, I want to add the details of a new guest when they are staying at my hotel - ... so that I know who is staying at my hotel. | non_test | as a hotel manager i want to add the details of a new guest when they are staying at my hotel so that i know who is staying at my hotel | 0 |
175,763 | 6,553,755,116 | IssuesEvent | 2017-09-06 00:45:45 | minio/minio | https://api.github.com/repos/minio/minio | closed | [Proposal] Allow setting optional per bucket ttls | duplicate priority: medium triage | <!--- Provide a general summary of the issue in the Title above -->
I think it would be fairly useful if minio allowed per bucket time to live (ttl) to enable the use case where minio acts as a disk backed cache. Unless I missed it in the documentation, there doesnt seem to be an easy way to do this currently.
## Expected Behavior
<!--- If you're describing a bug, tell us what should happen -->
<!--- If you're suggesting a change/improvement, tell us how it should work -->
Allow setting per bucket ttls (like s3)
## Context
<!--- How has this issue affected you? What are you trying to accomplish? -->
<!--- Providing context helps us come up with a solution that is most useful in the real world -->
Currently my company uses s3 for this, but we are investigating alternatives. Minio seems great, but lacks this feature.
## Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
* aws
| 1.0 | [Proposal] Allow setting optional per bucket ttls - <!--- Provide a general summary of the issue in the Title above -->
I think it would be fairly useful if minio allowed per bucket time to live (ttl) to enable the use case where minio acts as a disk backed cache. Unless I missed it in the documentation, there doesnt seem to be an easy way to do this currently.
## Expected Behavior
<!--- If you're describing a bug, tell us what should happen -->
<!--- If you're suggesting a change/improvement, tell us how it should work -->
Allow setting per bucket ttls (like s3)
## Context
<!--- How has this issue affected you? What are you trying to accomplish? -->
<!--- Providing context helps us come up with a solution that is most useful in the real world -->
Currently my company uses s3 for this, but we are investigating alternatives. Minio seems great, but lacks this feature.
## Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
* aws
| non_test | allow setting optional per bucket ttls i think it would be fairly useful if minio allowed per bucket time to live ttl to enable the use case where minio acts as a disk backed cache unless i missed it in the documentation there doesnt seem to be an easy way to do this currently expected behavior allow setting per bucket ttls like context currently my company uses for this but we are investigating alternatives minio seems great but lacks this feature your environment aws | 0 |
50,824 | 6,114,968,926 | IssuesEvent | 2017-06-22 03:48:31 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | teamcity: failed tests on master: testrace/TestEndTransactionResolveOnlyLocalIntents, Example-ORMs/TestSQLAlchemy, Example-ORMs/TestSQLAlchemy/FirstRun, Example-ORMs/TestSQLAlchemy/SecondRun, Example-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart, Example-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Products, Example-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Customers, Example-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Order | Robot test-failure | The following tests appear to have failed:
[#278257](https://teamcity.cockroachdb.com/viewLog.html?buildId=278257):
```
--- FAIL: testrace/TestEndTransactionResolveOnlyLocalIntents (0.070s)
replica_test.go:3902: heartbeat for transaction "test" id=c9b405a9 key="a" rw=false pri=0.00247792 iso=SERIALIZABLE stat=PENDING epo=1 ts=1498100447.919013571,0 orig=1498100447.919013571,0 max=1498100447.919013572,0 wto=false rop=false seq=5 failed; record not present
------- Stdout: -------
I170622 03:00:47.930517 11590 storage/replica_command.go:188 [s1,r2/1:{a -/Max}] test injecting error: boom
--- FAIL: Example-ORMs/TestSQLAlchemy (184.260s)
null
--- FAIL: Example-ORMs/TestSQLAlchemy/FirstRun (180.800s)
main_test.go:160: Get http://localhost:6543/ping: dial tcp [::1]:6543: getsockopt: connection refused
--- FAIL: Example-ORMs/TestSQLAlchemy/SecondRun (1.800s)
null
--- FAIL: Example-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart (0.000s)
null
--- FAIL: Example-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Products (0.040s)
test_driver.go:200: expecting customers from api after creation to be [{0 0x8d4a60}], found []
--- FAIL: Example-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Customers (0.040s)
test_driver.go:200: expecting customers from api after creation to be [{0 0x8d4a60}], found []
------- Stderr: -------
2017/06/22 03:04:26 process 13970 started: ../cockroach start --logtostderr --insecure --host=localhost --port=0 --http-port=0 --store=/tmp/cockroach-testserver117729386 --listening-url-file=/tmp/cockroach-testserver117729386/listen-url
--- FAIL: Example-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Order (0.040s)
test_driver.go:200: expecting customers from api after creation to be [{0 0x8d4a60}], found []
```
Please assign, take a look and update the issue accordingly. | 1.0 | teamcity: failed tests on master: testrace/TestEndTransactionResolveOnlyLocalIntents, Example-ORMs/TestSQLAlchemy, Example-ORMs/TestSQLAlchemy/FirstRun, Example-ORMs/TestSQLAlchemy/SecondRun, Example-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart, Example-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Products, Example-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Customers, Example-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Order - The following tests appear to have failed:
[#278257](https://teamcity.cockroachdb.com/viewLog.html?buildId=278257):
```
--- FAIL: testrace/TestEndTransactionResolveOnlyLocalIntents (0.070s)
replica_test.go:3902: heartbeat for transaction "test" id=c9b405a9 key="a" rw=false pri=0.00247792 iso=SERIALIZABLE stat=PENDING epo=1 ts=1498100447.919013571,0 orig=1498100447.919013571,0 max=1498100447.919013572,0 wto=false rop=false seq=5 failed; record not present
------- Stdout: -------
I170622 03:00:47.930517 11590 storage/replica_command.go:188 [s1,r2/1:{a -/Max}] test injecting error: boom
--- FAIL: Example-ORMs/TestSQLAlchemy (184.260s)
null
--- FAIL: Example-ORMs/TestSQLAlchemy/FirstRun (180.800s)
main_test.go:160: Get http://localhost:6543/ping: dial tcp [::1]:6543: getsockopt: connection refused
--- FAIL: Example-ORMs/TestSQLAlchemy/SecondRun (1.800s)
null
--- FAIL: Example-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart (0.000s)
null
--- FAIL: Example-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Products (0.040s)
test_driver.go:200: expecting customers from api after creation to be [{0 0x8d4a60}], found []
--- FAIL: Example-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Customers (0.040s)
test_driver.go:200: expecting customers from api after creation to be [{0 0x8d4a60}], found []
------- Stderr: -------
2017/06/22 03:04:26 process 13970 started: ../cockroach start --logtostderr --insecure --host=localhost --port=0 --http-port=0 --store=/tmp/cockroach-testserver117729386 --listening-url-file=/tmp/cockroach-testserver117729386/listen-url
--- FAIL: Example-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Order (0.040s)
test_driver.go:200: expecting customers from api after creation to be [{0 0x8d4a60}], found []
```
Please assign, take a look and update the issue accordingly. | test | teamcity failed tests on master testrace testendtransactionresolveonlylocalintents example orms testsqlalchemy example orms testsqlalchemy firstrun example orms testsqlalchemy secondrun example orms testsqlalchemy secondrun retrievefromapiafterrestart example orms testsqlalchemy secondrun retrievefromapiafterrestart products example orms testsqlalchemy secondrun retrievefromapiafterrestart customers example orms testsqlalchemy secondrun retrievefromapiafterrestart order the following tests appear to have failed fail testrace testendtransactionresolveonlylocalintents replica test go heartbeat for transaction test id key a rw false pri iso serializable stat pending epo ts orig max wto false rop false seq failed record not present stdout storage replica command go test injecting error boom fail example orms testsqlalchemy null fail example orms testsqlalchemy firstrun main test go get dial tcp getsockopt connection refused fail example orms testsqlalchemy secondrun null fail example orms testsqlalchemy secondrun retrievefromapiafterrestart null fail example orms testsqlalchemy secondrun retrievefromapiafterrestart products test driver go expecting customers from api after creation to be found fail example orms testsqlalchemy secondrun retrievefromapiafterrestart customers test driver go expecting customers from api after creation to be found stderr process started cockroach start logtostderr insecure host localhost port http port store tmp cockroach listening url file tmp cockroach listen url fail example orms testsqlalchemy secondrun retrievefromapiafterrestart order test driver go expecting customers from api after creation to be found please assign take a look and update the issue accordingly | 1 |
273,869 | 8,554,163,713 | IssuesEvent | 2018-11-08 04:42:44 | CS2103-AY1819S1-T13-4/main | https://api.github.com/repos/CS2103-AY1819S1-T13-4/main | closed | Clear command not implemented | priority.Medium severity.Medium type.Bug | 3.6 under the user guide states that the CAP Tracker has a clear command. Currently, I cannot find its implementation. | 1.0 | Clear command not implemented - 3.6 under the user guide states that the CAP Tracker has a clear command. Currently, I cannot find its implementation. | non_test | clear command not implemented under the user guide states that the cap tracker has a clear command currently i cannot find its implementation | 0 |
338,117 | 30,281,714,812 | IssuesEvent | 2023-07-08 06:17:18 | infinitest/infinitest | https://api.github.com/repos/infinitest/infinitest | closed | [infinitest-eclipse] Slow test warning not removed when test ignored | type: bug comp:infinitest-eclipse | I have infinitest installed in Eclipse (Spring Tool Suite - Eclipse Kepler SR2 (4.3.2)). If I write a JUnit test that includes the "timeout" element in @Test that deliberately exceeds the timeout, infinitest creates a Slow Test Warning and Test Failure as expected. If I then @Ignore the test, infinitest removes the Test Failure but not the Slow Test Warning.
Is this expected behaviour? I would expect no warnings or failures for a test that is marked as @Ignored.
| 1.0 | [infinitest-eclipse] Slow test warning not removed when test ignored - I have infinitest installed in Eclipse (Spring Tool Suite - Eclipse Kepler SR2 (4.3.2)). If I write a JUnit test that includes the "timeout" element in @Test that deliberately exceeds the timeout, infinitest creates a Slow Test Warning and Test Failure as expected. If I then @Ignore the test, infinitest removes the Test Failure but not the Slow Test Warning.
Is this expected behaviour? I would expect no warnings or failures for a test that is marked as @Ignored.
| test | slow test warning not removed when test ignored i have infinitest installed in eclipse spring tool suite eclipse kepler if i write a junit test that includes the timeout element in test that deliberately exceeds the timeout infinitest creates a slow test warning and test failure as expected if i then ignore the test infinitest removes the test failure but not the slow test warning is this expected behaviour i would expect no warnings or failures for a test that is marked as ignored | 1 |
152,449 | 12,109,244,125 | IssuesEvent | 2020-04-21 08:26:49 | NLCR/registrdigitalizace | https://api.github.com/repos/NLCR/registrdigitalizace | closed | Doplnit číslo vydání do zobrazení bibliografického záznamu v seznamu výsledků vyhledávání | Aplikace - Importní program Aplikace - Relief Aplikace - Vyhledávání Pripraveno k testovani Size L enhancement | Jedná se o MARC pole 250 podpole a
Je to potřeba v případech, kdy v daném roce vyšlo více vydání. | 1.0 | Doplnit číslo vydání do zobrazení bibliografického záznamu v seznamu výsledků vyhledávání - Jedná se o MARC pole 250 podpole a
Je to potřeba v případech, kdy v daném roce vyšlo více vydání. | test | doplnit číslo vydání do zobrazení bibliografického záznamu v seznamu výsledků vyhledávání jedná se o marc pole podpole a je to potřeba v případech kdy v daném roce vyšlo více vydání | 1 |
440,200 | 12,695,376,487 | IssuesEvent | 2020-06-22 08:19:08 | zeebe-io/zeebe | https://api.github.com/repos/zeebe-io/zeebe | closed | Add documentation about long polling feature flag | Priority: High Scope: gateway Severity: Low Status: Needs Review Type: Docs | **Description**
After #4660 was merged, I noticed we did not append the documentation about long polling with information about disabling this feature altogether. I think that the [job workers - long polling](https://docs.zeebe.io/basics/job-workers.html#long-polling) paragraph should have additional info about its configuration. | 1.0 | Add documentation about long polling feature flag - **Description**
After #4660 was merged, I noticed we did not append the documentation about long polling with information about disabling this feature altogether. I think that the [job workers - long polling](https://docs.zeebe.io/basics/job-workers.html#long-polling) paragraph should have additional info about its configuration. | non_test | add documentation about long polling feature flag description after was merged i noticed we did not append the documentation about long polling with information about disabling this feature altogether i think that the paragraph should have additional info about its configuration | 0 |
297,259 | 25,714,894,913 | IssuesEvent | 2022-12-07 09:38:37 | apache/camel-k | https://api.github.com/repos/apache/camel-k | closed | E2E - Prometheus trait tests started to fail constantly after #3875 | area/test | It seems the Prometheus trait tests constantly fail due to #3875.
https://github.com/apache/camel-k/actions/runs/3618428819/jobs/6098274907
```
❌ TestPrometheusTrait (4m21.63s)
OLM is not available in the cluster. Fallback to regular installation.
Warning: the operator won't be able to detect a local image registry via KEP-1755
Camel K installed in namespace test-4877bb87-8db7-40b8-b110-a02826105dbf
prometheus_test.go:57:
Timed out after 60.005s.
Expected
<v1.ConditionStatus>: Unknown
to equal
<v1.ConditionStatus>: True
```
We should either fix the e2e tests or revert the commit.
^^ @squakez @vitorz | 1.0 | E2E - Prometheus trait tests started to fail constantly after #3875 - It seems the Prometheus trait tests constantly fail due to #3875.
https://github.com/apache/camel-k/actions/runs/3618428819/jobs/6098274907
```
❌ TestPrometheusTrait (4m21.63s)
OLM is not available in the cluster. Fallback to regular installation.
Warning: the operator won't be able to detect a local image registry via KEP-1755
Camel K installed in namespace test-4877bb87-8db7-40b8-b110-a02826105dbf
prometheus_test.go:57:
Timed out after 60.005s.
Expected
<v1.ConditionStatus>: Unknown
to equal
<v1.ConditionStatus>: True
```
We should either fix the e2e tests or revert the commit.
^^ @squakez @vitorz | test | prometheus trait tests started to fail constantly after it seems the prometheus trait tests constantly fail due to ❌ testprometheustrait olm is not available in the cluster fallback to regular installation warning the operator won t be able to detect a local image registry via kep camel k installed in namespace test prometheus test go timed out after expected unknown to equal true we should either fix the tests or revert the commit squakez vitorz | 1 |
245,604 | 20,780,991,417 | IssuesEvent | 2022-03-16 14:46:05 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | roachtest: asyncpg failed | C-test-failure O-robot O-roachtest branch-master T-sql-experience GA-blocker | roachtest.asyncpg [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=4368530&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=4368530&tab=artifacts#/asyncpg) on master @ [bbb473c8f304ac20fec51ff0a0d04e128383bcf6](https://github.com/cockroachdb/cockroach/commits/bbb473c8f304ac20fec51ff0a0d04e128383bcf6):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /artifacts/asyncpg/run_1
orm_helpers.go:191,orm_helpers.go:117,asyncpg.go:130,asyncpg.go:141,test_runner.go:779:
Tests run on Cockroach v22.1.0-alpha.1-1226-gbbb473c8f3
Tests run against asyncpg v0.24.0
134 Total Tests Run
126 tests passed
8 tests failed
34 tests skipped
96 tests ignored
0 tests passed unexpectedly
8 tests failed unexpectedly
0 tests expected failed but skipped
0 tests expected failed but not run
---
--- FAIL: test_transaction.TestTransaction.test_transaction_interface_errors (unexpected)
--- FAIL: test_transaction.TestTransaction.test_transaction_regular (unexpected)
--- FAIL: test_transaction.TestTransaction.test_transaction_nested (unexpected)
--- FAIL: test_timeout.TestTimeoutCoversPrepare.test_timeout_covers_prepare_01 (unexpected)
--- FAIL: test_transaction.TestTransaction.test_nested_isolation_level (unexpected)
--- FAIL: test_transaction.TestTransaction.test_transaction_within_manual_transaction (unexpected)
--- FAIL: test_transaction.TestTransaction.test_isolation_level (unexpected)
--- FAIL: test_timeout.TestTimeout.test_timeout_05 (unexpected)
For a full summary look at the asyncpg artifacts
An updated blocklist (asyncpgBlocklist22_1) is available in the artifacts' asyncpg log
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/sql-experience
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*asyncpg.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-13147 | 2.0 | roachtest: asyncpg failed - roachtest.asyncpg [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=4368530&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=4368530&tab=artifacts#/asyncpg) on master @ [bbb473c8f304ac20fec51ff0a0d04e128383bcf6](https://github.com/cockroachdb/cockroach/commits/bbb473c8f304ac20fec51ff0a0d04e128383bcf6):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /artifacts/asyncpg/run_1
orm_helpers.go:191,orm_helpers.go:117,asyncpg.go:130,asyncpg.go:141,test_runner.go:779:
Tests run on Cockroach v22.1.0-alpha.1-1226-gbbb473c8f3
Tests run against asyncpg v0.24.0
134 Total Tests Run
126 tests passed
8 tests failed
34 tests skipped
96 tests ignored
0 tests passed unexpectedly
8 tests failed unexpectedly
0 tests expected failed but skipped
0 tests expected failed but not run
---
--- FAIL: test_transaction.TestTransaction.test_transaction_interface_errors (unexpected)
--- FAIL: test_transaction.TestTransaction.test_transaction_regular (unexpected)
--- FAIL: test_transaction.TestTransaction.test_transaction_nested (unexpected)
--- FAIL: test_timeout.TestTimeoutCoversPrepare.test_timeout_covers_prepare_01 (unexpected)
--- FAIL: test_transaction.TestTransaction.test_nested_isolation_level (unexpected)
--- FAIL: test_transaction.TestTransaction.test_transaction_within_manual_transaction (unexpected)
--- FAIL: test_transaction.TestTransaction.test_isolation_level (unexpected)
--- FAIL: test_timeout.TestTimeout.test_timeout_05 (unexpected)
For a full summary look at the asyncpg artifacts
An updated blocklist (asyncpgBlocklist22_1) is available in the artifacts' asyncpg log
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/sql-experience
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*asyncpg.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-13147 | test | roachtest asyncpg failed roachtest asyncpg with on master the test failed on branch master cloud gce test artifacts and logs in artifacts asyncpg run orm helpers go orm helpers go asyncpg go asyncpg go test runner go tests run on cockroach alpha tests run against asyncpg total tests run tests passed tests failed tests skipped tests ignored tests passed unexpectedly tests failed unexpectedly tests expected failed but skipped tests expected failed but not run fail test transaction testtransaction test transaction interface errors unexpected fail test transaction testtransaction test transaction regular unexpected fail test transaction testtransaction test transaction nested unexpected fail test timeout testtimeoutcoversprepare test timeout covers prepare unexpected fail test transaction testtransaction test nested isolation level unexpected fail test transaction testtransaction test transaction within manual transaction unexpected fail test transaction testtransaction test isolation level unexpected fail test timeout testtimeout test timeout unexpected for a full summary look at the asyncpg artifacts an updated blocklist is available in the artifacts asyncpg log help see see cc cockroachdb sql experience jira issue crdb | 1 |
214,387 | 16,584,308,090 | IssuesEvent | 2021-05-31 16:09:49 | italia/anpr | https://api.github.com/repos/italia/anpr | closed | Errore EN179 su richiesta elenchi | Bug in Test | Buonasera,
inserendo una richiesta per servizio 4001 rientra subito l'errore EN179 sebbene non ci siano operazioni in sospeso.
Comune di Cansano
Halley Informatica
Arditi Alessandro
Risposta
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<a:Risposta4001 xmlns:a="http://sogei.it/ANPR/4000estrazione">
<a:rispostaKO>
<testataRisposta>
<idOperazioneComune>20210531171117943</idOperazioneComune>
<codMittente>067009</codMittente>
<codDestinatario>ANPR02</codDestinatario>
<operazioneRichiesta>4001</operazioneRichiesta>
<dataOraRichiesta>2021-05-31T17:11:17</dataOraRichiesta>
<idOperazioneANPR>545557499</idOperazioneANPR>
<esitoOperazione>XXXX</esitoOperazione>
</testataRisposta>
<listaErrori>
<errore>
<codiceErroreAnomalia>EN179</codiceErroreAnomalia>
<tipoErroreAnomalia>E</tipoErroreAnomalia>
<testoErroreAnomalia>Richiesta non effettuabile: e' presente una richiesta dello stesso tipo non ancora lavorata
</testoErroreAnomalia>
</errore>
</listaErrori>
</a:rispostaKO>
</a:Risposta4001>
</soapenv:Body>
</soapenv:Envelope>
| 1.0 | Errore EN179 su richiesta elenchi - Buonasera,
inserendo una richiesta per servizio 4001 rientra subito l'errore EN179 sebbene non ci siano operazioni in sospeso.
Comune di Cansano
Halley Informatica
Arditi Alessandro
Risposta
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<a:Risposta4001 xmlns:a="http://sogei.it/ANPR/4000estrazione">
<a:rispostaKO>
<testataRisposta>
<idOperazioneComune>20210531171117943</idOperazioneComune>
<codMittente>067009</codMittente>
<codDestinatario>ANPR02</codDestinatario>
<operazioneRichiesta>4001</operazioneRichiesta>
<dataOraRichiesta>2021-05-31T17:11:17</dataOraRichiesta>
<idOperazioneANPR>545557499</idOperazioneANPR>
<esitoOperazione>XXXX</esitoOperazione>
</testataRisposta>
<listaErrori>
<errore>
<codiceErroreAnomalia>EN179</codiceErroreAnomalia>
<tipoErroreAnomalia>E</tipoErroreAnomalia>
<testoErroreAnomalia>Richiesta non effettuabile: e' presente una richiesta dello stesso tipo non ancora lavorata
</testoErroreAnomalia>
</errore>
</listaErrori>
</a:rispostaKO>
</a:Risposta4001>
</soapenv:Body>
</soapenv:Envelope>
| test | errore su richiesta elenchi buonasera inserendo una richiesta per servizio rientra subito l errore sebbene non ci siano operazioni in sospeso comune di cansano halley informatica arditi alessandro risposta soapenv envelope xmlns soapenv a xmlns a xxxx e richiesta non effettuabile e presente una richiesta dello stesso tipo non ancora lavorata | 1 |
111,742 | 9,540,260,698 | IssuesEvent | 2019-04-30 19:03:21 | Microsoft/WindowsTemplateStudio | https://api.github.com/repos/Microsoft/WindowsTemplateStudio | closed | Add UI Testing for generated MenuBar apps | Can Close Out Soon Testing | Add language & framework `VisualComparisonTests`.
X-Ref #2292 & #2999 | 1.0 | Add UI Testing for generated MenuBar apps - Add language & framework `VisualComparisonTests`.
X-Ref #2292 & #2999 | test | add ui testing for generated menubar apps add language framework visualcomparisontests x ref | 1 |
46,511 | 13,172,604,371 | IssuesEvent | 2020-08-11 18:44:30 | uniquelyparticular/zendesk-magento-m1-request | https://api.github.com/repos/uniquelyparticular/zendesk-magento-m1-request | opened | CVE-2020-15366 (Medium) detected in ajv-5.5.2.tgz | security vulnerability | ## CVE-2020-15366 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ajv-5.5.2.tgz</b></p></summary>
<p>Another JSON Schema Validator</p>
<p>Library home page: <a href="https://registry.npmjs.org/ajv/-/ajv-5.5.2.tgz">https://registry.npmjs.org/ajv/-/ajv-5.5.2.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/zendesk-magento-m1-request/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/zendesk-magento-m1-request/node_modules/npm/node_modules/ajv/package.json</p>
<p>
Dependency Hierarchy:
- semantic-release-17.1.1.tgz (Root Library)
- npm-7.0.5.tgz
- npm-6.14.7.tgz
- request-2.88.0.tgz
- har-validator-5.1.0.tgz
- :x: **ajv-5.5.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/uniquelyparticular/zendesk-magento-m1-request/commit/d4980c01dc84d3fed40d92f36f4b1637315dadd7">d4980c01dc84d3fed40d92f36f4b1637315dadd7</a></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>
An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)
<p>Publish Date: 2020-07-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15366>CVE-2020-15366</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.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</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/ajv-validator/ajv/releases/tag/v6.12.3">https://github.com/ajv-validator/ajv/releases/tag/v6.12.3</a></p>
<p>Release Date: 2020-07-15</p>
<p>Fix Resolution: ajv - 6.12.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-2020-15366 (Medium) detected in ajv-5.5.2.tgz - ## CVE-2020-15366 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ajv-5.5.2.tgz</b></p></summary>
<p>Another JSON Schema Validator</p>
<p>Library home page: <a href="https://registry.npmjs.org/ajv/-/ajv-5.5.2.tgz">https://registry.npmjs.org/ajv/-/ajv-5.5.2.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/zendesk-magento-m1-request/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/zendesk-magento-m1-request/node_modules/npm/node_modules/ajv/package.json</p>
<p>
Dependency Hierarchy:
- semantic-release-17.1.1.tgz (Root Library)
- npm-7.0.5.tgz
- npm-6.14.7.tgz
- request-2.88.0.tgz
- har-validator-5.1.0.tgz
- :x: **ajv-5.5.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/uniquelyparticular/zendesk-magento-m1-request/commit/d4980c01dc84d3fed40d92f36f4b1637315dadd7">d4980c01dc84d3fed40d92f36f4b1637315dadd7</a></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>
An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)
<p>Publish Date: 2020-07-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15366>CVE-2020-15366</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.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</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/ajv-validator/ajv/releases/tag/v6.12.3">https://github.com/ajv-validator/ajv/releases/tag/v6.12.3</a></p>
<p>Release Date: 2020-07-15</p>
<p>Fix Resolution: ajv - 6.12.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_test | cve medium detected in ajv tgz cve medium severity vulnerability vulnerable library ajv tgz another json schema validator library home page a href path to dependency file tmp ws scm zendesk magento request package json path to vulnerable library tmp ws scm zendesk magento request node modules npm node modules ajv package json dependency hierarchy semantic release tgz root library npm tgz npm tgz request tgz har validator tgz x ajv tgz vulnerable library found in head commit a href vulnerability details an issue was discovered in ajv validate in ajv aka another json schema validator a carefully crafted json schema could be provided that allows execution of other code by prototype pollution while untrusted schemas are recommended against the worst case of an untrusted schema should be a denial of service not execution of code publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution ajv step up your open source security game with whitesource | 0 |
261,988 | 27,836,559,344 | IssuesEvent | 2023-03-20 09:53:51 | prombouts/SSLChecker | https://api.github.com/repos/prombouts/SSLChecker | closed | CVE-2017-0256 (Medium) detected in system.net.http.4.3.0.nupkg - autoclosed | Mend: dependency security vulnerability | ## CVE-2017-0256 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>system.net.http.4.3.0.nupkg</b></p></summary>
<p>Provides a programming interface for modern HTTP applications, including HTTP client components that...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/system.net.http.4.3.0.nupkg">https://api.nuget.org/packages/system.net.http.4.3.0.nupkg</a></p>
<p>Path to dependency file: /SslChecker/SslChecker/SslChecker.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/system.net.http/4.3.0/system.net.http.4.3.0.nupkg</p>
<p>
Dependency Hierarchy:
- microsoft.azure.webjobs.extensions.openapi.1.4.0.nupkg (Root Library)
- microsoft.azure.webjobs.extensions.openapi.core.1.4.0.nupkg
- microsoft.azure.webjobs.extensions.http.3.2.0.nupkg
- microsoft.aspnet.webapi.client.5.2.8.nupkg
- newtonsoft.json.bson.1.0.1.nupkg
- netstandard.library.1.6.1.nupkg
- :x: **system.net.http.4.3.0.nupkg** (Vulnerable Library)
<p>Found in base branch: <b>main</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>
A spoofing vulnerability exists when the ASP.NET Core fails to properly sanitize web requests.
<p>Publish Date: 2017-05-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-0256>CVE-2017-0256</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.3</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: Low
- 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://nvd.nist.gov/vuln/detail/CVE-2017-0256">https://nvd.nist.gov/vuln/detail/CVE-2017-0256</a></p>
<p>Release Date: 2017-05-12</p>
<p>Fix Resolution: Microsoft.AspNetCore.Mvc.ApiExplorer - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.Abstractions - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.Core - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Cors - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Localization - 1.1.3,1.0.4;System.Net.Http - 4.1.2,4.3.2;Microsoft.AspNetCore.Mvc.Razor - 1.1.3,1.0.4;System.Net.Http.WinHttpHandler - 4.0.2,4.3.0-preview1-24530-04;System.Net.Security - 4.3.0-preview1-24530-04,4.0.1;Microsoft.AspNetCore.Mvc.ViewFeatures - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.TagHelpers - 1.0.4,1.1.3;System.Text.Encodings.Web - 4.3.0-preview1-24530-04,4.0.1;Microsoft.AspNetCore.Mvc.Razor.Host - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.Formatters.Json - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.WebApiCompatShim - 1.0.4,1.1.3;System.Net.WebSockets.Client - 4.3.0-preview1-24530-04,4.0.1;Microsoft.AspNetCore.Mvc.Formatters.Xml - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.DataAnnotations - 1.0.4,1.1.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2017-0256 (Medium) detected in system.net.http.4.3.0.nupkg - autoclosed - ## CVE-2017-0256 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>system.net.http.4.3.0.nupkg</b></p></summary>
<p>Provides a programming interface for modern HTTP applications, including HTTP client components that...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/system.net.http.4.3.0.nupkg">https://api.nuget.org/packages/system.net.http.4.3.0.nupkg</a></p>
<p>Path to dependency file: /SslChecker/SslChecker/SslChecker.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/system.net.http/4.3.0/system.net.http.4.3.0.nupkg</p>
<p>
Dependency Hierarchy:
- microsoft.azure.webjobs.extensions.openapi.1.4.0.nupkg (Root Library)
- microsoft.azure.webjobs.extensions.openapi.core.1.4.0.nupkg
- microsoft.azure.webjobs.extensions.http.3.2.0.nupkg
- microsoft.aspnet.webapi.client.5.2.8.nupkg
- newtonsoft.json.bson.1.0.1.nupkg
- netstandard.library.1.6.1.nupkg
- :x: **system.net.http.4.3.0.nupkg** (Vulnerable Library)
<p>Found in base branch: <b>main</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>
A spoofing vulnerability exists when the ASP.NET Core fails to properly sanitize web requests.
<p>Publish Date: 2017-05-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-0256>CVE-2017-0256</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.3</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: Low
- 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://nvd.nist.gov/vuln/detail/CVE-2017-0256">https://nvd.nist.gov/vuln/detail/CVE-2017-0256</a></p>
<p>Release Date: 2017-05-12</p>
<p>Fix Resolution: Microsoft.AspNetCore.Mvc.ApiExplorer - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.Abstractions - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.Core - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Cors - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Localization - 1.1.3,1.0.4;System.Net.Http - 4.1.2,4.3.2;Microsoft.AspNetCore.Mvc.Razor - 1.1.3,1.0.4;System.Net.Http.WinHttpHandler - 4.0.2,4.3.0-preview1-24530-04;System.Net.Security - 4.3.0-preview1-24530-04,4.0.1;Microsoft.AspNetCore.Mvc.ViewFeatures - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.TagHelpers - 1.0.4,1.1.3;System.Text.Encodings.Web - 4.3.0-preview1-24530-04,4.0.1;Microsoft.AspNetCore.Mvc.Razor.Host - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.Formatters.Json - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.WebApiCompatShim - 1.0.4,1.1.3;System.Net.WebSockets.Client - 4.3.0-preview1-24530-04,4.0.1;Microsoft.AspNetCore.Mvc.Formatters.Xml - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.DataAnnotations - 1.0.4,1.1.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve medium detected in system net http nupkg autoclosed cve medium severity vulnerability vulnerable library system net http nupkg provides a programming interface for modern http applications including http client components that library home page a href path to dependency file sslchecker sslchecker sslchecker csproj path to vulnerable library home wss scanner nuget packages system net http system net http nupkg dependency hierarchy microsoft azure webjobs extensions openapi nupkg root library microsoft azure webjobs extensions openapi core nupkg microsoft azure webjobs extensions http nupkg microsoft aspnet webapi client nupkg newtonsoft json bson nupkg netstandard library nupkg x system net http nupkg vulnerable library found in base branch main vulnerability details a spoofing vulnerability exists when the asp net core fails to properly sanitize web requests 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 low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution microsoft aspnetcore mvc apiexplorer microsoft aspnetcore mvc abstractions microsoft aspnetcore mvc core microsoft aspnetcore mvc cors microsoft aspnetcore mvc localization system net http microsoft aspnetcore mvc razor system net http winhttphandler system net security microsoft aspnetcore mvc viewfeatures microsoft aspnetcore mvc taghelpers system text encodings web microsoft aspnetcore mvc razor host microsoft aspnetcore mvc formatters json microsoft aspnetcore mvc webapicompatshim system net websockets client microsoft aspnetcore mvc formatters xml microsoft aspnetcore mvc dataannotations step up your open source security game with mend | 0 |
313,544 | 26,935,449,936 | IssuesEvent | 2023-02-07 20:14:20 | hashicorp/terraform-provider-google | https://api.github.com/repos/hashicorp/terraform-provider-google | closed | Failing test(s): Os Policy Assignment: operation not done | size/xs test failure tpgtools | ### Affected Resource(s)
<!--- Please list the affected resources and data sources. --->
* google_os_config_os_policy_assignment
<!--- This is a template for reporting test failures on nightly builds. It should only be used by core contributors who have access to our CI/CD results. --->
<!-- i.e. "Consistently since X date" or "X% failure in MONTH" -->
Failure rate:
- ~0.6% in Jan 2022
- 55.6% in Feb 2022
<!-- List all impacted tests for searchability. The title of the issue can instead list one or more groups of tests, or describe the overall root cause. -->
Impacted tests:
- TestAccOsConfigOsPolicyAssignment_FixedOsPolicyAssignment
- TestAccOsConfigOsPolicyAssignment_PercentOsPolicyAssignment
<!-- Link to the nightly build(s), ideally with one impacted test opened -->
Nightly builds:
- https://ci-oss.hashicorp.engineering/buildConfiguration/GoogleCloud_ProviderGoogleCloudGoogleProject/254727?buildTab=tests&expandedTest=7114228571965012755
<!-- The error message that displays in the tests tab, for reference -->
Message:
```
Error: Error updating OSPolicyAssignment: operation not done.
```
| 1.0 | Failing test(s): Os Policy Assignment: operation not done - ### Affected Resource(s)
<!--- Please list the affected resources and data sources. --->
* google_os_config_os_policy_assignment
<!--- This is a template for reporting test failures on nightly builds. It should only be used by core contributors who have access to our CI/CD results. --->
<!-- i.e. "Consistently since X date" or "X% failure in MONTH" -->
Failure rate:
- ~0.6% in Jan 2022
- 55.6% in Feb 2022
<!-- List all impacted tests for searchability. The title of the issue can instead list one or more groups of tests, or describe the overall root cause. -->
Impacted tests:
- TestAccOsConfigOsPolicyAssignment_FixedOsPolicyAssignment
- TestAccOsConfigOsPolicyAssignment_PercentOsPolicyAssignment
<!-- Link to the nightly build(s), ideally with one impacted test opened -->
Nightly builds:
- https://ci-oss.hashicorp.engineering/buildConfiguration/GoogleCloud_ProviderGoogleCloudGoogleProject/254727?buildTab=tests&expandedTest=7114228571965012755
<!-- The error message that displays in the tests tab, for reference -->
Message:
```
Error: Error updating OSPolicyAssignment: operation not done.
```
| test | failing test s os policy assignment operation not done affected resource s google os config os policy assignment failure rate in jan in feb impacted tests testaccosconfigospolicyassignment fixedospolicyassignment testaccosconfigospolicyassignment percentospolicyassignment nightly builds message error error updating ospolicyassignment operation not done | 1 |
222,359 | 17,408,827,071 | IssuesEvent | 2021-08-03 09:36:50 | mennaelkashef/eShop | https://api.github.com/repos/mennaelkashef/eShop | opened | Test Charles Test | DOES-NOT-CONTAIN-STRING Hello! RULE-GOT-APPLIED Rule-works-on-convert-to-bug instabug test | # :clipboard: Bug Details
>Test Charles Test
key | value
--|--
Reported At | 2021-08-03 09:35:57 UTC
Email | Charles@test.com
Categories | Report a bug, Cat 2
Tags | test, Hello!, RULE-GOT-APPLIED, DOES-NOT-CONTAIN-STRING, Rule-works-on-convert-to-bug, instabug
App Version | 1.0-kotlin (1)
Session Duration | 167
Device | Google sdk_gphone64_arm64, OS Level 31
Display | 1080x2220 (xhdpi)
Location | Giza, Egypt (en)
## :point_right: [View Full Bug Report on Instabug](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7970?utm_source=github&utm_medium=integrations) :point_left:
___
# :chart_with_downwards_trend: Session Profiler
Here is what the app was doing right before the bug was reported:
Key | Value
--|--
Used Memory | 65.9% - 1.27/1.92 GB
Used Storage | 86.6% - 0.65/0.76 GB
Connectivity | Cellular
Battery | 100% - unplugged
Orientation | portrait
Find all the changes that happened in the parameters mentioned above during the last 60 seconds before the bug was reported here: :point_right: **[View Full Session Profiler](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7970?show-session-profiler=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :bust_in_silhouette: User Info
### User Attributes
```
key_name 996392388: 438aa70f0b88f76518461a52f7da1c0b
```
___
# :mag_right: Logs
### User Steps
Here are the last 10 steps done by the user right before the bug was reported:
```
09:33:12 com.example.app.splash.SplashActivity was stopped.
09:33:12 com.example.app.splash.SplashActivity was destroyed.
09:33:21 com.example.app.main.MainActivity was paused.
09:33:21 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was paused.
09:33:25 com.example.app.main.MainActivity was resumed.
09:35:51 Tap in "Sdk version: 10..." of type "androidx.appcompat.widget.AppCompatTextView" in "com.example.app.main.MainActivity"
09:35:51 com.example.app.main.MainActivity was paused.
09:35:51 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was paused.
09:35:53 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
09:35:57 Long press in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
```
Find all the user steps done by the user throughout the session here: :point_right: **[View All User Steps](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7970?show-logs=user_steps&utm_source=github&utm_medium=integrations)** :point_left:
### Console Log
Here are the last 10 console logs logged right before the bug was reported:
```
09:36:28 D/EGL_emulation( 8014): app_time_stats: avg=499.79ms min=494.51ms max=502.74ms count=3
09:36:29 D/EGL_emulation( 8014): app_time_stats: avg=499.66ms min=494.02ms max=504.87ms count=3
09:36:30 D/EGL_emulation( 8014): app_time_stats: avg=508.06ms min=498.88ms max=517.25ms count=2
09:36:32 D/EGL_emulation( 8014): app_time_stats: avg=497.81ms min=495.10ms max=500.90ms count=3
09:36:33 D/EGL_emulation( 8014): app_time_stats: avg=502.74ms min=500.15ms max=505.34ms count=2
09:36:34 D/EGL_emulation( 8014): app_time_stats: avg=504.71ms min=498.90ms max=515.37ms count=3
09:36:35 D/EGL_emulation( 8014): app_time_stats: avg=500.02ms min=499.36ms max=500.68ms count=2
09:36:36 D/EGL_emulation( 8014): app_time_stats: avg=499.72ms min=498.22ms max=501.23ms count=2
09:36:38 D/EGL_emulation( 8014): app_time_stats: avg=499.30ms min=495.45ms max=502.27ms count=3
09:36:39 D/EGL_emulation( 8014): app_time_stats: avg=508.73ms min=499.91ms max=517.55ms count=2
```
Find all the logged console logs throughout the session here: :point_right: **[View All Console Log](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7970?show-logs=console_log&utm_source=github&utm_medium=integrations)** :point_left:
___
# :camera: Images
[](https://d38gnqwzxziyyy.cloudfront.net/attachments/bugs/16427092/28fc7f3e352aad56454dd27615ac3918_original/22245949/bug_1627983351464_.jpg?Expires=4783657009&Signature=CxW3hY7FT3h1JOmQMIwpGb9HSczMqiTeKxDrjglrnSq~U3~FVlgtc1dt4hy6ct2INrnvutYLnFeWZqOa~dffssUKwpDUT2DiTzNhPmI8IiM9G1z1w5KxBNkmJS-g-pbzfNcLLYhe331~mnkalM9e6kYCITXUaqZBdVZSfYz0eipqctlG3Dw~PI1IgZMgturGd-Y3mr1TjBgA1vdQPErQjgoqji9ZqRb~qTQ5qpABPT4GAr5lKEUySkIZQbvGG93vZut6kwH-VMtWsLl0IMxA1UgH8uYSBEBIBKzMva~HGX0g4BqsMPtA8Nj6vF0yhoQdHnxXK7XMXjVc0hNjGb4hEw__&Key-Pair-Id=APKAIXAG65U6UUX7JAQQ)
___
# :warning: Looking for More Details?
1. **Network Log**: we are unable to capture your network requests automatically. If you are using HttpUrlConnection or Okhttp requests, [**check the details mentioned here**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations#section-network-logs).
2. **User Events**: start capturing custom User Events to send them along with each report. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations).
3. **Instabug Log**: start adding Instabug logs to see them right inside each report you receive. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations). | 1.0 | Test Charles Test - # :clipboard: Bug Details
>Test Charles Test
key | value
--|--
Reported At | 2021-08-03 09:35:57 UTC
Email | Charles@test.com
Categories | Report a bug, Cat 2
Tags | test, Hello!, RULE-GOT-APPLIED, DOES-NOT-CONTAIN-STRING, Rule-works-on-convert-to-bug, instabug
App Version | 1.0-kotlin (1)
Session Duration | 167
Device | Google sdk_gphone64_arm64, OS Level 31
Display | 1080x2220 (xhdpi)
Location | Giza, Egypt (en)
## :point_right: [View Full Bug Report on Instabug](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7970?utm_source=github&utm_medium=integrations) :point_left:
___
# :chart_with_downwards_trend: Session Profiler
Here is what the app was doing right before the bug was reported:
Key | Value
--|--
Used Memory | 65.9% - 1.27/1.92 GB
Used Storage | 86.6% - 0.65/0.76 GB
Connectivity | Cellular
Battery | 100% - unplugged
Orientation | portrait
Find all the changes that happened in the parameters mentioned above during the last 60 seconds before the bug was reported here: :point_right: **[View Full Session Profiler](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7970?show-session-profiler=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :bust_in_silhouette: User Info
### User Attributes
```
key_name 996392388: 438aa70f0b88f76518461a52f7da1c0b
```
___
# :mag_right: Logs
### User Steps
Here are the last 10 steps done by the user right before the bug was reported:
```
09:33:12 com.example.app.splash.SplashActivity was stopped.
09:33:12 com.example.app.splash.SplashActivity was destroyed.
09:33:21 com.example.app.main.MainActivity was paused.
09:33:21 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was paused.
09:33:25 com.example.app.main.MainActivity was resumed.
09:35:51 Tap in "Sdk version: 10..." of type "androidx.appcompat.widget.AppCompatTextView" in "com.example.app.main.MainActivity"
09:35:51 com.example.app.main.MainActivity was paused.
09:35:51 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was paused.
09:35:53 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
09:35:57 Long press in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
```
Find all the user steps done by the user throughout the session here: :point_right: **[View All User Steps](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7970?show-logs=user_steps&utm_source=github&utm_medium=integrations)** :point_left:
### Console Log
Here are the last 10 console logs logged right before the bug was reported:
```
09:36:28 D/EGL_emulation( 8014): app_time_stats: avg=499.79ms min=494.51ms max=502.74ms count=3
09:36:29 D/EGL_emulation( 8014): app_time_stats: avg=499.66ms min=494.02ms max=504.87ms count=3
09:36:30 D/EGL_emulation( 8014): app_time_stats: avg=508.06ms min=498.88ms max=517.25ms count=2
09:36:32 D/EGL_emulation( 8014): app_time_stats: avg=497.81ms min=495.10ms max=500.90ms count=3
09:36:33 D/EGL_emulation( 8014): app_time_stats: avg=502.74ms min=500.15ms max=505.34ms count=2
09:36:34 D/EGL_emulation( 8014): app_time_stats: avg=504.71ms min=498.90ms max=515.37ms count=3
09:36:35 D/EGL_emulation( 8014): app_time_stats: avg=500.02ms min=499.36ms max=500.68ms count=2
09:36:36 D/EGL_emulation( 8014): app_time_stats: avg=499.72ms min=498.22ms max=501.23ms count=2
09:36:38 D/EGL_emulation( 8014): app_time_stats: avg=499.30ms min=495.45ms max=502.27ms count=3
09:36:39 D/EGL_emulation( 8014): app_time_stats: avg=508.73ms min=499.91ms max=517.55ms count=2
```
Find all the logged console logs throughout the session here: :point_right: **[View All Console Log](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7970?show-logs=console_log&utm_source=github&utm_medium=integrations)** :point_left:
___
# :camera: Images
[](https://d38gnqwzxziyyy.cloudfront.net/attachments/bugs/16427092/28fc7f3e352aad56454dd27615ac3918_original/22245949/bug_1627983351464_.jpg?Expires=4783657009&Signature=CxW3hY7FT3h1JOmQMIwpGb9HSczMqiTeKxDrjglrnSq~U3~FVlgtc1dt4hy6ct2INrnvutYLnFeWZqOa~dffssUKwpDUT2DiTzNhPmI8IiM9G1z1w5KxBNkmJS-g-pbzfNcLLYhe331~mnkalM9e6kYCITXUaqZBdVZSfYz0eipqctlG3Dw~PI1IgZMgturGd-Y3mr1TjBgA1vdQPErQjgoqji9ZqRb~qTQ5qpABPT4GAr5lKEUySkIZQbvGG93vZut6kwH-VMtWsLl0IMxA1UgH8uYSBEBIBKzMva~HGX0g4BqsMPtA8Nj6vF0yhoQdHnxXK7XMXjVc0hNjGb4hEw__&Key-Pair-Id=APKAIXAG65U6UUX7JAQQ)
___
# :warning: Looking for More Details?
1. **Network Log**: we are unable to capture your network requests automatically. If you are using HttpUrlConnection or Okhttp requests, [**check the details mentioned here**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations#section-network-logs).
2. **User Events**: start capturing custom User Events to send them along with each report. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations).
3. **Instabug Log**: start adding Instabug logs to see them right inside each report you receive. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations). | test | test charles test clipboard bug details test charles test key value reported at utc email charles test com categories report a bug cat tags test hello rule got applied does not contain string rule works on convert to bug instabug app version kotlin session duration device google sdk os level display xhdpi location giza egypt en point right point left chart with downwards trend session profiler here is what the app was doing right before the bug was reported key value used memory gb used storage gb connectivity cellular battery unplugged orientation portrait find all the changes that happened in the parameters mentioned above during the last seconds before the bug was reported here point right point left bust in silhouette user info user attributes key name mag right logs user steps here are the last steps done by the user right before the bug was reported com example app splash splashactivity was stopped com example app splash splashactivity was destroyed com example app main mainactivity was paused in activity com example app main mainactivity fragment com example app main mainfragment was paused com example app main mainactivity was resumed tap in sdk version of type androidx appcompat widget appcompattextview in com example app main mainactivity com example app main mainactivity was paused in activity com example app main mainactivity fragment com example app main mainfragment was paused tap in androidx constraintlayout widget constraintlayout in com example app main mainactivity long press in androidx constraintlayout widget constraintlayout in com example app main mainactivity find all the user steps done by the user throughout the session here point right point left console log here are the last console logs logged right before the bug was reported d egl emulation app time stats avg min max count d egl emulation app time stats avg min max count d egl emulation app time stats avg min max count d egl emulation app time stats avg min max count d egl emulation app time stats avg min max count d egl emulation app time stats avg min max count d egl emulation app time stats avg min max count d egl emulation app time stats avg min max count d egl emulation app time stats avg min max count d egl emulation app time stats avg min max count find all the logged console logs throughout the session here point right point left camera images warning looking for more details network log we are unable to capture your network requests automatically if you are using httpurlconnection or okhttp requests user events start capturing custom user events to send them along with each report instabug log start adding instabug logs to see them right inside each report you receive | 1 |
319,502 | 27,377,102,530 | IssuesEvent | 2023-02-28 07:09:28 | prgrms-web-devcourse/Team-Kkini-Mukvengers-BE | https://api.github.com/repos/prgrms-web-devcourse/Team-Kkini-Mukvengers-BE | opened | 밥 모임원(방장이 아닌)을 생성한다. | 🚀 Feat ✅ Test | ### 🚀 목적
- 방장이 아닌 밥 모임원 생성 기능을 구현한다.
### 🔗 작업
- 모임원 생성 기능, 테스트 추가
### ✅ 완료조건
- 테스트 통과 | 1.0 | 밥 모임원(방장이 아닌)을 생성한다. - ### 🚀 목적
- 방장이 아닌 밥 모임원 생성 기능을 구현한다.
### 🔗 작업
- 모임원 생성 기능, 테스트 추가
### ✅ 완료조건
- 테스트 통과 | test | 밥 모임원 방장이 아닌 을 생성한다 🚀 목적 방장이 아닌 밥 모임원 생성 기능을 구현한다 🔗 작업 모임원 생성 기능 테스트 추가 ✅ 완료조건 테스트 통과 | 1 |
332,134 | 29,185,785,076 | IssuesEvent | 2023-05-19 15:18:53 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | reopened | Fix searching.test_argwhere | Sub Task Failing Test | | | |
|---|---|
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5024818534/jobs/9010978181" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5024818534/jobs/9010978181" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5024818534/jobs/9010978181" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-failure-red></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5024818534/jobs/9010978181" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/4973224096/jobs/8898928777" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
<details>
<summary>FAILED ivy_tests/test_ivy/test_functional/test_core/test_searching.py::test_argwhere[cpu-ivy.functional.backends.numpy-False-False]</summary>
2023-05-19T14:07:47.6358337Z E hypothesis.errors.InvalidArgument: Cannot sample from a length-zero sequence.2023-05-19T14:07:47.6358705Z E 2023-05-19T14:07:47.6359393Z E You can reproduce this example by temporarily adding @reproduce_failure('6.75.3', b'AAAA') as a decorator on your test case
</details>
| 1.0 | Fix searching.test_argwhere - | | |
|---|---|
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5024818534/jobs/9010978181" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5024818534/jobs/9010978181" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5024818534/jobs/9010978181" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-failure-red></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5024818534/jobs/9010978181" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/4973224096/jobs/8898928777" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
<details>
<summary>FAILED ivy_tests/test_ivy/test_functional/test_core/test_searching.py::test_argwhere[cpu-ivy.functional.backends.numpy-False-False]</summary>
2023-05-19T14:07:47.6358337Z E hypothesis.errors.InvalidArgument: Cannot sample from a length-zero sequence.2023-05-19T14:07:47.6358705Z E 2023-05-19T14:07:47.6359393Z E You can reproduce this example by temporarily adding @reproduce_failure('6.75.3', b'AAAA') as a decorator on your test case
</details>
| test | fix searching test argwhere tensorflow img src torch img src numpy img src jax img src paddle img src failed ivy tests test ivy test functional test core test searching py test argwhere e hypothesis errors invalidargument cannot sample from a length zero sequence e e you can reproduce this example by temporarily adding reproduce failure b aaaa as a decorator on your test case | 1 |
15,568 | 3,475,742,114 | IssuesEvent | 2015-12-26 02:00:16 | weidai11/cryptopp | https://api.github.com/repos/weidai11/cryptopp | closed | A problem with random generator on MinGW | need information need test case | This code causes a segmentation fault:
```
unsigned int result;
GenerateBlock((byte*)&result, sizeof(unsigned int));
```
Here is the call stack (image, as I cannot copy text from Code::Blocks call stack window):
This problem may be caused by [issue 26](https://github.com/weidai11/cryptopp/issues/26). | 1.0 | A problem with random generator on MinGW - This code causes a segmentation fault:
```
unsigned int result;
GenerateBlock((byte*)&result, sizeof(unsigned int));
```
Here is the call stack (image, as I cannot copy text from Code::Blocks call stack window):
This problem may be caused by [issue 26](https://github.com/weidai11/cryptopp/issues/26). | test | a problem with random generator on mingw this code causes a segmentation fault unsigned int result generateblock byte result sizeof unsigned int here is the call stack image as i cannot copy text from code blocks call stack window this problem may be caused by | 1 |
17,792 | 3,013,028,404 | IssuesEvent | 2015-07-29 05:32:42 | yawlfoundation/yawl | https://api.github.com/repos/yawlfoundation/yawl | closed | Only part of a yawl model is exported to the png format | auto-migrated Priority-Critical Type-Defect | ```
What steps will reproduce the problem?
1. Open the file gynOncEnglish9_ywl_v2.0RES.yawl
2. select the GynOnc net, that is the top net
3. select Net/Export to PNG image
What is the expected output? What do you see instead?
The expected output is that you get an png image providing a picture of
the top yawl model. However, only the top part of the yawl model is shown
instead.
What version of the product are you using? On what operating system?
I'm using version 2.0_beta_update3 of the yawl editor. Operating system is
windows server 2003 with Java 1.6.
Please provide any additional information below.
I included the yawl model and the exported picture. Moreover, I need to
improve a picture which is part of a chapter in the YAWL book.
```
Original issue reported on code.google.com by `Ronny.M...@gmail.com` on 14 Apr 2009 at 1:28
Attachments:
* [gynOncEnglish9_ywl_v2.0RES.yawl](https://storage.googleapis.com/google-code-attachments/yawl/issue-336/comment-0/gynOncEnglish9_ywl_v2.0RES.yawl)
* [partial.png](https://storage.googleapis.com/google-code-attachments/yawl/issue-336/comment-0/partial.png)
| 1.0 | Only part of a yawl model is exported to the png format - ```
What steps will reproduce the problem?
1. Open the file gynOncEnglish9_ywl_v2.0RES.yawl
2. select the GynOnc net, that is the top net
3. select Net/Export to PNG image
What is the expected output? What do you see instead?
The expected output is that you get an png image providing a picture of
the top yawl model. However, only the top part of the yawl model is shown
instead.
What version of the product are you using? On what operating system?
I'm using version 2.0_beta_update3 of the yawl editor. Operating system is
windows server 2003 with Java 1.6.
Please provide any additional information below.
I included the yawl model and the exported picture. Moreover, I need to
improve a picture which is part of a chapter in the YAWL book.
```
Original issue reported on code.google.com by `Ronny.M...@gmail.com` on 14 Apr 2009 at 1:28
Attachments:
* [gynOncEnglish9_ywl_v2.0RES.yawl](https://storage.googleapis.com/google-code-attachments/yawl/issue-336/comment-0/gynOncEnglish9_ywl_v2.0RES.yawl)
* [partial.png](https://storage.googleapis.com/google-code-attachments/yawl/issue-336/comment-0/partial.png)
| non_test | only part of a yawl model is exported to the png format what steps will reproduce the problem open the file ywl yawl select the gynonc net that is the top net select net export to png image what is the expected output what do you see instead the expected output is that you get an png image providing a picture of the top yawl model however only the top part of the yawl model is shown instead what version of the product are you using on what operating system i m using version beta of the yawl editor operating system is windows server with java please provide any additional information below i included the yawl model and the exported picture moreover i need to improve a picture which is part of a chapter in the yawl book original issue reported on code google com by ronny m gmail com on apr at attachments | 0 |
305,548 | 26,392,477,990 | IssuesEvent | 2023-01-12 16:39:45 | wp-cli/wp-cli | https://api.github.com/repos/wp-cli/wp-cli | closed | Test fail on MacOS because of gnused feature | scope:testing | When running behat tests on macOS I saw this failure:
```
--- Failed steps:
001 Scenario: BOM found in wp-config.php file # features/config.feature:548
And I run `sed -i '1s/^\(\xef\xbb\xbf\)\?/\xef\xbb\xbf/' wp-config.php` # features/config.feature:566
$ sed -i '1s/^\(\xef\xbb\xbf\)\?/\xef\xbb\xbf/' wp-config.php
sed: -I or -i may not be used with stdin
cwd: /var/folders/nc/16hfjyf9517918dd0dz2g7tr0000gn/T/wp-cli-test-run--63bd7a0a590628.51883440/
run time: 0.017526865005493
exit status: 1 (RuntimeException)
```
Which comes from https://github.com/wp-cli/wp-cli/blob/f094a7eeec1213d8e0dc35f30949f22c8f4f3db3/features/config.feature#L566
Some scripts try to get around this with a check like: https://github.com/wp-cli/sample-plugin/blob/master/bin/install-wp-tests.sh#L96-L101 though I'm not sure what is supported in these .feature files
| 1.0 | Test fail on MacOS because of gnused feature - When running behat tests on macOS I saw this failure:
```
--- Failed steps:
001 Scenario: BOM found in wp-config.php file # features/config.feature:548
And I run `sed -i '1s/^\(\xef\xbb\xbf\)\?/\xef\xbb\xbf/' wp-config.php` # features/config.feature:566
$ sed -i '1s/^\(\xef\xbb\xbf\)\?/\xef\xbb\xbf/' wp-config.php
sed: -I or -i may not be used with stdin
cwd: /var/folders/nc/16hfjyf9517918dd0dz2g7tr0000gn/T/wp-cli-test-run--63bd7a0a590628.51883440/
run time: 0.017526865005493
exit status: 1 (RuntimeException)
```
Which comes from https://github.com/wp-cli/wp-cli/blob/f094a7eeec1213d8e0dc35f30949f22c8f4f3db3/features/config.feature#L566
Some scripts try to get around this with a check like: https://github.com/wp-cli/sample-plugin/blob/master/bin/install-wp-tests.sh#L96-L101 though I'm not sure what is supported in these .feature files
| test | test fail on macos because of gnused feature when running behat tests on macos i saw this failure failed steps scenario bom found in wp config php file features config feature and i run sed i xef xbb xbf xef xbb xbf wp config php features config feature sed i xef xbb xbf xef xbb xbf wp config php sed i or i may not be used with stdin cwd var folders nc t wp cli test run run time exit status runtimeexception which comes from some scripts try to get around this with a check like though i m not sure what is supported in these feature files | 1 |
16,940 | 12,152,151,656 | IssuesEvent | 2020-04-24 21:31:38 | BCDevOps/developer-experience | https://api.github.com/repos/BCDevOps/developer-experience | closed | etd metrics enabled for Sysdig | Infrastructure closed | https://trello.com/c/iF0YzqDI/102-etd-metrics-enabled-for-sysdig
Seems like sysdig agent isn't configured to grab etcd metrics. Checking to see if turned off on purpose and if I can enable again. | 1.0 | etd metrics enabled for Sysdig - https://trello.com/c/iF0YzqDI/102-etd-metrics-enabled-for-sysdig
Seems like sysdig agent isn't configured to grab etcd metrics. Checking to see if turned off on purpose and if I can enable again. | non_test | etd metrics enabled for sysdig seems like sysdig agent isn t configured to grab etcd metrics checking to see if turned off on purpose and if i can enable again | 0 |
334,403 | 24,417,809,190 | IssuesEvent | 2022-10-05 17:29:07 | sam-tripathi/Defeat-JAVA | https://api.github.com/repos/sam-tripathi/Defeat-JAVA | closed | CUSTOMIZE AND ORGANIZE THE INTRODUCTION | documentation help wanted good first issue Hacktoberfest | Organize and Customize the introduction folder to make the repository organised for new learners.
NOTE: must read all the issues to understand the aim of the projects clearly. | 1.0 | CUSTOMIZE AND ORGANIZE THE INTRODUCTION - Organize and Customize the introduction folder to make the repository organised for new learners.
NOTE: must read all the issues to understand the aim of the projects clearly. | non_test | customize and organize the introduction organize and customize the introduction folder to make the repository organised for new learners note must read all the issues to understand the aim of the projects clearly | 0 |
254,392 | 21,783,786,526 | IssuesEvent | 2022-05-13 22:36:29 | rust-lang/rust | https://api.github.com/repos/rust-lang/rust | opened | Doctests now run on non-exported `macro_rules!`, but can't actually test the macro | T-rustdoc A-doctests | Since #88038 was resolved with #96630, doctests now run on `macro_rules!` even if the macro is not exported.
This could be considered a breaking change -- it did break CI for rayon when [this macro example](https://github.com/rayon-rs/rayon/blob/9dc52d76b12f3da13b87dd509ff29a801177b8d3/src/delegate.rs#L14-L19) for internal use suddenly became a real test and failed.
The problem is, I can't figure out how to make a working doctest for that, since it's not exported in the public API. What is the intended way to do this? And if there's not really a way to do it, then maybe this change should be reverted so there isn't any break.
I thought of `#[cfg_attr(doctest, macro_export)]`, which does make even older Rust try to test it, but that still can't reach the macro because it's still using the non-`doctest` build of the crate.
---
PS: I ended up making unit tests for that rayon macro, which is probably better in that case, but that doesn't answer how non-exported macro tests should work. | 1.0 | Doctests now run on non-exported `macro_rules!`, but can't actually test the macro - Since #88038 was resolved with #96630, doctests now run on `macro_rules!` even if the macro is not exported.
This could be considered a breaking change -- it did break CI for rayon when [this macro example](https://github.com/rayon-rs/rayon/blob/9dc52d76b12f3da13b87dd509ff29a801177b8d3/src/delegate.rs#L14-L19) for internal use suddenly became a real test and failed.
The problem is, I can't figure out how to make a working doctest for that, since it's not exported in the public API. What is the intended way to do this? And if there's not really a way to do it, then maybe this change should be reverted so there isn't any break.
I thought of `#[cfg_attr(doctest, macro_export)]`, which does make even older Rust try to test it, but that still can't reach the macro because it's still using the non-`doctest` build of the crate.
---
PS: I ended up making unit tests for that rayon macro, which is probably better in that case, but that doesn't answer how non-exported macro tests should work. | test | doctests now run on non exported macro rules but can t actually test the macro since was resolved with doctests now run on macro rules even if the macro is not exported this could be considered a breaking change it did break ci for rayon when for internal use suddenly became a real test and failed the problem is i can t figure out how to make a working doctest for that since it s not exported in the public api what is the intended way to do this and if there s not really a way to do it then maybe this change should be reverted so there isn t any break i thought of which does make even older rust try to test it but that still can t reach the macro because it s still using the non doctest build of the crate ps i ended up making unit tests for that rayon macro which is probably better in that case but that doesn t answer how non exported macro tests should work | 1 |
213,938 | 16,547,274,091 | IssuesEvent | 2021-05-28 02:37:18 | Azure/azure-sdk-for-cpp | https://api.github.com/repos/Azure/azure-sdk-for-cpp | closed | Unexpected output of ASSERT_DEATH | Client Storage test bug | Hi Ahson, I noticed you updated some of storage test code https://github.com/Azure/azure-sdk-for-cpp/blob/3596685e800dc32c8584cdbe141e10218fd28d8c/sdk/storage/azure-storage-common/test/crypt_functions_test.cpp#L130
The `ASSERT_DEATH` outputs some unrelated information. Is this expected behavior?
```
[----------] 5 tests from CryptFunctionsTest
[ RUN ] CryptFunctionsTest.Sha256
[ OK ] CryptFunctionsTest.Sha256 (0 ms)
[ RUN ] CryptFunctionsTest.HmacSha256
[ OK ] CryptFunctionsTest.HmacSha256 (0 ms)
[ RUN ] CryptFunctionsTest.Crc64Hash_Basic
[ OK ] CryptFunctionsTest.Crc64Hash_Basic (371 ms)
[ RUN ] CryptFunctionsTest.Crc64Hash_ExpectThrow
Running main() from D:\azure-sdk-for-cpp\build\_deps\googletest-src\googletest\src\gtest_main.cc
Running main() from D:\azure-sdk-for-cpp\build\_deps\googletest-src\googletest\src\gtest_main.cc
Running main() from D:\azure-sdk-for-cpp\build\_deps\googletest-src\googletest\src\gtest_main.cc
Running main() from D:\azure-sdk-for-cpp\build\_deps\googletest-src\googletest\src\gtest_main.cc
Running main() from D:\azure-sdk-for-cpp\build\_deps\googletest-src\googletest\src\gtest_main.cc
[ OK ] CryptFunctionsTest.Crc64Hash_ExpectThrow (119 ms)
[ RUN ] CryptFunctionsTest.Crc64Hash_CtorDtor
[ OK ] CryptFunctionsTest.Crc64Hash_CtorDtor (0 ms)
[----------] 5 tests from CryptFunctionsTest (493 ms total)
```
| 1.0 | Unexpected output of ASSERT_DEATH - Hi Ahson, I noticed you updated some of storage test code https://github.com/Azure/azure-sdk-for-cpp/blob/3596685e800dc32c8584cdbe141e10218fd28d8c/sdk/storage/azure-storage-common/test/crypt_functions_test.cpp#L130
The `ASSERT_DEATH` outputs some unrelated information. Is this expected behavior?
```
[----------] 5 tests from CryptFunctionsTest
[ RUN ] CryptFunctionsTest.Sha256
[ OK ] CryptFunctionsTest.Sha256 (0 ms)
[ RUN ] CryptFunctionsTest.HmacSha256
[ OK ] CryptFunctionsTest.HmacSha256 (0 ms)
[ RUN ] CryptFunctionsTest.Crc64Hash_Basic
[ OK ] CryptFunctionsTest.Crc64Hash_Basic (371 ms)
[ RUN ] CryptFunctionsTest.Crc64Hash_ExpectThrow
Running main() from D:\azure-sdk-for-cpp\build\_deps\googletest-src\googletest\src\gtest_main.cc
Running main() from D:\azure-sdk-for-cpp\build\_deps\googletest-src\googletest\src\gtest_main.cc
Running main() from D:\azure-sdk-for-cpp\build\_deps\googletest-src\googletest\src\gtest_main.cc
Running main() from D:\azure-sdk-for-cpp\build\_deps\googletest-src\googletest\src\gtest_main.cc
Running main() from D:\azure-sdk-for-cpp\build\_deps\googletest-src\googletest\src\gtest_main.cc
[ OK ] CryptFunctionsTest.Crc64Hash_ExpectThrow (119 ms)
[ RUN ] CryptFunctionsTest.Crc64Hash_CtorDtor
[ OK ] CryptFunctionsTest.Crc64Hash_CtorDtor (0 ms)
[----------] 5 tests from CryptFunctionsTest (493 ms total)
```
| test | unexpected output of assert death hi ahson i noticed you updated some of storage test code the assert death outputs some unrelated information is this expected behavior tests from cryptfunctionstest cryptfunctionstest cryptfunctionstest ms cryptfunctionstest cryptfunctionstest ms cryptfunctionstest basic cryptfunctionstest basic ms cryptfunctionstest expectthrow running main from d azure sdk for cpp build deps googletest src googletest src gtest main cc running main from d azure sdk for cpp build deps googletest src googletest src gtest main cc running main from d azure sdk for cpp build deps googletest src googletest src gtest main cc running main from d azure sdk for cpp build deps googletest src googletest src gtest main cc running main from d azure sdk for cpp build deps googletest src googletest src gtest main cc cryptfunctionstest expectthrow ms cryptfunctionstest ctordtor cryptfunctionstest ctordtor ms tests from cryptfunctionstest ms total | 1 |
351,733 | 32,023,966,719 | IssuesEvent | 2023-09-22 07:29:08 | nikohoffren/fork-commit-merge | https://api.github.com/repos/nikohoffren/fork-commit-merge | opened | Fork, Commit, Merge - Easy Issue (JavaScript/Jasmine) | help wanted good first issue first-contributor easy javascript testing jasmine | # Fork, Commit, Merge - Easy Issue (JavaScript/Jasmine)
## Make Simple Jasmine Test Pass
*Note: You don't have ask permission to start solving the issue or get assigned, since these issues are supposed to be always open for new contributors. The actions-user bot will reset the file back to previous state for the next contributor after your commit is merged. So you can just simply start working with the issue right away!*
### How to get started
Navigate to the directory used in this project with the command:
```bash
cd tasks/jasmine/easy
```
Install all the necessary dependencies and Jasmine:
```bash
npm i
```
Open `spec/booltest.spec.js` file and start implementing your solution!
### Description
The goal of this task is to make the Jasmine test in `spec/booltest.spec.js` file pass.
Add `expect` and `toBe` statements inside the test case that checks if true is equal to true.
Run your test with `npx jasmine` and make sure it passes.
### Expected output
After running the test, you should see output similar to this:
```bash
Randomized with seed 11274
Started
.
1 spec, 0 failures
Finished in 0.005 seconds
Randomized with seed 11274 (jasmine --random=true --seed=11274)
```
If it displays `0 failures`, that means the test passed and you are ready to make a pull request!
---
To work with this issue, you need to have npm and NodeJS installed to your local machine.
Check out [README.md](https://github.com/nikohoffren/fork-commit-merge/blob/main/README.md) for more instructions of installing npm and NodeJS as well as how to make a pull request.
Feel free to ask any questions here if you have some problems!
#### Also, kindly give this project a star to enhance its visibility for new developers! | 1.0 | Fork, Commit, Merge - Easy Issue (JavaScript/Jasmine) - # Fork, Commit, Merge - Easy Issue (JavaScript/Jasmine)
## Make Simple Jasmine Test Pass
*Note: You don't have ask permission to start solving the issue or get assigned, since these issues are supposed to be always open for new contributors. The actions-user bot will reset the file back to previous state for the next contributor after your commit is merged. So you can just simply start working with the issue right away!*
### How to get started
Navigate to the directory used in this project with the command:
```bash
cd tasks/jasmine/easy
```
Install all the necessary dependencies and Jasmine:
```bash
npm i
```
Open `spec/booltest.spec.js` file and start implementing your solution!
### Description
The goal of this task is to make the Jasmine test in `spec/booltest.spec.js` file pass.
Add `expect` and `toBe` statements inside the test case that checks if true is equal to true.
Run your test with `npx jasmine` and make sure it passes.
### Expected output
After running the test, you should see output similar to this:
```bash
Randomized with seed 11274
Started
.
1 spec, 0 failures
Finished in 0.005 seconds
Randomized with seed 11274 (jasmine --random=true --seed=11274)
```
If it displays `0 failures`, that means the test passed and you are ready to make a pull request!
---
To work with this issue, you need to have npm and NodeJS installed to your local machine.
Check out [README.md](https://github.com/nikohoffren/fork-commit-merge/blob/main/README.md) for more instructions of installing npm and NodeJS as well as how to make a pull request.
Feel free to ask any questions here if you have some problems!
#### Also, kindly give this project a star to enhance its visibility for new developers! | test | fork commit merge easy issue javascript jasmine fork commit merge easy issue javascript jasmine make simple jasmine test pass note you don t have ask permission to start solving the issue or get assigned since these issues are supposed to be always open for new contributors the actions user bot will reset the file back to previous state for the next contributor after your commit is merged so you can just simply start working with the issue right away how to get started navigate to the directory used in this project with the command bash cd tasks jasmine easy install all the necessary dependencies and jasmine bash npm i open spec booltest spec js file and start implementing your solution description the goal of this task is to make the jasmine test in spec booltest spec js file pass add expect and tobe statements inside the test case that checks if true is equal to true run your test with npx jasmine and make sure it passes expected output after running the test you should see output similar to this bash randomized with seed started spec failures finished in seconds randomized with seed jasmine random true seed if it displays failures that means the test passed and you are ready to make a pull request to work with this issue you need to have npm and nodejs installed to your local machine check out for more instructions of installing npm and nodejs as well as how to make a pull request feel free to ask any questions here if you have some problems also kindly give this project a star to enhance its visibility for new developers | 1 |
96,776 | 10,962,867,244 | IssuesEvent | 2019-11-27 18:15:23 | metabase/metabase | https://api.github.com/repos/metabase/metabase | opened | Enchantments to Full App Embedding Docs | .Documentation .Needs Triage Embedding/ | * It would be helpful if we also link to how to do an SSO endpoint (link to example) where we say you need it and in general link to setting up SSO.
In an ideal world there would be some (visual) schema or some such explaining the entire SSO workflow for people who've never worked with that before.
* Mention serialization under deployment considerations or some such, as else the pre-made dashboards are awkward state you carry around in a DB (or dump thereof), but from an app-developer perspective I'd definitely like the workflow for making & tweaking my dashboards be closer to how I do the rest of my development. | 1.0 | Enchantments to Full App Embedding Docs - * It would be helpful if we also link to how to do an SSO endpoint (link to example) where we say you need it and in general link to setting up SSO.
In an ideal world there would be some (visual) schema or some such explaining the entire SSO workflow for people who've never worked with that before.
* Mention serialization under deployment considerations or some such, as else the pre-made dashboards are awkward state you carry around in a DB (or dump thereof), but from an app-developer perspective I'd definitely like the workflow for making & tweaking my dashboards be closer to how I do the rest of my development. | non_test | enchantments to full app embedding docs it would be helpful if we also link to how to do an sso endpoint link to example where we say you need it and in general link to setting up sso in an ideal world there would be some visual schema or some such explaining the entire sso workflow for people who ve never worked with that before mention serialization under deployment considerations or some such as else the pre made dashboards are awkward state you carry around in a db or dump thereof but from an app developer perspective i d definitely like the workflow for making tweaking my dashboards be closer to how i do the rest of my development | 0 |
80,074 | 7,739,056,597 | IssuesEvent | 2018-05-28 14:19:11 | italia/spid | https://api.github.com/repos/italia/spid | closed | Richiesta validazione metadata - Comune di Calcio | metadata nuovo md test | Buongiorno,
si richiede la validazione dei metadati per conto del comune:
https://sportellotelematico.comune.calcio.bg.it/simplesaml/module.php/saml/sp/metadata.php/calcio | 1.0 | Richiesta validazione metadata - Comune di Calcio - Buongiorno,
si richiede la validazione dei metadati per conto del comune:
https://sportellotelematico.comune.calcio.bg.it/simplesaml/module.php/saml/sp/metadata.php/calcio | test | richiesta validazione metadata comune di calcio buongiorno si richiede la validazione dei metadati per conto del comune | 1 |
121,376 | 10,166,981,257 | IssuesEvent | 2019-08-07 17:05:22 | kudobuilder/kudo | https://api.github.com/repos/kudobuilder/kudo | closed | Seeing flakes due to already existing resources | component/testing flaky test kind/bug priority/high | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security sensitive, please disclose it privately to a security contact: https://github.com/kudobuilder/kudo/blob/master/SECURITY_CONTACTS
-->
**What happened**:
We're seeing some flakes due to resources already existing, e.g.:
```
--- FAIL: TestWaitForCRDs (0.12s)
kubernetes_integration_test.go:98:
Error Trace: kubernetes_integration_test.go:98
Error: Expected nil, but got: &errors.StatusError{ErrStatus:v1.Status{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ListMeta:v1.ListMeta{SelfLink:"", ResourceVersion:"", Continue:""}, Status:"Failure", Message:"instances.kudo.k8s.io \"zk\" already exists", Reason:"AlreadyExists", Details:(*v1.StatusDetails)(0xc000442060), Code:409}}
Test: TestWaitForCRDs
```
I believe this is an issue with the RetryClient that we need to resolve. Likely the first request hit an error and retried, but was still successfully processed by the API server so the resource already existed. We likely can fix these tests by using CreateOrUpdate instead of just Create. | 2.0 | Seeing flakes due to already existing resources - <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security sensitive, please disclose it privately to a security contact: https://github.com/kudobuilder/kudo/blob/master/SECURITY_CONTACTS
-->
**What happened**:
We're seeing some flakes due to resources already existing, e.g.:
```
--- FAIL: TestWaitForCRDs (0.12s)
kubernetes_integration_test.go:98:
Error Trace: kubernetes_integration_test.go:98
Error: Expected nil, but got: &errors.StatusError{ErrStatus:v1.Status{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ListMeta:v1.ListMeta{SelfLink:"", ResourceVersion:"", Continue:""}, Status:"Failure", Message:"instances.kudo.k8s.io \"zk\" already exists", Reason:"AlreadyExists", Details:(*v1.StatusDetails)(0xc000442060), Code:409}}
Test: TestWaitForCRDs
```
I believe this is an issue with the RetryClient that we need to resolve. Likely the first request hit an error and retried, but was still successfully processed by the API server so the resource already existed. We likely can fix these tests by using CreateOrUpdate instead of just Create. | test | seeing flakes due to already existing resources please use this template while reporting a bug and provide as much info as possible not doing so may result in your bug not being addressed in a timely manner thanks if the matter is security sensitive please disclose it privately to a security contact what happened we re seeing some flakes due to resources already existing e g fail testwaitforcrds kubernetes integration test go error trace kubernetes integration test go error expected nil but got errors statuserror errstatus status typemeta typemeta kind apiversion listmeta listmeta selflink resourceversion continue status failure message instances kudo io zk already exists reason alreadyexists details statusdetails code test testwaitforcrds i believe this is an issue with the retryclient that we need to resolve likely the first request hit an error and retried but was still successfully processed by the api server so the resource already existed we likely can fix these tests by using createorupdate instead of just create | 1 |
90,618 | 18,216,663,213 | IssuesEvent | 2021-09-30 05:47:52 | ContriHUB/BankingManagementApplication | https://api.github.com/repos/ContriHUB/BankingManagementApplication | opened | Make javaconnect a singleton class | sakt-coder medium | In javaconnect.java at line 15, a Connection object is made but never used. Make use of it to convert the javaconnect class to a Singleton Class. | 1.0 | Make javaconnect a singleton class - In javaconnect.java at line 15, a Connection object is made but never used. Make use of it to convert the javaconnect class to a Singleton Class. | non_test | make javaconnect a singleton class in javaconnect java at line a connection object is made but never used make use of it to convert the javaconnect class to a singleton class | 0 |
207,822 | 15,837,516,359 | IssuesEvent | 2021-04-06 20:54:17 | rancher/dashboard | https://api.github.com/repos/rancher/dashboard | closed | Volume Plugin for Storage class and PVs dropdown does not work | QA/XS [zube]: To Test kind/bug | **On 2.5-head commit id: `118f999`**
- On a downstream cluster --> Custer Explorer --> Storage Classes
- Dropdown of Storage class does not work / list all the supported providers
<img width="957" alt="Screen Shot 2021-03-30 at 8 45 51 PM" src="https://user-images.githubusercontent.com/26032343/113087733-1c8da200-9199-11eb-8427-9c66b1a550b4.png">
**Note:**
Same issue is seen for a PV also --> PV --> Create --> Volume plugin dropdown | 1.0 | Volume Plugin for Storage class and PVs dropdown does not work - **On 2.5-head commit id: `118f999`**
- On a downstream cluster --> Custer Explorer --> Storage Classes
- Dropdown of Storage class does not work / list all the supported providers
<img width="957" alt="Screen Shot 2021-03-30 at 8 45 51 PM" src="https://user-images.githubusercontent.com/26032343/113087733-1c8da200-9199-11eb-8427-9c66b1a550b4.png">
**Note:**
Same issue is seen for a PV also --> PV --> Create --> Volume plugin dropdown | test | volume plugin for storage class and pvs dropdown does not work on head commit id on a downstream cluster custer explorer storage classes dropdown of storage class does not work list all the supported providers img width alt screen shot at pm src note same issue is seen for a pv also pv create volume plugin dropdown | 1 |
287,921 | 31,856,503,168 | IssuesEvent | 2023-09-15 07:51:46 | Trinadh465/linux-4.1.15_CVE-2023-26607 | https://api.github.com/repos/Trinadh465/linux-4.1.15_CVE-2023-26607 | opened | CVE-2019-8912 (High) detected in linux-stable-rtv4.1.33 | Mend: dependency security vulnerability | ## CVE-2019-8912 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Trinadh465/linux-4.1.15_CVE-2023-26607/commit/6fca0e3f2f14e1e851258fd815766531370084b0">6fca0e3f2f14e1e851258fd815766531370084b0</a></p>
<p>Found in base branch: <b>main</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/crypto/af_alg.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/crypto/af_alg.c</b>
</p>
</details>
<p></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>
In the Linux kernel through 4.20.11, af_alg_release() in crypto/af_alg.c neglects to set a NULL value for a certain structure member, which leads to a use-after-free in sockfs_setattr.
<p>Publish Date: 2019-02-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-8912>CVE-2019-8912</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.8</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: 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>
<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-2019-8912">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8912</a></p>
<p>Release Date: 2019-02-18</p>
<p>Fix Resolution: v5.0-rc8</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2019-8912 (High) detected in linux-stable-rtv4.1.33 - ## CVE-2019-8912 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Trinadh465/linux-4.1.15_CVE-2023-26607/commit/6fca0e3f2f14e1e851258fd815766531370084b0">6fca0e3f2f14e1e851258fd815766531370084b0</a></p>
<p>Found in base branch: <b>main</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/crypto/af_alg.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/crypto/af_alg.c</b>
</p>
</details>
<p></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>
In the Linux kernel through 4.20.11, af_alg_release() in crypto/af_alg.c neglects to set a NULL value for a certain structure member, which leads to a use-after-free in sockfs_setattr.
<p>Publish Date: 2019-02-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-8912>CVE-2019-8912</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.8</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: 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>
<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-2019-8912">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8912</a></p>
<p>Release Date: 2019-02-18</p>
<p>Fix Resolution: v5.0-rc8</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve high detected in linux stable cve high severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href found in base branch main vulnerable source files crypto af alg c crypto af alg c vulnerability details in the linux kernel through af alg release in crypto af alg c neglects to set a null value for a certain structure member which leads to a use after free in sockfs setattr 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 high integrity impact high 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 mend | 0 |
161,397 | 12,543,004,901 | IssuesEvent | 2020-06-05 14:52:58 | zio/zio | https://api.github.com/repos/zio/zio | opened | Flaky ZManaged Test | flaky tests zmanaged | ```scala
testM("Runs finalizers if returning None and reservation is successful after timeout") {
for {
acquireLatch <- Promise.make[Nothing, Unit]
releaseLatch <- Promise.make[Nothing, Unit]
managed = ZManaged.makeReserve(
acquireLatch.await *> ZIO.succeed(Reservation(ZIO.unit, _ => releaseLatch.succeed(())))
)
res <- managed.timeout(Duration.Zero).use(ZIO.succeed(_))
_ <- acquireLatch.succeed(())
_ <- releaseLatch.await
} yield assert(res)(isNone)
} @@ nonFlaky(10000)
``` | 1.0 | Flaky ZManaged Test - ```scala
testM("Runs finalizers if returning None and reservation is successful after timeout") {
for {
acquireLatch <- Promise.make[Nothing, Unit]
releaseLatch <- Promise.make[Nothing, Unit]
managed = ZManaged.makeReserve(
acquireLatch.await *> ZIO.succeed(Reservation(ZIO.unit, _ => releaseLatch.succeed(())))
)
res <- managed.timeout(Duration.Zero).use(ZIO.succeed(_))
_ <- acquireLatch.succeed(())
_ <- releaseLatch.await
} yield assert(res)(isNone)
} @@ nonFlaky(10000)
``` | test | flaky zmanaged test scala testm runs finalizers if returning none and reservation is successful after timeout for acquirelatch promise make releaselatch promise make managed zmanaged makereserve acquirelatch await zio succeed reservation zio unit releaselatch succeed res managed timeout duration zero use zio succeed acquirelatch succeed releaselatch await yield assert res isnone nonflaky | 1 |
309,462 | 26,662,778,794 | IssuesEvent | 2023-01-25 22:56:36 | Moonshine-IDE/Moonshine-IDE | https://api.github.com/repos/Moonshine-IDE/Moonshine-IDE | closed | Maven Updates for JDK 17 | bug enhancement test ready | We are seeing errors with new Java Maven projects after the JDK 17 updates (#1124) | 1.0 | Maven Updates for JDK 17 - We are seeing errors with new Java Maven projects after the JDK 17 updates (#1124) | test | maven updates for jdk we are seeing errors with new java maven projects after the jdk updates | 1 |
288,768 | 24,935,467,848 | IssuesEvent | 2022-10-31 14:50:35 | rancher/terraform-provider-rke | https://api.github.com/repos/rancher/terraform-provider-rke | closed | Update RKE Terraform Provider with Newest RKE version 1.3.15 | enhancement [zube]: To Test team/area2 | Creating this issue to request a new RKE TF provider release to address [this addon issue in RKE](https://github.com/rancher/rancher/issues/38876) and make the default image the latest release of RKE (v1.3.15).
| 1.0 | Update RKE Terraform Provider with Newest RKE version 1.3.15 - Creating this issue to request a new RKE TF provider release to address [this addon issue in RKE](https://github.com/rancher/rancher/issues/38876) and make the default image the latest release of RKE (v1.3.15).
| test | update rke terraform provider with newest rke version creating this issue to request a new rke tf provider release to address and make the default image the latest release of rke | 1 |
202,230 | 15,269,459,773 | IssuesEvent | 2021-02-22 12:49:41 | AdoptOpenJDK/openjdk-infrastructure | https://api.github.com/repos/AdoptOpenJDK/openjdk-infrastructure | opened | test-azure-win2012r2-x64-2 / test-azure-win2016-x64-1: openj9 SharedClasses.xxx tests fail | testFail | The following openj9 shared classed test targets may fail when they land on test-azure-win2012r2-x64-2 or test-azure-win2016-x64-1.
```
SharedClassesAPI
SharedClasses.SCM01.MultiCL
SharedClasses.SCM01.MultiThread
SharedClasses.SCM01.MultiThreadMultiCL
SharedClasses.SCM23.MultiCL
SharedClasses.SCM23.MultiThread
SharedClasses.SCM23.MultiThreadMultiCL
```
The symptoms are various out of memory exceptions - e.g.
```
11:52:21 MT4 stderr JVMDUMP032I JVM requested Snap dump using 'C:\Users\jenkins\workspace\Grinder\openjdk-tests\TKG\output_1613993216963\SharedClasses.SCM23.MultiThread_1\20210222-114232-SharedClasses\results\Snap.20210222.114552.7872.0004.trc' in response to an event
11:52:21 MT4 stderr JVMDUMP010I Snap dump written to C:\Users\jenkins\workspace\Grinder\openjdk-tests\TKG\output_1613993216963\SharedClasses.SCM23.MultiThread_1\20210222-114232-SharedClasses\results\Snap.20210222.114552.7872.0004.trc
11:52:21 MT4 stderr JVMDUMP013I Processed dump event "systhrow", detail "java/lang/OutOfMemoryError".
11:52:21 MT4 stderr Exception in thread "main" java.lang.OutOfMemoryError: Failed to create a thread: retVal -1073741830, errno 22
11:52:21 MT4 stderr at java.lang.Thread.startImpl(Native Method)
11:52:21 MT4 stderr at java.lang.Thread.start(Thread.java:993)
11:52:21 MT4 stderr at net.openj9.test.sc.LoaderSlaveMultiThread.run(LoaderSlaveMultiThread.java:130)
11:52:21 MT4 stderr at net.openj9.test.sc.LoaderSlaveMultiThread.main(LoaderSlaveMultiThread.java:59)
```
Their Jenkins links show the machines have 4Gb RAM:
https://ci.adoptopenjdk.net/computer/test-azure-win2012r2-x64-2/ - Failed
https://ci.adoptopenjdk.net/computer/test-azure-win2016-x64-1/ - Failed
The links for two other machines also show them as having 4Gb memory, but the tests pass on those machines:
https://ci.adoptopenjdk.net/computer/test-azure-win2012r2-x64-1/ - Passed
https://ci.adoptopenjdk.net/computer/test-azure-win2012r2-x64-3/ - Passed
| 1.0 | test-azure-win2012r2-x64-2 / test-azure-win2016-x64-1: openj9 SharedClasses.xxx tests fail - The following openj9 shared classed test targets may fail when they land on test-azure-win2012r2-x64-2 or test-azure-win2016-x64-1.
```
SharedClassesAPI
SharedClasses.SCM01.MultiCL
SharedClasses.SCM01.MultiThread
SharedClasses.SCM01.MultiThreadMultiCL
SharedClasses.SCM23.MultiCL
SharedClasses.SCM23.MultiThread
SharedClasses.SCM23.MultiThreadMultiCL
```
The symptoms are various out of memory exceptions - e.g.
```
11:52:21 MT4 stderr JVMDUMP032I JVM requested Snap dump using 'C:\Users\jenkins\workspace\Grinder\openjdk-tests\TKG\output_1613993216963\SharedClasses.SCM23.MultiThread_1\20210222-114232-SharedClasses\results\Snap.20210222.114552.7872.0004.trc' in response to an event
11:52:21 MT4 stderr JVMDUMP010I Snap dump written to C:\Users\jenkins\workspace\Grinder\openjdk-tests\TKG\output_1613993216963\SharedClasses.SCM23.MultiThread_1\20210222-114232-SharedClasses\results\Snap.20210222.114552.7872.0004.trc
11:52:21 MT4 stderr JVMDUMP013I Processed dump event "systhrow", detail "java/lang/OutOfMemoryError".
11:52:21 MT4 stderr Exception in thread "main" java.lang.OutOfMemoryError: Failed to create a thread: retVal -1073741830, errno 22
11:52:21 MT4 stderr at java.lang.Thread.startImpl(Native Method)
11:52:21 MT4 stderr at java.lang.Thread.start(Thread.java:993)
11:52:21 MT4 stderr at net.openj9.test.sc.LoaderSlaveMultiThread.run(LoaderSlaveMultiThread.java:130)
11:52:21 MT4 stderr at net.openj9.test.sc.LoaderSlaveMultiThread.main(LoaderSlaveMultiThread.java:59)
```
Their Jenkins links show the machines have 4Gb RAM:
https://ci.adoptopenjdk.net/computer/test-azure-win2012r2-x64-2/ - Failed
https://ci.adoptopenjdk.net/computer/test-azure-win2016-x64-1/ - Failed
The links for two other machines also show them as having 4Gb memory, but the tests pass on those machines:
https://ci.adoptopenjdk.net/computer/test-azure-win2012r2-x64-1/ - Passed
https://ci.adoptopenjdk.net/computer/test-azure-win2012r2-x64-3/ - Passed
| test | test azure test azure sharedclasses xxx tests fail the following shared classed test targets may fail when they land on test azure or test azure sharedclassesapi sharedclasses multicl sharedclasses multithread sharedclasses multithreadmulticl sharedclasses multicl sharedclasses multithread sharedclasses multithreadmulticl the symptoms are various out of memory exceptions e g stderr jvm requested snap dump using c users jenkins workspace grinder openjdk tests tkg output sharedclasses multithread sharedclasses results snap trc in response to an event stderr snap dump written to c users jenkins workspace grinder openjdk tests tkg output sharedclasses multithread sharedclasses results snap trc stderr processed dump event systhrow detail java lang outofmemoryerror stderr exception in thread main java lang outofmemoryerror failed to create a thread retval errno stderr at java lang thread startimpl native method stderr at java lang thread start thread java stderr at net test sc loaderslavemultithread run loaderslavemultithread java stderr at net test sc loaderslavemultithread main loaderslavemultithread java their jenkins links show the machines have ram failed failed the links for two other machines also show them as having memory but the tests pass on those machines passed passed | 1 |
320,455 | 27,435,937,294 | IssuesEvent | 2023-03-02 07:24:56 | TencentBlueKing/bk-ci | https://api.github.com/repos/TencentBlueKing/bk-ci | closed | fix: tbs controller剔除异常worker | for test streams/for test | disable 连续发生网络错误的worker，防止大量任务远程失败转本地
定期检查被禁用的worker，若网络恢复则重新enable
| 2.0 | fix: tbs controller剔除异常worker - disable 连续发生网络错误的worker，防止大量任务远程失败转本地
定期检查被禁用的worker，若网络恢复则重新enable
| test | fix tbs controller剔除异常worker disable 连续发生网络错误的worker，防止大量任务远程失败转本地 定期检查被禁用的worker，若网络恢复则重新enable | 1 |
380,667 | 26,427,948,590 | IssuesEvent | 2023-01-14 12:41:42 | Anselmoo/spectrafit | https://api.github.com/repos/Anselmoo/spectrafit | closed | [Docs]: Add home directory to suggested docker command | documentation | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current Missing Information in the Docs
It's easier to use SpectrafitNotebook via docker if one runs the docker command remapping to a directory on the home computer. For example,
```shell
docker run -p 8888:8888 -it -v /home/target:/home/users/workspace ghcr.io/anselmoo/spectrafit:latest
```
### Anything else?
_No response_
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct | 1.0 | [Docs]: Add home directory to suggested docker command - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current Missing Information in the Docs
It's easier to use SpectrafitNotebook via docker if one runs the docker command remapping to a directory on the home computer. For example,
```shell
docker run -p 8888:8888 -it -v /home/target:/home/users/workspace ghcr.io/anselmoo/spectrafit:latest
```
### Anything else?
_No response_
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct | non_test | add home directory to suggested docker command is there an existing issue for this i have searched the existing issues current missing information in the docs it s easier to use spectrafitnotebook via docker if one runs the docker command remapping to a directory on the home computer for example shell docker run p it v home target home users workspace ghcr io anselmoo spectrafit latest anything else no response code of conduct i agree to follow this project s code of conduct | 0 |
776,111 | 27,247,271,638 | IssuesEvent | 2023-02-22 03:49:18 | chaotic-aur/packages | https://api.github.com/repos/chaotic-aur/packages | closed | [Request] ASUS Keyboard BackLight | request:new-pkg priority:low | ### Link to the package base(s) in the AUR
[asus-kbd-backlight](https://aur.archlinux.org/packages/asus-kbd-backlight)
### Utility this package has for you
Helper for adjusting keyboard backlight brightness in Asus Zenbook UX31A and ASUS N551 XX and similar models
### Do you consider the package(s) to be useful for every Chaotic-AUR user?
No, but for a few.
### Do you consider the package to be useful for feature testing/preview?
- [ ] Yes
### Have you tested if the package builds in a clean chroot?
- [X] Yes
### Does the package's license allow redistributing it?
YES!
### Have you searched the issues to ensure this request is unique?
- [X] YES!
### Have you read the README to ensure this package is not banned?
- [X] YES!
### More information
After installing the package, you need to activate its service.
and a module for the kernel to be called.
```
modprobe asus-nb-wmi
systemctl enable asus-kbd-backlight.service
```
| 1.0 | [Request] ASUS Keyboard BackLight - ### Link to the package base(s) in the AUR
[asus-kbd-backlight](https://aur.archlinux.org/packages/asus-kbd-backlight)
### Utility this package has for you
Helper for adjusting keyboard backlight brightness in Asus Zenbook UX31A and ASUS N551 XX and similar models
### Do you consider the package(s) to be useful for every Chaotic-AUR user?
No, but for a few.
### Do you consider the package to be useful for feature testing/preview?
- [ ] Yes
### Have you tested if the package builds in a clean chroot?
- [X] Yes
### Does the package's license allow redistributing it?
YES!
### Have you searched the issues to ensure this request is unique?
- [X] YES!
### Have you read the README to ensure this package is not banned?
- [X] YES!
### More information
After installing the package, you need to activate its service.
and a module for the kernel to be called.
```
modprobe asus-nb-wmi
systemctl enable asus-kbd-backlight.service
```
| non_test | asus keyboard backlight link to the package base s in the aur utility this package has for you helper for adjusting keyboard backlight brightness in asus zenbook and asus xx and similar models do you consider the package s to be useful for every chaotic aur user no but for a few do you consider the package to be useful for feature testing preview yes have you tested if the package builds in a clean chroot yes does the package s license allow redistributing it yes have you searched the issues to ensure this request is unique yes have you read the readme to ensure this package is not banned yes more information after installing the package you need to activate its service and a module for the kernel to be called modprobe asus nb wmi systemctl enable asus kbd backlight service | 0 |
266,054 | 23,220,185,810 | IssuesEvent | 2022-08-02 17:25:26 | elastic/kibana | https://api.github.com/repos/elastic/kibana | reopened | Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/infra/home_page·ts - InfraOps App Metrics UI Home page Saved Views should have save and load controls | Feature:Metrics UI failed-test Team:Infra Monitoring UI | A test failed on a tracked branch
```
Error: expected 'No view selected' to equal 'Default view'
at Assertion.assert (/dev/shm/workspace/parallel/16/kibana/node_modules/@kbn/expect/expect.js:100:11)
at Assertion.be.Assertion.equal (/dev/shm/workspace/parallel/16/kibana/node_modules/@kbn/expect/expect.js:227:8)
at Assertion.be (/dev/shm/workspace/parallel/16/kibana/node_modules/@kbn/expect/expect.js:69:22)
at Object.ensureViewIsLoaded (test/functional/page_objects/infra_saved_views.ts:78:49)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at Context.<anonymous> (test/functional/apps/infra/home_page.ts:96:9)
at Object.apply (/dev/shm/workspace/parallel/16/kibana/node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16)
```
First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+7.x/15597/)
<!-- kibanaCiData = {"failed-test":{"test.class":"Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/infra/home_page·ts","test.name":"InfraOps App Metrics UI Home page Saved Views should have save and load controls","test.failCount":20}} --> | 1.0 | Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/infra/home_page·ts - InfraOps App Metrics UI Home page Saved Views should have save and load controls - A test failed on a tracked branch
```
Error: expected 'No view selected' to equal 'Default view'
at Assertion.assert (/dev/shm/workspace/parallel/16/kibana/node_modules/@kbn/expect/expect.js:100:11)
at Assertion.be.Assertion.equal (/dev/shm/workspace/parallel/16/kibana/node_modules/@kbn/expect/expect.js:227:8)
at Assertion.be (/dev/shm/workspace/parallel/16/kibana/node_modules/@kbn/expect/expect.js:69:22)
at Object.ensureViewIsLoaded (test/functional/page_objects/infra_saved_views.ts:78:49)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at Context.<anonymous> (test/functional/apps/infra/home_page.ts:96:9)
at Object.apply (/dev/shm/workspace/parallel/16/kibana/node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16)
```
First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+7.x/15597/)
<!-- kibanaCiData = {"failed-test":{"test.class":"Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/infra/home_page·ts","test.name":"InfraOps App Metrics UI Home page Saved Views should have save and load controls","test.failCount":20}} --> | test | failing test chrome x pack ui functional tests x pack test functional apps infra home page·ts infraops app metrics ui home page saved views should have save and load controls a test failed on a tracked branch error expected no view selected to equal default view at assertion assert dev shm workspace parallel kibana node modules kbn expect expect js at assertion be assertion equal dev shm workspace parallel kibana node modules kbn expect expect js at assertion be dev shm workspace parallel kibana node modules kbn expect expect js at object ensureviewisloaded test functional page objects infra saved views ts at runmicrotasks at processticksandrejections internal process task queues js at context test functional apps infra home page ts at object apply dev shm workspace parallel kibana node modules kbn test target node functional test runner lib mocha wrap function js first failure | 1 |
293,332 | 25,285,101,604 | IssuesEvent | 2022-11-16 18:37:05 | wazuh/wazuh | https://api.github.com/repos/wazuh/wazuh | closed | Release 4.3.10 | release test/4.3.10 | Main issue gathering all the tasks regarding the preparation and validation of Wazuh version 4.3.10 release.
Close the issue only after the GA release.
## Release info
| | |
|---------------------------------------|------------------------------------------------------|
| Release name| Wazuh v4.3.10|
| Tag | https://github.com/wazuh/wazuh/tree/v4.3.10 |
| Branch | https://github.com/wazuh/wazuh/tree/4.3 |
| Changelog | https://github.com/wazuh/wazuh/blob/4.3/CHANGELOG.md |
| Latest release candidate (GA version) | N/A | |
## Release candidates
As usual, in order to publish, one or more release candidate versions are generated and fully tested, in the links below you can check the status and evolution of each version.
| Version | Issue | Tag | Status |
|---------|-------|-------------------------------------------------|-----------|
| RC1 | #15372 | [v4.3.10-rc1](https://github.com/wazuh/wazuh/tree/v4.3.10-rc1) | In progress |
- _In progress: Fixes are being implemented._
- _In review: All the fixes have been implemented. The RC is now tagged and the QA process kicks off._
- _Closed: Fixes and QA process has finished._
## Tests
All the test results for this release can be found in the [v4.3.10 project](https://github.com/orgs/wazuh/projects/23/views/2).
## Fixes/Known issues
All the fixes and the issues detected in the testing phase that won't be solved in this version can be found in the [v4.3.10 project](https://github.com/orgs/wazuh/projects/23/views/1).
| 1.0 | Release 4.3.10 - Main issue gathering all the tasks regarding the preparation and validation of Wazuh version 4.3.10 release.
Close the issue only after the GA release.
## Release info
| | |
|---------------------------------------|------------------------------------------------------|
| Release name| Wazuh v4.3.10|
| Tag | https://github.com/wazuh/wazuh/tree/v4.3.10 |
| Branch | https://github.com/wazuh/wazuh/tree/4.3 |
| Changelog | https://github.com/wazuh/wazuh/blob/4.3/CHANGELOG.md |
| Latest release candidate (GA version) | N/A | |
## Release candidates
As usual, in order to publish, one or more release candidate versions are generated and fully tested, in the links below you can check the status and evolution of each version.
| Version | Issue | Tag | Status |
|---------|-------|-------------------------------------------------|-----------|
| RC1 | #15372 | [v4.3.10-rc1](https://github.com/wazuh/wazuh/tree/v4.3.10-rc1) | In progress |
- _In progress: Fixes are being implemented._
- _In review: All the fixes have been implemented. The RC is now tagged and the QA process kicks off._
- _Closed: Fixes and QA process has finished._
## Tests
All the test results for this release can be found in the [v4.3.10 project](https://github.com/orgs/wazuh/projects/23/views/2).
## Fixes/Known issues
All the fixes and the issues detected in the testing phase that won't be solved in this version can be found in the [v4.3.10 project](https://github.com/orgs/wazuh/projects/23/views/1).
| test | release main issue gathering all the tasks regarding the preparation and validation of wazuh version release close the issue only after the ga release release info release name wazuh tag branch changelog latest release candidate ga version n a release candidates as usual in order to publish one or more release candidate versions are generated and fully tested in the links below you can check the status and evolution of each version version issue tag status in progress in progress fixes are being implemented in review all the fixes have been implemented the rc is now tagged and the qa process kicks off closed fixes and qa process has finished tests all the test results for this release can be found in the fixes known issues all the fixes and the issues detected in the testing phase that won t be solved in this version can be found in the | 1 |
298,388 | 25,821,633,471 | IssuesEvent | 2022-12-12 10:00:16 | hazelcast/hazelcast | https://api.github.com/repos/hazelcast/hazelcast | closed | com.hazelcast.client.listeners.MultiMapEntryListenerOnReconnectTest.testListenersTerminateRandomNode_smart [API-1656] | Team: Client Type: Test-Failure Source: Internal to-client-jira | _5.1.z_ (commit 6caccfd1b9c4bcbe50bbbcca554594e83864b8c7)
Failed on Openj9-11: https://jenkins.hazelcast.com/view/Official%20Builds/job/Hazelcast-5.maintenance-Openj9-11/53/testReport/com.hazelcast.client.listeners/MultiMapEntryListenerOnReconnectTest/testListenersTerminateRandomNode_smart/
<details><summary>Stacktrace:</summary>
```
java.lang.AssertionError: Received event count is 9 but it is expected to stay at 10 expected:<10> but was:<9>
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.failNotEquals(Assert.java:835)
at org.junit.Assert.assertEquals(Assert.java:647)
at com.hazelcast.client.listeners.AbstractListenersOnReconnectTest.lambda$validateListenerFunctionality$4(AbstractListenersOnReconnectTest.java:399)
at com.hazelcast.client.listeners.AbstractListenersOnReconnectTest$$Lambda$6259/0x0000000000000000.run(Unknown Source)
at com.hazelcast.test.HazelcastTestSupport.assertTrueAllTheTime(HazelcastTestSupport.java:1181)
at com.hazelcast.client.listeners.AbstractListenersOnReconnectTest.validateListenerFunctionality(AbstractListenersOnReconnectTest.java:397)
at com.hazelcast.client.listeners.AbstractListenersOnReconnectTest.validateRegistrationsAndListenerFunctionality(AbstractListenersOnReconnectTest.java:332)
at com.hazelcast.client.listeners.AbstractListenersOnReconnectTest.testListenersTerminateRandomNode(AbstractListenersOnReconnectTest.java:139)
at com.hazelcast.client.listeners.AbstractListenersOnReconnectTest.testListenersTerminateRandomNode_smart(AbstractListenersOnReconnectTest.java:105)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:115)
at com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:107)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.lang.Thread.run(Thread.java:866)
```
</details>
Standard output can be found here - https://console.aws.amazon.com/s3/buckets/j-artifacts/Hazelcast-5.maintenance-Openj9-11/53/ | 1.0 | com.hazelcast.client.listeners.MultiMapEntryListenerOnReconnectTest.testListenersTerminateRandomNode_smart [API-1656] - _5.1.z_ (commit 6caccfd1b9c4bcbe50bbbcca554594e83864b8c7)
Failed on Openj9-11: https://jenkins.hazelcast.com/view/Official%20Builds/job/Hazelcast-5.maintenance-Openj9-11/53/testReport/com.hazelcast.client.listeners/MultiMapEntryListenerOnReconnectTest/testListenersTerminateRandomNode_smart/
<details><summary>Stacktrace:</summary>
```
java.lang.AssertionError: Received event count is 9 but it is expected to stay at 10 expected:<10> but was:<9>
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.failNotEquals(Assert.java:835)
at org.junit.Assert.assertEquals(Assert.java:647)
at com.hazelcast.client.listeners.AbstractListenersOnReconnectTest.lambda$validateListenerFunctionality$4(AbstractListenersOnReconnectTest.java:399)
at com.hazelcast.client.listeners.AbstractListenersOnReconnectTest$$Lambda$6259/0x0000000000000000.run(Unknown Source)
at com.hazelcast.test.HazelcastTestSupport.assertTrueAllTheTime(HazelcastTestSupport.java:1181)
at com.hazelcast.client.listeners.AbstractListenersOnReconnectTest.validateListenerFunctionality(AbstractListenersOnReconnectTest.java:397)
at com.hazelcast.client.listeners.AbstractListenersOnReconnectTest.validateRegistrationsAndListenerFunctionality(AbstractListenersOnReconnectTest.java:332)
at com.hazelcast.client.listeners.AbstractListenersOnReconnectTest.testListenersTerminateRandomNode(AbstractListenersOnReconnectTest.java:139)
at com.hazelcast.client.listeners.AbstractListenersOnReconnectTest.testListenersTerminateRandomNode_smart(AbstractListenersOnReconnectTest.java:105)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:115)
at com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:107)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.lang.Thread.run(Thread.java:866)
```
</details>
Standard output can be found here - https://console.aws.amazon.com/s3/buckets/j-artifacts/Hazelcast-5.maintenance-Openj9-11/53/ | test | com hazelcast client listeners multimapentrylisteneronreconnecttest testlistenersterminaterandomnode smart z commit failed on stacktrace java lang assertionerror received event count is but it is expected to stay at expected but was at org junit assert fail assert java at org junit assert failnotequals assert java at org junit assert assertequals assert java at com hazelcast client listeners abstractlistenersonreconnecttest lambda validatelistenerfunctionality abstractlistenersonreconnecttest java at com hazelcast client listeners abstractlistenersonreconnecttest lambda run unknown source at com hazelcast test hazelcasttestsupport asserttrueallthetime hazelcasttestsupport java at com hazelcast client listeners abstractlistenersonreconnecttest validatelistenerfunctionality abstractlistenersonreconnecttest java at com hazelcast client listeners abstractlistenersonreconnecttest validateregistrationsandlistenerfunctionality abstractlistenersonreconnecttest java at com hazelcast client listeners abstractlistenersonreconnecttest testlistenersterminaterandomnode abstractlistenersonreconnecttest java at com hazelcast client listeners abstractlistenersonreconnecttest testlistenersterminaterandomnode smart abstractlistenersonreconnecttest java at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base 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 com hazelcast test failontimeoutstatement callablestatement call failontimeoutstatement java at com hazelcast test failontimeoutstatement callablestatement call failontimeoutstatement java at java base java util concurrent futuretask run futuretask java at java base java lang thread run thread java standard output can be found here | 1 |
46,731 | 13,181,009,217 | IssuesEvent | 2020-08-12 13:42:09 | mibo32/fitbit-api-example-java | https://api.github.com/repos/mibo32/fitbit-api-example-java | opened | CVE-2020-11620 (High) detected in jackson-databind-2.8.1.jar | security vulnerability | ## CVE-2020-11620 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.8.1.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /tmp/ws-scm/fitbit-api-example-java/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.8.1/jackson-databind-2.8.1.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-1.4.0.RELEASE.jar (Root Library)
- :x: **jackson-databind-2.8.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/mibo32/fitbit-api-example-java/commit/fdd0855fc8f3b846f83506299759cd9cc820e5d2">fdd0855fc8f3b846f83506299759cd9cc820e5d2</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>
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.jelly.impl.Embedded (aka commons-jelly).
<p>Publish Date: 2020-04-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11620>CVE-2020-11620</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>
<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-2020-11620">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11620</a></p>
<p>Release Date: 2020-04-07</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.4</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-2020-11620 (High) detected in jackson-databind-2.8.1.jar - ## CVE-2020-11620 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.8.1.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /tmp/ws-scm/fitbit-api-example-java/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.8.1/jackson-databind-2.8.1.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-1.4.0.RELEASE.jar (Root Library)
- :x: **jackson-databind-2.8.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/mibo32/fitbit-api-example-java/commit/fdd0855fc8f3b846f83506299759cd9cc820e5d2">fdd0855fc8f3b846f83506299759cd9cc820e5d2</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>
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.jelly.impl.Embedded (aka commons-jelly).
<p>Publish Date: 2020-04-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11620>CVE-2020-11620</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>
<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-2020-11620">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11620</a></p>
<p>Release Date: 2020-04-07</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve high detected in jackson databind jar cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file tmp ws scm fitbit api example java pom xml path to vulnerable library home wss scanner repository com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy spring boot starter web release jar root library x jackson databind jar vulnerable library found in head commit a href vulnerability details fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to org apache commons jelly impl embedded aka commons jelly 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 suggested fix type upgrade version origin a href release date fix resolution com fasterxml jackson core jackson databind step up your open source security game with whitesource | 0 |
19,161 | 3,423,372,397 | IssuesEvent | 2015-12-09 06:01:19 | joyent/sdc-adminui | https://api.github.com/repos/joyent/sdc-adminui | closed | Given a network, provision IPs on it with specific MAC addreses | enhancement need design review | Given a network, provision IPs on it with specific MAC addreses.
For instance on ovh (dedicated host), you can buy ip subnets, however you need to pre-generate them in their admin menu.
It would be helpful if I was able to prefill the entire subnet with mac addresses rather than use these commands manually:
sdc sdc-napi /nics -X POST -d '{ "vlan_id": 0, "nic_tag": "external", "ip" :"xxx.xxx.xxx.xxx", "primary": true, "owner_uuid": "UUID", "belongs_to_uuid": "UUID", "network_uuid": "UUID", "belongs_to_type": "zone", "mac":"00:00:00:00:00:00"}'
sdc sdc-vmapi /vms/UUID?action=add_nics -X POST -d '{"macs":"00:00:00:00:00:00"}' | 1.0 | Given a network, provision IPs on it with specific MAC addreses - Given a network, provision IPs on it with specific MAC addreses.
For instance on ovh (dedicated host), you can buy ip subnets, however you need to pre-generate them in their admin menu.
It would be helpful if I was able to prefill the entire subnet with mac addresses rather than use these commands manually:
sdc sdc-napi /nics -X POST -d '{ "vlan_id": 0, "nic_tag": "external", "ip" :"xxx.xxx.xxx.xxx", "primary": true, "owner_uuid": "UUID", "belongs_to_uuid": "UUID", "network_uuid": "UUID", "belongs_to_type": "zone", "mac":"00:00:00:00:00:00"}'
sdc sdc-vmapi /vms/UUID?action=add_nics -X POST -d '{"macs":"00:00:00:00:00:00"}' | non_test | given a network provision ips on it with specific mac addreses given a network provision ips on it with specific mac addreses for instance on ovh dedicated host you can buy ip subnets however you need to pre generate them in their admin menu it would be helpful if i was able to prefill the entire subnet with mac addresses rather than use these commands manually sdc sdc napi nics x post d vlan id nic tag external ip xxx xxx xxx xxx primary true owner uuid uuid belongs to uuid uuid network uuid uuid belongs to type zone mac sdc sdc vmapi vms uuid action add nics x post d macs | 0 |
101,188 | 8,780,599,854 | IssuesEvent | 2018-12-19 17:47:39 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | closed | Gutenberg translation broken only in multisites | Multisite Needs Testing i18n | **Describe the bug**
When using multisite (folders) the translation works ok only in main site, in children sites the translation is not fully working.
**To Reproduce**
Steps to reproduce the behavior:
1. Install WP multisite (Folder)
2. Create new site
3. Change new site language to Portugues or Spanish
4. Go to gutenberg Editor and see missing translations.
**Expected behavior**
The translations are missing
**Screenshots**
If applicable, add screenshots to help explain your problem.
1) Main site gutenberg screenshot:
2) Subsite gutenberg screenshot
**Desktop (please complete the following information):**
- OS: Debian
- Browser: Chrome, Safari, Firefox.
- Version Any
**Additional context**
- Using Wordpress Version 5.0.1
| 1.0 | Gutenberg translation broken only in multisites - **Describe the bug**
When using multisite (folders) the translation works ok only in main site, in children sites the translation is not fully working.
**To Reproduce**
Steps to reproduce the behavior:
1. Install WP multisite (Folder)
2. Create new site
3. Change new site language to Portugues or Spanish
4. Go to gutenberg Editor and see missing translations.
**Expected behavior**
The translations are missing
**Screenshots**
If applicable, add screenshots to help explain your problem.
1) Main site gutenberg screenshot:
2) Subsite gutenberg screenshot
**Desktop (please complete the following information):**
- OS: Debian
- Browser: Chrome, Safari, Firefox.
- Version Any
**Additional context**
- Using Wordpress Version 5.0.1
| test | gutenberg translation broken only in multisites describe the bug when using multisite folders the translation works ok only in main site in children sites the translation is not fully working to reproduce steps to reproduce the behavior install wp multisite folder create new site change new site language to portugues or spanish go to gutenberg editor and see missing translations expected behavior the translations are missing screenshots if applicable add screenshots to help explain your problem main site gutenberg screenshot subsite gutenberg screenshot desktop please complete the following information os debian browser chrome safari firefox version any additional context using wordpress version | 1 |
620,478 | 19,563,199,358 | IssuesEvent | 2022-01-03 19:19:14 | ScottUK/ladojrp-issues | https://api.github.com/repos/ScottUK/ladojrp-issues | closed | LACD Rank Permissions | Part 2 | Class: enhancement Priority: medium Scope: voice / web | **Describe the feature you'd like implemented**
The ability for ranks to assign ranks to dispatchers once reached Supervisor+
**Link to the resource if it already exists**
N/A
**Additional context**
The ability for the following to be changed/fixed on TS:
1) Supervisory Dispatcher able to assign **all ranks below their rank.**
2) Assistant Manager able to assign any ranks below Supervisor **(Same as supervisor- Below Supervisor)**
3) Manager able to assign any ranks below Assistant Manager **(Able to assign supervisor rank)**
4) Assistant Director being able to assign any ranks below Manager **(Able to assign Assistant Manager)**
5) Deputy Director being able to assign any ranks below Assistant Director **(Able to assign Manager)**
6) Director being able to **assign any ranks, including director (If able) in the LACD department.**
This will allow for max efficiency within the department as it doesn't require the highest to be on to assign ranks. The ability to assign these ranks will be monitored and will be held to a high standard. If broken, met with consequences or termination.
Thank you,
Alvarez
LACD Director
Alvarez#2161 | 1.0 | LACD Rank Permissions | Part 2 - **Describe the feature you'd like implemented**
The ability for ranks to assign ranks to dispatchers once reached Supervisor+
**Link to the resource if it already exists**
N/A
**Additional context**
The ability for the following to be changed/fixed on TS:
1) Supervisory Dispatcher able to assign **all ranks below their rank.**
2) Assistant Manager able to assign any ranks below Supervisor **(Same as supervisor- Below Supervisor)**
3) Manager able to assign any ranks below Assistant Manager **(Able to assign supervisor rank)**
4) Assistant Director being able to assign any ranks below Manager **(Able to assign Assistant Manager)**
5) Deputy Director being able to assign any ranks below Assistant Director **(Able to assign Manager)**
6) Director being able to **assign any ranks, including director (If able) in the LACD department.**
This will allow for max efficiency within the department as it doesn't require the highest to be on to assign ranks. The ability to assign these ranks will be monitored and will be held to a high standard. If broken, met with consequences or termination.
Thank you,
Alvarez
LACD Director
Alvarez#2161 | non_test | lacd rank permissions part describe the feature you d like implemented the ability for ranks to assign ranks to dispatchers once reached supervisor link to the resource if it already exists n a additional context the ability for the following to be changed fixed on ts supervisory dispatcher able to assign all ranks below their rank assistant manager able to assign any ranks below supervisor same as supervisor below supervisor manager able to assign any ranks below assistant manager able to assign supervisor rank assistant director being able to assign any ranks below manager able to assign assistant manager deputy director being able to assign any ranks below assistant director able to assign manager director being able to assign any ranks including director if able in the lacd department this will allow for max efficiency within the department as it doesn t require the highest to be on to assign ranks the ability to assign these ranks will be monitored and will be held to a high standard if broken met with consequences or termination thank you alvarez lacd director alvarez | 0 |
267,672 | 23,313,102,120 | IssuesEvent | 2022-08-08 10:01:26 | mozilla-mobile/fenix | https://api.github.com/repos/mozilla-mobile/fenix | closed | Intermittent UI test failure - < HistoryTest.deleteAllHistoryTest> | eng:intermittent-test eng:ui-test | ### Firebase Test Run: [Firebase link](https://console.firebase.google.com/u/0/project/moz-fenix/testlab/histories/bh.66b7091e15d53d45/matrices/4973210559128028868/executions/bs.a770f0d8bdd878f8/testcases/1/test-cases)
### Stacktrace:
androidx.test.espresso.NoMatchingViewException: No views in hierarchy found matching: view.getId() is <2131362998/org.mozilla.fenix.debug:id/snackbar_text>
View Hierarchy:
+>DecorView{id=-1, visibility=VISIBLE, width=1080, height=1920, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params={(0,0)(fillxfill) sim={adjust=resize} ty=BASE_APPLICATION wanim=0x7f14034f
fl=LAYOUT_IN_SCREEN LAYOUT_INSET_DECOR HARDWARE_ACCELERATED DRAWS_SYSTEM_BAR_BACKGROUNDS
pfl=FORCE_DRAW_STATUS_BAR_BACKGROUND FIT_INSETS_CONTROLLED
vsysui=LIGHT_STATUS_BAR LIGHT_NAVIGATION_BAR
fitSides=}, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=2}
|
+->LinearLayout{id=-1, visibility=VISIBLE, width=1080, height=1788, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.FrameLayout$LayoutParams@20eecaa, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=2}
|
+-->ViewStub{id=16908719, res-name=action_mode_bar_stub, visibility=GONE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=android.widget.LinearLayout$LayoutParams@1f2c09b, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0}
|
+-->FrameLayout{id=-1, visibility=VISIBLE, width=1080, height=1722, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.LinearLayout$LayoutParams@ded6c38, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=66.0, child-count=1}
|
+--->FitWindowsLinearLayout{id=2131361876, res-name=action_bar_root, visibility=VISIBLE, width=1080, height=1722, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.FrameLayout$LayoutParams@8c72976, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=2}
|
+---->ViewStubCompat{id=2131361946, res-name=action_mode_bar_stub, visibility=GONE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=android.widget.LinearLayout$LayoutParams@2b2cb77, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0}
|
+---->ContentFrameLayout{id=16908290, res-name=content, visibility=VISIBLE, width=1080, height=1722, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.LinearLayout$LayoutParams@52913e4, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=1}
|
+----->HomeActivityRootLinearLayout{id=2131362873, res-name=rootContainer, visibility=VISIBLE, width=1080, height=1722, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.FrameLayout$LayoutParams@ce5204d, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=2}
|
+------>Toolbar{id=2131362725, res-name=navigationToolbar, visibility=VISIBLE, width=1080, height=154, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.LinearLayout$LayoutParams@dfea813, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=4}
|
+------->FrameLayout{id=2131363128, res-name=toolbar_child_container, visibility=GONE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=androidx.appcompat.widget.Toolbar$LayoutParams@e558a50, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=0}
|
+------->AppCompatTextView{id=-1, visibility=VISIBLE, width=190, height=70, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=androidx.appcompat.widget.Toolbar$LayoutParams@4707449, tag=null, root-is-layout-requested=false, has-input-connection=false, x=198.0, y=42.0, text=History, input-type=0, ime-target=false, has-links=false}
|
+------->AppCompatImageButton{id=-1, desc=Navigate up, visibility=VISIBLE, width=154, height=154, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=true, is-enabled=true, is-focused=false, is-focusable=true, is-layout-requested=false, is-selected=false, layout-params=androidx.appcompat.widget.Toolbar$LayoutParams@c5f14e, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0}
|
+------->ActionMenuView{id=-1, visibility=VISIBLE, width=264, height=154, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=androidx.appcompat.widget.Toolbar$LayoutParams@421b26f, tag=null, root-is-layout-requested=false, has-input-connection=false, x=816.0, y=0.0, child-count=2}
|
+-------->ActionMenuItemView{id=2131362472, res-name=history_search, desc=Enter search terms, visibility=VISIBLE, width=132, height=132, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=true, is-enabled=true, is-focused=false, is-focusable=true, is-layout-requested=false, is-selected=false, layout-params=androidx.appcompat.widget.ActionMenuView$LayoutParams@790fb7c, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=11.0, text=, input-type=0, ime-target=false, has-links=false}
|
+-------->ActionMenuItemView{id=2131362466, res-name=history_delete_all, desc=Delete history, visibility=VISIBLE, width=132, height=132, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=true, is-enabled=true, is-focused=false, is-focusable=true, is-layout-requested=false, is-selected=false, layout-params=androidx.appcompat.widget.ActionMenuView$LayoutParams@3430c05, tag=null, root-is-layout-requested=false, has-input-connection=false, x=132.0, y=11.0, text=, input-type=0, ime-target=false, has-links=false}
|
+------>FragmentContainerView{id=2131362230, res-name=container, visibility=VISIBLE, width=1080, height=1568, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.LinearLayout$LayoutParams@213d45a, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=154.0, child-count=1}
|
+------->FragmentContainerView{id=2131362230, res-name=container, visibility=VISIBLE, width=1080, height=1568, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.FrameLayout$LayoutParams@4c1068b, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=1}
|
+-------->FrameLayout{id=2131362462, res-name=historyLayout, visibility=VISIBLE, width=1080, height=1568, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.FrameLayout$LayoutParams@b05368, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=1}
|
+--------->ConstraintLayout{id=2131362473, res-name=history_wrapper, visibility=VISIBLE, width=1080, height=1568, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.FrameLayout$LayoutParams@feb3e14, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=6}
|
+---------->ProgressBar{id=2131362824, res-name=progress_bar, visibility=VISIBLE, width=1080, height=22, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@b8bb6bd, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=-8.26875}
|
+---------->View{id=2131363142, res-name=top_spacer, visibility=GONE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@f5894b2, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0}
|
+---------->ConstraintLayout{id=2131362850, res-name=recently_closed_nav_empty, visibility=GONE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=true, is-enabled=true, is-focused=false, is-focusable=true, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@8c201b9, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=3}
|
+----------->AppCompatImageView{id=2131362501, res-name=icon, visibility=VISIBLE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@53749fe, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0}
|
+----------->AppCompatTextView{id=2131362852, res-name=recently_closed_tabs_header, visibility=VISIBLE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@98a155f, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, text=Recently closed tabs, input-type=0, ime-target=false, has-links=false}
|
+----------->AppCompatTextView{id=2131362851, res-name=recently_closed_tabs_description, visibility=VISIBLE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@8c83bac, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, text=0 tabs, input-type=0, ime-target=false, has-links=false}
|
+---------->ConstraintLayout{id=2131363050, res-name=synced_history_nav_empty, visibility=GONE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=true, is-enabled=true, is-focused=false, is-focusable=true, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@b64a87b, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=2}
|
+----------->AppCompatImageView{id=2131362501, res-name=icon, visibility=VISIBLE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@f536698, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0}
|
+----------->AppCompatTextView{id=2131363048, res-name=synced_history_header, visibility=VISIBLE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@1552ef1, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, text=Synced from other devices, input-type=0, ime-target=false, has-links=false}
|
+---------->AppCompatTextView{id=2131362467, res-name=history_empty_view, visibility=GONE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@4f89ad6, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, text=No history here, input-type=0, ime-target=false, has-links=false}
|
+---------->SwipeRefreshLayout{id=2131363044, res-name=swipe_refresh, visibility=VISIBLE, width=1080, height=1568, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@48b5157, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=2}
|
+----------->CircleImageView{id=-1, visibility=GONE, width=110, height=110, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.view.ViewGroup$LayoutParams@2645444, tag=null, root-is-layout-requested=false, has-input-connection=false, x=485.0, y=-110.0}
|
+----------->RecyclerView{id=2131362469, res-name=history_list, visibility=VISIBLE, width=1080, height=1568, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=true, is-layout-requested=false, is-selected=false, layout-params=android.view.ViewGroup$LayoutParams@6fcc92d, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=1}
|
+------------>LinearLayout{id=-1, visibility=VISIBLE, width=1080, height=644, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=androidx.recyclerview.widget.RecyclerView$LayoutParams@4bb8e62, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=6}
|
+------------->View{id=2131363142, res-name=top_spacer, visibility=VISIBLE, width=1080, height=22, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.LinearLayout$LayoutParams@b09abf3, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0}
|
+------------->ConstraintLayout{id=2131362850, res-name=recently_closed_nav_empty, visibility=VISIBLE, width=1080, height=154, has-focus=false, has-focusabl
### Build: 7/13 Main
┆Issue is synchronized with this [Jira Task](https://mozilla-hub.atlassian.net/browse/FNXV2-20996)
┆Link To Issue: https://mozilla-hub.atlassian.net/browse/FNXV2-20996
| 2.0 | Intermittent UI test failure - < HistoryTest.deleteAllHistoryTest> - ### Firebase Test Run: [Firebase link](https://console.firebase.google.com/u/0/project/moz-fenix/testlab/histories/bh.66b7091e15d53d45/matrices/4973210559128028868/executions/bs.a770f0d8bdd878f8/testcases/1/test-cases)
### Stacktrace:
androidx.test.espresso.NoMatchingViewException: No views in hierarchy found matching: view.getId() is <2131362998/org.mozilla.fenix.debug:id/snackbar_text>
View Hierarchy:
+>DecorView{id=-1, visibility=VISIBLE, width=1080, height=1920, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params={(0,0)(fillxfill) sim={adjust=resize} ty=BASE_APPLICATION wanim=0x7f14034f
fl=LAYOUT_IN_SCREEN LAYOUT_INSET_DECOR HARDWARE_ACCELERATED DRAWS_SYSTEM_BAR_BACKGROUNDS
pfl=FORCE_DRAW_STATUS_BAR_BACKGROUND FIT_INSETS_CONTROLLED
vsysui=LIGHT_STATUS_BAR LIGHT_NAVIGATION_BAR
fitSides=}, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=2}
|
+->LinearLayout{id=-1, visibility=VISIBLE, width=1080, height=1788, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.FrameLayout$LayoutParams@20eecaa, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=2}
|
+-->ViewStub{id=16908719, res-name=action_mode_bar_stub, visibility=GONE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=android.widget.LinearLayout$LayoutParams@1f2c09b, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0}
|
+-->FrameLayout{id=-1, visibility=VISIBLE, width=1080, height=1722, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.LinearLayout$LayoutParams@ded6c38, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=66.0, child-count=1}
|
+--->FitWindowsLinearLayout{id=2131361876, res-name=action_bar_root, visibility=VISIBLE, width=1080, height=1722, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.FrameLayout$LayoutParams@8c72976, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=2}
|
+---->ViewStubCompat{id=2131361946, res-name=action_mode_bar_stub, visibility=GONE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=android.widget.LinearLayout$LayoutParams@2b2cb77, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0}
|
+---->ContentFrameLayout{id=16908290, res-name=content, visibility=VISIBLE, width=1080, height=1722, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.LinearLayout$LayoutParams@52913e4, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=1}
|
+----->HomeActivityRootLinearLayout{id=2131362873, res-name=rootContainer, visibility=VISIBLE, width=1080, height=1722, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.FrameLayout$LayoutParams@ce5204d, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=2}
|
+------>Toolbar{id=2131362725, res-name=navigationToolbar, visibility=VISIBLE, width=1080, height=154, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.LinearLayout$LayoutParams@dfea813, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=4}
|
+------->FrameLayout{id=2131363128, res-name=toolbar_child_container, visibility=GONE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=androidx.appcompat.widget.Toolbar$LayoutParams@e558a50, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=0}
|
+------->AppCompatTextView{id=-1, visibility=VISIBLE, width=190, height=70, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=androidx.appcompat.widget.Toolbar$LayoutParams@4707449, tag=null, root-is-layout-requested=false, has-input-connection=false, x=198.0, y=42.0, text=History, input-type=0, ime-target=false, has-links=false}
|
+------->AppCompatImageButton{id=-1, desc=Navigate up, visibility=VISIBLE, width=154, height=154, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=true, is-enabled=true, is-focused=false, is-focusable=true, is-layout-requested=false, is-selected=false, layout-params=androidx.appcompat.widget.Toolbar$LayoutParams@c5f14e, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0}
|
+------->ActionMenuView{id=-1, visibility=VISIBLE, width=264, height=154, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=androidx.appcompat.widget.Toolbar$LayoutParams@421b26f, tag=null, root-is-layout-requested=false, has-input-connection=false, x=816.0, y=0.0, child-count=2}
|
+-------->ActionMenuItemView{id=2131362472, res-name=history_search, desc=Enter search terms, visibility=VISIBLE, width=132, height=132, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=true, is-enabled=true, is-focused=false, is-focusable=true, is-layout-requested=false, is-selected=false, layout-params=androidx.appcompat.widget.ActionMenuView$LayoutParams@790fb7c, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=11.0, text=, input-type=0, ime-target=false, has-links=false}
|
+-------->ActionMenuItemView{id=2131362466, res-name=history_delete_all, desc=Delete history, visibility=VISIBLE, width=132, height=132, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=true, is-enabled=true, is-focused=false, is-focusable=true, is-layout-requested=false, is-selected=false, layout-params=androidx.appcompat.widget.ActionMenuView$LayoutParams@3430c05, tag=null, root-is-layout-requested=false, has-input-connection=false, x=132.0, y=11.0, text=, input-type=0, ime-target=false, has-links=false}
|
+------>FragmentContainerView{id=2131362230, res-name=container, visibility=VISIBLE, width=1080, height=1568, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.LinearLayout$LayoutParams@213d45a, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=154.0, child-count=1}
|
+------->FragmentContainerView{id=2131362230, res-name=container, visibility=VISIBLE, width=1080, height=1568, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.FrameLayout$LayoutParams@4c1068b, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=1}
|
+-------->FrameLayout{id=2131362462, res-name=historyLayout, visibility=VISIBLE, width=1080, height=1568, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.FrameLayout$LayoutParams@b05368, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=1}
|
+--------->ConstraintLayout{id=2131362473, res-name=history_wrapper, visibility=VISIBLE, width=1080, height=1568, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.FrameLayout$LayoutParams@feb3e14, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=6}
|
+---------->ProgressBar{id=2131362824, res-name=progress_bar, visibility=VISIBLE, width=1080, height=22, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@b8bb6bd, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=-8.26875}
|
+---------->View{id=2131363142, res-name=top_spacer, visibility=GONE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@f5894b2, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0}
|
+---------->ConstraintLayout{id=2131362850, res-name=recently_closed_nav_empty, visibility=GONE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=true, is-enabled=true, is-focused=false, is-focusable=true, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@8c201b9, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=3}
|
+----------->AppCompatImageView{id=2131362501, res-name=icon, visibility=VISIBLE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@53749fe, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0}
|
+----------->AppCompatTextView{id=2131362852, res-name=recently_closed_tabs_header, visibility=VISIBLE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@98a155f, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, text=Recently closed tabs, input-type=0, ime-target=false, has-links=false}
|
+----------->AppCompatTextView{id=2131362851, res-name=recently_closed_tabs_description, visibility=VISIBLE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@8c83bac, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, text=0 tabs, input-type=0, ime-target=false, has-links=false}
|
+---------->ConstraintLayout{id=2131363050, res-name=synced_history_nav_empty, visibility=GONE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=true, is-enabled=true, is-focused=false, is-focusable=true, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@b64a87b, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=2}
|
+----------->AppCompatImageView{id=2131362501, res-name=icon, visibility=VISIBLE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@f536698, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0}
|
+----------->AppCompatTextView{id=2131363048, res-name=synced_history_header, visibility=VISIBLE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@1552ef1, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, text=Synced from other devices, input-type=0, ime-target=false, has-links=false}
|
+---------->AppCompatTextView{id=2131362467, res-name=history_empty_view, visibility=GONE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@4f89ad6, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, text=No history here, input-type=0, ime-target=false, has-links=false}
|
+---------->SwipeRefreshLayout{id=2131363044, res-name=swipe_refresh, visibility=VISIBLE, width=1080, height=1568, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=androidx.constraintlayout.widget.ConstraintLayout$LayoutParams@48b5157, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=2}
|
+----------->CircleImageView{id=-1, visibility=GONE, width=110, height=110, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.view.ViewGroup$LayoutParams@2645444, tag=null, root-is-layout-requested=false, has-input-connection=false, x=485.0, y=-110.0}
|
+----------->RecyclerView{id=2131362469, res-name=history_list, visibility=VISIBLE, width=1080, height=1568, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=true, is-layout-requested=false, is-selected=false, layout-params=android.view.ViewGroup$LayoutParams@6fcc92d, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=1}
|
+------------>LinearLayout{id=-1, visibility=VISIBLE, width=1080, height=644, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=androidx.recyclerview.widget.RecyclerView$LayoutParams@4bb8e62, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=6}
|
+------------->View{id=2131363142, res-name=top_spacer, visibility=VISIBLE, width=1080, height=22, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.LinearLayout$LayoutParams@b09abf3, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0}
|
+------------->ConstraintLayout{id=2131362850, res-name=recently_closed_nav_empty, visibility=VISIBLE, width=1080, height=154, has-focus=false, has-focusabl
### Build: 7/13 Main
┆Issue is synchronized with this [Jira Task](https://mozilla-hub.atlassian.net/browse/FNXV2-20996)
┆Link To Issue: https://mozilla-hub.atlassian.net/browse/FNXV2-20996
| test | intermittent ui test failure firebase test run stacktrace androidx test espresso nomatchingviewexception no views in hierarchy found matching view getid is view hierarchy decorview id visibility visible width height has focus false has focusable true has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params fillxfill sim adjust resize ty base application wanim fl layout in screen layout inset decor hardware accelerated draws system bar backgrounds pfl force draw status bar background fit insets controlled vsysui light status bar light navigation bar fitsides tag null root is layout requested false has input connection false x y child count linearlayout id visibility visible width height has focus false has focusable true has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params android widget framelayout layoutparams tag null root is layout requested false has input connection false x y child count viewstub id res name action mode bar stub visibility gone width height has focus false has focusable false has window focus true is clickable false is enabled true is focused false is focusable false is layout requested true is selected false layout params android widget linearlayout layoutparams tag null root is layout requested false has input connection false x y framelayout id visibility visible width height has focus false has focusable true has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params android widget linearlayout layoutparams tag null root is layout requested false has input connection false x y child count fitwindowslinearlayout id res name action bar root visibility visible width height has focus false has focusable true has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params android widget framelayout layoutparams tag null root is layout requested false has input connection false x y child count viewstubcompat id res name action mode bar stub visibility gone width height has focus false has focusable false has window focus true is clickable false is enabled true is focused false is focusable false is layout requested true is selected false layout params android widget linearlayout layoutparams tag null root is layout requested false has input connection false x y contentframelayout id res name content visibility visible width height has focus false has focusable true has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params android widget linearlayout layoutparams tag null root is layout requested false has input connection false x y child count homeactivityrootlinearlayout id res name rootcontainer visibility visible width height has focus false has focusable true has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params android widget framelayout layoutparams tag null root is layout requested false has input connection false x y child count toolbar id res name navigationtoolbar visibility visible width height has focus false has focusable false has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params android widget linearlayout layoutparams tag null root is layout requested false has input connection false x y child count framelayout id res name toolbar child container visibility gone width height has focus false has focusable false has window focus true is clickable false is enabled true is focused false is focusable false is layout requested true is selected false layout params androidx appcompat widget toolbar layoutparams tag null root is layout requested false has input connection false x y child count appcompattextview id visibility visible width height has focus false has focusable false has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params androidx appcompat widget toolbar layoutparams tag null root is layout requested false has input connection false x y text history input type ime target false has links false appcompatimagebutton id desc navigate up visibility visible width height has focus false has focusable false has window focus true is clickable true is enabled true is focused false is focusable true is layout requested false is selected false layout params androidx appcompat widget toolbar layoutparams tag null root is layout requested false has input connection false x y actionmenuview id visibility visible width height has focus false has focusable false has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params androidx appcompat widget toolbar layoutparams tag null root is layout requested false has input connection false x y child count actionmenuitemview id res name history search desc enter search terms visibility visible width height has focus false has focusable false has window focus true is clickable true is enabled true is focused false is focusable true is layout requested false is selected false layout params androidx appcompat widget actionmenuview layoutparams tag null root is layout requested false has input connection false x y text input type ime target false has links false actionmenuitemview id res name history delete all desc delete history visibility visible width height has focus false has focusable false has window focus true is clickable true is enabled true is focused false is focusable true is layout requested false is selected false layout params androidx appcompat widget actionmenuview layoutparams tag null root is layout requested false has input connection false x y text input type ime target false has links false fragmentcontainerview id res name container visibility visible width height has focus false has focusable true has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params android widget linearlayout layoutparams tag null root is layout requested false has input connection false x y child count fragmentcontainerview id res name container visibility visible width height has focus false has focusable true has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params android widget framelayout layoutparams tag null root is layout requested false has input connection false x y child count framelayout id res name historylayout visibility visible width height has focus false has focusable true has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params android widget framelayout layoutparams tag null root is layout requested false has input connection false x y child count constraintlayout id res name history wrapper visibility visible width height has focus false has focusable true has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params android widget framelayout layoutparams tag null root is layout requested false has input connection false x y child count progressbar id res name progress bar visibility visible width height has focus false has focusable false has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params androidx constraintlayout widget constraintlayout layoutparams tag null root is layout requested false has input connection false x y view id res name top spacer visibility gone width height has focus false has focusable false has window focus true is clickable false is enabled true is focused false is focusable false is layout requested true is selected false layout params androidx constraintlayout widget constraintlayout layoutparams tag null root is layout requested false has input connection false x y constraintlayout id res name recently closed nav empty visibility gone width height has focus false has focusable false has window focus true is clickable true is enabled true is focused false is focusable true is layout requested true is selected false layout params androidx constraintlayout widget constraintlayout layoutparams tag null root is layout requested false has input connection false x y child count appcompatimageview id res name icon visibility visible width height has focus false has focusable false has window focus true is clickable false is enabled true is focused false is focusable false is layout requested true is selected false layout params androidx constraintlayout widget constraintlayout layoutparams tag null root is layout requested false has input connection false x y appcompattextview id res name recently closed tabs header visibility visible width height has focus false has focusable false has window focus true is clickable false is enabled true is focused false is focusable false is layout requested true is selected false layout params androidx constraintlayout widget constraintlayout layoutparams tag null root is layout requested false has input connection false x y text recently closed tabs input type ime target false has links false appcompattextview id res name recently closed tabs description visibility visible width height has focus false has focusable false has window focus true is clickable false is enabled true is focused false is focusable false is layout requested true is selected false layout params androidx constraintlayout widget constraintlayout layoutparams tag null root is layout requested false has input connection false x y text tabs input type ime target false has links false constraintlayout id res name synced history nav empty visibility gone width height has focus false has focusable false has window focus true is clickable true is enabled true is focused false is focusable true is layout requested true is selected false layout params androidx constraintlayout widget constraintlayout layoutparams tag null root is layout requested false has input connection false x y child count appcompatimageview id res name icon visibility visible width height has focus false has focusable false has window focus true is clickable false is enabled true is focused false is focusable false is layout requested true is selected false layout params androidx constraintlayout widget constraintlayout layoutparams tag null root is layout requested false has input connection false x y appcompattextview id res name synced history header visibility visible width height has focus false has focusable false has window focus true is clickable false is enabled true is focused false is focusable false is layout requested true is selected false layout params androidx constraintlayout widget constraintlayout layoutparams tag null root is layout requested false has input connection false x y text synced from other devices input type ime target false has links false appcompattextview id res name history empty view visibility gone width height has focus false has focusable false has window focus true is clickable false is enabled true is focused false is focusable false is layout requested true is selected false layout params androidx constraintlayout widget constraintlayout layoutparams tag null root is layout requested false has input connection false x y text no history here input type ime target false has links false swiperefreshlayout id res name swipe refresh visibility visible width height has focus false has focusable true has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params androidx constraintlayout widget constraintlayout layoutparams tag null root is layout requested false has input connection false x y child count circleimageview id visibility gone width height has focus false has focusable false has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params android view viewgroup layoutparams tag null root is layout requested false has input connection false x y recyclerview id res name history list visibility visible width height has focus false has focusable true has window focus true is clickable false is enabled true is focused false is focusable true is layout requested false is selected false layout params android view viewgroup layoutparams tag null root is layout requested false has input connection false x y child count linearlayout id visibility visible width height has focus false has focusable true has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params androidx recyclerview widget recyclerview layoutparams tag null root is layout requested false has input connection false x y child count view id res name top spacer visibility visible width height has focus false has focusable false has window focus true is clickable false is enabled true is focused false is focusable false is layout requested false is selected false layout params android widget linearlayout layoutparams tag null root is layout requested false has input connection false x y constraintlayout id res name recently closed nav empty visibility visible width height has focus false has focusabl build main ┆issue is synchronized with this ┆link to issue | 1 |
236,443 | 19,541,521,608 | IssuesEvent | 2022-01-01 01:33:48 | scylladb/scylla | https://api.github.com/repos/scylladb/scylla | closed | scylla-gdb: scylla fiber is flaky | test gdb | We hit this quite frequently in next gating tests, e.g.
https://jenkins.scylladb.com/view/master/job/scylla-master/job/next/4360/artifact/testlog/x86_64_release/run.6588.log
```
*** CMD: scylla fiber $task
Provided pointer 0x00006000000af1f0 is not an object managed by seastar or not a task pointer
Traceback (most recent call last):
File "/jenkins/workspace/scylla-master/next/scylla/scylla-gdb.py", line 3355, in invoke
tptr, vptr, name = this_task
TypeError: cannot unpack non-iterable NoneType object
Traceback (most recent call last):
File "/jenkins/workspace/scylla-master/next/scylla/test/scylla-gdb/test.py", line 68, in <module>
dos('fiber $task')
File "/jenkins/workspace/scylla-master/next/scylla/test/scylla-gdb/test.py", line 19, in dos
return do('scylla ' + cmd, known_broken, loudly=True)
File "/jenkins/workspace/scylla-master/next/scylla/test/scylla-gdb/test.py", line 9, in do
ret = gdb.execute(cmd)
gdb.error: Error occurred in Python: cannot unpack non-iterable NoneType object
=== TEST.PY SUMMARY START ===
Test exited with code 255
```
@xemul can you please take a look at this?
| 1.0 | scylla-gdb: scylla fiber is flaky - We hit this quite frequently in next gating tests, e.g.
https://jenkins.scylladb.com/view/master/job/scylla-master/job/next/4360/artifact/testlog/x86_64_release/run.6588.log
```
*** CMD: scylla fiber $task
Provided pointer 0x00006000000af1f0 is not an object managed by seastar or not a task pointer
Traceback (most recent call last):
File "/jenkins/workspace/scylla-master/next/scylla/scylla-gdb.py", line 3355, in invoke
tptr, vptr, name = this_task
TypeError: cannot unpack non-iterable NoneType object
Traceback (most recent call last):
File "/jenkins/workspace/scylla-master/next/scylla/test/scylla-gdb/test.py", line 68, in <module>
dos('fiber $task')
File "/jenkins/workspace/scylla-master/next/scylla/test/scylla-gdb/test.py", line 19, in dos
return do('scylla ' + cmd, known_broken, loudly=True)
File "/jenkins/workspace/scylla-master/next/scylla/test/scylla-gdb/test.py", line 9, in do
ret = gdb.execute(cmd)
gdb.error: Error occurred in Python: cannot unpack non-iterable NoneType object
=== TEST.PY SUMMARY START ===
Test exited with code 255
```
@xemul can you please take a look at this?
| test | scylla gdb scylla fiber is flaky we hit this quite frequently in next gating tests e g cmd scylla fiber task provided pointer is not an object managed by seastar or not a task pointer traceback most recent call last file jenkins workspace scylla master next scylla scylla gdb py line in invoke tptr vptr name this task typeerror cannot unpack non iterable nonetype object traceback most recent call last file jenkins workspace scylla master next scylla test scylla gdb test py line in dos fiber task file jenkins workspace scylla master next scylla test scylla gdb test py line in dos return do scylla cmd known broken loudly true file jenkins workspace scylla master next scylla test scylla gdb test py line in do ret gdb execute cmd gdb error error occurred in python cannot unpack non iterable nonetype object test py summary start test exited with code xemul can you please take a look at this | 1 |
119,406 | 10,043,834,719 | IssuesEvent | 2019-07-19 08:33:16 | kyma-project/console | https://api.github.com/repos/kyma-project/console | reopened | Content-ui acceptance tests fails randomly | area/console bug test-failing | **Description**
Testing of content-ui randomly fail
See logs:
https://status.build.kyma-project.io/view/gcs/kyma-prow-logs/logs/post-master-kyma-gke-upgrade/1125757043936858116
https://status.build.kyma-project.io/view/gcs/kyma-prow-logs/logs/post-master-kyma-gke-upgrade/1126064822316699648
https://status.build.kyma-project.io/view/gcs/kyma-prow-logs/logs/post-master-kyma-gke-upgrade/1126527751927369728
**Expected result**
Test test-core-core-ui-acceptance doesn't fail without the reason.
**Actual result**
Random fails of docs-ui-test
**Steps to reproduce**
Random fails on standard kyma installation
**Troubleshooting**
<!-- Describe the steps you have already taken to solve the issue. -->
| 1.0 | Content-ui acceptance tests fails randomly - **Description**
Testing of content-ui randomly fail
See logs:
https://status.build.kyma-project.io/view/gcs/kyma-prow-logs/logs/post-master-kyma-gke-upgrade/1125757043936858116
https://status.build.kyma-project.io/view/gcs/kyma-prow-logs/logs/post-master-kyma-gke-upgrade/1126064822316699648
https://status.build.kyma-project.io/view/gcs/kyma-prow-logs/logs/post-master-kyma-gke-upgrade/1126527751927369728
**Expected result**
Test test-core-core-ui-acceptance doesn't fail without the reason.
**Actual result**
Random fails of docs-ui-test
**Steps to reproduce**
Random fails on standard kyma installation
**Troubleshooting**
<!-- Describe the steps you have already taken to solve the issue. -->
| test | content ui acceptance tests fails randomly description testing of content ui randomly fail see logs
expected result test test core core ui acceptance doesn t fail without the reason actual result random fails of docs ui test steps to reproduce random fails on standard kyma installation troubleshooting | 1 |
435,313 | 12,534,151,684 | IssuesEvent | 2020-06-04 18:53:59 | wso2/product-apim | https://api.github.com/repos/wso2/product-apim | closed | API versioning buggy in WSO2 APIM 3.1.0 | Priority/Normal Type/Bug | ### Description:
we found two issues with API versions which are really problematic with WSO2 APIM 3.1.
Issue1: The default version of API is pointing to the latest version when you create a new version of API.
Issue2: The default version of API is not accessible when you move the latest version of API to the CREATED state.
Please see the steps below to reproduce. Also, note these are exact steps that are working fine in APIM 2.6.0.
### Steps to reproduce:
Here is the scenario, all is done in the standard publisher UI of the vanilla version:
1. I have created API with version V1 and requesting it to be the default version. In synapse two files are created, one for V1 and one for the default version, which proxies to V1.
2. Issue #1: Then created Version V2 of API and request that it will not be the default version. Now I have three synapse files, for v1, v2, and for the default version. Looking at the synapse file of the default version I see that it proxies to V2, instead of V1 (recall that I requested the UI to leave V1 as default!).
3. Then made V1 as default again, and now once again the synapse file of the default version proxies to V1, as should be.
4. Issue #2: I have changed the state of V2, which is NOT the default version, to CREATED. What happens is that the synapse file of V2 is removed, which is ok, but also - the synapse file of the default version is removed - that is not ok and makes the URL of the default version return 404. Re-publishing V2 does not help: it returns the synapse file of V2, but the synapse file of the default version is still missing. Only when I go back to version V1, change it to CREATED and the PUBLISH it - the synapse file of the default version returns and also proxies to the correct version, V1, so the URL of the default version works again.
### Affected Product Version:
APIM 3.10
### Environment details (with versions):
- OS: Windows/CentoOS
---
### Optional Fields
#### Related Issues:
<!-- Any related issues from this/other repositories-->
#### Suggested Labels:
Priority/Urgent
#### Suggested Assignees:
<!--Only to be used by non-members--> | 1.0 | API versioning buggy in WSO2 APIM 3.1.0 - ### Description:
we found two issues with API versions which are really problematic with WSO2 APIM 3.1.
Issue1: The default version of API is pointing to the latest version when you create a new version of API.
Issue2: The default version of API is not accessible when you move the latest version of API to the CREATED state.
Please see the steps below to reproduce. Also, note these are exact steps that are working fine in APIM 2.6.0.
### Steps to reproduce:
Here is the scenario, all is done in the standard publisher UI of the vanilla version:
1. I have created API with version V1 and requesting it to be the default version. In synapse two files are created, one for V1 and one for the default version, which proxies to V1.
2. Issue #1: Then created Version V2 of API and request that it will not be the default version. Now I have three synapse files, for v1, v2, and for the default version. Looking at the synapse file of the default version I see that it proxies to V2, instead of V1 (recall that I requested the UI to leave V1 as default!).
3. Then made V1 as default again, and now once again the synapse file of the default version proxies to V1, as should be.
4. Issue #2: I have changed the state of V2, which is NOT the default version, to CREATED. What happens is that the synapse file of V2 is removed, which is ok, but also - the synapse file of the default version is removed - that is not ok and makes the URL of the default version return 404. Re-publishing V2 does not help: it returns the synapse file of V2, but the synapse file of the default version is still missing. Only when I go back to version V1, change it to CREATED and the PUBLISH it - the synapse file of the default version returns and also proxies to the correct version, V1, so the URL of the default version works again.
### Affected Product Version:
APIM 3.10
### Environment details (with versions):
- OS: Windows/CentoOS
---
### Optional Fields
#### Related Issues:
<!-- Any related issues from this/other repositories-->
#### Suggested Labels:
Priority/Urgent
#### Suggested Assignees:
<!--Only to be used by non-members--> | non_test | api versioning buggy in apim description we found two issues with api versions which are really problematic with apim the default version of api is pointing to the latest version when you create a new version of api the default version of api is not accessible when you move the latest version of api to the created state please see the steps below to reproduce also note these are exact steps that are working fine in apim steps to reproduce here is the scenario all is done in the standard publisher ui of the vanilla version i have created api with version and requesting it to be the default version in synapse two files are created one for and one for the default version which proxies to issue then created version of api and request that it will not be the default version now i have three synapse files for and for the default version looking at the synapse file of the default version i see that it proxies to instead of recall that i requested the ui to leave as default then made as default again and now once again the synapse file of the default version proxies to as should be issue i have changed the state of which is not the default version to created what happens is that the synapse file of is removed which is ok but also the synapse file of the default version is removed that is not ok and makes the url of the default version return re publishing does not help it returns the synapse file of but the synapse file of the default version is still missing only when i go back to version change it to created and the publish it the synapse file of the default version returns and also proxies to the correct version so the url of the default version works again affected product version apim environment details with versions os windows centoos optional fields related issues suggested labels priority urgent suggested assignees | 0 |
784,696 | 27,582,689,184 | IssuesEvent | 2023-03-08 17:16:49 | aws/aws-node-termination-handler | https://api.github.com/repos/aws/aws-node-termination-handler | closed | Migrate from `PodSecurityPolicy` to Pod Security Admission | Pending-Release Priority: Medium stalebot-ignore | **Describe the bug**
When running the end-to-end tests on Kubernetes server version 1.23, I get the following warning:
```
policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
```
**Steps to reproduce**
Run the following command on your local machine from the root of the repo:
```
test/k8s-local-cluster-test/run-test -v 1.23 -d
```
Then wait for it to build the image and start the cluster. After the first test starts running (e.g., "Running assertion script asg-lifecycle-sqs-test"), you'll see the warning above.
**Expected outcome**
We need to add support for Pod Security Admission before we can support Kubernetes server 1.25 ([expected release date August 2022](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.25#summary)). However, if we wish to maintain support for the most recent 6 Kubernetes versions (which would include 1.20 and 1.21 at that time), we will need to keep the existing PodSecurityPolicy specs or use a third-party solution, because support for built-in Pod Security Admission began in 1.22.
The migration guide is here: https://kubernetes.io/docs/tasks/configure-pod-container/migrate-from-psp/
`PodSecurityPolicy` is used in several places throughout the repository: https://github.com/aws/aws-node-termination-handler/search?q=PodSecurityPolicy
**Application Logs**
See above.
**Environment**
* NTH App Version: 1.16.3
* NTH Mode (IMDS/Queue processor): N/A
* OS/Arch: MacOS 12.3.1
* Kubernetes version: 1.23
* Installation method: Source code
| 1.0 | Migrate from `PodSecurityPolicy` to Pod Security Admission - **Describe the bug**
When running the end-to-end tests on Kubernetes server version 1.23, I get the following warning:
```
policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
```
**Steps to reproduce**
Run the following command on your local machine from the root of the repo:
```
test/k8s-local-cluster-test/run-test -v 1.23 -d
```
Then wait for it to build the image and start the cluster. After the first test starts running (e.g., "Running assertion script asg-lifecycle-sqs-test"), you'll see the warning above.
**Expected outcome**
We need to add support for Pod Security Admission before we can support Kubernetes server 1.25 ([expected release date August 2022](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.25#summary)). However, if we wish to maintain support for the most recent 6 Kubernetes versions (which would include 1.20 and 1.21 at that time), we will need to keep the existing PodSecurityPolicy specs or use a third-party solution, because support for built-in Pod Security Admission began in 1.22.
The migration guide is here: https://kubernetes.io/docs/tasks/configure-pod-container/migrate-from-psp/
`PodSecurityPolicy` is used in several places throughout the repository: https://github.com/aws/aws-node-termination-handler/search?q=PodSecurityPolicy
**Application Logs**
See above.
**Environment**
* NTH App Version: 1.16.3
* NTH Mode (IMDS/Queue processor): N/A
* OS/Arch: MacOS 12.3.1
* Kubernetes version: 1.23
* Installation method: Source code
| non_test | migrate from podsecuritypolicy to pod security admission describe the bug when running the end to end tests on kubernetes server version i get the following warning policy podsecuritypolicy is deprecated in unavailable in steps to reproduce run the following command on your local machine from the root of the repo test local cluster test run test v d then wait for it to build the image and start the cluster after the first test starts running e g running assertion script asg lifecycle sqs test you ll see the warning above expected outcome we need to add support for pod security admission before we can support kubernetes server however if we wish to maintain support for the most recent kubernetes versions which would include and at that time we will need to keep the existing podsecuritypolicy specs or use a third party solution because support for built in pod security admission began in the migration guide is here podsecuritypolicy is used in several places throughout the repository application logs see above environment nth app version nth mode imds queue processor n a os arch macos kubernetes version installation method source code | 0 |
616,750 | 19,319,787,340 | IssuesEvent | 2021-12-14 03:14:33 | webzard-io/sunmao-ui | https://api.github.com/repos/webzard-io/sunmao-ui | closed | Copy paste component | feature editor High Priority | # What should be copied when copy a component?
* properties
* trait(except slot trait)
* children | 1.0 | Copy paste component - # What should be copied when copy a component?
* properties
* trait(except slot trait)
* children | non_test | copy paste component what should be copied when copy a component properties trait except slot trait children | 0 |
19,345 | 3,768,374,452 | IssuesEvent | 2016-03-16 04:16:56 | googlefonts/fontbakery | https://api.github.com/repos/googlefonts/fontbakery | closed | Add test to nbspace check for U+0009 having same width as nbspace and space | P1 Quick testing | According to the Microsoft spec at https://www.microsoft.com/typography/otspec/recom.htm, the TAB (U+0009) character should have an advance width equal to that of space. | 1.0 | Add test to nbspace check for U+0009 having same width as nbspace and space - According to the Microsoft spec at https://www.microsoft.com/typography/otspec/recom.htm, the TAB (U+0009) character should have an advance width equal to that of space. | test | add test to nbspace check for u having same width as nbspace and space according to the microsoft spec at the tab u character should have an advance width equal to that of space | 1 |
56,557 | 6,522,110,910 | IssuesEvent | 2017-08-29 00:06:09 | rancher/rancher | https://api.github.com/repos/rancher/rancher | closed | Units used for Healthcheck parameters relating to Interval and Timeout is incorrect and there is no way to specify a unit. | area/cli kind/bug status/resolved status/to-test | Rancher server version - v1.6.8-rc6
Rancher cli version - v0.6.4-rc3
Steps to reproduce the problem:
When attempting to use units ("s" in my case) for --health-interval and --health-timeout , run command fails with ```Incorrect Usage``` error.
Command used:
```
./rancher run sangeetha/testnewhostrouting --blkio-weight 10 --cpu-period 1000 --cpu-quota 20000 --cpuset-mems 0 --health-cmd "curl - f http://localhost:80/name.html" --health-interval 2s --health-retries 3 --health-timeout 5s --ip 1.1.1.1 --kernel-memory 6000000 --memory-reservation 5000000 --memory-swappiness 100 --pids-limit -1 -P --shm-size 1024 --stop-signal SIGTERM
```
```FATA[0000] invalid value "2s" for flag -health-interval: strconv.ParseInt: parsing "2s": invalid syntax ```
```FATA[0000] invalid value "5s" for flag -health-timeout: strconv.ParseInt: parsing "5s": invalid syntax ```
But the usage option in the error message clearly indicate for units to be specified:
```
--health-cmd value Command to run to check health
--health-interval value Time between running the check (ms|s|m|h) (default 0s) (default: 0)
--health-retries value Consecutive failures needed to report unhealthy (default: 0)
--health-timeout value Maximum time to allow one check to run (ms|s|m|h) (default 0s) (default: 0)
```
When attempting to use --health-interval and --health-timeout with no units specified , docker inspect indicates a very big value set for Interval and Timeout
Command used:
```
./rancher run sangeetha/testnewhostrouting --blkio-weight 10 --cpu-period 1000 --cpu-quota 20000 --cpuset-mems 0 --health-cmd "curl - f http://localhost:80/name.html" --health-interval 2 --health-retries 3 --health-timeout 5 --ip 1.1.1.1 --kernel-memory 6000000 --memory-reservation 5000000 --memory-swappiness 100 --pids-limit -1 -P --shm-size 1024 --stop-signal SIGTERM
```
docker inspect:
```
"Healthcheck": {
"Test": [
"curl - f http://localhost:80/name.html"
],
"Interval": 2000000000,
"Timeout": 5000000000,
"Retries": 3
},
``` | 1.0 | Units used for Healthcheck parameters relating to Interval and Timeout is incorrect and there is no way to specify a unit. - Rancher server version - v1.6.8-rc6
Rancher cli version - v0.6.4-rc3
Steps to reproduce the problem:
When attempting to use units ("s" in my case) for --health-interval and --health-timeout , run command fails with ```Incorrect Usage``` error.
Command used:
```
./rancher run sangeetha/testnewhostrouting --blkio-weight 10 --cpu-period 1000 --cpu-quota 20000 --cpuset-mems 0 --health-cmd "curl - f http://localhost:80/name.html" --health-interval 2s --health-retries 3 --health-timeout 5s --ip 1.1.1.1 --kernel-memory 6000000 --memory-reservation 5000000 --memory-swappiness 100 --pids-limit -1 -P --shm-size 1024 --stop-signal SIGTERM
```
```FATA[0000] invalid value "2s" for flag -health-interval: strconv.ParseInt: parsing "2s": invalid syntax ```
```FATA[0000] invalid value "5s" for flag -health-timeout: strconv.ParseInt: parsing "5s": invalid syntax ```
But the usage option in the error message clearly indicate for units to be specified:
```
--health-cmd value Command to run to check health
--health-interval value Time between running the check (ms|s|m|h) (default 0s) (default: 0)
--health-retries value Consecutive failures needed to report unhealthy (default: 0)
--health-timeout value Maximum time to allow one check to run (ms|s|m|h) (default 0s) (default: 0)
```
When attempting to use --health-interval and --health-timeout with no units specified , docker inspect indicates a very big value set for Interval and Timeout
Command used:
```
./rancher run sangeetha/testnewhostrouting --blkio-weight 10 --cpu-period 1000 --cpu-quota 20000 --cpuset-mems 0 --health-cmd "curl - f http://localhost:80/name.html" --health-interval 2 --health-retries 3 --health-timeout 5 --ip 1.1.1.1 --kernel-memory 6000000 --memory-reservation 5000000 --memory-swappiness 100 --pids-limit -1 -P --shm-size 1024 --stop-signal SIGTERM
```
docker inspect:
```
"Healthcheck": {
"Test": [
"curl - f http://localhost:80/name.html"
],
"Interval": 2000000000,
"Timeout": 5000000000,
"Retries": 3
},
``` | test | units used for healthcheck parameters relating to interval and timeout is incorrect and there is no way to specify a unit rancher server version rancher cli version steps to reproduce the problem when attempting to use units s in my case for health interval and health timeout run command fails with incorrect usage error command used rancher run sangeetha testnewhostrouting blkio weight cpu period cpu quota cpuset mems health cmd curl f health interval health retries health timeout ip kernel memory memory reservation memory swappiness pids limit p shm size stop signal sigterm fata invalid value for flag health interval strconv parseint parsing invalid syntax fata invalid value for flag health timeout strconv parseint parsing invalid syntax but the usage option in the error message clearly indicate for units to be specified health cmd value command to run to check health health interval value time between running the check ms s m h default default health retries value consecutive failures needed to report unhealthy default health timeout value maximum time to allow one check to run ms s m h default default when attempting to use health interval and health timeout with no units specified docker inspect indicates a very big value set for interval and timeout command used rancher run sangeetha testnewhostrouting blkio weight cpu period cpu quota cpuset mems health cmd curl f health interval health retries health timeout ip kernel memory memory reservation memory swappiness pids limit p shm size stop signal sigterm docker inspect healthcheck test curl f interval timeout retries | 1 |
263 | 2,552,644,166 | IssuesEvent | 2015-02-02 18:29:06 | AdamsLair/duality | https://api.github.com/repos/AdamsLair/duality | closed | Improve Source/Media Folder Handling | Editor Feature Usability | - Right now, ```Source/Media``` is mostly a temp-like wasteland, because it isn't kept in sync with the Data directory properly.
- It doesn't have to be like this, since this would be an ideal place to store actual source data and even put it into version control. It could be an "optionally temporary" folder, that can or can not be used, depending on preference.
## ToDo
- Allow importing Resources from source files that are already located within ```Source/Media```.
- Keep the source folder in sync with the data folder at all times.
- Keep it optional like it is now: If someone was to delete the source folder, it shouldn't be a problem at all. | True | Improve Source/Media Folder Handling - - Right now, ```Source/Media``` is mostly a temp-like wasteland, because it isn't kept in sync with the Data directory properly.
- It doesn't have to be like this, since this would be an ideal place to store actual source data and even put it into version control. It could be an "optionally temporary" folder, that can or can not be used, depending on preference.
## ToDo
- Allow importing Resources from source files that are already located within ```Source/Media```.
- Keep the source folder in sync with the data folder at all times.
- Keep it optional like it is now: If someone was to delete the source folder, it shouldn't be a problem at all. | non_test | improve source media folder handling right now source media is mostly a temp like wasteland because it isn t kept in sync with the data directory properly it doesn t have to be like this since this would be an ideal place to store actual source data and even put it into version control it could be an optionally temporary folder that can or can not be used depending on preference todo allow importing resources from source files that are already located within source media keep the source folder in sync with the data folder at all times keep it optional like it is now if someone was to delete the source folder it shouldn t be a problem at all | 0 |
188,382 | 15,159,984,184 | IssuesEvent | 2021-02-12 05:54:19 | arturo-lang/arturo | https://api.github.com/repos/arturo-lang/arturo | closed | [Numbers\tan] add example for documentation | documentation easy library todo | [Numbers\tan] add example for documentation
https://github.com/arturo-lang/arturo/blob/a971add892fe3d675b3320f356cf2d96179e2a22/src/library/Numbers.nim#L655
```text
attrs = NoAttrs,
returns = {Floating},
# TODO(Numbers\tan) add example for documentation
# labels: library,documentation,easy
example = """
""":
##########################################################
```
d639b82c87090f66795b5d157c2189459d463e89 | 1.0 | [Numbers\tan] add example for documentation - [Numbers\tan] add example for documentation
https://github.com/arturo-lang/arturo/blob/a971add892fe3d675b3320f356cf2d96179e2a22/src/library/Numbers.nim#L655
```text
attrs = NoAttrs,
returns = {Floating},
# TODO(Numbers\tan) add example for documentation
# labels: library,documentation,easy
example = """
""":
##########################################################
```
d639b82c87090f66795b5d157c2189459d463e89 | non_test | add example for documentation add example for documentation text attrs noattrs returns floating todo numbers tan add example for documentation labels library documentation easy example | 0 |
7,105 | 9,393,197,785 | IssuesEvent | 2019-04-07 09:25:31 | koraktor/steam-condenser | https://api.github.com/repos/koraktor/steam-condenser | closed | Exception in `SteamId#fetch_games` | Community Compatibility Ruby | Ruby version:
```
› ruby --version
ruby 2.6.1p33 (2019-01-30 revision 66950) [x86_64-linux]
```
Gem version:
```
› gem list steam-condenser
*** LOCAL GEMS ***
steam-condenser (1.3.11)
```
Sample code:
```ruby
require 'steam-condenser'
WebApi.api_key = '*snip*'
id = SteamId.from_steam_id('STEAM_0:1:38735346')
puts "Profile is public: #{ id.public? }"
id.fetch_games
```
Output & exception:
```
Profile is public: true
Traceback (most recent call last):
5: from /tmp/sc.rb:7:in `<main>'
4: from /home/michael/.gem/ruby/2.6.1/gems/steam-condenser-1.3.11/lib/steam/community/steam_id.rb:326:in `fetch_games'
3: from /home/michael/.gem/ruby/2.6.1/gems/steam-condenser-1.3.11/lib/steam/community/steam_id.rb:326:in `each'
2: from /home/michael/.gem/ruby/2.6.1/gems/steam-condenser-1.3.11/lib/steam/community/steam_id.rb:328:in `block in fetch_games'
1: from /home/michael/.gem/ruby/2.6.1/gems/steam-condenser-1.3.11/lib/steam/community/steam_game.rb:64:in `new'
/home/michael/.gem/ruby/2.6.1/gems/steam-condenser-1.3.11/lib/steam/community/steam_game.rb:182:in `initialize': undefined method `[]' for nil:NilClass (NoMethodError)
``` | True | Exception in `SteamId#fetch_games` - Ruby version:
```
› ruby --version
ruby 2.6.1p33 (2019-01-30 revision 66950) [x86_64-linux]
```
Gem version:
```
› gem list steam-condenser
*** LOCAL GEMS ***
steam-condenser (1.3.11)
```
Sample code:
```ruby
require 'steam-condenser'
WebApi.api_key = '*snip*'
id = SteamId.from_steam_id('STEAM_0:1:38735346')
puts "Profile is public: #{ id.public? }"
id.fetch_games
```
Output & exception:
```
Profile is public: true
Traceback (most recent call last):
5: from /tmp/sc.rb:7:in `<main>'
4: from /home/michael/.gem/ruby/2.6.1/gems/steam-condenser-1.3.11/lib/steam/community/steam_id.rb:326:in `fetch_games'
3: from /home/michael/.gem/ruby/2.6.1/gems/steam-condenser-1.3.11/lib/steam/community/steam_id.rb:326:in `each'
2: from /home/michael/.gem/ruby/2.6.1/gems/steam-condenser-1.3.11/lib/steam/community/steam_id.rb:328:in `block in fetch_games'
1: from /home/michael/.gem/ruby/2.6.1/gems/steam-condenser-1.3.11/lib/steam/community/steam_game.rb:64:in `new'
/home/michael/.gem/ruby/2.6.1/gems/steam-condenser-1.3.11/lib/steam/community/steam_game.rb:182:in `initialize': undefined method `[]' for nil:NilClass (NoMethodError)
``` | non_test | exception in steamid fetch games ruby version › ruby version ruby revision gem version › gem list steam condenser local gems steam condenser sample code ruby require steam condenser webapi api key snip id steamid from steam id steam puts profile is public id public id fetch games output exception profile is public true traceback most recent call last from tmp sc rb in from home michael gem ruby gems steam condenser lib steam community steam id rb in fetch games from home michael gem ruby gems steam condenser lib steam community steam id rb in each from home michael gem ruby gems steam condenser lib steam community steam id rb in block in fetch games from home michael gem ruby gems steam condenser lib steam community steam game rb in new home michael gem ruby gems steam condenser lib steam community steam game rb in initialize undefined method for nil nilclass nomethoderror | 0 |
153,988 | 12,179,739,306 | IssuesEvent | 2020-04-28 11:13:08 | ColorlibHQ/simple-custom-post-order | https://api.github.com/repos/ColorlibHQ/simple-custom-post-order | closed | The table of posts is extending past the width of the browser window | need testing | The table of posts is extending past the width of the browser window. I tried unchecking a couple of column options (comments and tags) to see if that would fix it, but it didn’t. It’s like the title column is taking up way too much width than it should.
Screenshot of the issue:
And a comparison with the plugin disabled:
Disabled:
| 1.0 | The table of posts is extending past the width of the browser window - The table of posts is extending past the width of the browser window. I tried unchecking a couple of column options (comments and tags) to see if that would fix it, but it didn’t. It’s like the title column is taking up way too much width than it should.
Screenshot of the issue:
And a comparison with the plugin disabled:
Disabled:
| test | the table of posts is extending past the width of the browser window the table of posts is extending past the width of the browser window i tried unchecking a couple of column options comments and tags to see if that would fix it but it didn’t it’s like the title column is taking up way too much width than it should screenshot of the issue and a comparison with the plugin disabled disabled | 1 |
269,279 | 8,434,055,955 | IssuesEvent | 2018-10-17 09:08:35 | CS2113-AY1819S1-T12-1/main | https://api.github.com/repos/CS2113-AY1819S1-T12-1/main | closed | [v1.2] Display Event Page on selection | priority.high status.ongoing type.task | Display event page with event details upon selecting an event | 1.0 | [v1.2] Display Event Page on selection - Display event page with event details upon selecting an event | non_test | display event page on selection display event page with event details upon selecting an event | 0 |
131,707 | 10,707,233,537 | IssuesEvent | 2019-10-24 17:00:30 | SNLComputation/Albany | https://api.github.com/repos/SNLComputation/Albany | closed | FPEs in ACE tests | ACE Testing | Looks like the ACE tests are failing on a number of platforms including proxima due to FPEs, see http://cdash.sandia.gov/CDash-2-3-0/testDetails.php?test=5039598&build=90138 . It started yesterday. When I do a backtrace in gdb, it is not superhelpful. Here it is:
```
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Kokkos_Parallel.hpp:191
#12 0x00007fffede73c89 in LCM::ParallelConstitutiveModel<PHAL::AlbanyTraits::Jacobian, PHAL::AlbanyTraits, LCM::ACEiceMiniKernel<PHAL::AlbanyTraits::Jacobian, PHAL::AlbanyTraits> >::computeState(PHAL::Workset&, std::map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, Teuchos::RCP<PHX::MDField<Sacado::Fad::DFad<double> const> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, Teuchos::RCP<PHX--Type <RET> for more, q to quit, c to continue without paging--
::MDField<Sacado::Fad::DFad<double> const> > > > >, std::map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, Teuchos::RCP<PHX::MDField<Sacado::Fad::DFad<double>> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, Teuchos::RCP<PHX::MDField<Sacado::Fad::DFad<double>> > > > >) (this=0x7af200, workset=..., dep_fields=std::map with 8 elements = {...},
eval_fields=std::map with 14 elements = {...})
at /home/ikalash/nightlyCDash/repos/Albany/src/./LCM/parallel_models/ParallelConstitutiveModel_Def.hpp:61
#13 0x00007fffedfd939c in LCM::ConstitutiveModelInterface<PHAL::AlbanyTraits::Jacobian, PHAL::AlbanyTraits>::evaluateFields (this=0x7aed50,
workset=...) at /home/ikalash/nightlyCDash/repos/Albany/src/LCM/models/ConstitutiveModelInterface_Def.hpp:242
#14 0x00007ffff6cce9f0 in PHX::DagManager<PHAL::AlbanyTraits>::evaluateFields (this=0x752268, d=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Phalanx_DAG_Manager_Def.hpp:450
#15 0x00007ffff6ccb2d9 in PHX::EvaluationContainer<PHAL::AlbanyTraits::Jacobian, PHAL::AlbanyTraits>::evaluateFields (this=0x752260, d=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Phalanx_EvaluationContainer_Def.hpp:216
#16 0x00007ffff6c7565a in PHX::FieldManager<PHAL::AlbanyTraits>::evaluateFields<PHAL::AlbanyTraits::Jacobian> (this=0x752180, d=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Phalanx_FieldManager_Def.hpp:310
#17 0x00007ffff6c5c608 in Albany::Application::computeGlobalJacobianImpl (this=0x721f20, alpha=0, beta=1, omega=0, current_time=0, x=...,
xdot=..., xdotdot=..., p=..., f=..., jac=..., dt=0) at /home/ikalash/nightlyCDash/repos/Albany/src/Albany_Application.cpp:1491
#18 0x00007ffff6c5d52f in Albany::Application::computeGlobalJacobian (this=0x721f20, alpha=0, beta=1, omega=0, current_time=0, x=..., xdot=...,
xdotdot=..., p=..., f=..., jac=..., dt=0) at /home/ikalash/nightlyCDash/repos/Albany/src/Albany_Application.cpp:1629
#19 0x00007ffff6cf000b in Albany::ModelEvaluator::evalModelImpl (this=0x9128b0, inArgs=..., outArgs=...)
at /home/ikalash/nightlyCDash/repos/Albany/src/Albany_ModelEvaluator.cpp:768
#20 0x00007ffff6b9333e in Thyra::ModelEvaluatorDefaultBase<double>::evalModel (this=0x9128b0, inArgs=..., outArgs=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Thyra_ModelEvaluatorDefaultBase.hpp:691
#21 0x00007ffff6bb24e5 in Thyra::DefaultModelEvaluatorWithSolveFactory<double>::evalModelImpl (this=0xa11180, inArgs=..., outArgs=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Thyra_DefaultModelEvaluatorWithSolveFactory.hpp:325
#22 0x00007ffff6b9333e in Thyra::ModelEvaluatorDefaultBase<double>::evalModel (this=0xa111c8, inArgs=..., outArgs=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Thyra_ModelEvaluatorDefaultBase.hpp:691
#23 0x00007fffe4380e48 in LOCA::Thyra::Group::computeJacobian (this=0x9b5cc0)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src-loca/src-thyra/LOCA_Thyra_Group.C:180
#24 0x00007fffe3d5dbb8 in LOCA::MultiContinuation::ConstrainedGroup::computeJacobian (this=0xa9ee30)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src-loca/src/LOCA_MultiContinuation_ConstrainedGroup.C:357
#25 0x00007fffe3d6b335 in LOCA::MultiContinuation::ExtendedGroup::computeJacobian (this=0xa8f3e8)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src-loca/src/LOCA_MultiContinuation_ExtendedGroup.C:135
#26 0x00007fffe37ac797 in NOX::Direction::Newton::compute (this=0xb66750, dir=..., soln=..., solver=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src/NOX_Direction_Newton.C:131
--Type <RET> for more, q to quit, c to continue without paging--
#27 0x00007fffe37a1ade in NOX::Direction::Generic::compute (this=0xb66750, d=..., g=..., s=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src/NOX_Direction_Generic.C:59
#28 0x00007fffe37acdee in NOX::Direction::Newton::compute (this=0xb66750, dir=..., soln=..., solver=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src/NOX_Direction_Newton.C:164
#29 0x00007fffe37df470 in NOX::Solver::LineSearchBased::step (this=0x95c840)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src/NOX_Solver_LineSearchBased.C:194
#30 0x00007fffe37dfa84 in NOX::Solver::LineSearchBased::solve (this=0x95c840)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src/NOX_Solver_LineSearchBased.C:260
#31 0x00007fffe3e93a38 in LOCA::Stepper::compute (this=0x9708c0)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src-loca/src/LOCA_Stepper.C:600
#32 0x00007fffe3d17039 in LOCA::Abstract::Iterator::iterate (this=0x9708c0)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src-loca/src/LOCA_Abstract_Iterator.C:150
#33 0x00007fffe3d16f80 in LOCA::Abstract::Iterator::run (this=0x9708c0)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src-loca/src/LOCA_Abstract_Iterator.C:128
#34 0x00007fffeb2cd413 in Piro::LOCASolver<double>::evalModelImpl (this=0x9d9b80, inArgs=..., outArgs=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/piro/src/Piro_LOCASolver_Def.hpp:197
#35 0x00007ffff6b9333e in Thyra::ModelEvaluatorDefaultBase<double>::evalModel (this=0x9d9d10, inArgs=..., outArgs=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Thyra_ModelEvaluatorDefaultBase.hpp:691
#36 0x000000000047b7d3 in Piro::Detail::PerformSolveImpl<double, Thyra::VectorBase<double> const, Thyra::MultiVectorBase<double> const> (
model=..., computeResponses=..., computeSensitivities=false, responses=..., sensitivities=..., observer=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Piro_PerformSolve_Def.hpp:120
#37 0x0000000000477978 in Piro::Detail::PerformSolveImpl<double, Thyra::VectorBase<double> const, Thyra::MultiVectorBase<double> const> (
model=..., solveParams=..., responses=..., sensitivities=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Piro_PerformSolve_Def.hpp:162
#38 0x0000000000474642 in Piro::PerformSolveBase<double> (piroModel=..., solveParams=..., responses=..., sensitivities=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Piro_PerformSolve_Def.hpp:291
#39 0x0000000000470998 in Piro::PerformSolve<double> (piroModel=..., solveParams=..., responses=..., sensitivities=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Piro_PerformSolve_Def.hpp:230
#40 0x000000000046106f in main (argc=2, argv=0x7fffffffd0b8) at /home/ikalash/nightlyCDash/repos/Albany/src/Main_Solve.cpp:144
```
Here are the last lines in Albany from the stack:
https://github.com/SNLComputation/Albany/blob/master/src/LCM/parallel_models/ParallelConstitutiveModel_Def.hpp#L61-L67
I was surprised to see Kokkos::parallel_fors... I thought that was all removed from LCM awhile ago?
@lxmota, can you please look at this? I think your changes yesterday broke the tests. | 1.0 | FPEs in ACE tests - Looks like the ACE tests are failing on a number of platforms including proxima due to FPEs, see http://cdash.sandia.gov/CDash-2-3-0/testDetails.php?test=5039598&build=90138 . It started yesterday. When I do a backtrace in gdb, it is not superhelpful. Here it is:
```
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Kokkos_Parallel.hpp:191
#12 0x00007fffede73c89 in LCM::ParallelConstitutiveModel<PHAL::AlbanyTraits::Jacobian, PHAL::AlbanyTraits, LCM::ACEiceMiniKernel<PHAL::AlbanyTraits::Jacobian, PHAL::AlbanyTraits> >::computeState(PHAL::Workset&, std::map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, Teuchos::RCP<PHX::MDField<Sacado::Fad::DFad<double> const> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, Teuchos::RCP<PHX--Type <RET> for more, q to quit, c to continue without paging--
::MDField<Sacado::Fad::DFad<double> const> > > > >, std::map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, Teuchos::RCP<PHX::MDField<Sacado::Fad::DFad<double>> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, Teuchos::RCP<PHX::MDField<Sacado::Fad::DFad<double>> > > > >) (this=0x7af200, workset=..., dep_fields=std::map with 8 elements = {...},
eval_fields=std::map with 14 elements = {...})
at /home/ikalash/nightlyCDash/repos/Albany/src/./LCM/parallel_models/ParallelConstitutiveModel_Def.hpp:61
#13 0x00007fffedfd939c in LCM::ConstitutiveModelInterface<PHAL::AlbanyTraits::Jacobian, PHAL::AlbanyTraits>::evaluateFields (this=0x7aed50,
workset=...) at /home/ikalash/nightlyCDash/repos/Albany/src/LCM/models/ConstitutiveModelInterface_Def.hpp:242
#14 0x00007ffff6cce9f0 in PHX::DagManager<PHAL::AlbanyTraits>::evaluateFields (this=0x752268, d=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Phalanx_DAG_Manager_Def.hpp:450
#15 0x00007ffff6ccb2d9 in PHX::EvaluationContainer<PHAL::AlbanyTraits::Jacobian, PHAL::AlbanyTraits>::evaluateFields (this=0x752260, d=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Phalanx_EvaluationContainer_Def.hpp:216
#16 0x00007ffff6c7565a in PHX::FieldManager<PHAL::AlbanyTraits>::evaluateFields<PHAL::AlbanyTraits::Jacobian> (this=0x752180, d=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Phalanx_FieldManager_Def.hpp:310
#17 0x00007ffff6c5c608 in Albany::Application::computeGlobalJacobianImpl (this=0x721f20, alpha=0, beta=1, omega=0, current_time=0, x=...,
xdot=..., xdotdot=..., p=..., f=..., jac=..., dt=0) at /home/ikalash/nightlyCDash/repos/Albany/src/Albany_Application.cpp:1491
#18 0x00007ffff6c5d52f in Albany::Application::computeGlobalJacobian (this=0x721f20, alpha=0, beta=1, omega=0, current_time=0, x=..., xdot=...,
xdotdot=..., p=..., f=..., jac=..., dt=0) at /home/ikalash/nightlyCDash/repos/Albany/src/Albany_Application.cpp:1629
#19 0x00007ffff6cf000b in Albany::ModelEvaluator::evalModelImpl (this=0x9128b0, inArgs=..., outArgs=...)
at /home/ikalash/nightlyCDash/repos/Albany/src/Albany_ModelEvaluator.cpp:768
#20 0x00007ffff6b9333e in Thyra::ModelEvaluatorDefaultBase<double>::evalModel (this=0x9128b0, inArgs=..., outArgs=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Thyra_ModelEvaluatorDefaultBase.hpp:691
#21 0x00007ffff6bb24e5 in Thyra::DefaultModelEvaluatorWithSolveFactory<double>::evalModelImpl (this=0xa11180, inArgs=..., outArgs=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Thyra_DefaultModelEvaluatorWithSolveFactory.hpp:325
#22 0x00007ffff6b9333e in Thyra::ModelEvaluatorDefaultBase<double>::evalModel (this=0xa111c8, inArgs=..., outArgs=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Thyra_ModelEvaluatorDefaultBase.hpp:691
#23 0x00007fffe4380e48 in LOCA::Thyra::Group::computeJacobian (this=0x9b5cc0)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src-loca/src-thyra/LOCA_Thyra_Group.C:180
#24 0x00007fffe3d5dbb8 in LOCA::MultiContinuation::ConstrainedGroup::computeJacobian (this=0xa9ee30)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src-loca/src/LOCA_MultiContinuation_ConstrainedGroup.C:357
#25 0x00007fffe3d6b335 in LOCA::MultiContinuation::ExtendedGroup::computeJacobian (this=0xa8f3e8)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src-loca/src/LOCA_MultiContinuation_ExtendedGroup.C:135
#26 0x00007fffe37ac797 in NOX::Direction::Newton::compute (this=0xb66750, dir=..., soln=..., solver=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src/NOX_Direction_Newton.C:131
--Type <RET> for more, q to quit, c to continue without paging--
#27 0x00007fffe37a1ade in NOX::Direction::Generic::compute (this=0xb66750, d=..., g=..., s=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src/NOX_Direction_Generic.C:59
#28 0x00007fffe37acdee in NOX::Direction::Newton::compute (this=0xb66750, dir=..., soln=..., solver=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src/NOX_Direction_Newton.C:164
#29 0x00007fffe37df470 in NOX::Solver::LineSearchBased::step (this=0x95c840)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src/NOX_Solver_LineSearchBased.C:194
#30 0x00007fffe37dfa84 in NOX::Solver::LineSearchBased::solve (this=0x95c840)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src/NOX_Solver_LineSearchBased.C:260
#31 0x00007fffe3e93a38 in LOCA::Stepper::compute (this=0x9708c0)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src-loca/src/LOCA_Stepper.C:600
#32 0x00007fffe3d17039 in LOCA::Abstract::Iterator::iterate (this=0x9708c0)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src-loca/src/LOCA_Abstract_Iterator.C:150
#33 0x00007fffe3d16f80 in LOCA::Abstract::Iterator::run (this=0x9708c0)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/nox/src-loca/src/LOCA_Abstract_Iterator.C:128
#34 0x00007fffeb2cd413 in Piro::LOCASolver<double>::evalModelImpl (this=0x9d9b80, inArgs=..., outArgs=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/packages/piro/src/Piro_LOCASolver_Def.hpp:197
#35 0x00007ffff6b9333e in Thyra::ModelEvaluatorDefaultBase<double>::evalModel (this=0x9d9d10, inArgs=..., outArgs=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Thyra_ModelEvaluatorDefaultBase.hpp:691
#36 0x000000000047b7d3 in Piro::Detail::PerformSolveImpl<double, Thyra::VectorBase<double> const, Thyra::MultiVectorBase<double> const> (
model=..., computeResponses=..., computeSensitivities=false, responses=..., sensitivities=..., observer=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Piro_PerformSolve_Def.hpp:120
#37 0x0000000000477978 in Piro::Detail::PerformSolveImpl<double, Thyra::VectorBase<double> const, Thyra::MultiVectorBase<double> const> (
model=..., solveParams=..., responses=..., sensitivities=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Piro_PerformSolve_Def.hpp:162
#38 0x0000000000474642 in Piro::PerformSolveBase<double> (piroModel=..., solveParams=..., responses=..., sensitivities=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Piro_PerformSolve_Def.hpp:291
#39 0x0000000000470998 in Piro::PerformSolve<double> (piroModel=..., solveParams=..., responses=..., sensitivities=...)
at /home/ikalash/nightlyAlbanyTests/Results/Trilinos/build-debug/install/include/Piro_PerformSolve_Def.hpp:230
#40 0x000000000046106f in main (argc=2, argv=0x7fffffffd0b8) at /home/ikalash/nightlyCDash/repos/Albany/src/Main_Solve.cpp:144
```
Here are the last lines in Albany from the stack:
https://github.com/SNLComputation/Albany/blob/master/src/LCM/parallel_models/ParallelConstitutiveModel_Def.hpp#L61-L67
I was surprised to see Kokkos::parallel_fors... I thought that was all removed from LCM awhile ago?
@lxmota, can you please look at this? I think your changes yesterday broke the tests. | test | fpes in ace tests looks like the ace tests are failing on a number of platforms including proxima due to fpes see it started yesterday when i do a backtrace in gdb it is not superhelpful here it is at home ikalash nightlyalbanytests results trilinos build debug install include kokkos parallel hpp in lcm parallelconstitutivemodel computestate phal workset std map std allocator teuchos rcp const std less std allocator std allocator std allocator const teuchos rcp for more q to quit c to continue without paging mdfield const std map std allocator teuchos rcp std less std allocator std allocator std allocator const teuchos rcp this workset dep fields std map with elements eval fields std map with elements at home ikalash nightlycdash repos albany src lcm parallel models parallelconstitutivemodel def hpp in lcm constitutivemodelinterface evaluatefields this workset at home ikalash nightlycdash repos albany src lcm models constitutivemodelinterface def hpp in phx dagmanager evaluatefields this d at home ikalash nightlyalbanytests results trilinos build debug install include phalanx dag manager def hpp in phx evaluationcontainer evaluatefields this d at home ikalash nightlyalbanytests results trilinos build debug install include phalanx evaluationcontainer def hpp in phx fieldmanager evaluatefields this d at home ikalash nightlyalbanytests results trilinos build debug install include phalanx fieldmanager def hpp in albany application computeglobaljacobianimpl this alpha beta omega current time x xdot xdotdot p f jac dt at home ikalash nightlycdash repos albany src albany application cpp in albany application computeglobaljacobian this alpha beta omega current time x xdot xdotdot p f jac dt at home ikalash nightlycdash repos albany src albany application cpp in albany modelevaluator evalmodelimpl this inargs outargs at home ikalash nightlycdash repos albany src albany modelevaluator cpp in thyra modelevaluatordefaultbase evalmodel this inargs outargs at home ikalash nightlyalbanytests results trilinos build debug install include thyra modelevaluatordefaultbase hpp in thyra defaultmodelevaluatorwithsolvefactory evalmodelimpl this inargs outargs at home ikalash nightlyalbanytests results trilinos build debug install include thyra defaultmodelevaluatorwithsolvefactory hpp in thyra modelevaluatordefaultbase evalmodel this inargs outargs at home ikalash nightlyalbanytests results trilinos build debug install include thyra modelevaluatordefaultbase hpp in loca thyra group computejacobian this at home ikalash nightlyalbanytests results trilinos packages nox src loca src thyra loca thyra group c in loca multicontinuation constrainedgroup computejacobian this at home ikalash nightlyalbanytests results trilinos packages nox src loca src loca multicontinuation constrainedgroup c in loca multicontinuation extendedgroup computejacobian this at home ikalash nightlyalbanytests results trilinos packages nox src loca src loca multicontinuation extendedgroup c in nox direction newton compute this dir soln solver at home ikalash nightlyalbanytests results trilinos packages nox src nox direction newton c type for more q to quit c to continue without paging in nox direction generic compute this d g s at home ikalash nightlyalbanytests results trilinos packages nox src nox direction generic c in nox direction newton compute this dir soln solver at home ikalash nightlyalbanytests results trilinos packages nox src nox direction newton c in nox solver linesearchbased step this at home ikalash nightlyalbanytests results trilinos packages nox src nox solver linesearchbased c in nox solver linesearchbased solve this at home ikalash nightlyalbanytests results trilinos packages nox src nox solver linesearchbased c in loca stepper compute this at home ikalash nightlyalbanytests results trilinos packages nox src loca src loca stepper c in loca abstract iterator iterate this at home ikalash nightlyalbanytests results trilinos packages nox src loca src loca abstract iterator c in loca abstract iterator run this at home ikalash nightlyalbanytests results trilinos packages nox src loca src loca abstract iterator c in piro locasolver evalmodelimpl this inargs outargs at home ikalash nightlyalbanytests results trilinos packages piro src piro locasolver def hpp in thyra modelevaluatordefaultbase evalmodel this inargs outargs at home ikalash nightlyalbanytests results trilinos build debug install include thyra modelevaluatordefaultbase hpp in piro detail performsolveimpl const thyra multivectorbase const model computeresponses computesensitivities false responses sensitivities observer at home ikalash nightlyalbanytests results trilinos build debug install include piro performsolve def hpp in piro detail performsolveimpl const thyra multivectorbase const model solveparams responses sensitivities at home ikalash nightlyalbanytests results trilinos build debug install include piro performsolve def hpp in piro performsolvebase piromodel solveparams responses sensitivities at home ikalash nightlyalbanytests results trilinos build debug install include piro performsolve def hpp in piro performsolve piromodel solveparams responses sensitivities at home ikalash nightlyalbanytests results trilinos build debug install include piro performsolve def hpp in main argc argv at home ikalash nightlycdash repos albany src main solve cpp here are the last lines in albany from the stack i was surprised to see kokkos parallel fors i thought that was all removed from lcm awhile ago lxmota can you please look at this i think your changes yesterday broke the tests | 1 |
23,127 | 3,994,158,307 | IssuesEvent | 2016-05-10 11:12:54 | hazelcast/hazelcast-csharp-client | https://api.github.com/repos/hazelcast/hazelcast-csharp-client | closed | ClientDistributedObjectTest.TestGetDistributedObjects | Type: Test-Failure | ```
MESSAGE:
Expected: 3
But was: 4
+++++++++++++++++++
STACK TRACE:
at Hazelcast.Client.Test.ClientDistributedObjectTest.TestGetDistributedObjects() in c:\jenkins\ope-fs-root\workspace\csharp-client-master\Hazelcast.Test\Hazelcast.Client.Test\ClientDistributedObjectTest.cs:line 49
```
https://hazelcast-l337.ci.cloudbees.com/view/Official%20Builds/job/csharp-client-master/172/testReport/junit/Hazelcast.Client.Test/ClientDistributedObjectTest/TestGetDistributedObjects/ | 1.0 | ClientDistributedObjectTest.TestGetDistributedObjects - ```
MESSAGE:
Expected: 3
But was: 4
+++++++++++++++++++
STACK TRACE:
at Hazelcast.Client.Test.ClientDistributedObjectTest.TestGetDistributedObjects() in c:\jenkins\ope-fs-root\workspace\csharp-client-master\Hazelcast.Test\Hazelcast.Client.Test\ClientDistributedObjectTest.cs:line 49
```
https://hazelcast-l337.ci.cloudbees.com/view/Official%20Builds/job/csharp-client-master/172/testReport/junit/Hazelcast.Client.Test/ClientDistributedObjectTest/TestGetDistributedObjects/ | test | clientdistributedobjecttest testgetdistributedobjects message expected but was stack trace at hazelcast client test clientdistributedobjecttest testgetdistributedobjects in c jenkins ope fs root workspace csharp client master hazelcast test hazelcast client test clientdistributedobjecttest cs line | 1 |
134,547 | 5,229,362,426 | IssuesEvent | 2017-01-29 02:30:55 | Automattic/mongoose | https://api.github.com/repos/Automattic/mongoose | closed | New MongoDB 3.4 Collation support in queries | fixed? priority | Hi,
the new MongoDB 3.4 introduced collation support to run case insensitive queries.
https://docs.mongodb.com/manual/reference/method/cursor.collation/#cursor.collation
To run a query supporting collation is needed set collation on cursor.
It would be important add complete support in mongoose for this feature.
| 1.0 | New MongoDB 3.4 Collation support in queries - Hi,
the new MongoDB 3.4 introduced collation support to run case insensitive queries.
https://docs.mongodb.com/manual/reference/method/cursor.collation/#cursor.collation
To run a query supporting collation is needed set collation on cursor.
It would be important add complete support in mongoose for this feature.
| non_test | new mongodb collation support in queries hi the new mongodb introduced collation support to run case insensitive queries to run a query supporting collation is needed set collation on cursor it would be important add complete support in mongoose for this feature | 0 |
204,703 | 15,528,361,579 | IssuesEvent | 2021-03-13 10:34:48 | VultureProject/darwin | https://api.github.com/repos/VultureProject/darwin | closed | [IDEA] Test for content inspection | enhancement important tests | **What is your feature about ?**
Need automated test for content inspection filter
https://github.com/VultureProject/darwin/wiki/Filter-Content-Inspection
**Describe what you'd like**
Test must be passed on Ubuntu and FreeBSD | 1.0 | [IDEA] Test for content inspection - **What is your feature about ?**
Need automated test for content inspection filter
https://github.com/VultureProject/darwin/wiki/Filter-Content-Inspection
**Describe what you'd like**
Test must be passed on Ubuntu and FreeBSD | test | test for content inspection what is your feature about need automated test for content inspection filter describe what you d like test must be passed on ubuntu and freebsd | 1 |
155,815 | 24,524,267,800 | IssuesEvent | 2022-10-11 11:59:24 | kodo-pp/oxipaint | https://api.github.com/repos/kodo-pp/oxipaint | closed | Design a prototype with working UI using GTK | P-normal C-design S-pr-wair | Build a simple user interface using GTK as the UI toolkit. | 1.0 | Design a prototype with working UI using GTK - Build a simple user interface using GTK as the UI toolkit. | non_test | design a prototype with working ui using gtk build a simple user interface using gtk as the ui toolkit | 0 |
125,833 | 10,360,849,183 | IssuesEvent | 2019-09-06 08:39:16 | OWASP/SecurityShepherd | https://api.github.com/repos/OWASP/SecurityShepherd | opened | Testing - Move Integration Tests | Test Automation | The structure of the project has changed where it has a separate unit test and integration test folder.
Definition of done;
- all integration tests are moved to the IT folder
- all integration tests are renamed to trail with IT e.g. "lessonIT" | 1.0 | Testing - Move Integration Tests - The structure of the project has changed where it has a separate unit test and integration test folder.
Definition of done;
- all integration tests are moved to the IT folder
- all integration tests are renamed to trail with IT e.g. "lessonIT" | test | testing move integration tests the structure of the project has changed where it has a separate unit test and integration test folder definition of done all integration tests are moved to the it folder all integration tests are renamed to trail with it e g lessonit | 1 |
61,109 | 8,488,884,028 | IssuesEvent | 2018-10-26 18:04:24 | TTUSDC/ttuacm-backend | https://api.github.com/repos/TTUSDC/ttuacm-backend | closed | Need Issue Templates and PR Templates | Documentation Hacktoberfest Priority: Medium | We want people to be able to submit these in a formatted matter so that us developers can have an easier time and deliver it faster | 1.0 | Need Issue Templates and PR Templates - We want people to be able to submit these in a formatted matter so that us developers can have an easier time and deliver it faster | non_test | need issue templates and pr templates we want people to be able to submit these in a formatted matter so that us developers can have an easier time and deliver it faster | 0 |
204,490 | 15,497,247,249 | IssuesEvent | 2021-03-11 04:14:23 | kubernetes/kubernetes | https://api.github.com/repos/kubernetes/kubernetes | closed | [sig-network] EndpointSlice should create and delete Endpoints and EndpointSlices for a Service with a selector specified | area/deflake area/test kind/flake sig/network triage/accepted | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
**Which jobs are flaking**:
gce-ubuntu-master-default
**Which test(s) are flaking**:
[sig-network] EndpointSlice should create and delete Endpoints and EndpointSlices for a Service with a selector specified
**Testgrid link**:
https://testgrid.k8s.io/sig-release-master-informing#gce-ubuntu-master-default&sort-by-flakiness=&embed=
**Reason for failure**:
from [Spyglass for job 1278952987569426433](https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-ubuntu-gce/1278952987569426433)
we have
[I0703 07:42:24.519 Jul 3 07:42:20.620: FAIL: EndpointSlice resource not deleted after Service endpointslice-3248/example-empty-selector was deleted: timed out waiting for the condition](https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-ubuntu-gce/1278952987569426433#1:build-log.txt%3A40945)
following thru to the [corresponding gubernator logs/ci-kubernetes-e2e-ubuntu-gce/1278952987569426433/]( https://gubernator.k8s.io/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-ubuntu-gce/1278952987569426433/nodelog?junit=junit_09.xml&wrap=on)
we see lot of occurrences of
`W0703 07:45:10.958376 8 request.go:161] Auditing failed of request: encoding failed: /v1, Kind=DeleteOptions is unstructured and is not suitable for converting to "cloud.google.com/v1beta1"`
**Anything else we need to know**:
- links to go.k8s.io/triage appreciated
| 1.0 | [sig-network] EndpointSlice should create and delete Endpoints and EndpointSlices for a Service with a selector specified - <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
**Which jobs are flaking**:
gce-ubuntu-master-default
**Which test(s) are flaking**:
[sig-network] EndpointSlice should create and delete Endpoints and EndpointSlices for a Service with a selector specified
**Testgrid link**:
https://testgrid.k8s.io/sig-release-master-informing#gce-ubuntu-master-default&sort-by-flakiness=&embed=
**Reason for failure**:
from [Spyglass for job 1278952987569426433](https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-ubuntu-gce/1278952987569426433)
we have
[I0703 07:42:24.519 Jul 3 07:42:20.620: FAIL: EndpointSlice resource not deleted after Service endpointslice-3248/example-empty-selector was deleted: timed out waiting for the condition](https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-ubuntu-gce/1278952987569426433#1:build-log.txt%3A40945)
following thru to the [corresponding gubernator logs/ci-kubernetes-e2e-ubuntu-gce/1278952987569426433/]( https://gubernator.k8s.io/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-ubuntu-gce/1278952987569426433/nodelog?junit=junit_09.xml&wrap=on)
we see lot of occurrences of
`W0703 07:45:10.958376 8 request.go:161] Auditing failed of request: encoding failed: /v1, Kind=DeleteOptions is unstructured and is not suitable for converting to "cloud.google.com/v1beta1"`
**Anything else we need to know**:
- links to go.k8s.io/triage appreciated
| test | endpointslice should create and delete endpoints and endpointslices for a service with a selector specified which jobs are flaking gce ubuntu master default which test s are flaking endpointslice should create and delete endpoints and endpointslices for a service with a selector specified testgrid link reason for failure from we have following thru to the we see lot of occurrences of request go auditing failed of request encoding failed kind deleteoptions is unstructured and is not suitable for converting to cloud google com anything else we need to know links to go io triage appreciated | 1 |
244,641 | 26,441,572,873 | IssuesEvent | 2023-01-16 01:08:54 | panasalap/linux-4.1.15 | https://api.github.com/repos/panasalap/linux-4.1.15 | opened | CVE-2022-4379 (High) detected in linux-yocto-4.1v4.1.17 | security vulnerability | ## CVE-2022-4379 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yocto-4.1v4.1.17</b></p></summary>
<p>
<p>[no description]</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto-4.1>https://git.yoctoproject.org/git/linux-yocto-4.1</a></p>
<p>Found in HEAD commit: <a href="https://github.com/panasalap/linux-4.1.15/commit/aae4c2fa46027fd4c477372871df090c6b94f3f1">aae4c2fa46027fd4c477372871df090c6b94f3f1</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/nfsd/nfs4proc.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/nfsd/nfs4proc.c</b>
</p>
</details>
<p></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>
A use-after-free vulnerability was found in __nfs42_ssc_open() in fs/nfs/nfs4file.c in the Linux kernel. This flaw allows an attacker to conduct a remote denial
<p>Publish Date: 2023-01-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-4379>CVE-2022-4379</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://www.linuxkernelcves.com/cves/CVE-2022-4379">https://www.linuxkernelcves.com/cves/CVE-2022-4379</a></p>
<p>Release Date: 2023-01-10</p>
<p>Fix Resolution: v6.1.3</p>
</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-4379 (High) detected in linux-yocto-4.1v4.1.17 - ## CVE-2022-4379 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yocto-4.1v4.1.17</b></p></summary>
<p>
<p>[no description]</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto-4.1>https://git.yoctoproject.org/git/linux-yocto-4.1</a></p>
<p>Found in HEAD commit: <a href="https://github.com/panasalap/linux-4.1.15/commit/aae4c2fa46027fd4c477372871df090c6b94f3f1">aae4c2fa46027fd4c477372871df090c6b94f3f1</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/nfsd/nfs4proc.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/nfsd/nfs4proc.c</b>
</p>
</details>
<p></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>
A use-after-free vulnerability was found in __nfs42_ssc_open() in fs/nfs/nfs4file.c in the Linux kernel. This flaw allows an attacker to conduct a remote denial
<p>Publish Date: 2023-01-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-4379>CVE-2022-4379</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://www.linuxkernelcves.com/cves/CVE-2022-4379">https://www.linuxkernelcves.com/cves/CVE-2022-4379</a></p>
<p>Release Date: 2023-01-10</p>
<p>Fix Resolution: v6.1.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve high detected in linux yocto cve high severity vulnerability vulnerable library linux yocto library home page a href found in head commit a href found in base branch master vulnerable source files fs nfsd c fs nfsd c vulnerability details a use after free vulnerability was found in ssc open in fs nfs c in the linux kernel this flaw allows an attacker to conduct a remote denial 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 mend | 0 |
72,207 | 31,281,005,566 | IssuesEvent | 2023-08-22 09:34:45 | kubeshop/testkube | https://api.github.com/repos/kubeshop/testkube | closed | UI: Labels are badly positioned | bug 🐛 service:dashboard 🎡 | **Describe the bug**
The labels are positioned strangely. The problem occurs on dev.testkube.io, but it doesn't on demo.testkube.io, so it's related to some new change.
**To Reproduce**
https://dev.testkube.io/tests/cypress-default-executor-smoke-electron-testsource/settings
**Expected behavior**
It should be positioned correctly, in line.
**Screenshots**
| Before | Now |
|-|-|
| <img width="1606" alt="Zrzut ekranu 2023-08-21 o 11 56 41" src="https://github.com/kubeshop/testkube/assets/3843526/3b0014cf-e064-4520-84ad-f46627235e18"> | <img width="1613" alt="Zrzut ekranu 2023-08-21 o 11 54 01" src="https://github.com/kubeshop/testkube/assets/3843526/3d0b48fd-3d98-49b2-bc58-bfaafa22c511"> | | 1.0 | UI: Labels are badly positioned - **Describe the bug**
The labels are positioned strangely. The problem occurs on dev.testkube.io, but it doesn't on demo.testkube.io, so it's related to some new change.
**To Reproduce**
https://dev.testkube.io/tests/cypress-default-executor-smoke-electron-testsource/settings
**Expected behavior**
It should be positioned correctly, in line.
**Screenshots**
| Before | Now |
|-|-|
| <img width="1606" alt="Zrzut ekranu 2023-08-21 o 11 56 41" src="https://github.com/kubeshop/testkube/assets/3843526/3b0014cf-e064-4520-84ad-f46627235e18"> | <img width="1613" alt="Zrzut ekranu 2023-08-21 o 11 54 01" src="https://github.com/kubeshop/testkube/assets/3843526/3d0b48fd-3d98-49b2-bc58-bfaafa22c511"> | | non_test | ui labels are badly positioned describe the bug the labels are positioned strangely the problem occurs on dev testkube io but it doesn t on demo testkube io so it s related to some new change to reproduce expected behavior it should be positioned correctly in line screenshots before now img width alt zrzut ekranu o src img width alt zrzut ekranu o src | 0 |
173,227 | 13,392,379,229 | IssuesEvent | 2020-09-03 01:11:27 | SunstriderEmu/BugTracker | https://api.github.com/repos/SunstriderEmu/BugTracker | closed | [Dungeon] Mind control trotem in Sethekk does not work | confirmed testfix | **Describe the bug**
Mind Control totems casted by Time-Lost Controller does not work
**To Reproduce**
Fight with Time-Lost Controller in Sethekk
http://tbc.cavernoftime.com/spell=32764 (I know it's a private server but it use to works like this)
| 1.0 | [Dungeon] Mind control trotem in Sethekk does not work - **Describe the bug**
Mind Control totems casted by Time-Lost Controller does not work
**To Reproduce**
Fight with Time-Lost Controller in Sethekk
http://tbc.cavernoftime.com/spell=32764 (I know it's a private server but it use to works like this)
| test | mind control trotem in sethekk does not work describe the bug mind control totems casted by time lost controller does not work to reproduce fight with time lost controller in sethekk i know it s a private server but it use to works like this | 1 |
166,636 | 6,307,965,654 | IssuesEvent | 2017-07-22 07:08:35 | coreos/etcd-operator | https://api.github.com/repos/coreos/etcd-operator | closed | Use "tolerate-unready-endpoints" to check etcd pod readiness | priority/Pmaybe | ref:
- https://github.com/kubernetes/kubernetes/issues/39207
- https://github.com/kubernetes/kubernetes/issues/39363
When etcd starts, it has a bootstrap phase that talks to other peers:
Start -> bootstrapping -> running/serving
If "bootstrap" phase failed, it is the same as dead because no data is available, no quorum information is known.
However, if we start etcd in a Kubernetes Pod, even if it starts running, it doesn't mean etcd is running. It is important for the operator to know the status of the etcd member in this phase. We can only proceed with this member after it's "ready".
There is a field in Kubernetes to decouple readiness and endpoints called
```
TolerateUnreadyEndpointsAnnotation = "service.alpha.kubernetes.io/tolerate-unready-endpoints"
```
Making use of this will help us differentiate the "bootstrapping" phase. | 1.0 | Use "tolerate-unready-endpoints" to check etcd pod readiness - ref:
- https://github.com/kubernetes/kubernetes/issues/39207
- https://github.com/kubernetes/kubernetes/issues/39363
When etcd starts, it has a bootstrap phase that talks to other peers:
Start -> bootstrapping -> running/serving
If "bootstrap" phase failed, it is the same as dead because no data is available, no quorum information is known.
However, if we start etcd in a Kubernetes Pod, even if it starts running, it doesn't mean etcd is running. It is important for the operator to know the status of the etcd member in this phase. We can only proceed with this member after it's "ready".
There is a field in Kubernetes to decouple readiness and endpoints called
```
TolerateUnreadyEndpointsAnnotation = "service.alpha.kubernetes.io/tolerate-unready-endpoints"
```
Making use of this will help us differentiate the "bootstrapping" phase. | non_test | use tolerate unready endpoints to check etcd pod readiness ref when etcd starts it has a bootstrap phase that talks to other peers start bootstrapping running serving if bootstrap phase failed it is the same as dead because no data is available no quorum information is known however if we start etcd in a kubernetes pod even if it starts running it doesn t mean etcd is running it is important for the operator to know the status of the etcd member in this phase we can only proceed with this member after it s ready there is a field in kubernetes to decouple readiness and endpoints called tolerateunreadyendpointsannotation service alpha kubernetes io tolerate unready endpoints making use of this will help us differentiate the bootstrapping phase | 0 |
312,494 | 26,868,607,803 | IssuesEvent | 2023-02-04 06:35:48 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | roachtest: disk-stalled/dmsetup failed | C-test-failure O-robot O-roachtest release-blocker branch-release-22.2 | roachtest.disk-stalled/dmsetup [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8580163?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8580163?buildTab=artifacts#/disk-stalled/dmsetup) on release-22.2 @ [9efe3c5c73d3a5eb54b3c4bfe2e3a83504702c39](https://github.com/cockroachdb/cockroach/commits/9efe3c5c73d3a5eb54b3c4bfe2e3a83504702c39):
```
test artifacts and logs in: /artifacts/disk-stalled/dmsetup/run_1
(test_impl.go:286).Fatal: output in run_063449.119660262_n1-4_sudo_mount: sudo mount /mnt/data1 returned: COMMAND_PROBLEM: exit status 32
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>
- #96410 roachtest: disk-stalled/dmsetup failed [C-test-failure O-roachtest O-robot T-storage branch-master release-blocker]
</p>
</details>
/cc @cockroachdb/storage
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*disk-stalled/dmsetup.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 2.0 | roachtest: disk-stalled/dmsetup failed - roachtest.disk-stalled/dmsetup [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8580163?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8580163?buildTab=artifacts#/disk-stalled/dmsetup) on release-22.2 @ [9efe3c5c73d3a5eb54b3c4bfe2e3a83504702c39](https://github.com/cockroachdb/cockroach/commits/9efe3c5c73d3a5eb54b3c4bfe2e3a83504702c39):
```
test artifacts and logs in: /artifacts/disk-stalled/dmsetup/run_1
(test_impl.go:286).Fatal: output in run_063449.119660262_n1-4_sudo_mount: sudo mount /mnt/data1 returned: COMMAND_PROBLEM: exit status 32
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>
- #96410 roachtest: disk-stalled/dmsetup failed [C-test-failure O-roachtest O-robot T-storage branch-master release-blocker]
</p>
</details>
/cc @cockroachdb/storage
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*disk-stalled/dmsetup.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| test | roachtest disk stalled dmsetup failed roachtest disk stalled dmsetup with on release test artifacts and logs in artifacts disk stalled dmsetup run test impl go fatal output in run sudo mount sudo mount mnt returned command problem exit status parameters roachtest cloud gce roachtest cpu roachtest encrypted false roachtest ssd help see see same failure on other branches roachtest disk stalled dmsetup failed cc cockroachdb storage | 1 |
343,284 | 30,654,172,594 | IssuesEvent | 2023-07-25 10:55:52 | brave/brave-browser | https://api.github.com/repos/brave/brave-browser | opened | Incorrect estimated earnings for lower bound when the sys date is set at the begining of the next month and view an Ad | bug feature/rewards QA/Yes QA/Test-Plan-Specified OS/Android | <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description <!-- Provide a brief description of the issue -->
Found while testing https://github.com/brave/brave-browser/issues/30352
Incorrect estimated earnings for lower bound when the sys date is set at the begining of the next month and view an Ad
## Steps to reproduce <!-- Please add a series of steps to reproduce the issue -->
1. Clean profile 1.5.x
2. View 2 ads
3. cashed in 1 ad with the server
4. close the browser
5. Advance the sys date to 4th Aug
6. Relaunch the browser
7. Confirmed that payout processing message is displayed with estimated earnings range 0.008 - 0.010
8. Confirmed that estimated earnings range for the not redeemed ad is 0.008 - 0.010
9. View another ad
10. Estimated earnings range for lower bound is `0.088` instead of `0.016`
## Actual result <!-- Please add screenshots if needed -->
Incorrect estimated earnings for lower bound when the sys date is set at the begining of the next month and view an Ad
## Expected result
## Issue reproduces how often <!-- [Easily reproduced/Intermittent issue/No steps to reproduce] -->
Easy
## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->
- Can you reproduce this issue with the current Play Store version? NA
- Can you reproduce this issue with the current Play Store Beta version? Yes
- Can you reproduce this issue with the current Play Store Nightly version?Yes
## Device details
- Install type (ARM, x86): All
- Device type (Phone, Tablet, Phablet): all
- Android version: 12
## Brave version
1.5.74
### Website problems only
- Does the issue resolve itself when disabling Brave Shields? NA
- Does the issue resolve itself when disabling Brave Rewards?NA
- Is the issue reproducible on the latest version of Chrome? NA
### Additional information
<!-- Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue -->
cc: @brave/qa-team @Miyayes @sujitacharya2005 @deeppandya | 1.0 | Incorrect estimated earnings for lower bound when the sys date is set at the begining of the next month and view an Ad - <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description <!-- Provide a brief description of the issue -->
Found while testing https://github.com/brave/brave-browser/issues/30352
Incorrect estimated earnings for lower bound when the sys date is set at the begining of the next month and view an Ad
## Steps to reproduce <!-- Please add a series of steps to reproduce the issue -->
1. Clean profile 1.5.x
2. View 2 ads
3. cashed in 1 ad with the server
4. close the browser
5. Advance the sys date to 4th Aug
6. Relaunch the browser
7. Confirmed that payout processing message is displayed with estimated earnings range 0.008 - 0.010
8. Confirmed that estimated earnings range for the not redeemed ad is 0.008 - 0.010
9. View another ad
10. Estimated earnings range for lower bound is `0.088` instead of `0.016`
## Actual result <!-- Please add screenshots if needed -->
Incorrect estimated earnings for lower bound when the sys date is set at the begining of the next month and view an Ad
## Expected result
## Issue reproduces how often <!-- [Easily reproduced/Intermittent issue/No steps to reproduce] -->
Easy
## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->
- Can you reproduce this issue with the current Play Store version? NA
- Can you reproduce this issue with the current Play Store Beta version? Yes
- Can you reproduce this issue with the current Play Store Nightly version?Yes
## Device details
- Install type (ARM, x86): All
- Device type (Phone, Tablet, Phablet): all
- Android version: 12
## Brave version
1.5.74
### Website problems only
- Does the issue resolve itself when disabling Brave Shields? NA
- Does the issue resolve itself when disabling Brave Rewards?NA
- Is the issue reproducible on the latest version of Chrome? NA
### Additional information
<!-- Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue -->
cc: @brave/qa-team @Miyayes @sujitacharya2005 @deeppandya | test | incorrect estimated earnings for lower bound when the sys date is set at the begining of the next month and view an ad have you searched for similar issues before submitting this issue please check the open issues and add a note before logging a new issue please use the template below to provide information about the issue insufficient info will get the issue closed it will only be reopened after sufficient info is provided description found while testing incorrect estimated earnings for lower bound when the sys date is set at the begining of the next month and view an ad steps to reproduce clean profile x view ads cashed in ad with the server close the browser advance the sys date to aug relaunch the browser confirmed that payout processing message is displayed with estimated earnings range confirmed that estimated earnings range for the not redeemed ad is view another ad estimated earnings range for lower bound is instead of actual result incorrect estimated earnings for lower bound when the sys date is set at the begining of the next month and view an ad expected result issue reproduces how often easy version channel information can you reproduce this issue with the current play store version na can you reproduce this issue with the current play store beta version yes can you reproduce this issue with the current play store nightly version yes device details install type arm all device type phone tablet phablet all android version brave version website problems only does the issue resolve itself when disabling brave shields na does the issue resolve itself when disabling brave rewards na is the issue reproducible on the latest version of chrome na additional information cc brave qa team miyayes deeppandya | 1 |
280,751 | 21,315,150,505 | IssuesEvent | 2022-04-16 06:22:07 | kaiyichen/pe | https://api.github.com/repos/kaiyichen/pe | opened | page break can be improved | type.DocumentationBug severity.VeryLow | 
Could have use page break before a new command in user guide
<!--session: 1650088856903-6a3e3942-7b34-4316-8b28-e5a0330828ea-->
<!--Version: Web v3.4.2--> | 1.0 | page break can be improved - 
Could have use page break before a new command in user guide
<!--session: 1650088856903-6a3e3942-7b34-4316-8b28-e5a0330828ea-->
<!--Version: Web v3.4.2--> | non_test | page break can be improved could have use page break before a new command in user guide | 0 |
179,386 | 14,703,899,996 | IssuesEvent | 2021-01-04 15:42:35 | sumelms/website | https://api.github.com/repos/sumelms/website | closed | Create the Code of Conduct | documentation :bookmark_tabs: | Discuss and adopt a code of conduct to define Sumé community standards.
We can describe on the website and link with every Sumé application. | 1.0 | Create the Code of Conduct - Discuss and adopt a code of conduct to define Sumé community standards.
We can describe on the website and link with every Sumé application. | non_test | create the code of conduct discuss and adopt a code of conduct to define sumé community standards we can describe on the website and link with every sumé application | 0 |
93,702 | 10,773,590,033 | IssuesEvent | 2019-11-02 21:37:57 | Vertfromage/ManFight | https://api.github.com/repos/Vertfromage/ManFight | closed | Improve the game | Hacktoberfest documentation enhancement good first issue | This is a simple text based java game I made. I thought it would be fun to let any other beginners who have been learning java contribute to it for Hacktoberfest... this will be my first year participating too.
Possible Improvements:
- Add documentation
- Add a monster class
- Add more fight moves
- incorporate the random class
- Add insult method that throws out random insults and causes hurt feelings. | 1.0 | Improve the game - This is a simple text based java game I made. I thought it would be fun to let any other beginners who have been learning java contribute to it for Hacktoberfest... this will be my first year participating too.
Possible Improvements:
- Add documentation
- Add a monster class
- Add more fight moves
- incorporate the random class
- Add insult method that throws out random insults and causes hurt feelings. | non_test | improve the game this is a simple text based java game i made i thought it would be fun to let any other beginners who have been learning java contribute to it for hacktoberfest this will be my first year participating too possible improvements add documentation add a monster class add more fight moves incorporate the random class add insult method that throws out random insults and causes hurt feelings | 0 |
101,350 | 31,035,385,581 | IssuesEvent | 2023-08-10 14:55:44 | zephyrproject-rtos/zephyr | https://api.github.com/repos/zephyrproject-rtos/zephyr | closed | gen_isr_tables: unable to support riscv plic interrupt mapping | bug priority: medium area: Kernel area: Build System area: RISCV | **Describe the bug**
Currently, in a multi-level (nested) interrupt controller arrangement, the maximum number of IRQs supported for a given level is silently hard-coded with a few "magic numbers".
https://github.com/zephyrproject-rtos/zephyr/blob/main/scripts/build/gen_isr_tables.py#L18-L28
The per-level limit set in Python is 255. However, some architectures (RISC-V being one of them) have a standard interrupt controller design that supports far more than 255.
Directly from the RISC-V PLIC specification, this standard interrupt controller supports 1023 IRQs locally (so significantly more than 255).
https://github.com/riscv/riscv-plic-spec/blob/master/riscv-plic.adoc#memory-map
Moreover, there are many boards in Zephyr which already include a PLIC in their Devicetree.
```shell
# likely some duplication, but there are many plics..
grep "plic" $(find boards soc arch -name '*.dts' -o -name '*.dtsi') | wc -l
157
```
Namely, `adp_xc7k_ae350` ([andes_v5_ae350.dtsi](https://github.com/zephyrproject-rtos/zephyr/blob/main/dts/riscv/andes/andes_v5_ae350.dtsi#L179))
This is a bit of "a big deal" because Zephyr is unable to accomadate a fundamental feature of most RISC-V designs. Luckily it is 95% a configuration and build issue.
Please also mention any information which could help others to understand
the problem you're facing:
- What target platform are you using? `adp_xc7k_ae350`
- What have you tried to diagnose or workaround this issue? added to the testsuite and found the root cause of the error
- Is this a regression? Likely not.
**To Reproduce**
Add the test case ~~in the linked PR~~ Linked at the bottom of this issue. Optionally, make the modifications mentioned below to increase verbosity of `gen_isr_tables.py`.
1. `west build -p auto -b adp_xc7k_ae350 -T tests/kernel/gen_isr_table/arch.interrupt.gen_isr_table.riscv64.multi_level`
2. See error
**Expected behavior**
1. The build to succeed without issue.
2. The interrupt is routed and available to SW at the given IRQ
**Impact**
It's actually a bit of a showstopper.
**Logs and console output**
```shell
west build -p auto -b adp_xc7k_ae350 -T tests/kernel/gen_isr_table/arch.interrupt.gen_isr_table.riscv64.multi_level
...
gen_isr_tables.py: 2nd level offsets: [11]
gen_isr_tables.py: (64, 0)
gen_isr_tables.py: Configured interrupt routing
gen_isr_tables.py: handler irq flags param
gen_isr_tables.py: --------------------------
gen_isr_tables.py: 0xa72 1 0 0xb01dface
gen_isr_tables.py: 0x2618 11 0 0x0
gen_isr_tables.py: 0x2c50 2059 0 0x5260
gen_isr_tables.py: 0x3298 7 0 0x0
gen_isr_tables.py: offset is 0
gen_isr_tables.py: num_vectors is 64
gen_isr_tables.py: IRQ = 0x1
gen_isr_tables.py: IRQ_level = 1
gen_isr_tables.py: IRQ_Indx = 1
gen_isr_tables.py: IRQ_Pos = 1
gen_isr_tables.py: IRQ = 0xb
gen_isr_tables.py: IRQ_level = 1
gen_isr_tables.py: IRQ_Indx = 11
gen_isr_tables.py: IRQ_Pos = 11
gen_isr_tables.py: IRQ = 0x80b
gen_isr_tables.py: IRQ_level = 2
gen_isr_tables.py: IRQ_Indx = 8
gen_isr_tables.py: IRQ_Pos = 19
gen_isr_tables.py: IRQ = 0x7
gen_isr_tables.py: IRQ_level = 1
gen_isr_tables.py: IRQ_Indx = 7
gen_isr_tables.py: IRQ_Pos = 7
gen_isr_tables.py: error: MAX_IRQ_PER_AGGREGATOR: 1023 does not fit in the bitmask 0xff
ninja: build stopped: subcommand failed.
```
**Environment (please complete the following information):**
- OS: (e.g. Linux, MacOS, Windows): Linux
- Toolchain (e.g Zephyr SDK, ...): Zephyr SDK v0.16.1
- Commit SHA or Version used: b0e9cb3f480ed475da584d7179c77e0ff19aa80b
**Additional context**
Test case here
https://bit.ly/45i4DL2
| 1.0 | gen_isr_tables: unable to support riscv plic interrupt mapping - **Describe the bug**
Currently, in a multi-level (nested) interrupt controller arrangement, the maximum number of IRQs supported for a given level is silently hard-coded with a few "magic numbers".
https://github.com/zephyrproject-rtos/zephyr/blob/main/scripts/build/gen_isr_tables.py#L18-L28
The per-level limit set in Python is 255. However, some architectures (RISC-V being one of them) have a standard interrupt controller design that supports far more than 255.
Directly from the RISC-V PLIC specification, this standard interrupt controller supports 1023 IRQs locally (so significantly more than 255).
https://github.com/riscv/riscv-plic-spec/blob/master/riscv-plic.adoc#memory-map
Moreover, there are many boards in Zephyr which already include a PLIC in their Devicetree.
```shell
# likely some duplication, but there are many plics..
grep "plic" $(find boards soc arch -name '*.dts' -o -name '*.dtsi') | wc -l
157
```
Namely, `adp_xc7k_ae350` ([andes_v5_ae350.dtsi](https://github.com/zephyrproject-rtos/zephyr/blob/main/dts/riscv/andes/andes_v5_ae350.dtsi#L179))
This is a bit of "a big deal" because Zephyr is unable to accomadate a fundamental feature of most RISC-V designs. Luckily it is 95% a configuration and build issue.
Please also mention any information which could help others to understand
the problem you're facing:
- What target platform are you using? `adp_xc7k_ae350`
- What have you tried to diagnose or workaround this issue? added to the testsuite and found the root cause of the error
- Is this a regression? Likely not.
**To Reproduce**
Add the test case ~~in the linked PR~~ Linked at the bottom of this issue. Optionally, make the modifications mentioned below to increase verbosity of `gen_isr_tables.py`.
1. `west build -p auto -b adp_xc7k_ae350 -T tests/kernel/gen_isr_table/arch.interrupt.gen_isr_table.riscv64.multi_level`
2. See error
**Expected behavior**
1. The build to succeed without issue.
2. The interrupt is routed and available to SW at the given IRQ
**Impact**
It's actually a bit of a showstopper.
**Logs and console output**
```shell
west build -p auto -b adp_xc7k_ae350 -T tests/kernel/gen_isr_table/arch.interrupt.gen_isr_table.riscv64.multi_level
...
gen_isr_tables.py: 2nd level offsets: [11]
gen_isr_tables.py: (64, 0)
gen_isr_tables.py: Configured interrupt routing
gen_isr_tables.py: handler irq flags param
gen_isr_tables.py: --------------------------
gen_isr_tables.py: 0xa72 1 0 0xb01dface
gen_isr_tables.py: 0x2618 11 0 0x0
gen_isr_tables.py: 0x2c50 2059 0 0x5260
gen_isr_tables.py: 0x3298 7 0 0x0
gen_isr_tables.py: offset is 0
gen_isr_tables.py: num_vectors is 64
gen_isr_tables.py: IRQ = 0x1
gen_isr_tables.py: IRQ_level = 1
gen_isr_tables.py: IRQ_Indx = 1
gen_isr_tables.py: IRQ_Pos = 1
gen_isr_tables.py: IRQ = 0xb
gen_isr_tables.py: IRQ_level = 1
gen_isr_tables.py: IRQ_Indx = 11
gen_isr_tables.py: IRQ_Pos = 11
gen_isr_tables.py: IRQ = 0x80b
gen_isr_tables.py: IRQ_level = 2
gen_isr_tables.py: IRQ_Indx = 8
gen_isr_tables.py: IRQ_Pos = 19
gen_isr_tables.py: IRQ = 0x7
gen_isr_tables.py: IRQ_level = 1
gen_isr_tables.py: IRQ_Indx = 7
gen_isr_tables.py: IRQ_Pos = 7
gen_isr_tables.py: error: MAX_IRQ_PER_AGGREGATOR: 1023 does not fit in the bitmask 0xff
ninja: build stopped: subcommand failed.
```
**Environment (please complete the following information):**
- OS: (e.g. Linux, MacOS, Windows): Linux
- Toolchain (e.g Zephyr SDK, ...): Zephyr SDK v0.16.1
- Commit SHA or Version used: b0e9cb3f480ed475da584d7179c77e0ff19aa80b
**Additional context**
Test case here
https://bit.ly/45i4DL2
| non_test | gen isr tables unable to support riscv plic interrupt mapping describe the bug currently in a multi level nested interrupt controller arrangement the maximum number of irqs supported for a given level is silently hard coded with a few magic numbers the per level limit set in python is however some architectures risc v being one of them have a standard interrupt controller design that supports far more than directly from the risc v plic specification this standard interrupt controller supports irqs locally so significantly more than moreover there are many boards in zephyr which already include a plic in their devicetree shell likely some duplication but there are many plics grep plic find boards soc arch name dts o name dtsi wc l namely adp this is a bit of a big deal because zephyr is unable to accomadate a fundamental feature of most risc v designs luckily it is a configuration and build issue please also mention any information which could help others to understand the problem you re facing what target platform are you using adp what have you tried to diagnose or workaround this issue added to the testsuite and found the root cause of the error is this a regression likely not to reproduce add the test case in the linked pr linked at the bottom of this issue optionally make the modifications mentioned below to increase verbosity of gen isr tables py west build p auto b adp t tests kernel gen isr table arch interrupt gen isr table multi level see error expected behavior the build to succeed without issue the interrupt is routed and available to sw at the given irq impact it s actually a bit of a showstopper logs and console output shell west build p auto b adp t tests kernel gen isr table arch interrupt gen isr table multi level gen isr tables py level offsets gen isr tables py gen isr tables py configured interrupt routing gen isr tables py handler irq flags param gen isr tables py gen isr tables py gen isr tables py gen isr tables py gen isr tables py gen isr tables py offset is gen isr tables py num vectors is gen isr tables py irq gen isr tables py irq level gen isr tables py irq indx gen isr tables py irq pos gen isr tables py irq gen isr tables py irq level gen isr tables py irq indx gen isr tables py irq pos gen isr tables py irq gen isr tables py irq level gen isr tables py irq indx gen isr tables py irq pos gen isr tables py irq gen isr tables py irq level gen isr tables py irq indx gen isr tables py irq pos gen isr tables py error max irq per aggregator does not fit in the bitmask ninja build stopped subcommand failed environment please complete the following information os e g linux macos windows linux toolchain e g zephyr sdk zephyr sdk commit sha or version used additional context test case here | 0 |
115,753 | 24,807,772,213 | IssuesEvent | 2022-10-25 06:54:23 | zhmcclient/python-zhmcclient | https://api.github.com/repos/zhmcclient/python-zhmcclient | closed | Add support for Lpar Reset Normal, and add os_ipl_token parameter to Lpar Reset Clear | area: code type: feature resolution: fixed | Needed for corresponding functionality on zhmccli project, see https://github.com/zhmcclient/zhmccli/issues/111 | 1.0 | Add support for Lpar Reset Normal, and add os_ipl_token parameter to Lpar Reset Clear - Needed for corresponding functionality on zhmccli project, see https://github.com/zhmcclient/zhmccli/issues/111 | non_test | add support for lpar reset normal and add os ipl token parameter to lpar reset clear needed for corresponding functionality on zhmccli project see | 0 |
340,526 | 24,658,675,333 | IssuesEvent | 2022-10-18 03:38:41 | ICEI-PUC-Minas-PMV-SI/pmv-si-2022-2-e1-proj-web-t3-conexao-melhor-idade | https://api.github.com/repos/ICEI-PUC-Minas-PMV-SI/pmv-si-2022-2-e1-proj-web-t3-conexao-melhor-idade | closed | Criar design de página Home page - usuário logado - Profissional | documentation | Barra de pesquisa
Postos de saúde e hospitais mais próximos (google maps)
| 1.0 | Criar design de página Home page - usuário logado - Profissional - Barra de pesquisa
Postos de saúde e hospitais mais próximos (google maps)
| non_test | criar design de página home page usuário logado profissional barra de pesquisa postos de saúde e hospitais mais próximos google maps | 0 |
193,746 | 14,661,325,548 | IssuesEvent | 2020-12-29 03:14:01 | whileTrue0x90/challenge-bot-test | https://api.github.com/repos/whileTrue0x90/challenge-bot-test | closed | RRTT | challenge-program picked sig/test | ## Description
issue background
## Tasks
task 1
task 2
task 3
## Score
100
## Mentor
whileTrue0x90
## Recommended Skills
skill 1
skill 2
skill 3
## Learning Materials(optional)
nothing
| 1.0 | RRTT - ## Description
issue background
## Tasks
task 1
task 2
task 3
## Score
100
## Mentor
whileTrue0x90
## Recommended Skills
skill 1
skill 2
skill 3
## Learning Materials(optional)
nothing
| test | rrtt description issue background tasks task task task score mentor recommended skills skill skill skill learning materials optional nothing | 1 |
126,876 | 26,933,572,736 | IssuesEvent | 2023-02-07 18:40:49 | qexat/pyvism | https://api.github.com/repos/qexat/pyvism | closed | List concatenation is not consistent | issue: good first issue topic: code style type: report | `src/pyvism/runtime/errors.py` has two occurrences of list concatenation:
```py
# a + [b]
def _get_ruler_size(self) -> int:
return len(str(max(line.number for line in self.info_lines + [self.error_line]))) + 1
```
```py
# [*a, b]
@property
def lines(self) -> list[MessageLine]:
return sorted([*self.info_lines, self.error_line], key=lambda line: line.number)
```
I believe it should be consistent and only one of the ways should be used. In my (and [`ruff`](https://github.com/charliermarsh/ruff)'s) opinion, it should be the latter as it's [faster](https://github.com/charliermarsh/ruff/pull/1957) and easier to read.
| 1.0 | List concatenation is not consistent - `src/pyvism/runtime/errors.py` has two occurrences of list concatenation:
```py
# a + [b]
def _get_ruler_size(self) -> int:
return len(str(max(line.number for line in self.info_lines + [self.error_line]))) + 1
```
```py
# [*a, b]
@property
def lines(self) -> list[MessageLine]:
return sorted([*self.info_lines, self.error_line], key=lambda line: line.number)
```
I believe it should be consistent and only one of the ways should be used. In my (and [`ruff`](https://github.com/charliermarsh/ruff)'s) opinion, it should be the latter as it's [faster](https://github.com/charliermarsh/ruff/pull/1957) and easier to read.
| non_test | list concatenation is not consistent src pyvism runtime errors py has two occurrences of list concatenation py a def get ruler size self int return len str max line number for line in self info lines py property def lines self list return sorted key lambda line line number i believe it should be consistent and only one of the ways should be used in my and opinion it should be the latter as it s and easier to read | 0 |
176,492 | 13,643,890,556 | IssuesEvent | 2020-09-25 17:55:21 | microsoft/azuredatastudio | https://api.github.com/repos/microsoft/azuredatastudio | closed | A11y_AzureDataStudio_Welcome_ExtendyourdataStudio_ScreenReader : The "SQL Admin Pack" is not announced as heading element for screen reader users. | A11y_July27_2020_TestPass Area - Shell Bug Triage: Done | **"[Check out Accessibility Insights!](https://nam06.safelinks.protection.outlook.com/?url=https://accessibilityinsights.io/&data=02%7c01%7cv-manai%40microsoft.com%7cb67b2c4b646d4f9561a208d6f4b5c39b%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636965458847260936&sdata=T26HQfSGOlnuRQdX%2ByXk%2B2bxqgwFvCIVfuboZUWidYY%3D&reserved=0) - Identify accessibility bugs before check-in and make bug fixing faster and easier.”**
GitHubTags:#A11y_AzureDataStudioJuly2020;#A11y_July27_2020_TestPass;#A11yMAS;#A11yTCS;#SQL Azure Data Studio;#Benchmark;#MAC;#Screenreader;#VoiceOver;#A11ySev2;#Benchmark;#MAS1.3.1;#MAS2.4.6;#FTP;
### Environment Details:
Application Name: Azure Data Studio
Application Version: 1.21.0-insider
Commit: eccf3cf
Date: 2020-07-24T09:28:31.172Z
VS Code: 1.48.0
Electron: 9.1.0
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Darwin x64 19.6.0
Operating system: macOS Catalina (Version 10.15.6 (19G73)
Screen Reader: VoiceOver
MAS References: MAS1.3.1, MAS2.4.6
### Repro Steps:
1. Launch Azure Data Studio Insiders application.
2. If Welcome screen is not shown on application launch, then navigate to Help --> Welcome.
3. Navigate Extend your data Studio on Welcome screen.
4. Start screen reader, navigate to the "SQL Admin Pack" text and observe if it is announced as a heading element.
### Actual:
When screen reader users navigate to the "SQL Admin Pack" text it is announced as a plain text but visually it is appearing as a heading element.
### Expected:
The "SQL Admin Pack" text should be announced as a heading element with level 3 for screen reader users.
### User Impact:
If the text that is visually appearing as an heading element but the same is not announced to the screen reader users then the screen reader users will have difficulty in understanding the structure of the screen content.
### Attachment link for Reference:
[11550_A11y_AzureDataStudio_Welcome_ExtendyourdataStudio_ScreenReader The "SQL Admin Pack" is not announced as heading element for screen reader users.zip](https://github.com/microsoft/azuredatastudio/files/4986021/11550_A11y_AzureDataStudio_Welcome_ExtendyourdataStudio_ScreenReader.The.SQL.Admin.Pack.is.not.announced.as.heading.element.for.screen.reader.users.zip) | 1.0 | A11y_AzureDataStudio_Welcome_ExtendyourdataStudio_ScreenReader : The "SQL Admin Pack" is not announced as heading element for screen reader users. - **"[Check out Accessibility Insights!](https://nam06.safelinks.protection.outlook.com/?url=https://accessibilityinsights.io/&data=02%7c01%7cv-manai%40microsoft.com%7cb67b2c4b646d4f9561a208d6f4b5c39b%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636965458847260936&sdata=T26HQfSGOlnuRQdX%2ByXk%2B2bxqgwFvCIVfuboZUWidYY%3D&reserved=0) - Identify accessibility bugs before check-in and make bug fixing faster and easier.”**
GitHubTags:#A11y_AzureDataStudioJuly2020;#A11y_July27_2020_TestPass;#A11yMAS;#A11yTCS;#SQL Azure Data Studio;#Benchmark;#MAC;#Screenreader;#VoiceOver;#A11ySev2;#Benchmark;#MAS1.3.1;#MAS2.4.6;#FTP;
### Environment Details:
Application Name: Azure Data Studio
Application Version: 1.21.0-insider
Commit: eccf3cf
Date: 2020-07-24T09:28:31.172Z
VS Code: 1.48.0
Electron: 9.1.0
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Darwin x64 19.6.0
Operating system: macOS Catalina (Version 10.15.6 (19G73)
Screen Reader: VoiceOver
MAS References: MAS1.3.1, MAS2.4.6
### Repro Steps:
1. Launch Azure Data Studio Insiders application.
2. If Welcome screen is not shown on application launch, then navigate to Help --> Welcome.
3. Navigate Extend your data Studio on Welcome screen.
4. Start screen reader, navigate to the "SQL Admin Pack" text and observe if it is announced as a heading element.
### Actual:
When screen reader users navigate to the "SQL Admin Pack" text it is announced as a plain text but visually it is appearing as a heading element.
### Expected:
The "SQL Admin Pack" text should be announced as a heading element with level 3 for screen reader users.
### User Impact:
If the text that is visually appearing as an heading element but the same is not announced to the screen reader users then the screen reader users will have difficulty in understanding the structure of the screen content.
### Attachment link for Reference:
[11550_A11y_AzureDataStudio_Welcome_ExtendyourdataStudio_ScreenReader The "SQL Admin Pack" is not announced as heading element for screen reader users.zip](https://github.com/microsoft/azuredatastudio/files/4986021/11550_A11y_AzureDataStudio_Welcome_ExtendyourdataStudio_ScreenReader.The.SQL.Admin.Pack.is.not.announced.as.heading.element.for.screen.reader.users.zip) | test | azuredatastudio welcome extendyourdatastudio screenreader the sql admin pack is not announced as heading element for screen reader users identify accessibility bugs before check in and make bug fixing faster and easier ” githubtags testpass sql azure data studio benchmark mac screenreader voiceover benchmark ftp environment details application name azure data studio application version insider commit date vs code electron chrome node js electron os darwin operating system macos catalina version screen reader voiceover mas references repro steps launch azure data studio insiders application if welcome screen is not shown on application launch then navigate to help welcome navigate extend your data studio on welcome screen start screen reader navigate to the sql admin pack text and observe if it is announced as a heading element actual when screen reader users navigate to the sql admin pack text it is announced as a plain text but visually it is appearing as a heading element expected the sql admin pack text should be announced as a heading element with level for screen reader users user impact if the text that is visually appearing as an heading element but the same is not announced to the screen reader users then the screen reader users will have difficulty in understanding the structure of the screen content attachment link for reference | 1 |
31,490 | 13,537,350,648 | IssuesEvent | 2020-09-16 10:21:48 | terraform-providers/terraform-provider-aws | https://api.github.com/repos/terraform-providers/terraform-provider-aws | closed | aws_route53_zone_association is unable to create/read/import associations from another account | service/route53 waiting-response | ### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
### Terraform CLI and Terraform AWS Provider Version
Terraform v0.13.2
+ provider registry.terraform.io/hashicorp/aws v3.5.0
### Affected Resource(s)
* aws_route53_zone_association
### Terraform Configuration Files
```hcl
resource "aws_route53_zone_association" "external-account-zone-association" {
zone_id = "AAAAAAAAAAAAAA"
vpc_id = "vpc-aaaaaaaaaaaaa" # VPC ID from another account
vpc_region = "us-east-1"
}
```
### Debug Output
https://gist.github.com/hmrbarros/59f7401c331083e93850671bcc475983
### Panic Output
N/A
### Expected Behavior
Should be imported, the values are correct and the associations exists.
It's working on version 2.70 of the provider.
### Actual Behavior
```
Error: Cannot import non-existent remote object
```
### Steps to Reproduce
- `terraform import 'aws_route53_zone_association.zone_association["AAAAAAAAAAAAAA_vpc-aaaaaaaaaaaaa"]' 'AAAAAAAAAAAAAA:vpc-aaaaaaaaaaaaa'`
### Important Factoids
We have full permissions in the account that owns the Route53 Zone and no permissions in the account that owns the VPC.
Although the code here represents the issue when importing the resource, the same happens when creating a new resource in the same conditions.
If a state from 2.70 exists, 3.5 will ignore these resources that reference VPCs in another account
### References
N?A
| 1.0 | aws_route53_zone_association is unable to create/read/import associations from another account - ### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
### Terraform CLI and Terraform AWS Provider Version
Terraform v0.13.2
+ provider registry.terraform.io/hashicorp/aws v3.5.0
### Affected Resource(s)
* aws_route53_zone_association
### Terraform Configuration Files
```hcl
resource "aws_route53_zone_association" "external-account-zone-association" {
zone_id = "AAAAAAAAAAAAAA"
vpc_id = "vpc-aaaaaaaaaaaaa" # VPC ID from another account
vpc_region = "us-east-1"
}
```
### Debug Output
https://gist.github.com/hmrbarros/59f7401c331083e93850671bcc475983
### Panic Output
N/A
### Expected Behavior
Should be imported, the values are correct and the associations exists.
It's working on version 2.70 of the provider.
### Actual Behavior
```
Error: Cannot import non-existent remote object
```
### Steps to Reproduce
- `terraform import 'aws_route53_zone_association.zone_association["AAAAAAAAAAAAAA_vpc-aaaaaaaaaaaaa"]' 'AAAAAAAAAAAAAA:vpc-aaaaaaaaaaaaa'`
### Important Factoids
We have full permissions in the account that owns the Route53 Zone and no permissions in the account that owns the VPC.
Although the code here represents the issue when importing the resource, the same happens when creating a new resource in the same conditions.
If a state from 2.70 exists, 3.5 will ignore these resources that reference VPCs in another account
### References
N?A
| non_test | aws zone association is unable to create read import associations from another account community note please vote on this issue by adding a 👍 to the original issue to help the community and maintainers prioritize this request please do not leave or other comments that do not add relevant new information or questions they generate extra noise for issue followers and do not help prioritize the request if you are interested in working on this issue or have submitted a pull request please leave a comment terraform cli and terraform aws provider version terraform provider registry terraform io hashicorp aws affected resource s aws zone association terraform configuration files hcl resource aws zone association external account zone association zone id aaaaaaaaaaaaaa vpc id vpc aaaaaaaaaaaaa vpc id from another account vpc region us east debug output panic output n a expected behavior should be imported the values are correct and the associations exists it s working on version of the provider actual behavior error cannot import non existent remote object steps to reproduce terraform import aws zone association zone association aaaaaaaaaaaaaa vpc aaaaaaaaaaaaa important factoids we have full permissions in the account that owns the zone and no permissions in the account that owns the vpc although the code here represents the issue when importing the resource the same happens when creating a new resource in the same conditions if a state from exists will ignore these resources that reference vpcs in another account references n a | 0 |
470,901 | 13,548,959,333 | IssuesEvent | 2020-09-17 07:27:56 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.amazon.com.mx - see bug description | browser-fenix engine-gecko priority-important | <!-- @browser: Firefox Mobile 81.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.1.0; Mobile; rv:81.0) Gecko/81.0 Firefox/81.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/58370 -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://www.amazon.com.mx/
**Browser / Version**: Firefox Mobile 81.0
**Operating System**: Android 8.1.0
**Tested Another Browser**: Yes Chrome
**Problem type**: Something else
**Description**: When you click the menu and go to the end a rectangle cover the last part of the menu, inside your account it covers the exit option.
**Steps to Reproduce**:
<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: 20200910180444</li><li>channel: beta</li><li>hasTouchScreen: true</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.amazon.com.mx - see bug description - <!-- @browser: Firefox Mobile 81.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.1.0; Mobile; rv:81.0) Gecko/81.0 Firefox/81.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/58370 -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://www.amazon.com.mx/
**Browser / Version**: Firefox Mobile 81.0
**Operating System**: Android 8.1.0
**Tested Another Browser**: Yes Chrome
**Problem type**: Something else
**Description**: When you click the menu and go to the end a rectangle cover the last part of the menu, inside your account it covers the exit option.
**Steps to Reproduce**:
<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: 20200910180444</li><li>channel: beta</li><li>hasTouchScreen: true</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_test | see bug description url browser version firefox mobile operating system android tested another browser yes chrome problem type something else description when you click the menu and go to the end a rectangle cover the last part of the menu inside your account it covers the exit option 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 from with ❤️ | 0 |
184,829 | 14,289,966,075 | IssuesEvent | 2020-11-23 20:06:49 | github-vet/rangeclosure-findings | https://api.github.com/repos/github-vet/rangeclosure-findings | closed | themotion/ladder: autoscaler/scale/aws/ecs_test.go; 46 LoC | fresh small test |
Found a possible issue in [themotion/ladder](https://www.github.com/themotion/ladder) at [autoscaler/scale/aws/ecs_test.go](https://github.com/themotion/ladder/blob/9e85f8be9014184a1aa02912df16532394e7a9e4/autoscaler/scale/aws/ecs_test.go#L239-L284)
The below snippet of Go code triggered static analysis which searches for goroutines and/or defer statements
which capture loop variables.
[Click here to see the code in its original context.](https://github.com/themotion/ladder/blob/9e85f8be9014184a1aa02912df16532394e7a9e4/autoscaler/scale/aws/ecs_test.go#L239-L284)
<details>
<summary>Click here to show the 46 line(s) of Go which triggered the analyzer.</summary>
```go
for _, test := range tests {
ctrl := gomock.NewController(t)
defer ctrl.Finish()
mockECS := sdk.NewMockECSAPI(ctrl)
// Set our mock desired result
awsMock.MockECSDescribeServicesMultiple(t, mockECS, []string{"test"}, int64(test.current))
ops := map[string]interface{}{
ecsAwsRegionOpt: "us-west-2",
ecsClusterNameOpt: "testCluster",
ecsServiceNameOpt: "test",
}
e, err := NewECSService(context.TODO(), ops)
if err != nil {
t.Errorf("\n- Creation shouldn't give error: %v", err)
}
e.client = mockECS
e.waiterInterval = 2 * time.Millisecond
res := make(chan error)
go func() {
err := e.Wait(context.TODO(), types.Quantity{Q: test.desired}, types.NotScaling)
if err != nil {
t.Fatalf("Wait returned error, it shoudln't: %s", err)
}
res <- nil
}()
var timeout bool
select {
case <-time.After(10 * time.Millisecond):
timeout = true
case <-res:
}
close(res)
if test.wantTimeout && !timeout {
t.Error("Wait should timeout, it dind't")
}
if !test.wantTimeout && timeout {
t.Error("Wait shouldn't timeout, it did")
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 9e85f8be9014184a1aa02912df16532394e7a9e4
| 1.0 | themotion/ladder: autoscaler/scale/aws/ecs_test.go; 46 LoC -
Found a possible issue in [themotion/ladder](https://www.github.com/themotion/ladder) at [autoscaler/scale/aws/ecs_test.go](https://github.com/themotion/ladder/blob/9e85f8be9014184a1aa02912df16532394e7a9e4/autoscaler/scale/aws/ecs_test.go#L239-L284)
The below snippet of Go code triggered static analysis which searches for goroutines and/or defer statements
which capture loop variables.
[Click here to see the code in its original context.](https://github.com/themotion/ladder/blob/9e85f8be9014184a1aa02912df16532394e7a9e4/autoscaler/scale/aws/ecs_test.go#L239-L284)
<details>
<summary>Click here to show the 46 line(s) of Go which triggered the analyzer.</summary>
```go
for _, test := range tests {
ctrl := gomock.NewController(t)
defer ctrl.Finish()
mockECS := sdk.NewMockECSAPI(ctrl)
// Set our mock desired result
awsMock.MockECSDescribeServicesMultiple(t, mockECS, []string{"test"}, int64(test.current))
ops := map[string]interface{}{
ecsAwsRegionOpt: "us-west-2",
ecsClusterNameOpt: "testCluster",
ecsServiceNameOpt: "test",
}
e, err := NewECSService(context.TODO(), ops)
if err != nil {
t.Errorf("\n- Creation shouldn't give error: %v", err)
}
e.client = mockECS
e.waiterInterval = 2 * time.Millisecond
res := make(chan error)
go func() {
err := e.Wait(context.TODO(), types.Quantity{Q: test.desired}, types.NotScaling)
if err != nil {
t.Fatalf("Wait returned error, it shoudln't: %s", err)
}
res <- nil
}()
var timeout bool
select {
case <-time.After(10 * time.Millisecond):
timeout = true
case <-res:
}
close(res)
if test.wantTimeout && !timeout {
t.Error("Wait should timeout, it dind't")
}
if !test.wantTimeout && timeout {
t.Error("Wait shouldn't timeout, it did")
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 9e85f8be9014184a1aa02912df16532394e7a9e4
| test | themotion ladder autoscaler scale aws ecs test go loc found a possible issue in at the below snippet of go code triggered static analysis which searches for goroutines and or defer statements which capture loop variables click here to show the line s of go which triggered the analyzer go for test range tests ctrl gomock newcontroller t defer ctrl finish mockecs sdk newmockecsapi ctrl set our mock desired result awsmock mockecsdescribeservicesmultiple t mockecs string test test current ops map interface ecsawsregionopt us west ecsclusternameopt testcluster ecsservicenameopt test e err newecsservice context todo ops if err nil t errorf n creation shouldn t give error v err e client mockecs e waiterinterval time millisecond res make chan error go func err e wait context todo types quantity q test desired types notscaling if err nil t fatalf wait returned error it shoudln t s err res nil var timeout bool select case time after time millisecond timeout true case res close res if test wanttimeout timeout t error wait should timeout it dind t if test wanttimeout timeout t error wait shouldn t timeout it did leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id | 1 |
257,998 | 22,269,109,207 | IssuesEvent | 2022-06-10 10:24:44 | wso2/product-is | https://api.github.com/repos/wso2/product-is | opened | Basic authentication is not supported in TOTP and FIDO | docs IS-6.0.0-Test-Hackathon | **Is your suggestion related to a missing or misleading document? Please describe.**
Even though basic authentication is mentioned in the documents it's not supported with REST APIs calls to [FIDO](https://is.docs.wso2.com/en/latest/develop/fido-rest-api/) and [TOTP](https://is.docs.wso2.com/en/latest/develop/totp-rest-api/).
<img width="1512" alt="Screenshot 2022-06-10 at 15 51 45" src="https://user-images.githubusercontent.com/38417165/173045527-490df9cf-a6b9-461c-a1c8-b58bfabedcdc.png">
**Describe the improvement**
Add necessary steps on using a token to invoke REST APIs calls to documentation.
| 1.0 | Basic authentication is not supported in TOTP and FIDO - **Is your suggestion related to a missing or misleading document? Please describe.**
Even though basic authentication is mentioned in the documents it's not supported with REST APIs calls to [FIDO](https://is.docs.wso2.com/en/latest/develop/fido-rest-api/) and [TOTP](https://is.docs.wso2.com/en/latest/develop/totp-rest-api/).
<img width="1512" alt="Screenshot 2022-06-10 at 15 51 45" src="https://user-images.githubusercontent.com/38417165/173045527-490df9cf-a6b9-461c-a1c8-b58bfabedcdc.png">
**Describe the improvement**
Add necessary steps on using a token to invoke REST APIs calls to documentation.
| test | basic authentication is not supported in totp and fido is your suggestion related to a missing or misleading document please describe even though basic authentication is mentioned in the documents it s not supported with rest apis calls to and img width alt screenshot at src describe the improvement add necessary steps on using a token to invoke rest apis calls to documentation | 1 |
110,648 | 13,925,288,754 | IssuesEvent | 2020-10-21 16:38:33 | flutter/flutter | https://api.github.com/repos/flutter/flutter | closed | Text with different styles in TextField cause the cursor to stall on web. | a: text input e: web_canvaskit e: web_html engine f: material design found in release: 1.24 framework has reproducible steps platform-web | I'm creating a custom TextEditingController to support for different styles within a single textfield. So I have overridden the ### `buildTextSpan `function in a child class of `TextEditingController `like this:
```
class NewTextEditingController extends TextEditingController {
NewTextEditingController({String text})
: assert(text != null),
super(text: text);
@override
TextSpan buildTextSpan({TextStyle style, bool withComposing}) {
return TextSpan(
children: [TextSpan(text: text.substring(0, 2)),
TextSpan(text: text.substring(2),style: TextStyle(fontWeight: FontWeight.w700))], style: style);
}
}
```
This controller just displays the first letters of the textfield as regular weight and the remaining part as bold.
Then I modified the `_MyHomePageState` class in the default application to have a textfield in a listview like this:
```
class _MyHomePageState extends State<MyHomePage> {
NewTextEditingController controller = new NewTextEditingController(text: "test");
@override
Widget build(BuildContext context) {
return Scaffold(
body: Material(
color: Colors.white,
child: ListView(
children: [
TextField(
controller: controller,
)
],
),
),
);
}
}
```
And while on mobile it works just fine:
On web the cursor doesn't move from the initial position (0) and the text just gets added at the end. Selection is also not possible.
Futter doctor:
```
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel master, 1.24.0-2.0.pre.86, on Microsoft Windows [Version ], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.5.4)
[√] Android Studio (version 4.0)
[√] VS Code, 64-bit edition (version 1.49.3)
[√] Connected device (3 available)
• No issues found!
```
| 1.0 | Text with different styles in TextField cause the cursor to stall on web. - I'm creating a custom TextEditingController to support for different styles within a single textfield. So I have overridden the ### `buildTextSpan `function in a child class of `TextEditingController `like this:
```
class NewTextEditingController extends TextEditingController {
NewTextEditingController({String text})
: assert(text != null),
super(text: text);
@override
TextSpan buildTextSpan({TextStyle style, bool withComposing}) {
return TextSpan(
children: [TextSpan(text: text.substring(0, 2)),
TextSpan(text: text.substring(2),style: TextStyle(fontWeight: FontWeight.w700))], style: style);
}
}
```
This controller just displays the first letters of the textfield as regular weight and the remaining part as bold.
Then I modified the `_MyHomePageState` class in the default application to have a textfield in a listview like this:
```
class _MyHomePageState extends State<MyHomePage> {
NewTextEditingController controller = new NewTextEditingController(text: "test");
@override
Widget build(BuildContext context) {
return Scaffold(
body: Material(
color: Colors.white,
child: ListView(
children: [
TextField(
controller: controller,
)
],
),
),
);
}
}
```
And while on mobile it works just fine:
On web the cursor doesn't move from the initial position (0) and the text just gets added at the end. Selection is also not possible.
Futter doctor:
```
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel master, 1.24.0-2.0.pre.86, on Microsoft Windows [Version ], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.5.4)
[√] Android Studio (version 4.0)
[√] VS Code, 64-bit edition (version 1.49.3)
[√] Connected device (3 available)
• No issues found!
```
| non_test | text with different styles in textfield cause the cursor to stall on web i m creating a custom texteditingcontroller to support for different styles within a single textfield so i have overridden the buildtextspan function in a child class of texteditingcontroller like this class newtexteditingcontroller extends texteditingcontroller newtexteditingcontroller string text assert text null super text text override textspan buildtextspan textstyle style bool withcomposing return textspan children textspan text text substring textspan text text substring style textstyle fontweight fontweight style style this controller just displays the first letters of the textfield as regular weight and the remaining part as bold then i modified the myhomepagestate class in the default application to have a textfield in a listview like this class myhomepagestate extends state newtexteditingcontroller controller new newtexteditingcontroller text test override widget build buildcontext context return scaffold body material color colors white child listview children textfield controller controller and while on mobile it works just fine on web the cursor doesn t move from the initial position and the text just gets added at the end selection is also not possible futter doctor doctor summary to see all details run flutter doctor v flutter channel master pre on microsoft windows locale en us android toolchain develop for android devices android sdk version chrome develop for the web visual studio develop for windows visual studio community android studio version vs code bit edition version connected device available • no issues found | 0 |
97,362 | 8,653,070,534 | IssuesEvent | 2018-11-27 09:52:58 | humera987/FXLabs-Test-Automation | https://api.github.com/repos/humera987/FXLabs-Test-Automation | closed | new tested 27 : ApiV1TestSuitesProjectIdIdCoverageGetPathParamIdMysqlSqlInjectionTimebound | new tested 27 | Project : new tested 27
Job : UAT
Env : UAT
Region : US_WEST
Result : fail
Status Code : 404
Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=MjkwN2MzZTgtYThhZi00ZjdhLWE0OGYtNDVhYTE5NGM5YmRm; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Tue, 27 Nov 2018 09:48:48 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/test-suites/project-id//coverage
Request :
Response :
{
"timestamp" : "2018-11-27T09:48:48.881+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/test-suites/project-id/coverage"
}
Logs :
Assertion [@ResponseTime < 7000 OR @ResponseTime > 10000] resolved-to [966 < 7000 OR 966 > 10000] result [Passed]Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]
--- FX Bot --- | 1.0 | new tested 27 : ApiV1TestSuitesProjectIdIdCoverageGetPathParamIdMysqlSqlInjectionTimebound - Project : new tested 27
Job : UAT
Env : UAT
Region : US_WEST
Result : fail
Status Code : 404
Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=MjkwN2MzZTgtYThhZi00ZjdhLWE0OGYtNDVhYTE5NGM5YmRm; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Tue, 27 Nov 2018 09:48:48 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/test-suites/project-id//coverage
Request :
Response :
{
"timestamp" : "2018-11-27T09:48:48.881+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/test-suites/project-id/coverage"
}
Logs :
Assertion [@ResponseTime < 7000 OR @ResponseTime > 10000] resolved-to [966 < 7000 OR 966 > 10000] result [Passed]Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]
--- FX Bot --- | test | new tested project new tested job uat env uat region us west result fail status code headers x content type options x xss protection cache control pragma expires x frame options set cookie content type transfer encoding date endpoint request response timestamp status error not found message no message available path api api test suites project id coverage logs assertion resolved to result assertion resolved to result fx bot | 1 |
724,549 | 24,934,564,033 | IssuesEvent | 2022-10-31 14:15:28 | MicroHealthLLC/mSuite | https://api.github.com/repos/MicroHealthLLC/mSuite | closed | TreeChart: Save Private map (without default content) should not get automatically deleted after reload/refresh OR collaborator clicks "Verify" on Password modal. | bug priority | Screenshot Example of non-default Save Private map; reload/refresh clicked; map automatically gets deleted and the index screen displays
_____________________________________________________________
Screenshot Example of non-default Save Private map; collaborator inputs password, clicks Verify
Screenshot Example of Index screen or 404 Error screen displaying after map was automatically deleted
| 1.0 | TreeChart: Save Private map (without default content) should not get automatically deleted after reload/refresh OR collaborator clicks "Verify" on Password modal. - Screenshot Example of non-default Save Private map; reload/refresh clicked; map automatically gets deleted and the index screen displays
_____________________________________________________________
Screenshot Example of non-default Save Private map; collaborator inputs password, clicks Verify
Screenshot Example of Index screen or 404 Error screen displaying after map was automatically deleted
| non_test | treechart save private map without default content should not get automatically deleted after reload refresh or collaborator clicks verify on password modal screenshot example of non default save private map reload refresh clicked map automatically gets deleted and the index screen displays screenshot example of non default save private map collaborator inputs password clicks verify screenshot example of index screen or error screen displaying after map was automatically deleted | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.