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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
45,415 | 5,714,179,138 | IssuesEvent | 2017-04-19 09:43:20 | nextgis/nextgisweb_compulink | https://api.github.com/repos/nextgis/nextgisweb_compulink | closed | Загрузка документов в форме принятых участков | 4 test enhancement frontend | Предлагаю сделать просто - грузить всегда, даже если объект не создается | 1.0 | Загрузка документов в форме принятых участков - Предлагаю сделать просто - грузить всегда, даже если объект не создается | test | загрузка документов в форме принятых участков предлагаю сделать просто грузить всегда даже если объект не создается | 1 |
507,182 | 14,679,932,928 | IssuesEvent | 2020-12-31 08:31:50 | k8smeetup/website-tasks | https://api.github.com/repos/k8smeetup/website-tasks | opened | /docs/concepts/storage/persistent-volumes.md | lang/zh priority/P0 sync/update version/master welcome | Source File: [/docs/concepts/storage/persistent-volumes.md](https://github.com/kubernetes/website/blob/master/content/en/docs/concepts/storage/persistent-volumes.md)
Diff 命令参考:
```bash
# 查看原始文档与翻译文档更新差异
git diff --no-index -- content/en/docs/concepts/storage/persistent-volumes.md content/zh/docs/concepts/storage/persistent-volumes.md
# 跨分支持查看原始文档更新差异
git diff release-1.19 master -- content/en/docs/concepts/storage/persistent-volumes.md
``` | 1.0 | /docs/concepts/storage/persistent-volumes.md - Source File: [/docs/concepts/storage/persistent-volumes.md](https://github.com/kubernetes/website/blob/master/content/en/docs/concepts/storage/persistent-volumes.md)
Diff 命令参考:
```bash
# 查看原始文档与翻译文档更新差异
git diff --no-index -- content/en/docs/concepts/storage/persistent-volumes.md content/zh/docs/concepts/storage/persistent-volumes.md
# 跨分支持查看原始文档更新差异
git diff release-1.19 master -- content/en/docs/concepts/storage/persistent-volumes.md
``` | non_test | docs concepts storage persistent volumes md source file diff 命令参考 bash 查看原始文档与翻译文档更新差异 git diff no index content en docs concepts storage persistent volumes md content zh docs concepts storage persistent volumes md 跨分支持查看原始文档更新差异 git diff release master content en docs concepts storage persistent volumes md | 0 |
218,666 | 17,014,097,996 | IssuesEvent | 2021-07-02 09:30:07 | microsoft/PowerToys | https://api.github.com/repos/microsoft/PowerToys | closed | [FancyZones] Failing unit tests | Area-Tests Product-FancyZones Resolution-Fix-Committed | Tests `EditorArgsUnitTests::MonitorToJson` and `EditorArgsUnitTests::EditorArgsToJson` are failing due to changes in https://github.com/microsoft/PowerToys/pull/11840, where new members `width` and `height` were added to the `MonitorInfo` struct.
In the tests expected values are incorrectly initialized and cause improper results. | 1.0 | [FancyZones] Failing unit tests - Tests `EditorArgsUnitTests::MonitorToJson` and `EditorArgsUnitTests::EditorArgsToJson` are failing due to changes in https://github.com/microsoft/PowerToys/pull/11840, where new members `width` and `height` were added to the `MonitorInfo` struct.
In the tests expected values are incorrectly initialized and cause improper results. | test | failing unit tests tests editorargsunittests monitortojson and editorargsunittests editorargstojson are failing due to changes in where new members width and height were added to the monitorinfo struct in the tests expected values are incorrectly initialized and cause improper results | 1 |
301,609 | 26,078,474,957 | IssuesEvent | 2022-12-24 23:51:28 | lkrg-org/lkrg | https://api.github.com/repos/lkrg-org/lkrg | closed | mkosi: error: unrecognized arguments: --with-unified-kernel-images=no --root-size=4G | testing | Today `mkosi-mainline` has failed with `mkosi: error: unrecognized arguments: --with-unified-kernel-images=no --root-size=4G`. I guess something changed in `mkosi` and we need to adapt. @vt-alt | 1.0 | mkosi: error: unrecognized arguments: --with-unified-kernel-images=no --root-size=4G - Today `mkosi-mainline` has failed with `mkosi: error: unrecognized arguments: --with-unified-kernel-images=no --root-size=4G`. I guess something changed in `mkosi` and we need to adapt. @vt-alt | test | mkosi error unrecognized arguments with unified kernel images no root size today mkosi mainline has failed with mkosi error unrecognized arguments with unified kernel images no root size i guess something changed in mkosi and we need to adapt vt alt | 1 |
226,409 | 18,016,870,882 | IssuesEvent | 2021-09-16 14:46:32 | modin-project/modin | https://api.github.com/repos/modin-project/modin | closed | Use verbose mode for IO tests in order to see on which test the hang occurs | Testing :chart_with_upwards_trend: | Example CI logs:
```shell
modin\pandas\test\test_io.py ........................................... [ 2%]
........................................................................ [ 5%]
.............................................ssssssssssssssssssss.ss.ss. [ 9%]
ss.ss.ss.ss.ss.ss.ss.ss.ss.ssssssssssssssssssss.ss.ss.ss.ss.ss.ss.ss.ss. [ 12%]
ss.ss.ss.ssssssssssssssssssss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ss.sssssssss [ 16%]
sssssssssss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ssssssssssssssssssss.ss.ss. [ 19%]
ss.ss.ss.ss.ss.ss.ss.ss.ss.ssssssssssssssssssss.ss.ss.ss.ss.ss.ss.ss.ss. [ 23%]
ss.ss.ss.ssssssssssssssssssss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ss.sssssssss [ 26%]
sssssssssss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ss............................ [ 30%]
.xx.xx.xx.xx.xx....xx.xx.xx.xx.xx....xx.xx.xx.xx.xx....xx.xx.xx.xx.xx... [ 33%]
..x..x..x..x..x.....x..x..x..x..x....xx.xx.xx.xx.xx....xx.xx.xx.xx.xx... [ 37%]
.xx.xx.xx.xx.xx....xx.xx.xx.xx.xx.....x..x..x..x..x.....x..x..x..x..x... [ 40%]
.xx.xx.xx.xx.xx....xx.xx.xx.xx.xx....xx.xx.xx.xx.xx....xx.xx.xx.xx.xx... [ 44%]
..x..x..x..x..x.....x..x..x..x..x.xxxxxxxx.xxxxxxxx.xxxxxxxx.xxxxxxxx..x [ 47%]
x........................(pid=3308) Tokenization took: 0.00 ms
(pid=3308) Type conversion took: 0.00 ms
(pid=3308) Parser memory cleanup took: 0.00 ms
(pid=3308) Tokenization took: 0.00 ms
(pid=3308) Type conversion took: 0.00 ms
(pid=3308) Parser memory cleanup took: 0.00 ms
(pid=4692) Tokenization took: 0.00 ms
(pid=4692) Type conversion took: 0.00 ms
(pid=4692) Parser memory cleanup took: 0.00 ms
(pid=4692) Tokenization took: 0.00 ms
(pid=4692) Type conversion took: 0.00 ms
(pid=4692) Parser memory cleanup took: 0.00 ms
............................................... [ 51%]
........................................................................ [ 54%]
........................................................................ [ 58%]
........................................................................ [ 61%]
...............xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx [ 65%]
xxxxxxxxxxxxxxx........xxxxxxxx........xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx [ 68%]
xxxxxxxxxxxxxxx......................................................... [ 72%]
.......................x........x........xxxxxxxxxx..................... [ 75%]
........................................................................ [ 79%]
........................................................................ [ 82%]
........................................................................ [ 86%]
........................................................................ [ 89%]
..............................xxxxxxxxxxxxxxxxxxxxxxxx.................. [ 93%]
...........................................
Error: The action has timed out.
``` | 1.0 | Use verbose mode for IO tests in order to see on which test the hang occurs - Example CI logs:
```shell
modin\pandas\test\test_io.py ........................................... [ 2%]
........................................................................ [ 5%]
.............................................ssssssssssssssssssss.ss.ss. [ 9%]
ss.ss.ss.ss.ss.ss.ss.ss.ss.ssssssssssssssssssss.ss.ss.ss.ss.ss.ss.ss.ss. [ 12%]
ss.ss.ss.ssssssssssssssssssss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ss.sssssssss [ 16%]
sssssssssss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ssssssssssssssssssss.ss.ss. [ 19%]
ss.ss.ss.ss.ss.ss.ss.ss.ss.ssssssssssssssssssss.ss.ss.ss.ss.ss.ss.ss.ss. [ 23%]
ss.ss.ss.ssssssssssssssssssss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ss.sssssssss [ 26%]
sssssssssss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ss.ss............................ [ 30%]
.xx.xx.xx.xx.xx....xx.xx.xx.xx.xx....xx.xx.xx.xx.xx....xx.xx.xx.xx.xx... [ 33%]
..x..x..x..x..x.....x..x..x..x..x....xx.xx.xx.xx.xx....xx.xx.xx.xx.xx... [ 37%]
.xx.xx.xx.xx.xx....xx.xx.xx.xx.xx.....x..x..x..x..x.....x..x..x..x..x... [ 40%]
.xx.xx.xx.xx.xx....xx.xx.xx.xx.xx....xx.xx.xx.xx.xx....xx.xx.xx.xx.xx... [ 44%]
..x..x..x..x..x.....x..x..x..x..x.xxxxxxxx.xxxxxxxx.xxxxxxxx.xxxxxxxx..x [ 47%]
x........................(pid=3308) Tokenization took: 0.00 ms
(pid=3308) Type conversion took: 0.00 ms
(pid=3308) Parser memory cleanup took: 0.00 ms
(pid=3308) Tokenization took: 0.00 ms
(pid=3308) Type conversion took: 0.00 ms
(pid=3308) Parser memory cleanup took: 0.00 ms
(pid=4692) Tokenization took: 0.00 ms
(pid=4692) Type conversion took: 0.00 ms
(pid=4692) Parser memory cleanup took: 0.00 ms
(pid=4692) Tokenization took: 0.00 ms
(pid=4692) Type conversion took: 0.00 ms
(pid=4692) Parser memory cleanup took: 0.00 ms
............................................... [ 51%]
........................................................................ [ 54%]
........................................................................ [ 58%]
........................................................................ [ 61%]
...............xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx [ 65%]
xxxxxxxxxxxxxxx........xxxxxxxx........xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx [ 68%]
xxxxxxxxxxxxxxx......................................................... [ 72%]
.......................x........x........xxxxxxxxxx..................... [ 75%]
........................................................................ [ 79%]
........................................................................ [ 82%]
........................................................................ [ 86%]
........................................................................ [ 89%]
..............................xxxxxxxxxxxxxxxxxxxxxxxx.................. [ 93%]
...........................................
Error: The action has timed out.
``` | test | use verbose mode for io tests in order to see on which test the hang occurs example ci logs shell modin pandas test test io py ssssssssssssssssssss ss ss ss ss ss ss ss ss ss ss ss ssssssssssssssssssss ss ss ss ss ss ss ss ss ss ss ss ssssssssssssssssssss ss ss ss ss ss ss ss ss ss ss ss sssssssss sssssssssss ss ss ss ss ss ss ss ss ss ss ss ssssssssssssssssssss ss ss ss ss ss ss ss ss ss ss ss ssssssssssssssssssss ss ss ss ss ss ss ss ss ss ss ss ssssssssssssssssssss ss ss ss ss ss ss ss ss ss ss ss sssssssss sssssssssss ss ss ss ss ss ss ss ss ss ss ss xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx x x x x x x x x x x xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx x x x x x x x x x x xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx x x x x x x x x x x xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx x x pid tokenization took ms pid type conversion took ms pid parser memory cleanup took ms pid tokenization took ms pid type conversion took ms pid parser memory cleanup took ms pid tokenization took ms pid type conversion took ms pid parser memory cleanup took ms pid tokenization took ms pid type conversion took ms pid parser memory cleanup took ms xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxx xxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxx x x xxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxx error the action has timed out | 1 |
509,543 | 14,739,588,120 | IssuesEvent | 2021-01-07 07:31:03 | MikeVedsted/JoinMe | https://api.github.com/repos/MikeVedsted/JoinMe | opened | [FEAT] Allow users to edit comments on front end | Priority: Medium :zap: Status: Received :inbox_tray: Type: Enhancement :rocket: | **💡 I would really like to solve or include**
Clearly and concisely describe the problem you are trying to solve.
Back end is already ready to handle editing comments but we have not built any functionalities to allow users to do it yet.
**👶 How would a user describe this?**
Describe how users are affected by statements users might make or a user story.
I made a typo in my comment. Can I correct it somewhere?
**♻️ Additional context**
Describe any other reasons that might make this feature necessary.
user flow needs to be considered. Where, how and why it should be allowed, and if anything else should be displayed, such as displaying that the comment has been edited.
**🚀 I'm ready for take off**
Before submitting, please mark if you:
- [x] Checked that this feature doesn't already exists
- [x] Checked that a feature request doesn't already exists
- [x] Went through the user flow, and understand the impact
- [x] Made sure the request shows why it is important to users but doesn't exaggerate the value
| 1.0 | [FEAT] Allow users to edit comments on front end - **💡 I would really like to solve or include**
Clearly and concisely describe the problem you are trying to solve.
Back end is already ready to handle editing comments but we have not built any functionalities to allow users to do it yet.
**👶 How would a user describe this?**
Describe how users are affected by statements users might make or a user story.
I made a typo in my comment. Can I correct it somewhere?
**♻️ Additional context**
Describe any other reasons that might make this feature necessary.
user flow needs to be considered. Where, how and why it should be allowed, and if anything else should be displayed, such as displaying that the comment has been edited.
**🚀 I'm ready for take off**
Before submitting, please mark if you:
- [x] Checked that this feature doesn't already exists
- [x] Checked that a feature request doesn't already exists
- [x] Went through the user flow, and understand the impact
- [x] Made sure the request shows why it is important to users but doesn't exaggerate the value
| non_test | allow users to edit comments on front end 💡 i would really like to solve or include clearly and concisely describe the problem you are trying to solve back end is already ready to handle editing comments but we have not built any functionalities to allow users to do it yet 👶 how would a user describe this describe how users are affected by statements users might make or a user story i made a typo in my comment can i correct it somewhere ♻️ additional context describe any other reasons that might make this feature necessary user flow needs to be considered where how and why it should be allowed and if anything else should be displayed such as displaying that the comment has been edited 🚀 i m ready for take off before submitting please mark if you checked that this feature doesn t already exists checked that a feature request doesn t already exists went through the user flow and understand the impact made sure the request shows why it is important to users but doesn t exaggerate the value | 0 |
46,247 | 24,440,239,589 | IssuesEvent | 2022-10-06 14:09:35 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | opened | Improve pattern rendering sequence | [Type] Enhancement [Type] Performance [Feature] Patterns | At the moment, patterns seem to go through a few rendering adjustments before settling into their final form. I'm spotting at least three but there could be more.
It'd be great to solve this as it makes the pattern inserter and the pattern experience feel more fragile.
### Render 1
<img width="299" alt="image" src="https://user-images.githubusercontent.com/548849/194334629-19d0151c-d370-493d-863d-13de263777e6.png">
### Render 2
<img width="300" alt="image" src="https://user-images.githubusercontent.com/548849/194334708-a7ed3ed0-343c-48e6-89df-400e7188a4fa.png">
### Render 3
<img width="300" alt="image" src="https://user-images.githubusercontent.com/548849/194334785-18b096ac-56c2-4026-b379-92a6cdde2ea1.png">
---
cc @youknowriad @tyxla @jsnajdr as it also relates to https://github.com/WordPress/gutenberg/pull/42525 | True | Improve pattern rendering sequence - At the moment, patterns seem to go through a few rendering adjustments before settling into their final form. I'm spotting at least three but there could be more.
It'd be great to solve this as it makes the pattern inserter and the pattern experience feel more fragile.
### Render 1
<img width="299" alt="image" src="https://user-images.githubusercontent.com/548849/194334629-19d0151c-d370-493d-863d-13de263777e6.png">
### Render 2
<img width="300" alt="image" src="https://user-images.githubusercontent.com/548849/194334708-a7ed3ed0-343c-48e6-89df-400e7188a4fa.png">
### Render 3
<img width="300" alt="image" src="https://user-images.githubusercontent.com/548849/194334785-18b096ac-56c2-4026-b379-92a6cdde2ea1.png">
---
cc @youknowriad @tyxla @jsnajdr as it also relates to https://github.com/WordPress/gutenberg/pull/42525 | non_test | improve pattern rendering sequence at the moment patterns seem to go through a few rendering adjustments before settling into their final form i m spotting at least three but there could be more it d be great to solve this as it makes the pattern inserter and the pattern experience feel more fragile render img width alt image src render img width alt image src render img width alt image src cc youknowriad tyxla jsnajdr as it also relates to | 0 |
289,183 | 24,966,152,408 | IssuesEvent | 2022-11-01 19:34:12 | microsoft/react-native-windows | https://api.github.com/repos/microsoft/react-native-windows | closed | Build error after updating Visual Studio 2022 | bug Needs: Author Feedback Needs: Verify on Latest Version Area: Developer Experience Scenario: Visual Studio | ### Problem Description
VS2022 17.1 causes build error. Reverting to 17.0.6 resolves the build but worth noting I can't see any previous builds on VS Community, only Enterprise and Professional.
### Steps To Reproduce
Create a fresh project and build.
### Expected Results
Build should succeed.
### CLI version
6.4.0
### Environment
```markdown
info Fetching system and libraries information...
System:
OS: Windows 10 10.0.22000
CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Memory: 18.93 GB / 31.73 GB
Binaries:
Node: 16.13.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.17 - ~\AppData\Roaming\npm\yarn.CMD
npm: 8.1.3 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK:
AllowDevelopmentWithoutDevLicense: Enabled
AllowAllTrustedApps: Enabled
Versions: 10.0.18362.0, 10.0.19041.0, 10.0.22000.0
IDEs:
Android Studio: Not Found
Visual Studio: 17.1.32228.430 (Visual Studio Community 2022)
Languages:
Java: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.67.0 => 0.67.0
react-native-windows: 0.67.3 => 0.67.3
npmGlobalPackages:
*react-native*: Not Found
```
### Target Platform Version
_No response_
### Target Device(s)
Desktop
### Visual Studio Version
Visual Studio 2022
### Build Configuration
Debug
### Snack, code example, screenshot, or link to a repository
_No response_ | 1.0 | Build error after updating Visual Studio 2022 - ### Problem Description
VS2022 17.1 causes build error. Reverting to 17.0.6 resolves the build but worth noting I can't see any previous builds on VS Community, only Enterprise and Professional.
### Steps To Reproduce
Create a fresh project and build.
### Expected Results
Build should succeed.
### CLI version
6.4.0
### Environment
```markdown
info Fetching system and libraries information...
System:
OS: Windows 10 10.0.22000
CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Memory: 18.93 GB / 31.73 GB
Binaries:
Node: 16.13.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.17 - ~\AppData\Roaming\npm\yarn.CMD
npm: 8.1.3 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK:
AllowDevelopmentWithoutDevLicense: Enabled
AllowAllTrustedApps: Enabled
Versions: 10.0.18362.0, 10.0.19041.0, 10.0.22000.0
IDEs:
Android Studio: Not Found
Visual Studio: 17.1.32228.430 (Visual Studio Community 2022)
Languages:
Java: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.67.0 => 0.67.0
react-native-windows: 0.67.3 => 0.67.3
npmGlobalPackages:
*react-native*: Not Found
```
### Target Platform Version
_No response_
### Target Device(s)
Desktop
### Visual Studio Version
Visual Studio 2022
### Build Configuration
Debug
### Snack, code example, screenshot, or link to a repository
_No response_ | test | build error after updating visual studio problem description causes build error reverting to resolves the build but worth noting i can t see any previous builds on vs community only enterprise and professional steps to reproduce create a fresh project and build expected results build should succeed cli version environment markdown info fetching system and libraries information system os windows cpu intel r core tm cpu memory gb gb binaries node c program files nodejs node exe yarn appdata roaming npm yarn cmd npm c program files nodejs npm cmd watchman not found sdks android sdk not found windows sdk allowdevelopmentwithoutdevlicense enabled allowalltrustedapps enabled versions ides android studio not found visual studio visual studio community languages java not found npmpackages react native community cli not found react react native react native windows npmglobalpackages react native not found target platform version no response target device s desktop visual studio version visual studio build configuration debug snack code example screenshot or link to a repository no response | 1 |
38,113 | 2,839,064,368 | IssuesEvent | 2015-05-27 11:37:56 | heron-mc/heron-mc | https://api.github.com/repos/heron-mc/heron-mc | closed | Italian translation | auto-migrated Component-UI Milestone-Release1.0.6 OpSys-All Priority-Medium Project-None Type-Enhancement Usability | ```
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Please provide any additional information below.
```
Original issue reported on code.google.com by `roberto....@gmail.com` on 12 Jan 2015 at 5:00 | 1.0 | Italian translation - ```
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Please provide any additional information below.
```
Original issue reported on code.google.com by `roberto....@gmail.com` on 12 Jan 2015 at 5:00 | non_test | italian translation what steps will reproduce the problem what is the expected output what do you see instead what version of the product are you using on what operating system please provide any additional information below original issue reported on code google com by roberto gmail com on jan at | 0 |
16,301 | 11,906,097,827 | IssuesEvent | 2020-03-30 19:45:24 | Opentrons/opentrons | https://api.github.com/repos/Opentrons/opentrons | opened | CI: Run Cypress E2E tests in CI build | infrastructure | # Overview
We're got a bunch of E2E tests now. But we never run them! We should run Cypress tests in Travis. | 1.0 | CI: Run Cypress E2E tests in CI build - # Overview
We're got a bunch of E2E tests now. But we never run them! We should run Cypress tests in Travis. | non_test | ci run cypress tests in ci build overview we re got a bunch of tests now but we never run them we should run cypress tests in travis | 0 |
272,477 | 29,795,030,258 | IssuesEvent | 2023-06-16 01:05:29 | billmcchesney1/pacbot | https://api.github.com/repos/billmcchesney1/pacbot | closed | CVE-2022-23491 (High) detected in certifi-2020.12.5-py2.py3-none-any.whl - autoclosed | Mend: dependency security vulnerability | ## CVE-2022-23491 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>certifi-2020.12.5-py2.py3-none-any.whl</b></p></summary>
<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/5e/a0/5f06e1e1d463903cf0c0eebeb751791119ed7a4b3737fdc9a77f1cdfb51f/certifi-2020.12.5-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/5e/a0/5f06e1e1d463903cf0c0eebeb751791119ed7a4b3737fdc9a77f1cdfb51f/certifi-2020.12.5-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /installer/requirements.txt</p>
<p>Path to vulnerable library: /installer/requirements.txt</p>
<p>
Dependency Hierarchy:
- docker_py-1.10.6-py2.py3-none-any.whl (Root Library)
- requests-2.25.1-py2.py3-none-any.whl
- :x: **certifi-2020.12.5-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/billmcchesney1/pacbot/commit/acf9a0620c1a37cee4f2896d71e1c3731c5c7b06">acf9a0620c1a37cee4f2896d71e1c3731c5c7b06</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi 2022.12.07 removes root certificates from "TrustCor" from the root store. These are in the process of being removed from Mozilla's trust store. TrustCor's root certificates are being removed pursuant to an investigation prompted by media reporting that TrustCor's ownership also operated a business that produced spyware. Conclusions of Mozilla's investigation can be found in the linked google group discussion.
<p>Publish Date: 2022-12-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23491>CVE-2022-23491</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-23491">https://www.cve.org/CVERecord?id=CVE-2022-23491</a></p>
<p>Release Date: 2022-12-07</p>
<p>Fix Resolution: certifi - 2022.12.07</p>
</p>
</details>
<p></p>
| True | CVE-2022-23491 (High) detected in certifi-2020.12.5-py2.py3-none-any.whl - autoclosed - ## CVE-2022-23491 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>certifi-2020.12.5-py2.py3-none-any.whl</b></p></summary>
<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/5e/a0/5f06e1e1d463903cf0c0eebeb751791119ed7a4b3737fdc9a77f1cdfb51f/certifi-2020.12.5-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/5e/a0/5f06e1e1d463903cf0c0eebeb751791119ed7a4b3737fdc9a77f1cdfb51f/certifi-2020.12.5-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /installer/requirements.txt</p>
<p>Path to vulnerable library: /installer/requirements.txt</p>
<p>
Dependency Hierarchy:
- docker_py-1.10.6-py2.py3-none-any.whl (Root Library)
- requests-2.25.1-py2.py3-none-any.whl
- :x: **certifi-2020.12.5-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/billmcchesney1/pacbot/commit/acf9a0620c1a37cee4f2896d71e1c3731c5c7b06">acf9a0620c1a37cee4f2896d71e1c3731c5c7b06</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi 2022.12.07 removes root certificates from "TrustCor" from the root store. These are in the process of being removed from Mozilla's trust store. TrustCor's root certificates are being removed pursuant to an investigation prompted by media reporting that TrustCor's ownership also operated a business that produced spyware. Conclusions of Mozilla's investigation can be found in the linked google group discussion.
<p>Publish Date: 2022-12-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23491>CVE-2022-23491</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-23491">https://www.cve.org/CVERecord?id=CVE-2022-23491</a></p>
<p>Release Date: 2022-12-07</p>
<p>Fix Resolution: certifi - 2022.12.07</p>
</p>
</details>
<p></p>
| non_test | cve high detected in certifi none any whl autoclosed cve high severity vulnerability vulnerable library certifi none any whl python package for providing mozilla s ca bundle library home page a href path to dependency file installer requirements txt path to vulnerable library installer requirements txt dependency hierarchy docker py none any whl root library requests none any whl x certifi none any whl vulnerable library found in head commit a href found in base branch master vulnerability details certifi is a curated collection of root certificates for validating the trustworthiness of ssl certificates while verifying the identity of tls hosts certifi removes root certificates from trustcor from the root store these are in the process of being removed from mozilla s trust store trustcor s root certificates are being removed pursuant to an investigation prompted by media reporting that trustcor s ownership also operated a business that produced spyware conclusions of mozilla s investigation can be found in the linked google group discussion publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution certifi | 0 |
243,788 | 20,573,891,490 | IssuesEvent | 2022-03-04 00:58:18 | backend-br/vagas | https://api.github.com/repos/backend-br/vagas | closed | [Remoto] Back-end Developer Node Js PL | SR @MaxMilhas | CLT Pleno PHP JavaScript NodeJS Express Java Remoto MySQL MongoDB TypeScript NoSQL Redis PostgreSQL Testes Unitários Scrum Git Rest Docker Stale | ## Nossa empresa
A MaxMilhas acredita que todo mundo merece voar. Possibilitar que cada vez mais pessoas possam viajar e viver histórias incríveis é o propósito que nos move.
Revolucionamos o setor de turismo e tecnologia do Brasil, nos tornamos um dos maiores cases de bootstrapping do país e estamos entre as 10 melhores empresas para se trabalhar em Minas Gerais, de acordo com o Great Place To Work, GPTW.
Hoje, já somos mais de 350 especialistas, pessoas incríveis que trabalham por propósito e com paixão.
Ao decorrer desses sete anos de trajetória, construímos uma cultura forte, plural, inclusiva e humana, que direciona as nossas tomadas de decisão na busca por resultados que nos faça crescer como empresa e como profissionais.
Juntos, sabemos que podemos voar cada vez mais alto.
## Descrição da vaga
Participar da implementação e manutenção da plataforma de busca de voos;
Atuar com desenvolvimento de novos projetos, camada de integração e serviços;
Realizar o desenvolvimento da documentação técnica dos projetos.
## Local
Remoto
## Requisitos
**Obrigatórios:**
Experiência em design e arquitetura de software;
Experiência com Node.js em produção (Javascript e TypeScript);
Criação de API´s e microserviços (REST / Express);
Experiência com testes unitários (mocha, chai, sinon)
Conhecimento de Banco de Dados NOSQL (MONGODB, REDIS);
Experiência em Conteinerização (Docker);
Métodos ágeis (Scrum);
Experiência com controle de versão GIT;
**Desejáveis:**
Conhecimentos em sistemas de alta disponibilidade e escalabilidade;
Conhecimento em framework SPA (React);
Conhecimento em banco de dados relacional (MySQL, Postgresql, etc);
Conhecimento em outras linguagens de programação (Java, .NET, PHP, etc).
## Benefícios
Plano de saúde/Odonto Sulamerica
Seguro de vida
VR de R$ 30,00/dia
Auxílio creche
Gympass.
Convênio com o SESC.
20% da remuneração mensal voltada para cursos, palestras e afins de forma anual.
Condição exclusiva para comprar viagens aqui no nosso site a preço de custo.
Benefício exclusivo “De Malas Prontas”: o colaborador terá R$ 500,00 para viagem durante as férias e ainda recebe o seu vale refeição ou alimentação para usar neste período.
Day Off no dia do aniversário.
Consultoria de bem-estar financeiro com a nossa parceira Leve.
Acesso a plataforma de Idiomas Rosetta, e você só paga 50% do valor.
Cuide da sua saúde mental com a plataforma Vittude que oferece Psicoterapia e arcamos com 40% do valor.
## Contratação
CLT a combinar
## Como se candidatar
Por favor envie um e-mail para raianny-cristina@hotmail.com com seu CV anexado - enviar no assunto: Vaga NodeJS
## Tempo médio de feedbacks
Costumamos enviar feedbacks em até 07 dias após cada processo.
E-mail para contato em caso de não haver resposta: raianny-cristina@hotmail.com
#### Regime
- CLT
#### Nível
- Pleno
- Sênior
| 1.0 | [Remoto] Back-end Developer Node Js PL | SR @MaxMilhas - ## Nossa empresa
A MaxMilhas acredita que todo mundo merece voar. Possibilitar que cada vez mais pessoas possam viajar e viver histórias incríveis é o propósito que nos move.
Revolucionamos o setor de turismo e tecnologia do Brasil, nos tornamos um dos maiores cases de bootstrapping do país e estamos entre as 10 melhores empresas para se trabalhar em Minas Gerais, de acordo com o Great Place To Work, GPTW.
Hoje, já somos mais de 350 especialistas, pessoas incríveis que trabalham por propósito e com paixão.
Ao decorrer desses sete anos de trajetória, construímos uma cultura forte, plural, inclusiva e humana, que direciona as nossas tomadas de decisão na busca por resultados que nos faça crescer como empresa e como profissionais.
Juntos, sabemos que podemos voar cada vez mais alto.
## Descrição da vaga
Participar da implementação e manutenção da plataforma de busca de voos;
Atuar com desenvolvimento de novos projetos, camada de integração e serviços;
Realizar o desenvolvimento da documentação técnica dos projetos.
## Local
Remoto
## Requisitos
**Obrigatórios:**
Experiência em design e arquitetura de software;
Experiência com Node.js em produção (Javascript e TypeScript);
Criação de API´s e microserviços (REST / Express);
Experiência com testes unitários (mocha, chai, sinon)
Conhecimento de Banco de Dados NOSQL (MONGODB, REDIS);
Experiência em Conteinerização (Docker);
Métodos ágeis (Scrum);
Experiência com controle de versão GIT;
**Desejáveis:**
Conhecimentos em sistemas de alta disponibilidade e escalabilidade;
Conhecimento em framework SPA (React);
Conhecimento em banco de dados relacional (MySQL, Postgresql, etc);
Conhecimento em outras linguagens de programação (Java, .NET, PHP, etc).
## Benefícios
Plano de saúde/Odonto Sulamerica
Seguro de vida
VR de R$ 30,00/dia
Auxílio creche
Gympass.
Convênio com o SESC.
20% da remuneração mensal voltada para cursos, palestras e afins de forma anual.
Condição exclusiva para comprar viagens aqui no nosso site a preço de custo.
Benefício exclusivo “De Malas Prontas”: o colaborador terá R$ 500,00 para viagem durante as férias e ainda recebe o seu vale refeição ou alimentação para usar neste período.
Day Off no dia do aniversário.
Consultoria de bem-estar financeiro com a nossa parceira Leve.
Acesso a plataforma de Idiomas Rosetta, e você só paga 50% do valor.
Cuide da sua saúde mental com a plataforma Vittude que oferece Psicoterapia e arcamos com 40% do valor.
## Contratação
CLT a combinar
## Como se candidatar
Por favor envie um e-mail para raianny-cristina@hotmail.com com seu CV anexado - enviar no assunto: Vaga NodeJS
## Tempo médio de feedbacks
Costumamos enviar feedbacks em até 07 dias após cada processo.
E-mail para contato em caso de não haver resposta: raianny-cristina@hotmail.com
#### Regime
- CLT
#### Nível
- Pleno
- Sênior
| test | back end developer node js pl sr maxmilhas nossa empresa a maxmilhas acredita que todo mundo merece voar possibilitar que cada vez mais pessoas possam viajar e viver histórias incríveis é o propósito que nos move revolucionamos o setor de turismo e tecnologia do brasil nos tornamos um dos maiores cases de bootstrapping do país e estamos entre as melhores empresas para se trabalhar em minas gerais de acordo com o great place to work gptw hoje já somos mais de especialistas pessoas incríveis que trabalham por propósito e com paixão ao decorrer desses sete anos de trajetória construímos uma cultura forte plural inclusiva e humana que direciona as nossas tomadas de decisão na busca por resultados que nos faça crescer como empresa e como profissionais juntos sabemos que podemos voar cada vez mais alto descrição da vaga participar da implementação e manutenção da plataforma de busca de voos atuar com desenvolvimento de novos projetos camada de integração e serviços realizar o desenvolvimento da documentação técnica dos projetos local remoto requisitos obrigatórios experiência em design e arquitetura de software experiência com node js em produção javascript e typescript criação de api´s e microserviços rest express experiência com testes unitários mocha chai sinon conhecimento de banco de dados nosql mongodb redis experiência em conteinerização docker métodos ágeis scrum experiência com controle de versão git desejáveis conhecimentos em sistemas de alta disponibilidade e escalabilidade conhecimento em framework spa react conhecimento em banco de dados relacional mysql postgresql etc conhecimento em outras linguagens de programação java net php etc benefícios plano de saúde odonto sulamerica seguro de vida vr de r dia auxílio creche gympass convênio com o sesc da remuneração mensal voltada para cursos palestras e afins de forma anual condição exclusiva para comprar viagens aqui no nosso site a preço de custo benefício exclusivo “de malas prontas” o colaborador terá r para viagem durante as férias e ainda recebe o seu vale refeição ou alimentação para usar neste período day off no dia do aniversário consultoria de bem estar financeiro com a nossa parceira leve acesso a plataforma de idiomas rosetta e você só paga do valor cuide da sua saúde mental com a plataforma vittude que oferece psicoterapia e arcamos com do valor contratação clt a combinar como se candidatar por favor envie um e mail para raianny cristina hotmail com com seu cv anexado enviar no assunto vaga nodejs tempo médio de feedbacks costumamos enviar feedbacks em até dias após cada processo e mail para contato em caso de não haver resposta raianny cristina hotmail com regime clt nível pleno sênior | 1 |
275,468 | 30,247,795,020 | IssuesEvent | 2023-07-06 17:53:38 | BCDevOps/developer-experience | https://api.github.com/repos/BCDevOps/developer-experience | opened | STRA for Instruqt for OCP Training | *team/ security* | **Describe the issue**
There is a need to complete a security assessment for our use of the Instruqt tool for OCP training.
**Additional context**
https://instruqt.com/
**How does this benefit the users of our platform?**
**Definition of done**
- [ ] Information gathering
- [ ] Proposed use documented
- [ ] Identify risks
- [ ] Review Cloud Security Schedule items
- [ ] Create SoAR | True | STRA for Instruqt for OCP Training - **Describe the issue**
There is a need to complete a security assessment for our use of the Instruqt tool for OCP training.
**Additional context**
https://instruqt.com/
**How does this benefit the users of our platform?**
**Definition of done**
- [ ] Information gathering
- [ ] Proposed use documented
- [ ] Identify risks
- [ ] Review Cloud Security Schedule items
- [ ] Create SoAR | non_test | stra for instruqt for ocp training describe the issue there is a need to complete a security assessment for our use of the instruqt tool for ocp training additional context how does this benefit the users of our platform definition of done information gathering proposed use documented identify risks review cloud security schedule items create soar | 0 |
333,506 | 29,669,769,277 | IssuesEvent | 2023-06-11 08:59:12 | python/cpython | https://api.github.com/repos/python/cpython | closed | test_sqlite3.test_userfunctions redefines test_func_return_too_large_int() method | type-bug tests topic-sqlite3 | Lib/test/test_sqlite3/test_userfunctions.py defines to methods called test_func_return_too_large_int() in the same class, so the first one is never called.
cc @erlend-aasland
<!-- gh-linked-prs -->
### Linked PRs
* gh-105558
* gh-105561
* gh-105562
<!-- /gh-linked-prs -->
| 1.0 | test_sqlite3.test_userfunctions redefines test_func_return_too_large_int() method - Lib/test/test_sqlite3/test_userfunctions.py defines to methods called test_func_return_too_large_int() in the same class, so the first one is never called.
cc @erlend-aasland
<!-- gh-linked-prs -->
### Linked PRs
* gh-105558
* gh-105561
* gh-105562
<!-- /gh-linked-prs -->
| test | test test userfunctions redefines test func return too large int method lib test test test userfunctions py defines to methods called test func return too large int in the same class so the first one is never called cc erlend aasland linked prs gh gh gh | 1 |
54,114 | 6,366,076,152 | IssuesEvent | 2017-08-01 00:01:53 | Turfjs/turf | https://api.github.com/repos/Turfjs/turf | opened | Improve linting tests | docs testing | # Improve linting tests
Based on https://github.com/Turfjs/turf/pull/873#issuecomment-318890019 & https://github.com/Turfjs/turf/pull/873#issuecomment-319229572.
## To-Do
- [ ] add `@name` linting to tests
- [ ] investigate how to tackle linting new modules
| 1.0 | Improve linting tests - # Improve linting tests
Based on https://github.com/Turfjs/turf/pull/873#issuecomment-318890019 & https://github.com/Turfjs/turf/pull/873#issuecomment-319229572.
## To-Do
- [ ] add `@name` linting to tests
- [ ] investigate how to tackle linting new modules
| test | improve linting tests improve linting tests based on to do add name linting to tests investigate how to tackle linting new modules | 1 |
208,158 | 15,878,080,501 | IssuesEvent | 2021-04-09 10:29:56 | momentum-mod/game | https://api.github.com/repos/momentum-mod/game | closed | +strafe display does not show on mom_hud_showkeypresses | Blocked: Needs testing & verification Priority: Medium Size: Trivial Type: Bug | **Describe the bug**
With `mom_hud_showkeypresses 1` the center dot that is meant to represent `+strafe` being used does not show up any more. This worked before swapping to chaos.
**To Reproduce**
Steps to reproduce the behavior:
1. `mom_hud_showkeypresses 1`
2. `bind e +strafe`
3. Hold E and observe the lack of dot
**Expected behavior**
The dot should appear while +strafe is being used, like below (don't mind the twitch compression)
**Desktop/Branch (please complete the following information):**
- OS: Windows
- Branch: 0.8.8-rc
**Additional context**
Reported by Ark | 1.0 | +strafe display does not show on mom_hud_showkeypresses - **Describe the bug**
With `mom_hud_showkeypresses 1` the center dot that is meant to represent `+strafe` being used does not show up any more. This worked before swapping to chaos.
**To Reproduce**
Steps to reproduce the behavior:
1. `mom_hud_showkeypresses 1`
2. `bind e +strafe`
3. Hold E and observe the lack of dot
**Expected behavior**
The dot should appear while +strafe is being used, like below (don't mind the twitch compression)
**Desktop/Branch (please complete the following information):**
- OS: Windows
- Branch: 0.8.8-rc
**Additional context**
Reported by Ark | test | strafe display does not show on mom hud showkeypresses describe the bug with mom hud showkeypresses the center dot that is meant to represent strafe being used does not show up any more this worked before swapping to chaos to reproduce steps to reproduce the behavior mom hud showkeypresses bind e strafe hold e and observe the lack of dot expected behavior the dot should appear while strafe is being used like below don t mind the twitch compression desktop branch please complete the following information os windows branch rc additional context reported by ark | 1 |
76,678 | 14,663,788,461 | IssuesEvent | 2020-12-29 10:28:48 | Torkin1/pokemon_goose_game | https://api.github.com/repos/Torkin1/pokemon_goose_game | closed | Create a new View on the gameActivty | NewCode | The view has to contain
- [x] Gold (pokè Coins ) of the current player
- [x] Add Pokemons health bar
- [ ] pokemons name (possibly a little icon too)
- [x] other info that yout think are needed | 1.0 | Create a new View on the gameActivty - The view has to contain
- [x] Gold (pokè Coins ) of the current player
- [x] Add Pokemons health bar
- [ ] pokemons name (possibly a little icon too)
- [x] other info that yout think are needed | non_test | create a new view on the gameactivty the view has to contain gold pokè coins of the current player add pokemons health bar pokemons name possibly a little icon too other info that yout think are needed | 0 |
206,508 | 16,044,455,601 | IssuesEvent | 2021-04-22 12:05:07 | bitpal/bitpal | https://api.github.com/repos/bitpal/bitpal | opened | Need to add inline documentation | documentation | Should have:
- [ ] Each module should have a `@moduledoc` tag
- [ ] Public functions should preferably have a `@doc` tag
We should also activate the `ModuleDoc` chech in credo when done. | 1.0 | Need to add inline documentation - Should have:
- [ ] Each module should have a `@moduledoc` tag
- [ ] Public functions should preferably have a `@doc` tag
We should also activate the `ModuleDoc` chech in credo when done. | non_test | need to add inline documentation should have each module should have a moduledoc tag public functions should preferably have a doc tag we should also activate the moduledoc chech in credo when done | 0 |
4,357 | 2,610,092,317 | IssuesEvent | 2015-02-26 18:27:52 | chrsmith/dsdsdaadf | https://api.github.com/repos/chrsmith/dsdsdaadf | opened | 深圳封闭性粉刺怎么祛除 | auto-migrated Priority-Medium Type-Defect | ```
深圳封闭性粉刺怎么祛除【深圳韩方科颜全国热线400-869-1818��
�24小时QQ4008691818】深圳韩方科颜专业祛痘连锁机构，机构以��
�国秘方——韩方科颜这一国妆准字号治疗型权威，祛痘佳品�
��韩方科颜专业祛痘连锁机构，采用韩国秘方配合专业“不反
弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开创国��
�专业治疗粉刺、痤疮签约包治先河，成功消除了许多顾客脸�
��的痘痘。
```
-----
Original issue reported on code.google.com by `szft...@163.com` on 14 May 2014 at 7:55 | 1.0 | 深圳封闭性粉刺怎么祛除 - ```
深圳封闭性粉刺怎么祛除【深圳韩方科颜全国热线400-869-1818��
�24小时QQ4008691818】深圳韩方科颜专业祛痘连锁机构，机构以��
�国秘方——韩方科颜这一国妆准字号治疗型权威，祛痘佳品�
��韩方科颜专业祛痘连锁机构，采用韩国秘方配合专业“不反
弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开创国��
�专业治疗粉刺、痤疮签约包治先河，成功消除了许多顾客脸�
��的痘痘。
```
-----
Original issue reported on code.google.com by `szft...@163.com` on 14 May 2014 at 7:55 | non_test | 深圳封闭性粉刺怎么祛除 深圳封闭性粉刺怎么祛除【 �� � 】深圳韩方科颜专业祛痘连锁机构，机构以�� �国秘方——韩方科颜这一国妆准字号治疗型权威，祛痘佳品� ��韩方科颜专业祛痘连锁机构，采用韩国秘方配合专业“不反 弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开创国�� �专业治疗粉刺、痤疮签约包治先河，成功消除了许多顾客脸� ��的痘痘。 original issue reported on code google com by szft com on may at | 0 |
113,839 | 14,495,005,027 | IssuesEvent | 2020-12-11 10:32:33 | nextcloud/news | https://api.github.com/repos/nextcloud/news | closed | [Feature request] Allow-/denypattern filter for articles | design enhancement | Read and tick the following checkbox after you have created the issue or place an x inside the brackets ;)
* [x] I have read the [CONTRIBUTING.md](https://github.com/nextcloud/news/blob/master/CONTRIBUTING.md) and followed the provided tips
**Is your feature request related to a problem? Please describe.**
Some feeds feature articles which are not interesting to the subscriber. For instance: I subscribe to a tech news feed which features articles on Android and iOS. However, since I don't have an iPhone, I'm not interested in the latter and would like to ignore such articles.
**Describe the solution you'd like**
A cascade of two regexp patterns might help: If the article subject matches the denypattern, it is ignored *unless* it also matches the allowpattern. Example:
1. Denypattern: `/iOS|iPhone/i`
2. Allowpattern: `/Android/i`
Subject | Denypattern | Allowpattern | Result
---|---|---|---
New Apps in Oct | no match | *skipped* | allow
New Apps for Android | no match | *skipped* | allow
New Apps for iPhone | match | no match | deny
New Apps for iPhone and Android | match | match | allow
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/94670390-feature-request-allow-denypattern-filter-for-articles?utm_campaign=plugin&utm_content=tracker%2F38605310&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F38605310&utm_medium=issues&utm_source=github).
</bountysource-plugin> | 1.0 | [Feature request] Allow-/denypattern filter for articles - Read and tick the following checkbox after you have created the issue or place an x inside the brackets ;)
* [x] I have read the [CONTRIBUTING.md](https://github.com/nextcloud/news/blob/master/CONTRIBUTING.md) and followed the provided tips
**Is your feature request related to a problem? Please describe.**
Some feeds feature articles which are not interesting to the subscriber. For instance: I subscribe to a tech news feed which features articles on Android and iOS. However, since I don't have an iPhone, I'm not interested in the latter and would like to ignore such articles.
**Describe the solution you'd like**
A cascade of two regexp patterns might help: If the article subject matches the denypattern, it is ignored *unless* it also matches the allowpattern. Example:
1. Denypattern: `/iOS|iPhone/i`
2. Allowpattern: `/Android/i`
Subject | Denypattern | Allowpattern | Result
---|---|---|---
New Apps in Oct | no match | *skipped* | allow
New Apps for Android | no match | *skipped* | allow
New Apps for iPhone | match | no match | deny
New Apps for iPhone and Android | match | match | allow
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/94670390-feature-request-allow-denypattern-filter-for-articles?utm_campaign=plugin&utm_content=tracker%2F38605310&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F38605310&utm_medium=issues&utm_source=github).
</bountysource-plugin> | non_test | allow denypattern filter for articles read and tick the following checkbox after you have created the issue or place an x inside the brackets i have read the and followed the provided tips is your feature request related to a problem please describe some feeds feature articles which are not interesting to the subscriber for instance i subscribe to a tech news feed which features articles on android and ios however since i don t have an iphone i m not interested in the latter and would like to ignore such articles describe the solution you d like a cascade of two regexp patterns might help if the article subject matches the denypattern it is ignored unless it also matches the allowpattern example denypattern ios iphone i allowpattern android i subject denypattern allowpattern result new apps in oct no match skipped allow new apps for android no match skipped allow new apps for iphone match no match deny new apps for iphone and android match match allow want to back this issue we accept bounties via | 0 |
652,255 | 21,526,859,344 | IssuesEvent | 2022-04-28 19:23:21 | fnnezami/Westdrive-LoopAR | https://api.github.com/repos/fnnezami/Westdrive-LoopAR | closed | Dancing Trees and Fog Bending | low priority visuals | Right now, we encountered a lot of dancing trees in all scenes. This means, that the billborads are dancing on the z axis.
We know, that the stolen code for the shader might be a bit problematic, but there has to be a way to lock these on the x and z axis. | 1.0 | Dancing Trees and Fog Bending - Right now, we encountered a lot of dancing trees in all scenes. This means, that the billborads are dancing on the z axis.
We know, that the stolen code for the shader might be a bit problematic, but there has to be a way to lock these on the x and z axis. | non_test | dancing trees and fog bending right now we encountered a lot of dancing trees in all scenes this means that the billborads are dancing on the z axis we know that the stolen code for the shader might be a bit problematic but there has to be a way to lock these on the x and z axis | 0 |
106,018 | 9,106,296,997 | IssuesEvent | 2019-02-20 23:20:40 | rancher/rancher | https://api.github.com/repos/rancher/rancher | closed | GKE - cannot provision a GKE cluster with custom access scope | area/gke area/ui kind/bug-qa status/ready-for-review status/resolved status/to-test team/cn version/2.0 | <!--
Please search for existing issues first, then read https://rancher.com/docs/rancher/v2.x/en/contributing/#bugs-issues-or-questions to see what we expect in an issue
For security issues, please email security@rancher.com instead of posting a public issue in GitHub. You may (but are not required to) use the GPG key located on Keybase.
-->
**What kind of request is this (question/bug/enhancement/feature request):**
Bug
**Steps to reproduce (least amount of steps as possible):**
- run Rancher master container
- add a GKE cluster
- choose `Set access for each API` for the `Security`, and leave the rest default value
<img width="1445" alt="screenshot" src="https://user-images.githubusercontent.com/6218999/53038013-e9fd1100-3438-11e9-980c-655198ba3923.png">
**Result:**
Rancer shows error message like this
```
This cluster is currently Provisioning; areas that interact directly with it will not be available until the API is ready.
Googleapi: Error 400: Cluster.node_config.oauth_scopes cannot have the same scope (https://www.googleapis.com/auth/none) repeated twice., badRequest
```
<img width="1423" alt="screenshot" src="https://user-images.githubusercontent.com/6218999/53038004-e1a4d600-3438-11e9-941a-8ccd2dc7fc48.png">
**Other details that may be helpful:**
**Environment information**
- Rancher version (`rancher/rancher`/`rancher/server` image tag or shown bottom left in the UI): master 2/19
- Installation option (single install/HA):
single install
<!--
If the reported issue is regarding a created cluster, please provide requested info below
-->
**Cluster information**
- Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
- Machine type (cloud/VM/metal) and specifications (CPU/memory):
- Kubernetes version (use `kubectl version`):
```
(paste the output here)
```
- Docker version (use `docker version`):
```
(paste the output here)
```
| 1.0 | GKE - cannot provision a GKE cluster with custom access scope - <!--
Please search for existing issues first, then read https://rancher.com/docs/rancher/v2.x/en/contributing/#bugs-issues-or-questions to see what we expect in an issue
For security issues, please email security@rancher.com instead of posting a public issue in GitHub. You may (but are not required to) use the GPG key located on Keybase.
-->
**What kind of request is this (question/bug/enhancement/feature request):**
Bug
**Steps to reproduce (least amount of steps as possible):**
- run Rancher master container
- add a GKE cluster
- choose `Set access for each API` for the `Security`, and leave the rest default value
<img width="1445" alt="screenshot" src="https://user-images.githubusercontent.com/6218999/53038013-e9fd1100-3438-11e9-980c-655198ba3923.png">
**Result:**
Rancer shows error message like this
```
This cluster is currently Provisioning; areas that interact directly with it will not be available until the API is ready.
Googleapi: Error 400: Cluster.node_config.oauth_scopes cannot have the same scope (https://www.googleapis.com/auth/none) repeated twice., badRequest
```
<img width="1423" alt="screenshot" src="https://user-images.githubusercontent.com/6218999/53038004-e1a4d600-3438-11e9-941a-8ccd2dc7fc48.png">
**Other details that may be helpful:**
**Environment information**
- Rancher version (`rancher/rancher`/`rancher/server` image tag or shown bottom left in the UI): master 2/19
- Installation option (single install/HA):
single install
<!--
If the reported issue is regarding a created cluster, please provide requested info below
-->
**Cluster information**
- Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
- Machine type (cloud/VM/metal) and specifications (CPU/memory):
- Kubernetes version (use `kubectl version`):
```
(paste the output here)
```
- Docker version (use `docker version`):
```
(paste the output here)
```
| test | gke cannot provision a gke cluster with custom access scope please search for existing issues first then read to see what we expect in an issue for security issues please email security rancher com instead of posting a public issue in github you may but are not required to use the gpg key located on keybase what kind of request is this question bug enhancement feature request bug steps to reproduce least amount of steps as possible run rancher master container add a gke cluster choose set access for each api for the security and leave the rest default value img width alt screenshot src result rancer shows error message like this this cluster is currently provisioning areas that interact directly with it will not be available until the api is ready googleapi error cluster node config oauth scopes cannot have the same scope repeated twice badrequest img width alt screenshot src other details that may be helpful environment information rancher version rancher rancher rancher server image tag or shown bottom left in the ui master installation option single install ha single install if the reported issue is regarding a created cluster please provide requested info below cluster information cluster type hosted infrastructure provider custom imported machine type cloud vm metal and specifications cpu memory kubernetes version use kubectl version paste the output here docker version use docker version paste the output here | 1 |
65,236 | 6,952,894,559 | IssuesEvent | 2017-12-06 19:03:41 | StuPro-TOSCAna/cloudformation-builder | https://api.github.com/repos/StuPro-TOSCAna/cloudformation-builder | opened | Deployment of lamp-template fails | bug test | Currently, the Deployment of the template created by the CloudFormationBuilderTest fails on AWS.
I'm currently investigating the causes of this and will fix those as soon as I have found all of them. | 1.0 | Deployment of lamp-template fails - Currently, the Deployment of the template created by the CloudFormationBuilderTest fails on AWS.
I'm currently investigating the causes of this and will fix those as soon as I have found all of them. | test | deployment of lamp template fails currently the deployment of the template created by the cloudformationbuildertest fails on aws i m currently investigating the causes of this and will fix those as soon as i have found all of them | 1 |
27,759 | 4,328,567,024 | IssuesEvent | 2016-07-26 14:25:57 | luyadev/luya | https://api.github.com/repos/luyadev/luya | closed | Added default order by for angular crud list | enhancement work_requires_testing | Ability to set defualt order in model `ngRestListOrder`. | 1.0 | Added default order by for angular crud list - Ability to set defualt order in model `ngRestListOrder`. | test | added default order by for angular crud list ability to set defualt order in model ngrestlistorder | 1 |
308,100 | 26,577,259,639 | IssuesEvent | 2023-01-22 00:38:56 | sourcegraph/sec-pr-audit-trail | https://api.github.com/repos/sourcegraph/sec-pr-audit-trail | opened | sourcegraph/deploy-sourcegraph#4221: "chore(deps): update index.docker.io/sourcegraph/jaeger-all-in-one:insiders docker digest to 652aeb4" | exception/review exception/test-plan sourcegraph/deploy-sourcegraph | https://github.com/sourcegraph/deploy-sourcegraph/pull/4221 "chore(deps): update index.docker.io/sourcegraph/jaeger-all-in-one:insiders docker digest to 652aeb4" **has no test plan** and **was not reviewed**.
Learn more about test plans in our [testing guidelines](https://docs.sourcegraph.com/dev/background-information/testing_principles#test-plans).
@sourcegraph-bot please comment in this issue with an explanation for this exception and close this issue. | 1.0 | sourcegraph/deploy-sourcegraph#4221: "chore(deps): update index.docker.io/sourcegraph/jaeger-all-in-one:insiders docker digest to 652aeb4" - https://github.com/sourcegraph/deploy-sourcegraph/pull/4221 "chore(deps): update index.docker.io/sourcegraph/jaeger-all-in-one:insiders docker digest to 652aeb4" **has no test plan** and **was not reviewed**.
Learn more about test plans in our [testing guidelines](https://docs.sourcegraph.com/dev/background-information/testing_principles#test-plans).
@sourcegraph-bot please comment in this issue with an explanation for this exception and close this issue. | test | sourcegraph deploy sourcegraph chore deps update index docker io sourcegraph jaeger all in one insiders docker digest to chore deps update index docker io sourcegraph jaeger all in one insiders docker digest to has no test plan and was not reviewed learn more about test plans in our sourcegraph bot please comment in this issue with an explanation for this exception and close this issue | 1 |
283,964 | 24,573,226,958 | IssuesEvent | 2022-10-13 10:14:41 | claritychallenge/clarity | https://api.github.com/repos/claritychallenge/clarity | opened | Unit tests for engine module | tests | Develop unit tests for the data module (see #80 for overview).
Specific modules within `engine` are...
- [ ] `engine/issues.py`
- [ ] `engone/system.py` | 1.0 | Unit tests for engine module - Develop unit tests for the data module (see #80 for overview).
Specific modules within `engine` are...
- [ ] `engine/issues.py`
- [ ] `engone/system.py` | test | unit tests for engine module develop unit tests for the data module see for overview specific modules within engine are engine issues py engone system py | 1 |
236,401 | 7,749,051,956 | IssuesEvent | 2018-05-30 10:09:44 | Gloirin/m2gTest | https://api.github.com/repos/Gloirin/m2gTest | closed | 0003236:
break quoting in html editor with ENTER | Felamimail bug high priority | **Reported by pschuele on 28 Oct 2010 12:48**
**Version:** Neele (2011-01-2)
break quoting in html editor with ENTER
**Additional information:** some DOM (selection/ranges/...) resources:
https://developer.mozilla.org/en/DOM
http://dylanschiemann.com/2002/12/07/dom-2-range-with-javascript/
http://help.dottoro.com/ljfjepre.php
| 1.0 | 0003236:
break quoting in html editor with ENTER - **Reported by pschuele on 28 Oct 2010 12:48**
**Version:** Neele (2011-01-2)
break quoting in html editor with ENTER
**Additional information:** some DOM (selection/ranges/...) resources:
https://developer.mozilla.org/en/DOM
http://dylanschiemann.com/2002/12/07/dom-2-range-with-javascript/
http://help.dottoro.com/ljfjepre.php
| non_test | break quoting in html editor with enter reported by pschuele on oct version neele break quoting in html editor with enter additional information some dom selection ranges resources | 0 |
116,437 | 9,852,591,364 | IssuesEvent | 2019-06-19 13:11:55 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | teamcity: failed test: TestEnqueueRange | C-test-failure O-robot | The following tests appear to have failed on master (testrace): TestEnqueueRange
You may want to check [for open issues](https://github.com/cockroachdb/cockroach/issues?q=is%3Aissue+is%3Aopen+TestEnqueueRange).
[#1344165](https://teamcity.cockroachdb.com/viewLog.html?buildId=1344165):
```
TestEnqueueRange
...y another peer
W190617 21:13:10.762679 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
W190617 21:13:11.792898 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
W190617 21:13:12.864986 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
W190617 21:13:13.971209 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
W190617 21:13:14.831349 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
I190617 21:13:15.797517 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (gc): node unavailable; try another peer
I190617 21:13:15.797801 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (merge): node unavailable; try another peer
I190617 21:13:15.797908 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (split): node unavailable; try another peer
I190617 21:13:15.797976 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (replicate): node unavailable; try another peer
I190617 21:13:15.798079 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (replicaGC): node unavailable; try another peer
I190617 21:13:15.798161 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (raftlog): node unavailable; try another peer
I190617 21:13:15.798240 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (raftsnapshot): node unavailable; try another peer
I190617 21:13:15.798313 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (consistencyChecker): node unavailable; try another peer
I190617 21:13:15.798394 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (timeSeriesMaintenance): node unavailable; try another peer
W190617 21:13:16.436352 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
W190617 21:13:17.460334 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
W190617 21:13:18.439469 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
W190617 21:13:19.323398 32789 server/node.go:787 [n2,summaries] error recording status summaries: node unavailable; try another peer
W190617 21:13:19.433590 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
W190617 21:13:19.690629 32769 ts/db.go:199 [n2,ts-poll] node unavailable; try another peer
W190617 21:13:20.038500 32952 server/node.go:787 [n3,summaries] error recording status summaries: node unavailable; try another peer
W190617 21:13:20.170325 33050 ts/db.go:199 [n3,ts-poll] node unavailable; try another peer
I190617 21:13:21.491027 32768 server/status/runtime.go:500 [n2] runtime stats: 1.3 GiB RSS, 265 goroutines, 138 MiB/90 MiB/270 MiB GO alloc/idle/total(stale), 28 MiB/68 MiB CGO alloc/total, 5.9 CGO/sec, 3.4/1.3 %(u/s)time, 0.0 %gc (0x), 243 KiB/243 KiB (r/w)net
I190617 21:13:21.491057 33049 server/status/runtime.go:500 [n3] runtime stats: 1.3 GiB RSS, 143 goroutines, 139 MiB/90 MiB/270 MiB GO alloc/idle/total(stale), 28 MiB/68 MiB CGO alloc/total, 0.6 CGO/sec, 2.6/1.4 %(u/s)time, 0.0 %gc (0x), 243 KiB/243 KiB (r/w)net
W190617 21:13:37.206100 33145 server/node.go:872 [n3] node=3: unable to log node_join event: log-event: node unavailable; try another peer
admin_test.go:1624: AdminChangeReplicas error: snapshot failed: (n2,s2):?: remote failed to apply snapshot: rpc error: code = Unavailable desc = transport is closing
```
Please assign, take a look and update the issue accordingly.
| 1.0 | teamcity: failed test: TestEnqueueRange - The following tests appear to have failed on master (testrace): TestEnqueueRange
You may want to check [for open issues](https://github.com/cockroachdb/cockroach/issues?q=is%3Aissue+is%3Aopen+TestEnqueueRange).
[#1344165](https://teamcity.cockroachdb.com/viewLog.html?buildId=1344165):
```
TestEnqueueRange
...y another peer
W190617 21:13:10.762679 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
W190617 21:13:11.792898 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
W190617 21:13:12.864986 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
W190617 21:13:13.971209 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
W190617 21:13:14.831349 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
I190617 21:13:15.797517 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (gc): node unavailable; try another peer
I190617 21:13:15.797801 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (merge): node unavailable; try another peer
I190617 21:13:15.797908 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (split): node unavailable; try another peer
I190617 21:13:15.797976 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (replicate): node unavailable; try another peer
I190617 21:13:15.798079 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (replicaGC): node unavailable; try another peer
I190617 21:13:15.798161 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (raftlog): node unavailable; try another peer
I190617 21:13:15.798240 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (raftsnapshot): node unavailable; try another peer
I190617 21:13:15.798313 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (consistencyChecker): node unavailable; try another peer
I190617 21:13:15.798394 32787 storage/queue.go:527 [n2,s2] rate limited in MaybeAdd (timeSeriesMaintenance): node unavailable; try another peer
W190617 21:13:16.436352 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
W190617 21:13:17.460334 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
W190617 21:13:18.439469 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
W190617 21:13:19.323398 32789 server/node.go:787 [n2,summaries] error recording status summaries: node unavailable; try another peer
W190617 21:13:19.433590 32755 storage/store.go:1532 [n2,s2,r1/?:/{Min-System/NodeL…}] could not gossip first range descriptor: node unavailable; try another peer
W190617 21:13:19.690629 32769 ts/db.go:199 [n2,ts-poll] node unavailable; try another peer
W190617 21:13:20.038500 32952 server/node.go:787 [n3,summaries] error recording status summaries: node unavailable; try another peer
W190617 21:13:20.170325 33050 ts/db.go:199 [n3,ts-poll] node unavailable; try another peer
I190617 21:13:21.491027 32768 server/status/runtime.go:500 [n2] runtime stats: 1.3 GiB RSS, 265 goroutines, 138 MiB/90 MiB/270 MiB GO alloc/idle/total(stale), 28 MiB/68 MiB CGO alloc/total, 5.9 CGO/sec, 3.4/1.3 %(u/s)time, 0.0 %gc (0x), 243 KiB/243 KiB (r/w)net
I190617 21:13:21.491057 33049 server/status/runtime.go:500 [n3] runtime stats: 1.3 GiB RSS, 143 goroutines, 139 MiB/90 MiB/270 MiB GO alloc/idle/total(stale), 28 MiB/68 MiB CGO alloc/total, 0.6 CGO/sec, 2.6/1.4 %(u/s)time, 0.0 %gc (0x), 243 KiB/243 KiB (r/w)net
W190617 21:13:37.206100 33145 server/node.go:872 [n3] node=3: unable to log node_join event: log-event: node unavailable; try another peer
admin_test.go:1624: AdminChangeReplicas error: snapshot failed: (n2,s2):?: remote failed to apply snapshot: rpc error: code = Unavailable desc = transport is closing
```
Please assign, take a look and update the issue accordingly.
| test | teamcity failed test testenqueuerange the following tests appear to have failed on master testrace testenqueuerange you may want to check testenqueuerange y another peer storage store go could not gossip first range descriptor node unavailable try another peer storage store go could not gossip first range descriptor node unavailable try another peer storage store go could not gossip first range descriptor node unavailable try another peer storage store go could not gossip first range descriptor node unavailable try another peer storage store go could not gossip first range descriptor node unavailable try another peer storage queue go rate limited in maybeadd gc node unavailable try another peer storage queue go rate limited in maybeadd merge node unavailable try another peer storage queue go rate limited in maybeadd split node unavailable try another peer storage queue go rate limited in maybeadd replicate node unavailable try another peer storage queue go rate limited in maybeadd replicagc node unavailable try another peer storage queue go rate limited in maybeadd raftlog node unavailable try another peer storage queue go rate limited in maybeadd raftsnapshot node unavailable try another peer storage queue go rate limited in maybeadd consistencychecker node unavailable try another peer storage queue go rate limited in maybeadd timeseriesmaintenance node unavailable try another peer storage store go could not gossip first range descriptor node unavailable try another peer storage store go could not gossip first range descriptor node unavailable try another peer storage store go could not gossip first range descriptor node unavailable try another peer server node go error recording status summaries node unavailable try another peer storage store go could not gossip first range descriptor node unavailable try another peer ts db go node unavailable try another peer server node go error recording status summaries node unavailable try another peer ts db go node unavailable try another peer server status runtime go runtime stats gib rss goroutines mib mib mib go alloc idle total stale mib mib cgo alloc total cgo sec u s time gc kib kib r w net server status runtime go runtime stats gib rss goroutines mib mib mib go alloc idle total stale mib mib cgo alloc total cgo sec u s time gc kib kib r w net server node go node unable to log node join event log event node unavailable try another peer admin test go adminchangereplicas error snapshot failed remote failed to apply snapshot rpc error code unavailable desc transport is closing please assign take a look and update the issue accordingly | 1 |
61,532 | 25,550,315,820 | IssuesEvent | 2022-11-29 22:55:25 | microsoft/BotFramework-WebChat | https://api.github.com/repos/microsoft/BotFramework-WebChat | closed | Restoring chat history should not mark user activities as "send failed" | bug customer-reported Bot Services customer-replied-to icm | ### Is it an issue related to Adaptive Cards?
- [ ] Yes, this is an Adaptive Card issue but it is specific to Web Chat.
### Do you have any screenshots?
### What version of Web Chat are you using?
Latest production
The bug first introduced in 4.15.3 and did not repro on 4.15.2.
### Which distribution are you using Web Chat from?
Bundle (webchat.js)
### Which hosting environment does this issue primarily affect?
Web apps
### Which browsers and platforms do the issue happened?
Browser: Edge (latest), Browser: Chrome (latest), Browser: Firefox (latest), Browser: Safari (latest), Browser: IE Mode (latest), Platform: Windows, Platform: macOS, Platform: iOS/iPadOS, Platform: Android
### Which area does this issue affect?
Chat history
### Is this an accessibility issue?
- [ ] Yes, this is an accessibility issue.
### Please describe the bug
When restoring chat history from ABS, activities sent by user are wrongly tagged as "Send failed. Retry."
This only repro when the `localTimestamp` field is present.
### Do you see any errors in console log?
_No response_
### How to reproduce the issue?
Use this HTML in WebDriver.
```html
<!DOCTYPE html>
<html lang="en-US">
<head>
<link href="/assets/index.css" rel="stylesheet" type="text/css" />
<script crossorigin="anonymous" src="/test-harness.js"></script>
<script crossorigin="anonymous" src="/test-page-object.js"></script>
<script crossorigin="anonymous" src="/__dist__/webchat-es5.js"></script>
<!-- <script crossorigin="anonymous" src="https://cdn.botframework.com/botframework-webchat/4.15.2/webchat-es5.js"></script> -->
</head>
<body>
<div id="webchat"></div>
<script>
run(async function () {
const store = testHelpers.createStore();
const directLine = testHelpers.createDirectLineEmulator(store);
WebChat.renderWebChat(
{ directLine, store, userID: 'u-00001' },
document.getElementById('webchat')
);
await pageConditions.uiConnected();
await directLine.emulateIncomingActivity({
type: 'message',
id: 'c00001-us|0000000',
timestamp: '2022-11-11T19:34:00.000Z',
// If `localTimestamp` is not present, this will not repro.
localTimestamp: '2022-11-11T11:34:00.000-08:00',
from: {
id: 'u00001',
role: 'user'
},
text: 'Hello, World!',
channelData: {
clientActivityID: 'ca00001'
}
});
});
</script>
</body>
</html>
```
### What is the expected and actual behavior?
Expected:
The send status for the first activity should be "Just now." or a date.
Actual:
The send status is "Send failed. Retry."
### Adaptive Card JSON
_No response_
### Additional context
Possibly related to PR #4362.
Related to ticket [346670699](https://portal.microsofticm.com/imp/v3/incidents/details/346670699/home).
| 1.0 | Restoring chat history should not mark user activities as "send failed" - ### Is it an issue related to Adaptive Cards?
- [ ] Yes, this is an Adaptive Card issue but it is specific to Web Chat.
### Do you have any screenshots?
### What version of Web Chat are you using?
Latest production
The bug first introduced in 4.15.3 and did not repro on 4.15.2.
### Which distribution are you using Web Chat from?
Bundle (webchat.js)
### Which hosting environment does this issue primarily affect?
Web apps
### Which browsers and platforms do the issue happened?
Browser: Edge (latest), Browser: Chrome (latest), Browser: Firefox (latest), Browser: Safari (latest), Browser: IE Mode (latest), Platform: Windows, Platform: macOS, Platform: iOS/iPadOS, Platform: Android
### Which area does this issue affect?
Chat history
### Is this an accessibility issue?
- [ ] Yes, this is an accessibility issue.
### Please describe the bug
When restoring chat history from ABS, activities sent by user are wrongly tagged as "Send failed. Retry."
This only repro when the `localTimestamp` field is present.
### Do you see any errors in console log?
_No response_
### How to reproduce the issue?
Use this HTML in WebDriver.
```html
<!DOCTYPE html>
<html lang="en-US">
<head>
<link href="/assets/index.css" rel="stylesheet" type="text/css" />
<script crossorigin="anonymous" src="/test-harness.js"></script>
<script crossorigin="anonymous" src="/test-page-object.js"></script>
<script crossorigin="anonymous" src="/__dist__/webchat-es5.js"></script>
<!-- <script crossorigin="anonymous" src="https://cdn.botframework.com/botframework-webchat/4.15.2/webchat-es5.js"></script> -->
</head>
<body>
<div id="webchat"></div>
<script>
run(async function () {
const store = testHelpers.createStore();
const directLine = testHelpers.createDirectLineEmulator(store);
WebChat.renderWebChat(
{ directLine, store, userID: 'u-00001' },
document.getElementById('webchat')
);
await pageConditions.uiConnected();
await directLine.emulateIncomingActivity({
type: 'message',
id: 'c00001-us|0000000',
timestamp: '2022-11-11T19:34:00.000Z',
// If `localTimestamp` is not present, this will not repro.
localTimestamp: '2022-11-11T11:34:00.000-08:00',
from: {
id: 'u00001',
role: 'user'
},
text: 'Hello, World!',
channelData: {
clientActivityID: 'ca00001'
}
});
});
</script>
</body>
</html>
```
### What is the expected and actual behavior?
Expected:
The send status for the first activity should be "Just now." or a date.
Actual:
The send status is "Send failed. Retry."
### Adaptive Card JSON
_No response_
### Additional context
Possibly related to PR #4362.
Related to ticket [346670699](https://portal.microsofticm.com/imp/v3/incidents/details/346670699/home).
| non_test | restoring chat history should not mark user activities as send failed is it an issue related to adaptive cards yes this is an adaptive card issue but it is specific to web chat do you have any screenshots what version of web chat are you using latest production the bug first introduced in and did not repro on which distribution are you using web chat from bundle webchat js which hosting environment does this issue primarily affect web apps which browsers and platforms do the issue happened browser edge latest browser chrome latest browser firefox latest browser safari latest browser ie mode latest platform windows platform macos platform ios ipados platform android which area does this issue affect chat history is this an accessibility issue yes this is an accessibility issue please describe the bug when restoring chat history from abs activities sent by user are wrongly tagged as send failed retry this only repro when the localtimestamp field is present do you see any errors in console log no response how to reproduce the issue use this html in webdriver html run async function const store testhelpers createstore const directline testhelpers createdirectlineemulator store webchat renderwebchat directline store userid u document getelementbyid webchat await pageconditions uiconnected await directline emulateincomingactivity type message id us timestamp if localtimestamp is not present this will not repro localtimestamp from id role user text hello world channeldata clientactivityid what is the expected and actual behavior expected the send status for the first activity should be just now or a date actual the send status is send failed retry adaptive card json no response additional context possibly related to pr related to ticket | 0 |
345,342 | 30,802,750,550 | IssuesEvent | 2023-08-01 03:44:38 | opensearch-project/OpenSearch | https://api.github.com/repos/opensearch-project/OpenSearch | closed | [BUG] org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests.testBasicTaskResourceTracking is flaky | bug flaky-test | See https://build.ci.opensearch.org/job/gradle-check/18108/
```
REPRODUCE WITH: ./gradlew ':server:test' --tests "org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests.testBasicTaskResourceTracking" -Dtests.seed=3A623BD634D99A0D -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=ar-KW -Dtests.timezone=Europe/Paris -Druntime.java=20
```
Error showing up -
```
يون 21, 2023 9:25:43 م com.carrotsearch.randomizedtesting.RandomizedRunner$QueueUncaughtExceptionsHandler uncaughtException
WARNING: Uncaught exception in thread: Thread[#125,opensearch[TransportTasksActionTests][search][T#1],5,TGRP-ResourceAwareTasksTests]
java.lang.AssertionError:
Expected: a value less than or equal to <8200000L>
but: <8280016L> was greater than <8200000L>
at __randomizedtesting.SeedInfo.seed([3A623BD634D99A0D]:0)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
at org.junit.Assert.assertThat(Assert.java:964)
at org.junit.Assert.assertThat(Assert.java:930)
at org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests.assertMemoryUsageWithinLimits(ResourceAwareTasksTests.java:677)
at org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests.lambda$testBasicTaskResourceTracking$1(ResourceAwareTasksTests.java:314)
at org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests$ResourceAwareNodesAction$1$1.innerOnResponse(ResourceAwareTasksTests.java:194)
at org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests$ResourceAwareNodesAction$1$1.innerOnResponse(ResourceAwareTasksTests.java:191)
at org.opensearch.action.NotifyOnceListener.onResponse(NotifyOnceListener.java:55)
at org.opensearch.tasks.Task.lambda$decrementResourceTrackingThreads$1(Task.java:564)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at org.opensearch.tasks.Task.decrementResourceTrackingThreads(Task.java:562)
at org.opensearch.tasks.Task.stopThreadResourceTracking(Task.java:468)
at org.opensearch.tasks.TaskResourceTrackingService.taskExecutionFinishedOnThread(TaskResourceTrackingService.java:198)
at org.opensearch.threadpool.TaskAwareRunnable.doRun(TaskAwareRunnable.java:81)
at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52)
at org.opensearch.common.util.concurrent.TimedRunnable.doRun(TimedRunnable.java:59)
at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:806)
at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1623)
``` | 1.0 | [BUG] org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests.testBasicTaskResourceTracking is flaky - See https://build.ci.opensearch.org/job/gradle-check/18108/
```
REPRODUCE WITH: ./gradlew ':server:test' --tests "org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests.testBasicTaskResourceTracking" -Dtests.seed=3A623BD634D99A0D -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=ar-KW -Dtests.timezone=Europe/Paris -Druntime.java=20
```
Error showing up -
```
يون 21, 2023 9:25:43 م com.carrotsearch.randomizedtesting.RandomizedRunner$QueueUncaughtExceptionsHandler uncaughtException
WARNING: Uncaught exception in thread: Thread[#125,opensearch[TransportTasksActionTests][search][T#1],5,TGRP-ResourceAwareTasksTests]
java.lang.AssertionError:
Expected: a value less than or equal to <8200000L>
but: <8280016L> was greater than <8200000L>
at __randomizedtesting.SeedInfo.seed([3A623BD634D99A0D]:0)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
at org.junit.Assert.assertThat(Assert.java:964)
at org.junit.Assert.assertThat(Assert.java:930)
at org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests.assertMemoryUsageWithinLimits(ResourceAwareTasksTests.java:677)
at org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests.lambda$testBasicTaskResourceTracking$1(ResourceAwareTasksTests.java:314)
at org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests$ResourceAwareNodesAction$1$1.innerOnResponse(ResourceAwareTasksTests.java:194)
at org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests$ResourceAwareNodesAction$1$1.innerOnResponse(ResourceAwareTasksTests.java:191)
at org.opensearch.action.NotifyOnceListener.onResponse(NotifyOnceListener.java:55)
at org.opensearch.tasks.Task.lambda$decrementResourceTrackingThreads$1(Task.java:564)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at org.opensearch.tasks.Task.decrementResourceTrackingThreads(Task.java:562)
at org.opensearch.tasks.Task.stopThreadResourceTracking(Task.java:468)
at org.opensearch.tasks.TaskResourceTrackingService.taskExecutionFinishedOnThread(TaskResourceTrackingService.java:198)
at org.opensearch.threadpool.TaskAwareRunnable.doRun(TaskAwareRunnable.java:81)
at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52)
at org.opensearch.common.util.concurrent.TimedRunnable.doRun(TimedRunnable.java:59)
at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:806)
at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1623)
``` | test | org opensearch action admin cluster node tasks resourceawaretaskstests testbasictaskresourcetracking is flaky see reproduce with gradlew server test tests org opensearch action admin cluster node tasks resourceawaretaskstests testbasictaskresourcetracking dtests seed dtests security manager true dtests jvm argline xx tieredstopatlevel xx reservedcodecachesize dtests locale ar kw dtests timezone europe paris druntime java error showing up يون م com carrotsearch randomizedtesting randomizedrunner queueuncaughtexceptionshandler uncaughtexception warning uncaught exception in thread thread tgrp resourceawaretaskstests java lang assertionerror expected a value less than or equal to but was greater than at randomizedtesting seedinfo seed at org hamcrest matcherassert assertthat matcherassert java at org junit assert assertthat assert java at org junit assert assertthat assert java at org opensearch action admin cluster node tasks resourceawaretaskstests assertmemoryusagewithinlimits resourceawaretaskstests java at org opensearch action admin cluster node tasks resourceawaretaskstests lambda testbasictaskresourcetracking resourceawaretaskstests java at org opensearch action admin cluster node tasks resourceawaretaskstests resourceawarenodesaction inneronresponse resourceawaretaskstests java at org opensearch action admin cluster node tasks resourceawaretaskstests resourceawarenodesaction inneronresponse resourceawaretaskstests java at org opensearch action notifyoncelistener onresponse notifyoncelistener java at org opensearch tasks task lambda decrementresourcetrackingthreads task java at java base java util arraylist foreach arraylist java at org opensearch tasks task decrementresourcetrackingthreads task java at org opensearch tasks task stopthreadresourcetracking task java at org opensearch tasks taskresourcetrackingservice taskexecutionfinishedonthread taskresourcetrackingservice java at org opensearch threadpool taskawarerunnable dorun taskawarerunnable java at org opensearch common util concurrent abstractrunnable run abstractrunnable java at org opensearch common util concurrent timedrunnable dorun timedrunnable java at org opensearch common util concurrent threadcontext contextpreservingabstractrunnable dorun threadcontext java at org opensearch common util concurrent abstractrunnable run abstractrunnable java at java base java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java base java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java base java lang thread run thread java | 1 |
270,337 | 20,598,063,952 | IssuesEvent | 2022-03-05 20:40:54 | bounswe/bounswe2022group6 | https://api.github.com/repos/bounswe/bounswe2022group6 | opened | Creating a page for the repository research | documentation help wanted | A page needs to be created to store the repositories that we liked. The page should have,
- repository names as headers that are also links to the repositories
- a brief explanation of what the repository is for
- a brief explanation to why the person who found it liked it
- the name of the team member who found it
**Deadline: ** 06.03.2022 | 1.0 | Creating a page for the repository research - A page needs to be created to store the repositories that we liked. The page should have,
- repository names as headers that are also links to the repositories
- a brief explanation of what the repository is for
- a brief explanation to why the person who found it liked it
- the name of the team member who found it
**Deadline: ** 06.03.2022 | non_test | creating a page for the repository research a page needs to be created to store the repositories that we liked the page should have repository names as headers that are also links to the repositories a brief explanation of what the repository is for a brief explanation to why the person who found it liked it the name of the team member who found it deadline | 0 |
21,281 | 3,881,665,008 | IssuesEvent | 2016-04-13 06:15:40 | couchbase/couchbase-lite-ios | https://api.github.com/repos/couchbase/couchbase-lite-ios | opened | Test Replicator/Reachability with Proxy | chore testing | Per change to support reachability over a proxy, we should test the replicator with a proxy setup.
| 1.0 | Test Replicator/Reachability with Proxy - Per change to support reachability over a proxy, we should test the replicator with a proxy setup.
| test | test replicator reachability with proxy per change to support reachability over a proxy we should test the replicator with a proxy setup | 1 |
40,982 | 5,328,654,193 | IssuesEvent | 2017-02-15 12:46:39 | modelica/Modelica | https://api.github.com/repos/modelica/Modelica | closed | Naming of ModelicaTest.MultiBody.Forces.Worldtorque | duplicate L: ModelicaTest | Rename ModelicaTest.MultiBody.Forces.Worldtorque to WorldTorques in order to better comply with ModelicaTest.MultiBody.Forces.WorldForces. | 1.0 | Naming of ModelicaTest.MultiBody.Forces.Worldtorque - Rename ModelicaTest.MultiBody.Forces.Worldtorque to WorldTorques in order to better comply with ModelicaTest.MultiBody.Forces.WorldForces. | test | naming of modelicatest multibody forces worldtorque rename modelicatest multibody forces worldtorque to worldtorques in order to better comply with modelicatest multibody forces worldforces | 1 |
92,505 | 8,366,062,095 | IssuesEvent | 2018-10-04 07:58:04 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | roachtest: drop/tpcc/w=100,nodes=9 failed | C-test-failure O-robot | SHA: https://github.com/cockroachdb/cockroach/commits/6a236533824c797948eaddbd6bedf5e12eee1a13
Parameters:
To repro, try:
```
# Don't forget to check out a clean suitable branch and experiment with the
# stress invocation until the desired results present themselves. For example,
# using stressrace instead of stress and passing the '-p' stressflag which
# controls concurrency.
./scripts/gceworker.sh start && ./scripts/gceworker.sh mosh
cd ~/go/src/github.com/cockroachdb/cockroach && \
make stress TESTS=drop/tpcc/w=100,nodes=9 PKG=roachtest TESTTIMEOUT=5m STRESSFLAGS='-stderr=false -maxtime 20m -timeout 10m'
```
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=942507&tab=buildLog
```
The test failed on master:
test.go:500,cluster.go:897,drop.go:45,cluster.go:1206,errgroup.go:58: /home/agent/work/.go/bin/roachprod run teamcity-942507-drop-tpcc-w-100-nodes-9:1 -- ./workload fixtures load tpcc --warehouses=100 --db tpcc {pgurl:1} returned:
stderr:
stdout:
1004 07:25:44.533858 74 ccl/workloadccl/fixture.go:454 loaded order (21s, 3000000 rows, 6000000 index entries, 166 MiB)
I181004 07:25:50.250698 70 ccl/workloadccl/fixture.go:454 loaded warehouse (27s, 100 rows, 0 index entries, 5.1 KiB)
I181004 07:26:36.304737 75 ccl/workloadccl/fixture.go:454 loaded new_order (1m13s, 900000 rows, 0 index entries, 11 MiB)
I181004 07:27:06.501609 73 ccl/workloadccl/fixture.go:454 loaded history (1m43s, 3000000 rows, 6000000 index entries, 380 MiB)
I181004 07:27:07.909798 77 ccl/workloadccl/fixture.go:454 loaded stock (1m44s, 10000000 rows, 10000000 index entries, 3.1 GiB)
I181004 07:27:26.360689 72 ccl/workloadccl/fixture.go:454 loaded customer (2m3s, 3000000 rows, 3000000 index entries, 1.7 GiB)
I181004 07:27:30.366393 78 ccl/workloadccl/fixture.go:454 loaded order_line (2m7s, 29995875 rows, 29995875 index entries, 2.0 GiB)
Error: restoring fixture: PostLoad hook: pq: foreign key requires an existing index on columns ("ol_supply_w_id", "ol_i_id")
Error: exit status 1
: exit status 1
test.go:500,cluster.go:1227,drop.go:159,drop.go:184: Goexit() was called
``` | 1.0 | roachtest: drop/tpcc/w=100,nodes=9 failed - SHA: https://github.com/cockroachdb/cockroach/commits/6a236533824c797948eaddbd6bedf5e12eee1a13
Parameters:
To repro, try:
```
# Don't forget to check out a clean suitable branch and experiment with the
# stress invocation until the desired results present themselves. For example,
# using stressrace instead of stress and passing the '-p' stressflag which
# controls concurrency.
./scripts/gceworker.sh start && ./scripts/gceworker.sh mosh
cd ~/go/src/github.com/cockroachdb/cockroach && \
make stress TESTS=drop/tpcc/w=100,nodes=9 PKG=roachtest TESTTIMEOUT=5m STRESSFLAGS='-stderr=false -maxtime 20m -timeout 10m'
```
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=942507&tab=buildLog
```
The test failed on master:
test.go:500,cluster.go:897,drop.go:45,cluster.go:1206,errgroup.go:58: /home/agent/work/.go/bin/roachprod run teamcity-942507-drop-tpcc-w-100-nodes-9:1 -- ./workload fixtures load tpcc --warehouses=100 --db tpcc {pgurl:1} returned:
stderr:
stdout:
1004 07:25:44.533858 74 ccl/workloadccl/fixture.go:454 loaded order (21s, 3000000 rows, 6000000 index entries, 166 MiB)
I181004 07:25:50.250698 70 ccl/workloadccl/fixture.go:454 loaded warehouse (27s, 100 rows, 0 index entries, 5.1 KiB)
I181004 07:26:36.304737 75 ccl/workloadccl/fixture.go:454 loaded new_order (1m13s, 900000 rows, 0 index entries, 11 MiB)
I181004 07:27:06.501609 73 ccl/workloadccl/fixture.go:454 loaded history (1m43s, 3000000 rows, 6000000 index entries, 380 MiB)
I181004 07:27:07.909798 77 ccl/workloadccl/fixture.go:454 loaded stock (1m44s, 10000000 rows, 10000000 index entries, 3.1 GiB)
I181004 07:27:26.360689 72 ccl/workloadccl/fixture.go:454 loaded customer (2m3s, 3000000 rows, 3000000 index entries, 1.7 GiB)
I181004 07:27:30.366393 78 ccl/workloadccl/fixture.go:454 loaded order_line (2m7s, 29995875 rows, 29995875 index entries, 2.0 GiB)
Error: restoring fixture: PostLoad hook: pq: foreign key requires an existing index on columns ("ol_supply_w_id", "ol_i_id")
Error: exit status 1
: exit status 1
test.go:500,cluster.go:1227,drop.go:159,drop.go:184: Goexit() was called
``` | test | roachtest drop tpcc w nodes failed sha parameters to repro try don t forget to check out a clean suitable branch and experiment with the stress invocation until the desired results present themselves for example using stressrace instead of stress and passing the p stressflag which controls concurrency scripts gceworker sh start scripts gceworker sh mosh cd go src github com cockroachdb cockroach make stress tests drop tpcc w nodes pkg roachtest testtimeout stressflags stderr false maxtime timeout failed test the test failed on master test go cluster go drop go cluster go errgroup go home agent work go bin roachprod run teamcity drop tpcc w nodes workload fixtures load tpcc warehouses db tpcc pgurl returned stderr stdout ccl workloadccl fixture go loaded order rows index entries mib ccl workloadccl fixture go loaded warehouse rows index entries kib ccl workloadccl fixture go loaded new order rows index entries mib ccl workloadccl fixture go loaded history rows index entries mib ccl workloadccl fixture go loaded stock rows index entries gib ccl workloadccl fixture go loaded customer rows index entries gib ccl workloadccl fixture go loaded order line rows index entries gib error restoring fixture postload hook pq foreign key requires an existing index on columns ol supply w id ol i id error exit status exit status test go cluster go drop go drop go goexit was called | 1 |
39,928 | 5,256,872,320 | IssuesEvent | 2017-02-02 19:03:33 | openbmc/openbmc-test-automation | https://api.github.com/repos/openbmc/openbmc-test-automation | closed | IPL: [Automation] Witherspoon PowerOn Test | feature Func:IPL Test | We have a go ahead to start trying test on witherspoon.. Will start enabling the poweron use case..
Place holder until poweron come cleans.. | 1.0 | IPL: [Automation] Witherspoon PowerOn Test - We have a go ahead to start trying test on witherspoon.. Will start enabling the poweron use case..
Place holder until poweron come cleans.. | test | ipl witherspoon poweron test we have a go ahead to start trying test on witherspoon will start enabling the poweron use case place holder until poweron come cleans | 1 |
304,764 | 23,082,232,862 | IssuesEvent | 2022-07-26 08:17:51 | agri-gaia/seerep | https://api.github.com/repos/agri-gaia/seerep | closed | Add docker quickstart to README | documentation | Add a `docker run ` and an example docker-compose to the readme so that it is also displayed when looking at the image in the browser | 1.0 | Add docker quickstart to README - Add a `docker run ` and an example docker-compose to the readme so that it is also displayed when looking at the image in the browser | non_test | add docker quickstart to readme add a docker run and an example docker compose to the readme so that it is also displayed when looking at the image in the browser | 0 |
104,314 | 4,209,268,469 | IssuesEvent | 2016-06-29 04:02:13 | PoisonNinja/Electron | https://api.github.com/repos/PoisonNinja/Electron | opened | New memory manager | enhancement high-priority kernel | Honestly, the ToaruOS memory manager is huge, and I admit that it works great. However, I would like to replace all ToaruOS code with my own, and this seems like a good candidate. It would also be a great learning experience, as I don't really understand how memory managers work. | 1.0 | New memory manager - Honestly, the ToaruOS memory manager is huge, and I admit that it works great. However, I would like to replace all ToaruOS code with my own, and this seems like a good candidate. It would also be a great learning experience, as I don't really understand how memory managers work. | non_test | new memory manager honestly the toaruos memory manager is huge and i admit that it works great however i would like to replace all toaruos code with my own and this seems like a good candidate it would also be a great learning experience as i don t really understand how memory managers work | 0 |
178,490 | 13,781,502,922 | IssuesEvent | 2020-10-08 16:15:51 | project-receptor/receptor | https://api.github.com/repos/project-receptor/receptor | closed | Handle kubernetes credentials in a secure manner | needs_test | Graham has a PR up that allows for passing in Kubernetes credentials at runtime, a requirement for the AWX / Tower use case of Receptor: project-receptor/receptor#172
There is a security concern regarding the implementation here:
> your k8s bearer token winds up in the Receptor status file, visible in work list, etc | 1.0 | Handle kubernetes credentials in a secure manner - Graham has a PR up that allows for passing in Kubernetes credentials at runtime, a requirement for the AWX / Tower use case of Receptor: project-receptor/receptor#172
There is a security concern regarding the implementation here:
> your k8s bearer token winds up in the Receptor status file, visible in work list, etc | test | handle kubernetes credentials in a secure manner graham has a pr up that allows for passing in kubernetes credentials at runtime a requirement for the awx tower use case of receptor project receptor receptor there is a security concern regarding the implementation here your bearer token winds up in the receptor status file visible in work list etc | 1 |
176,093 | 28,030,492,911 | IssuesEvent | 2023-03-28 12:04:56 | ethereum/solidity | https://api.github.com/repos/ethereum/solidity | closed | Allow covariant return type implementation | language design :rage4: high effort low impact needs design closed-due-inactivity stale | ## Abstract
Languages usually allow covariant return type implementation of interfaces (C++, Java), but solidity seems to enforce type equality in return values.
## Motivation
Languages usually allow covariant return type implementation of interfaces (C++, Java), but solidity seems to enforce type equality in return values. Take an example code (fails both in `8.+` and `7.6`):
```solidity
interface A {}
interface B is A {}
interface X {
function temp() external pure returns (A);
}
contract Y is X {
// This is allowed since B is implicitly cast to A on return
/*
function some_fun() pure external override returns(A){
return B(address(0));
}
*/
// This gets rejected by the compiler since `B` is not equal to `A`
function some_fun() pure external override returns(B){
return B(address(0));
}
}
```
This gets especially problematic with automatic getters for public contract data.
```solidity
interface A {}
interface B is A {}
interface X {
function data() external view returns (A);
}
contract Y is X {
B public override data; // Fails since type is not correct
B public data; // Missing override specifier
}
```
To get the second contract to type check (and use the `B` interface instead of `A`), one has to add an internal field for `data` and manually write the getter function.
## Specification
Implementation type checking should be implemented using `is subtype` instead of using strict type equality.
## Backwards Compatibility
I am unsure of backward incompatibilities, but it might pose some unexpected problems with differently sized uint types and unexpected implicit overloads. | 2.0 | Allow covariant return type implementation - ## Abstract
Languages usually allow covariant return type implementation of interfaces (C++, Java), but solidity seems to enforce type equality in return values.
## Motivation
Languages usually allow covariant return type implementation of interfaces (C++, Java), but solidity seems to enforce type equality in return values. Take an example code (fails both in `8.+` and `7.6`):
```solidity
interface A {}
interface B is A {}
interface X {
function temp() external pure returns (A);
}
contract Y is X {
// This is allowed since B is implicitly cast to A on return
/*
function some_fun() pure external override returns(A){
return B(address(0));
}
*/
// This gets rejected by the compiler since `B` is not equal to `A`
function some_fun() pure external override returns(B){
return B(address(0));
}
}
```
This gets especially problematic with automatic getters for public contract data.
```solidity
interface A {}
interface B is A {}
interface X {
function data() external view returns (A);
}
contract Y is X {
B public override data; // Fails since type is not correct
B public data; // Missing override specifier
}
```
To get the second contract to type check (and use the `B` interface instead of `A`), one has to add an internal field for `data` and manually write the getter function.
## Specification
Implementation type checking should be implemented using `is subtype` instead of using strict type equality.
## Backwards Compatibility
I am unsure of backward incompatibilities, but it might pose some unexpected problems with differently sized uint types and unexpected implicit overloads. | non_test | allow covariant return type implementation abstract languages usually allow covariant return type implementation of interfaces c java but solidity seems to enforce type equality in return values motivation languages usually allow covariant return type implementation of interfaces c java but solidity seems to enforce type equality in return values take an example code fails both in and solidity interface a interface b is a interface x function temp external pure returns a contract y is x this is allowed since b is implicitly cast to a on return function some fun pure external override returns a return b address this gets rejected by the compiler since b is not equal to a function some fun pure external override returns b return b address this gets especially problematic with automatic getters for public contract data solidity interface a interface b is a interface x function data external view returns a contract y is x b public override data fails since type is not correct b public data missing override specifier to get the second contract to type check and use the b interface instead of a one has to add an internal field for data and manually write the getter function specification implementation type checking should be implemented using is subtype instead of using strict type equality backwards compatibility i am unsure of backward incompatibilities but it might pose some unexpected problems with differently sized uint types and unexpected implicit overloads | 0 |
451,407 | 13,035,087,910 | IssuesEvent | 2020-07-28 09:46:50 | onaio/reveal-frontend | https://api.github.com/repos/onaio/reveal-frontend | closed | Refactors Oauth flow to account for opensrp server migration to keycloack . | Priority: High | We need to support the new flow for oath login due to opensrp migrating to use keycloack for its user management.
- I believe the changes will mostly be in the onaio/gatekeeper package.
- from preliminary talks it seems that we should expect the response for `user-details` to change
- Also we will know be getting the redirect_uris, and authorization_uris, from an endpoint on the server `/opensrp/rest/config/keycloak` | 1.0 | Refactors Oauth flow to account for opensrp server migration to keycloack . - We need to support the new flow for oath login due to opensrp migrating to use keycloack for its user management.
- I believe the changes will mostly be in the onaio/gatekeeper package.
- from preliminary talks it seems that we should expect the response for `user-details` to change
- Also we will know be getting the redirect_uris, and authorization_uris, from an endpoint on the server `/opensrp/rest/config/keycloak` | non_test | refactors oauth flow to account for opensrp server migration to keycloack we need to support the new flow for oath login due to opensrp migrating to use keycloack for its user management i believe the changes will mostly be in the onaio gatekeeper package from preliminary talks it seems that we should expect the response for user details to change also we will know be getting the redirect uris and authorization uris from an endpoint on the server opensrp rest config keycloak | 0 |
64,627 | 15,978,069,457 | IssuesEvent | 2021-04-17 08:13:23 | StanfordLegion/legion | https://api.github.com/repos/StanfordLegion/legion | closed | Build failure when CXX=mpicxx | Build bug | When attempting to build current `stable` (0cf9ddd6) for GASNet's ibv-conduit, I have set `CXX=mpicxx` based on past practice. However, I find that for this case and others using MPI, `runtime/runtime.mk` executes `export OMPI_CXX := $(CXX)`. The result is that Open MPI recursively calls itself and fails spectacularly.
Now that I am aware of it, I will avoid triggering this behavior, and so this not a "big problem" for me.
However, @streichler suggested to me that it might be possible for `runtime.mk` to detect and avoid this case, and requested that I report this issue. | 1.0 | Build failure when CXX=mpicxx - When attempting to build current `stable` (0cf9ddd6) for GASNet's ibv-conduit, I have set `CXX=mpicxx` based on past practice. However, I find that for this case and others using MPI, `runtime/runtime.mk` executes `export OMPI_CXX := $(CXX)`. The result is that Open MPI recursively calls itself and fails spectacularly.
Now that I am aware of it, I will avoid triggering this behavior, and so this not a "big problem" for me.
However, @streichler suggested to me that it might be possible for `runtime.mk` to detect and avoid this case, and requested that I report this issue. | non_test | build failure when cxx mpicxx when attempting to build current stable for gasnet s ibv conduit i have set cxx mpicxx based on past practice however i find that for this case and others using mpi runtime runtime mk executes export ompi cxx cxx the result is that open mpi recursively calls itself and fails spectacularly now that i am aware of it i will avoid triggering this behavior and so this not a big problem for me however streichler suggested to me that it might be possible for runtime mk to detect and avoid this case and requested that i report this issue | 0 |
1,129 | 2,532,274,852 | IssuesEvent | 2015-01-23 15:03:43 | AAndharia/ZIMS-School-Mgmt | https://api.github.com/repos/AAndharia/ZIMS-School-Mgmt | closed | edit student | bug Tested & Verified | click on edit button from list of student > change photo > submit will add new record instead of update student record | 1.0 | edit student - click on edit button from list of student > change photo > submit will add new record instead of update student record | test | edit student click on edit button from list of student change photo submit will add new record instead of update student record | 1 |
23,266 | 4,004,792,398 | IssuesEvent | 2016-05-12 08:53:07 | openshift/origin | https://api.github.com/repos/openshift/origin | closed | extended test: openshift mongo ephemeral consistently failing | area/tests component/image kind/bug priority/P1 | ```
• Failure [905.914 seconds]
[images][mongodb] openshift mongodb image
/data/src/github.com/openshift/origin/test/extended/images/mongodb_ephemeral.go:61
creating from a template
/data/src/github.com/openshift/origin/test/extended/images/mongodb_ephemeral.go:59
should process and create the "/data/src/github.com/openshift/origin/examples/db-templates/mongodb-ephemeral-template.json" template [It]
/data/src/github.com/openshift/origin/test/extended/images/mongodb_ephemeral.go:58
Expected error:
<*errors.errorString | 0xc208dce050>: {
s: "timed out waiting for deployment \"mongodb\" after 15m0s",
}
timed out waiting for deployment "mongodb" after 15m0s
not to have occurred
/data/src/github.com/openshift/origin/test/extended/images/mongodb_ephemeral.go:29
```
Has not passed once in the last 5-10 runs, probably not a flake. | 1.0 | extended test: openshift mongo ephemeral consistently failing - ```
• Failure [905.914 seconds]
[images][mongodb] openshift mongodb image
/data/src/github.com/openshift/origin/test/extended/images/mongodb_ephemeral.go:61
creating from a template
/data/src/github.com/openshift/origin/test/extended/images/mongodb_ephemeral.go:59
should process and create the "/data/src/github.com/openshift/origin/examples/db-templates/mongodb-ephemeral-template.json" template [It]
/data/src/github.com/openshift/origin/test/extended/images/mongodb_ephemeral.go:58
Expected error:
<*errors.errorString | 0xc208dce050>: {
s: "timed out waiting for deployment \"mongodb\" after 15m0s",
}
timed out waiting for deployment "mongodb" after 15m0s
not to have occurred
/data/src/github.com/openshift/origin/test/extended/images/mongodb_ephemeral.go:29
```
Has not passed once in the last 5-10 runs, probably not a flake. | test | extended test openshift mongo ephemeral consistently failing • failure openshift mongodb image data src github com openshift origin test extended images mongodb ephemeral go creating from a template data src github com openshift origin test extended images mongodb ephemeral go should process and create the data src github com openshift origin examples db templates mongodb ephemeral template json template data src github com openshift origin test extended images mongodb ephemeral go expected error s timed out waiting for deployment mongodb after timed out waiting for deployment mongodb after not to have occurred data src github com openshift origin test extended images mongodb ephemeral go has not passed once in the last runs probably not a flake | 1 |
285,054 | 8,753,635,241 | IssuesEvent | 2018-12-14 09:08:03 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | online.s-pankki.fi - see bug description | browser-firefox priority-normal | <!-- @browser: Firefox 64.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0 -->
<!-- @reported_with: -->
**URL**: https://online.s-pankki.fi/ebank/auth/loginEbank.do
**Browser / Version**: Firefox 64.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes
**Problem type**: Something else
**Description**: login to bank services is broken, since last update. Works fine with Edge
**Steps to Reproduce**:
[](https://webcompat.com/uploads/2018/12/f6b07022-758b-4e71-b5c1-017fbd048089.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | online.s-pankki.fi - see bug description - <!-- @browser: Firefox 64.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0 -->
<!-- @reported_with: -->
**URL**: https://online.s-pankki.fi/ebank/auth/loginEbank.do
**Browser / Version**: Firefox 64.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes
**Problem type**: Something else
**Description**: login to bank services is broken, since last update. Works fine with Edge
**Steps to Reproduce**:
[](https://webcompat.com/uploads/2018/12/f6b07022-758b-4e71-b5c1-017fbd048089.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_test | online s pankki fi see bug description url browser version firefox operating system windows tested another browser yes problem type something else description login to bank services is broken since last update works fine with edge steps to reproduce browser configuration none from with ❤️ | 0 |
216,893 | 16,822,163,444 | IssuesEvent | 2021-06-17 14:16:12 | ESMValGroup/ESMValTool | https://api.github.com/repos/ESMValGroup/ESMValTool | opened | [technical] Be very careful how to pin PyPi dependencies in light of pip=21.x.x new solver | deployment installation testing | pip=21 has a brand new solver that is a lot more restrictive than previous (legacy) solver; this is good and bad at the same time (have yet to see the good side, mind you :grin: ). Take this [branch](https://github.com/ESMValGroup/ESMValTool/compare/pin_deps_pypi) for instance, where I have pinned a few test dependencies and a couple more actual deps to almost their latest version, you'd imagine this would work fine - no, pip will go on and try all previous versions and run [forever](https://circle-production-customer-artifacts.s3.amazonaws.com/picard/589ba551c9e77c0001faef5d/60cb4271235b2032f244026d-0-build/artifacts/logs/install.txt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20210617T140616Z&X-Amz-SignedHeaders=host&X-Amz-Expires=60&X-Amz-Credential=AKIAJR3Q6CR467H7Z55A%2F20210617%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Signature=262870adef8fa921ca764593035322c78276891b73ae975d0832c4d575a2e3f9) eventually the CI would kill the job out of time with no output. This is something that we have to be very careful with and we need to figure out an optimal solution for it (not just manual "hey this needs to be pinned" pinning method), the PyPi guys give some [guidelines](https://pip.pypa.io/en/latest/user_guide/#possible-ways-to-reduce-backtracking-occurring) on how to improve the pip env solving and minimize backtracking but IMHO this is bollox, the previous solver was doing a good job and I dunno why they need to become more conda-like now. | 1.0 | [technical] Be very careful how to pin PyPi dependencies in light of pip=21.x.x new solver - pip=21 has a brand new solver that is a lot more restrictive than previous (legacy) solver; this is good and bad at the same time (have yet to see the good side, mind you :grin: ). Take this [branch](https://github.com/ESMValGroup/ESMValTool/compare/pin_deps_pypi) for instance, where I have pinned a few test dependencies and a couple more actual deps to almost their latest version, you'd imagine this would work fine - no, pip will go on and try all previous versions and run [forever](https://circle-production-customer-artifacts.s3.amazonaws.com/picard/589ba551c9e77c0001faef5d/60cb4271235b2032f244026d-0-build/artifacts/logs/install.txt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20210617T140616Z&X-Amz-SignedHeaders=host&X-Amz-Expires=60&X-Amz-Credential=AKIAJR3Q6CR467H7Z55A%2F20210617%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Signature=262870adef8fa921ca764593035322c78276891b73ae975d0832c4d575a2e3f9) eventually the CI would kill the job out of time with no output. This is something that we have to be very careful with and we need to figure out an optimal solution for it (not just manual "hey this needs to be pinned" pinning method), the PyPi guys give some [guidelines](https://pip.pypa.io/en/latest/user_guide/#possible-ways-to-reduce-backtracking-occurring) on how to improve the pip env solving and minimize backtracking but IMHO this is bollox, the previous solver was doing a good job and I dunno why they need to become more conda-like now. | test | be very careful how to pin pypi dependencies in light of pip x x new solver pip has a brand new solver that is a lot more restrictive than previous legacy solver this is good and bad at the same time have yet to see the good side mind you grin take this for instance where i have pinned a few test dependencies and a couple more actual deps to almost their latest version you d imagine this would work fine no pip will go on and try all previous versions and run eventually the ci would kill the job out of time with no output this is something that we have to be very careful with and we need to figure out an optimal solution for it not just manual hey this needs to be pinned pinning method the pypi guys give some on how to improve the pip env solving and minimize backtracking but imho this is bollox the previous solver was doing a good job and i dunno why they need to become more conda like now | 1 |
752,434 | 26,285,473,964 | IssuesEvent | 2023-01-07 19:41:03 | asastats/channel | https://api.github.com/repos/asastats/channel | closed | [Internal] Add AlgoRai's goBTC and goETH vaults | feature medium priority | https://medium.com/@algorai.finance/algorai-finance-partners-with-algomint-to-launch-gobtc-goeth-options-vaults-bb847daea5
> Call and Put strategies on goBTC and goETH will be offered and vaults will be open from Friday 14th October 2022. | 1.0 | [Internal] Add AlgoRai's goBTC and goETH vaults - https://medium.com/@algorai.finance/algorai-finance-partners-with-algomint-to-launch-gobtc-goeth-options-vaults-bb847daea5
> Call and Put strategies on goBTC and goETH will be offered and vaults will be open from Friday 14th October 2022. | non_test | add algorai s gobtc and goeth vaults call and put strategies on gobtc and goeth will be offered and vaults will be open from friday october | 0 |
189,432 | 6,797,565,364 | IssuesEvent | 2017-11-01 23:36:53 | ucdavis/ipa-client-angular | https://api.github.com/repos/ucdavis/ipa-client-angular | closed | Teaching Call Form: Typeahead text searching needs improvement | bug high priority | For example, if the typeahead has EDU 101, EDU 102, EDU 103, etc., typing simply 'edu' results in no results filtered, but they re-appear when you finish typing 'edu 101'. This should really work how one expects dropdown typeaheads to work. | 1.0 | Teaching Call Form: Typeahead text searching needs improvement - For example, if the typeahead has EDU 101, EDU 102, EDU 103, etc., typing simply 'edu' results in no results filtered, but they re-appear when you finish typing 'edu 101'. This should really work how one expects dropdown typeaheads to work. | non_test | teaching call form typeahead text searching needs improvement for example if the typeahead has edu edu edu etc typing simply edu results in no results filtered but they re appear when you finish typing edu this should really work how one expects dropdown typeaheads to work | 0 |
91,848 | 15,856,662,527 | IssuesEvent | 2021-04-08 02:53:00 | Check-den-Fakt/WebScraper | https://api.github.com/repos/Check-den-Fakt/WebScraper | opened | CVE-2021-23337 (High) detected in lodash-4.17.15.tgz | security vulnerability | ## CVE-2021-23337 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.15.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p>
<p>Path to dependency file: WebScraper/package.json</p>
<p>Path to vulnerable library: WebScraper/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- cheerio-1.0.0-rc.3.tgz (Root Library)
- :x: **lodash-4.17.15.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</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.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- 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://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash - 4.17.21</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-23337 (High) detected in lodash-4.17.15.tgz - ## CVE-2021-23337 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.15.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p>
<p>Path to dependency file: WebScraper/package.json</p>
<p>Path to vulnerable library: WebScraper/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- cheerio-1.0.0-rc.3.tgz (Root Library)
- :x: **lodash-4.17.15.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</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.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- 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://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash - 4.17.21</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 lodash tgz cve high severity vulnerability vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file webscraper package json path to vulnerable library webscraper node modules lodash package json dependency hierarchy cheerio rc tgz root library x lodash tgz vulnerable library vulnerability details lodash versions prior to are vulnerable to command injection via the template function publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required high 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 lodash step up your open source security game with whitesource | 0 |
598,772 | 18,251,419,884 | IssuesEvent | 2021-10-02 09:17:25 | danilaSADev/Dudes-in-space | https://api.github.com/repos/danilaSADev/Dudes-in-space | closed | Task Generator | enhancement priority | # We need to create class that will be responsible for generating tasks for cosmonauts.
After task is being generated, it fires an event OnTaskAppeared.
Each task is going to be unique.
There's also may be an extreme tasks, that should get more player's attention and be solved as quickly as possible. (events) | 1.0 | Task Generator - # We need to create class that will be responsible for generating tasks for cosmonauts.
After task is being generated, it fires an event OnTaskAppeared.
Each task is going to be unique.
There's also may be an extreme tasks, that should get more player's attention and be solved as quickly as possible. (events) | non_test | task generator we need to create class that will be responsible for generating tasks for cosmonauts after task is being generated it fires an event ontaskappeared each task is going to be unique there s also may be an extreme tasks that should get more player s attention and be solved as quickly as possible events | 0 |
70,241 | 9,383,614,379 | IssuesEvent | 2019-04-05 04:29:37 | junit-team/junit5 | https://api.github.com/repos/junit-team/junit5 | closed | Update API status in User Guide | status: in progress theme: documentation | ## Overview
@fanngrim wrote on Mar 24 20:24 at https://gitter.im/junit-team/junit5
> Hi,
> I just noticed something in the documentation.
> The user guide states that Dynamic Tests are still an experimental feature but when checking the Experimental APIs table they are not listed there.
> Also, the TestFactory annotation is marked as MAINTAINED. Is the the documentation outdated?
## Deliverables
- [x] Remove outdated warning from Dynamic Tests section: https://github.com/junit-team/junit5/commit/1d9541999b3a38c6aa6c6f45e524753276fdc469
- [x] Verify other sections of the User Guide are in-sync with their annotations
- [x] Capturing std out/err
- [x] Parameterized Tests
- [x] JUnit 4 `Rule` support
- [x] JUnit 4 `@Ignore` support
- [x] `@TempDir`
- [x] Parallel test execution
- [x] Test Kit | 1.0 | Update API status in User Guide - ## Overview
@fanngrim wrote on Mar 24 20:24 at https://gitter.im/junit-team/junit5
> Hi,
> I just noticed something in the documentation.
> The user guide states that Dynamic Tests are still an experimental feature but when checking the Experimental APIs table they are not listed there.
> Also, the TestFactory annotation is marked as MAINTAINED. Is the the documentation outdated?
## Deliverables
- [x] Remove outdated warning from Dynamic Tests section: https://github.com/junit-team/junit5/commit/1d9541999b3a38c6aa6c6f45e524753276fdc469
- [x] Verify other sections of the User Guide are in-sync with their annotations
- [x] Capturing std out/err
- [x] Parameterized Tests
- [x] JUnit 4 `Rule` support
- [x] JUnit 4 `@Ignore` support
- [x] `@TempDir`
- [x] Parallel test execution
- [x] Test Kit | non_test | update api status in user guide overview fanngrim wrote on mar at hi i just noticed something in the documentation the user guide states that dynamic tests are still an experimental feature but when checking the experimental apis table they are not listed there also the testfactory annotation is marked as maintained is the the documentation outdated deliverables remove outdated warning from dynamic tests section verify other sections of the user guide are in sync with their annotations capturing std out err parameterized tests junit rule support junit ignore support tempdir parallel test execution test kit | 0 |
88,917 | 8,180,633,726 | IssuesEvent | 2018-08-28 20:06:18 | pytest-dev/pytest | https://api.github.com/repos/pytest-dev/pytest | closed | doctests regression with v3.7.3 on OS-X | os: mac plugin: doctests type: bug type: regression | - [x] Include a detailed description of the bug or suggestion
After upgrading to v3.7.3, all doctests started failing with the exception:
```
<my-pyenv>/lib/python3.7/site-packages/_pytest/doctest.py:206: TypeError: cannot unpack non-iterable NoneType object
```
Everything is OK with v3.7.2.
Slightly longer traceback (For the record, looking into the stacktrace, I see some references to "darwin"-specific functions):
```
___________________________________________________________________ [doctest] xxx ___________________________________________________________________
self = <CallInfo when='call' exception: cannot unpack non-iterable NoneType object>, func = <function call_runtest_hook.<locals>.<lambda> at 0x1112f49d8>, when = 'call'
treat_keyboard_interrupt_as_exception = False
def __init__(self, func, when, treat_keyboard_interrupt_as_exception=False):
#: context of invocation: one of "setup", "call",
#: "teardown", "memocollect"
self.when = when
self.start = time()
try:
> self.result = func()
<my-pyenv>/lib/python3.7/site-packages/_pytest/runner.py:201:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> lambda: ihook(item=item, **kwds),
when=when,
treat_keyboard_interrupt_as_exception=item.config.getvalue("usepdb"),
)
<my-pyenv>/lib/python3.7/site-packages/_pytest/runner.py:183:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <_HookCaller 'pytest_runtest_call'>, args = (), kwargs = {'item': <DoctestItem 'somemodule.somefunction'>}, notincall = set()
def __call__(self, *args, **kwargs):
if args:
raise TypeError("hook calling supports only keyword arguments")
assert not self.is_historic()
if self.argnames:
notincall = set(self.argnames) - set(['__multicall__']) - set(
kwargs.keys())
if notincall:
warnings.warn(
"Argument(s) {} which are declared in the hookspec "
"can not be found in this hook call"
.format(tuple(notincall)),
stacklevel=2,
)
> return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs)
<my-pyenv>/lib/python3.7/site-packages/pluggy/hooks.py:258:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <_pytest.config.PytestPluginManager object at 0x1034317b8>, hook = <_HookCaller 'pytest_runtest_call'>
methods = [<HookImpl plugin_name='runner', plugin=<module '_pytest.runner' from '<my-pyenv......t 0x103d4f4e0>>, <HookImpl plugin_name='logging-plugin', plugin=<_pytest.logging.LoggingPlugin object at 0x10e8f9860>>]
kwargs = {'item': <DoctestItem 'somemodule.somefunction'>}
def _hookexec(self, hook, methods, kwargs):
# called from all hookcaller instances.
# enable_tracing will set its own wrapping function at self._inner_hookexec
> return self._inner_hookexec(hook, methods, kwargs)
<my-pyenv>/lib/python3.7/site-packages/pluggy/manager.py:67:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
hook = <_HookCaller 'pytest_runtest_call'>
methods = [<HookImpl plugin_name='runner', plugin=<module '_pytest.runner' from '<my-pyenv......t 0x103d4f4e0>>, <HookImpl plugin_name='logging-plugin', plugin=<_pytest.logging.LoggingPlugin object at 0x10e8f9860>>]
kwargs = {'item': <DoctestItem 'somemodule.somefunction'>}
self._inner_hookexec = lambda hook, methods, kwargs: \
hook.multicall(
methods, kwargs,
> firstresult=hook.spec_opts.get('firstresult'),
)
<my-pyenv>/lib/python3.7/site-packages/pluggy/manager.py:61:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
hook_impls = [<HookImpl plugin_name='runner', plugin=<module '_pytest.runner' from '<my-pyenv......t 0x103d4f4e0>>, <HookImpl plugin_name='logging-plugin', plugin=<_pytest.logging.LoggingPlugin object at 0x10e8f9860>>]
caller_kwargs = {'item': <DoctestItem 'somemodule.somefunction'>}, firstresult = False
def _multicall(hook_impls, caller_kwargs, firstresult=False):
"""Execute a call into multiple python functions/methods and return the
result(s).
``caller_kwargs`` comes from _HookCaller.__call__().
"""
__tracebackhide__ = True
results = []
excinfo = None
try: # run impl and wrapper setup functions in a loop
teardowns = []
try:
for hook_impl in reversed(hook_impls):
try:
args = [caller_kwargs[argname] for argname in hook_impl.argnames]
except KeyError:
for argname in hook_impl.argnames:
if argname not in caller_kwargs:
raise HookCallError(
"hook call must provide argument %r" % (argname,))
if hook_impl.hookwrapper:
try:
gen = hook_impl.function(*args)
next(gen) # first yield
teardowns.append(gen)
except StopIteration:
_raise_wrapfail(gen, "did not yield")
else:
res = hook_impl.function(*args)
if res is not None:
results.append(res)
if firstresult: # halt further impl calls
break
except BaseException:
excinfo = sys.exc_info()
finally:
if firstresult: # first result hooks return a single value
outcome = _Result(results[0] if results else None, excinfo)
else:
outcome = _Result(results, excinfo)
# run all wrapper post-yield blocks
for gen in reversed(teardowns):
try:
gen.send(outcome)
_raise_wrapfail(gen, "has second yield")
except StopIteration:
pass
> return outcome.get_result()
<my-pyenv>/lib/python3.7/site-packages/pluggy/callers.py:201:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <pluggy.callers._Result object at 0x11116efd0>
def get_result(self):
"""Get the result(s) for this hook call.
If the hook was marked as a ``firstresult`` only a single value
will be returned otherwise a list of results.
"""
__tracebackhide__ = True
if self._excinfo is None:
return self._result
else:
ex = self._excinfo
if _py3:
> raise ex[1].with_traceback(ex[2])
<my-pyenv>/lib/python3.7/site-packages/pluggy/callers.py:76:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
hook_impls = [<HookImpl plugin_name='runner', plugin=<module '_pytest.runner' from '<my-pyenv......t 0x103d4f4e0>>, <HookImpl plugin_name='logging-plugin', plugin=<_pytest.logging.LoggingPlugin object at 0x10e8f9860>>]
caller_kwargs = {'item': <DoctestItem 'somemodule.somefunction'>}, firstresult = False
def _multicall(hook_impls, caller_kwargs, firstresult=False):
"""Execute a call into multiple python functions/methods and return the
result(s).
``caller_kwargs`` comes from _HookCaller.__call__().
"""
__tracebackhide__ = True
results = []
excinfo = None
try: # run impl and wrapper setup functions in a loop
teardowns = []
try:
for hook_impl in reversed(hook_impls):
try:
args = [caller_kwargs[argname] for argname in hook_impl.argnames]
except KeyError:
for argname in hook_impl.argnames:
if argname not in caller_kwargs:
raise HookCallError(
"hook call must provide argument %r" % (argname,))
if hook_impl.hookwrapper:
try:
gen = hook_impl.function(*args)
next(gen) # first yield
teardowns.append(gen)
except StopIteration:
_raise_wrapfail(gen, "did not yield")
else:
> res = hook_impl.function(*args)
<my-pyenv>/lib/python3.7/site-packages/pluggy/callers.py:180:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
item = <DoctestItem 'somemodule.somefunction'>
def pytest_runtest_call(item):
_update_current_test_var(item, "call")
sys.last_type, sys.last_value, sys.last_traceback = (None, None, None)
try:
> item.runtest()
<my-pyenv>/lib/python3.7/site-packages/_pytest/runner.py:111:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <DoctestItem 'somemodule.somefunction'>
def runtest(self):
_check_all_skipped(self.dtest)
> self._disable_output_capturing_for_darwin()
<my-pyenv>/lib/python3.7/site-packages/_pytest/doctest.py:192:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <DoctestItem 'somemodule.somefunction'>
def _disable_output_capturing_for_darwin(self):
"""
Disable output capturing. Otherwise, stdout is lost to doctest (#985)
"""
if platform.system() != "Darwin":
return
capman = self.config.pluginmanager.getplugin("capturemanager")
if capman:
> out, err = capman.suspend_global_capture(in_=True)
E TypeError: cannot unpack non-iterable NoneType object
<my-pyenv>/lib/python3.7/site-packages/_pytest/doctest.py:206: TypeError
```
- [x] `pip list` of the virtual environment you are using
```
...
mypy 0.620
pytest 3.7.3
pytest-cov 2.5.1
pytest-django 3.4.2
tox 3.2.1
...
```
- [x] pytest and operating system versions
`pytest v3.7.3` and
```
$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.13.6
BuildVersion: 17G65
```
- [ ] Minimal example if possible
| 1.0 | doctests regression with v3.7.3 on OS-X - - [x] Include a detailed description of the bug or suggestion
After upgrading to v3.7.3, all doctests started failing with the exception:
```
<my-pyenv>/lib/python3.7/site-packages/_pytest/doctest.py:206: TypeError: cannot unpack non-iterable NoneType object
```
Everything is OK with v3.7.2.
Slightly longer traceback (For the record, looking into the stacktrace, I see some references to "darwin"-specific functions):
```
___________________________________________________________________ [doctest] xxx ___________________________________________________________________
self = <CallInfo when='call' exception: cannot unpack non-iterable NoneType object>, func = <function call_runtest_hook.<locals>.<lambda> at 0x1112f49d8>, when = 'call'
treat_keyboard_interrupt_as_exception = False
def __init__(self, func, when, treat_keyboard_interrupt_as_exception=False):
#: context of invocation: one of "setup", "call",
#: "teardown", "memocollect"
self.when = when
self.start = time()
try:
> self.result = func()
<my-pyenv>/lib/python3.7/site-packages/_pytest/runner.py:201:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> lambda: ihook(item=item, **kwds),
when=when,
treat_keyboard_interrupt_as_exception=item.config.getvalue("usepdb"),
)
<my-pyenv>/lib/python3.7/site-packages/_pytest/runner.py:183:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <_HookCaller 'pytest_runtest_call'>, args = (), kwargs = {'item': <DoctestItem 'somemodule.somefunction'>}, notincall = set()
def __call__(self, *args, **kwargs):
if args:
raise TypeError("hook calling supports only keyword arguments")
assert not self.is_historic()
if self.argnames:
notincall = set(self.argnames) - set(['__multicall__']) - set(
kwargs.keys())
if notincall:
warnings.warn(
"Argument(s) {} which are declared in the hookspec "
"can not be found in this hook call"
.format(tuple(notincall)),
stacklevel=2,
)
> return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs)
<my-pyenv>/lib/python3.7/site-packages/pluggy/hooks.py:258:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <_pytest.config.PytestPluginManager object at 0x1034317b8>, hook = <_HookCaller 'pytest_runtest_call'>
methods = [<HookImpl plugin_name='runner', plugin=<module '_pytest.runner' from '<my-pyenv......t 0x103d4f4e0>>, <HookImpl plugin_name='logging-plugin', plugin=<_pytest.logging.LoggingPlugin object at 0x10e8f9860>>]
kwargs = {'item': <DoctestItem 'somemodule.somefunction'>}
def _hookexec(self, hook, methods, kwargs):
# called from all hookcaller instances.
# enable_tracing will set its own wrapping function at self._inner_hookexec
> return self._inner_hookexec(hook, methods, kwargs)
<my-pyenv>/lib/python3.7/site-packages/pluggy/manager.py:67:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
hook = <_HookCaller 'pytest_runtest_call'>
methods = [<HookImpl plugin_name='runner', plugin=<module '_pytest.runner' from '<my-pyenv......t 0x103d4f4e0>>, <HookImpl plugin_name='logging-plugin', plugin=<_pytest.logging.LoggingPlugin object at 0x10e8f9860>>]
kwargs = {'item': <DoctestItem 'somemodule.somefunction'>}
self._inner_hookexec = lambda hook, methods, kwargs: \
hook.multicall(
methods, kwargs,
> firstresult=hook.spec_opts.get('firstresult'),
)
<my-pyenv>/lib/python3.7/site-packages/pluggy/manager.py:61:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
hook_impls = [<HookImpl plugin_name='runner', plugin=<module '_pytest.runner' from '<my-pyenv......t 0x103d4f4e0>>, <HookImpl plugin_name='logging-plugin', plugin=<_pytest.logging.LoggingPlugin object at 0x10e8f9860>>]
caller_kwargs = {'item': <DoctestItem 'somemodule.somefunction'>}, firstresult = False
def _multicall(hook_impls, caller_kwargs, firstresult=False):
"""Execute a call into multiple python functions/methods and return the
result(s).
``caller_kwargs`` comes from _HookCaller.__call__().
"""
__tracebackhide__ = True
results = []
excinfo = None
try: # run impl and wrapper setup functions in a loop
teardowns = []
try:
for hook_impl in reversed(hook_impls):
try:
args = [caller_kwargs[argname] for argname in hook_impl.argnames]
except KeyError:
for argname in hook_impl.argnames:
if argname not in caller_kwargs:
raise HookCallError(
"hook call must provide argument %r" % (argname,))
if hook_impl.hookwrapper:
try:
gen = hook_impl.function(*args)
next(gen) # first yield
teardowns.append(gen)
except StopIteration:
_raise_wrapfail(gen, "did not yield")
else:
res = hook_impl.function(*args)
if res is not None:
results.append(res)
if firstresult: # halt further impl calls
break
except BaseException:
excinfo = sys.exc_info()
finally:
if firstresult: # first result hooks return a single value
outcome = _Result(results[0] if results else None, excinfo)
else:
outcome = _Result(results, excinfo)
# run all wrapper post-yield blocks
for gen in reversed(teardowns):
try:
gen.send(outcome)
_raise_wrapfail(gen, "has second yield")
except StopIteration:
pass
> return outcome.get_result()
<my-pyenv>/lib/python3.7/site-packages/pluggy/callers.py:201:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <pluggy.callers._Result object at 0x11116efd0>
def get_result(self):
"""Get the result(s) for this hook call.
If the hook was marked as a ``firstresult`` only a single value
will be returned otherwise a list of results.
"""
__tracebackhide__ = True
if self._excinfo is None:
return self._result
else:
ex = self._excinfo
if _py3:
> raise ex[1].with_traceback(ex[2])
<my-pyenv>/lib/python3.7/site-packages/pluggy/callers.py:76:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
hook_impls = [<HookImpl plugin_name='runner', plugin=<module '_pytest.runner' from '<my-pyenv......t 0x103d4f4e0>>, <HookImpl plugin_name='logging-plugin', plugin=<_pytest.logging.LoggingPlugin object at 0x10e8f9860>>]
caller_kwargs = {'item': <DoctestItem 'somemodule.somefunction'>}, firstresult = False
def _multicall(hook_impls, caller_kwargs, firstresult=False):
"""Execute a call into multiple python functions/methods and return the
result(s).
``caller_kwargs`` comes from _HookCaller.__call__().
"""
__tracebackhide__ = True
results = []
excinfo = None
try: # run impl and wrapper setup functions in a loop
teardowns = []
try:
for hook_impl in reversed(hook_impls):
try:
args = [caller_kwargs[argname] for argname in hook_impl.argnames]
except KeyError:
for argname in hook_impl.argnames:
if argname not in caller_kwargs:
raise HookCallError(
"hook call must provide argument %r" % (argname,))
if hook_impl.hookwrapper:
try:
gen = hook_impl.function(*args)
next(gen) # first yield
teardowns.append(gen)
except StopIteration:
_raise_wrapfail(gen, "did not yield")
else:
> res = hook_impl.function(*args)
<my-pyenv>/lib/python3.7/site-packages/pluggy/callers.py:180:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
item = <DoctestItem 'somemodule.somefunction'>
def pytest_runtest_call(item):
_update_current_test_var(item, "call")
sys.last_type, sys.last_value, sys.last_traceback = (None, None, None)
try:
> item.runtest()
<my-pyenv>/lib/python3.7/site-packages/_pytest/runner.py:111:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <DoctestItem 'somemodule.somefunction'>
def runtest(self):
_check_all_skipped(self.dtest)
> self._disable_output_capturing_for_darwin()
<my-pyenv>/lib/python3.7/site-packages/_pytest/doctest.py:192:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <DoctestItem 'somemodule.somefunction'>
def _disable_output_capturing_for_darwin(self):
"""
Disable output capturing. Otherwise, stdout is lost to doctest (#985)
"""
if platform.system() != "Darwin":
return
capman = self.config.pluginmanager.getplugin("capturemanager")
if capman:
> out, err = capman.suspend_global_capture(in_=True)
E TypeError: cannot unpack non-iterable NoneType object
<my-pyenv>/lib/python3.7/site-packages/_pytest/doctest.py:206: TypeError
```
- [x] `pip list` of the virtual environment you are using
```
...
mypy 0.620
pytest 3.7.3
pytest-cov 2.5.1
pytest-django 3.4.2
tox 3.2.1
...
```
- [x] pytest and operating system versions
`pytest v3.7.3` and
```
$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.13.6
BuildVersion: 17G65
```
- [ ] Minimal example if possible
| test | doctests regression with on os x include a detailed description of the bug or suggestion after upgrading to all doctests started failing with the exception lib site packages pytest doctest py typeerror cannot unpack non iterable nonetype object everything is ok with slightly longer traceback for the record looking into the stacktrace i see some references to darwin specific functions xxx self func at when call treat keyboard interrupt as exception false def init self func when treat keyboard interrupt as exception false context of invocation one of setup call teardown memocollect self when when self start time try self result func lib site packages pytest runner py lambda ihook item item kwds when when treat keyboard interrupt as exception item config getvalue usepdb lib site packages pytest runner py self args kwargs item notincall set def call self args kwargs if args raise typeerror hook calling supports only keyword arguments assert not self is historic if self argnames notincall set self argnames set set kwargs keys if notincall warnings warn argument s which are declared in the hookspec can not be found in this hook call format tuple notincall stacklevel return self hookexec self self nonwrappers self wrappers kwargs lib site packages pluggy hooks py self hook methods kwargs item def hookexec self hook methods kwargs called from all hookcaller instances enable tracing will set its own wrapping function at self inner hookexec return self inner hookexec hook methods kwargs lib site packages pluggy manager py hook methods kwargs item self inner hookexec lambda hook methods kwargs hook multicall methods kwargs firstresult hook spec opts get firstresult lib site packages pluggy manager py hook impls caller kwargs item firstresult false def multicall hook impls caller kwargs firstresult false execute a call into multiple python functions methods and return the result s caller kwargs comes from hookcaller call tracebackhide true results excinfo none try run impl and wrapper setup functions in a loop teardowns try for hook impl in reversed hook impls try args for argname in hook impl argnames except keyerror for argname in hook impl argnames if argname not in caller kwargs raise hookcallerror hook call must provide argument r argname if hook impl hookwrapper try gen hook impl function args next gen first yield teardowns append gen except stopiteration raise wrapfail gen did not yield else res hook impl function args if res is not none results append res if firstresult halt further impl calls break except baseexception excinfo sys exc info finally if firstresult first result hooks return a single value outcome result results if results else none excinfo else outcome result results excinfo run all wrapper post yield blocks for gen in reversed teardowns try gen send outcome raise wrapfail gen has second yield except stopiteration pass return outcome get result lib site packages pluggy callers py self def get result self get the result s for this hook call if the hook was marked as a firstresult only a single value will be returned otherwise a list of results tracebackhide true if self excinfo is none return self result else ex self excinfo if raise ex with traceback ex lib site packages pluggy callers py hook impls caller kwargs item firstresult false def multicall hook impls caller kwargs firstresult false execute a call into multiple python functions methods and return the result s caller kwargs comes from hookcaller call tracebackhide true results excinfo none try run impl and wrapper setup functions in a loop teardowns try for hook impl in reversed hook impls try args for argname in hook impl argnames except keyerror for argname in hook impl argnames if argname not in caller kwargs raise hookcallerror hook call must provide argument r argname if hook impl hookwrapper try gen hook impl function args next gen first yield teardowns append gen except stopiteration raise wrapfail gen did not yield else res hook impl function args lib site packages pluggy callers py item def pytest runtest call item update current test var item call sys last type sys last value sys last traceback none none none try item runtest lib site packages pytest runner py self def runtest self check all skipped self dtest self disable output capturing for darwin lib site packages pytest doctest py self def disable output capturing for darwin self disable output capturing otherwise stdout is lost to doctest if platform system darwin return capman self config pluginmanager getplugin capturemanager if capman out err capman suspend global capture in true e typeerror cannot unpack non iterable nonetype object lib site packages pytest doctest py typeerror pip list of the virtual environment you are using mypy pytest pytest cov pytest django tox pytest and operating system versions pytest and sw vers productname mac os x productversion buildversion minimal example if possible | 1 |
164,183 | 12,792,367,195 | IssuesEvent | 2020-07-02 01:11:45 | microsoft/azure-tools-for-java | https://api.github.com/repos/microsoft/azure-tools-for-java | closed | Null issue for Docker Hosts | IntelliJ Internal Test P3 bug docker-host stacktrace transfter | In most cases, both global and mooncake
1. Right click a project and click Publish as Docker Container
2. New a docker host ,e.g. gsspringboot52881 (you can use the default configuration)
3. After published, the new host will display in the Azure explorer, right click gsspringboot52881 and choose any option(e.g. refresh), error occurs unless you refresh **Docker Hosts** node.
**Error Log:**
```
null
java.lang.NullPointerException
at com.microsoft.tooling.msservices.serviceexplorer.azure.docker.DockerHostNode.refreshItems(DockerHostNode.java:88)
at com.microsoft.tooling.msservices.serviceexplorer.RefreshableNode.refreshItems(RefreshableNode.java:92)
at com.microsoft.tooling.msservices.serviceexplorer.RefreshableNode$2.run(RefreshableNode.java:130)
at com.microsoft.intellij.helpers.IDEHelperImpl$2$1.run(IDEHelperImpl.java:157)
at com.intellij.openapi.progress.impl.CoreProgressManager$TaskRunnable.run(CoreProgressManager.java:718)
at com.intellij.openapi.progress.impl.CoreProgressManager.a(CoreProgressManager.java:170)
at com.intellij.openapi.progress.impl.CoreProgressManager.a(CoreProgressManager.java:548)
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:493)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:94)
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:157)
at com.intellij.openapi.progress.impl.ProgressManagerImpl$2.run(ProgressManagerImpl.java:165)
at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:330)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
```
| 1.0 | Null issue for Docker Hosts - In most cases, both global and mooncake
1. Right click a project and click Publish as Docker Container
2. New a docker host ,e.g. gsspringboot52881 (you can use the default configuration)
3. After published, the new host will display in the Azure explorer, right click gsspringboot52881 and choose any option(e.g. refresh), error occurs unless you refresh **Docker Hosts** node.
**Error Log:**
```
null
java.lang.NullPointerException
at com.microsoft.tooling.msservices.serviceexplorer.azure.docker.DockerHostNode.refreshItems(DockerHostNode.java:88)
at com.microsoft.tooling.msservices.serviceexplorer.RefreshableNode.refreshItems(RefreshableNode.java:92)
at com.microsoft.tooling.msservices.serviceexplorer.RefreshableNode$2.run(RefreshableNode.java:130)
at com.microsoft.intellij.helpers.IDEHelperImpl$2$1.run(IDEHelperImpl.java:157)
at com.intellij.openapi.progress.impl.CoreProgressManager$TaskRunnable.run(CoreProgressManager.java:718)
at com.intellij.openapi.progress.impl.CoreProgressManager.a(CoreProgressManager.java:170)
at com.intellij.openapi.progress.impl.CoreProgressManager.a(CoreProgressManager.java:548)
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:493)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:94)
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:157)
at com.intellij.openapi.progress.impl.ProgressManagerImpl$2.run(ProgressManagerImpl.java:165)
at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:330)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
```
| test | null issue for docker hosts in most cases both global and mooncake right click a project and click publish as docker container new a docker host e g you can use the default configuration after published the new host will display in the azure explorer right click and choose any option e g refresh error occurs unless you refresh docker hosts node error log null java lang nullpointerexception at com microsoft tooling msservices serviceexplorer azure docker dockerhostnode refreshitems dockerhostnode java at com microsoft tooling msservices serviceexplorer refreshablenode refreshitems refreshablenode java at com microsoft tooling msservices serviceexplorer refreshablenode run refreshablenode java at com microsoft intellij helpers idehelperimpl run idehelperimpl java at com intellij openapi progress impl coreprogressmanager taskrunnable run coreprogressmanager java at com intellij openapi progress impl coreprogressmanager a coreprogressmanager java at com intellij openapi progress impl coreprogressmanager a coreprogressmanager java at com intellij openapi progress impl coreprogressmanager executeprocessunderprogress coreprogressmanager java at com intellij openapi progress impl progressmanagerimpl executeprocessunderprogress progressmanagerimpl java at com intellij openapi progress impl coreprogressmanager runprocess coreprogressmanager java at com intellij openapi progress impl progressmanagerimpl run progressmanagerimpl java at com intellij openapi application impl applicationimpl run applicationimpl java at java util concurrent executors runnableadapter call executors java 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 |
47,903 | 5,920,046,677 | IssuesEvent | 2017-05-22 19:16:00 | Microsoft/ChakraCore | https://api.github.com/repos/Microsoft/ChakraCore | opened | test/DebuggerCommon/attachdetach-delaycapture.js - background job thread fails | Test Bug | See `test/DebuggerCommon/rlexe.xml` test `attachdetach-delaycapture.js` comment:
`<!-- xplat-todo: enable back - investigate [background job thread fails] (Microsoft/ChakraCore#3012) -->`
| 1.0 | test/DebuggerCommon/attachdetach-delaycapture.js - background job thread fails - See `test/DebuggerCommon/rlexe.xml` test `attachdetach-delaycapture.js` comment:
`<!-- xplat-todo: enable back - investigate [background job thread fails] (Microsoft/ChakraCore#3012) -->`
| test | test debuggercommon attachdetach delaycapture js background job thread fails see test debuggercommon rlexe xml test attachdetach delaycapture js comment | 1 |
476,002 | 13,732,066,253 | IssuesEvent | 2020-10-05 03:23:48 | jabardigitalservice/pikobar-pelaporan-frontend | https://api.github.com/repos/jabardigitalservice/pikobar-pelaporan-frontend | reopened | Improvement Buat Laporan Kasus - 2 | priority high | ## Tambahan & Revisi :
### Form Identitas Pasien
- [ ] Asal Daerah dihapus aja, biarkan by default Jawa Barat
- [ ] Penginputan kriteria pasien & status pasien sebaiknya diinput diform informasi klinis
### Form Info Klinis
- [ ] Set mandatory Tanggal Update Status Pasien Terakhir
- [ ] Menambahkan label "Tanggal Update Status Pasien Terakhir"
### Form Pemeriksaan Penunjang
- [ ] Kondisional jenis pemeriksaan PCR, maka hasil pemeriksaanya ; Positif, Negatif, Invalid, Dalam Proses
- [ ] Kondisional jenis pemeriksaan Rapid, maka hasil pemeriksaanya ; Reaktif, Non Reaktif, Invalid
- [ ] Kondisional jenis pemeriksaan Radiologi, maka hasil pemeriksaanya ; Free Text
- [ ] Kondisional jenis pemeriksaan CT-Scan, maka hasil pemeriksaanya ; Free Text
- [ ] Kondisional jenis pemeriksaan TCM-SARS COV-2, maka hasil pemeriksaanya ; Positif, Negatif, Invalid, Dalam Proses
### Form Kontak Paparan
- [ ] Input "Dalam 14 hari sebelum sakit, apakah memiliki kontak erat dengan kasus suspek/probabel/konfirmasi COVID-19 lainnya ?" sebaiknya dihilangkan, karena sudah tercover **diform kontak terkait**
### List Kasus
- [ ] untuk CTA dilist kasus, sebaiknya hanya Lihat Detail, Cetak Laporan PE, Hapus Kasus
- [ ] Ketika klik lihat detail direct ke detail case (yg kotak2)
| 1.0 | Improvement Buat Laporan Kasus - 2 - ## Tambahan & Revisi :
### Form Identitas Pasien
- [ ] Asal Daerah dihapus aja, biarkan by default Jawa Barat
- [ ] Penginputan kriteria pasien & status pasien sebaiknya diinput diform informasi klinis
### Form Info Klinis
- [ ] Set mandatory Tanggal Update Status Pasien Terakhir
- [ ] Menambahkan label "Tanggal Update Status Pasien Terakhir"
### Form Pemeriksaan Penunjang
- [ ] Kondisional jenis pemeriksaan PCR, maka hasil pemeriksaanya ; Positif, Negatif, Invalid, Dalam Proses
- [ ] Kondisional jenis pemeriksaan Rapid, maka hasil pemeriksaanya ; Reaktif, Non Reaktif, Invalid
- [ ] Kondisional jenis pemeriksaan Radiologi, maka hasil pemeriksaanya ; Free Text
- [ ] Kondisional jenis pemeriksaan CT-Scan, maka hasil pemeriksaanya ; Free Text
- [ ] Kondisional jenis pemeriksaan TCM-SARS COV-2, maka hasil pemeriksaanya ; Positif, Negatif, Invalid, Dalam Proses
### Form Kontak Paparan
- [ ] Input "Dalam 14 hari sebelum sakit, apakah memiliki kontak erat dengan kasus suspek/probabel/konfirmasi COVID-19 lainnya ?" sebaiknya dihilangkan, karena sudah tercover **diform kontak terkait**
### List Kasus
- [ ] untuk CTA dilist kasus, sebaiknya hanya Lihat Detail, Cetak Laporan PE, Hapus Kasus
- [ ] Ketika klik lihat detail direct ke detail case (yg kotak2)
| non_test | improvement buat laporan kasus tambahan revisi form identitas pasien asal daerah dihapus aja biarkan by default jawa barat penginputan kriteria pasien status pasien sebaiknya diinput diform informasi klinis form info klinis set mandatory tanggal update status pasien terakhir menambahkan label tanggal update status pasien terakhir form pemeriksaan penunjang kondisional jenis pemeriksaan pcr maka hasil pemeriksaanya positif negatif invalid dalam proses kondisional jenis pemeriksaan rapid maka hasil pemeriksaanya reaktif non reaktif invalid kondisional jenis pemeriksaan radiologi maka hasil pemeriksaanya free text kondisional jenis pemeriksaan ct scan maka hasil pemeriksaanya free text kondisional jenis pemeriksaan tcm sars cov maka hasil pemeriksaanya positif negatif invalid dalam proses form kontak paparan input dalam hari sebelum sakit apakah memiliki kontak erat dengan kasus suspek probabel konfirmasi covid lainnya sebaiknya dihilangkan karena sudah tercover diform kontak terkait list kasus untuk cta dilist kasus sebaiknya hanya lihat detail cetak laporan pe hapus kasus ketika klik lihat detail direct ke detail case yg | 0 |
131,957 | 10,724,167,242 | IssuesEvent | 2019-10-27 23:55:44 | intellij-dlanguage/intellij-dlanguage | https://api.github.com/repos/intellij-dlanguage/intellij-dlanguage | closed | DUnit: Argument test is missing | Unit Tests bug | Before this line.
https://github.com/intellij-dlanguage/intellij-dlanguage/blob/5ec1640f4de9ceb81c5a7a0c7ee391095b5a52d7/src/main/java/io/github/intellij/dlanguage/unittest/DUnitTestRunProcessHandler.java#L219
there should be a line
```parametersList.addParametersString("test");```
With this change, d-unit is called correctly, successMatcher is succeeding but still no output is produced to UI. It seems the method testStdOut has no effect? | 1.0 | DUnit: Argument test is missing - Before this line.
https://github.com/intellij-dlanguage/intellij-dlanguage/blob/5ec1640f4de9ceb81c5a7a0c7ee391095b5a52d7/src/main/java/io/github/intellij/dlanguage/unittest/DUnitTestRunProcessHandler.java#L219
there should be a line
```parametersList.addParametersString("test");```
With this change, d-unit is called correctly, successMatcher is succeeding but still no output is produced to UI. It seems the method testStdOut has no effect? | test | dunit argument test is missing before this line there should be a line parameterslist addparametersstring test with this change d unit is called correctly successmatcher is succeeding but still no output is produced to ui it seems the method teststdout has no effect | 1 |
443,322 | 12,792,548,904 | IssuesEvent | 2020-07-02 01:40:39 | lardemua/atom | https://api.github.com/repos/lardemua/atom | closed | Merge general hand eye with calibrate | High Priority enhancement help wanted | Should do this to advance in the general approach.
Defined with @eupedrosa that the best way is to try to put in calibrate the stuff from hand eye, i.e. to use the calibrate as base. | 1.0 | Merge general hand eye with calibrate - Should do this to advance in the general approach.
Defined with @eupedrosa that the best way is to try to put in calibrate the stuff from hand eye, i.e. to use the calibrate as base. | non_test | merge general hand eye with calibrate should do this to advance in the general approach defined with eupedrosa that the best way is to try to put in calibrate the stuff from hand eye i e to use the calibrate as base | 0 |
93,346 | 8,410,153,223 | IssuesEvent | 2018-10-12 09:40:34 | Microsoft/vsts-tasks | https://api.github.com/repos/Microsoft/vsts-tasks | closed | Visual Studio Test task isn't generating code coverage for xUnit | Area: Test | ## Environment
VSTS - unable to provide account due to privacy restrictions
- Agent - Hosted or Private:
Private
10.0.14393
Azure Windows Server 2016 Datacenter
## Issue Description
**Task:** Visual Studio Test
**Issue:** code coverage file is empty after running xUnit tests
* Unit tests run, produce results (trx file) and publish them to VSTS without issue
* Code coverage file is created, but contains no data
* If I run the command the task is using from a command prompt the code coverage file is correctly populated with results
**Command Run By Task:** [command]"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe" @C:\VSTS\agents\dp-sitecore\agent-01\_work\_temp\0ec34221-a61d-11e8-8b14-df0fad7a6635.txt
**Contents of .txt file:**
"C:\VSTS\agents\dp-sitecore\agent-01\_work\2\s\Source\Feature\Authentication\tests\bin\Debug\Obfuscated.Authentication.Tests.dll"
_<... More binaries listed ...>_
"C:\VSTS\agents\dp-sitecore\agent-01\_work\2\s\Source\Foundation\Users\tests\bin\Debug\Obfuscated.Users.Tests.dll"
/EnableCodeCoverage
/InIsolation
/logger:"trx"
/TestAdapterPath:"C:\VSTS\agents\dp-sitecore\agent-01\_work\2\s\Source"
/diag:"C:\VSTS\agents\dp-sitecore\agent-01\_work\_temp\8d729900-a612-11e8-85fc-5f27b65d8975.txt"
The only difference I can see between my manual approach and the task is a reference to the Microsoft Coverage Collection Tool in the logs. When I run the command manually, this isn't mentioned at all.
Had to do an image as it has some odd characters preventing text copy/paste.
### Error logs
No errors reported. | 1.0 | Visual Studio Test task isn't generating code coverage for xUnit - ## Environment
VSTS - unable to provide account due to privacy restrictions
- Agent - Hosted or Private:
Private
10.0.14393
Azure Windows Server 2016 Datacenter
## Issue Description
**Task:** Visual Studio Test
**Issue:** code coverage file is empty after running xUnit tests
* Unit tests run, produce results (trx file) and publish them to VSTS without issue
* Code coverage file is created, but contains no data
* If I run the command the task is using from a command prompt the code coverage file is correctly populated with results
**Command Run By Task:** [command]"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe" @C:\VSTS\agents\dp-sitecore\agent-01\_work\_temp\0ec34221-a61d-11e8-8b14-df0fad7a6635.txt
**Contents of .txt file:**
"C:\VSTS\agents\dp-sitecore\agent-01\_work\2\s\Source\Feature\Authentication\tests\bin\Debug\Obfuscated.Authentication.Tests.dll"
_<... More binaries listed ...>_
"C:\VSTS\agents\dp-sitecore\agent-01\_work\2\s\Source\Foundation\Users\tests\bin\Debug\Obfuscated.Users.Tests.dll"
/EnableCodeCoverage
/InIsolation
/logger:"trx"
/TestAdapterPath:"C:\VSTS\agents\dp-sitecore\agent-01\_work\2\s\Source"
/diag:"C:\VSTS\agents\dp-sitecore\agent-01\_work\_temp\8d729900-a612-11e8-85fc-5f27b65d8975.txt"
The only difference I can see between my manual approach and the task is a reference to the Microsoft Coverage Collection Tool in the logs. When I run the command manually, this isn't mentioned at all.
Had to do an image as it has some odd characters preventing text copy/paste.
### Error logs
No errors reported. | test | visual studio test task isn t generating code coverage for xunit environment vsts unable to provide account due to privacy restrictions agent hosted or private private azure windows server datacenter issue description task visual studio test issue code coverage file is empty after running xunit tests unit tests run produce results trx file and publish them to vsts without issue code coverage file is created but contains no data if i run the command the task is using from a command prompt the code coverage file is correctly populated with results command run by task c program files microsoft visual studio enterprise ide commonextensions microsoft testwindow vstest console exe c vsts agents dp sitecore agent work temp txt contents of txt file c vsts agents dp sitecore agent work s source feature authentication tests bin debug obfuscated authentication tests dll c vsts agents dp sitecore agent work s source foundation users tests bin debug obfuscated users tests dll enablecodecoverage inisolation logger trx testadapterpath c vsts agents dp sitecore agent work s source diag c vsts agents dp sitecore agent work temp txt the only difference i can see between my manual approach and the task is a reference to the microsoft coverage collection tool in the logs when i run the command manually this isn t mentioned at all had to do an image as it has some odd characters preventing text copy paste error logs no errors reported | 1 |
44,830 | 5,655,102,831 | IssuesEvent | 2017-04-09 14:54:31 | youFrivolous/sw-project | https://api.github.com/repos/youFrivolous/sw-project | closed | 테스트를 위한 임의 파일 생성 코드 | test | 파일 전송을 하기에 앞서 매번 샘플 텍스트파일을 간단하게 생성하는 것은 무리라고 생각합니다.
파일의 전송량이나 중간의 데이터 손실 확인을 위해 1부터 N까지의 수를 줄당 가로폭 1000칸 내외로 출력합니다.
아래 코드를 이용해서 리디렉션이나 파이프라이닝으로 큰 파일을 생성하길 바랍니다.
**generator.cpp**
```cpp
#include <cstdio>
typedef long long lld;
lld lengthOfNumber(int n){
lld k = 0;
for(;n>0; n/=10) ++k;
return k;
}
lld toLld(char *a){
lld k = 0;
for(int i=0; a[i]; ++i) k = 10LL*k + a[i]-'0';
return k;
}
int main(int argc, char *argv[]){
lld n = toLld(argv[1]);
lld bytes = 0LL, linePush = 0LL;
fprintf(stderr, "[info] %lld개의 숫자 생성중..\n", n);
for(lld i=0; i<n; ++i){
fprintf(stdout, "%lld", i+1);
int len = lengthOfNumber(i+1);
bytes += len;
linePush += len;
// 1000자+alpha마다 줄내림한다. (오차범위: log_10(n))
if( linePush >= 1000 ) puts("+"), bytes += 2, linePush = 0;
}
fprintf(stderr, "[info] 예상 크기: %lld bytes\n\n", bytes);
return 0;
}
```
### 간단한 사용법
**Unix/Windows Shell**
```
$ g++ generator.cpp -o generator
$ ./generator 1000000 > SampleBinaryFile
[info] 1000000개의 숫자 생성중..
[info] 예상 크기: 5900652 bytes
```
터미널에서 위와 같이 실행한다면 소스 파일과 같은 경로에 적당한 크기의 파일이 생성되어 있을 것입니다. | 1.0 | 테스트를 위한 임의 파일 생성 코드 - 파일 전송을 하기에 앞서 매번 샘플 텍스트파일을 간단하게 생성하는 것은 무리라고 생각합니다.
파일의 전송량이나 중간의 데이터 손실 확인을 위해 1부터 N까지의 수를 줄당 가로폭 1000칸 내외로 출력합니다.
아래 코드를 이용해서 리디렉션이나 파이프라이닝으로 큰 파일을 생성하길 바랍니다.
**generator.cpp**
```cpp
#include <cstdio>
typedef long long lld;
lld lengthOfNumber(int n){
lld k = 0;
for(;n>0; n/=10) ++k;
return k;
}
lld toLld(char *a){
lld k = 0;
for(int i=0; a[i]; ++i) k = 10LL*k + a[i]-'0';
return k;
}
int main(int argc, char *argv[]){
lld n = toLld(argv[1]);
lld bytes = 0LL, linePush = 0LL;
fprintf(stderr, "[info] %lld개의 숫자 생성중..\n", n);
for(lld i=0; i<n; ++i){
fprintf(stdout, "%lld", i+1);
int len = lengthOfNumber(i+1);
bytes += len;
linePush += len;
// 1000자+alpha마다 줄내림한다. (오차범위: log_10(n))
if( linePush >= 1000 ) puts("+"), bytes += 2, linePush = 0;
}
fprintf(stderr, "[info] 예상 크기: %lld bytes\n\n", bytes);
return 0;
}
```
### 간단한 사용법
**Unix/Windows Shell**
```
$ g++ generator.cpp -o generator
$ ./generator 1000000 > SampleBinaryFile
[info] 1000000개의 숫자 생성중..
[info] 예상 크기: 5900652 bytes
```
터미널에서 위와 같이 실행한다면 소스 파일과 같은 경로에 적당한 크기의 파일이 생성되어 있을 것입니다. | test | 테스트를 위한 임의 파일 생성 코드 파일 전송을 하기에 앞서 매번 샘플 텍스트파일을 간단하게 생성하는 것은 무리라고 생각합니다 파일의 전송량이나 중간의 데이터 손실 확인을 위해 n까지의 수를 줄당 가로폭 내외로 출력합니다 아래 코드를 이용해서 리디렉션이나 파이프라이닝으로 큰 파일을 생성하길 바랍니다 generator cpp cpp include typedef long long lld lld lengthofnumber int n lld k for n n k return k lld tolld char a lld k for int i a i k k a return k int main int argc char argv lld n tolld argv lld bytes linepush fprintf stderr lld개의 숫자 생성중 n n for lld i i n i fprintf stdout lld i int len lengthofnumber i bytes len linepush len alpha마다 줄내림한다 오차범위 log n if linepush puts bytes linepush fprintf stderr 예상 크기 lld bytes n n bytes return 간단한 사용법 unix windows shell g generator cpp o generator generator samplebinaryfile 숫자 생성중 예상 크기 bytes 터미널에서 위와 같이 실행한다면 소스 파일과 같은 경로에 적당한 크기의 파일이 생성되어 있을 것입니다 | 1 |
6,298 | 2,832,348,204 | IssuesEvent | 2015-05-25 07:11:07 | AeroScripts/QuestieDev | https://api.github.com/repos/AeroScripts/QuestieDev | closed | tag icons in minimap of questie are always in the middle of minimap | bug test again | While i was doing quests in Tanaris, i find that all minimap icons of questie are always in the middle of minimap. When I click Toggle Questie, they disappeared and they can not show themself when i click Toggle again. | 1.0 | tag icons in minimap of questie are always in the middle of minimap - While i was doing quests in Tanaris, i find that all minimap icons of questie are always in the middle of minimap. When I click Toggle Questie, they disappeared and they can not show themself when i click Toggle again. | test | tag icons in minimap of questie are always in the middle of minimap while i was doing quests in tanaris i find that all minimap icons of questie are always in the middle of minimap when i click toggle questie they disappeared and they can not show themself when i click toggle again | 1 |
524,429 | 15,213,317,528 | IssuesEvent | 2021-02-17 11:37:29 | HSLdevcom/bultti | https://api.github.com/repos/HSLdevcom/bultti | closed | Refactor reports data types | Priority 1 enhancement | Reports need better datatypes. Currently the reports return the base entities, like Departures, but reports need to show different things. So the report datatype needs to only include the fields which are relevant to the report.
This also results in cleaner and more comprehensible code since we can get rid of GraphQL unions and messy typechecking among other things. | 1.0 | Refactor reports data types - Reports need better datatypes. Currently the reports return the base entities, like Departures, but reports need to show different things. So the report datatype needs to only include the fields which are relevant to the report.
This also results in cleaner and more comprehensible code since we can get rid of GraphQL unions and messy typechecking among other things. | non_test | refactor reports data types reports need better datatypes currently the reports return the base entities like departures but reports need to show different things so the report datatype needs to only include the fields which are relevant to the report this also results in cleaner and more comprehensible code since we can get rid of graphql unions and messy typechecking among other things | 0 |
35,412 | 4,974,638,991 | IssuesEvent | 2016-12-06 07:35:34 | lenatech/hws16_swt_server | https://api.github.com/repos/lenatech/hws16_swt_server | closed | If none recipe were found, must send none to android | bug test | need to do 2 things
1. Add exception
2. Check whether there really exist none recipe | 1.0 | If none recipe were found, must send none to android - need to do 2 things
1. Add exception
2. Check whether there really exist none recipe | test | if none recipe were found must send none to android need to do things add exception check whether there really exist none recipe | 1 |
125,913 | 10,369,317,897 | IssuesEvent | 2019-09-08 01:39:39 | zio/zio | https://api.github.com/repos/zio/zio | closed | ZIO Test: Improve Reporting of Property Based Testing Result | tests | This ticket is to improve reporting of property based testing results. A completed ticket will make two or possibly three improvements to existing test reporting:
- [ ] Report the shrunk random variables that caused the test to fail in addition to the failing test result. This will involve modifying the `checkStream` method in `CheckVariants.scala` so instead of just mapping the test over the random sample we keep a tuple of the sample and the test result and shrink those.
- [ ] Show the number of tests that passed before the failing test. This can also be done within the `checkStream` function, probably by using something like `zipWithIndex`.
A nice to have would be:
- [ ] Show the random seed for failing property based tests. This will be a little tricky because property based tests don't necessarily need to use a "random" variable (all the check methods are generic in `R` and could be done with an exhaustive sample). So we would need a way to at compile time identify which ones do and then access the `Random` to get the seed. | 1.0 | ZIO Test: Improve Reporting of Property Based Testing Result - This ticket is to improve reporting of property based testing results. A completed ticket will make two or possibly three improvements to existing test reporting:
- [ ] Report the shrunk random variables that caused the test to fail in addition to the failing test result. This will involve modifying the `checkStream` method in `CheckVariants.scala` so instead of just mapping the test over the random sample we keep a tuple of the sample and the test result and shrink those.
- [ ] Show the number of tests that passed before the failing test. This can also be done within the `checkStream` function, probably by using something like `zipWithIndex`.
A nice to have would be:
- [ ] Show the random seed for failing property based tests. This will be a little tricky because property based tests don't necessarily need to use a "random" variable (all the check methods are generic in `R` and could be done with an exhaustive sample). So we would need a way to at compile time identify which ones do and then access the `Random` to get the seed. | test | zio test improve reporting of property based testing result this ticket is to improve reporting of property based testing results a completed ticket will make two or possibly three improvements to existing test reporting report the shrunk random variables that caused the test to fail in addition to the failing test result this will involve modifying the checkstream method in checkvariants scala so instead of just mapping the test over the random sample we keep a tuple of the sample and the test result and shrink those show the number of tests that passed before the failing test this can also be done within the checkstream function probably by using something like zipwithindex a nice to have would be show the random seed for failing property based tests this will be a little tricky because property based tests don t necessarily need to use a random variable all the check methods are generic in r and could be done with an exhaustive sample so we would need a way to at compile time identify which ones do and then access the random to get the seed | 1 |
291,896 | 8,951,126,232 | IssuesEvent | 2019-01-25 13:01:22 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.eurobet.it - site is not usable | browser-firefox-mobile priority-normal | <!-- @browser: Firefox Mobile 65.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.1.0; Mobile; rv:65.0) Gecko/65.0 Firefox/65.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://www.eurobet.it/it/scommesse/#!
**Browser / Version**: Firefox Mobile 65.0
**Operating System**: Android 8.1.0
**Tested Another Browser**: No
**Problem type**: Site is not usable
**Description**: The site is unstable and don't work
**Steps to Reproduce**:
[](https://webcompat.com/uploads/2019/1/2b0b6402-4a9e-48c7-b00c-4243cc4c5b4f.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20190117232427</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: true</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: beta</li>
</ul>
<p>Console Messages:</p>
<pre>
[u'[console.log(Is AEM Mode: true) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:54378]', u'[console.log(IsLivePage: undefined) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:54410]', u'[console.debug(Reading session storage with key: sessionStorageCacheEurobet) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:877397]', u'[console.debug(Adding response to cache: https://www.eurobet.it/bonus-service/sport-schedule/services/bonus) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:876964]', u'[console.debug(Writing session storage with key: https://www.eurobet.it/bonus-service/sport-schedule/services/bonus) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:877268]', u'[console.debug(Reading session storage with key: sessionStorageCacheEurobet) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:877397]', u'[console.debug(Adding response to cache: https://www.eurobet.it/promo-proxy-service/internal-services/promotion-number) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:876964]', u'[console.debug(Writing session storage with key: https://www.eurobet.it/promo-proxy-service/internal-services/promotion-number) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:877268]', u'[console.debug(Reading session storage with key: sessionStorageCacheEurobet) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:877397]', u'[console.debug(Adding response to cache: https://www.eurobet.it/custom-account-service/internal-services/account-settings/9441520) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:876964]', u'[console.debug(Writing session storage with key: https://www.eurobet.it/custom-account-service/internal-services/account-settings/9441520) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:877268]', u'[console.debug(Reading session storage with key: sessionStorageCacheEurobet) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:877397]', u'[console.log(Auto save reducers: schedina,search,userData,barcodeDialogData,multiLiveFavorites,statsStreamData,gamingSearch,marcoPoloData) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:2219497]', u'[console.log(Looks like we are in prodution mode!) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:2220348]', u'[console.log(\nVersion Sport React: 1.21.9\n\n) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:2220400]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[console.debug(Init prematch data) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:2089036]', u'[console.debug(Cache hit for: https://www.eurobet.it/bonus-service/sport-schedule/services/bonus) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:875320]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[console.debug(Cache hit for: https://www.eurobet.it/custom-account-service/internal-services/account-settings/9441520) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:875320]', u'[console.debug(Gestisco chat autenticato...) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:2211400]', u'[console.debug(Adding response to cache: https://www.eurobet.it/detail-service/sport-schedule/services/bet/29031/788/3) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:876964]', u'[console.debug(Adding response to cache: https://www.eurobet.it/detail-service/sport-schedule/services/bet/29031/790/3) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:876964]', u'[console.warn(Promo non inizializzata (codPalinsesto-codAvvenimento-codiceMercato): 29031-790-3) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:1252709]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[console.log(All requests are now complete with the following codes:) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:2089142]', u'[console.log( sportListResponse.code: 1) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:2089213]', u'[console.log( bonusInfoResponse.code: 1) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:2089267]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[console.warn(AT:, [getOffer()], request failed, TypeError: e.targetDiv is null) https://assets.adobedtm.com/9614a692da9220a7e7e7467ebf7403b249c4fa8e/mbox-contents-de6ece6182e3a9b54339b27416a669d86fcc9980.js:10:5169]', u'[console.error(getOffer error: , e.targetDiv is null, unknown) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:2:43273]', u'[console.warn(AT:, [getOffer()], request failed, TypeError: e.targetDiv is null) https://assets.adobedtm.com/9614a692da9220a7e7e7467ebf7403b249c4fa8e/mbox-contents-de6ece6182e3a9b54339b27416a669d86fcc9980.js:10:5169]', u'[console.error(getOffer error: , e.targetDiv is null, unknown) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:2:43273]', u'[console.warn(AT:, [getOffer()], request failed, TypeError: e.targetDiv is null) https://assets.adobedtm.com/9614a692da9220a7e7e7467ebf7403b249c4fa8e/mbox-contents-de6ece6182e3a9b54339b27416a669d86fcc9980.js:10:5169]', u'[console.error(getOffer error: , e.targetDiv is null, unknown) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:2:43273]', u'[console.warn(AT:, [getOffer()], request failed, TypeError: e.targetDiv is null) https://assets.adobedtm.com/9614a692da9220a7e7e7467ebf7403b249c4fa8e/mbox-contents-de6ece6182e3a9b54339b27416a669d86fcc9980.js:10:5169]', u'[console.error(getOffer error: , e.targetDiv is null, unknown) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:2:43273]', u'[console.warn(No statsStream found!) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:2:6534]', u'[console.warn(No carouselAppBanner found!) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:2:158849]', u'[console.debug(Cache hit for: https://www.eurobet.it/promo-proxy-service/internal-services/promotion-number) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:875320]', u'[console.debug(retrieving live data) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:801735]', u'[console.debug(retrievied live data) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:801801]', u'[console.debug(Modify me for tracking analytics path: , /schedina/) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:346234]', u'[console.debug(componentWillUnmount) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:801886]', u'[console.debug(Clearing schedule) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:801624]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[console.debug(Modify me for tracking analytics path: , /schedina/) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:346234]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[console.debug(Bet deleted 3-1-0,0,0,0,0,0) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:261223]', u'[console.log(Removed event 28521-9702) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:265744]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[console.debug(Modify me for tracking analytics path: , /) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:346234]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[JavaScript Warning: " stata ignorata una chiamata preventDefault() su un evento di tipo touchmove da un listener registrato come passive." {file: "https://www.eurobet.it/etc/designs/eurobet/clientlib-all.min.js" line: 6900}]', u'[console.debug(retrieving live data) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:801735]', u'[console.debug(retrievied live data) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:801801]']
</pre>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.eurobet.it - site is not usable - <!-- @browser: Firefox Mobile 65.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.1.0; Mobile; rv:65.0) Gecko/65.0 Firefox/65.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://www.eurobet.it/it/scommesse/#!
**Browser / Version**: Firefox Mobile 65.0
**Operating System**: Android 8.1.0
**Tested Another Browser**: No
**Problem type**: Site is not usable
**Description**: The site is unstable and don't work
**Steps to Reproduce**:
[](https://webcompat.com/uploads/2019/1/2b0b6402-4a9e-48c7-b00c-4243cc4c5b4f.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20190117232427</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: true</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: beta</li>
</ul>
<p>Console Messages:</p>
<pre>
[u'[console.log(Is AEM Mode: true) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:54378]', u'[console.log(IsLivePage: undefined) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:54410]', u'[console.debug(Reading session storage with key: sessionStorageCacheEurobet) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:877397]', u'[console.debug(Adding response to cache: https://www.eurobet.it/bonus-service/sport-schedule/services/bonus) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:876964]', u'[console.debug(Writing session storage with key: https://www.eurobet.it/bonus-service/sport-schedule/services/bonus) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:877268]', u'[console.debug(Reading session storage with key: sessionStorageCacheEurobet) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:877397]', u'[console.debug(Adding response to cache: https://www.eurobet.it/promo-proxy-service/internal-services/promotion-number) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:876964]', u'[console.debug(Writing session storage with key: https://www.eurobet.it/promo-proxy-service/internal-services/promotion-number) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:877268]', u'[console.debug(Reading session storage with key: sessionStorageCacheEurobet) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:877397]', u'[console.debug(Adding response to cache: https://www.eurobet.it/custom-account-service/internal-services/account-settings/9441520) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:876964]', u'[console.debug(Writing session storage with key: https://www.eurobet.it/custom-account-service/internal-services/account-settings/9441520) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:877268]', u'[console.debug(Reading session storage with key: sessionStorageCacheEurobet) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:877397]', u'[console.log(Auto save reducers: schedina,search,userData,barcodeDialogData,multiLiveFavorites,statsStreamData,gamingSearch,marcoPoloData) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:2219497]', u'[console.log(Looks like we are in prodution mode!) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:2220348]', u'[console.log(\nVersion Sport React: 1.21.9\n\n) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:2220400]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[console.debug(Init prematch data) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:2089036]', u'[console.debug(Cache hit for: https://www.eurobet.it/bonus-service/sport-schedule/services/bonus) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:875320]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[console.debug(Cache hit for: https://www.eurobet.it/custom-account-service/internal-services/account-settings/9441520) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:875320]', u'[console.debug(Gestisco chat autenticato...) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:2211400]', u'[console.debug(Adding response to cache: https://www.eurobet.it/detail-service/sport-schedule/services/bet/29031/788/3) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:876964]', u'[console.debug(Adding response to cache: https://www.eurobet.it/detail-service/sport-schedule/services/bet/29031/790/3) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:876964]', u'[console.warn(Promo non inizializzata (codPalinsesto-codAvvenimento-codiceMercato): 29031-790-3) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:1252709]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[console.log(All requests are now complete with the following codes:) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:2089142]', u'[console.log( sportListResponse.code: 1) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:2089213]', u'[console.log( bonusInfoResponse.code: 1) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:2089267]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[console.warn(AT:, [getOffer()], request failed, TypeError: e.targetDiv is null) https://assets.adobedtm.com/9614a692da9220a7e7e7467ebf7403b249c4fa8e/mbox-contents-de6ece6182e3a9b54339b27416a669d86fcc9980.js:10:5169]', u'[console.error(getOffer error: , e.targetDiv is null, unknown) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:2:43273]', u'[console.warn(AT:, [getOffer()], request failed, TypeError: e.targetDiv is null) https://assets.adobedtm.com/9614a692da9220a7e7e7467ebf7403b249c4fa8e/mbox-contents-de6ece6182e3a9b54339b27416a669d86fcc9980.js:10:5169]', u'[console.error(getOffer error: , e.targetDiv is null, unknown) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:2:43273]', u'[console.warn(AT:, [getOffer()], request failed, TypeError: e.targetDiv is null) https://assets.adobedtm.com/9614a692da9220a7e7e7467ebf7403b249c4fa8e/mbox-contents-de6ece6182e3a9b54339b27416a669d86fcc9980.js:10:5169]', u'[console.error(getOffer error: , e.targetDiv is null, unknown) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:2:43273]', u'[console.warn(AT:, [getOffer()], request failed, TypeError: e.targetDiv is null) https://assets.adobedtm.com/9614a692da9220a7e7e7467ebf7403b249c4fa8e/mbox-contents-de6ece6182e3a9b54339b27416a669d86fcc9980.js:10:5169]', u'[console.error(getOffer error: , e.targetDiv is null, unknown) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:2:43273]', u'[console.warn(No statsStream found!) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:2:6534]', u'[console.warn(No carouselAppBanner found!) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:2:158849]', u'[console.debug(Cache hit for: https://www.eurobet.it/promo-proxy-service/internal-services/promotion-number) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:875320]', u'[console.debug(retrieving live data) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:801735]', u'[console.debug(retrievied live data) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:801801]', u'[console.debug(Modify me for tracking analytics path: , /schedina/) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:346234]', u'[console.debug(componentWillUnmount) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:801886]', u'[console.debug(Clearing schedule) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:801624]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[console.debug(Modify me for tracking analytics path: , /schedina/) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:346234]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[console.debug(Bet deleted 3-1-0,0,0,0,0,0) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:261223]', u'[console.log(Removed event 28521-9702) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:265744]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[console.debug(Modify me for tracking analytics path: , /) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:346234]', u'[console.debug(manageSticky) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-sport.min.js:1:2204]', u'[JavaScript Warning: " stata ignorata una chiamata preventDefault() su un evento di tipo touchmove da un listener registrato come passive." {file: "https://www.eurobet.it/etc/designs/eurobet/clientlib-all.min.js" line: 6900}]', u'[console.debug(retrieving live data) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:801735]', u'[console.debug(retrievied live data) https://www.eurobet.it/etc/designs/eurobet/clientlib-react-common.min.js:1:801801]']
</pre>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_test | site is not usable url browser version firefox mobile operating system android tested another browser no problem type site is not usable description the site is unstable and don t work steps to reproduce browser configuration mixed active content blocked false image mem shared true buildid tracking content blocked false gfx webrender blob images true hastouchscreen true mixed passive content blocked false gfx webrender enabled false gfx webrender all false channel beta console messages u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u request failed typeerror e targetdiv is null u u request failed typeerror e targetdiv is null u u request failed typeerror e targetdiv is null u u request failed typeerror e targetdiv is null u u u u u u u u u u u u u u u u u u u u from with ❤️ | 0 |
24,684 | 4,104,872,245 | IssuesEvent | 2016-06-05 17:20:10 | FreeCodeCamp/FreeCodeCamp | https://api.github.com/repos/FreeCodeCamp/FreeCodeCamp | closed | Remainder challenge needs numbers directly used in modulo | first-timers-only help wanted tests | Challenge [Finding a Remainder in JavaScript](https://www.freecodecamp.com/challenges/finding-a-remainder-in-javascript#?solution=%0A%2F%2F%20Only%20change%20code%20below%20this%20line%0Avar%20a%3D11%3B%0Avar%20b%3D3%3B%0Avar%20remainder%3B%0Avar%20remainder%3Da%20%25%20b%3B) has an issue.
User Agent is: <code>Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36</code>.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
```javascript
// Only change code below this line
var a=11;
var b=3;
var remainder;
var remainder=a % b;
```
| 1.0 | Remainder challenge needs numbers directly used in modulo - Challenge [Finding a Remainder in JavaScript](https://www.freecodecamp.com/challenges/finding-a-remainder-in-javascript#?solution=%0A%2F%2F%20Only%20change%20code%20below%20this%20line%0Avar%20a%3D11%3B%0Avar%20b%3D3%3B%0Avar%20remainder%3B%0Avar%20remainder%3Da%20%25%20b%3B) has an issue.
User Agent is: <code>Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36</code>.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
```javascript
// Only change code below this line
var a=11;
var b=3;
var remainder;
var remainder=a % b;
```
| test | remainder challenge needs numbers directly used in modulo challenge has an issue user agent is mozilla windows nt applewebkit khtml like gecko chrome safari please describe how to reproduce this issue and include links to screenshots if possible my code javascript only change code below this line var a var b var remainder var remainder a b | 1 |
74,813 | 7,445,898,327 | IssuesEvent | 2018-03-28 07:12:02 | prasadtalasila/IRCLogParser | https://api.github.com/repos/prasadtalasila/IRCLogParser | closed | functional test for data set | functional test | Create a functional test for verifying the data set summary feature. The relevant lines in the driver files are:
27,28,83 and 87 of [slack.py](https://github.com/prasadtalasila/IRCLogParser/blob/master/slack.py#L87)
| 1.0 | functional test for data set - Create a functional test for verifying the data set summary feature. The relevant lines in the driver files are:
27,28,83 and 87 of [slack.py](https://github.com/prasadtalasila/IRCLogParser/blob/master/slack.py#L87)
| test | functional test for data set create a functional test for verifying the data set summary feature the relevant lines in the driver files are and of | 1 |
274,759 | 23,863,768,735 | IssuesEvent | 2022-09-07 09:16:53 | input-output-hk/cardano-ledger | https://api.github.com/repos/input-output-hk/cardano-ledger | closed | Arbitrary instances with alternate, valid, serializations. | :detective: testing | The ledger is very careful to never re-serialize any data structures that will be hashed. This is important since there are multiple valid ways to encode many data structures in CBOR. Developers who use reuse some of the ledger code, however, are not always as aware of how important this is. In particular, sometimes projects will mix and match the ledger code and other third party serialization libraries, leading to confusion about why hashes do not match. See #2943 as an example.
[Section 3.9 of the CBOR RFC](https://datatracker.ietf.org/doc/html/rfc7049#section-3.9) describes the various choices allowed in CBOR (in the context of describing which choice to make if you want to be canonical).
The ledger itself, however, has to make specific choices about how to serialize, even though the deserializers are flexible.
In order to make it more transparent that some of the ledger serialization is arbitrary (using definite vs indefinite lists, etc), we can write our `Arbitrary` generators such that they vary these choices.
The structure that seems to lead to the most confusion seems to be `Datum`. We could address `Datum`s directly, or perhaps write a general way of "twiddling" all of our CBOR encodings. | 1.0 | Arbitrary instances with alternate, valid, serializations. - The ledger is very careful to never re-serialize any data structures that will be hashed. This is important since there are multiple valid ways to encode many data structures in CBOR. Developers who use reuse some of the ledger code, however, are not always as aware of how important this is. In particular, sometimes projects will mix and match the ledger code and other third party serialization libraries, leading to confusion about why hashes do not match. See #2943 as an example.
[Section 3.9 of the CBOR RFC](https://datatracker.ietf.org/doc/html/rfc7049#section-3.9) describes the various choices allowed in CBOR (in the context of describing which choice to make if you want to be canonical).
The ledger itself, however, has to make specific choices about how to serialize, even though the deserializers are flexible.
In order to make it more transparent that some of the ledger serialization is arbitrary (using definite vs indefinite lists, etc), we can write our `Arbitrary` generators such that they vary these choices.
The structure that seems to lead to the most confusion seems to be `Datum`. We could address `Datum`s directly, or perhaps write a general way of "twiddling" all of our CBOR encodings. | test | arbitrary instances with alternate valid serializations the ledger is very careful to never re serialize any data structures that will be hashed this is important since there are multiple valid ways to encode many data structures in cbor developers who use reuse some of the ledger code however are not always as aware of how important this is in particular sometimes projects will mix and match the ledger code and other third party serialization libraries leading to confusion about why hashes do not match see as an example describes the various choices allowed in cbor in the context of describing which choice to make if you want to be canonical the ledger itself however has to make specific choices about how to serialize even though the deserializers are flexible in order to make it more transparent that some of the ledger serialization is arbitrary using definite vs indefinite lists etc we can write our arbitrary generators such that they vary these choices the structure that seems to lead to the most confusion seems to be datum we could address datum s directly or perhaps write a general way of twiddling all of our cbor encodings | 1 |
81,642 | 10,163,202,574 | IssuesEvent | 2019-08-07 08:46:55 | nodunayo/speakerline | https://api.github.com/repos/nodunayo/speakerline | closed | You can add and edit tags up to three tags on a proposal | design feature help wanted | We need a better way for users to find proposals that interest them. Therefore, I propose adding the ability to add tags to a proposal upon creating it as well as the ability to edit them.
I also want to limit tags to 3 so that tags are more useful for organisation and finding purposes. It's also a useful tool for speakers struggling to choose three tags to wonder whether their proposal covers too much scope!
In a separate chunk of work, we can add the ability to filter proposals down by tags. | 1.0 | You can add and edit tags up to three tags on a proposal - We need a better way for users to find proposals that interest them. Therefore, I propose adding the ability to add tags to a proposal upon creating it as well as the ability to edit them.
I also want to limit tags to 3 so that tags are more useful for organisation and finding purposes. It's also a useful tool for speakers struggling to choose three tags to wonder whether their proposal covers too much scope!
In a separate chunk of work, we can add the ability to filter proposals down by tags. | non_test | you can add and edit tags up to three tags on a proposal we need a better way for users to find proposals that interest them therefore i propose adding the ability to add tags to a proposal upon creating it as well as the ability to edit them i also want to limit tags to so that tags are more useful for organisation and finding purposes it s also a useful tool for speakers struggling to choose three tags to wonder whether their proposal covers too much scope in a separate chunk of work we can add the ability to filter proposals down by tags | 0 |
62,469 | 6,797,513,755 | IssuesEvent | 2017-11-01 23:19:04 | daviddarnes/alembic | https://api.github.com/repos/daviddarnes/alembic | closed | Switch Gemfile back to gemspec reference | enhancement needs tests | Seems as though all other themes do this, and it makes sense as not doing so could cause disparity between gems, use the following in the `Gemfile`:
``` ruby
source "https://rubygems.org"
gemspec
``` | 1.0 | Switch Gemfile back to gemspec reference - Seems as though all other themes do this, and it makes sense as not doing so could cause disparity between gems, use the following in the `Gemfile`:
``` ruby
source "https://rubygems.org"
gemspec
``` | test | switch gemfile back to gemspec reference seems as though all other themes do this and it makes sense as not doing so could cause disparity between gems use the following in the gemfile ruby source gemspec | 1 |
337,179 | 30,243,286,046 | IssuesEvent | 2023-07-06 14:47:56 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | opened | Fix jax_lax_operators.test_jax_convert_element_type | JAX Frontend Sub Task Failing Test | | | |
|---|---|
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5476583278"><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5476583278"><img src=https://img.shields.io/badge/-failure-red></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5476583278"><img src=https://img.shields.io/badge/-failure-red></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5476583278"><img src=https://img.shields.io/badge/-failure-red></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5476583278"><img src=https://img.shields.io/badge/-failure-red></a>
| 1.0 | Fix jax_lax_operators.test_jax_convert_element_type - | | |
|---|---|
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5476583278"><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5476583278"><img src=https://img.shields.io/badge/-failure-red></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5476583278"><img src=https://img.shields.io/badge/-failure-red></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5476583278"><img src=https://img.shields.io/badge/-failure-red></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5476583278"><img src=https://img.shields.io/badge/-failure-red></a>
| test | fix jax lax operators test jax convert element type torch a href src numpy a href src tensorflow a href src jax a href src paddle a href src | 1 |
65,101 | 6,948,665,066 | IssuesEvent | 2017-12-06 01:35:05 | QubesOS/updates-status | https://api.github.com/repos/QubesOS/updates-status | closed | core-admin v4.0.13 (r4.0) | r4.0-dom0-testing | Update of core-admin to v4.0.13 for Qubes r4.0, see comments below for details.
Built from: https://github.com/QubesOS/qubes-core-admin/commit/6f1cedff800fccc6cdfffbab1b363dfc419d699c
[Changes since previous version](https://github.com/QubesOS/qubes-core-admin/compare/v4.0.12...v4.0.13):
QubesOS/qubes-core-admin@6f1cedf version 4.0.13
QubesOS/qubes-core-admin@b41c118 Fix typo in volume import end handler
Referenced issues:
If you're release manager, you can issue GPG-inline signed command:
* `Upload core-admin 6f1cedff800fccc6cdfffbab1b363dfc419d699c r4.0 current repo` (available 7 days from now)
* `Upload core-admin 6f1cedff800fccc6cdfffbab1b363dfc419d699c r4.0 current (dists) repo`, you can choose subset of distributions, like `vm-fc24 vm-fc25` (available 7 days from now)
* `Upload core-admin 6f1cedff800fccc6cdfffbab1b363dfc419d699c r4.0 security-testing repo`
Above commands will work only if packages in current-testing repository were built from given commit (i.e. no new version superseded it).
| 1.0 | core-admin v4.0.13 (r4.0) - Update of core-admin to v4.0.13 for Qubes r4.0, see comments below for details.
Built from: https://github.com/QubesOS/qubes-core-admin/commit/6f1cedff800fccc6cdfffbab1b363dfc419d699c
[Changes since previous version](https://github.com/QubesOS/qubes-core-admin/compare/v4.0.12...v4.0.13):
QubesOS/qubes-core-admin@6f1cedf version 4.0.13
QubesOS/qubes-core-admin@b41c118 Fix typo in volume import end handler
Referenced issues:
If you're release manager, you can issue GPG-inline signed command:
* `Upload core-admin 6f1cedff800fccc6cdfffbab1b363dfc419d699c r4.0 current repo` (available 7 days from now)
* `Upload core-admin 6f1cedff800fccc6cdfffbab1b363dfc419d699c r4.0 current (dists) repo`, you can choose subset of distributions, like `vm-fc24 vm-fc25` (available 7 days from now)
* `Upload core-admin 6f1cedff800fccc6cdfffbab1b363dfc419d699c r4.0 security-testing repo`
Above commands will work only if packages in current-testing repository were built from given commit (i.e. no new version superseded it).
| test | core admin update of core admin to for qubes see comments below for details built from qubesos qubes core admin version qubesos qubes core admin fix typo in volume import end handler referenced issues if you re release manager you can issue gpg inline signed command upload core admin current repo available days from now upload core admin current dists repo you can choose subset of distributions like vm vm available days from now upload core admin security testing repo above commands will work only if packages in current testing repository were built from given commit i e no new version superseded it | 1 |
786,616 | 27,660,520,775 | IssuesEvent | 2023-03-12 13:18:21 | renovatebot/renovate | https://api.github.com/repos/renovatebot/renovate | closed | Bitbucket Cloud: initialize repos with development branch | type:feature priority-3-medium platform:bitbucket status:in-progress | ### What would you like Renovate to be able to do?
Use development branch to initialize Bitbucket Cloud repositories.
Bitbucket Cloud supports a [variety of branching models](https://support.atlassian.com/bitbucket-cloud/docs/branch-a-repository/#The-branching-model), which are configured at the repository level.
Two of importance to this feature request are
- **Development branch** - this is where new feature branches are targeted, commonly `main` or `master` for trunk-based development and `develop` for git-flow. This is configured under _Repository Details >> Worklow >> Branching Model_
- **Main branch** - this is configured under _Repository Details >> Advanced >> Main branch_. Commonly this is left set to `main` or `master` regardless of trunk-based, git-flow or other workflow
At present, when Bitbucket Cloud repositories are initialized, it sets the defaultBranch to be the repositories **main branch** instead of the preferred **development branch**. This means that for repositories using non trunk-based workflows, Renovate PRs will be targeting the wrong branch for their workflow.
This same situation was discussed on https://github.com/renovatebot/renovate/discussions/11739 a few years back with a suggested workaround of using the [baseBranches](https://docs.renovatebot.com/configuration-options/#basebranches).
This feature request would remove the need for such a workaround.
### If you have any ideas on how this should be implemented, please tell us here.
Update the Bitbucket repositories initialization to fetch the **development branch** from the [REST API: Branching Model for the Repository](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-branching-model/#api-repositories-workspace-repo-slug-branching-model-get) and set this as the Renovate repository default branch.
### Is this a feature you are interested in implementing yourself?
Yes | 1.0 | Bitbucket Cloud: initialize repos with development branch - ### What would you like Renovate to be able to do?
Use development branch to initialize Bitbucket Cloud repositories.
Bitbucket Cloud supports a [variety of branching models](https://support.atlassian.com/bitbucket-cloud/docs/branch-a-repository/#The-branching-model), which are configured at the repository level.
Two of importance to this feature request are
- **Development branch** - this is where new feature branches are targeted, commonly `main` or `master` for trunk-based development and `develop` for git-flow. This is configured under _Repository Details >> Worklow >> Branching Model_
- **Main branch** - this is configured under _Repository Details >> Advanced >> Main branch_. Commonly this is left set to `main` or `master` regardless of trunk-based, git-flow or other workflow
At present, when Bitbucket Cloud repositories are initialized, it sets the defaultBranch to be the repositories **main branch** instead of the preferred **development branch**. This means that for repositories using non trunk-based workflows, Renovate PRs will be targeting the wrong branch for their workflow.
This same situation was discussed on https://github.com/renovatebot/renovate/discussions/11739 a few years back with a suggested workaround of using the [baseBranches](https://docs.renovatebot.com/configuration-options/#basebranches).
This feature request would remove the need for such a workaround.
### If you have any ideas on how this should be implemented, please tell us here.
Update the Bitbucket repositories initialization to fetch the **development branch** from the [REST API: Branching Model for the Repository](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-branching-model/#api-repositories-workspace-repo-slug-branching-model-get) and set this as the Renovate repository default branch.
### Is this a feature you are interested in implementing yourself?
Yes | non_test | bitbucket cloud initialize repos with development branch what would you like renovate to be able to do use development branch to initialize bitbucket cloud repositories bitbucket cloud supports a which are configured at the repository level two of importance to this feature request are development branch this is where new feature branches are targeted commonly main or master for trunk based development and develop for git flow this is configured under repository details worklow branching model main branch this is configured under repository details advanced main branch commonly this is left set to main or master regardless of trunk based git flow or other workflow at present when bitbucket cloud repositories are initialized it sets the defaultbranch to be the repositories main branch instead of the preferred development branch this means that for repositories using non trunk based workflows renovate prs will be targeting the wrong branch for their workflow this same situation was discussed on a few years back with a suggested workaround of using the this feature request would remove the need for such a workaround if you have any ideas on how this should be implemented please tell us here update the bitbucket repositories initialization to fetch the development branch from the and set this as the renovate repository default branch is this a feature you are interested in implementing yourself yes | 0 |
194,959 | 14,697,392,121 | IssuesEvent | 2021-01-04 03:09:14 | github-vet/rangeloop-pointer-findings | https://api.github.com/repos/github-vet/rangeloop-pointer-findings | closed | kubernetes-sigs/aws-encryption-provider: pkg/httputil/client_test.go; 67 LoC | fresh medium test |
Found a possible issue in [kubernetes-sigs/aws-encryption-provider](https://www.github.com/kubernetes-sigs/aws-encryption-provider) at [pkg/httputil/client_test.go](https://github.com/kubernetes-sigs/aws-encryption-provider/blob/01a3b6dbc137a9f9d57cb63a8ab2c9b4b4c5f203/pkg/httputil/client_test.go#L58-L124)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.
> range-loop variable tt used in defer or goroutine at line 70
[Click here to see the code in its original context.](https://github.com/kubernetes-sigs/aws-encryption-provider/blob/01a3b6dbc137a9f9d57cb63a8ab2c9b4b4c5f203/pkg/httputil/client_test.go#L58-L124)
<details>
<summary>Click here to show the 67 line(s) of Go which triggered the analyzer.</summary>
```go
for idx, tt := range tbs {
cli, err := NewRateLimitedClient(tt.qps, tt.burst)
if err != nil {
t.Fatalf("#%d: failed to create a new client (%v)", idx, err)
}
start := time.Now()
errc := make(chan error, tt.requests)
for i := 0; i < tt.requests; i++ {
go func() {
var ctx context.Context
if tt.ctxTimeout > 0 {
var cancel context.CancelFunc
ctx, cancel = context.WithTimeout(context.TODO(), tt.ctxTimeout)
defer cancel()
} else {
ctx = context.TODO()
}
req, err := http.NewRequest(http.MethodGet, u, nil)
if err != nil {
errc <- err
return
}
_, err = cli.Do(req.WithContext(ctx))
errc <- err
}()
}
failed := false
for i := 0; i < tt.requests; i++ {
err = <-errc
switch {
case tt.err == "": // expects no error
if err != nil {
t.Errorf("#%d-%d: unexpected error %v", idx, i, err)
}
case tt.err != "": // expects error
if err == nil {
// this means that the request did not get throttled.
continue
}
if !strings.Contains(err.Error(), tt.err) &&
// TODO: why does this happen even when ctx is not canceled
// ref. https://github.com/golang/go/issues/36848
!strings.Contains(err.Error(), "i/o timeout") {
t.Errorf("#%d-%d: expected %q, got %v", idx, i, tt.err, err)
}
failed = true
}
}
if tt.err != "" && !failed {
t.Fatalf("#%d: expected failure %q, got no error", idx, tt.err)
}
if tt.err == "" {
observedDuration := time.Since(start).Round(time.Second)
expectedDuration := time.Duration(0)
if tt.qps + tt.burst < tt.requests {
expectedDuration = (time.Duration(tt.requests/(tt.qps)) * time.Second)
}
if expectedDuration > 0 && observedDuration > expectedDuration {
t.Fatalf("with rate limit, requests expected duration %v, got %v", expectedDuration, observedDuration)
}
}
}
```
</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: 01a3b6dbc137a9f9d57cb63a8ab2c9b4b4c5f203
| 1.0 | kubernetes-sigs/aws-encryption-provider: pkg/httputil/client_test.go; 67 LoC -
Found a possible issue in [kubernetes-sigs/aws-encryption-provider](https://www.github.com/kubernetes-sigs/aws-encryption-provider) at [pkg/httputil/client_test.go](https://github.com/kubernetes-sigs/aws-encryption-provider/blob/01a3b6dbc137a9f9d57cb63a8ab2c9b4b4c5f203/pkg/httputil/client_test.go#L58-L124)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.
> range-loop variable tt used in defer or goroutine at line 70
[Click here to see the code in its original context.](https://github.com/kubernetes-sigs/aws-encryption-provider/blob/01a3b6dbc137a9f9d57cb63a8ab2c9b4b4c5f203/pkg/httputil/client_test.go#L58-L124)
<details>
<summary>Click here to show the 67 line(s) of Go which triggered the analyzer.</summary>
```go
for idx, tt := range tbs {
cli, err := NewRateLimitedClient(tt.qps, tt.burst)
if err != nil {
t.Fatalf("#%d: failed to create a new client (%v)", idx, err)
}
start := time.Now()
errc := make(chan error, tt.requests)
for i := 0; i < tt.requests; i++ {
go func() {
var ctx context.Context
if tt.ctxTimeout > 0 {
var cancel context.CancelFunc
ctx, cancel = context.WithTimeout(context.TODO(), tt.ctxTimeout)
defer cancel()
} else {
ctx = context.TODO()
}
req, err := http.NewRequest(http.MethodGet, u, nil)
if err != nil {
errc <- err
return
}
_, err = cli.Do(req.WithContext(ctx))
errc <- err
}()
}
failed := false
for i := 0; i < tt.requests; i++ {
err = <-errc
switch {
case tt.err == "": // expects no error
if err != nil {
t.Errorf("#%d-%d: unexpected error %v", idx, i, err)
}
case tt.err != "": // expects error
if err == nil {
// this means that the request did not get throttled.
continue
}
if !strings.Contains(err.Error(), tt.err) &&
// TODO: why does this happen even when ctx is not canceled
// ref. https://github.com/golang/go/issues/36848
!strings.Contains(err.Error(), "i/o timeout") {
t.Errorf("#%d-%d: expected %q, got %v", idx, i, tt.err, err)
}
failed = true
}
}
if tt.err != "" && !failed {
t.Fatalf("#%d: expected failure %q, got no error", idx, tt.err)
}
if tt.err == "" {
observedDuration := time.Since(start).Round(time.Second)
expectedDuration := time.Duration(0)
if tt.qps + tt.burst < tt.requests {
expectedDuration = (time.Duration(tt.requests/(tt.qps)) * time.Second)
}
if expectedDuration > 0 && observedDuration > expectedDuration {
t.Fatalf("with rate limit, requests expected duration %v, got %v", expectedDuration, observedDuration)
}
}
}
```
</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: 01a3b6dbc137a9f9d57cb63a8ab2c9b4b4c5f203
| test | kubernetes sigs aws encryption provider pkg httputil client test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message range loop variable tt used in defer or goroutine at line click here to show the line s of go which triggered the analyzer go for idx tt range tbs cli err newratelimitedclient tt qps tt burst if err nil t fatalf d failed to create a new client v idx err start time now errc make chan error tt requests for i i tt requests i go func var ctx context context if tt ctxtimeout var cancel context cancelfunc ctx cancel context withtimeout context todo tt ctxtimeout defer cancel else ctx context todo req err http newrequest http methodget u nil if err nil errc err return err cli do req withcontext ctx errc err failed false for i i tt requests i err errc switch case tt err expects no error if err nil t errorf d d unexpected error v idx i err case tt err expects error if err nil this means that the request did not get throttled continue if strings contains err error tt err todo why does this happen even when ctx is not canceled ref strings contains err error i o timeout t errorf d d expected q got v idx i tt err err failed true if tt err failed t fatalf d expected failure q got no error idx tt err if tt err observedduration time since start round time second expectedduration time duration if tt qps tt burst tt requests expectedduration time duration tt requests tt qps time second if expectedduration observedduration expectedduration t fatalf with rate limit requests expected duration v got v expectedduration observedduration 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 |
79,307 | 9,879,137,842 | IssuesEvent | 2019-06-24 09:19:23 | LinkdropProtocol/linkdrop-monorepo | https://api.github.com/repos/LinkdropProtocol/linkdrop-monorepo | closed | Linkdrop Dashboard & Analytics mockups | design | # Description
Mockups of Dashboard where user can create and set up Linkdrop campaign and see analytics. Also, mockups of Sign Up / Login's user flow.
# Subtasks included
- [x] Linkdrop Sign up / Log In flow
- [ ] Linkdrop Dashboard and Campaign creation flow
- [ ] Linkdrop Analitycs (#24)
# Definition of done
Above screens are done, fully handed-over, and the implementation has started.
# Reviewer
@Dobrokhvalov, @Kisgus | 1.0 | Linkdrop Dashboard & Analytics mockups - # Description
Mockups of Dashboard where user can create and set up Linkdrop campaign and see analytics. Also, mockups of Sign Up / Login's user flow.
# Subtasks included
- [x] Linkdrop Sign up / Log In flow
- [ ] Linkdrop Dashboard and Campaign creation flow
- [ ] Linkdrop Analitycs (#24)
# Definition of done
Above screens are done, fully handed-over, and the implementation has started.
# Reviewer
@Dobrokhvalov, @Kisgus | non_test | linkdrop dashboard analytics mockups description mockups of dashboard where user can create and set up linkdrop campaign and see analytics also mockups of sign up login s user flow subtasks included linkdrop sign up log in flow linkdrop dashboard and campaign creation flow linkdrop analitycs definition of done above screens are done fully handed over and the implementation has started reviewer dobrokhvalov kisgus | 0 |
68,785 | 17,401,880,125 | IssuesEvent | 2021-08-02 20:59:48 | beaverbuilder/documentation | https://api.github.com/repos/beaverbuilder/documentation | closed | Add all tut videos from YouTube to docs | category: bb theme category: beaver builder category: beaver themer doc: improve | Add all tut videos from YouTube to docs and test embedding them using `<video>` instead of YT embed code due to related videos being shown at the end.
| 1.0 | Add all tut videos from YouTube to docs - Add all tut videos from YouTube to docs and test embedding them using `<video>` instead of YT embed code due to related videos being shown at the end.
| non_test | add all tut videos from youtube to docs add all tut videos from youtube to docs and test embedding them using instead of yt embed code due to related videos being shown at the end | 0 |
44,035 | 5,581,815,140 | IssuesEvent | 2017-03-28 19:46:38 | tue-robotics/nl_robot_console | https://api.github.com/repos/tue-robotics/nl_robot_console | closed | ice tea (without "_") not working | bug Test | I think spaces are not allowed. This mean that the object_recognition should also only produce labels without spaces.
@Rayman can you check this in the object recognition and change if needed. | 1.0 | ice tea (without "_") not working - I think spaces are not allowed. This mean that the object_recognition should also only produce labels without spaces.
@Rayman can you check this in the object recognition and change if needed. | test | ice tea without not working i think spaces are not allowed this mean that the object recognition should also only produce labels without spaces rayman can you check this in the object recognition and change if needed | 1 |
63,854 | 8,697,488,455 | IssuesEvent | 2018-12-04 20:25:13 | pokt-network/pocket-core | https://api.github.com/repos/pokt-network/pocket-core | opened | Plan out multiple session creation persistent connection scheme | documentation | In Pocket, several sessions will be simultaneously created. This shard of the network is stateful. What should the scheme be of constantly creating persistent connections for each session
@luyzdeleon this may be crucial when planning | 1.0 | Plan out multiple session creation persistent connection scheme - In Pocket, several sessions will be simultaneously created. This shard of the network is stateful. What should the scheme be of constantly creating persistent connections for each session
@luyzdeleon this may be crucial when planning | non_test | plan out multiple session creation persistent connection scheme in pocket several sessions will be simultaneously created this shard of the network is stateful what should the scheme be of constantly creating persistent connections for each session luyzdeleon this may be crucial when planning | 0 |
33,939 | 4,866,484,919 | IssuesEvent | 2016-11-14 23:59:04 | jruby/jruby | https://api.github.com/repos/jruby/jruby | opened | [ruby 2.4] New hanging or crashing tests | JRuby 9000 ruby 2.4 tests | I have had to exclude some new Ruby 2.4 tests to get a complete test run. They should be examined before 9.2. | 1.0 | [ruby 2.4] New hanging or crashing tests - I have had to exclude some new Ruby 2.4 tests to get a complete test run. They should be examined before 9.2. | test | new hanging or crashing tests i have had to exclude some new ruby tests to get a complete test run they should be examined before | 1 |
662,769 | 22,152,527,869 | IssuesEvent | 2022-06-03 18:30:55 | yugabyte/yugabyte-db | https://api.github.com/repos/yugabyte/yugabyte-db | closed | [YSQL] Enable yb_db_admin to use database | kind/bug area/ysql priority/medium 2.12 Backport Required | Jira Link: [DB-612](https://yugabyte.atlassian.net/browse/DB-612)
### Description
```
CREATE DATABASE name
[ [ WITH ] [ OWNER [=] user_name ]
[ TEMPLATE [=] template ]
[ ENCODING [=] encoding ]
[ LOCALE [=] locale ]
[ LC_COLLATE [=] lc_collate ]
[ LC_CTYPE [=] lc_ctype ]
[ TABLESPACE [=] tablespace_name ]
[ ALLOW_CONNECTIONS [=] allowconn ]
[ CONNECTION LIMIT [=] connlimit ]
[ IS_TEMPLATE [=] istemplate ] ]
```
```
ALTER DATABASE name [ [ WITH ] option [ ... ] ]
where option can be:
ALLOW_CONNECTIONS allowconn
CONNECTION LIMIT connlimit
IS_TEMPLATE istemplate
ALTER DATABASE name RENAME TO new_name
ALTER DATABASE name OWNER TO { new_owner | CURRENT_ROLE | CURRENT_USER | SESSION_USER }
ALTER DATABASE name SET TABLESPACE new_tablespace
ALTER DATABASE name SET configuration_parameter { TO | = } { value | DEFAULT }
ALTER DATABASE name SET configuration_parameter FROM CURRENT
ALTER DATABASE name RESET configuration_parameter
ALTER DATABASE name RESET ALL
```
```
DROP DATABASE
``` | 1.0 | [YSQL] Enable yb_db_admin to use database - Jira Link: [DB-612](https://yugabyte.atlassian.net/browse/DB-612)
### Description
```
CREATE DATABASE name
[ [ WITH ] [ OWNER [=] user_name ]
[ TEMPLATE [=] template ]
[ ENCODING [=] encoding ]
[ LOCALE [=] locale ]
[ LC_COLLATE [=] lc_collate ]
[ LC_CTYPE [=] lc_ctype ]
[ TABLESPACE [=] tablespace_name ]
[ ALLOW_CONNECTIONS [=] allowconn ]
[ CONNECTION LIMIT [=] connlimit ]
[ IS_TEMPLATE [=] istemplate ] ]
```
```
ALTER DATABASE name [ [ WITH ] option [ ... ] ]
where option can be:
ALLOW_CONNECTIONS allowconn
CONNECTION LIMIT connlimit
IS_TEMPLATE istemplate
ALTER DATABASE name RENAME TO new_name
ALTER DATABASE name OWNER TO { new_owner | CURRENT_ROLE | CURRENT_USER | SESSION_USER }
ALTER DATABASE name SET TABLESPACE new_tablespace
ALTER DATABASE name SET configuration_parameter { TO | = } { value | DEFAULT }
ALTER DATABASE name SET configuration_parameter FROM CURRENT
ALTER DATABASE name RESET configuration_parameter
ALTER DATABASE name RESET ALL
```
```
DROP DATABASE
``` | non_test | enable yb db admin to use database jira link description create database name user name template encoding locale lc collate lc ctype tablespace name allowconn connlimit istemplate alter database name option where option can be allow connections allowconn connection limit connlimit is template istemplate alter database name rename to new name alter database name owner to new owner current role current user session user alter database name set tablespace new tablespace alter database name set configuration parameter to value default alter database name set configuration parameter from current alter database name reset configuration parameter alter database name reset all drop database | 0 |
116,015 | 9,818,652,176 | IssuesEvent | 2019-06-13 19:49:39 | magento-engcom/msi | https://api.github.com/repos/magento-engcom/msi | closed | "Only X left' = 0 not displayed for 'Out of stock' Simple product on Default source and Main website automation | MFTF (Functional Test Coverage) | ### Steps to be automated
1. New source created
2. New Stock created with New Source assigned
3. Simple Product created on Default source with Qty = 0 and status 'Out of stock'
4. Enable 'Display Out of Stock Products' in Configuration
5. Set 'Only X left Threshold' = 0 in Configuration
6. Verify that message 'Only 0 left' not appeared on Simple product page on frontend | 1.0 | "Only X left' = 0 not displayed for 'Out of stock' Simple product on Default source and Main website automation - ### Steps to be automated
1. New source created
2. New Stock created with New Source assigned
3. Simple Product created on Default source with Qty = 0 and status 'Out of stock'
4. Enable 'Display Out of Stock Products' in Configuration
5. Set 'Only X left Threshold' = 0 in Configuration
6. Verify that message 'Only 0 left' not appeared on Simple product page on frontend | test | only x left not displayed for out of stock simple product on default source and main website automation steps to be automated new source created new stock created with new source assigned simple product created on default source with qty and status out of stock enable display out of stock products in configuration set only x left threshold in configuration verify that message only left not appeared on simple product page on frontend | 1 |
5,829 | 7,346,265,018 | IssuesEvent | 2018-03-07 20:07:21 | stelligent/mu | https://api.github.com/repos/stelligent/mu | reopened | S3 Revision ID's can begin with a period (.) which leads to invalid Docker tags | bug services | As the title states, when using S3 as a CodePipeline source, the Revision ID that gets generated and used to tag the Docker images in ECR can start with a period. The image can be pushed, but when it tries to pull the image when deploying the ECS service later, it causes a "cannotpullcontainerimage" error. | 1.0 | S3 Revision ID's can begin with a period (.) which leads to invalid Docker tags - As the title states, when using S3 as a CodePipeline source, the Revision ID that gets generated and used to tag the Docker images in ECR can start with a period. The image can be pushed, but when it tries to pull the image when deploying the ECS service later, it causes a "cannotpullcontainerimage" error. | non_test | revision id s can begin with a period which leads to invalid docker tags as the title states when using as a codepipeline source the revision id that gets generated and used to tag the docker images in ecr can start with a period the image can be pushed but when it tries to pull the image when deploying the ecs service later it causes a cannotpullcontainerimage error | 0 |
797,482 | 28,147,179,410 | IssuesEvent | 2023-04-02 16:12:24 | AY2223S2-CS2113-T11-3/tp | https://api.github.com/repos/AY2223S2-CS2113-T11-3/tp | closed | [PE-D][Tester D] Removing empty pet name throws exception and terminates | type.Bug priority.High severity.High | 
User guide does mention that the pet name should not be empty, but it is not enforced.
<!--session: 1680252521773-f89ba828-9c53-4111-9490-4f9e7a58ddf6--><!--Version: Web v3.4.7-->
-------------
Labels: `type.FunctionalityBug` `severity.High`
original: namsengi11/ped#2 | 1.0 | [PE-D][Tester D] Removing empty pet name throws exception and terminates - 
User guide does mention that the pet name should not be empty, but it is not enforced.
<!--session: 1680252521773-f89ba828-9c53-4111-9490-4f9e7a58ddf6--><!--Version: Web v3.4.7-->
-------------
Labels: `type.FunctionalityBug` `severity.High`
original: namsengi11/ped#2 | non_test | removing empty pet name throws exception and terminates user guide does mention that the pet name should not be empty but it is not enforced labels type functionalitybug severity high original ped | 0 |
313,608 | 9,565,138,601 | IssuesEvent | 2019-05-05 10:01:58 | bounswe/bounswe2019group1 | https://api.github.com/repos/bounswe/bounswe2019group1 | opened | Create get events backend operations | Coding: Backend Effort: Medium Priority: Medium | All events are fetched from Database and sent to Frontend. | 1.0 | Create get events backend operations - All events are fetched from Database and sent to Frontend. | non_test | create get events backend operations all events are fetched from database and sent to frontend | 0 |
32,598 | 4,778,379,266 | IssuesEvent | 2016-10-27 19:06:46 | mozilla/pdf.js | https://api.github.com/repos/mozilla/pdf.js | closed | Update Node to latest version on the bots | 1-test | One bot is running 4.4.3, the other one is too old.
Then we can make use of modern JS features and improved standard libraries. | 1.0 | Update Node to latest version on the bots - One bot is running 4.4.3, the other one is too old.
Then we can make use of modern JS features and improved standard libraries. | test | update node to latest version on the bots one bot is running the other one is too old then we can make use of modern js features and improved standard libraries | 1 |
330,426 | 28,376,702,244 | IssuesEvent | 2023-04-12 21:29:36 | flutter/flutter | https://api.github.com/repos/flutter/flutter | closed | Google Testing CI check is flaky | team: google testing | Example: https://github.com/flutter/flutter/pull/116218
This is mainly being tracked internally (b/260764527), but this bug card is meant to give visibility of progress on the issue | 1.0 | Google Testing CI check is flaky - Example: https://github.com/flutter/flutter/pull/116218
This is mainly being tracked internally (b/260764527), but this bug card is meant to give visibility of progress on the issue | test | google testing ci check is flaky example this is mainly being tracked internally b but this bug card is meant to give visibility of progress on the issue | 1 |
5,857 | 2,796,439,494 | IssuesEvent | 2015-05-12 07:31:14 | h2opaulh2o/IP-A3-Project | https://api.github.com/repos/h2opaulh2o/IP-A3-Project | closed | Make tests for XMLReader and XMLWriter classes | Testing | In Interface branch, Integration director you will see a NetBeans project.
Install NetBeans on your computer and run this project.
After try to make some tests for XMLReader and XMLWriter classes from "pkginterface". | 1.0 | Make tests for XMLReader and XMLWriter classes - In Interface branch, Integration director you will see a NetBeans project.
Install NetBeans on your computer and run this project.
After try to make some tests for XMLReader and XMLWriter classes from "pkginterface". | test | make tests for xmlreader and xmlwriter classes in interface branch integration director you will see a netbeans project install netbeans on your computer and run this project after try to make some tests for xmlreader and xmlwriter classes from pkginterface | 1 |
295,923 | 22,283,631,324 | IssuesEvent | 2022-06-11 09:00:36 | AndyNotfound/PythonWhatsappBot | https://api.github.com/repos/AndyNotfound/PythonWhatsappBot | closed | Documentation | documentation | Make the README.md more readable and make it more like a guidance to your program | 1.0 | Documentation - Make the README.md more readable and make it more like a guidance to your program | non_test | documentation make the readme md more readable and make it more like a guidance to your program | 0 |
227,147 | 17,375,370,092 | IssuesEvent | 2021-07-30 20:10:09 | softlayer/githubio_source | https://api.github.com/repos/softlayer/githubio_source | closed | Merge hardware server examples written in Go into one file | Documentation | There are examples in Go related to create, cancel, edit, list, list available packages to create servers, they will be merged as a whole example.
Examples to merge:
https://sldn.softlayer.com/go/cancel_server.go/
https://sldn.softlayer.com/go/create_server.go/
https://sldn.softlayer.com/go/edit_server.go/
https://sldn.softlayer.com/go/list_servers.go/
https://sldn.softlayer.com/go/list_servers_to_order.go/
https://sldn.softlayer.com/go/list_servers_to_order_hourly.go/ | 1.0 | Merge hardware server examples written in Go into one file - There are examples in Go related to create, cancel, edit, list, list available packages to create servers, they will be merged as a whole example.
Examples to merge:
https://sldn.softlayer.com/go/cancel_server.go/
https://sldn.softlayer.com/go/create_server.go/
https://sldn.softlayer.com/go/edit_server.go/
https://sldn.softlayer.com/go/list_servers.go/
https://sldn.softlayer.com/go/list_servers_to_order.go/
https://sldn.softlayer.com/go/list_servers_to_order_hourly.go/ | non_test | merge hardware server examples written in go into one file there are examples in go related to create cancel edit list list available packages to create servers they will be merged as a whole example examples to merge | 0 |
340,209 | 30,502,219,086 | IssuesEvent | 2023-07-18 14:35:49 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | roachtest: costfuzz/workload-replay failed | C-test-failure O-robot O-roachtest branch-master release-blocker T-disaster-recovery T-sql-queries | roachtest.costfuzz/workload-replay [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/10950435?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/10950435?buildTab=artifacts#/costfuzz/workload-replay) on master @ [7675ca4998134028f0623e04737b5cb69fcc33a9](https://github.com/cockroachdb/cockroach/commits/7675ca4998134028f0623e04737b5cb69fcc33a9):
```
The details about this test failure have been omitted; consult the log for more details
```
<p>Parameters: <code>ROACHTEST_arch=amd64</code>
, <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_fs=ext4</code>
, <code>ROACHTEST_localSSD=true</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>
/cc @cockroachdb/sql-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*costfuzz/workload-replay.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-29837 | 2.0 | roachtest: costfuzz/workload-replay failed - roachtest.costfuzz/workload-replay [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/10950435?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/10950435?buildTab=artifacts#/costfuzz/workload-replay) on master @ [7675ca4998134028f0623e04737b5cb69fcc33a9](https://github.com/cockroachdb/cockroach/commits/7675ca4998134028f0623e04737b5cb69fcc33a9):
```
The details about this test failure have been omitted; consult the log for more details
```
<p>Parameters: <code>ROACHTEST_arch=amd64</code>
, <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_fs=ext4</code>
, <code>ROACHTEST_localSSD=true</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>
/cc @cockroachdb/sql-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*costfuzz/workload-replay.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-29837 | test | roachtest costfuzz workload replay failed roachtest costfuzz workload replay with on master the details about this test failure have been omitted consult the log for more details parameters roachtest arch roachtest cloud gce roachtest cpu roachtest encrypted false roachtest fs roachtest localssd true roachtest ssd help see see cc cockroachdb sql queries jira issue crdb | 1 |
50,707 | 6,108,139,334 | IssuesEvent | 2017-06-21 09:46:20 | lago-project/lago | https://api.github.com/repos/lago-project/lago | closed | tests: add `systemd-analyze blame` where applicable and dump it to the artifacts | enhancement tests | Related PR: https://github.com/lago-project/lago/pull/565, with that we can compare boot times more efficiently in the CI. | 1.0 | tests: add `systemd-analyze blame` where applicable and dump it to the artifacts - Related PR: https://github.com/lago-project/lago/pull/565, with that we can compare boot times more efficiently in the CI. | test | tests add systemd analyze blame where applicable and dump it to the artifacts related pr with that we can compare boot times more efficiently in the ci | 1 |
316,766 | 27,182,783,728 | IssuesEvent | 2023-02-18 21:06:01 | MicrosoftDocs/minecraft-creator | https://api.github.com/repos/MicrosoftDocs/minecraft-creator | closed | [Improvement] [GameTest] Pre entity spawn event | GameTest/Scripting | **Fire an event before an entity spawns**
Allow event handlers to modify entities before they spawn, essentially acting as a pre admission hook. The ability to cancel this (where appropriate, for example would cancelling on a player kick them?) would probably come in use as a filter or forcing components to be added/modified (rainbow sheep world anyone?) | 1.0 | [Improvement] [GameTest] Pre entity spawn event - **Fire an event before an entity spawns**
Allow event handlers to modify entities before they spawn, essentially acting as a pre admission hook. The ability to cancel this (where appropriate, for example would cancelling on a player kick them?) would probably come in use as a filter or forcing components to be added/modified (rainbow sheep world anyone?) | test | pre entity spawn event fire an event before an entity spawns allow event handlers to modify entities before they spawn essentially acting as a pre admission hook the ability to cancel this where appropriate for example would cancelling on a player kick them would probably come in use as a filter or forcing components to be added modified rainbow sheep world anyone | 1 |
528,384 | 15,365,447,967 | IssuesEvent | 2021-03-01 23:36:06 | agrc/electrofishing | https://api.github.com/repos/agrc/electrofishing | opened | Add Comment boxes | database change lower priority | - [ ] `Method` tab - for each piece of equipment
- [ ] `Catch` tab - for each pass
- [ ] `Habitat` tab | 1.0 | Add Comment boxes - - [ ] `Method` tab - for each piece of equipment
- [ ] `Catch` tab - for each pass
- [ ] `Habitat` tab | non_test | add comment boxes method tab for each piece of equipment catch tab for each pass habitat tab | 0 |
15,433 | 2,853,544,466 | IssuesEvent | 2015-06-01 19:07:03 | nerdralph/picoboot | https://api.github.com/repos/nerdralph/picoboot | closed | stk500 rxpkt won't read packets contain CRC_EOP in data | auto-migrated Priority-Medium Type-Defect | ```
There are some neat optimizations in the picobootSTK500.S file, but I don't see
how the current rxpacket code would work for a program_page command if the data
to be programmed contains a CRC_EOP byte (0x20)
```
Original issue reported on code.google.com by `wes...@gmail.com` on 31 Jul 2014 at 9:29 | 1.0 | stk500 rxpkt won't read packets contain CRC_EOP in data - ```
There are some neat optimizations in the picobootSTK500.S file, but I don't see
how the current rxpacket code would work for a program_page command if the data
to be programmed contains a CRC_EOP byte (0x20)
```
Original issue reported on code.google.com by `wes...@gmail.com` on 31 Jul 2014 at 9:29 | non_test | rxpkt won t read packets contain crc eop in data there are some neat optimizations in the s file but i don t see how the current rxpacket code would work for a program page command if the data to be programmed contains a crc eop byte original issue reported on code google com by wes gmail com on jul at | 0 |
277,948 | 21,057,902,507 | IssuesEvent | 2022-04-01 06:28:46 | justinekoh/ped | https://api.github.com/repos/justinekoh/ped | opened | UG List command unsuitable line | severity.Low type.DocumentationBug | 
This line may be better off in another section that describes the GUI, and will do better with visuals
<!--session: 1648792865230-ce059e58-d8e6-4e61-9d66-ef10cb85bcb7-->
<!--Version: Web v3.4.2--> | 1.0 | UG List command unsuitable line - 
This line may be better off in another section that describes the GUI, and will do better with visuals
<!--session: 1648792865230-ce059e58-d8e6-4e61-9d66-ef10cb85bcb7-->
<!--Version: Web v3.4.2--> | non_test | ug list command unsuitable line this line may be better off in another section that describes the gui and will do better with visuals | 0 |
65,763 | 7,915,988,657 | IssuesEvent | 2018-07-04 03:05:45 | RandolphChin/RandolphChin.github.io | https://api.github.com/repos/RandolphChin/RandolphChin.github.io | opened | 适配器模式与外观模式 | Design Pattern | 适配器模式：将一个类的接口，转换成客户期望的另一个接口，适配器让原本接口不兼容的类可以合作无间。
在中国使用美国制造的笔记本电脑，需要使用一个交流电的适配器
客户使用适配器的过程如下：
1. 客户通过目标接口调用适配器的方法对适配器发出请求
2. 适配器使用被适配者接口把请求转换成被适配者的一个或多个调用接口
3. 客户接收到调用的结果，但并未察觉这一切是适配器在起转换作用
**外观模式(Facade-Pattern)**：提供了一个统一的接口，用来访问子系统中的一群接口。外观定义了一个高层
接口，让子系统更容易使用。提供简化的接口的同时，依然把系统完整的功能暴露出来，将客户实现从子系统中解耦
**适配器模式与外观模式区别**：适配器意图是改变接口符合客户的期望(将接口转换成不同接口)，
而外观模式的意图是提供子系统的一个简化接口(简化接口)
**适配器模式与外观模式相同点**：都可以包装许多类
适配器模式类图如下
家庭影院观看电影，困难的方式是需要打开相关的许多子系统
将灯光调暗 -> 放下屏幕 -> 打开投影机 -> 将投影机输入切换到DVD ->将投影机设置在宽屏模式 -> 打开功放
-> 功放设置为环绕立体声 -> 打开 DVD 播放器 -> 开始播放 DVD
外观模式是通过简单的方式将这些任务写成类和方法进行封装，达到简化目的
**要点**
当需要使用一个现在的类而其接口并不符合你的需要时，就使用适配器
当需要简化并统一一个很大的接口或者一群复杂的接口时，使用外观
适配器改变接口以符合靠窗户的期望
外观将客户从一个复杂的子系统中解耦
实现一个外观，需要将子系统组合进外观中，然后将工作委托给子系统执行
**适配器模式与装饰者模式与外观模式区别**:
适配器将一个对象包装起来以改变接口；装饰者将一个对象包装起来以增加新的行为和责任；外观将一群对象
"包装"起来以简化其接口
示例
如果它走起来像鸭子，叫起来像只鸭子，那么他可能是一只包装了鸭子适配器的火鸡
Duck
```Java
public interface Duck{
public void quack();
public void fly()
}
```
绿头鸭
```Java
public classs MallardDuck implement Duck{
public void quack(){
Syso("quack")
}
public void fly(){
Syso("i'm flying")
}
}
```
Turkey
```Java
public interface Turkey{
public void gobble();
public void fly();
}
```
WildTurkey
```Java
public class WildTurkey implements Turkey{
public void gobble(){
syso("Gobble gobble");
}
public void fly(){
syso("i'm flying");
}
}
```
缺少鸭子对象，想用一些火鸡对象来冒充。因为火鸡的接口不同，所以不能直接拿来用，需要写个适配器
```Java
// 首先需要实现想救困扶危成的类型接口，也就是客户所期望看到的接口
public class TurkeyAdapter implemenets Duck{
Turkey turkey;
// 使用构造器取得适配的对象引用
public TurkeyAdapter (Turkey turkey){
this.turkey = turkey
}
// 实现接口中所有的方法
public void quack(){
turkey.gobble()
}
public void flay(){
turkey.fly()
}
}
```
TestTest
```Java
public class DuckTestDrive{
public static void main(String[] args){
MallardDuck duck = new MallardDuck()
WildTuckey turkey = new WildTurkey();
Duck turkeyAdapter = new TurkeyAdapter(turkey);
turkey.gobble();
turkey.fly();
turkeyAdapter.quack();
turkeyAdapter.fly();
}
}
``` | 1.0 | 适配器模式与外观模式 - 适配器模式：将一个类的接口，转换成客户期望的另一个接口，适配器让原本接口不兼容的类可以合作无间。
在中国使用美国制造的笔记本电脑，需要使用一个交流电的适配器
客户使用适配器的过程如下：
1. 客户通过目标接口调用适配器的方法对适配器发出请求
2. 适配器使用被适配者接口把请求转换成被适配者的一个或多个调用接口
3. 客户接收到调用的结果，但并未察觉这一切是适配器在起转换作用
**外观模式(Facade-Pattern)**：提供了一个统一的接口，用来访问子系统中的一群接口。外观定义了一个高层
接口，让子系统更容易使用。提供简化的接口的同时，依然把系统完整的功能暴露出来，将客户实现从子系统中解耦
**适配器模式与外观模式区别**：适配器意图是改变接口符合客户的期望(将接口转换成不同接口)，
而外观模式的意图是提供子系统的一个简化接口(简化接口)
**适配器模式与外观模式相同点**：都可以包装许多类
适配器模式类图如下
家庭影院观看电影，困难的方式是需要打开相关的许多子系统
将灯光调暗 -> 放下屏幕 -> 打开投影机 -> 将投影机输入切换到DVD ->将投影机设置在宽屏模式 -> 打开功放
-> 功放设置为环绕立体声 -> 打开 DVD 播放器 -> 开始播放 DVD
外观模式是通过简单的方式将这些任务写成类和方法进行封装，达到简化目的
**要点**
当需要使用一个现在的类而其接口并不符合你的需要时，就使用适配器
当需要简化并统一一个很大的接口或者一群复杂的接口时，使用外观
适配器改变接口以符合靠窗户的期望
外观将客户从一个复杂的子系统中解耦
实现一个外观，需要将子系统组合进外观中，然后将工作委托给子系统执行
**适配器模式与装饰者模式与外观模式区别**:
适配器将一个对象包装起来以改变接口；装饰者将一个对象包装起来以增加新的行为和责任；外观将一群对象
"包装"起来以简化其接口
示例
如果它走起来像鸭子，叫起来像只鸭子，那么他可能是一只包装了鸭子适配器的火鸡
Duck
```Java
public interface Duck{
public void quack();
public void fly()
}
```
绿头鸭
```Java
public classs MallardDuck implement Duck{
public void quack(){
Syso("quack")
}
public void fly(){
Syso("i'm flying")
}
}
```
Turkey
```Java
public interface Turkey{
public void gobble();
public void fly();
}
```
WildTurkey
```Java
public class WildTurkey implements Turkey{
public void gobble(){
syso("Gobble gobble");
}
public void fly(){
syso("i'm flying");
}
}
```
缺少鸭子对象，想用一些火鸡对象来冒充。因为火鸡的接口不同，所以不能直接拿来用，需要写个适配器
```Java
// 首先需要实现想救困扶危成的类型接口，也就是客户所期望看到的接口
public class TurkeyAdapter implemenets Duck{
Turkey turkey;
// 使用构造器取得适配的对象引用
public TurkeyAdapter (Turkey turkey){
this.turkey = turkey
}
// 实现接口中所有的方法
public void quack(){
turkey.gobble()
}
public void flay(){
turkey.fly()
}
}
```
TestTest
```Java
public class DuckTestDrive{
public static void main(String[] args){
MallardDuck duck = new MallardDuck()
WildTuckey turkey = new WildTurkey();
Duck turkeyAdapter = new TurkeyAdapter(turkey);
turkey.gobble();
turkey.fly();
turkeyAdapter.quack();
turkeyAdapter.fly();
}
}
``` | non_test | 适配器模式与外观模式 适配器模式：将一个类的接口，转换成客户期望的另一个接口，适配器让原本接口不兼容的类可以合作无间。 在中国使用美国制造的笔记本电脑，需要使用一个交流电的适配器 客户使用适配器的过程如下： 客户通过目标接口调用适配器的方法对适配器发出请求 适配器使用被适配者接口把请求转换成被适配者的一个或多个调用接口 客户接收到调用的结果，但并未察觉这一切是适配器在起转换作用 外观模式 facade pattern ：提供了一个统一的接口，用来访问子系统中的一群接口。外观定义了一个高层 接口，让子系统更容易使用。提供简化的接口的同时，依然把系统完整的功能暴露出来，将客户实现从子系统中解耦 适配器模式与外观模式区别 ：适配器意图是改变接口符合客户的期望 将接口转换成不同接口 ， 而外观模式的意图是提供子系统的一个简化接口 简化接口 适配器模式与外观模式相同点 ：都可以包装许多类 适配器模式类图如下 家庭影院观看电影，困难的方式是需要打开相关的许多子系统 将灯光调暗 放下屏幕 打开投影机 将投影机输入切换到dvd 将投影机设置在宽屏模式 打开功放 功放设置为环绕立体声 打开 dvd 播放器 开始播放 dvd 外观模式是通过简单的方式将这些任务写成类和方法进行封装，达到简化目的 要点 当需要使用一个现在的类而其接口并不符合你的需要时，就使用适配器 当需要简化并统一一个很大的接口或者一群复杂的接口时，使用外观 适配器改变接口以符合靠窗户的期望 外观将客户从一个复杂的子系统中解耦 实现一个外观，需要将子系统组合进外观中，然后将工作委托给子系统执行 适配器模式与装饰者模式与外观模式区别 适配器将一个对象包装起来以改变接口；装饰者将一个对象包装起来以增加新的行为和责任；外观将一群对象 包装 起来以简化其接口 示例 如果它走起来像鸭子，叫起来像只鸭子，那么他可能是一只包装了鸭子适配器的火鸡 duck java public interface duck public void quack public void fly 绿头鸭 java public classs mallardduck implement duck public void quack syso quack public void fly syso i m flying turkey java public interface turkey public void gobble public void fly wildturkey java public class wildturkey implements turkey public void gobble syso gobble gobble public void fly syso i m flying 缺少鸭子对象，想用一些火鸡对象来冒充。因为火鸡的接口不同，所以不能直接拿来用，需要写个适配器 java 首先需要实现想救困扶危成的类型接口，也就是客户所期望看到的接口 public class turkeyadapter implemenets duck turkey turkey 使用构造器取得适配的对象引用 public turkeyadapter turkey turkey this turkey turkey 实现接口中所有的方法 public void quack turkey gobble public void flay turkey fly testtest java public class ducktestdrive public static void main string args mallardduck duck new mallardduck wildtuckey turkey new wildturkey duck turkeyadapter new turkeyadapter turkey turkey gobble turkey fly turkeyadapter quack turkeyadapter fly | 0 |
200,491 | 15,801,722,239 | IssuesEvent | 2021-04-03 06:17:22 | hojiefeng/ped | https://api.github.com/repos/hojiefeng/ped | opened | Find command does not match UG | severity.Medium type.DocumentationBug | Find command only accepts index but on the UG there are parameters /n and /i which does not work
<!--session: 1617429859731-59b28e30-0e21-4334-84bf-6cf4fbdac809--> | 1.0 | Find command does not match UG - Find command only accepts index but on the UG there are parameters /n and /i which does not work
<!--session: 1617429859731-59b28e30-0e21-4334-84bf-6cf4fbdac809--> | non_test | find command does not match ug find command only accepts index but on the ug there are parameters n and i which does not work | 0 |
216,131 | 16,637,010,202 | IssuesEvent | 2021-06-04 01:06:38 | fasteddy516/EDMC-Telemetry | https://api.github.com/repos/fasteddy516/EDMC-Telemetry | closed | Update documentation for 0.3.0 | documentation | Lots has changed in this version - `README.md` needs to be updated to reflect these changes. | 1.0 | Update documentation for 0.3.0 - Lots has changed in this version - `README.md` needs to be updated to reflect these changes. | non_test | update documentation for lots has changed in this version readme md needs to be updated to reflect these changes | 0 |
232,123 | 25,565,288,608 | IssuesEvent | 2022-11-30 13:53:47 | snowdensb/caseflow | https://api.github.com/repos/snowdensb/caseflow | opened | CVE-2022-38900 (High) detected in decode-uri-component-0.2.0.tgz | security vulnerability | ## CVE-2022-38900 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>decode-uri-component-0.2.0.tgz</b></p></summary>
<p>A better decodeURIComponent</p>
<p>Library home page: <a href="https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz">https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz</a></p>
<p>Path to dependency file: /client/package.json</p>
<p>Path to vulnerable library: /client/node_modules/decode-uri-component/package.json</p>
<p>
Dependency Hierarchy:
- jest-dom-5.11.10.tgz (Root Library)
- css-3.0.0.tgz
- source-map-resolve-0.6.0.tgz
- :x: **decode-uri-component-0.2.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/snowdensb/caseflow/commit/81f8b3f5658022f994993a18a7653667705b7f6e">81f8b3f5658022f994993a18a7653667705b7f6e</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
decode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS.
<p>Publish Date: 2022-11-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38900>CVE-2022-38900</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>
| True | CVE-2022-38900 (High) detected in decode-uri-component-0.2.0.tgz - ## CVE-2022-38900 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>decode-uri-component-0.2.0.tgz</b></p></summary>
<p>A better decodeURIComponent</p>
<p>Library home page: <a href="https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz">https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz</a></p>
<p>Path to dependency file: /client/package.json</p>
<p>Path to vulnerable library: /client/node_modules/decode-uri-component/package.json</p>
<p>
Dependency Hierarchy:
- jest-dom-5.11.10.tgz (Root Library)
- css-3.0.0.tgz
- source-map-resolve-0.6.0.tgz
- :x: **decode-uri-component-0.2.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/snowdensb/caseflow/commit/81f8b3f5658022f994993a18a7653667705b7f6e">81f8b3f5658022f994993a18a7653667705b7f6e</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
decode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS.
<p>Publish Date: 2022-11-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38900>CVE-2022-38900</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>
| non_test | cve high detected in decode uri component tgz cve high severity vulnerability vulnerable library decode uri component tgz a better decodeuricomponent library home page a href path to dependency file client package json path to vulnerable library client node modules decode uri component package json dependency hierarchy jest dom tgz root library css tgz source map resolve tgz x decode uri component tgz vulnerable library found in head commit a href found in base branch master vulnerability details decode uri component is vulnerable to improper input validation resulting in dos 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 | 0 |
56,391 | 15,053,429,799 | IssuesEvent | 2021-02-03 16:18:01 | Rise-Vision/rise-vision-apps | https://api.github.com/repos/Rise-Vision/rise-vision-apps | closed | "Add Display License" Consolidated UI Feedback | visual defect | ### Padding below "Cost will decrease" box
**Issue:** The padding below this box:
should be `15px`.
---
### Button sizes
**Issue:** These buttons:
should be using [our "Large" button sizes](https://docs.google.com/document/d/1JaurbTMAWsHZIauyrENMVdM1shwdzb5BqtKkjSURVoI/edit#bookmark=id.9bkt4s31wbfk).
---
### Padding below coupon code input
**Issue:** The padding below this input:
should be `15px`.
---
### Upper limit for number of additional display licenses
**Issue:** Should there be an upper limit (maximum) number for how many display licenses someone can add? When I enter a ridiculously high number (`55555555555555555555555555555555555555555555555`, for example), I get this:
---
### Input size for additional display license amount
**Issue:** This input:
Is bigger than [the mockup](https://overflow.io/s/I1SU0UQE?node=ccf09664). My preference would be for it to match the mockup.
---
### Opening up the "contact us" form in the help widget.
**Issue:** When you click this link:
Can we open the contact form like this:
---
### Opening up the "common questions" article in the help widget.
**Issue:** When you click this link:
Can we open the article in the help widget directly, like this:
 | 1.0 | "Add Display License" Consolidated UI Feedback - ### Padding below "Cost will decrease" box
**Issue:** The padding below this box:
should be `15px`.
---
### Button sizes
**Issue:** These buttons:
should be using [our "Large" button sizes](https://docs.google.com/document/d/1JaurbTMAWsHZIauyrENMVdM1shwdzb5BqtKkjSURVoI/edit#bookmark=id.9bkt4s31wbfk).
---
### Padding below coupon code input
**Issue:** The padding below this input:
should be `15px`.
---
### Upper limit for number of additional display licenses
**Issue:** Should there be an upper limit (maximum) number for how many display licenses someone can add? When I enter a ridiculously high number (`55555555555555555555555555555555555555555555555`, for example), I get this:
---
### Input size for additional display license amount
**Issue:** This input:
Is bigger than [the mockup](https://overflow.io/s/I1SU0UQE?node=ccf09664). My preference would be for it to match the mockup.
---
### Opening up the "contact us" form in the help widget.
**Issue:** When you click this link:
Can we open the contact form like this:
---
### Opening up the "common questions" article in the help widget.
**Issue:** When you click this link:
Can we open the article in the help widget directly, like this:
 | non_test | add display license consolidated ui feedback padding below cost will decrease box issue the padding below this box should be button sizes issue these buttons should be using padding below coupon code input issue the padding below this input should be upper limit for number of additional display licenses issue should there be an upper limit maximum number for how many display licenses someone can add when i enter a ridiculously high number for example i get this input size for additional display license amount issue this input is bigger than my preference would be for it to match the mockup opening up the contact us form in the help widget issue when you click this link can we open the contact form like this opening up the common questions article in the help widget issue when you click this link can we open the article in the help widget directly like this | 0 |
136,181 | 11,042,886,528 | IssuesEvent | 2019-12-09 10:03:58 | microsoft/AzureStorageExplorer | https://api.github.com/repos/microsoft/AzureStorageExplorer | opened | The 'Manage Access' dialog for one adls gen2 blob shows unfriendly | :beetle: regression :gear: adls gen2 🧪 testing | **Storage Explorer Version:** 1.11.1
**Build:** [20191206.5](https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=3301659)
**Branch:** dev/marayerm/electron7/packaging
**Platform/OS:** Windows 10/ Linux Ubuntu 18.04/macOS High Sierra
**Architecture:** ia32/x64
**Regression From:** Previous build (20191206.2)
**Steps to reproduce:**
1. Expand one ADLS Gen2 storage account -> Blob Containers.
2. Select one blob container which contains one blob at least.
3. Right click one blob and select 'Manage Access...'.
4. Check the Manage Access dialog.
**Expect Experience:**
The Manage Access dialog shows friendly.
**Actual Experience:**
The Manage Access dialog shows unfriendly.
**More Info:**
1. For ADLS Gen2 blob container & ADLS Gen2 folder, the Manage Access dialog shows like below.
| 1.0 | The 'Manage Access' dialog for one adls gen2 blob shows unfriendly - **Storage Explorer Version:** 1.11.1
**Build:** [20191206.5](https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=3301659)
**Branch:** dev/marayerm/electron7/packaging
**Platform/OS:** Windows 10/ Linux Ubuntu 18.04/macOS High Sierra
**Architecture:** ia32/x64
**Regression From:** Previous build (20191206.2)
**Steps to reproduce:**
1. Expand one ADLS Gen2 storage account -> Blob Containers.
2. Select one blob container which contains one blob at least.
3. Right click one blob and select 'Manage Access...'.
4. Check the Manage Access dialog.
**Expect Experience:**
The Manage Access dialog shows friendly.
**Actual Experience:**
The Manage Access dialog shows unfriendly.
**More Info:**
1. For ADLS Gen2 blob container & ADLS Gen2 folder, the Manage Access dialog shows like below.
| test | the manage access dialog for one adls blob shows unfriendly storage explorer version build branch dev marayerm packaging platform os windows linux ubuntu macos high sierra architecture regression from previous build steps to reproduce expand one adls storage account blob containers select one blob container which contains one blob at least right click one blob and select manage access check the manage access dialog expect experience the manage access dialog shows friendly actual experience the manage access dialog shows unfriendly more info for adls blob container adls folder the manage access dialog shows like below | 1 |
160,592 | 12,517,287,909 | IssuesEvent | 2020-06-03 10:52:18 | aliasrobotics/RVD | https://api.github.com/repos/aliasrobotics/RVD | closed | RVD#2208: Using Binary to parse untrusted XML data is known to be vulnerable to XM..., /opt/ros_melodic_ws/src/ros_comm/rosparam/src/rosparam/__init__.py:59 | bandit bug duplicate invalid static analysis testing triage | ```yaml
{
"id": 2208,
"title": "RVD#2208: Using Binary to parse untrusted XML data is known to be vulnerable to XM..., /opt/ros_melodic_ws/src/ros_comm/rosparam/src/rosparam/__init__.py:59",
"type": "bug",
"description": "HIGH confidence of HIGH severity bug. Using Binary to parse untrusted XML data is known to be vulnerable to XML attacks. Use defused.xmlrpc.monkey_patch() function to monkey-patch xmlrpclib and mitigate XML vulnerabilities. at /opt/ros_melodic_ws/src/ros_comm/rosparam/src/rosparam/__init__.py:59 See links for more info on the bug.",
"cwe": "None",
"cve": "None",
"keywords": [
"bandit",
"bug",
"static analysis",
"testing",
"triage",
"bug"
],
"system": "",
"vendor": null,
"severity": {
"rvss-score": 0,
"rvss-vector": "",
"severity-description": "",
"cvss-score": 0,
"cvss-vector": ""
},
"links": [
"https://github.com/aliasrobotics/RVD/issues/2208",
"https://bandit.readthedocs.io/en/latest/blacklists/blacklist_imports.html#b411-import-xmlrpclib"
],
"flaw": {
"phase": "testing",
"specificity": "subject-specific",
"architectural-location": "application-specific",
"application": "N/A",
"subsystem": "N/A",
"package": "N/A",
"languages": "None",
"date-detected": "2020-06-02 (10:34)",
"detected-by": "Alias Robotics",
"detected-by-method": "testing static",
"date-reported": "2020-06-02 (10:34)",
"reported-by": "Alias Robotics",
"reported-by-relationship": "automatic",
"issue": "https://github.com/aliasrobotics/RVD/issues/2208",
"reproducibility": "always",
"trace": "/opt/ros_melodic_ws/src/ros_comm/rosparam/src/rosparam/__init__.py:59",
"reproduction": "See artifacts below (if available)",
"reproduction-image": ""
},
"exploitation": {
"description": "",
"exploitation-image": "",
"exploitation-vector": ""
},
"mitigation": {
"description": "",
"pull-request": "",
"date-mitigation": ""
}
}
``` | 1.0 | RVD#2208: Using Binary to parse untrusted XML data is known to be vulnerable to XM..., /opt/ros_melodic_ws/src/ros_comm/rosparam/src/rosparam/__init__.py:59 - ```yaml
{
"id": 2208,
"title": "RVD#2208: Using Binary to parse untrusted XML data is known to be vulnerable to XM..., /opt/ros_melodic_ws/src/ros_comm/rosparam/src/rosparam/__init__.py:59",
"type": "bug",
"description": "HIGH confidence of HIGH severity bug. Using Binary to parse untrusted XML data is known to be vulnerable to XML attacks. Use defused.xmlrpc.monkey_patch() function to monkey-patch xmlrpclib and mitigate XML vulnerabilities. at /opt/ros_melodic_ws/src/ros_comm/rosparam/src/rosparam/__init__.py:59 See links for more info on the bug.",
"cwe": "None",
"cve": "None",
"keywords": [
"bandit",
"bug",
"static analysis",
"testing",
"triage",
"bug"
],
"system": "",
"vendor": null,
"severity": {
"rvss-score": 0,
"rvss-vector": "",
"severity-description": "",
"cvss-score": 0,
"cvss-vector": ""
},
"links": [
"https://github.com/aliasrobotics/RVD/issues/2208",
"https://bandit.readthedocs.io/en/latest/blacklists/blacklist_imports.html#b411-import-xmlrpclib"
],
"flaw": {
"phase": "testing",
"specificity": "subject-specific",
"architectural-location": "application-specific",
"application": "N/A",
"subsystem": "N/A",
"package": "N/A",
"languages": "None",
"date-detected": "2020-06-02 (10:34)",
"detected-by": "Alias Robotics",
"detected-by-method": "testing static",
"date-reported": "2020-06-02 (10:34)",
"reported-by": "Alias Robotics",
"reported-by-relationship": "automatic",
"issue": "https://github.com/aliasrobotics/RVD/issues/2208",
"reproducibility": "always",
"trace": "/opt/ros_melodic_ws/src/ros_comm/rosparam/src/rosparam/__init__.py:59",
"reproduction": "See artifacts below (if available)",
"reproduction-image": ""
},
"exploitation": {
"description": "",
"exploitation-image": "",
"exploitation-vector": ""
},
"mitigation": {
"description": "",
"pull-request": "",
"date-mitigation": ""
}
}
``` | test | rvd using binary to parse untrusted xml data is known to be vulnerable to xm opt ros melodic ws src ros comm rosparam src rosparam init py yaml id title rvd using binary to parse untrusted xml data is known to be vulnerable to xm opt ros melodic ws src ros comm rosparam src rosparam init py type bug description high confidence of high severity bug using binary to parse untrusted xml data is known to be vulnerable to xml attacks use defused xmlrpc monkey patch function to monkey patch xmlrpclib and mitigate xml vulnerabilities at opt ros melodic ws src ros comm rosparam src rosparam init py see links for more info on the bug cwe none cve none keywords bandit bug static analysis testing triage bug system vendor null severity rvss score rvss vector severity description cvss score cvss vector links flaw phase testing specificity subject specific architectural location application specific application n a subsystem n a package n a languages none date detected detected by alias robotics detected by method testing static date reported reported by alias robotics reported by relationship automatic issue reproducibility always trace opt ros melodic ws src ros comm rosparam src rosparam init py reproduction see artifacts below if available reproduction image exploitation description exploitation image exploitation vector mitigation description pull request date mitigation | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.