Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3 values | title stringlengths 1 844 | labels stringlengths 4 721 | body stringlengths 1 261k | index stringclasses 12 values | text_combine stringlengths 96 261k | label stringclasses 2 values | text stringlengths 96 248k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
270,509 | 20,602,561,880 | IssuesEvent | 2022-03-06 13:49:39 | Haltroy/Yorot | https://api.github.com/repos/Haltroy/Yorot | closed | Win32 - Status | documentation win-nt news | # Status
I know that there's a giant gap starting from May and ending end of October, there are multiple reasons why. The first reason is that I'm also a student so I also have to work on my exams (they start in 15th of November again so I might disappear for 2 weeks again) and a family member of my family (shocking right?) and a friend of people that I used to meet IRL (we now meet in dc) so I was busy with a lot of stuff at that time. Also, the first commit after that long time is just work that was done in that month (plus some work done in other months when ı had time). But now, I'm slowly starting to work on this project and I want it to actually stay stable unlike it's predecessor "Korot".
If the Win32 works as I intended to, I'm going to start porting the entire thing to Avalonia. The method of adding controls will stay same (just check any .Designer.cs in any WİnForms code) for the first version (for testing) then they'll be added to XML file. (I hope we can dynamically add controls to Avalonia ?forms? otherwise we just skip to the hard one which is the second phase.)
Some features (Sync with Web, ChildSafe etc.) might end up on the second version because I really want to finish the first version first then add crazy features later. And no, Sync and ChildSafe is not going to be the only features that are going to be added, I'm also thinking about more theme customization (change background for an image etc.), a "Yorot Virtual Drive" for protecting data from outside (need to find a good encryption method that only that Yorot flavor can see and it shouldn't be easy to spot like looking at the source code to learn at least where it is stored) and a "GroundWorks" project so App/Extension developers don't have to make their add-ons in HTML+JS but instead HTML+JS+C# (HTML file that can launch C# under the ground, that's why I called this "Ground Works") which can be easily integrated to any flavor.
Oh yeah, also thinking about codenames for versions. Sadly, the first release will have "indev1" but I'm thinking about Ubuntu's (the OS) approach on names but I'm going to use Greek alphabet names instead of animal names ("Arctic Alpha", "Bliss Beta", etc.) for each major version. Still a thought, might not be a real deal on first stable release.
EDIT: I deleted "iOS" and "macOS" labels since I really **don't** want to release them on **literal 1984 that we call Apple**. If I do that, they will take Yorot down because "it was competing with Safari" or "is a threat for the ""ecosystem""™". So unless you really want an *actual* release for that platforms, ask the **Big Brother of Modern Computer Software that made fun of IBM for acting like the Big Brother in 80's**™ (I'm not joking, after these I always laugh at that Macintosh ad) to allow non-OSX users to edit files without requiring a Mac and don't ban stuff because they were too lazy to compete with it. Yes I hate them despite their good history and yes I prefer 80s of that company to 20xx's of that same company.
# TODOs:
- [ ] Finish all TODOs inside of the code.
- [ ] #31
- [ ] #2
- [ ] #20
- [ ] OOBE | 1.0 | Win32 - Status - # Status
I know that there's a giant gap starting from May and ending end of October, there are multiple reasons why. The first reason is that I'm also a student so I also have to work on my exams (they start in 15th of November again so I might disappear for 2 weeks again) and a family member of my family (shocking right?) and a friend of people that I used to meet IRL (we now meet in dc) so I was busy with a lot of stuff at that time. Also, the first commit after that long time is just work that was done in that month (plus some work done in other months when ı had time). But now, I'm slowly starting to work on this project and I want it to actually stay stable unlike it's predecessor "Korot".
If the Win32 works as I intended to, I'm going to start porting the entire thing to Avalonia. The method of adding controls will stay same (just check any .Designer.cs in any WİnForms code) for the first version (for testing) then they'll be added to XML file. (I hope we can dynamically add controls to Avalonia ?forms? otherwise we just skip to the hard one which is the second phase.)
Some features (Sync with Web, ChildSafe etc.) might end up on the second version because I really want to finish the first version first then add crazy features later. And no, Sync and ChildSafe is not going to be the only features that are going to be added, I'm also thinking about more theme customization (change background for an image etc.), a "Yorot Virtual Drive" for protecting data from outside (need to find a good encryption method that only that Yorot flavor can see and it shouldn't be easy to spot like looking at the source code to learn at least where it is stored) and a "GroundWorks" project so App/Extension developers don't have to make their add-ons in HTML+JS but instead HTML+JS+C# (HTML file that can launch C# under the ground, that's why I called this "Ground Works") which can be easily integrated to any flavor.
Oh yeah, also thinking about codenames for versions. Sadly, the first release will have "indev1" but I'm thinking about Ubuntu's (the OS) approach on names but I'm going to use Greek alphabet names instead of animal names ("Arctic Alpha", "Bliss Beta", etc.) for each major version. Still a thought, might not be a real deal on first stable release.
EDIT: I deleted "iOS" and "macOS" labels since I really **don't** want to release them on **literal 1984 that we call Apple**. If I do that, they will take Yorot down because "it was competing with Safari" or "is a threat for the ""ecosystem""™". So unless you really want an *actual* release for that platforms, ask the **Big Brother of Modern Computer Software that made fun of IBM for acting like the Big Brother in 80's**™ (I'm not joking, after these I always laugh at that Macintosh ad) to allow non-OSX users to edit files without requiring a Mac and don't ban stuff because they were too lazy to compete with it. Yes I hate them despite their good history and yes I prefer 80s of that company to 20xx's of that same company.
# TODOs:
- [ ] Finish all TODOs inside of the code.
- [ ] #31
- [ ] #2
- [ ] #20
- [ ] OOBE | non_priority | status status i know that there s a giant gap starting from may and ending end of october there are multiple reasons why the first reason is that i m also a student so i also have to work on my exams they start in of november again so i might disappear for weeks again and a family member of my family shocking right and a friend of people that i used to meet irl we now meet in dc so i was busy with a lot of stuff at that time also the first commit after that long time is just work that was done in that month plus some work done in other months when ı had time but now i m slowly starting to work on this project and i want it to actually stay stable unlike it s predecessor korot if the works as i intended to i m going to start porting the entire thing to avalonia the method of adding controls will stay same just check any designer cs in any wi̇nforms code for the first version for testing then they ll be added to xml file i hope we can dynamically add controls to avalonia forms otherwise we just skip to the hard one which is the second phase some features sync with web childsafe etc might end up on the second version because i really want to finish the first version first then add crazy features later and no sync and childsafe is not going to be the only features that are going to be added i m also thinking about more theme customization change background for an image etc a yorot virtual drive for protecting data from outside need to find a good encryption method that only that yorot flavor can see and it shouldn t be easy to spot like looking at the source code to learn at least where it is stored and a groundworks project so app extension developers don t have to make their add ons in html js but instead html js c html file that can launch c under the ground that s why i called this ground works which can be easily integrated to any flavor oh yeah also thinking about codenames for versions sadly the first release will have but i m thinking about ubuntu s the os approach on names but i m going to use greek alphabet names instead of animal names arctic alpha bliss beta etc for each major version still a thought might not be a real deal on first stable release edit i deleted ios and macos labels since i really don t want to release them on literal that we call apple if i do that they will take yorot down because it was competing with safari or is a threat for the ecosystem ™ so unless you really want an actual release for that platforms ask the big brother of modern computer software that made fun of ibm for acting like the big brother in s ™ i m not joking after these i always laugh at that macintosh ad to allow non osx users to edit files without requiring a mac and don t ban stuff because they were too lazy to compete with it yes i hate them despite their good history and yes i prefer of that company to s of that same company todos finish all todos inside of the code oobe | 0 |
23,051 | 11,816,717,339 | IssuesEvent | 2020-03-20 09:38:05 | flutter/flutter | https://api.github.com/repos/flutter/flutter | closed | Performance issues between versions | framework severe: performance waiting for customer response | Hello everyone, I have a map application using flutter_map, I have the following scenario: when I use v1.5.4-hotfix.2 the application does not present any performance problems, but when I do it with flutter v1.7.8 + hotfix.3 or v1 .7.8 + hotfix.4 the application becomes slow even until it hangs. Any suggestions will be very grateful | True | Performance issues between versions - Hello everyone, I have a map application using flutter_map, I have the following scenario: when I use v1.5.4-hotfix.2 the application does not present any performance problems, but when I do it with flutter v1.7.8 + hotfix.3 or v1 .7.8 + hotfix.4 the application becomes slow even until it hangs. Any suggestions will be very grateful | non_priority | performance issues between versions hello everyone i have a map application using flutter map i have the following scenario when i use hotfix the application does not present any performance problems but when i do it with flutter hotfix or hotfix the application becomes slow even until it hangs any suggestions will be very grateful | 0 |
152,925 | 19,700,189,303 | IssuesEvent | 2022-01-12 15:55:38 | TIBCOSoftware/MqttStreamUsingNanoscale | https://api.github.com/repos/TIBCOSoftware/MqttStreamUsingNanoscale | opened | CVE-2020-28469 (High) detected in glob-parent-2.0.0.tgz, glob-parent-3.1.0.tgz | security vulnerability | ## CVE-2020-28469 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>glob-parent-2.0.0.tgz</b>, <b>glob-parent-3.1.0.tgz</b></p></summary>
<p>
<details><summary><b>glob-parent-2.0.0.tgz</b></p></summary>
<p>Strips glob magic from a string to provide the parent path</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-2.0.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-2.0.0.tgz</a></p>
<p>Path to dependency file: /MqttStreamUsingNanoscale/package.json</p>
<p>Path to vulnerable library: /node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- app-scripts-0.0.45.tgz (Root Library)
- chokidar-1.6.1.tgz
- :x: **glob-parent-2.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-3.1.0.tgz</b></p></summary>
<p>Strips glob magic from a string to provide the parent directory path</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p>
<p>Path to dependency file: /MqttStreamUsingNanoscale/package.json</p>
<p>Path to vulnerable library: /node_modules/watchpack/node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- app-scripts-0.0.45.tgz (Root Library)
- webpack-2.7.0.tgz
- watchpack-1.6.0.tgz
- chokidar-2.1.6.tgz
- :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
This affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.
<p>Publish Date: 2021-06-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28469>CVE-2020-28469</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469</a></p>
<p>Release Date: 2021-06-03</p>
<p>Fix Resolution: glob-parent - 5.1.2</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"glob-parent","packageVersion":"2.0.0","packageFilePaths":["/MqttStreamUsingNanoscale/package.json"],"isTransitiveDependency":true,"dependencyTree":"@ionic/app-scripts:0.0.45;chokidar:1.6.1;glob-parent:2.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"glob-parent - 5.1.2","isBinary":false},{"packageType":"javascript/Node.js","packageName":"glob-parent","packageVersion":"3.1.0","packageFilePaths":["/MqttStreamUsingNanoscale/package.json"],"isTransitiveDependency":true,"dependencyTree":"@ionic/app-scripts:0.0.45;webpack:2.7.0;watchpack:1.6.0;chokidar:2.1.6;glob-parent:3.1.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"glob-parent - 5.1.2","isBinary":false}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2020-28469","vulnerabilityDetails":"This affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28469","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-28469 (High) detected in glob-parent-2.0.0.tgz, glob-parent-3.1.0.tgz - ## CVE-2020-28469 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>glob-parent-2.0.0.tgz</b>, <b>glob-parent-3.1.0.tgz</b></p></summary>
<p>
<details><summary><b>glob-parent-2.0.0.tgz</b></p></summary>
<p>Strips glob magic from a string to provide the parent path</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-2.0.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-2.0.0.tgz</a></p>
<p>Path to dependency file: /MqttStreamUsingNanoscale/package.json</p>
<p>Path to vulnerable library: /node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- app-scripts-0.0.45.tgz (Root Library)
- chokidar-1.6.1.tgz
- :x: **glob-parent-2.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-3.1.0.tgz</b></p></summary>
<p>Strips glob magic from a string to provide the parent directory path</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p>
<p>Path to dependency file: /MqttStreamUsingNanoscale/package.json</p>
<p>Path to vulnerable library: /node_modules/watchpack/node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- app-scripts-0.0.45.tgz (Root Library)
- webpack-2.7.0.tgz
- watchpack-1.6.0.tgz
- chokidar-2.1.6.tgz
- :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
This affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.
<p>Publish Date: 2021-06-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28469>CVE-2020-28469</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469</a></p>
<p>Release Date: 2021-06-03</p>
<p>Fix Resolution: glob-parent - 5.1.2</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"glob-parent","packageVersion":"2.0.0","packageFilePaths":["/MqttStreamUsingNanoscale/package.json"],"isTransitiveDependency":true,"dependencyTree":"@ionic/app-scripts:0.0.45;chokidar:1.6.1;glob-parent:2.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"glob-parent - 5.1.2","isBinary":false},{"packageType":"javascript/Node.js","packageName":"glob-parent","packageVersion":"3.1.0","packageFilePaths":["/MqttStreamUsingNanoscale/package.json"],"isTransitiveDependency":true,"dependencyTree":"@ionic/app-scripts:0.0.45;webpack:2.7.0;watchpack:1.6.0;chokidar:2.1.6;glob-parent:3.1.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"glob-parent - 5.1.2","isBinary":false}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2020-28469","vulnerabilityDetails":"This affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28469","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in glob parent tgz glob parent tgz cve high severity vulnerability vulnerable libraries glob parent tgz glob parent tgz glob parent tgz strips glob magic from a string to provide the parent path library home page a href path to dependency file mqttstreamusingnanoscale package json path to vulnerable library node modules glob parent package json dependency hierarchy app scripts tgz root library chokidar tgz x glob parent tgz vulnerable library glob parent tgz strips glob magic from a string to provide the parent directory path library home page a href path to dependency file mqttstreamusingnanoscale package json path to vulnerable library node modules watchpack node modules glob parent package json dependency hierarchy app scripts tgz root library webpack tgz watchpack tgz chokidar tgz x glob parent tgz vulnerable library vulnerability details this affects the package glob parent before the enclosure regex used to check for strings ending in enclosure containing path separator publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution glob parent isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree ionic app scripts chokidar glob parent isminimumfixversionavailable true minimumfixversion glob parent isbinary false packagetype javascript node js packagename glob parent packageversion packagefilepaths istransitivedependency true dependencytree ionic app scripts webpack watchpack chokidar glob parent isminimumfixversionavailable true minimumfixversion glob parent isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails this affects the package glob parent before the enclosure regex used to check for strings ending in enclosure containing path separator vulnerabilityurl | 0 |
42,207 | 17,082,886,021 | IssuesEvent | 2021-07-08 08:08:09 | getferdi/ferdi | https://api.github.com/repos/getferdi/ferdi | closed | No badge notification for Messenger | bug service-specific | **Bug description:**
No notification badge appears on new messages from Messenger. I've tried 5.5.0 and 5.6.0-beta.
**Steps to reproduce:**
Add Messenger service get a new message?
**Expected behavior**
Notification badge should appear
**Screenshots**
<!-- If applicable, add screenshots to help explain your problem. -->
<!-- You can simply drag and drop any image file into the editor to add it to the report -->
**Environment:**
- Operating System: Windows 10 H2 & MacOS Big Sur 11.0.1
- Ferdi Version: 5.5.0 & 5.6.0-beta2
- Server: Using without an account | 1.0 | No badge notification for Messenger - **Bug description:**
No notification badge appears on new messages from Messenger. I've tried 5.5.0 and 5.6.0-beta.
**Steps to reproduce:**
Add Messenger service get a new message?
**Expected behavior**
Notification badge should appear
**Screenshots**
<!-- If applicable, add screenshots to help explain your problem. -->
<!-- You can simply drag and drop any image file into the editor to add it to the report -->
**Environment:**
- Operating System: Windows 10 H2 & MacOS Big Sur 11.0.1
- Ferdi Version: 5.5.0 & 5.6.0-beta2
- Server: Using without an account | non_priority | no badge notification for messenger bug description no notification badge appears on new messages from messenger i ve tried and beta steps to reproduce add messenger service get a new message expected behavior notification badge should appear screenshots environment operating system windows macos big sur ferdi version server using without an account | 0 |
152,221 | 23,933,855,055 | IssuesEvent | 2022-09-11 00:03:37 | elastic/eui | https://api.github.com/repos/elastic/eui | closed | [Navigation] Secondary navigation flyout component | assign:designer discussion stale-issue stale-issue-closed | **Background:**
We’re undergoing a re-organization of the information architecture in the security app. We believe (and have received feedback) that the app in its current state is unwieldy and hard to navigate. This is becoming increasingly apparent as we add more capabilities and fold in features from our recent acquisitions of build.security and cmd.
We’d like a way to streamline the side navigation and de-clutter it while still making sure that our core workflows are easily discoverable and accessible. To that point, we have proposed a UI mechanism that augments the side navigation in the hope of achieving these goals. We have received positive feedback from all stakeholders in security and are ready to discuss logistics of implementation. It was suggested that we reach out to the EUI team to talk this through.
**The mechanism:**
This is an icon on the right of the side nav pane that’s inline with items with secondary navigation
<img width="162" alt="image" src="https://user-images.githubusercontent.com/48926600/157069217-7790c0d5-e40d-480b-8c0a-1d53fc1699f5.png">
**Examples of how this would look:**
Alerts — https://www.figma.com/file/oqSuZ399Lcdmnrha2OkIqT/Presentation?node-id=702%3A235861
Dashboards — https://www.figma.com/file/oqSuZ399Lcdmnrha2OkIqT/Presentation?node-id=702%3A233789
Configurations — https://www.figma.com/file/oqSuZ399Lcdmnrha2OkIqT/Presentation?node-id=702%3A237756
**Assets of note:**
GH issue — https://github.com/elastic/security-design-team/discussions/24#discussioncomment-2199665
Figma file — https://www.figma.com/file/oqSuZ399Lcdmnrha2OkIqT/Presentation?node-id=370%3A229493 | 1.0 | [Navigation] Secondary navigation flyout component - **Background:**
We’re undergoing a re-organization of the information architecture in the security app. We believe (and have received feedback) that the app in its current state is unwieldy and hard to navigate. This is becoming increasingly apparent as we add more capabilities and fold in features from our recent acquisitions of build.security and cmd.
We’d like a way to streamline the side navigation and de-clutter it while still making sure that our core workflows are easily discoverable and accessible. To that point, we have proposed a UI mechanism that augments the side navigation in the hope of achieving these goals. We have received positive feedback from all stakeholders in security and are ready to discuss logistics of implementation. It was suggested that we reach out to the EUI team to talk this through.
**The mechanism:**
This is an icon on the right of the side nav pane that’s inline with items with secondary navigation
<img width="162" alt="image" src="https://user-images.githubusercontent.com/48926600/157069217-7790c0d5-e40d-480b-8c0a-1d53fc1699f5.png">
**Examples of how this would look:**
Alerts — https://www.figma.com/file/oqSuZ399Lcdmnrha2OkIqT/Presentation?node-id=702%3A235861
Dashboards — https://www.figma.com/file/oqSuZ399Lcdmnrha2OkIqT/Presentation?node-id=702%3A233789
Configurations — https://www.figma.com/file/oqSuZ399Lcdmnrha2OkIqT/Presentation?node-id=702%3A237756
**Assets of note:**
GH issue — https://github.com/elastic/security-design-team/discussions/24#discussioncomment-2199665
Figma file — https://www.figma.com/file/oqSuZ399Lcdmnrha2OkIqT/Presentation?node-id=370%3A229493 | non_priority | secondary navigation flyout component background we’re undergoing a re organization of the information architecture in the security app we believe and have received feedback that the app in its current state is unwieldy and hard to navigate this is becoming increasingly apparent as we add more capabilities and fold in features from our recent acquisitions of build security and cmd we’d like a way to streamline the side navigation and de clutter it while still making sure that our core workflows are easily discoverable and accessible to that point we have proposed a ui mechanism that augments the side navigation in the hope of achieving these goals we have received positive feedback from all stakeholders in security and are ready to discuss logistics of implementation it was suggested that we reach out to the eui team to talk this through the mechanism this is an icon on the right of the side nav pane that’s inline with items with secondary navigation img width alt image src examples of how this would look alerts — dashboards — configurations — assets of note gh issue — figma file — | 0 |
6,111 | 3,002,711,852 | IssuesEvent | 2015-07-24 18:49:41 | matplotlib/matplotlib | https://api.github.com/repos/matplotlib/matplotlib | closed | Plots missing from http://matplotlib.org/devdocs/users/colormaps.html | Documentation | Looks like the documentation was rebuild without scikit image.
The master branch no longer requires scikit image but the 1.4.3 branch does to build these docs.
| 1.0 | Plots missing from http://matplotlib.org/devdocs/users/colormaps.html - Looks like the documentation was rebuild without scikit image.
The master branch no longer requires scikit image but the 1.4.3 branch does to build these docs.
| non_priority | plots missing from looks like the documentation was rebuild without scikit image the master branch no longer requires scikit image but the branch does to build these docs | 0 |
93,566 | 15,895,256,462 | IssuesEvent | 2021-04-11 13:22:39 | rammatzkvosky/caseflow | https://api.github.com/repos/rammatzkvosky/caseflow | opened | CVE-2020-24025 (Medium) detected in node-sass-4.14.1.tgz | security vulnerability | ## CVE-2020-24025 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-sass-4.14.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz</a></p>
<p>Path to dependency file: caseflow/client/package.json</p>
<p>Path to vulnerable library: caseflow/client/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.14.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rammatzkvosky/caseflow/commit/8f9f47fb6b371540f9f6b5421908ffe6200fad09">8f9f47fb6b371540f9f6b5421908ffe6200fad09</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Certificate validation in node-sass 2.0.0 to 4.14.1 is disabled when requesting binaries even if the user is not specifying an alternative download path.
<p>Publish Date: 2021-01-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-24025>CVE-2020-24025</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.14.1","packageFilePaths":["/client/package.json"],"isTransitiveDependency":false,"dependencyTree":"node-sass:4.14.1","isMinimumFixVersionAvailable":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-24025","vulnerabilityDetails":"Certificate validation in node-sass 2.0.0 to 4.14.1 is disabled when requesting binaries even if the user is not specifying an alternative download path.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-24025","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-24025 (Medium) detected in node-sass-4.14.1.tgz - ## CVE-2020-24025 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-sass-4.14.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz</a></p>
<p>Path to dependency file: caseflow/client/package.json</p>
<p>Path to vulnerable library: caseflow/client/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.14.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rammatzkvosky/caseflow/commit/8f9f47fb6b371540f9f6b5421908ffe6200fad09">8f9f47fb6b371540f9f6b5421908ffe6200fad09</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Certificate validation in node-sass 2.0.0 to 4.14.1 is disabled when requesting binaries even if the user is not specifying an alternative download path.
<p>Publish Date: 2021-01-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-24025>CVE-2020-24025</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.14.1","packageFilePaths":["/client/package.json"],"isTransitiveDependency":false,"dependencyTree":"node-sass:4.14.1","isMinimumFixVersionAvailable":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-24025","vulnerabilityDetails":"Certificate validation in node-sass 2.0.0 to 4.14.1 is disabled when requesting binaries even if the user is not specifying an alternative download path.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-24025","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in node sass tgz cve medium severity vulnerability vulnerable library node sass tgz wrapper around libsass library home page a href path to dependency file caseflow client package json path to vulnerable library caseflow client node modules node sass package json dependency hierarchy x node sass tgz vulnerable library found in head commit a href found in base branch master vulnerability details certificate validation in node sass to is disabled when requesting binaries even if the user is not specifying an alternative download path publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact low availability impact none for more information on scores click a href isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree node sass isminimumfixversionavailable false basebranches vulnerabilityidentifier cve vulnerabilitydetails certificate validation in node sass to is disabled when requesting binaries even if the user is not specifying an alternative download path vulnerabilityurl | 0 |
13,898 | 16,657,576,408 | IssuesEvent | 2021-06-05 20:14:08 | laugharn/link | https://api.github.com/repos/laugharn/link | closed | Persist Front-End User Data | kind/improvement process/selected size/sm team/front | Waiting for the user response from a cold lambda is visually annoying. We should persist that data with some kind of local storage that is more expansive than a cookie but more secure than normal local storage.
- [x] Use localforage to persist user data
- [x] Clear the persisted data when a user is not authenticated or logs out. | 1.0 | Persist Front-End User Data - Waiting for the user response from a cold lambda is visually annoying. We should persist that data with some kind of local storage that is more expansive than a cookie but more secure than normal local storage.
- [x] Use localforage to persist user data
- [x] Clear the persisted data when a user is not authenticated or logs out. | non_priority | persist front end user data waiting for the user response from a cold lambda is visually annoying we should persist that data with some kind of local storage that is more expansive than a cookie but more secure than normal local storage use localforage to persist user data clear the persisted data when a user is not authenticated or logs out | 0 |
32,648 | 15,560,066,736 | IssuesEvent | 2021-03-16 12:18:28 | treeverse/lakeFS | https://api.github.com/repos/treeverse/lakeFS | closed | Cache GetRepository, GetCommitByPrefix and GetCommit | performance | All these are in the critical path of most requests and are prime candidates for caching. Currently 50% of the time is spent on those for random reads.
To generate random read load:
`lakectl abuse random-read lakefs://repo1@a67a8fa0cfc598859a46ef652800f9d4e2d70db41a78c27f1500193118156068 --amount 1000000 --from-file ./randomfiles --parallelism $(nproc)`
While executing, generating a pprof profile using `http://<LAKEFS ADDR>/_pprof` and download a profile.
Commenting out the DB requests from these functions and returning a static repository/commit object increased throughput from ~11.5k r/s to ~18k r/s
| True | Cache GetRepository, GetCommitByPrefix and GetCommit - All these are in the critical path of most requests and are prime candidates for caching. Currently 50% of the time is spent on those for random reads.
To generate random read load:
`lakectl abuse random-read lakefs://repo1@a67a8fa0cfc598859a46ef652800f9d4e2d70db41a78c27f1500193118156068 --amount 1000000 --from-file ./randomfiles --parallelism $(nproc)`
While executing, generating a pprof profile using `http://<LAKEFS ADDR>/_pprof` and download a profile.
Commenting out the DB requests from these functions and returning a static repository/commit object increased throughput from ~11.5k r/s to ~18k r/s
| non_priority | cache getrepository getcommitbyprefix and getcommit all these are in the critical path of most requests and are prime candidates for caching currently of the time is spent on those for random reads to generate random read load lakectl abuse random read lakefs amount from file randomfiles parallelism nproc while executing generating a pprof profile using addr pprof and download a profile commenting out the db requests from these functions and returning a static repository commit object increased throughput from r s to r s | 0 |
61,184 | 14,943,008,803 | IssuesEvent | 2021-01-25 22:14:27 | hashicorp/packer | https://api.github.com/repos/hashicorp/packer | closed | Error during pushing docker image to ECR after updating to the new version | bug builder/docker regression track-internal | Hi,
I faced the issue during pushing the docker image to ECR after updating the packer version from 1.5.4 to 1.6.5. As for now, I rollbacked the version to 1.5.4
Here is packer-1.6.5:
```
==> docker.base: Provisioning with shell script: /tmp/packer-shell485448421
==> docker.base: Committing the container
docker.base: Image ID: sha256:d1ab9a4eaf3729dc838460702674320624641b0dd2d7794d8a643f25e61e4ad3
==> docker.base: Killing the container: 22156c60d9a54391829832ccb4c833bf235af6ccf131845a46fcd3c13c8539e8
==> docker.base: Running post-processor: (type docker-tag)
==> docker.base (docker-tag): Deprecation warning: "tag" option has been replaced with "tags". In future versions of Packer, this configuration may not work. Please call `packer fix` on your template to update.
docker.base (docker-tag): Tagging image: sha256:d1ab9a4eaf3729dc838460702674320624641b0dd2d7794d8a643f25e61e4ad3
docker.base (docker-tag): Repository: ************.dkr.ecr.us-east-1.amazonaws.com/zevs:07Nov20201647
==> docker.base: Running post-processor: (type docker-push)
docker.base (docker-push): Fetching ECR credentials...
docker.base (docker-push): Logging in...
docker.base (docker-push): WARNING! Your password will be stored unencrypted in /home/aston-r/.docker/config.json.
docker.base (docker-push): Configure a credential helper to remove this warning. See
docker.base (docker-push): https://docs.docker.com/engine/reference/commandline/login/#credentials-store
docker.base (docker-push): Login Succeeded
docker.base (docker-push): Pushing: sha256:d1ab9a4eaf3729dc838460702674320624641b0dd2d7794d8a643f25e61e4ad3
docker.base (docker-push): The push refers to repository [docker.io/library/sha256] <----!!!!!!!!!!!
docker.base (docker-push): An image does not exist locally with the tag: sha256 <----!!!!!!!!!!!
docker.base (docker-push): Logging out...
docker.base (docker-push): Removing login credentials for ************.dkr.ecr.us-east-1.amazonaws.com
```
Here is packer-1.5.4:
```
docker: Provisioning with shell script: /tmp/packer-shell594000477
==> docker: Committing the container
docker: Image ID: sha256:fd4911057124d247748de8661ced48132ffe9119999f0e6e1d8b3177ab4bd6a6
==> docker: Killing the container: e79bf9656518c8393ab522e5610ca66249b72c069ad4145569388ea1bb89bd20
==> docker: Running post-processor: (type docker-tag)
docker (docker-tag): Tagging image: sha256:fd4911057124d247748de8661ced48132ffe9119999f0e6e1d8b3177ab4bd6a6
docker (docker-tag): Repository: ************.dkr.ecr.us-east-1.amazonaws.com/zevs:07Nov20201631
==> docker: Running post-processor: (type docker-push)
docker (docker-push): Fetching ECR credentials...
docker (docker-push): Logging in...
docker (docker-push): Login Succeeded
docker (docker-push): WARNING! Your password will be stored unencrypted in /home/aston-r/.docker/config.json.
docker (docker-push): Configure a credential helper to remove this warning. See
docker (docker-push): https://docs.docker.com/engine/reference/commandline/login/#credentials-store
docker (docker-push): Pushing: ************.dkr.ecr.us-east-1.amazonaws.com/zevs:07Nov20201631
docker (docker-push): The push refers to repository [************.dkr.ecr.us-east-1.amazonaws.com/zevs]
docker (docker-push): d6dae3c01d10: Preparing
docker (docker-push): 292349d27210: Preparing
docker (docker-push): 6360407af3e7: Preparing
docker (docker-push): 68aa0de28940: Preparing
docker (docker-push): f04cc38c0ac2: Preparing
docker (docker-push): ace0eda3e3be: Preparing
docker (docker-push): ace0eda3e3be: Waiting
docker (docker-push): 6360407af3e7: Pushed
docker (docker-push): f04cc38c0ac2: Pushed
docker (docker-push): 292349d27210: Pushed
docker (docker-push): ace0eda3e3be: Pushed
docker (docker-push): 68aa0de28940: Pushed
docker (docker-push): d6dae3c01d10: Pushed
docker (docker-push): 07Nov20201631: digest: sha256:f4e81ab4e1a5fdf9236413ad5a71fa3707431487d48394fe9931242ebc8a729a size: 1581
docker (docker-push): Logging out...
docker (docker-push): Removing login credentials for ************.dkr.ecr.us-east-1.amazonaws.com
Build 'docker' finished.
==> Builds finished. The artifacts of successful builds are:
--> docker: Imported Docker image: sha256:fd4911057124d247748de8661ced48132ffe9119999f0e6e1d8b3177ab4bd6a6
--> docker: Imported Docker image: ************.dkr.ecr.us-east-1.amazonaws.com/zevs:07Nov20201631
--> docker: Imported Docker image: ************.dkr.ecr.us-east-1.amazonaws.com/zevs:07Nov20201631
```
I am using the HCL2 template to build the image. Here is a part of it:
```
build {
sources = ["source.docker.base"]
provisioner "ansible" {
playbook_file = "prepare.yml"
user = "root"
}
provisioner "ansible" {
playbook_file = "main.yml"
user = "zevs"
galaxy_file = "requirements.yml"
galaxy_force_install = true
extra_arguments = ["--extra-vars", "target=all"]
}
provisioner "shell" {
inline = ["rm -rf /var/cache/apk /home/zevs/.ansible /root/.ansible"]
}
post-processor "docker-tag" {
repository = local.repo
tag = [formatdate("DDMMMYYYYhhmm", timestamp())]
}
post-processor "docker-push" {
ecr_login = true
login_server = var.registry
}
}
```
I also attached the part of the log with `PACKER_LOG=1` I tried to use tags just in case in docker-tag, but it did not help.
[packer-build.log](https://github.com/hashicorp/packer/files/5505201/packer-build.log)
| 1.0 | Error during pushing docker image to ECR after updating to the new version - Hi,
I faced the issue during pushing the docker image to ECR after updating the packer version from 1.5.4 to 1.6.5. As for now, I rollbacked the version to 1.5.4
Here is packer-1.6.5:
```
==> docker.base: Provisioning with shell script: /tmp/packer-shell485448421
==> docker.base: Committing the container
docker.base: Image ID: sha256:d1ab9a4eaf3729dc838460702674320624641b0dd2d7794d8a643f25e61e4ad3
==> docker.base: Killing the container: 22156c60d9a54391829832ccb4c833bf235af6ccf131845a46fcd3c13c8539e8
==> docker.base: Running post-processor: (type docker-tag)
==> docker.base (docker-tag): Deprecation warning: "tag" option has been replaced with "tags". In future versions of Packer, this configuration may not work. Please call `packer fix` on your template to update.
docker.base (docker-tag): Tagging image: sha256:d1ab9a4eaf3729dc838460702674320624641b0dd2d7794d8a643f25e61e4ad3
docker.base (docker-tag): Repository: ************.dkr.ecr.us-east-1.amazonaws.com/zevs:07Nov20201647
==> docker.base: Running post-processor: (type docker-push)
docker.base (docker-push): Fetching ECR credentials...
docker.base (docker-push): Logging in...
docker.base (docker-push): WARNING! Your password will be stored unencrypted in /home/aston-r/.docker/config.json.
docker.base (docker-push): Configure a credential helper to remove this warning. See
docker.base (docker-push): https://docs.docker.com/engine/reference/commandline/login/#credentials-store
docker.base (docker-push): Login Succeeded
docker.base (docker-push): Pushing: sha256:d1ab9a4eaf3729dc838460702674320624641b0dd2d7794d8a643f25e61e4ad3
docker.base (docker-push): The push refers to repository [docker.io/library/sha256] <----!!!!!!!!!!!
docker.base (docker-push): An image does not exist locally with the tag: sha256 <----!!!!!!!!!!!
docker.base (docker-push): Logging out...
docker.base (docker-push): Removing login credentials for ************.dkr.ecr.us-east-1.amazonaws.com
```
Here is packer-1.5.4:
```
docker: Provisioning with shell script: /tmp/packer-shell594000477
==> docker: Committing the container
docker: Image ID: sha256:fd4911057124d247748de8661ced48132ffe9119999f0e6e1d8b3177ab4bd6a6
==> docker: Killing the container: e79bf9656518c8393ab522e5610ca66249b72c069ad4145569388ea1bb89bd20
==> docker: Running post-processor: (type docker-tag)
docker (docker-tag): Tagging image: sha256:fd4911057124d247748de8661ced48132ffe9119999f0e6e1d8b3177ab4bd6a6
docker (docker-tag): Repository: ************.dkr.ecr.us-east-1.amazonaws.com/zevs:07Nov20201631
==> docker: Running post-processor: (type docker-push)
docker (docker-push): Fetching ECR credentials...
docker (docker-push): Logging in...
docker (docker-push): Login Succeeded
docker (docker-push): WARNING! Your password will be stored unencrypted in /home/aston-r/.docker/config.json.
docker (docker-push): Configure a credential helper to remove this warning. See
docker (docker-push): https://docs.docker.com/engine/reference/commandline/login/#credentials-store
docker (docker-push): Pushing: ************.dkr.ecr.us-east-1.amazonaws.com/zevs:07Nov20201631
docker (docker-push): The push refers to repository [************.dkr.ecr.us-east-1.amazonaws.com/zevs]
docker (docker-push): d6dae3c01d10: Preparing
docker (docker-push): 292349d27210: Preparing
docker (docker-push): 6360407af3e7: Preparing
docker (docker-push): 68aa0de28940: Preparing
docker (docker-push): f04cc38c0ac2: Preparing
docker (docker-push): ace0eda3e3be: Preparing
docker (docker-push): ace0eda3e3be: Waiting
docker (docker-push): 6360407af3e7: Pushed
docker (docker-push): f04cc38c0ac2: Pushed
docker (docker-push): 292349d27210: Pushed
docker (docker-push): ace0eda3e3be: Pushed
docker (docker-push): 68aa0de28940: Pushed
docker (docker-push): d6dae3c01d10: Pushed
docker (docker-push): 07Nov20201631: digest: sha256:f4e81ab4e1a5fdf9236413ad5a71fa3707431487d48394fe9931242ebc8a729a size: 1581
docker (docker-push): Logging out...
docker (docker-push): Removing login credentials for ************.dkr.ecr.us-east-1.amazonaws.com
Build 'docker' finished.
==> Builds finished. The artifacts of successful builds are:
--> docker: Imported Docker image: sha256:fd4911057124d247748de8661ced48132ffe9119999f0e6e1d8b3177ab4bd6a6
--> docker: Imported Docker image: ************.dkr.ecr.us-east-1.amazonaws.com/zevs:07Nov20201631
--> docker: Imported Docker image: ************.dkr.ecr.us-east-1.amazonaws.com/zevs:07Nov20201631
```
I am using the HCL2 template to build the image. Here is a part of it:
```
build {
sources = ["source.docker.base"]
provisioner "ansible" {
playbook_file = "prepare.yml"
user = "root"
}
provisioner "ansible" {
playbook_file = "main.yml"
user = "zevs"
galaxy_file = "requirements.yml"
galaxy_force_install = true
extra_arguments = ["--extra-vars", "target=all"]
}
provisioner "shell" {
inline = ["rm -rf /var/cache/apk /home/zevs/.ansible /root/.ansible"]
}
post-processor "docker-tag" {
repository = local.repo
tag = [formatdate("DDMMMYYYYhhmm", timestamp())]
}
post-processor "docker-push" {
ecr_login = true
login_server = var.registry
}
}
```
I also attached the part of the log with `PACKER_LOG=1` I tried to use tags just in case in docker-tag, but it did not help.
[packer-build.log](https://github.com/hashicorp/packer/files/5505201/packer-build.log)
| non_priority | error during pushing docker image to ecr after updating to the new version hi i faced the issue during pushing the docker image to ecr after updating the packer version from to as for now i rollbacked the version to here is packer docker base provisioning with shell script tmp packer docker base committing the container docker base image id docker base killing the container docker base running post processor type docker tag docker base docker tag deprecation warning tag option has been replaced with tags in future versions of packer this configuration may not work please call packer fix on your template to update docker base docker tag tagging image docker base docker tag repository dkr ecr us east amazonaws com zevs docker base running post processor type docker push docker base docker push fetching ecr credentials docker base docker push logging in docker base docker push warning your password will be stored unencrypted in home aston r docker config json docker base docker push configure a credential helper to remove this warning see docker base docker push docker base docker push login succeeded docker base docker push pushing docker base docker push the push refers to repository docker base docker push an image does not exist locally with the tag docker base docker push logging out docker base docker push removing login credentials for dkr ecr us east amazonaws com here is packer docker provisioning with shell script tmp packer docker committing the container docker image id docker killing the container docker running post processor type docker tag docker docker tag tagging image docker docker tag repository dkr ecr us east amazonaws com zevs docker running post processor type docker push docker docker push fetching ecr credentials docker docker push logging in docker docker push login succeeded docker docker push warning your password will be stored unencrypted in home aston r docker config json docker docker push configure a credential helper to remove this warning see docker docker push docker docker push pushing dkr ecr us east amazonaws com zevs docker docker push the push refers to repository docker docker push preparing docker docker push preparing docker docker push preparing docker docker push preparing docker docker push preparing docker docker push preparing docker docker push waiting docker docker push pushed docker docker push pushed docker docker push pushed docker docker push pushed docker docker push pushed docker docker push pushed docker docker push digest size docker docker push logging out docker docker push removing login credentials for dkr ecr us east amazonaws com build docker finished builds finished the artifacts of successful builds are docker imported docker image docker imported docker image dkr ecr us east amazonaws com zevs docker imported docker image dkr ecr us east amazonaws com zevs i am using the template to build the image here is a part of it build sources provisioner ansible playbook file prepare yml user root provisioner ansible playbook file main yml user zevs galaxy file requirements yml galaxy force install true extra arguments provisioner shell inline post processor docker tag repository local repo tag post processor docker push ecr login true login server var registry i also attached the part of the log with packer log i tried to use tags just in case in docker tag but it did not help | 0 |
178,666 | 14,676,104,885 | IssuesEvent | 2020-12-30 19:18:24 | apache/buildstream | https://api.github.com/repos/apache/buildstream | closed | Documentation does not build with latest version of sphinx | bug documentation | [See original issue on GitLab](https://gitlab.com/BuildStream/buildstream/-/issues/312)
In GitLab by [[Gitlab user @tristanvb]](https://gitlab.com/tristanvb) on Mar 21, 2018, 14:43
Today sphinx 1.7.2 was released, and I needed to add this commit to pin sphinx to 1.7.1 and pass CI again:
```
commit f9edceed17039df045677f7103c40f7dbadf2a5d
Author: Tristan Van Berkom <tristan.vanberkom[[Gitlab user @codethink]](https://gitlab.com/codethink).co.uk>
Date: Wed Mar 21 23:23:28 2018 +0900
.gitlab-ci.yml: Pin the sphinx version to 1.7.1
The new version today 1.7.2 causes the following build error:
Warning, treated as error:
/builds/BuildStream/buildstream/dist/buildstream/doc/source/buildstream.sandbox.rst:document isn't included in any toctree
``` | 1.0 | Documentation does not build with latest version of sphinx - [See original issue on GitLab](https://gitlab.com/BuildStream/buildstream/-/issues/312)
In GitLab by [[Gitlab user @tristanvb]](https://gitlab.com/tristanvb) on Mar 21, 2018, 14:43
Today sphinx 1.7.2 was released, and I needed to add this commit to pin sphinx to 1.7.1 and pass CI again:
```
commit f9edceed17039df045677f7103c40f7dbadf2a5d
Author: Tristan Van Berkom <tristan.vanberkom[[Gitlab user @codethink]](https://gitlab.com/codethink).co.uk>
Date: Wed Mar 21 23:23:28 2018 +0900
.gitlab-ci.yml: Pin the sphinx version to 1.7.1
The new version today 1.7.2 causes the following build error:
Warning, treated as error:
/builds/BuildStream/buildstream/dist/buildstream/doc/source/buildstream.sandbox.rst:document isn't included in any toctree
``` | non_priority | documentation does not build with latest version of sphinx in gitlab by on mar today sphinx was released and i needed to add this commit to pin sphinx to and pass ci again commit author tristan van berkom tristan vanberkom date wed mar gitlab ci yml pin the sphinx version to the new version today causes the following build error warning treated as error builds buildstream buildstream dist buildstream doc source buildstream sandbox rst document isn t included in any toctree | 0 |
4,051 | 6,652,416,983 | IssuesEvent | 2017-09-29 01:17:26 | bwsw/cloudstack-ui | https://api.github.com/repos/bwsw/cloudstack-ui | opened | Provide user with capability to save password for VM to VM tags | Epic requirement | Provide user with capability to save password for VM to VM tags (create, reset password) | 1.0 | Provide user with capability to save password for VM to VM tags - Provide user with capability to save password for VM to VM tags (create, reset password) | non_priority | provide user with capability to save password for vm to vm tags provide user with capability to save password for vm to vm tags create reset password | 0 |
264,740 | 28,212,776,096 | IssuesEvent | 2023-04-05 06:30:51 | hshivhare67/platform_frameworks_av_AOSP10_r33_CVE-2023-20933 | https://api.github.com/repos/hshivhare67/platform_frameworks_av_AOSP10_r33_CVE-2023-20933 | closed | CVE-2021-0437 (High) detected in avandroid-10.0.0_r33, avandroid-10.0.0_r33 - autoclosed | Mend: dependency security vulnerability | ## CVE-2021-0437 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>avandroid-10.0.0_r33</b>, <b>avandroid-10.0.0_r33</b></p></summary>
<p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In setPlayPolicy of DrmPlugin.cpp, there is a possible double free. This could lead to local escalation of privilege in a privileged process with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-8.1 Android-9 Android-10Android ID: A-176168330
<p>Publish Date: 2021-04-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-0437>CVE-2021-0437</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://source.android.com/security/bulletin/2021-04-01">https://source.android.com/security/bulletin/2021-04-01</a></p>
<p>Release Date: 2020-11-07</p>
<p>Fix Resolution: android-11.0.0_r34</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-0437 (High) detected in avandroid-10.0.0_r33, avandroid-10.0.0_r33 - autoclosed - ## CVE-2021-0437 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>avandroid-10.0.0_r33</b>, <b>avandroid-10.0.0_r33</b></p></summary>
<p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In setPlayPolicy of DrmPlugin.cpp, there is a possible double free. This could lead to local escalation of privilege in a privileged process with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-8.1 Android-9 Android-10Android ID: A-176168330
<p>Publish Date: 2021-04-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-0437>CVE-2021-0437</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://source.android.com/security/bulletin/2021-04-01">https://source.android.com/security/bulletin/2021-04-01</a></p>
<p>Release Date: 2020-11-07</p>
<p>Fix Resolution: android-11.0.0_r34</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in avandroid avandroid autoclosed cve high severity vulnerability vulnerable libraries avandroid avandroid vulnerability details in setplaypolicy of drmplugin cpp there is a possible double free this could lead to local escalation of privilege in a privileged process with no additional execution privileges needed user interaction is not needed for exploitation product androidversions android android android android id a publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution android step up your open source security game with mend | 0 |
13,096 | 8,792,754,763 | IssuesEvent | 2018-12-21 17:11:58 | concourse/concourse | https://api.github.com/repos/concourse/concourse | opened | Remove GET /sky/token route | auth enhancement security | This endpoint was added so that people can copy their token to `fly` more easily, and is no longer necessary now that we have the new login UI (#2845):
https://github.com/concourse/concourse/blob/d5b95215cf0652ccca86a37205c6ee59f29c86ce/skymarshal/skyserver/skyserver.go#L278-L288 | True | Remove GET /sky/token route - This endpoint was added so that people can copy their token to `fly` more easily, and is no longer necessary now that we have the new login UI (#2845):
https://github.com/concourse/concourse/blob/d5b95215cf0652ccca86a37205c6ee59f29c86ce/skymarshal/skyserver/skyserver.go#L278-L288 | non_priority | remove get sky token route this endpoint was added so that people can copy their token to fly more easily and is no longer necessary now that we have the new login ui | 0 |
102,433 | 16,566,212,161 | IssuesEvent | 2021-05-29 13:14:55 | AlexRogalskiy/github-action-random-quote | https://api.github.com/repos/AlexRogalskiy/github-action-random-quote | opened | CVE-2021-23343 (High) detected in path-parse-1.0.6.tgz | security vulnerability | ## CVE-2021-23343 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>path-parse-1.0.6.tgz</b></p></summary>
<p>Node.js path.parse() ponyfill</p>
<p>Library home page: <a href="https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz">https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz</a></p>
<p>Path to dependency file: github-action-random-quote/package.json</p>
<p>Path to vulnerable library: github-action-random-quote/node_modules/path-parse/package.json</p>
<p>
Dependency Hierarchy:
- eslint-import-resolver-typescript-2.4.0.tgz (Root Library)
- resolve-1.20.0.tgz
- :x: **path-parse-1.0.6.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/github-action-random-quote/commit/99c135aa691d6abe5673bace94251bc0966b49e0">99c135aa691d6abe5673bace94251bc0966b49e0</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
All versions of package path-parse are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity.
<p>Publish Date: 2021-05-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23343>CVE-2021-23343</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/jbgutierrez/path-parse/issues/8">https://github.com/jbgutierrez/path-parse/issues/8</a></p>
<p>Release Date: 2021-05-04</p>
<p>Fix Resolution: path-parse - 1.0.7</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-23343 (High) detected in path-parse-1.0.6.tgz - ## CVE-2021-23343 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>path-parse-1.0.6.tgz</b></p></summary>
<p>Node.js path.parse() ponyfill</p>
<p>Library home page: <a href="https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz">https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz</a></p>
<p>Path to dependency file: github-action-random-quote/package.json</p>
<p>Path to vulnerable library: github-action-random-quote/node_modules/path-parse/package.json</p>
<p>
Dependency Hierarchy:
- eslint-import-resolver-typescript-2.4.0.tgz (Root Library)
- resolve-1.20.0.tgz
- :x: **path-parse-1.0.6.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/github-action-random-quote/commit/99c135aa691d6abe5673bace94251bc0966b49e0">99c135aa691d6abe5673bace94251bc0966b49e0</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
All versions of package path-parse are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity.
<p>Publish Date: 2021-05-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23343>CVE-2021-23343</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/jbgutierrez/path-parse/issues/8">https://github.com/jbgutierrez/path-parse/issues/8</a></p>
<p>Release Date: 2021-05-04</p>
<p>Fix Resolution: path-parse - 1.0.7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in path parse tgz cve high severity vulnerability vulnerable library path parse tgz node js path parse ponyfill library home page a href path to dependency file github action random quote package json path to vulnerable library github action random quote node modules path parse package json dependency hierarchy eslint import resolver typescript tgz root library resolve tgz x path parse tgz vulnerable library found in head commit a href vulnerability details all versions of package path parse are vulnerable to regular expression denial of service redos via splitdevicere splittailre and splitpathre regular expressions redos exhibits polynomial worst case time complexity publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution path parse step up your open source security game with whitesource | 0 |
74,144 | 20,029,037,914 | IssuesEvent | 2022-02-02 01:43:44 | microsoft/react-native-windows | https://api.github.com/repos/microsoft/react-native-windows | closed | Unable to build playground.sln with VS 2019 in main | bug must-have Area: Build Infrastructure Area: Playground | ### Problem Description
Trying to build playground.sln in main fails with a bunch of errors.
### Steps To Reproduce
1. Clone repo.
2. `yarn && yarn build`
3. Open playground.sln in VS 2019
4. Switch to x86
5. Build Solution
### Expected Results
Solution builds.
### CLI version
npx react-native --version
### Environment
```markdown
info Fetching system and libraries information...
error Unable to print environment info.
Error: Command failed: wmic os get Caption
'wmic' is not recognized as an internal or external command,
operable program or batch file.
info React Native v0.60.0 is now available (your project is running on v0.0.0-20220107-2008-ca5aaa766).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.60.0.
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.0.0-20220107-2008-ca5aaa766.
info To upgrade, run "react-native upgrade".
```
### Target Platform Version
10.0.19041
### Target Device(s)
Desktop
### Visual Studio Version
Visual Studio 2019
### Build Configuration
Debug
### Snack, code example, screenshot, or link to a repository
_No response_ | 1.0 | Unable to build playground.sln with VS 2019 in main - ### Problem Description
Trying to build playground.sln in main fails with a bunch of errors.
### Steps To Reproduce
1. Clone repo.
2. `yarn && yarn build`
3. Open playground.sln in VS 2019
4. Switch to x86
5. Build Solution
### Expected Results
Solution builds.
### CLI version
npx react-native --version
### Environment
```markdown
info Fetching system and libraries information...
error Unable to print environment info.
Error: Command failed: wmic os get Caption
'wmic' is not recognized as an internal or external command,
operable program or batch file.
info React Native v0.60.0 is now available (your project is running on v0.0.0-20220107-2008-ca5aaa766).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.60.0.
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.0.0-20220107-2008-ca5aaa766.
info To upgrade, run "react-native upgrade".
```
### Target Platform Version
10.0.19041
### Target Device(s)
Desktop
### Visual Studio Version
Visual Studio 2019
### Build Configuration
Debug
### Snack, code example, screenshot, or link to a repository
_No response_ | non_priority | unable to build playground sln with vs in main problem description trying to build playground sln in main fails with a bunch of errors steps to reproduce clone repo yarn yarn build open playground sln in vs switch to build solution expected results solution builds cli version npx react native version environment markdown info fetching system and libraries information error unable to print environment info error command failed wmic os get caption wmic is not recognized as an internal or external command operable program or batch file info react native is now available your project is running on info changelog info diff info to upgrade run react native upgrade target platform version target device s desktop visual studio version visual studio build configuration debug snack code example screenshot or link to a repository no response | 0 |
368,250 | 25,784,078,289 | IssuesEvent | 2022-12-09 18:35:22 | vector-im/matrix-bot-sdk | https://api.github.com/repos/vector-im/matrix-bot-sdk | opened | Update security disclosure policy | documentation | The [security disclosure policy](https://github.com/vector-im/matrix-bot-sdk/blob/element-main/.github/SECURITY.md) pulled from upstream says to contact Travis. This fork should have its own security policy & contact(s).
The security policy link in [the issue template config](https://github.com/vector-im/matrix-bot-sdk/blob/element-main/.github/ISSUE_TEMPLATE/config.yaml) must be updated too. | 1.0 | Update security disclosure policy - The [security disclosure policy](https://github.com/vector-im/matrix-bot-sdk/blob/element-main/.github/SECURITY.md) pulled from upstream says to contact Travis. This fork should have its own security policy & contact(s).
The security policy link in [the issue template config](https://github.com/vector-im/matrix-bot-sdk/blob/element-main/.github/ISSUE_TEMPLATE/config.yaml) must be updated too. | non_priority | update security disclosure policy the pulled from upstream says to contact travis this fork should have its own security policy contact s the security policy link in must be updated too | 0 |
107,522 | 9,216,329,543 | IssuesEvent | 2019-03-11 07:42:13 | Ericsson/codechecker | https://api.github.com/repos/Ericsson/codechecker | closed | use separate workspace for the sqlite and postgresql tests | Kind: Enhancement Target: Developer environment Target: Test | using a separate workspace for the sqlite and postgresql tests should allow to run the tests parallel
The `WORKSPACE` variable could be set by an environment variable for the web server tests:
https://github.com/Ericsson/codechecker/blob/c0664e3f6448bbd586b3f4d37cf49b9f1c20793c/web/tests/Makefile#L16 | 1.0 | use separate workspace for the sqlite and postgresql tests - using a separate workspace for the sqlite and postgresql tests should allow to run the tests parallel
The `WORKSPACE` variable could be set by an environment variable for the web server tests:
https://github.com/Ericsson/codechecker/blob/c0664e3f6448bbd586b3f4d37cf49b9f1c20793c/web/tests/Makefile#L16 | non_priority | use separate workspace for the sqlite and postgresql tests using a separate workspace for the sqlite and postgresql tests should allow to run the tests parallel the workspace variable could be set by an environment variable for the web server tests | 0 |
62,868 | 17,203,835,314 | IssuesEvent | 2021-07-17 20:36:30 | InterNetNews/inn | https://api.github.com/repos/InterNetNews/inn | closed | Improve the colon-space check in headers | C: nnrpd P: medium R: fixed T: defect | **Reported by iulius on 15 Sep 2015 19:43 UTC**
Posting the below article generates that log in news.err:
Sep 15 21:37:08 news nnrpd[29674]: Bad header copying headers for Perl: 'message-id <test@example.com>'
nnrpd should check that syntax before calling the Perl filter.
POST
340 Ok, recommended message-ID <mt9rvr$sva$1@news.trigofacile.com>
From: <test@example.com>
Newsgroups: trigofacile.test
Subject: test
Date: Mon, 14 Sep 2015 15:40:14 +0000 (UTC)
message-id <test@example.com>
Test
.
441 437 No colon-space in "message-id <test@example.com>" header | 1.0 | Improve the colon-space check in headers - **Reported by iulius on 15 Sep 2015 19:43 UTC**
Posting the below article generates that log in news.err:
Sep 15 21:37:08 news nnrpd[29674]: Bad header copying headers for Perl: 'message-id <test@example.com>'
nnrpd should check that syntax before calling the Perl filter.
POST
340 Ok, recommended message-ID <mt9rvr$sva$1@news.trigofacile.com>
From: <test@example.com>
Newsgroups: trigofacile.test
Subject: test
Date: Mon, 14 Sep 2015 15:40:14 +0000 (UTC)
message-id <test@example.com>
Test
.
441 437 No colon-space in "message-id <test@example.com>" header | non_priority | improve the colon space check in headers reported by iulius on sep utc posting the below article generates that log in news err sep news nnrpd bad header copying headers for perl message id nnrpd should check that syntax before calling the perl filter post ok recommended message id from newsgroups trigofacile test subject test date mon sep utc message id test no colon space in message id header | 0 |
27,374 | 12,546,822,619 | IssuesEvent | 2020-06-05 21:28:13 | Azure/azure-sdk-for-net | https://api.github.com/repos/Azure/azure-sdk-for-net | closed | Remove USReceipt and related types | Client Cognitive Services FormRecognizer blocking-release | Based on the outcome of the design discussion around receipts (per https://github.com/azure/azure-sdk-for-net/issues/11912), we will remove strong types from the Receipts feature.
Draft proposal is here: https://github.com/Azure/azure-sdk-for-net/pull/12399 | 1.0 | Remove USReceipt and related types - Based on the outcome of the design discussion around receipts (per https://github.com/azure/azure-sdk-for-net/issues/11912), we will remove strong types from the Receipts feature.
Draft proposal is here: https://github.com/Azure/azure-sdk-for-net/pull/12399 | non_priority | remove usreceipt and related types based on the outcome of the design discussion around receipts per we will remove strong types from the receipts feature draft proposal is here | 0 |
112,291 | 17,088,040,370 | IssuesEvent | 2021-07-08 14:09:44 | dotnet/docs | https://api.github.com/repos/dotnet/docs | closed | Declaring Global Objects instructions are incorrect. | Pri2 doc-enhancement dotnet-security/tech up-for-grabs | There is a mistake in the instructions:
**Declaring Global Objects**
_Add the following code to the Form's constructor._
You can't add that code to the constructor or none of the other methods will be able to see the declared variables. It has to be done as part of the Form1 declaration. So maybe... before the Form's constructor if that's what you wanted to say.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 2a8e441d-cd59-de15-a814-0d86d4cda052
* Version Independent ID: c94ca6d4-7e93-8aac-93d1-7f249c77d243
* Content: [Walkthrough: Creating a Cryptographic Application](https://docs.microsoft.com/en-us/dotnet/standard/security/walkthrough-creating-a-cryptographic-application)
* Content Source: [docs/standard/security/walkthrough-creating-a-cryptographic-application.md](https://github.com/dotnet/docs/blob/main/docs/standard/security/walkthrough-creating-a-cryptographic-application.md)
* Product: **dotnet**
* Technology: **dotnet-security**
* GitHub Login: @IEvangelist
* Microsoft Alias: **dapine** | True | Declaring Global Objects instructions are incorrect. - There is a mistake in the instructions:
**Declaring Global Objects**
_Add the following code to the Form's constructor._
You can't add that code to the constructor or none of the other methods will be able to see the declared variables. It has to be done as part of the Form1 declaration. So maybe... before the Form's constructor if that's what you wanted to say.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 2a8e441d-cd59-de15-a814-0d86d4cda052
* Version Independent ID: c94ca6d4-7e93-8aac-93d1-7f249c77d243
* Content: [Walkthrough: Creating a Cryptographic Application](https://docs.microsoft.com/en-us/dotnet/standard/security/walkthrough-creating-a-cryptographic-application)
* Content Source: [docs/standard/security/walkthrough-creating-a-cryptographic-application.md](https://github.com/dotnet/docs/blob/main/docs/standard/security/walkthrough-creating-a-cryptographic-application.md)
* Product: **dotnet**
* Technology: **dotnet-security**
* GitHub Login: @IEvangelist
* Microsoft Alias: **dapine** | non_priority | declaring global objects instructions are incorrect there is a mistake in the instructions declaring global objects add the following code to the form s constructor you can t add that code to the constructor or none of the other methods will be able to see the declared variables it has to be done as part of the declaration so maybe before the form s constructor if that s what you wanted to say document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source product dotnet technology dotnet security github login ievangelist microsoft alias dapine | 0 |
178,948 | 30,039,129,624 | IssuesEvent | 2023-06-27 14:29:25 | FRONTENDSCHOOL5/final-25-would-you | https://api.github.com/repos/FRONTENDSCHOOL5/final-25-would-you | closed | [💄design] 공통UI(header) 마크업 | design | ## 작업할 내용
- 공통UI(header) 마크업
## 구현 방법 및 예상 결과
- 마크업 추가
## 특이사항
- feat_#9_header 브랜치 생성해서 따로 작업 | 1.0 | [💄design] 공통UI(header) 마크업 - ## 작업할 내용
- 공통UI(header) 마크업
## 구현 방법 및 예상 결과
- 마크업 추가
## 특이사항
- feat_#9_header 브랜치 생성해서 따로 작업 | non_priority | 공통ui header 마크업 작업할 내용 공통ui header 마크업 구현 방법 및 예상 결과 마크업 추가 특이사항 feat header 브랜치 생성해서 따로 작업 | 0 |
45,868 | 24,250,584,475 | IssuesEvent | 2022-09-27 13:56:29 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | optimize Prisma test performance tracking | C-performance A-sql-execution A-tools-prisma T-sql-schema T-sql-queries | **Describe the problem**
Currently the Prisma test suite takes 45 minutes to complete
**To Reproduce**
* Check out https://github.com/prisma/prisma-engines
* Set `current_connector` file to contain `cockroach`
* I used to write the following to `.test_config`:
```json
{
"connector": "cockroachdb",
"runner": "direct"
}
```
* Set up a local cockroach
* I was using https://gist.github.com/ajwerner/ce2e55540ce91d2e076470d2f478963c
* Run `cargo test -p query-engine-tests`
**Expected behavior**
The Prisma test suite should complete in under 30 minutes, or as quickly as competitor databases.
**Additional context**
Making this test suite fast will allow Prisma, and possibly more generally other third-party tools, to iterate more quickly using CockroachDB.
Jira issue: CRDB-18910 | True | optimize Prisma test performance tracking - **Describe the problem**
Currently the Prisma test suite takes 45 minutes to complete
**To Reproduce**
* Check out https://github.com/prisma/prisma-engines
* Set `current_connector` file to contain `cockroach`
* I used to write the following to `.test_config`:
```json
{
"connector": "cockroachdb",
"runner": "direct"
}
```
* Set up a local cockroach
* I was using https://gist.github.com/ajwerner/ce2e55540ce91d2e076470d2f478963c
* Run `cargo test -p query-engine-tests`
**Expected behavior**
The Prisma test suite should complete in under 30 minutes, or as quickly as competitor databases.
**Additional context**
Making this test suite fast will allow Prisma, and possibly more generally other third-party tools, to iterate more quickly using CockroachDB.
Jira issue: CRDB-18910 | non_priority | optimize prisma test performance tracking describe the problem currently the prisma test suite takes minutes to complete to reproduce check out set current connector file to contain cockroach i used to write the following to test config json connector cockroachdb runner direct set up a local cockroach i was using run cargo test p query engine tests expected behavior the prisma test suite should complete in under minutes or as quickly as competitor databases additional context making this test suite fast will allow prisma and possibly more generally other third party tools to iterate more quickly using cockroachdb jira issue crdb | 0 |
193,403 | 14,652,503,703 | IssuesEvent | 2020-12-28 02:04:59 | Grinnode-live/2020-grin-bug-bash-challenge | https://api.github.com/repos/Grinnode-live/2020-grin-bug-bash-challenge | closed | [GRIN-Wallet][Owner API] testing the issue invoice tx method | Grin-Wallet Test-Case | **Description**
Testing the init send tx method from the Owner API
**Prerequisites**
1. GRIN-Node
2. GRIN-Wallet
**Test procedure**
1. Prepare two wallets (1) and (2), run wallet (2) in Owner API listener mode
2. Use [node.js](https://gist.github.com/marekyggdrasil/82716db323b34019bf02237012e0d16f) or [python](https://github.com/grinfans/grin.py/blob/main/wallet_v3.py) to run a encrypted request to [init issue invoice method](https://docs.rs/grin_wallet_api/4.0.0/grin_wallet_api/struct.Owner.html#method.issue_invoice_tx)
3. Complete the `invoice -> pay -> finalize` flow as done in https://github.com/Grinnode-live/2020-grin-bug-bash-challenge/issues/17
**Expected result:**
Expect the `invoice -> pay -> finalize` flow initiated by Owner API to work correctly as in https://github.com/Grinnode-live/2020-grin-bug-bash-challenge/issues/17
Include the output of the following command for both wallets
```
grin-wallet -V
```
and your environment
```
uname -a
``` | 1.0 | [GRIN-Wallet][Owner API] testing the issue invoice tx method - **Description**
Testing the init send tx method from the Owner API
**Prerequisites**
1. GRIN-Node
2. GRIN-Wallet
**Test procedure**
1. Prepare two wallets (1) and (2), run wallet (2) in Owner API listener mode
2. Use [node.js](https://gist.github.com/marekyggdrasil/82716db323b34019bf02237012e0d16f) or [python](https://github.com/grinfans/grin.py/blob/main/wallet_v3.py) to run a encrypted request to [init issue invoice method](https://docs.rs/grin_wallet_api/4.0.0/grin_wallet_api/struct.Owner.html#method.issue_invoice_tx)
3. Complete the `invoice -> pay -> finalize` flow as done in https://github.com/Grinnode-live/2020-grin-bug-bash-challenge/issues/17
**Expected result:**
Expect the `invoice -> pay -> finalize` flow initiated by Owner API to work correctly as in https://github.com/Grinnode-live/2020-grin-bug-bash-challenge/issues/17
Include the output of the following command for both wallets
```
grin-wallet -V
```
and your environment
```
uname -a
``` | non_priority | testing the issue invoice tx method description testing the init send tx method from the owner api prerequisites grin node grin wallet test procedure prepare two wallets and run wallet in owner api listener mode use or to run a encrypted request to complete the invoice pay finalize flow as done in expected result expect the invoice pay finalize flow initiated by owner api to work correctly as in include the output of the following command for both wallets grin wallet v and your environment uname a | 0 |
247,421 | 20,978,248,659 | IssuesEvent | 2022-03-28 17:11:22 | aldefouw/redcap_cypress | https://api.github.com/repos/aldefouw/redcap_cypress | closed | Browse Projects | Core Functionality Test Script Feature | File Location:
https://github.com/aldefouw/redcap_cypress/blob/v11.1.29/cypress/features/core/pre-requisite/browse_projects.feature
Task:
Write the test specs in Gherkin DSL following manual test script as guide
Contact Adam De Fouw ([aldefouw@medicine.wisc.edu](mailto:aldefouw@medicine.wisc.edu)) with any questions. | 1.0 | Browse Projects - File Location:
https://github.com/aldefouw/redcap_cypress/blob/v11.1.29/cypress/features/core/pre-requisite/browse_projects.feature
Task:
Write the test specs in Gherkin DSL following manual test script as guide
Contact Adam De Fouw ([aldefouw@medicine.wisc.edu](mailto:aldefouw@medicine.wisc.edu)) with any questions. | non_priority | browse projects file location task write the test specs in gherkin dsl following manual test script as guide contact adam de fouw mailto aldefouw medicine wisc edu with any questions | 0 |
25,505 | 4,350,997,803 | IssuesEvent | 2016-07-31 16:08:27 | hazelcast/hazelcast | https://api.github.com/repos/hazelcast/hazelcast | opened | `ClientEngineImpl::getConnectedClientStats` re-uses an operation | Team: Client Team: Integration Type: Defect | I've got this error shortly after a member started:
```
Exception in thread "hz._hzInstance_1_dev.cached.thread-3" java.lang.IllegalStateException: An operation[com.hazelcast.client.impl.operations.GetConnectedClientsOperation{serviceName='hz:core:clientEngine', identityHash=1178814838, partitionId=-1, replicaIndex=0, callId=3, invocationTime=1469980997245 (2016-07-31 19:03:17.245), waitTimeout=-1, callTimeout=60000}] can not be used for multiple invocations!
at com.hazelcast.spi.impl.operationservice.impl.Invocation.invoke0(Invocation.java:218)
at com.hazelcast.spi.impl.operationservice.impl.Invocation.invoke(Invocation.java:205)
at com.hazelcast.spi.impl.operationservice.impl.OperationServiceImpl.invokeOnTarget(OperationServiceImpl.java:311)
at com.hazelcast.client.impl.ClientEngineImpl.getConnectedClientStats(ClientEngineImpl.java:459)
at com.hazelcast.util.PhoneHome.phoneHome(PhoneHome.java:143)
at com.hazelcast.util.PhoneHome$1.run(PhoneHome.java:80)
at com.hazelcast.spi.impl.executionservice.impl.SkipOnConcurrentExecutionDecorator.run(SkipOnConcurrentExecutionDecorator.java:40)
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServiceDelegate.java:212)
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)
at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:76)
at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:92)
Jul 31, 2016 7:03:17 PM com.hazelcast.core.LifecycleService
```
The problem is the [`GetConnectedClientsOperation`](https://github.com/jerrinot/hazelcast/blob/f9ffb473e664e23db3fd47afbee2443f9072c21b/hazelcast/src/main/java/com/hazelcast/client/impl/ClientEngineImpl.java#L451-L451) is re-used for multiple invocations. This is not allowed - a new operation should be created of each invocation. | 1.0 | `ClientEngineImpl::getConnectedClientStats` re-uses an operation - I've got this error shortly after a member started:
```
Exception in thread "hz._hzInstance_1_dev.cached.thread-3" java.lang.IllegalStateException: An operation[com.hazelcast.client.impl.operations.GetConnectedClientsOperation{serviceName='hz:core:clientEngine', identityHash=1178814838, partitionId=-1, replicaIndex=0, callId=3, invocationTime=1469980997245 (2016-07-31 19:03:17.245), waitTimeout=-1, callTimeout=60000}] can not be used for multiple invocations!
at com.hazelcast.spi.impl.operationservice.impl.Invocation.invoke0(Invocation.java:218)
at com.hazelcast.spi.impl.operationservice.impl.Invocation.invoke(Invocation.java:205)
at com.hazelcast.spi.impl.operationservice.impl.OperationServiceImpl.invokeOnTarget(OperationServiceImpl.java:311)
at com.hazelcast.client.impl.ClientEngineImpl.getConnectedClientStats(ClientEngineImpl.java:459)
at com.hazelcast.util.PhoneHome.phoneHome(PhoneHome.java:143)
at com.hazelcast.util.PhoneHome$1.run(PhoneHome.java:80)
at com.hazelcast.spi.impl.executionservice.impl.SkipOnConcurrentExecutionDecorator.run(SkipOnConcurrentExecutionDecorator.java:40)
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServiceDelegate.java:212)
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)
at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:76)
at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:92)
Jul 31, 2016 7:03:17 PM com.hazelcast.core.LifecycleService
```
The problem is the [`GetConnectedClientsOperation`](https://github.com/jerrinot/hazelcast/blob/f9ffb473e664e23db3fd47afbee2443f9072c21b/hazelcast/src/main/java/com/hazelcast/client/impl/ClientEngineImpl.java#L451-L451) is re-used for multiple invocations. This is not allowed - a new operation should be created of each invocation. | non_priority | clientengineimpl getconnectedclientstats re uses an operation i ve got this error shortly after a member started exception in thread hz hzinstance dev cached thread java lang illegalstateexception an operation can not be used for multiple invocations at com hazelcast spi impl operationservice impl invocation invocation java at com hazelcast spi impl operationservice impl invocation invoke invocation java at com hazelcast spi impl operationservice impl operationserviceimpl invokeontarget operationserviceimpl java at com hazelcast client impl clientengineimpl getconnectedclientstats clientengineimpl java at com hazelcast util phonehome phonehome phonehome java at com hazelcast util phonehome run phonehome java at com hazelcast spi impl executionservice impl skiponconcurrentexecutiondecorator run skiponconcurrentexecutiondecorator java at com hazelcast util executor cachedexecutorservicedelegate worker run cachedexecutorservicedelegate 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 at com hazelcast util executor hazelcastmanagedthread executerun hazelcastmanagedthread java at com hazelcast util executor hazelcastmanagedthread run hazelcastmanagedthread java jul pm com hazelcast core lifecycleservice the problem is the is re used for multiple invocations this is not allowed a new operation should be created of each invocation | 0 |
343,264 | 24,766,392,494 | IssuesEvent | 2022-10-22 15:27:40 | RandomFractals/chicago-crimes | https://api.github.com/repos/RandomFractals/chicago-crimes | closed | Add Chicago Crimes DuckDB SQL Magic Jupyter notebook example | documentation notebook | Inspired by this post on using DuckDB with sql magics in Jupyter notebooks, written by @rmoff:
https://rmoff.net/2022/10/14/current-22-session-analysis-with-duckdb-and-jupyter-notebook/
Gist: https://gist.github.com/rmoff/e5cd6e04fc54e592fc4c232863252607
More info about this Jupyter notebook setup from the official duckDB docs:
https://duckdb.org/docs/guides/python/jupyter | 1.0 | Add Chicago Crimes DuckDB SQL Magic Jupyter notebook example - Inspired by this post on using DuckDB with sql magics in Jupyter notebooks, written by @rmoff:
https://rmoff.net/2022/10/14/current-22-session-analysis-with-duckdb-and-jupyter-notebook/
Gist: https://gist.github.com/rmoff/e5cd6e04fc54e592fc4c232863252607
More info about this Jupyter notebook setup from the official duckDB docs:
https://duckdb.org/docs/guides/python/jupyter | non_priority | add chicago crimes duckdb sql magic jupyter notebook example inspired by this post on using duckdb with sql magics in jupyter notebooks written by rmoff gist more info about this jupyter notebook setup from the official duckdb docs | 0 |
145,929 | 11,715,052,671 | IssuesEvent | 2020-03-09 13:31:19 | tikv/tikv | https://api.github.com/repos/tikv/tikv | opened | test test_cdc::test_cdc_not_leader ... thread 'main' panicked | component/test-bench | test_cdc::test_cdc_not_leader
```
[2020-03-09T03:05:09.375Z] running 1 test
[2020-03-09T03:05:12.045Z] test test_cdc::test_cdc_not_leader ... thread 'main' panicked at 'assertion failed: !suite.obs.get(&leader.get_store_id()).unwrap().is_subscribed(1)', components/cdc/tests/integrations/test_cdc.rs:436:5
[2020-03-09T03:05:12.045Z] stack backtrace:
[2020-03-09T03:05:12.972Z] 0: backtrace::backtrace::libunwind::trace
[2020-03-09T03:05:12.972Z] at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
[2020-03-09T03:05:12.972Z] 1: backtrace::backtrace::trace_unsynchronized
[2020-03-09T03:05:12.972Z] at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
[2020-03-09T03:05:12.972Z] 2: std::sys_common::backtrace::_print_fmt
[2020-03-09T03:05:12.972Z] at src/libstd/sys_common/backtrace.rs:84
[2020-03-09T03:05:12.972Z] 3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
[2020-03-09T03:05:12.972Z] at src/libstd/sys_common/backtrace.rs:61
[2020-03-09T03:05:12.972Z] 4: core::fmt::write
[2020-03-09T03:05:12.972Z] at src/libcore/fmt/mod.rs:1025
[2020-03-09T03:05:12.972Z] 5: std::io::Write::write_fmt
[2020-03-09T03:05:12.972Z] at src/libstd/io/mod.rs:1426
[2020-03-09T03:05:12.972Z] 6: std::sys_common::backtrace::_print
[2020-03-09T03:05:12.972Z] at src/libstd/sys_common/backtrace.rs:65
[2020-03-09T03:05:12.972Z] 7: std::sys_common::backtrace::print
[2020-03-09T03:05:12.972Z] at src/libstd/sys_common/backtrace.rs:50
[2020-03-09T03:05:12.972Z] 8: std::panicking::default_hook::{{closure}}
[2020-03-09T03:05:12.972Z] at src/libstd/panicking.rs:193
[2020-03-09T03:05:12.972Z] 9: std::panicking::default_hook
[2020-03-09T03:05:12.972Z] at src/libstd/panicking.rs:210
[2020-03-09T03:05:12.972Z] 10: std::panicking::rust_panic_with_hook
[2020-03-09T03:05:12.972Z] at src/libstd/panicking.rs:471
[2020-03-09T03:05:12.972Z] 11: std::panicking::begin_panic
[2020-03-09T03:05:12.972Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/panicking.rs:404
[2020-03-09T03:05:12.972Z] 12: integrations::test_cdc::test_cdc_not_leader
[2020-03-09T03:05:12.972Z] at components/cdc/tests/integrations/test_cdc.rs:436
[2020-03-09T03:05:12.972Z] 13: integrations::test_cdc::test_cdc_not_leader::{{closure}}
[2020-03-09T03:05:12.972Z] at components/cdc/tests/integrations/test_cdc.rs:344
[2020-03-09T03:05:12.972Z] 14: core::ops::function::FnOnce::call_once
[2020-03-09T03:05:12.972Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libcore/ops/function.rs:232
[2020-03-09T03:05:12.972Z] 15: <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once
[2020-03-09T03:05:12.972Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/liballoc/boxed.rs:1022
[2020-03-09T03:05:12.972Z] 16: __rust_maybe_catch_panic
[2020-03-09T03:05:12.972Z] at src/libpanic_unwind/lib.rs:78
[2020-03-09T03:05:12.972Z] 17: std::panicking::try
[2020-03-09T03:05:12.972Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/panicking.rs:270
[2020-03-09T03:05:12.972Z] 18: std::panic::catch_unwind
[2020-03-09T03:05:12.972Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/panic.rs:394
[2020-03-09T03:05:12.972Z] 19: test::run_test_in_process
[2020-03-09T03:05:12.972Z] at src/libtest/lib.rs:567
[2020-03-09T03:05:12.972Z] 20: test::run_test::run_test_inner::{{closure}}
[2020-03-09T03:05:12.972Z] at src/libtest/lib.rs:474
[2020-03-09T03:05:12.972Z] 21: test::run_test::run_test_inner
[2020-03-09T03:05:12.972Z] at src/libtest/lib.rs:495
[2020-03-09T03:05:12.972Z] 22: test::run_test
[2020-03-09T03:05:12.972Z] at src/libtest/lib.rs:531
[2020-03-09T03:05:12.972Z] 23: test::run_tests
[2020-03-09T03:05:12.972Z] at src/libtest/lib.rs:300
[2020-03-09T03:05:12.972Z] 24: test::console::run_tests_console
[2020-03-09T03:05:12.972Z] at src/libtest/console.rs:295
[2020-03-09T03:05:12.972Z] 25: test::test_main
[2020-03-09T03:05:12.972Z] at src/libtest/lib.rs:121
[2020-03-09T03:05:12.972Z] 26: test::test_main_static
[2020-03-09T03:05:12.972Z] at src/libtest/lib.rs:140
[2020-03-09T03:05:12.972Z] 27: integrations::main
[2020-03-09T03:05:12.972Z] 28: std::rt::lang_start::{{closure}}
[2020-03-09T03:05:12.972Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/rt.rs:67
[2020-03-09T03:05:12.972Z] 29: std::rt::lang_start_internal::{{closure}}
[2020-03-09T03:05:12.972Z] at src/libstd/rt.rs:52
[2020-03-09T03:05:12.972Z] 30: std::panicking::try::do_call
[2020-03-09T03:05:12.972Z] at src/libstd/panicking.rs:292
[2020-03-09T03:05:12.972Z] 31: __rust_maybe_catch_panic
[2020-03-09T03:05:12.972Z] at src/libpanic_unwind/lib.rs:78
[2020-03-09T03:05:12.972Z] 32: std::panicking::try
[2020-03-09T03:05:12.972Z] at src/libstd/panicking.rs:270
[2020-03-09T03:05:12.972Z] 33: std::panic::catch_unwind
[2020-03-09T03:05:12.972Z] at src/libstd/panic.rs:394
[2020-03-09T03:05:12.972Z] 34: std::rt::lang_start_internal
[2020-03-09T03:05:12.972Z] at src/libstd/rt.rs:51
[2020-03-09T03:05:12.972Z] 35: std::rt::lang_start
[2020-03-09T03:05:12.972Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/rt.rs:67
[2020-03-09T03:05:12.972Z] 36: main
[2020-03-09T03:05:12.972Z] 37: __libc_start_main
[2020-03-09T03:05:12.972Z] 38: <unknown>
[2020-03-09T03:05:12.972Z] note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[2020-03-09T03:05:12.972Z] FAILED
[2020-03-09T03:05:12.972Z]
[2020-03-09T03:05:12.972Z] failures:
[2020-03-09T03:05:12.972Z]
[2020-03-09T03:05:12.972Z] failures:
[2020-03-09T03:05:12.972Z] test_cdc::test_cdc_not_leader
``` | 1.0 | test test_cdc::test_cdc_not_leader ... thread 'main' panicked - test_cdc::test_cdc_not_leader
```
[2020-03-09T03:05:09.375Z] running 1 test
[2020-03-09T03:05:12.045Z] test test_cdc::test_cdc_not_leader ... thread 'main' panicked at 'assertion failed: !suite.obs.get(&leader.get_store_id()).unwrap().is_subscribed(1)', components/cdc/tests/integrations/test_cdc.rs:436:5
[2020-03-09T03:05:12.045Z] stack backtrace:
[2020-03-09T03:05:12.972Z] 0: backtrace::backtrace::libunwind::trace
[2020-03-09T03:05:12.972Z] at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
[2020-03-09T03:05:12.972Z] 1: backtrace::backtrace::trace_unsynchronized
[2020-03-09T03:05:12.972Z] at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
[2020-03-09T03:05:12.972Z] 2: std::sys_common::backtrace::_print_fmt
[2020-03-09T03:05:12.972Z] at src/libstd/sys_common/backtrace.rs:84
[2020-03-09T03:05:12.972Z] 3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
[2020-03-09T03:05:12.972Z] at src/libstd/sys_common/backtrace.rs:61
[2020-03-09T03:05:12.972Z] 4: core::fmt::write
[2020-03-09T03:05:12.972Z] at src/libcore/fmt/mod.rs:1025
[2020-03-09T03:05:12.972Z] 5: std::io::Write::write_fmt
[2020-03-09T03:05:12.972Z] at src/libstd/io/mod.rs:1426
[2020-03-09T03:05:12.972Z] 6: std::sys_common::backtrace::_print
[2020-03-09T03:05:12.972Z] at src/libstd/sys_common/backtrace.rs:65
[2020-03-09T03:05:12.972Z] 7: std::sys_common::backtrace::print
[2020-03-09T03:05:12.972Z] at src/libstd/sys_common/backtrace.rs:50
[2020-03-09T03:05:12.972Z] 8: std::panicking::default_hook::{{closure}}
[2020-03-09T03:05:12.972Z] at src/libstd/panicking.rs:193
[2020-03-09T03:05:12.972Z] 9: std::panicking::default_hook
[2020-03-09T03:05:12.972Z] at src/libstd/panicking.rs:210
[2020-03-09T03:05:12.972Z] 10: std::panicking::rust_panic_with_hook
[2020-03-09T03:05:12.972Z] at src/libstd/panicking.rs:471
[2020-03-09T03:05:12.972Z] 11: std::panicking::begin_panic
[2020-03-09T03:05:12.972Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/panicking.rs:404
[2020-03-09T03:05:12.972Z] 12: integrations::test_cdc::test_cdc_not_leader
[2020-03-09T03:05:12.972Z] at components/cdc/tests/integrations/test_cdc.rs:436
[2020-03-09T03:05:12.972Z] 13: integrations::test_cdc::test_cdc_not_leader::{{closure}}
[2020-03-09T03:05:12.972Z] at components/cdc/tests/integrations/test_cdc.rs:344
[2020-03-09T03:05:12.972Z] 14: core::ops::function::FnOnce::call_once
[2020-03-09T03:05:12.972Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libcore/ops/function.rs:232
[2020-03-09T03:05:12.972Z] 15: <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once
[2020-03-09T03:05:12.972Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/liballoc/boxed.rs:1022
[2020-03-09T03:05:12.972Z] 16: __rust_maybe_catch_panic
[2020-03-09T03:05:12.972Z] at src/libpanic_unwind/lib.rs:78
[2020-03-09T03:05:12.972Z] 17: std::panicking::try
[2020-03-09T03:05:12.972Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/panicking.rs:270
[2020-03-09T03:05:12.972Z] 18: std::panic::catch_unwind
[2020-03-09T03:05:12.972Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/panic.rs:394
[2020-03-09T03:05:12.972Z] 19: test::run_test_in_process
[2020-03-09T03:05:12.972Z] at src/libtest/lib.rs:567
[2020-03-09T03:05:12.972Z] 20: test::run_test::run_test_inner::{{closure}}
[2020-03-09T03:05:12.972Z] at src/libtest/lib.rs:474
[2020-03-09T03:05:12.972Z] 21: test::run_test::run_test_inner
[2020-03-09T03:05:12.972Z] at src/libtest/lib.rs:495
[2020-03-09T03:05:12.972Z] 22: test::run_test
[2020-03-09T03:05:12.972Z] at src/libtest/lib.rs:531
[2020-03-09T03:05:12.972Z] 23: test::run_tests
[2020-03-09T03:05:12.972Z] at src/libtest/lib.rs:300
[2020-03-09T03:05:12.972Z] 24: test::console::run_tests_console
[2020-03-09T03:05:12.972Z] at src/libtest/console.rs:295
[2020-03-09T03:05:12.972Z] 25: test::test_main
[2020-03-09T03:05:12.972Z] at src/libtest/lib.rs:121
[2020-03-09T03:05:12.972Z] 26: test::test_main_static
[2020-03-09T03:05:12.972Z] at src/libtest/lib.rs:140
[2020-03-09T03:05:12.972Z] 27: integrations::main
[2020-03-09T03:05:12.972Z] 28: std::rt::lang_start::{{closure}}
[2020-03-09T03:05:12.972Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/rt.rs:67
[2020-03-09T03:05:12.972Z] 29: std::rt::lang_start_internal::{{closure}}
[2020-03-09T03:05:12.972Z] at src/libstd/rt.rs:52
[2020-03-09T03:05:12.972Z] 30: std::panicking::try::do_call
[2020-03-09T03:05:12.972Z] at src/libstd/panicking.rs:292
[2020-03-09T03:05:12.972Z] 31: __rust_maybe_catch_panic
[2020-03-09T03:05:12.972Z] at src/libpanic_unwind/lib.rs:78
[2020-03-09T03:05:12.972Z] 32: std::panicking::try
[2020-03-09T03:05:12.972Z] at src/libstd/panicking.rs:270
[2020-03-09T03:05:12.972Z] 33: std::panic::catch_unwind
[2020-03-09T03:05:12.972Z] at src/libstd/panic.rs:394
[2020-03-09T03:05:12.972Z] 34: std::rt::lang_start_internal
[2020-03-09T03:05:12.972Z] at src/libstd/rt.rs:51
[2020-03-09T03:05:12.972Z] 35: std::rt::lang_start
[2020-03-09T03:05:12.972Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/rt.rs:67
[2020-03-09T03:05:12.972Z] 36: main
[2020-03-09T03:05:12.972Z] 37: __libc_start_main
[2020-03-09T03:05:12.972Z] 38: <unknown>
[2020-03-09T03:05:12.972Z] note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[2020-03-09T03:05:12.972Z] FAILED
[2020-03-09T03:05:12.972Z]
[2020-03-09T03:05:12.972Z] failures:
[2020-03-09T03:05:12.972Z]
[2020-03-09T03:05:12.972Z] failures:
[2020-03-09T03:05:12.972Z] test_cdc::test_cdc_not_leader
``` | non_priority | test test cdc test cdc not leader thread main panicked test cdc test cdc not leader running test test test cdc test cdc not leader thread main panicked at assertion failed suite obs get leader get store id unwrap is subscribed components cdc tests integrations test cdc rs stack backtrace backtrace backtrace libunwind trace at cargo registry src github com backtrace src backtrace libunwind rs backtrace backtrace trace unsynchronized at cargo registry src github com backtrace src backtrace mod rs std sys common backtrace print fmt at src libstd sys common backtrace rs fmt at src libstd sys common backtrace rs core fmt write at src libcore fmt mod rs std io write write fmt at src libstd io mod rs std sys common backtrace print at src libstd sys common backtrace rs std sys common backtrace print at src libstd sys common backtrace rs std panicking default hook closure at src libstd panicking rs std panicking default hook at src libstd panicking rs std panicking rust panic with hook at src libstd panicking rs std panicking begin panic at rustc src libstd panicking rs integrations test cdc test cdc not leader at components cdc tests integrations test cdc rs integrations test cdc test cdc not leader closure at components cdc tests integrations test cdc rs core ops function fnonce call once at rustc src libcore ops function rs as core ops function fnonce call once at rustc src liballoc boxed rs rust maybe catch panic at src libpanic unwind lib rs std panicking try at rustc src libstd panicking rs std panic catch unwind at rustc src libstd panic rs test run test in process at src libtest lib rs test run test run test inner closure at src libtest lib rs test run test run test inner at src libtest lib rs test run test at src libtest lib rs test run tests at src libtest lib rs test console run tests console at src libtest console rs test test main at src libtest lib rs test test main static at src libtest lib rs integrations main std rt lang start closure at rustc src libstd rt rs std rt lang start internal closure at src libstd rt rs std panicking try do call at src libstd panicking rs rust maybe catch panic at src libpanic unwind lib rs std panicking try at src libstd panicking rs std panic catch unwind at src libstd panic rs std rt lang start internal at src libstd rt rs std rt lang start at rustc src libstd rt rs main libc start main note some details are omitted run with rust backtrace full for a verbose backtrace failed failures failures test cdc test cdc not leader | 0 |
137,339 | 12,750,894,394 | IssuesEvent | 2020-06-27 07:35:13 | TesseractCoding/NeoAlgo | https://api.github.com/repos/TesseractCoding/NeoAlgo | opened | Implementation of Brick Sort/ Odd even sort | documentation enhancement good first issue | **Algorithm: Implementation Of [Brick Sort](https://en.wikipedia.org/wiki/Odd%E2%80%93even_sort)**
an odd–even sort or odd–even transposition sort (also known as brick sort or parity sort) is a relatively simple sorting algorithm, developed originally for use on parallel processors with local interconnections. It is a comparison sort related to bubble sort, It is a comparison sort related to bubble sort, with which it shares many characteristics.
**Languages Supported:**
- C
- C++
- C#
- Java
- Python
- go
- dart
| 1.0 | Implementation of Brick Sort/ Odd even sort - **Algorithm: Implementation Of [Brick Sort](https://en.wikipedia.org/wiki/Odd%E2%80%93even_sort)**
an odd–even sort or odd–even transposition sort (also known as brick sort or parity sort) is a relatively simple sorting algorithm, developed originally for use on parallel processors with local interconnections. It is a comparison sort related to bubble sort, It is a comparison sort related to bubble sort, with which it shares many characteristics.
**Languages Supported:**
- C
- C++
- C#
- Java
- Python
- go
- dart
| non_priority | implementation of brick sort odd even sort algorithm implementation of an odd–even sort or odd–even transposition sort also known as brick sort or parity sort is a relatively simple sorting algorithm developed originally for use on parallel processors with local interconnections it is a comparison sort related to bubble sort it is a comparison sort related to bubble sort with which it shares many characteristics languages supported c c c java python go dart | 0 |
449,545 | 31,849,791,932 | IssuesEvent | 2023-09-14 23:58:11 | perturbo-code/perturbopy | https://api.github.com/repos/perturbo-code/perturbopy | opened | Awful README.md | documentation help wanted usability | Hey guys,
We need to format README.md properly. Firstly, it is necessary for people to have information when viewing the package on PyPI, and secondly, it is not quite clear from the repository in general what kind of package it is. A link to the documentation does not help in this case. | 1.0 | Awful README.md - Hey guys,
We need to format README.md properly. Firstly, it is necessary for people to have information when viewing the package on PyPI, and secondly, it is not quite clear from the repository in general what kind of package it is. A link to the documentation does not help in this case. | non_priority | awful readme md hey guys we need to format readme md properly firstly it is necessary for people to have information when viewing the package on pypi and secondly it is not quite clear from the repository in general what kind of package it is a link to the documentation does not help in this case | 0 |
30,260 | 13,220,222,309 | IssuesEvent | 2020-08-17 12:00:51 | kyma-incubator/compass | https://api.github.com/repos/kyma-incubator/compass | closed | KEB is unavailable for a transient period during rolling update | area/management-plane area/service-catalog | **Description**
I have noticed short availability check failures for kyma environment broker during rolling update.
The availability check probes the `http://compass-kyma-environment-broker.compass-system:15020/app-health/kyma-environment-broker/livez` URL, so it goes through the istio proxy and it's probe rewrite/hijack functionality.
During the failure, no HTTP response was received but the connection was terminated quickly, hence I'm suspecting the istio proxy sidecar terminated the connection.
I suspect since no K8S readiness probe is specified for the KEB container, the pod is considered ready even though istio proxy is not ready to forward traffic to KEB container. A possible solution could be to specify the same /healthz endpoint for readiness probe, so that the pod is only added to the `Endpoints` resource when the HTTP probe through the istio proxy goes through.
| 1.0 | KEB is unavailable for a transient period during rolling update - **Description**
I have noticed short availability check failures for kyma environment broker during rolling update.
The availability check probes the `http://compass-kyma-environment-broker.compass-system:15020/app-health/kyma-environment-broker/livez` URL, so it goes through the istio proxy and it's probe rewrite/hijack functionality.
During the failure, no HTTP response was received but the connection was terminated quickly, hence I'm suspecting the istio proxy sidecar terminated the connection.
I suspect since no K8S readiness probe is specified for the KEB container, the pod is considered ready even though istio proxy is not ready to forward traffic to KEB container. A possible solution could be to specify the same /healthz endpoint for readiness probe, so that the pod is only added to the `Endpoints` resource when the HTTP probe through the istio proxy goes through.
| non_priority | keb is unavailable for a transient period during rolling update description i have noticed short availability check failures for kyma environment broker during rolling update the availability check probes the url so it goes through the istio proxy and it s probe rewrite hijack functionality during the failure no http response was received but the connection was terminated quickly hence i m suspecting the istio proxy sidecar terminated the connection i suspect since no readiness probe is specified for the keb container the pod is considered ready even though istio proxy is not ready to forward traffic to keb container a possible solution could be to specify the same healthz endpoint for readiness probe so that the pod is only added to the endpoints resource when the http probe through the istio proxy goes through | 0 |
150,770 | 13,358,478,496 | IssuesEvent | 2020-08-31 11:46:40 | EddLabs/eddington | https://api.github.com/repos/EddLabs/eddington | closed | Automatic Documentation of FitResult | documentation good first issue | We should add automatic documentation for the `FitResult` class in the *docs/api* folder.
[This](https://raw.githubusercontent.com/EddLabs/eddington/master/docs/api/fit_data.rst) is how the *rst* source file should look like, and [this](https://eddington.readthedocs.io/en/latest/api/fit_data.html) is how the HTML result should look like in [ReadTheDocs](https://eddington.readthedocs.io/en/latest/). | 1.0 | Automatic Documentation of FitResult - We should add automatic documentation for the `FitResult` class in the *docs/api* folder.
[This](https://raw.githubusercontent.com/EddLabs/eddington/master/docs/api/fit_data.rst) is how the *rst* source file should look like, and [this](https://eddington.readthedocs.io/en/latest/api/fit_data.html) is how the HTML result should look like in [ReadTheDocs](https://eddington.readthedocs.io/en/latest/). | non_priority | automatic documentation of fitresult we should add automatic documentation for the fitresult class in the docs api folder is how the rst source file should look like and is how the html result should look like in | 0 |
192,531 | 14,619,620,528 | IssuesEvent | 2020-12-22 18:11:17 | input-output-hk/jormungandr | https://api.github.com/repos/input-output-hk/jormungandr | opened | Panic on tallying private votes | Tests | **Describe the bug**
panic during tallying private vote:
```
thread 'tokio-runtime-worker' panicked at 'assertion failed: `(left == right)`
left: `3`,
right: `2`', C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-vote\src\lib.rs:113:9
stack backtrace:
0: 0x7ff78698e5e9 - std::backtrace_rs::backtrace::dbghelp::trace
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\..\..\backtrace\src\backtrace\dbghelp.rs:98
1: 0x7ff78698e5e9 - std::backtrace_rs::backtrace::trace_unsynchronized
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\..\..\backtrace\src\backtrace\mod.rs:66
2: 0x7ff78698e5e9 - std::sys_common::backtrace::_print_fmt
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:79
3: 0x7ff78698e5e9 - std::sys_common::backtrace::_print::{{impl}}::fmt
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:58
4: 0x7ff7869a8efb - core::fmt::write
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\core\src\fmt\mod.rs:1080
5: 0x7ff7869856c8 - std::io::Write::write_fmt<std::sys::windows::stdio::Stderr>
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\io\mod.rs:1516
6: 0x7ff7869913d4 - std::sys_common::backtrace::_print
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:61
7: 0x7ff7869913d4 - std::sys_common::backtrace::print
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:48
8: 0x7ff7869913d4 - std::panicking::default_hook::{{closure}}
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:208
9: 0x7ff786990fb8 - std::panicking::default_hook
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:227
10: 0x7ff786991c8f - std::panicking::rust_panic_with_hook
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:577
11: 0x7ff7869917f5 - std::panicking::begin_panic_handler::{{closure}}
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:484
12: 0x7ff78698ee9f - std::sys_common::backtrace::__rust_end_short_backtrace<closure-0,!>
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:153
13: 0x7ff7869917a9 - std::panicking::begin_panic_handler
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:483
14: 0x7ff78699175c - std::panicking::begin_panic_fmt
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:437
15: 0x7ff7867d30b8 - chain_vote::EncryptedTally::add
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-vote\src\lib.rs:113
16: 0x7ff7865e0edc - chain_impl_mockchain::vote::manager::ProposalManager::private_tally
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-impl-mockchain\src\vote\manager.rs:193
17: 0x7ff7865e3189 - chain_impl_mockchain::vote::manager::ProposalManagers::private_tally_start
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-impl-mockchain\src\vote\manager.rs:405
18: 0x7ff7865e50cd - chain_impl_mockchain::vote::manager::VotePlanManager::private_tally_start
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-impl-mockchain\src\vote\manager.rs:623
19: 0x7ff786654cf0 - chain_impl_mockchain::vote::ledger::{{impl}}::apply_encrypted_vote_tally::{{closure}}
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-impl-mockchain\src\vote\ledger.rs:193
20: 0x7ff786780ae8 - imhamt::node::reference::update_rec<chain_crypto::digest::DigestOf<chain_crypto::hash::Blake2b256, chain_impl_mockchain::certificate::vote_plan::VotePlan>,chain_impl_mockchain::vote::manager::VotePlanManager,closure-0,chain_impl_mockchain::vote::manager::
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\imhamt\src\node\reference.rs:470
21: 0x7ff7866a82d1 - imhamt::hamt::Hamt<std::collections::hash::map::DefaultHasher, chain_crypto::digest::DigestOf<chain_crypto::hash::Blake2b256, chain_impl_mockchain::certificate::vote_plan::VotePlan>, chain_impl_mockchain::vote::manager::VotePlanManager>::update<std::colle
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\imhamt\src\hamt.rs:138
22: 0x7ff786654a3b - chain_impl_mockchain::vote::ledger::VotePlanLedger::apply_encrypted_vote_tally
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-impl-mockchain\src\vote\ledger.rs:192
23: 0x7ff7866640be - chain_impl_mockchain::ledger::ledger::Ledger::apply_encrypted_vote_tally
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-impl-mockchain\src\ledger\ledger.rs:1168
24: 0x7ff78665c649 - chain_impl_mockchain::ledger::ledger::Ledger::apply_fragment
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-impl-mockchain\src\ledger\ledger.rs:939
25: 0x7ff784897dbf - jormungandr::fragment::selection::{{impl}}::select
at C:\Work\iohk\jormungandr\jormungandr\src\fragment\selection.rs:77
26: 0x7ff7855a0666 - jormungandr::fragment::pool::Pool::select
at C:\Work\iohk\jormungandr\jormungandr\src\fragment\pool.rs:107
27: 0x7ff784de39b7 - jormungandr::fragment::process::{{impl}}::start::{{closure}}
at C:\Work\iohk\jormungandr\jormungandr\src\fragment\process.rs:100
28: 0x7ff7847de459 - core::future::from_generator::{{impl}}::poll<generator-0>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\future\mod.rs:80
29: 0x7ff7854787bc - jormungandr::utils::task::{{impl}}::spawn_try_future::{{closure}}<closure-1,core::future::from_generator::GenFuture<generator-0>,jormungandr::fragment::process::Error>
at C:\Work\iohk\jormungandr\jormungandr\src\utils\task.rs:153
30: 0x7ff7847e6e9a - core::future::from_generator::{{impl}}::poll<generator-0>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\future\mod.rs:80
31: 0x7ff78507d05c - tokio::runtime::task::core::{{impl}}::poll::{{closure}}<core::future::from_generator::GenFuture<generator-0>,alloc::sync::Arc<tokio::runtime::thread_pool::worker::Worker>>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\core.rs:173
32: 0x7ff7855cddfc - tokio::loom::std::unsafe_cell::UnsafeCell<tokio::runtime::task::core::Stage<core::future::from_generator::GenFuture<generator-0>>>::with_mut<tokio::runtime::task::core::Stage<core::future::from_generator::GenFuture<generator-0>>,core::task::poll::Poll<cor
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\loom\std\unsafe_cell.rs:14
33: 0x7ff785073737 - tokio::runtime::task::core::Core<core::future::from_generator::GenFuture<generator-0>, alloc::sync::Arc<tokio::runtime::thread_pool::worker::Worker>>::poll<core::future::from_generator::GenFuture<generator-0>,alloc::sync::Arc<tokio::runtime::thread_pool::
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\core.rs:158
34: 0x7ff784ea0332 - tokio::runtime::task::harness::{{impl}}::poll::{{closure}}<core::future::from_generator::GenFuture<generator-0>,alloc::sync::Arc<tokio::runtime::thread_pool::worker::Worker>>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\harness.rs:107
35: 0x7ff7850fed6a - core::ops::function::FnOnce::call_once<closure-0,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\ops\function.rs:227
36: 0x7ff7854feb7b - std::panic::{{impl}}::call_once<core::task::poll::Poll<core::result::Result<core::result::Result<tuple<>, alloc::boxed::Box<Error>>, tokio::runtime::task::error::JoinError>>,closure-0>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:308
37: 0x7ff78569cb20 - std::panicking::try::do_call<std::panic::AssertUnwindSafe<closure-0>,core::task::poll::Poll<core::result::Result<core::result::Result<tuple<>, alloc::boxed::Box<Error>>, tokio::runtime::task::error::JoinError>>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:381
38: 0x7ff7856a9597 - std::panicking::try::do_catch<std::panic::AssertUnwindSafe<closure-0>,tuple<>>
39: 0x7ff78568a642 - std::panicking::try<core::task::poll::Poll<core::result::Result<core::result::Result<tuple<>, alloc::boxed::Box<Error>>, tokio::runtime::task::error::JoinError>>,std::panic::AssertUnwindSafe<closure-0>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:345
40: 0x7ff7854ff11b - std::panic::catch_unwind<std::panic::AssertUnwindSafe<closure-0>,core::task::poll::Poll<core::result::Result<core::result::Result<tuple<>, alloc::boxed::Box<Error>>, tokio::runtime::task::error::JoinError>>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:382
41: 0x7ff784e870bb - tokio::runtime::task::harness::Harness<core::future::from_generator::GenFuture<generator-0>, alloc::sync::Arc<tokio::runtime::thread_pool::worker::Worker>>::poll<core::future::from_generator::GenFuture<generator-0>,alloc::sync::Arc<tokio::runtime::thread_
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\harness.rs:89
42: 0x7ff784856ba2 - tokio::runtime::task::raw::poll<core::future::from_generator::GenFuture<generator-0>,alloc::sync::Arc<tokio::runtime::thread_pool::worker::Worker>>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\raw.rs:104
43: 0x7ff78637023d - tokio::runtime::task::raw::RawTask::poll
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\raw.rs:66
44: 0x7ff786362417 - tokio::runtime::task::Notified<alloc::sync::Arc<tokio::runtime::thread_pool::worker::Worker>>::run<alloc::sync::Arc<tokio::runtime::thread_pool::worker::Worker>>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\mod.rs:169
45: 0x7ff78632b320 - tokio::runtime::thread_pool::worker::{{impl}}::run_task::{{closure}}
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\thread_pool\worker.rs:370
46: 0x7ff78630f236 - tokio::coop::with_budget::{{closure}}<core::result::Result<alloc::boxed::Box<tokio::runtime::thread_pool::worker::Core>, tuple<>>,closure-0>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\coop.rs:127
47: 0x7ff786348e04 - std::thread::local::LocalKey<core::cell::Cell<tokio::coop::Budget>>::try_with<core::cell::Cell<tokio::coop::Budget>,closure-0,core::result::Result<alloc::boxed::Box<tokio::runtime::thread_pool::worker::Core>, tuple<>>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\thread\local.rs:272
48: 0x7ff786347d7d - std::thread::local::LocalKey<core::cell::Cell<tokio::coop::Budget>>::with<core::cell::Cell<tokio::coop::Budget>,closure-0,core::result::Result<alloc::boxed::Box<tokio::runtime::thread_pool::worker::Core>, tuple<>>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\thread\local.rs:248
49: 0x7ff78632afe0 - tokio::coop::with_budget
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\coop.rs:120
50: 0x7ff78632afe0 - tokio::coop::budget
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\coop.rs:96
51: 0x7ff78632afe0 - tokio::runtime::thread_pool::worker::Context::run_task
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\thread_pool\worker.rs:348
52: 0x7ff78632ab63 - tokio::runtime::thread_pool::worker::Context::run
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\thread_pool\worker.rs:320
53: 0x7ff78632a9ef - tokio::runtime::thread_pool::worker::run::{{closure}}
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\thread_pool\worker.rs:305
54: 0x7ff78630e6d9 - tokio::macros::scoped_tls::ScopedKey<tokio::runtime::thread_pool::worker::Context>::set<tokio::runtime::thread_pool::worker::Context,closure-0,tuple<>>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\macros\scoped_tls.rs:63
55: 0x7ff78632a8bd - tokio::runtime::thread_pool::worker::run
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\thread_pool\worker.rs:302
56: 0x7ff78632a79e - tokio::runtime::thread_pool::worker::{{impl}}::launch::{{closure}}
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\thread_pool\worker.rs:281
57: 0x7ff78637054b - tokio::runtime::blocking::task::{{impl}}::poll<closure-0,tuple<>>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\blocking\task.rs:41
58: 0x7ff786331fca - tokio::runtime::task::core::{{impl}}::poll::{{closure}}<tokio::runtime::blocking::task::BlockingTask<closure-0>,tokio::runtime::blocking::schedule::NoopSchedule>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\core.rs:173
59: 0x7ff78638322a - tokio::loom::std::unsafe_cell::UnsafeCell<tokio::runtime::task::core::Stage<tokio::runtime::blocking::task::BlockingTask<closure-0>>>::with_mut<tokio::runtime::task::core::Stage<tokio::runtime::blocking::task::BlockingTask<closure-0>>,core::task::poll::Po
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\loom\std\unsafe_cell.rs:14
60: 0x7ff786331e0f - tokio::runtime::task::core::Core<tokio::runtime::blocking::task::BlockingTask<closure-0>, tokio::runtime::blocking::schedule::NoopSchedule>::poll<tokio::runtime::blocking::task::BlockingTask<closure-0>,tokio::runtime::blocking::schedule::NoopSchedule>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\core.rs:158
61: 0x7ff786397781 - tokio::runtime::task::harness::{{impl}}::poll::{{closure}}<tokio::runtime::blocking::task::BlockingTask<closure-0>,tokio::runtime::blocking::schedule::NoopSchedule>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\harness.rs:107
62: 0x7ff78631d42a - core::ops::function::FnOnce::call_once<closure-0,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\ops\function.rs:227
63: 0x7ff786371fdb - std::panic::{{impl}}::call_once<core::task::poll::Poll<core::result::Result<tuple<>, tokio::runtime::task::error::JoinError>>,closure-0>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:308
64: 0x7ff78634abb0 - std::panicking::try::do_call<std::panic::AssertUnwindSafe<closure-0>,core::task::poll::Poll<core::result::Result<tuple<>, tokio::runtime::task::error::JoinError>>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:381
65: 0x7ff786350e47 - tokio::time::driver::entry::{{impl}}::drop
66: 0x7ff78634a9a2 - std::panicking::try<core::task::poll::Poll<core::result::Result<tuple<>, tokio::runtime::task::error::JoinError>>,std::panic::AssertUnwindSafe<closure-0>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:345
67: 0x7ff78637220b - std::panic::catch_unwind<std::panic::AssertUnwindSafe<closure-0>,core::task::poll::Poll<core::result::Result<tuple<>, tokio::runtime::task::error::JoinError>>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:382
68: 0x7ff78639737b - tokio::runtime::task::harness::Harness<tokio::runtime::blocking::task::BlockingTask<closure-0>, tokio::runtime::blocking::schedule::NoopSchedule>::poll<tokio::runtime::blocking::task::BlockingTask<closure-0>,tokio::runtime::blocking::schedule::NoopSchedul
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\harness.rs:89
69: 0x7ff7863703d2 - tokio::runtime::task::raw::poll<tokio::runtime::blocking::task::BlockingTask<closure-0>,tokio::runtime::blocking::schedule::NoopSchedule>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\raw.rs:104
70: 0x7ff78637023d - tokio::runtime::task::raw::RawTask::poll
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\raw.rs:66
71: 0x7ff786362397 - tokio::runtime::task::Notified<tokio::runtime::blocking::schedule::NoopSchedule>::run<tokio::runtime::blocking::schedule::NoopSchedule>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\mod.rs:169
72: 0x7ff78634f542 - tokio::runtime::blocking::pool::Inner::run
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\blocking\pool.rs:250
73: 0x7ff78634f2d4 - tokio::runtime::blocking::pool::{{impl}}::spawn_thread::{{closure}}::{{closure}}
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\blocking\pool.rs:230
74: 0x7ff786316bb4 - tokio::runtime::context::enter<closure-0,tuple<>>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\context.rs:72
75: 0x7ff786343c55 - tokio::runtime::handle::Handle::enter<closure-0,tuple<>>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\handle.rs:76
76: 0x7ff78634f367 - tokio::runtime::blocking::pool::{{impl}}::spawn_thread::{{closure}}
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\blocking\pool.rs:229
77: 0x7ff78632dd9a - std::sys_common::backtrace::__rust_begin_short_backtrace<closure-0,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\sys_common\backtrace.rs:137
78: 0x7ff7863011a3 - std::thread::{{impl}}::spawn_unchecked::{{closure}}::{{closure}}<closure-0,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\thread\mod.rs:464
79: 0x7ff786372026 - std::panic::{{impl}}::call_once<tuple<>,closure-0>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:308
80: 0x7ff78634aafd - std::panicking::try::do_call<std::panic::AssertUnwindSafe<closure-0>,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:381
81: 0x7ff786350e47 - tokio::time::driver::entry::{{impl}}::drop
82: 0x7ff78634a7aa - std::panicking::try<tuple<>,std::panic::AssertUnwindSafe<closure-0>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:345
83: 0x7ff786372256 - std::panic::catch_unwind<std::panic::AssertUnwindSafe<closure-0>,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:382
84: 0x7ff786300fc6 - std::thread::{{impl}}::spawn_unchecked::{{closure}}<closure-0,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\thread\mod.rs:463
85: 0x7ff78631d2de - core::ops::function::FnOnce::call_once<closure-0,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\ops\function.rs:227
86: 0x7ff786996f87 - alloc::boxed::{{impl}}::call_once
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\alloc\src\boxed.rs:1042
87: 0x7ff786996f87 - alloc::boxed::{{impl}}::call_once
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\alloc\src\boxed.rs:1042
88: 0x7ff786996f87 - std::sys::windows::thread::{{impl}}::new::thread_start
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys\windows\thread.rs:56
89: 0x7ff9e2407034 - BaseThreadInitThunk
90: 0x7ff9e31bd0d1 - RtlUserThreadStart
Standard Output:
Standard Error: error when trying to perform an HTTP request
|-> node internal error
|-> HTTP status server error (500 Internal Server Error) for url (http://127.0.0.1:6723/api/v0/fragment/logs)
non-zero status with message(). waiting 1 s and trying again (4 of 5)
A service has terminated with an error
|-> service panicked: assertion failed: `(left == right)`
left: `3`,
right: `2`
Standard Output:
Standard Error: error when trying to perform an HTTP request
|-> communication with node failed in unexpected way
|-> error sending request for url (http://127.0.0.1:6723/api/v0/fragment/logs): error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> No connection could be made because the target machine actively refused it. (os error 10061)
thread 'jormungandr::vit::private::jcli_e2e_flow_private_vote' panicked at 'Unexpected failure.
code-1
stderr=```error when trying to perform an HTTP request
|-> communication with node failed in unexpected way
|-> error sending request for url (http://127.0.0.1:6723/api/v0/fragment/logs): error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> No connection could be made because the target machine actively refused it. (os error 10061)
```
command=`"C:\\Work\\iohk\\jormungandr\\target\\debug\\jcli.exe" "rest" "v0" "message" "logs" "--host" "http://127.0.0.1:6723/api"`
code=1
stdout=``````
stderr=```error when trying to perform an HTTP request
|-> communication with node failed in unexpected way
|-> error sending request for url (http://127.0.0.1:6723/api/v0/fragment/logs): error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> No connection could be made because the target machine actively refused it. (os error 10061)
```
', C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\assert_cmd-1.0.2\src\assert.rs:158:13
stack backtrace:
0: 0x7ff6757007a9 - std::backtrace_rs::backtrace::dbghelp::trace
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\..\..\backtrace\src\backtrace\dbghelp.rs:98
1: 0x7ff6757007a9 - std::backtrace_rs::backtrace::trace_unsynchronized
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\..\..\backtrace\src\backtrace\mod.rs:66
2: 0x7ff6757007a9 - std::sys_common::backtrace::_print_fmt
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:79
3: 0x7ff6757007a9 - std::sys_common::backtrace::_print::{{impl}}::fmt
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:58
4: 0x7ff6757212ab - core::fmt::write
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\core\src\fmt\mod.rs:1080
5: 0x7ff6756f67c8 - std::io::Write::write_fmt<std::sys::windows::stdio::Stderr>
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\io\mod.rs:1516
6: 0x7ff675703a54 - std::sys_common::backtrace::_print
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:61
7: 0x7ff675703a54 - std::sys_common::backtrace::print
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:48
8: 0x7ff675703a54 - std::panicking::default_hook::{{closure}}
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:208
9: 0x7ff675703638 - std::panicking::default_hook
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:227
10: 0x7ff67570430f - std::panicking::rust_panic_with_hook
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:577
11: 0x7ff675703e75 - std::panicking::begin_panic_handler::{{closure}}
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:484
12: 0x7ff67570105f - std::sys_common::backtrace::__rust_end_short_backtrace<closure-0,!>
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:153
13: 0x7ff675703e29 - std::panicking::begin_panic_handler
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:483
14: 0x7ff675703ddc - std::panicking::begin_panic_fmt
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:437
15: 0x7ff674509d9e - assert_cmd::assert::Assert::success
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\assert_cmd-1.0.2\src\assert.rs:158
16: 0x7ff6744946cc - jormungandr_integration_tests::common::jcli::api::rest::v0::message::Message::logs<alloc::string::String*>
at C:\Work\iohk\jormungandr\testing\jormungandr-integration-tests\src\common\jcli\api\rest\v0\message.rs:33
17: 0x7ff67425f540 - jormungandr_integration_tests::common::jcli::services::fragment_check::{{impl}}::wait_until_processed::{{closure}}
at C:\Work\iohk\jormungandr\testing\jormungandr-integration-tests\src\common\jcli\services\fragment_check.rs:92
18: 0x7ff6743a3143 - core::result::Result<chain_impl_mockchain::key::Hash, jortestkit::process::ProcessError>::map_err<chain_impl_mockchain::key::Hash,jortestkit::process::ProcessError,jormungandr_integration_tests::common::jcli::services::Error,closure-2>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\result.rs:595
19: 0x7ff67446b602 - jormungandr_integration_tests::common::jcli::services::fragment_check::FragmentCheck::wait_until_processed
at C:\Work\iohk\jormungandr\testing\jormungandr-integration-tests\src\common\jcli\services\fragment_check.rs:51
20: 0x7ff67446b066 - jormungandr_integration_tests::common::jcli::services::fragment_check::FragmentCheck::assert_in_block_with_wait
at C:\Work\iohk\jormungandr\testing\jormungandr-integration-tests\src\common\jcli\services\fragment_check.rs:40
21: 0x7ff67446b01c - jormungandr_integration_tests::common::jcli::services::fragment_check::FragmentCheck::assert_in_block
at C:\Work\iohk\jormungandr\testing\jormungandr-integration-tests\src\common\jcli\services\fragment_check.rs:36
22: 0x7ff674415624 - jormungandr_integration_tests::jormungandr::vit::private::jcli_e2e_flow_private_vote
at C:\Work\iohk\jormungandr\testing\jormungandr-integration-tests\src\jormungandr\vit\private.rs:188
23: 0x7ff6742f0cbe - jormungandr_integration_tests::jormungandr::vit::private::jcli_e2e_flow_private_vote::{{closure}}
at C:\Work\iohk\jormungandr\testing\jormungandr-integration-tests\src\jormungandr\vit\private.rs:25
24: 0x7ff6743c20db - core::ops::function::FnOnce::call_once<closure-0,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\ops\function.rs:227
25: 0x7ff6744f14e6 - core::ops::function::FnOnce::call_once
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\core\src\ops\function.rs:227
26: 0x7ff6744f14e6 - test::__rust_begin_short_backtrace<fn()>
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\test\src\lib.rs:516
27: 0x7ff6744eee1e - alloc::boxed::{{impl}}::call_once
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\alloc\src\boxed.rs:1042
28: 0x7ff6744eee1e - std::panic::{{impl}}::call_once
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\panic.rs:308
29: 0x7ff6744eee1e - std::panicking::try::do_call
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\panicking.rs:381
30: 0x7ff6744eee1e - std::panicking::try
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\panicking.rs:345
31: 0x7ff6744eee1e - std::panic::catch_unwind
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\panic.rs:382
32: 0x7ff6744eee1e - test::run_test_in_process
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\test\src\lib.rs:543
33: 0x7ff6744eee1e - test::run_test::run_test_inner::{{closure}}
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\test\src\lib.rs:449
34: 0x7ff6744c0376 - std::sys_common::backtrace::__rust_begin_short_backtrace<closure-0,tuple<>>
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\sys_common\backtrace.rs:137
35: 0x7ff6744c0376 - std::sys_common::backtrace::__rust_begin_short_backtrace<closure-0,tuple<>>
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\sys_common\backtrace.rs:137
36: 0x7ff6744c723e - std::thread::{{impl}}::spawn_unchecked::{{closure}}::{{closure}}
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\thread\mod.rs:464
37: 0x7ff6744c723e - std::panic::{{impl}}::call_once
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\panic.rs:308
38: 0x7ff6744c723e - std::panicking::try::do_call
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\panicking.rs:381
39: 0x7ff6744c723e - std::panicking::try
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\panicking.rs:345
40: 0x7ff6744c723e - std::panic::catch_unwind
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\panic.rs:382
41: 0x7ff6744c723e - std::thread::{{impl}}::spawn_unchecked::{{closure}}
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\thread\mod.rs:463
42: 0x7ff6744c723e - core::ops::function::FnOnce::call_once<closure-0,tuple<>>
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\core\src\ops\function.rs:227
43: 0x7ff67570f9f7 - alloc::boxed::{{impl}}::call_once
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\alloc\src\boxed.rs:1042
44: 0x7ff67570f9f7 - alloc::boxed::{{impl}}::call_once
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\alloc\src\boxed.rs:1042
45: 0x7ff67570f9f7 - std::sys::windows::thread::{{impl}}::new::thread_start
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys\windows\thread.rs:56
46: 0x7ff9e2407034 - BaseThreadInitThunk
47: 0x7ff9e31bd0d1 - RtlUserThreadStart
Error lines:
{"msg":"servicefinishedwitherror","level":"ERRO","ts":"2020-12-22T18:57:01.994343700+01:00","task":"leadership","reason":"fragmentselectionfailed"}
{"msg":"Servicehasterminatedwithanerror","level":"CRIT","ts":"2020-12-22T18:57:01.999725200+01:00","reason":"servicepanicked:assertionfailed:`(left==right)`\nleft:`3`,\nright:`2`"}
test jormungandr::vit::private::jcli_e2e_flow_private_vote ... FAILED
failures:
failures:
jormungandr::vit::private::jcli_e2e_flow_private_vote
```
**Mandatory Information**
1. `jcli --full-version` newest master;
2. `jormungandr --full-version` newest master;
**To Reproduce**
Steps to reproduce the behavior:
1. checkout branch `private_vote`
2. run test ` jormungandr::vit::private::jcli_e2e_flow_private_vote`
| 1.0 | Panic on tallying private votes - **Describe the bug**
panic during tallying private vote:
```
thread 'tokio-runtime-worker' panicked at 'assertion failed: `(left == right)`
left: `3`,
right: `2`', C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-vote\src\lib.rs:113:9
stack backtrace:
0: 0x7ff78698e5e9 - std::backtrace_rs::backtrace::dbghelp::trace
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\..\..\backtrace\src\backtrace\dbghelp.rs:98
1: 0x7ff78698e5e9 - std::backtrace_rs::backtrace::trace_unsynchronized
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\..\..\backtrace\src\backtrace\mod.rs:66
2: 0x7ff78698e5e9 - std::sys_common::backtrace::_print_fmt
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:79
3: 0x7ff78698e5e9 - std::sys_common::backtrace::_print::{{impl}}::fmt
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:58
4: 0x7ff7869a8efb - core::fmt::write
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\core\src\fmt\mod.rs:1080
5: 0x7ff7869856c8 - std::io::Write::write_fmt<std::sys::windows::stdio::Stderr>
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\io\mod.rs:1516
6: 0x7ff7869913d4 - std::sys_common::backtrace::_print
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:61
7: 0x7ff7869913d4 - std::sys_common::backtrace::print
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:48
8: 0x7ff7869913d4 - std::panicking::default_hook::{{closure}}
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:208
9: 0x7ff786990fb8 - std::panicking::default_hook
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:227
10: 0x7ff786991c8f - std::panicking::rust_panic_with_hook
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:577
11: 0x7ff7869917f5 - std::panicking::begin_panic_handler::{{closure}}
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:484
12: 0x7ff78698ee9f - std::sys_common::backtrace::__rust_end_short_backtrace<closure-0,!>
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:153
13: 0x7ff7869917a9 - std::panicking::begin_panic_handler
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:483
14: 0x7ff78699175c - std::panicking::begin_panic_fmt
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:437
15: 0x7ff7867d30b8 - chain_vote::EncryptedTally::add
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-vote\src\lib.rs:113
16: 0x7ff7865e0edc - chain_impl_mockchain::vote::manager::ProposalManager::private_tally
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-impl-mockchain\src\vote\manager.rs:193
17: 0x7ff7865e3189 - chain_impl_mockchain::vote::manager::ProposalManagers::private_tally_start
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-impl-mockchain\src\vote\manager.rs:405
18: 0x7ff7865e50cd - chain_impl_mockchain::vote::manager::VotePlanManager::private_tally_start
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-impl-mockchain\src\vote\manager.rs:623
19: 0x7ff786654cf0 - chain_impl_mockchain::vote::ledger::{{impl}}::apply_encrypted_vote_tally::{{closure}}
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-impl-mockchain\src\vote\ledger.rs:193
20: 0x7ff786780ae8 - imhamt::node::reference::update_rec<chain_crypto::digest::DigestOf<chain_crypto::hash::Blake2b256, chain_impl_mockchain::certificate::vote_plan::VotePlan>,chain_impl_mockchain::vote::manager::VotePlanManager,closure-0,chain_impl_mockchain::vote::manager::
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\imhamt\src\node\reference.rs:470
21: 0x7ff7866a82d1 - imhamt::hamt::Hamt<std::collections::hash::map::DefaultHasher, chain_crypto::digest::DigestOf<chain_crypto::hash::Blake2b256, chain_impl_mockchain::certificate::vote_plan::VotePlan>, chain_impl_mockchain::vote::manager::VotePlanManager>::update<std::colle
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\imhamt\src\hamt.rs:138
22: 0x7ff786654a3b - chain_impl_mockchain::vote::ledger::VotePlanLedger::apply_encrypted_vote_tally
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-impl-mockchain\src\vote\ledger.rs:192
23: 0x7ff7866640be - chain_impl_mockchain::ledger::ledger::Ledger::apply_encrypted_vote_tally
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-impl-mockchain\src\ledger\ledger.rs:1168
24: 0x7ff78665c649 - chain_impl_mockchain::ledger::ledger::Ledger::apply_fragment
at C:\Users\Dariusz\.cargo\git\checkouts\chain-libs-352b144b1a97bf6e\a7b6603\chain-impl-mockchain\src\ledger\ledger.rs:939
25: 0x7ff784897dbf - jormungandr::fragment::selection::{{impl}}::select
at C:\Work\iohk\jormungandr\jormungandr\src\fragment\selection.rs:77
26: 0x7ff7855a0666 - jormungandr::fragment::pool::Pool::select
at C:\Work\iohk\jormungandr\jormungandr\src\fragment\pool.rs:107
27: 0x7ff784de39b7 - jormungandr::fragment::process::{{impl}}::start::{{closure}}
at C:\Work\iohk\jormungandr\jormungandr\src\fragment\process.rs:100
28: 0x7ff7847de459 - core::future::from_generator::{{impl}}::poll<generator-0>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\future\mod.rs:80
29: 0x7ff7854787bc - jormungandr::utils::task::{{impl}}::spawn_try_future::{{closure}}<closure-1,core::future::from_generator::GenFuture<generator-0>,jormungandr::fragment::process::Error>
at C:\Work\iohk\jormungandr\jormungandr\src\utils\task.rs:153
30: 0x7ff7847e6e9a - core::future::from_generator::{{impl}}::poll<generator-0>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\future\mod.rs:80
31: 0x7ff78507d05c - tokio::runtime::task::core::{{impl}}::poll::{{closure}}<core::future::from_generator::GenFuture<generator-0>,alloc::sync::Arc<tokio::runtime::thread_pool::worker::Worker>>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\core.rs:173
32: 0x7ff7855cddfc - tokio::loom::std::unsafe_cell::UnsafeCell<tokio::runtime::task::core::Stage<core::future::from_generator::GenFuture<generator-0>>>::with_mut<tokio::runtime::task::core::Stage<core::future::from_generator::GenFuture<generator-0>>,core::task::poll::Poll<cor
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\loom\std\unsafe_cell.rs:14
33: 0x7ff785073737 - tokio::runtime::task::core::Core<core::future::from_generator::GenFuture<generator-0>, alloc::sync::Arc<tokio::runtime::thread_pool::worker::Worker>>::poll<core::future::from_generator::GenFuture<generator-0>,alloc::sync::Arc<tokio::runtime::thread_pool::
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\core.rs:158
34: 0x7ff784ea0332 - tokio::runtime::task::harness::{{impl}}::poll::{{closure}}<core::future::from_generator::GenFuture<generator-0>,alloc::sync::Arc<tokio::runtime::thread_pool::worker::Worker>>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\harness.rs:107
35: 0x7ff7850fed6a - core::ops::function::FnOnce::call_once<closure-0,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\ops\function.rs:227
36: 0x7ff7854feb7b - std::panic::{{impl}}::call_once<core::task::poll::Poll<core::result::Result<core::result::Result<tuple<>, alloc::boxed::Box<Error>>, tokio::runtime::task::error::JoinError>>,closure-0>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:308
37: 0x7ff78569cb20 - std::panicking::try::do_call<std::panic::AssertUnwindSafe<closure-0>,core::task::poll::Poll<core::result::Result<core::result::Result<tuple<>, alloc::boxed::Box<Error>>, tokio::runtime::task::error::JoinError>>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:381
38: 0x7ff7856a9597 - std::panicking::try::do_catch<std::panic::AssertUnwindSafe<closure-0>,tuple<>>
39: 0x7ff78568a642 - std::panicking::try<core::task::poll::Poll<core::result::Result<core::result::Result<tuple<>, alloc::boxed::Box<Error>>, tokio::runtime::task::error::JoinError>>,std::panic::AssertUnwindSafe<closure-0>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:345
40: 0x7ff7854ff11b - std::panic::catch_unwind<std::panic::AssertUnwindSafe<closure-0>,core::task::poll::Poll<core::result::Result<core::result::Result<tuple<>, alloc::boxed::Box<Error>>, tokio::runtime::task::error::JoinError>>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:382
41: 0x7ff784e870bb - tokio::runtime::task::harness::Harness<core::future::from_generator::GenFuture<generator-0>, alloc::sync::Arc<tokio::runtime::thread_pool::worker::Worker>>::poll<core::future::from_generator::GenFuture<generator-0>,alloc::sync::Arc<tokio::runtime::thread_
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\harness.rs:89
42: 0x7ff784856ba2 - tokio::runtime::task::raw::poll<core::future::from_generator::GenFuture<generator-0>,alloc::sync::Arc<tokio::runtime::thread_pool::worker::Worker>>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\raw.rs:104
43: 0x7ff78637023d - tokio::runtime::task::raw::RawTask::poll
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\raw.rs:66
44: 0x7ff786362417 - tokio::runtime::task::Notified<alloc::sync::Arc<tokio::runtime::thread_pool::worker::Worker>>::run<alloc::sync::Arc<tokio::runtime::thread_pool::worker::Worker>>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\mod.rs:169
45: 0x7ff78632b320 - tokio::runtime::thread_pool::worker::{{impl}}::run_task::{{closure}}
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\thread_pool\worker.rs:370
46: 0x7ff78630f236 - tokio::coop::with_budget::{{closure}}<core::result::Result<alloc::boxed::Box<tokio::runtime::thread_pool::worker::Core>, tuple<>>,closure-0>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\coop.rs:127
47: 0x7ff786348e04 - std::thread::local::LocalKey<core::cell::Cell<tokio::coop::Budget>>::try_with<core::cell::Cell<tokio::coop::Budget>,closure-0,core::result::Result<alloc::boxed::Box<tokio::runtime::thread_pool::worker::Core>, tuple<>>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\thread\local.rs:272
48: 0x7ff786347d7d - std::thread::local::LocalKey<core::cell::Cell<tokio::coop::Budget>>::with<core::cell::Cell<tokio::coop::Budget>,closure-0,core::result::Result<alloc::boxed::Box<tokio::runtime::thread_pool::worker::Core>, tuple<>>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\thread\local.rs:248
49: 0x7ff78632afe0 - tokio::coop::with_budget
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\coop.rs:120
50: 0x7ff78632afe0 - tokio::coop::budget
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\coop.rs:96
51: 0x7ff78632afe0 - tokio::runtime::thread_pool::worker::Context::run_task
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\thread_pool\worker.rs:348
52: 0x7ff78632ab63 - tokio::runtime::thread_pool::worker::Context::run
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\thread_pool\worker.rs:320
53: 0x7ff78632a9ef - tokio::runtime::thread_pool::worker::run::{{closure}}
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\thread_pool\worker.rs:305
54: 0x7ff78630e6d9 - tokio::macros::scoped_tls::ScopedKey<tokio::runtime::thread_pool::worker::Context>::set<tokio::runtime::thread_pool::worker::Context,closure-0,tuple<>>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\macros\scoped_tls.rs:63
55: 0x7ff78632a8bd - tokio::runtime::thread_pool::worker::run
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\thread_pool\worker.rs:302
56: 0x7ff78632a79e - tokio::runtime::thread_pool::worker::{{impl}}::launch::{{closure}}
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\thread_pool\worker.rs:281
57: 0x7ff78637054b - tokio::runtime::blocking::task::{{impl}}::poll<closure-0,tuple<>>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\blocking\task.rs:41
58: 0x7ff786331fca - tokio::runtime::task::core::{{impl}}::poll::{{closure}}<tokio::runtime::blocking::task::BlockingTask<closure-0>,tokio::runtime::blocking::schedule::NoopSchedule>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\core.rs:173
59: 0x7ff78638322a - tokio::loom::std::unsafe_cell::UnsafeCell<tokio::runtime::task::core::Stage<tokio::runtime::blocking::task::BlockingTask<closure-0>>>::with_mut<tokio::runtime::task::core::Stage<tokio::runtime::blocking::task::BlockingTask<closure-0>>,core::task::poll::Po
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\loom\std\unsafe_cell.rs:14
60: 0x7ff786331e0f - tokio::runtime::task::core::Core<tokio::runtime::blocking::task::BlockingTask<closure-0>, tokio::runtime::blocking::schedule::NoopSchedule>::poll<tokio::runtime::blocking::task::BlockingTask<closure-0>,tokio::runtime::blocking::schedule::NoopSchedule>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\core.rs:158
61: 0x7ff786397781 - tokio::runtime::task::harness::{{impl}}::poll::{{closure}}<tokio::runtime::blocking::task::BlockingTask<closure-0>,tokio::runtime::blocking::schedule::NoopSchedule>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\harness.rs:107
62: 0x7ff78631d42a - core::ops::function::FnOnce::call_once<closure-0,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\ops\function.rs:227
63: 0x7ff786371fdb - std::panic::{{impl}}::call_once<core::task::poll::Poll<core::result::Result<tuple<>, tokio::runtime::task::error::JoinError>>,closure-0>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:308
64: 0x7ff78634abb0 - std::panicking::try::do_call<std::panic::AssertUnwindSafe<closure-0>,core::task::poll::Poll<core::result::Result<tuple<>, tokio::runtime::task::error::JoinError>>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:381
65: 0x7ff786350e47 - tokio::time::driver::entry::{{impl}}::drop
66: 0x7ff78634a9a2 - std::panicking::try<core::task::poll::Poll<core::result::Result<tuple<>, tokio::runtime::task::error::JoinError>>,std::panic::AssertUnwindSafe<closure-0>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:345
67: 0x7ff78637220b - std::panic::catch_unwind<std::panic::AssertUnwindSafe<closure-0>,core::task::poll::Poll<core::result::Result<tuple<>, tokio::runtime::task::error::JoinError>>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:382
68: 0x7ff78639737b - tokio::runtime::task::harness::Harness<tokio::runtime::blocking::task::BlockingTask<closure-0>, tokio::runtime::blocking::schedule::NoopSchedule>::poll<tokio::runtime::blocking::task::BlockingTask<closure-0>,tokio::runtime::blocking::schedule::NoopSchedul
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\harness.rs:89
69: 0x7ff7863703d2 - tokio::runtime::task::raw::poll<tokio::runtime::blocking::task::BlockingTask<closure-0>,tokio::runtime::blocking::schedule::NoopSchedule>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\raw.rs:104
70: 0x7ff78637023d - tokio::runtime::task::raw::RawTask::poll
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\raw.rs:66
71: 0x7ff786362397 - tokio::runtime::task::Notified<tokio::runtime::blocking::schedule::NoopSchedule>::run<tokio::runtime::blocking::schedule::NoopSchedule>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\task\mod.rs:169
72: 0x7ff78634f542 - tokio::runtime::blocking::pool::Inner::run
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\blocking\pool.rs:250
73: 0x7ff78634f2d4 - tokio::runtime::blocking::pool::{{impl}}::spawn_thread::{{closure}}::{{closure}}
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\blocking\pool.rs:230
74: 0x7ff786316bb4 - tokio::runtime::context::enter<closure-0,tuple<>>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\context.rs:72
75: 0x7ff786343c55 - tokio::runtime::handle::Handle::enter<closure-0,tuple<>>
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\handle.rs:76
76: 0x7ff78634f367 - tokio::runtime::blocking::pool::{{impl}}::spawn_thread::{{closure}}
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-0.2.24\src\runtime\blocking\pool.rs:229
77: 0x7ff78632dd9a - std::sys_common::backtrace::__rust_begin_short_backtrace<closure-0,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\sys_common\backtrace.rs:137
78: 0x7ff7863011a3 - std::thread::{{impl}}::spawn_unchecked::{{closure}}::{{closure}}<closure-0,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\thread\mod.rs:464
79: 0x7ff786372026 - std::panic::{{impl}}::call_once<tuple<>,closure-0>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:308
80: 0x7ff78634aafd - std::panicking::try::do_call<std::panic::AssertUnwindSafe<closure-0>,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:381
81: 0x7ff786350e47 - tokio::time::driver::entry::{{impl}}::drop
82: 0x7ff78634a7aa - std::panicking::try<tuple<>,std::panic::AssertUnwindSafe<closure-0>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:345
83: 0x7ff786372256 - std::panic::catch_unwind<std::panic::AssertUnwindSafe<closure-0>,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:382
84: 0x7ff786300fc6 - std::thread::{{impl}}::spawn_unchecked::{{closure}}<closure-0,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\thread\mod.rs:463
85: 0x7ff78631d2de - core::ops::function::FnOnce::call_once<closure-0,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\ops\function.rs:227
86: 0x7ff786996f87 - alloc::boxed::{{impl}}::call_once
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\alloc\src\boxed.rs:1042
87: 0x7ff786996f87 - alloc::boxed::{{impl}}::call_once
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\alloc\src\boxed.rs:1042
88: 0x7ff786996f87 - std::sys::windows::thread::{{impl}}::new::thread_start
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys\windows\thread.rs:56
89: 0x7ff9e2407034 - BaseThreadInitThunk
90: 0x7ff9e31bd0d1 - RtlUserThreadStart
Standard Output:
Standard Error: error when trying to perform an HTTP request
|-> node internal error
|-> HTTP status server error (500 Internal Server Error) for url (http://127.0.0.1:6723/api/v0/fragment/logs)
non-zero status with message(). waiting 1 s and trying again (4 of 5)
A service has terminated with an error
|-> service panicked: assertion failed: `(left == right)`
left: `3`,
right: `2`
Standard Output:
Standard Error: error when trying to perform an HTTP request
|-> communication with node failed in unexpected way
|-> error sending request for url (http://127.0.0.1:6723/api/v0/fragment/logs): error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> No connection could be made because the target machine actively refused it. (os error 10061)
thread 'jormungandr::vit::private::jcli_e2e_flow_private_vote' panicked at 'Unexpected failure.
code-1
stderr=```error when trying to perform an HTTP request
|-> communication with node failed in unexpected way
|-> error sending request for url (http://127.0.0.1:6723/api/v0/fragment/logs): error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> No connection could be made because the target machine actively refused it. (os error 10061)
```
command=`"C:\\Work\\iohk\\jormungandr\\target\\debug\\jcli.exe" "rest" "v0" "message" "logs" "--host" "http://127.0.0.1:6723/api"`
code=1
stdout=``````
stderr=```error when trying to perform an HTTP request
|-> communication with node failed in unexpected way
|-> error sending request for url (http://127.0.0.1:6723/api/v0/fragment/logs): error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
|-> No connection could be made because the target machine actively refused it. (os error 10061)
```
', C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\assert_cmd-1.0.2\src\assert.rs:158:13
stack backtrace:
0: 0x7ff6757007a9 - std::backtrace_rs::backtrace::dbghelp::trace
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\..\..\backtrace\src\backtrace\dbghelp.rs:98
1: 0x7ff6757007a9 - std::backtrace_rs::backtrace::trace_unsynchronized
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\..\..\backtrace\src\backtrace\mod.rs:66
2: 0x7ff6757007a9 - std::sys_common::backtrace::_print_fmt
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:79
3: 0x7ff6757007a9 - std::sys_common::backtrace::_print::{{impl}}::fmt
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:58
4: 0x7ff6757212ab - core::fmt::write
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\core\src\fmt\mod.rs:1080
5: 0x7ff6756f67c8 - std::io::Write::write_fmt<std::sys::windows::stdio::Stderr>
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\io\mod.rs:1516
6: 0x7ff675703a54 - std::sys_common::backtrace::_print
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:61
7: 0x7ff675703a54 - std::sys_common::backtrace::print
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:48
8: 0x7ff675703a54 - std::panicking::default_hook::{{closure}}
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:208
9: 0x7ff675703638 - std::panicking::default_hook
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:227
10: 0x7ff67570430f - std::panicking::rust_panic_with_hook
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:577
11: 0x7ff675703e75 - std::panicking::begin_panic_handler::{{closure}}
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:484
12: 0x7ff67570105f - std::sys_common::backtrace::__rust_end_short_backtrace<closure-0,!>
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys_common\backtrace.rs:153
13: 0x7ff675703e29 - std::panicking::begin_panic_handler
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:483
14: 0x7ff675703ddc - std::panicking::begin_panic_fmt
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\panicking.rs:437
15: 0x7ff674509d9e - assert_cmd::assert::Assert::success
at C:\Users\Dariusz\.cargo\registry\src\github.com-1ecc6299db9ec823\assert_cmd-1.0.2\src\assert.rs:158
16: 0x7ff6744946cc - jormungandr_integration_tests::common::jcli::api::rest::v0::message::Message::logs<alloc::string::String*>
at C:\Work\iohk\jormungandr\testing\jormungandr-integration-tests\src\common\jcli\api\rest\v0\message.rs:33
17: 0x7ff67425f540 - jormungandr_integration_tests::common::jcli::services::fragment_check::{{impl}}::wait_until_processed::{{closure}}
at C:\Work\iohk\jormungandr\testing\jormungandr-integration-tests\src\common\jcli\services\fragment_check.rs:92
18: 0x7ff6743a3143 - core::result::Result<chain_impl_mockchain::key::Hash, jortestkit::process::ProcessError>::map_err<chain_impl_mockchain::key::Hash,jortestkit::process::ProcessError,jormungandr_integration_tests::common::jcli::services::Error,closure-2>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\result.rs:595
19: 0x7ff67446b602 - jormungandr_integration_tests::common::jcli::services::fragment_check::FragmentCheck::wait_until_processed
at C:\Work\iohk\jormungandr\testing\jormungandr-integration-tests\src\common\jcli\services\fragment_check.rs:51
20: 0x7ff67446b066 - jormungandr_integration_tests::common::jcli::services::fragment_check::FragmentCheck::assert_in_block_with_wait
at C:\Work\iohk\jormungandr\testing\jormungandr-integration-tests\src\common\jcli\services\fragment_check.rs:40
21: 0x7ff67446b01c - jormungandr_integration_tests::common::jcli::services::fragment_check::FragmentCheck::assert_in_block
at C:\Work\iohk\jormungandr\testing\jormungandr-integration-tests\src\common\jcli\services\fragment_check.rs:36
22: 0x7ff674415624 - jormungandr_integration_tests::jormungandr::vit::private::jcli_e2e_flow_private_vote
at C:\Work\iohk\jormungandr\testing\jormungandr-integration-tests\src\jormungandr\vit\private.rs:188
23: 0x7ff6742f0cbe - jormungandr_integration_tests::jormungandr::vit::private::jcli_e2e_flow_private_vote::{{closure}}
at C:\Work\iohk\jormungandr\testing\jormungandr-integration-tests\src\jormungandr\vit\private.rs:25
24: 0x7ff6743c20db - core::ops::function::FnOnce::call_once<closure-0,tuple<>>
at C:\Users\Dariusz\.rustup\toolchains\beta-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\ops\function.rs:227
25: 0x7ff6744f14e6 - core::ops::function::FnOnce::call_once
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\core\src\ops\function.rs:227
26: 0x7ff6744f14e6 - test::__rust_begin_short_backtrace<fn()>
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\test\src\lib.rs:516
27: 0x7ff6744eee1e - alloc::boxed::{{impl}}::call_once
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\alloc\src\boxed.rs:1042
28: 0x7ff6744eee1e - std::panic::{{impl}}::call_once
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\panic.rs:308
29: 0x7ff6744eee1e - std::panicking::try::do_call
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\panicking.rs:381
30: 0x7ff6744eee1e - std::panicking::try
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\panicking.rs:345
31: 0x7ff6744eee1e - std::panic::catch_unwind
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\panic.rs:382
32: 0x7ff6744eee1e - test::run_test_in_process
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\test\src\lib.rs:543
33: 0x7ff6744eee1e - test::run_test::run_test_inner::{{closure}}
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\test\src\lib.rs:449
34: 0x7ff6744c0376 - std::sys_common::backtrace::__rust_begin_short_backtrace<closure-0,tuple<>>
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\sys_common\backtrace.rs:137
35: 0x7ff6744c0376 - std::sys_common::backtrace::__rust_begin_short_backtrace<closure-0,tuple<>>
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\sys_common\backtrace.rs:137
36: 0x7ff6744c723e - std::thread::{{impl}}::spawn_unchecked::{{closure}}::{{closure}}
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\thread\mod.rs:464
37: 0x7ff6744c723e - std::panic::{{impl}}::call_once
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\panic.rs:308
38: 0x7ff6744c723e - std::panicking::try::do_call
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\panicking.rs:381
39: 0x7ff6744c723e - std::panicking::try
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\panicking.rs:345
40: 0x7ff6744c723e - std::panic::catch_unwind
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\panic.rs:382
41: 0x7ff6744c723e - std::thread::{{impl}}::spawn_unchecked::{{closure}}
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\std\src\thread\mod.rs:463
42: 0x7ff6744c723e - core::ops::function::FnOnce::call_once<closure-0,tuple<>>
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\core\src\ops\function.rs:227
43: 0x7ff67570f9f7 - alloc::boxed::{{impl}}::call_once
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\alloc\src\boxed.rs:1042
44: 0x7ff67570f9f7 - alloc::boxed::{{impl}}::call_once
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\library\alloc\src\boxed.rs:1042
45: 0x7ff67570f9f7 - std::sys::windows::thread::{{impl}}::new::thread_start
at /rustc/1219014599fd873fcb640b675d8a662150c74e40\/library\std\src\sys\windows\thread.rs:56
46: 0x7ff9e2407034 - BaseThreadInitThunk
47: 0x7ff9e31bd0d1 - RtlUserThreadStart
Error lines:
{"msg":"servicefinishedwitherror","level":"ERRO","ts":"2020-12-22T18:57:01.994343700+01:00","task":"leadership","reason":"fragmentselectionfailed"}
{"msg":"Servicehasterminatedwithanerror","level":"CRIT","ts":"2020-12-22T18:57:01.999725200+01:00","reason":"servicepanicked:assertionfailed:`(left==right)`\nleft:`3`,\nright:`2`"}
test jormungandr::vit::private::jcli_e2e_flow_private_vote ... FAILED
failures:
failures:
jormungandr::vit::private::jcli_e2e_flow_private_vote
```
**Mandatory Information**
1. `jcli --full-version` newest master;
2. `jormungandr --full-version` newest master;
**To Reproduce**
Steps to reproduce the behavior:
1. checkout branch `private_vote`
2. run test ` jormungandr::vit::private::jcli_e2e_flow_private_vote`
| non_priority | panic on tallying private votes describe the bug panic during tallying private vote thread tokio runtime worker panicked at assertion failed left right left right c users dariusz cargo git checkouts chain libs chain vote src lib rs stack backtrace std backtrace rs backtrace dbghelp trace at rustc library std src backtrace src backtrace dbghelp rs std backtrace rs backtrace trace unsynchronized at rustc library std src backtrace src backtrace mod rs std sys common backtrace print fmt at rustc library std src sys common backtrace rs std sys common backtrace print impl fmt at rustc library std src sys common backtrace rs core fmt write at rustc library core src fmt mod rs std io write write fmt at rustc library std src io mod rs std sys common backtrace print at rustc library std src sys common backtrace rs std sys common backtrace print at rustc library std src sys common backtrace rs std panicking default hook closure at rustc library std src panicking rs std panicking default hook at rustc library std src panicking rs std panicking rust panic with hook at rustc library std src panicking rs std panicking begin panic handler closure at rustc library std src panicking rs std sys common backtrace rust end short backtrace at rustc library std src sys common backtrace rs std panicking begin panic handler at rustc library std src panicking rs std panicking begin panic fmt at rustc library std src panicking rs chain vote encryptedtally add at c users dariusz cargo git checkouts chain libs chain vote src lib rs chain impl mockchain vote manager proposalmanager private tally at c users dariusz cargo git checkouts chain libs chain impl mockchain src vote manager rs chain impl mockchain vote manager proposalmanagers private tally start at c users dariusz cargo git checkouts chain libs chain impl mockchain src vote manager rs chain impl mockchain vote manager voteplanmanager private tally start at c users dariusz cargo git checkouts chain libs chain impl mockchain src vote manager rs chain impl mockchain vote ledger impl apply encrypted vote tally closure at c users dariusz cargo git checkouts chain libs chain impl mockchain src vote ledger rs imhamt node reference update rec chain impl mockchain vote manager voteplanmanager closure chain impl mockchain vote manager at c users dariusz cargo git checkouts chain libs imhamt src node reference rs imhamt hamt hamt chain impl mockchain vote manager voteplanmanager update std colle at c users dariusz cargo git checkouts chain libs imhamt src hamt rs chain impl mockchain vote ledger voteplanledger apply encrypted vote tally at c users dariusz cargo git checkouts chain libs chain impl mockchain src vote ledger rs chain impl mockchain ledger ledger ledger apply encrypted vote tally at c users dariusz cargo git checkouts chain libs chain impl mockchain src ledger ledger rs chain impl mockchain ledger ledger ledger apply fragment at c users dariusz cargo git checkouts chain libs chain impl mockchain src ledger ledger rs jormungandr fragment selection impl select at c work iohk jormungandr jormungandr src fragment selection rs jormungandr fragment pool pool select at c work iohk jormungandr jormungandr src fragment pool rs jormungandr fragment process impl start closure at c work iohk jormungandr jormungandr src fragment process rs core future from generator impl poll at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library core src future mod rs jormungandr utils task impl spawn try future closure jormungandr fragment process error at c work iohk jormungandr jormungandr src utils task rs core future from generator impl poll at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library core src future mod rs tokio runtime task core impl poll closure alloc sync arc at c users dariusz cargo registry src github com tokio src runtime task core rs tokio loom std unsafe cell unsafecell with mut core task poll poll cor at c users dariusz cargo registry src github com tokio src loom std unsafe cell rs tokio runtime task core core alloc sync arc poll alloc sync arc tokio runtime thread pool at c users dariusz cargo registry src github com tokio src runtime task core rs tokio runtime task harness impl poll closure alloc sync arc at c users dariusz cargo registry src github com tokio src runtime task harness rs core ops function fnonce call once at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library core src ops function rs std panic impl call once alloc boxed box tokio runtime task error joinerror closure at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library std src panic rs std panicking try do call core task poll poll alloc boxed box tokio runtime task error joinerror at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library std src panicking rs std panicking try do catch tuple std panicking try alloc boxed box tokio runtime task error joinerror std panic assertunwindsafe at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library std src panicking rs std panic catch unwind core task poll poll alloc boxed box tokio runtime task error joinerror at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library std src panic rs tokio runtime task harness harness alloc sync arc poll alloc sync arc tokio runtime thread at c users dariusz cargo registry src github com tokio src runtime task harness rs tokio runtime task raw poll alloc sync arc at c users dariusz cargo registry src github com tokio src runtime task raw rs tokio runtime task raw rawtask poll at c users dariusz cargo registry src github com tokio src runtime task raw rs tokio runtime task notified run at c users dariusz cargo registry src github com tokio src runtime task mod rs tokio runtime thread pool worker impl run task closure at c users dariusz cargo registry src github com tokio src runtime thread pool worker rs tokio coop with budget closure tuple closure at c users dariusz cargo registry src github com tokio src coop rs std thread local localkey try with closure core result result tuple at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library std src thread local rs std thread local localkey with closure core result result tuple at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library std src thread local rs tokio coop with budget at c users dariusz cargo registry src github com tokio src coop rs tokio coop budget at c users dariusz cargo registry src github com tokio src coop rs tokio runtime thread pool worker context run task at c users dariusz cargo registry src github com tokio src runtime thread pool worker rs tokio runtime thread pool worker context run at c users dariusz cargo registry src github com tokio src runtime thread pool worker rs tokio runtime thread pool worker run closure at c users dariusz cargo registry src github com tokio src runtime thread pool worker rs tokio macros scoped tls scopedkey set at c users dariusz cargo registry src github com tokio src macros scoped tls rs tokio runtime thread pool worker run at c users dariusz cargo registry src github com tokio src runtime thread pool worker rs tokio runtime thread pool worker impl launch closure at c users dariusz cargo registry src github com tokio src runtime thread pool worker rs tokio runtime blocking task impl poll at c users dariusz cargo registry src github com tokio src runtime blocking task rs tokio runtime task core impl poll closure tokio runtime blocking schedule noopschedule at c users dariusz cargo registry src github com tokio src runtime task core rs tokio loom std unsafe cell unsafecell with mut core task poll po at c users dariusz cargo registry src github com tokio src loom std unsafe cell rs tokio runtime task core core tokio runtime blocking schedule noopschedule poll tokio runtime blocking schedule noopschedule at c users dariusz cargo registry src github com tokio src runtime task core rs tokio runtime task harness impl poll closure tokio runtime blocking schedule noopschedule at c users dariusz cargo registry src github com tokio src runtime task harness rs core ops function fnonce call once at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library core src ops function rs std panic impl call once tokio runtime task error joinerror closure at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library std src panic rs std panicking try do call core task poll poll tokio runtime task error joinerror at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library std src panicking rs tokio time driver entry impl drop std panicking try tokio runtime task error joinerror std panic assertunwindsafe at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library std src panicking rs std panic catch unwind core task poll poll tokio runtime task error joinerror at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library std src panic rs tokio runtime task harness harness tokio runtime blocking schedule noopschedule poll tokio runtime blocking schedule noopschedul at c users dariusz cargo registry src github com tokio src runtime task harness rs tokio runtime task raw poll tokio runtime blocking schedule noopschedule at c users dariusz cargo registry src github com tokio src runtime task raw rs tokio runtime task raw rawtask poll at c users dariusz cargo registry src github com tokio src runtime task raw rs tokio runtime task notified run at c users dariusz cargo registry src github com tokio src runtime task mod rs tokio runtime blocking pool inner run at c users dariusz cargo registry src github com tokio src runtime blocking pool rs tokio runtime blocking pool impl spawn thread closure closure at c users dariusz cargo registry src github com tokio src runtime blocking pool rs tokio runtime context enter at c users dariusz cargo registry src github com tokio src runtime context rs tokio runtime handle handle enter at c users dariusz cargo registry src github com tokio src runtime handle rs tokio runtime blocking pool impl spawn thread closure at c users dariusz cargo registry src github com tokio src runtime blocking pool rs std sys common backtrace rust begin short backtrace at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library std src sys common backtrace rs std thread impl spawn unchecked closure closure at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library std src thread mod rs std panic impl call once closure at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library std src panic rs std panicking try do call tuple at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library std src panicking rs tokio time driver entry impl drop std panicking try std panic assertunwindsafe at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library std src panicking rs std panic catch unwind tuple at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library std src panic rs std thread impl spawn unchecked closure at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library std src thread mod rs core ops function fnonce call once at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library core src ops function rs alloc boxed impl call once at rustc library alloc src boxed rs alloc boxed impl call once at rustc library alloc src boxed rs std sys windows thread impl new thread start at rustc library std src sys windows thread rs basethreadinitthunk rtluserthreadstart standard output standard error error when trying to perform an http request node internal error http status server error internal server error for url non zero status with message waiting s and trying again of a service has terminated with an error service panicked assertion failed left right left right standard output standard error error when trying to perform an http request communication with node failed in unexpected way error sending request for url error trying to connect tcp connect error no connection could be made because the target machine actively refused it os error error trying to connect tcp connect error no connection could be made because the target machine actively refused it os error tcp connect error no connection could be made because the target machine actively refused it os error no connection could be made because the target machine actively refused it os error thread jormungandr vit private jcli flow private vote panicked at unexpected failure code stderr error when trying to perform an http request communication with node failed in unexpected way error sending request for url error trying to connect tcp connect error no connection could be made because the target machine actively refused it os error error trying to connect tcp connect error no connection could be made because the target machine actively refused it os error tcp connect error no connection could be made because the target machine actively refused it os error no connection could be made because the target machine actively refused it os error command c work iohk jormungandr target debug jcli exe rest message logs host code stdout stderr error when trying to perform an http request communication with node failed in unexpected way error sending request for url error trying to connect tcp connect error no connection could be made because the target machine actively refused it os error error trying to connect tcp connect error no connection could be made because the target machine actively refused it os error tcp connect error no connection could be made because the target machine actively refused it os error no connection could be made because the target machine actively refused it os error c users dariusz cargo registry src github com assert cmd src assert rs stack backtrace std backtrace rs backtrace dbghelp trace at rustc library std src backtrace src backtrace dbghelp rs std backtrace rs backtrace trace unsynchronized at rustc library std src backtrace src backtrace mod rs std sys common backtrace print fmt at rustc library std src sys common backtrace rs std sys common backtrace print impl fmt at rustc library std src sys common backtrace rs core fmt write at rustc library core src fmt mod rs std io write write fmt at rustc library std src io mod rs std sys common backtrace print at rustc library std src sys common backtrace rs std sys common backtrace print at rustc library std src sys common backtrace rs std panicking default hook closure at rustc library std src panicking rs std panicking default hook at rustc library std src panicking rs std panicking rust panic with hook at rustc library std src panicking rs std panicking begin panic handler closure at rustc library std src panicking rs std sys common backtrace rust end short backtrace at rustc library std src sys common backtrace rs std panicking begin panic handler at rustc library std src panicking rs std panicking begin panic fmt at rustc library std src panicking rs assert cmd assert assert success at c users dariusz cargo registry src github com assert cmd src assert rs jormungandr integration tests common jcli api rest message message logs at c work iohk jormungandr testing jormungandr integration tests src common jcli api rest message rs jormungandr integration tests common jcli services fragment check impl wait until processed closure at c work iohk jormungandr testing jormungandr integration tests src common jcli services fragment check rs core result result map err at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library core src result rs jormungandr integration tests common jcli services fragment check fragmentcheck wait until processed at c work iohk jormungandr testing jormungandr integration tests src common jcli services fragment check rs jormungandr integration tests common jcli services fragment check fragmentcheck assert in block with wait at c work iohk jormungandr testing jormungandr integration tests src common jcli services fragment check rs jormungandr integration tests common jcli services fragment check fragmentcheck assert in block at c work iohk jormungandr testing jormungandr integration tests src common jcli services fragment check rs jormungandr integration tests jormungandr vit private jcli flow private vote at c work iohk jormungandr testing jormungandr integration tests src jormungandr vit private rs jormungandr integration tests jormungandr vit private jcli flow private vote closure at c work iohk jormungandr testing jormungandr integration tests src jormungandr vit private rs core ops function fnonce call once at c users dariusz rustup toolchains beta pc windows msvc lib rustlib src rust library core src ops function rs core ops function fnonce call once at rustc library core src ops function rs test rust begin short backtrace at rustc library test src lib rs alloc boxed impl call once at rustc library alloc src boxed rs std panic impl call once at rustc library std src panic rs std panicking try do call at rustc library std src panicking rs std panicking try at rustc library std src panicking rs std panic catch unwind at rustc library std src panic rs test run test in process at rustc library test src lib rs test run test run test inner closure at rustc library test src lib rs std sys common backtrace rust begin short backtrace at rustc library std src sys common backtrace rs std sys common backtrace rust begin short backtrace at rustc library std src sys common backtrace rs std thread impl spawn unchecked closure closure at rustc library std src thread mod rs std panic impl call once at rustc library std src panic rs std panicking try do call at rustc library std src panicking rs std panicking try at rustc library std src panicking rs std panic catch unwind at rustc library std src panic rs std thread impl spawn unchecked closure at rustc library std src thread mod rs core ops function fnonce call once at rustc library core src ops function rs alloc boxed impl call once at rustc library alloc src boxed rs alloc boxed impl call once at rustc library alloc src boxed rs std sys windows thread impl new thread start at rustc library std src sys windows thread rs basethreadinitthunk rtluserthreadstart error lines msg servicefinishedwitherror level erro ts task leadership reason fragmentselectionfailed msg servicehasterminatedwithanerror level crit ts reason servicepanicked assertionfailed left right nleft nright test jormungandr vit private jcli flow private vote failed failures failures jormungandr vit private jcli flow private vote mandatory information jcli full version newest master jormungandr full version newest master to reproduce steps to reproduce the behavior checkout branch private vote run test jormungandr vit private jcli flow private vote | 0 |
257,190 | 27,561,799,926 | IssuesEvent | 2023-03-07 22:47:09 | samqws-marketing/box_box-ui-elements | https://api.github.com/repos/samqws-marketing/box_box-ui-elements | closed | CVE-2020-7608 (Medium) detected in multiple libraries - autoclosed | security vulnerability | ## CVE-2020-7608 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>yargs-parser-5.0.0.tgz</b>, <b>yargs-parser-7.0.0.tgz</b>, <b>yargs-parser-11.1.1.tgz</b>, <b>yargs-parser-16.1.0.tgz</b>, <b>yargs-parser-13.1.1.tgz</b>, <b>yargs-parser-10.1.0.tgz</b>, <b>yargs-parser-9.0.2.tgz</b>, <b>yargs-parser-4.2.1.tgz</b></p></summary>
<p>
<details><summary><b>yargs-parser-5.0.0.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-5.0.0.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-5.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- node-sass-4.13.1.tgz (Root Library)
- sass-graph-2.2.4.tgz
- yargs-7.1.0.tgz
- :x: **yargs-parser-5.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-7.0.0.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-7.0.0.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-7.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- nsp-3.2.1.tgz (Root Library)
- yargs-9.0.1.tgz
- :x: **yargs-parser-7.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-11.1.1.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-11.1.1.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-11.1.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- flow-typed-2.6.2.tgz (Root Library)
- yargs-12.0.5.tgz
- :x: **yargs-parser-11.1.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-16.1.0.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-16.1.0.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-16.1.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- flow-copy-source-2.0.9.tgz (Root Library)
- yargs-15.0.2.tgz
- :x: **yargs-parser-16.1.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-13.1.1.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-13.1.1.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-13.1.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- prettier-eslint-cli-5.0.0.tgz (Root Library)
- yargs-13.3.0.tgz
- :x: **yargs-parser-13.1.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-10.1.0.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-10.1.0.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-10.1.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- conventional-changelog-cli-2.0.31.tgz (Root Library)
- meow-5.0.0.tgz
- :x: **yargs-parser-10.1.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-9.0.2.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-9.0.2.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-9.0.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- semantic-release-16.0.2.tgz (Root Library)
- npm-6.0.0.tgz
- npm-6.13.1.tgz
- libnpx-10.2.0.tgz
- yargs-11.0.0.tgz
- :x: **yargs-parser-9.0.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-4.2.1.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-4.2.1.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-4.2.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- addon-actions-5.3.9.tgz (Root Library)
- react-inspector-4.0.0.tgz
- storybook-chromatic-2.2.2.tgz
- localtunnel-1.10.1.tgz
- yargs-6.6.0.tgz
- :x: **yargs-parser-4.2.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/samqws-marketing/box_box-ui-elements/commit/4fc776e2b95c8b497f6994cb2165365562ae1f82">4fc776e2b95c8b497f6994cb2165365562ae1f82</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
yargs-parser could be tricked into adding or modifying properties of Object.prototype using a "__proto__" payload.
<p>Publish Date: 2020-03-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-7608>CVE-2020-7608</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2020-03-16</p>
<p>Fix Resolution (yargs-parser): 5.0.1</p>
<p>Direct dependency fix Resolution (node-sass): 4.14.0</p><p>Fix Resolution (yargs-parser): 13.1.2</p>
<p>Direct dependency fix Resolution (flow-typed): 3.0.0</p><p>Fix Resolution (yargs-parser): 13.1.2</p>
<p>Direct dependency fix Resolution (prettier-eslint-cli): 5.0.1</p><p>Fix Resolution (yargs-parser): 13.1.2</p>
<p>Direct dependency fix Resolution (conventional-changelog-cli): 2.0.33</p><p>Fix Resolution (yargs-parser): 13.1.2</p>
<p>Direct dependency fix Resolution (semantic-release): 16.0.3</p><p>Fix Resolution (yargs-parser): 5.0.0-security.0</p>
<p>Direct dependency fix Resolution (@storybook/addon-actions): 5.3.10</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| True | CVE-2020-7608 (Medium) detected in multiple libraries - autoclosed - ## CVE-2020-7608 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>yargs-parser-5.0.0.tgz</b>, <b>yargs-parser-7.0.0.tgz</b>, <b>yargs-parser-11.1.1.tgz</b>, <b>yargs-parser-16.1.0.tgz</b>, <b>yargs-parser-13.1.1.tgz</b>, <b>yargs-parser-10.1.0.tgz</b>, <b>yargs-parser-9.0.2.tgz</b>, <b>yargs-parser-4.2.1.tgz</b></p></summary>
<p>
<details><summary><b>yargs-parser-5.0.0.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-5.0.0.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-5.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- node-sass-4.13.1.tgz (Root Library)
- sass-graph-2.2.4.tgz
- yargs-7.1.0.tgz
- :x: **yargs-parser-5.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-7.0.0.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-7.0.0.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-7.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- nsp-3.2.1.tgz (Root Library)
- yargs-9.0.1.tgz
- :x: **yargs-parser-7.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-11.1.1.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-11.1.1.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-11.1.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- flow-typed-2.6.2.tgz (Root Library)
- yargs-12.0.5.tgz
- :x: **yargs-parser-11.1.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-16.1.0.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-16.1.0.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-16.1.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- flow-copy-source-2.0.9.tgz (Root Library)
- yargs-15.0.2.tgz
- :x: **yargs-parser-16.1.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-13.1.1.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-13.1.1.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-13.1.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- prettier-eslint-cli-5.0.0.tgz (Root Library)
- yargs-13.3.0.tgz
- :x: **yargs-parser-13.1.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-10.1.0.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-10.1.0.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-10.1.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- conventional-changelog-cli-2.0.31.tgz (Root Library)
- meow-5.0.0.tgz
- :x: **yargs-parser-10.1.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-9.0.2.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-9.0.2.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-9.0.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- semantic-release-16.0.2.tgz (Root Library)
- npm-6.0.0.tgz
- npm-6.13.1.tgz
- libnpx-10.2.0.tgz
- yargs-11.0.0.tgz
- :x: **yargs-parser-9.0.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-4.2.1.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-4.2.1.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-4.2.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- addon-actions-5.3.9.tgz (Root Library)
- react-inspector-4.0.0.tgz
- storybook-chromatic-2.2.2.tgz
- localtunnel-1.10.1.tgz
- yargs-6.6.0.tgz
- :x: **yargs-parser-4.2.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/samqws-marketing/box_box-ui-elements/commit/4fc776e2b95c8b497f6994cb2165365562ae1f82">4fc776e2b95c8b497f6994cb2165365562ae1f82</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
yargs-parser could be tricked into adding or modifying properties of Object.prototype using a "__proto__" payload.
<p>Publish Date: 2020-03-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-7608>CVE-2020-7608</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2020-03-16</p>
<p>Fix Resolution (yargs-parser): 5.0.1</p>
<p>Direct dependency fix Resolution (node-sass): 4.14.0</p><p>Fix Resolution (yargs-parser): 13.1.2</p>
<p>Direct dependency fix Resolution (flow-typed): 3.0.0</p><p>Fix Resolution (yargs-parser): 13.1.2</p>
<p>Direct dependency fix Resolution (prettier-eslint-cli): 5.0.1</p><p>Fix Resolution (yargs-parser): 13.1.2</p>
<p>Direct dependency fix Resolution (conventional-changelog-cli): 2.0.33</p><p>Fix Resolution (yargs-parser): 13.1.2</p>
<p>Direct dependency fix Resolution (semantic-release): 16.0.3</p><p>Fix Resolution (yargs-parser): 5.0.0-security.0</p>
<p>Direct dependency fix Resolution (@storybook/addon-actions): 5.3.10</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| non_priority | cve medium detected in multiple libraries autoclosed cve medium severity vulnerability vulnerable libraries yargs parser tgz yargs parser tgz yargs parser tgz yargs parser tgz yargs parser tgz yargs parser tgz yargs parser tgz yargs parser tgz yargs parser tgz the mighty option parser used by yargs library home page a href path to dependency file package json path to vulnerable library node modules yargs parser package json dependency hierarchy node sass tgz root library sass graph tgz yargs tgz x yargs parser tgz vulnerable library yargs parser tgz the mighty option parser used by yargs library home page a href path to dependency file package json path to vulnerable library node modules yargs parser package json dependency hierarchy nsp tgz root library yargs tgz x yargs parser tgz vulnerable library yargs parser tgz the mighty option parser used by yargs library home page a href path to dependency file package json path to vulnerable library node modules yargs parser package json dependency hierarchy flow typed tgz root library yargs tgz x yargs parser tgz vulnerable library yargs parser tgz the mighty option parser used by yargs library home page a href path to dependency file package json path to vulnerable library node modules yargs parser package json dependency hierarchy flow copy source tgz root library yargs tgz x yargs parser tgz vulnerable library yargs parser tgz the mighty option parser used by yargs library home page a href path to dependency file package json path to vulnerable library node modules yargs parser package json dependency hierarchy prettier eslint cli tgz root library yargs tgz x yargs parser tgz vulnerable library yargs parser tgz the mighty option parser used by yargs library home page a href path to dependency file package json path to vulnerable library node modules yargs parser package json dependency hierarchy conventional changelog cli tgz root library meow tgz x yargs parser tgz vulnerable library yargs parser tgz the mighty option parser used by yargs library home page a href path to dependency file package json path to vulnerable library node modules yargs parser package json dependency hierarchy semantic release tgz root library npm tgz npm tgz libnpx tgz yargs tgz x yargs parser tgz vulnerable library yargs parser tgz the mighty option parser used by yargs library home page a href path to dependency file package json path to vulnerable library node modules yargs parser package json dependency hierarchy addon actions tgz root library react inspector tgz storybook chromatic tgz localtunnel tgz yargs tgz x yargs parser tgz vulnerable library found in head commit a href found in base branch master vulnerability details yargs parser could be tricked into adding or modifying properties of object prototype using a proto payload publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version release date fix resolution yargs parser direct dependency fix resolution node sass fix resolution yargs parser direct dependency fix resolution flow typed fix resolution yargs parser direct dependency fix resolution prettier eslint cli fix resolution yargs parser direct dependency fix resolution conventional changelog cli fix resolution yargs parser direct dependency fix resolution semantic release fix resolution yargs parser security direct dependency fix resolution storybook addon actions check this box to open an automated fix pr | 0 |
11,961 | 7,570,496,372 | IssuesEvent | 2018-04-23 09:11:21 | OpenKnowledgeMaps/Headstart | https://api.github.com/repos/OpenKnowledgeMaps/Headstart | closed | Change cursor to indicate possibility to zoom in or out of bubble | frontend usability | At the moment the cursor doesn't change its appearance to indicate that you can zoom in or out of one bubble. The problem is that some users don't understand how to zoom in or out of a bubble.
Suggestion:
**1. Zoom in**
When map is zoomed out and the user hovers over bubble, change cursor to `cursor: zoom-in;`
**2. Zoom out**
When the map is zoomed in and the user hovers over (only) white areas outside of bubble (within map area), change cursor to `cursor: zoom-out;`
| True | Change cursor to indicate possibility to zoom in or out of bubble - At the moment the cursor doesn't change its appearance to indicate that you can zoom in or out of one bubble. The problem is that some users don't understand how to zoom in or out of a bubble.
Suggestion:
**1. Zoom in**
When map is zoomed out and the user hovers over bubble, change cursor to `cursor: zoom-in;`
**2. Zoom out**
When the map is zoomed in and the user hovers over (only) white areas outside of bubble (within map area), change cursor to `cursor: zoom-out;`
| non_priority | change cursor to indicate possibility to zoom in or out of bubble at the moment the cursor doesn t change its appearance to indicate that you can zoom in or out of one bubble the problem is that some users don t understand how to zoom in or out of a bubble suggestion zoom in when map is zoomed out and the user hovers over bubble change cursor to cursor zoom in zoom out when the map is zoomed in and the user hovers over only white areas outside of bubble within map area change cursor to cursor zoom out | 0 |
123,389 | 17,772,222,884 | IssuesEvent | 2021-08-30 14:52:13 | kapseliboi/json-editor | https://api.github.com/repos/kapseliboi/json-editor | opened | CVE-2021-27292 (High) detected in ua-parser-js-0.7.22.tgz | security vulnerability | ## CVE-2021-27292 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ua-parser-js-0.7.22.tgz</b></p></summary>
<p>Lightweight JavaScript-based user-agent string parser</p>
<p>Library home page: <a href="https://registry.npmjs.org/ua-parser-js/-/ua-parser-js-0.7.22.tgz">https://registry.npmjs.org/ua-parser-js/-/ua-parser-js-0.7.22.tgz</a></p>
<p>Path to dependency file: json-editor/package.json</p>
<p>Path to vulnerable library: json-editor/node_modules/ua-parser-js/package.json</p>
<p>
Dependency Hierarchy:
- karma-5.2.3.tgz (Root Library)
- :x: **ua-parser-js-0.7.22.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kapseliboi/json-editor/commit/9e026ded311421b7261c6a277c7f98ec94d8b1aa">9e026ded311421b7261c6a277c7f98ec94d8b1aa</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>
ua-parser-js >= 0.7.14, fixed in 0.7.24, uses a regular expression which is vulnerable to denial of service. If an attacker sends a malicious User-Agent header, ua-parser-js will get stuck processing it for an extended period of time.
<p>Publish Date: 2021-03-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-27292>CVE-2021-27292</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/faisalman/ua-parser-js/releases/tag/0.7.24">https://github.com/faisalman/ua-parser-js/releases/tag/0.7.24</a></p>
<p>Release Date: 2021-03-17</p>
<p>Fix Resolution: ua-parser-js - 0.7.24</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-27292 (High) detected in ua-parser-js-0.7.22.tgz - ## CVE-2021-27292 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ua-parser-js-0.7.22.tgz</b></p></summary>
<p>Lightweight JavaScript-based user-agent string parser</p>
<p>Library home page: <a href="https://registry.npmjs.org/ua-parser-js/-/ua-parser-js-0.7.22.tgz">https://registry.npmjs.org/ua-parser-js/-/ua-parser-js-0.7.22.tgz</a></p>
<p>Path to dependency file: json-editor/package.json</p>
<p>Path to vulnerable library: json-editor/node_modules/ua-parser-js/package.json</p>
<p>
Dependency Hierarchy:
- karma-5.2.3.tgz (Root Library)
- :x: **ua-parser-js-0.7.22.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kapseliboi/json-editor/commit/9e026ded311421b7261c6a277c7f98ec94d8b1aa">9e026ded311421b7261c6a277c7f98ec94d8b1aa</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>
ua-parser-js >= 0.7.14, fixed in 0.7.24, uses a regular expression which is vulnerable to denial of service. If an attacker sends a malicious User-Agent header, ua-parser-js will get stuck processing it for an extended period of time.
<p>Publish Date: 2021-03-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-27292>CVE-2021-27292</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/faisalman/ua-parser-js/releases/tag/0.7.24">https://github.com/faisalman/ua-parser-js/releases/tag/0.7.24</a></p>
<p>Release Date: 2021-03-17</p>
<p>Fix Resolution: ua-parser-js - 0.7.24</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in ua parser js tgz cve high severity vulnerability vulnerable library ua parser js tgz lightweight javascript based user agent string parser library home page a href path to dependency file json editor package json path to vulnerable library json editor node modules ua parser js package json dependency hierarchy karma tgz root library x ua parser js tgz vulnerable library found in head commit a href found in base branch master vulnerability details ua parser js fixed in uses a regular expression which is vulnerable to denial of service if an attacker sends a malicious user agent header ua parser js will get stuck processing it for an extended period of time publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution ua parser js step up your open source security game with whitesource | 0 |
185,549 | 14,360,074,808 | IssuesEvent | 2020-11-30 16:23:51 | hashgraph/hedera-services | https://api.github.com/repos/hashgraph/hedera-services | closed | In v0.9.0-rc4 branch's 6-node JRS perf regression, errors for "Could not download '0.0.112' | Test Development bug | **Summary of the defect**
HAPIClientValidation failed with "Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE" and other error messages.
**How to reproduce (if possible)**
Refer the slack report link: https://hedera-hashgraph.slack.com/archives/CKWHL8R9A/p1605671530308400
and follow up with its detailed test log files.
**Service logs (if applicable)**
```
---- HAPIClientValidator FAILED validation ----
<<ERROR>>
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PAYER_ACCOUNT_NOT_FOUND
ClientNode - Suite Result Failures
Node 0 - CryptoCreateForSuiteRunner FAILED CreatePayerAccountForEachClient
Exceptions:1
Node 0 - SubmitMessageLoadTest FAILED RunSubmitMessages
Exceptions:1
Node 1 - CryptoCreateForSuiteRunner FAILED CreatePayerAccountForEachClient
Exceptions:1
Node 1 - SubmitMessageLoadTest FAILED RunSubmitMessages
Exceptions:1
Node 2 - CryptoCreateForSuiteRunner FAILED CreatePayerAccountForEachClient
Exceptions:1
Node 2 - SubmitMessageLoadTest FAILED RunSubmitMessages
Exceptions:1
Node 3 - CryptoCreateForSuiteRunner FAILED CreatePayerAccountForEachClient
Exceptions:1
Node 3 - SubmitMessageLoadTest FAILED RunSubmitMessages
Exceptions:1
Node 4 - CryptoCreateForSuiteRunner FAILED CreatePayerAccountForEachClient
Exceptions:1
Node 4 - SubmitMessageLoadTest FAILED RunSubmitMessages
Exceptions:1
Node 5 - CryptoCreateForSuiteRunner FAILED CreatePayerAccountForEachClient
Node 5 - SubmitMessageLoadTest FAILED RunSubmitMessages
Exceptions:1
...
```
**Environment:**
- OS: [e.g. Ubuntu 18.04]
- Java: [e.g. OpenJDK 11.0.4]
- Hedera Services Version: [e.g. 0.0.5]
- HAPI Version: [e.g. 0.0.5]
**Additional Context**
Add any other context about the problem here. Attach any logs here, if applicable.
| 1.0 | In v0.9.0-rc4 branch's 6-node JRS perf regression, errors for "Could not download '0.0.112' - **Summary of the defect**
HAPIClientValidation failed with "Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE" and other error messages.
**How to reproduce (if possible)**
Refer the slack report link: https://hedera-hashgraph.slack.com/archives/CKWHL8R9A/p1605671530308400
and follow up with its detailed test log files.
**Service logs (if applicable)**
```
---- HAPIClientValidator FAILED validation ----
<<ERROR>>
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PLATFORM_NOT_ACTIVE
java.lang.IllegalStateException: Could not download '0.0.112' final status PAYER_ACCOUNT_NOT_FOUND
ClientNode - Suite Result Failures
Node 0 - CryptoCreateForSuiteRunner FAILED CreatePayerAccountForEachClient
Exceptions:1
Node 0 - SubmitMessageLoadTest FAILED RunSubmitMessages
Exceptions:1
Node 1 - CryptoCreateForSuiteRunner FAILED CreatePayerAccountForEachClient
Exceptions:1
Node 1 - SubmitMessageLoadTest FAILED RunSubmitMessages
Exceptions:1
Node 2 - CryptoCreateForSuiteRunner FAILED CreatePayerAccountForEachClient
Exceptions:1
Node 2 - SubmitMessageLoadTest FAILED RunSubmitMessages
Exceptions:1
Node 3 - CryptoCreateForSuiteRunner FAILED CreatePayerAccountForEachClient
Exceptions:1
Node 3 - SubmitMessageLoadTest FAILED RunSubmitMessages
Exceptions:1
Node 4 - CryptoCreateForSuiteRunner FAILED CreatePayerAccountForEachClient
Exceptions:1
Node 4 - SubmitMessageLoadTest FAILED RunSubmitMessages
Exceptions:1
Node 5 - CryptoCreateForSuiteRunner FAILED CreatePayerAccountForEachClient
Node 5 - SubmitMessageLoadTest FAILED RunSubmitMessages
Exceptions:1
...
```
**Environment:**
- OS: [e.g. Ubuntu 18.04]
- Java: [e.g. OpenJDK 11.0.4]
- Hedera Services Version: [e.g. 0.0.5]
- HAPI Version: [e.g. 0.0.5]
**Additional Context**
Add any other context about the problem here. Attach any logs here, if applicable.
| non_priority | in branch s node jrs perf regression errors for could not download summary of the defect hapiclientvalidation failed with could not download final status platform not active and other error messages how to reproduce if possible refer the slack report link and follow up with its detailed test log files service logs if applicable hapiclientvalidator failed validation java lang illegalstateexception could not download final status platform not active java lang illegalstateexception could not download final status platform not active java lang illegalstateexception could not download final status platform not active java lang illegalstateexception could not download final status platform not active java lang illegalstateexception could not download final status platform not active java lang illegalstateexception could not download final status platform not active java lang illegalstateexception could not download final status platform not active java lang illegalstateexception could not download final status platform not active java lang illegalstateexception could not download final status platform not active java lang illegalstateexception could not download final status platform not active java lang illegalstateexception could not download final status payer account not found clientnode suite result failures node cryptocreateforsuiterunner failed createpayeraccountforeachclient exceptions node submitmessageloadtest failed runsubmitmessages exceptions node cryptocreateforsuiterunner failed createpayeraccountforeachclient exceptions node submitmessageloadtest failed runsubmitmessages exceptions node cryptocreateforsuiterunner failed createpayeraccountforeachclient exceptions node submitmessageloadtest failed runsubmitmessages exceptions node cryptocreateforsuiterunner failed createpayeraccountforeachclient exceptions node submitmessageloadtest failed runsubmitmessages exceptions node cryptocreateforsuiterunner failed createpayeraccountforeachclient exceptions node submitmessageloadtest failed runsubmitmessages exceptions node cryptocreateforsuiterunner failed createpayeraccountforeachclient node submitmessageloadtest failed runsubmitmessages exceptions environment os java hedera services version hapi version additional context add any other context about the problem here attach any logs here if applicable | 0 |
262,621 | 27,979,916,811 | IssuesEvent | 2023-03-26 02:21:41 | MatBenfield/news | https://api.github.com/repos/MatBenfield/news | closed | [SecurityWeek] US Charges 20-Year-Old Head of Hacker Site BreachForums | SecurityWeek Stale |
The US Justice Department charged Conor Brian Fitzpatrick, founder of BreachForums, a major underground website for computer hackers.
The post [US Charges 20-Year-Old Head of Hacker Site BreachForums](https://www.securityweek.com/us-charges-20-year-old-head-of-hacker-site-breachforums/) appeared first on [SecurityWeek](https://www.securityweek.com).
<https://www.securityweek.com/us-charges-20-year-old-head-of-hacker-site-breachforums/>
| True | [SecurityWeek] US Charges 20-Year-Old Head of Hacker Site BreachForums -
The US Justice Department charged Conor Brian Fitzpatrick, founder of BreachForums, a major underground website for computer hackers.
The post [US Charges 20-Year-Old Head of Hacker Site BreachForums](https://www.securityweek.com/us-charges-20-year-old-head-of-hacker-site-breachforums/) appeared first on [SecurityWeek](https://www.securityweek.com).
<https://www.securityweek.com/us-charges-20-year-old-head-of-hacker-site-breachforums/>
| non_priority | us charges year old head of hacker site breachforums the us justice department charged conor brian fitzpatrick founder of breachforums a major underground website for computer hackers the post appeared first on | 0 |
123,965 | 12,222,925,450 | IssuesEvent | 2020-05-02 15:23:35 | anitab-org/mentorship-backend | https://api.github.com/repos/anitab-org/mentorship-backend | closed | Create guide on how to test PRs and backend with Swagger UI | Category: Documentation/Training Type: Maintenance | ## Description
As a contributor for testing,
I need a guide to help me understand how Swagger UI works and how to use multiple APIs from the project,
so that I can properly test pull requests from contributors that solve issues for the project.
Idea is to create a Markdown-based guide on the repository to help guide testers. [Conversation started here on Zulip](https://anitab-org.zulipchat.com/#narrow/stream/216325-quality-assurance/topic/PR.20that.20needs.20Testing/near/194472739).
_this has already an assignee_
## Acceptance Criteria
### Update [Required]
- [ ] Create guide on docs folder
## Definition of Done
- [ ] All of the required items are completed.
- [x] Approval by 1 mentor.
## Estimation
2 hours | 1.0 | Create guide on how to test PRs and backend with Swagger UI - ## Description
As a contributor for testing,
I need a guide to help me understand how Swagger UI works and how to use multiple APIs from the project,
so that I can properly test pull requests from contributors that solve issues for the project.
Idea is to create a Markdown-based guide on the repository to help guide testers. [Conversation started here on Zulip](https://anitab-org.zulipchat.com/#narrow/stream/216325-quality-assurance/topic/PR.20that.20needs.20Testing/near/194472739).
_this has already an assignee_
## Acceptance Criteria
### Update [Required]
- [ ] Create guide on docs folder
## Definition of Done
- [ ] All of the required items are completed.
- [x] Approval by 1 mentor.
## Estimation
2 hours | non_priority | create guide on how to test prs and backend with swagger ui description as a contributor for testing i need a guide to help me understand how swagger ui works and how to use multiple apis from the project so that i can properly test pull requests from contributors that solve issues for the project idea is to create a markdown based guide on the repository to help guide testers this has already an assignee acceptance criteria update create guide on docs folder definition of done all of the required items are completed approval by mentor estimation hours | 0 |
14,325 | 3,391,574,676 | IssuesEvent | 2015-11-30 16:02:46 | 18F/doi-extractives-data | https://api.github.com/repos/18F/doi-extractives-data | closed | Visual bug: global nav isn't centered on desktop | workflow:testing | It was centered, and then I merged the mobile view PR too quickly, and didn't notice that we had a regression. Booooo. Looks like the following, with USEITI all the way to the left:
<img width="1218" alt="screenshot 2015-11-29 20 21 53" src="https://cloud.githubusercontent.com/assets/4827522/11465408/b1d054a6-96f5-11e5-9a43-56909ec08413.png">
It should be centered still, with right and left edges lining up with content below.
| 1.0 | Visual bug: global nav isn't centered on desktop - It was centered, and then I merged the mobile view PR too quickly, and didn't notice that we had a regression. Booooo. Looks like the following, with USEITI all the way to the left:
<img width="1218" alt="screenshot 2015-11-29 20 21 53" src="https://cloud.githubusercontent.com/assets/4827522/11465408/b1d054a6-96f5-11e5-9a43-56909ec08413.png">
It should be centered still, with right and left edges lining up with content below.
| non_priority | visual bug global nav isn t centered on desktop it was centered and then i merged the mobile view pr too quickly and didn t notice that we had a regression booooo looks like the following with useiti all the way to the left img width alt screenshot src it should be centered still with right and left edges lining up with content below | 0 |
43,931 | 11,349,478,105 | IssuesEvent | 2020-01-24 05:07:25 | quiverteam/Engine | https://api.github.com/repos/quiverteam/Engine | closed | filesystem_stdio doesn't link on Linux | Posix build system | ```
[ 6%] Linking CXX shared library libfilesystem_stdio.so
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/QueuedLoader.cpp.o: in function `AdjustAsyncIOSpeed()':
/home/ridvan/source/Engine/src/filesystem/QueuedLoader.cpp:404: undefined reference to `g_pFullFileSystem'
/usr/bin/ld: /home/ridvan/source/Engine/src/filesystem/QueuedLoader.cpp:404: undefined reference to `g_pFullFileSystem'
/usr/bin/ld: /home/ridvan/source/Engine/src/filesystem/QueuedLoader.cpp:419: undefined reference to `g_pFullFileSystem'
/usr/bin/ld: /home/ridvan/source/Engine/src/filesystem/QueuedLoader.cpp:419: undefined reference to `g_pFullFileSystem'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/QueuedLoader.cpp.o: in function `IOComputationJob(FileJob_t*, void*, int, LoaderError_t)':
/home/ridvan/source/Engine/src/filesystem/QueuedLoader.cpp:474: undefined reference to `g_pFullFileSystem'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/QueuedLoader.cpp.o:/home/ridvan/source/Engine/src/filesystem/QueuedLoader.cpp:474: more undefined references to `g_pFullFileSystem' follow
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/QueuedLoader.cpp.o: in function `CTier2AppSystem<IQueuedLoader, 0>::Connect(void* (*)(char const*, int*))':
/home/ridvan/source/Engine/src/public/tier2/tier2.h:94: undefined reference to `ConnectTier2Libraries(void* (**)(char const*, int*), int)'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/QueuedLoader.cpp.o: in function `CTier2AppSystem<IQueuedLoader, 0>::Disconnect()':
/home/ridvan/source/Engine/src/public/tier2/tier2.h:118: undefined reference to `DisconnectTier2Libraries()'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/basefilesystem.cpp.o: in function `CBaseFileSystem::CBaseFileSystem()':
/home/ridvan/source/Engine/src/filesystem/basefilesystem.cpp:269: undefined reference to `g_pFullFileSystem'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/basefilesystem.cpp.o: in function `CBaseFileSystem::LoadKeyValues(KeyValues&, IFileSystem::KeyValuesPreloadType_t, char const*, char const*)':
/home/ridvan/source/Engine/src/filesystem/basefilesystem.cpp:3547: undefined reference to `CCompiledKeyValuesReader::InstanceInPlace(KeyValues&, char const*)'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/basefilesystem.cpp.o: in function `CBaseFileSystem::LoadKeyValues(IFileSystem::KeyValuesPreloadType_t, char const*, char const*)':
/home/ridvan/source/Engine/src/filesystem/basefilesystem.cpp:3584: undefined reference to `CCompiledKeyValuesReader::Instance(char const*)'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/basefilesystem.cpp.o: in function `CBaseFileSystem::ExtractRootKeyName(IFileSystem::KeyValuesPreloadType_t, char*, unsigned int, char const*, char const*)':
/home/ridvan/source/Engine/src/filesystem/basefilesystem.cpp:3677: undefined reference to `CCompiledKeyValuesReader::LookupKeyValuesRootKeyName(char const*, char*, unsigned int)'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/basefilesystem.cpp.o: in function `CBaseFileSystem::SetupPreloadData()':
/home/ridvan/source/Engine/src/filesystem/basefilesystem.cpp:3717: undefined reference to `CCompiledKeyValuesReader::CCompiledKeyValuesReader()'
/usr/bin/ld: /home/ridvan/source/Engine/src/filesystem/basefilesystem.cpp:3718: undefined reference to `CCompiledKeyValuesReader::LoadFile(char const*)'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/basefilesystem.cpp.o: in function `void CByteswap::SwapFieldsToTargetEndian<ZIP_EndOfCentralDirRecord>(ZIP_EndOfCentralDirRecord*, void*, unsigned int)':
/home/ridvan/source/Engine/src/public/tier1/byteswap.h:39: undefined reference to `ZIP_EndOfCentralDirRecord::m_DataMap'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/basefilesystem.cpp.o: in function `void CByteswap::SwapFieldsToTargetEndian<ZIP_FileHeader>(ZIP_FileHeader*, void*, unsigned int)':
/home/ridvan/source/Engine/src/public/tier1/byteswap.h:39: undefined reference to `ZIP_FileHeader::m_DataMap'
collect2: error: ld returned 1 exit status
make[2]: *** [filesystem/CMakeFiles/filesystem_stdio.dir/build.make:185: filesystem/libfilesystem_stdio.so] Error 1
make[1]: *** [CMakeFiles/Makefile2:479: filesystem/CMakeFiles/filesystem_stdio.dir/all] Error 2
make: *** [Makefile:84: all] Error 2
``` | 1.0 | filesystem_stdio doesn't link on Linux - ```
[ 6%] Linking CXX shared library libfilesystem_stdio.so
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/QueuedLoader.cpp.o: in function `AdjustAsyncIOSpeed()':
/home/ridvan/source/Engine/src/filesystem/QueuedLoader.cpp:404: undefined reference to `g_pFullFileSystem'
/usr/bin/ld: /home/ridvan/source/Engine/src/filesystem/QueuedLoader.cpp:404: undefined reference to `g_pFullFileSystem'
/usr/bin/ld: /home/ridvan/source/Engine/src/filesystem/QueuedLoader.cpp:419: undefined reference to `g_pFullFileSystem'
/usr/bin/ld: /home/ridvan/source/Engine/src/filesystem/QueuedLoader.cpp:419: undefined reference to `g_pFullFileSystem'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/QueuedLoader.cpp.o: in function `IOComputationJob(FileJob_t*, void*, int, LoaderError_t)':
/home/ridvan/source/Engine/src/filesystem/QueuedLoader.cpp:474: undefined reference to `g_pFullFileSystem'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/QueuedLoader.cpp.o:/home/ridvan/source/Engine/src/filesystem/QueuedLoader.cpp:474: more undefined references to `g_pFullFileSystem' follow
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/QueuedLoader.cpp.o: in function `CTier2AppSystem<IQueuedLoader, 0>::Connect(void* (*)(char const*, int*))':
/home/ridvan/source/Engine/src/public/tier2/tier2.h:94: undefined reference to `ConnectTier2Libraries(void* (**)(char const*, int*), int)'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/QueuedLoader.cpp.o: in function `CTier2AppSystem<IQueuedLoader, 0>::Disconnect()':
/home/ridvan/source/Engine/src/public/tier2/tier2.h:118: undefined reference to `DisconnectTier2Libraries()'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/basefilesystem.cpp.o: in function `CBaseFileSystem::CBaseFileSystem()':
/home/ridvan/source/Engine/src/filesystem/basefilesystem.cpp:269: undefined reference to `g_pFullFileSystem'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/basefilesystem.cpp.o: in function `CBaseFileSystem::LoadKeyValues(KeyValues&, IFileSystem::KeyValuesPreloadType_t, char const*, char const*)':
/home/ridvan/source/Engine/src/filesystem/basefilesystem.cpp:3547: undefined reference to `CCompiledKeyValuesReader::InstanceInPlace(KeyValues&, char const*)'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/basefilesystem.cpp.o: in function `CBaseFileSystem::LoadKeyValues(IFileSystem::KeyValuesPreloadType_t, char const*, char const*)':
/home/ridvan/source/Engine/src/filesystem/basefilesystem.cpp:3584: undefined reference to `CCompiledKeyValuesReader::Instance(char const*)'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/basefilesystem.cpp.o: in function `CBaseFileSystem::ExtractRootKeyName(IFileSystem::KeyValuesPreloadType_t, char*, unsigned int, char const*, char const*)':
/home/ridvan/source/Engine/src/filesystem/basefilesystem.cpp:3677: undefined reference to `CCompiledKeyValuesReader::LookupKeyValuesRootKeyName(char const*, char*, unsigned int)'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/basefilesystem.cpp.o: in function `CBaseFileSystem::SetupPreloadData()':
/home/ridvan/source/Engine/src/filesystem/basefilesystem.cpp:3717: undefined reference to `CCompiledKeyValuesReader::CCompiledKeyValuesReader()'
/usr/bin/ld: /home/ridvan/source/Engine/src/filesystem/basefilesystem.cpp:3718: undefined reference to `CCompiledKeyValuesReader::LoadFile(char const*)'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/basefilesystem.cpp.o: in function `void CByteswap::SwapFieldsToTargetEndian<ZIP_EndOfCentralDirRecord>(ZIP_EndOfCentralDirRecord*, void*, unsigned int)':
/home/ridvan/source/Engine/src/public/tier1/byteswap.h:39: undefined reference to `ZIP_EndOfCentralDirRecord::m_DataMap'
/usr/bin/ld: CMakeFiles/filesystem_stdio.dir/basefilesystem.cpp.o: in function `void CByteswap::SwapFieldsToTargetEndian<ZIP_FileHeader>(ZIP_FileHeader*, void*, unsigned int)':
/home/ridvan/source/Engine/src/public/tier1/byteswap.h:39: undefined reference to `ZIP_FileHeader::m_DataMap'
collect2: error: ld returned 1 exit status
make[2]: *** [filesystem/CMakeFiles/filesystem_stdio.dir/build.make:185: filesystem/libfilesystem_stdio.so] Error 1
make[1]: *** [CMakeFiles/Makefile2:479: filesystem/CMakeFiles/filesystem_stdio.dir/all] Error 2
make: *** [Makefile:84: all] Error 2
``` | non_priority | filesystem stdio doesn t link on linux linking cxx shared library libfilesystem stdio so usr bin ld cmakefiles filesystem stdio dir queuedloader cpp o in function adjustasynciospeed home ridvan source engine src filesystem queuedloader cpp undefined reference to g pfullfilesystem usr bin ld home ridvan source engine src filesystem queuedloader cpp undefined reference to g pfullfilesystem usr bin ld home ridvan source engine src filesystem queuedloader cpp undefined reference to g pfullfilesystem usr bin ld home ridvan source engine src filesystem queuedloader cpp undefined reference to g pfullfilesystem usr bin ld cmakefiles filesystem stdio dir queuedloader cpp o in function iocomputationjob filejob t void int loadererror t home ridvan source engine src filesystem queuedloader cpp undefined reference to g pfullfilesystem usr bin ld cmakefiles filesystem stdio dir queuedloader cpp o home ridvan source engine src filesystem queuedloader cpp more undefined references to g pfullfilesystem follow usr bin ld cmakefiles filesystem stdio dir queuedloader cpp o in function connect void char const int home ridvan source engine src public h undefined reference to void char const int int usr bin ld cmakefiles filesystem stdio dir queuedloader cpp o in function disconnect home ridvan source engine src public h undefined reference to usr bin ld cmakefiles filesystem stdio dir basefilesystem cpp o in function cbasefilesystem cbasefilesystem home ridvan source engine src filesystem basefilesystem cpp undefined reference to g pfullfilesystem usr bin ld cmakefiles filesystem stdio dir basefilesystem cpp o in function cbasefilesystem loadkeyvalues keyvalues ifilesystem keyvaluespreloadtype t char const char const home ridvan source engine src filesystem basefilesystem cpp undefined reference to ccompiledkeyvaluesreader instanceinplace keyvalues char const usr bin ld cmakefiles filesystem stdio dir basefilesystem cpp o in function cbasefilesystem loadkeyvalues ifilesystem keyvaluespreloadtype t char const char const home ridvan source engine src filesystem basefilesystem cpp undefined reference to ccompiledkeyvaluesreader instance char const usr bin ld cmakefiles filesystem stdio dir basefilesystem cpp o in function cbasefilesystem extractrootkeyname ifilesystem keyvaluespreloadtype t char unsigned int char const char const home ridvan source engine src filesystem basefilesystem cpp undefined reference to ccompiledkeyvaluesreader lookupkeyvaluesrootkeyname char const char unsigned int usr bin ld cmakefiles filesystem stdio dir basefilesystem cpp o in function cbasefilesystem setuppreloaddata home ridvan source engine src filesystem basefilesystem cpp undefined reference to ccompiledkeyvaluesreader ccompiledkeyvaluesreader usr bin ld home ridvan source engine src filesystem basefilesystem cpp undefined reference to ccompiledkeyvaluesreader loadfile char const usr bin ld cmakefiles filesystem stdio dir basefilesystem cpp o in function void cbyteswap swapfieldstotargetendian zip endofcentraldirrecord void unsigned int home ridvan source engine src public byteswap h undefined reference to zip endofcentraldirrecord m datamap usr bin ld cmakefiles filesystem stdio dir basefilesystem cpp o in function void cbyteswap swapfieldstotargetendian zip fileheader void unsigned int home ridvan source engine src public byteswap h undefined reference to zip fileheader m datamap error ld returned exit status make error make error make error | 0 |
2,514 | 8,655,460,059 | IssuesEvent | 2018-11-27 16:00:32 | codestation/qcma | https://api.github.com/repos/codestation/qcma | closed | QCMA stop connecting over WiFi with time | unmaintained | Ubuntu 16.04 QCMA 0.4.1
Ubuntu linked to N56U router w/Padavan (OpenWRT) by cable, the same router serves wifi to VITA
Starts with the system and work flawlessly several hours. Then stops connecting at all - PSVITA gives "PC is not connected" error
What can be done about this? | True | QCMA stop connecting over WiFi with time - Ubuntu 16.04 QCMA 0.4.1
Ubuntu linked to N56U router w/Padavan (OpenWRT) by cable, the same router serves wifi to VITA
Starts with the system and work flawlessly several hours. Then stops connecting at all - PSVITA gives "PC is not connected" error
What can be done about this? | non_priority | qcma stop connecting over wifi with time ubuntu qcma ubuntu linked to router w padavan openwrt by cable the same router serves wifi to vita starts with the system and work flawlessly several hours then stops connecting at all psvita gives pc is not connected error what can be done about this | 0 |
39,589 | 10,354,601,625 | IssuesEvent | 2019-09-05 14:03:34 | virtualsatellite/VirtualSatellite4-Core | https://api.github.com/repos/virtualsatellite/VirtualSatellite4-Core | opened | Make maven more robust against checksum errors | build quality | '''
17:[WARNING] Could not validate integrity of download ...
'''
The above warnings shows up on TravisCI. The maven build should ignore this warning. | 1.0 | Make maven more robust against checksum errors - '''
17:[WARNING] Could not validate integrity of download ...
'''
The above warnings shows up on TravisCI. The maven build should ignore this warning. | non_priority | make maven more robust against checksum errors could not validate integrity of download the above warnings shows up on travisci the maven build should ignore this warning | 0 |
276,736 | 20,998,171,451 | IssuesEvent | 2022-03-29 15:05:04 | BetterThanTomorrow/calva | https://api.github.com/repos/BetterThanTomorrow/calva | closed | In example actual does not match expected. | documentation | In [Evaluation](../blob/published/docs/site/evaluation.md#evaluate-to-cursor) the expected result is `(12 21)` but the actual result is `(13 21)`.
Here is the corrected form.
```clojure
(->> [1 1 2 3 5 8 13 21]
(partition 2)
(zipmap [:a :b :c :d])
:d| ; => (13 21)
(apply -)
(Math/abs))
```
| 1.0 | In example actual does not match expected. - In [Evaluation](../blob/published/docs/site/evaluation.md#evaluate-to-cursor) the expected result is `(12 21)` but the actual result is `(13 21)`.
Here is the corrected form.
```clojure
(->> [1 1 2 3 5 8 13 21]
(partition 2)
(zipmap [:a :b :c :d])
:d| ; => (13 21)
(apply -)
(Math/abs))
```
| non_priority | in example actual does not match expected in blob published docs site evaluation md evaluate to cursor the expected result is but the actual result is here is the corrected form clojure partition zipmap d apply math abs | 0 |
244,651 | 20,682,295,318 | IssuesEvent | 2022-03-10 14:56:10 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | Failing test: Firefox UI Functional Tests.test/functional/apps/discover/_field_data·ts - discover app discover tab field data a bad syntax query should show an error message | Feature:Discover failed-test Team:DataDiscovery | A test failed on a tracked branch
```
Error: retry.try timeout: Error: retry.try timeout: ElementClickInterceptedError: Element <textarea id="i03d82c35-306d-11ec-bb53-ebe3e029bdd7" class="euiTextArea euiTextArea--resizeVertical euiTextArea--fullWidth kbnQueryBar__textarea kbnQueryBar__textarea--hasPrepend kbnQueryBar__textarea--hasAppend"> is not clickable at point (353,124) because another element <p> obscures it
at Object.throwDecodedError (node_modules/selenium-webdriver/lib/error.js:550:15)
at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:565:13)
at Executor.execute (node_modules/selenium-webdriver/lib/http.js:491:26)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Task.exec (test/functional/services/remote/prevent_parallel_calls.ts:28:20)
at onFailure (test/common/services/retry/retry_for_success.ts:17:9)
at retryForSuccess (test/common/services/retry/retry_for_success.ts:59:13)
at RetryService.try (test/common/services/retry/retry.ts:31:12)
at Proxy.clickByCssSelector (test/functional/services/common/find.ts:368:5)
at TestSubjects.click (test/functional/services/common/test_subjects.ts:105:5)
at /opt/local-ssd/buildkite/builds/kb-cigroup-4d-ca1222238c171f6b/elastic/kibana-hourly/kibana/test/functional/services/query_bar.ts:30:7
at runAttempt (test/common/services/retry/retry_for_success.ts:29:15)
at retryForSuccess (test/common/services/retry/retry_for_success.ts:68:21)
at RetryService.try (test/common/services/retry/retry.ts:31:12)
at QueryBarService.setQuery (test/functional/services/query_bar.ts:29:5)
at Context.<anonymous> (test/functional/apps/discover/_field_data.ts:73:9)
at Object.apply (node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16)
at onFailure (test/common/services/retry/retry_for_success.ts:17:9)
at retryForSuccess (test/common/services/retry/retry_for_success.ts:59:13)
at RetryService.try (test/common/services/retry/retry.ts:31:12)
at QueryBarService.setQuery (test/functional/services/query_bar.ts:29:5)
at Context.<anonymous> (test/functional/apps/discover/_field_data.ts:73:9)
at Object.apply (node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16)
```
First failure: [CI Build - master](https://buildkite.com/elastic/kibana-hourly/builds/1589#c3b48ab2-6009-40e7-a31a-d8f370bfa37d)
<!-- kibanaCiData = {"failed-test":{"test.class":"Firefox UI Functional Tests.test/functional/apps/discover/_field_data·ts","test.name":"discover app discover tab field data a bad syntax query should show an error message","test.failCount":1}} --> | 1.0 | Failing test: Firefox UI Functional Tests.test/functional/apps/discover/_field_data·ts - discover app discover tab field data a bad syntax query should show an error message - A test failed on a tracked branch
```
Error: retry.try timeout: Error: retry.try timeout: ElementClickInterceptedError: Element <textarea id="i03d82c35-306d-11ec-bb53-ebe3e029bdd7" class="euiTextArea euiTextArea--resizeVertical euiTextArea--fullWidth kbnQueryBar__textarea kbnQueryBar__textarea--hasPrepend kbnQueryBar__textarea--hasAppend"> is not clickable at point (353,124) because another element <p> obscures it
at Object.throwDecodedError (node_modules/selenium-webdriver/lib/error.js:550:15)
at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:565:13)
at Executor.execute (node_modules/selenium-webdriver/lib/http.js:491:26)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Task.exec (test/functional/services/remote/prevent_parallel_calls.ts:28:20)
at onFailure (test/common/services/retry/retry_for_success.ts:17:9)
at retryForSuccess (test/common/services/retry/retry_for_success.ts:59:13)
at RetryService.try (test/common/services/retry/retry.ts:31:12)
at Proxy.clickByCssSelector (test/functional/services/common/find.ts:368:5)
at TestSubjects.click (test/functional/services/common/test_subjects.ts:105:5)
at /opt/local-ssd/buildkite/builds/kb-cigroup-4d-ca1222238c171f6b/elastic/kibana-hourly/kibana/test/functional/services/query_bar.ts:30:7
at runAttempt (test/common/services/retry/retry_for_success.ts:29:15)
at retryForSuccess (test/common/services/retry/retry_for_success.ts:68:21)
at RetryService.try (test/common/services/retry/retry.ts:31:12)
at QueryBarService.setQuery (test/functional/services/query_bar.ts:29:5)
at Context.<anonymous> (test/functional/apps/discover/_field_data.ts:73:9)
at Object.apply (node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16)
at onFailure (test/common/services/retry/retry_for_success.ts:17:9)
at retryForSuccess (test/common/services/retry/retry_for_success.ts:59:13)
at RetryService.try (test/common/services/retry/retry.ts:31:12)
at QueryBarService.setQuery (test/functional/services/query_bar.ts:29:5)
at Context.<anonymous> (test/functional/apps/discover/_field_data.ts:73:9)
at Object.apply (node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16)
```
First failure: [CI Build - master](https://buildkite.com/elastic/kibana-hourly/builds/1589#c3b48ab2-6009-40e7-a31a-d8f370bfa37d)
<!-- kibanaCiData = {"failed-test":{"test.class":"Firefox UI Functional Tests.test/functional/apps/discover/_field_data·ts","test.name":"discover app discover tab field data a bad syntax query should show an error message","test.failCount":1}} --> | non_priority | failing test firefox ui functional tests test functional apps discover field data·ts discover app discover tab field data a bad syntax query should show an error message a test failed on a tracked branch error retry try timeout error retry try timeout elementclickinterceptederror element is not clickable at point because another element obscures it at object throwdecodederror node modules selenium webdriver lib error js at parsehttpresponse node modules selenium webdriver lib http js at executor execute node modules selenium webdriver lib http js at processticksandrejections node internal process task queues at task exec test functional services remote prevent parallel calls ts at onfailure test common services retry retry for success ts at retryforsuccess test common services retry retry for success ts at retryservice try test common services retry retry ts at proxy clickbycssselector test functional services common find ts at testsubjects click test functional services common test subjects ts at opt local ssd buildkite builds kb cigroup elastic kibana hourly kibana test functional services query bar ts at runattempt test common services retry retry for success ts at retryforsuccess test common services retry retry for success ts at retryservice try test common services retry retry ts at querybarservice setquery test functional services query bar ts at context test functional apps discover field data ts at object apply node modules kbn test target node functional test runner lib mocha wrap function js at onfailure test common services retry retry for success ts at retryforsuccess test common services retry retry for success ts at retryservice try test common services retry retry ts at querybarservice setquery test functional services query bar ts at context test functional apps discover field data ts at object apply node modules kbn test target node functional test runner lib mocha wrap function js first failure | 0 |
309,810 | 26,679,167,381 | IssuesEvent | 2023-01-26 16:21:29 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | Test(s) needed for [maps] fix Can not style by date time with vector tiles #124530 | tests_needed Team:Presentation Feature:Maps | Kibana QA Team is following up on closed PRs for regressions and blockers to see if tests were added. Please link a PR with added tests for PR https://github.com/elastic/kibana/pull/124530 or comment why tests are not needed or not possible. | 1.0 | Test(s) needed for [maps] fix Can not style by date time with vector tiles #124530 - Kibana QA Team is following up on closed PRs for regressions and blockers to see if tests were added. Please link a PR with added tests for PR https://github.com/elastic/kibana/pull/124530 or comment why tests are not needed or not possible. | non_priority | test s needed for fix can not style by date time with vector tiles kibana qa team is following up on closed prs for regressions and blockers to see if tests were added please link a pr with added tests for pr or comment why tests are not needed or not possible | 0 |
438,799 | 30,662,523,504 | IssuesEvent | 2023-07-25 15:53:11 | astral-sh/ruff | https://api.github.com/repos/astral-sh/ruff | closed | W505 does not seem to work | documentation | <!--
Thank you for taking the time to report an issue! We're glad to have you involved with Ruff.
If you're filing a bug report, please consider including the following information:
* A minimal code snippet that reproduces the bug.
* The command you invoked (e.g., `ruff /path/to/file.py --fix`), ideally including the `--isolated` flag.
* The current Ruff settings (any relevant sections from your `pyproject.toml`).
* The current Ruff version (`ruff --version`).
-->
W505 does not seem to trigger for the [bad example in its docs](https://beta.ruff.rs/docs/rules/doc-line-too-long/#example):
```shellsession
ruff 0.0.280
$ cat t.py
def function(x):
"""Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis auctor purus ut ex fermentum, at maximus est hendrerit."""
$ ruff t.py
t.py:2:89: E501 Line too long (127 > 88 characters)
Found 1 error.
$ ruff --select W505 --ignore E501 t.py
$
```
Actually, I seem unable to trigger it in the first place:
```shellsession
$ cat t.py
def function(x):
# Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis auctor purus ut ex fermentum, at maximus est hendrerit.
pass
$ ruff t.py
t.py:2:89: E501 Line too long (123 > 88 characters)
Found 1 error.
$ ruff --select W505 --ignore E501 t.py
$
```
No `pyproject.toml` involved. | 1.0 | W505 does not seem to work - <!--
Thank you for taking the time to report an issue! We're glad to have you involved with Ruff.
If you're filing a bug report, please consider including the following information:
* A minimal code snippet that reproduces the bug.
* The command you invoked (e.g., `ruff /path/to/file.py --fix`), ideally including the `--isolated` flag.
* The current Ruff settings (any relevant sections from your `pyproject.toml`).
* The current Ruff version (`ruff --version`).
-->
W505 does not seem to trigger for the [bad example in its docs](https://beta.ruff.rs/docs/rules/doc-line-too-long/#example):
```shellsession
ruff 0.0.280
$ cat t.py
def function(x):
"""Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis auctor purus ut ex fermentum, at maximus est hendrerit."""
$ ruff t.py
t.py:2:89: E501 Line too long (127 > 88 characters)
Found 1 error.
$ ruff --select W505 --ignore E501 t.py
$
```
Actually, I seem unable to trigger it in the first place:
```shellsession
$ cat t.py
def function(x):
# Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis auctor purus ut ex fermentum, at maximus est hendrerit.
pass
$ ruff t.py
t.py:2:89: E501 Line too long (123 > 88 characters)
Found 1 error.
$ ruff --select W505 --ignore E501 t.py
$
```
No `pyproject.toml` involved. | non_priority | does not seem to work thank you for taking the time to report an issue we re glad to have you involved with ruff if you re filing a bug report please consider including the following information a minimal code snippet that reproduces the bug the command you invoked e g ruff path to file py fix ideally including the isolated flag the current ruff settings any relevant sections from your pyproject toml the current ruff version ruff version does not seem to trigger for the shellsession ruff cat t py def function x lorem ipsum dolor sit amet consectetur adipiscing elit duis auctor purus ut ex fermentum at maximus est hendrerit ruff t py t py line too long characters found error ruff select ignore t py actually i seem unable to trigger it in the first place shellsession cat t py def function x lorem ipsum dolor sit amet consectetur adipiscing elit duis auctor purus ut ex fermentum at maximus est hendrerit pass ruff t py t py line too long characters found error ruff select ignore t py no pyproject toml involved | 0 |
226,481 | 24,947,191,808 | IssuesEvent | 2022-11-01 01:59:08 | saif-khan1211/First_real_scan | https://api.github.com/repos/saif-khan1211/First_real_scan | closed | CVE-2022-40156 (High) detected in xstream-1.4.8.jar - autoclosed | security vulnerability | ## CVE-2022-40156 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.8.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to vulnerable library: /target/libs/provided/xstream-1.4.8.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.8.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Those using Xstream to seralize XML data may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. This effect may support a denial of service attack.
<p>Publish Date: 2022-09-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-40156>CVE-2022-40156</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>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-40156 (High) detected in xstream-1.4.8.jar - autoclosed - ## CVE-2022-40156 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.8.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to vulnerable library: /target/libs/provided/xstream-1.4.8.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.8.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Those using Xstream to seralize XML data may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. This effect may support a denial of service attack.
<p>Publish Date: 2022-09-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-40156>CVE-2022-40156</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>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in xstream jar autoclosed cve high severity vulnerability vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to vulnerable library target libs provided xstream jar dependency hierarchy x xstream jar vulnerable library found in base branch main vulnerability details those using xstream to seralize xml data may be vulnerable to denial of service attacks dos if the parser is running on user supplied input an attacker may supply content that causes the parser to crash by stackoverflow this effect may support a denial of service attack 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 step up your open source security game with mend | 0 |
87,546 | 25,142,853,276 | IssuesEvent | 2022-11-10 01:12:31 | apache/pulsar | https://api.github.com/repos/apache/pulsar | closed | Pulsar Client has no support in Mac 10.14.5 (18F132) ? | type/bug component/build triage/week-24 lifecycle/stale | **Describe the bug**
Python Pulsar Client say import _pulsar ImportError Reason: image not found
**To Reproduce**
Steps to reproduce the behavior:
In Mac: pip install pulsar-client --upgrade
python consumer.py
```
Traceback (most recent call last):
File "consumer.py", line 1, in <module>
import pulsar
File "/Users/chethan/anaconda3/lib/python3.7/site-packages/pulsar/__init__.py", line 99, in <module>
import _pulsar
ImportError: dlopen(/Users/chethan/anaconda3/lib/python3.7/site-packages/_pulsar.cpython-37m-darwin.so, 2): Library not loaded: /usr/local/opt/python/Frameworks/Python.framework/Versions/3.7/Python
Referenced from: /Users/chethan/anaconda3/lib/python3.7/site-packages/_pulsar.cpython-37m-darwin.so
Reason: image not found
```
**Desktop (please complete the following information):**
- OS: Mac 10.14.5 (18F132)
**Additional context**
Tried in both normal env and Conda env: 3.7, 2.7
Whats the possible solution?
Also, In official [docs](https://pulsar.apache.org/docs/en/client-libraries-python/): `pip install pulsar-client==2.3.2`
But, I got error while installing:
Collecting pulsar-client==2.3.2
```
ERROR: Could not find a version that satisfies the requirement pulsar-client==2.3.2 (from versions: 1.18.dev1, 1.19.dev1, 1.19.dev2, 1.19.0, 1.20.0, 1.21.0, 1.22.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, 2.3.0, 2.3.0.post1, 2.3.1)
ERROR: No matching distribution found for pulsar-client==2.3.2
```
Thanks!. | 1.0 | Pulsar Client has no support in Mac 10.14.5 (18F132) ? - **Describe the bug**
Python Pulsar Client say import _pulsar ImportError Reason: image not found
**To Reproduce**
Steps to reproduce the behavior:
In Mac: pip install pulsar-client --upgrade
python consumer.py
```
Traceback (most recent call last):
File "consumer.py", line 1, in <module>
import pulsar
File "/Users/chethan/anaconda3/lib/python3.7/site-packages/pulsar/__init__.py", line 99, in <module>
import _pulsar
ImportError: dlopen(/Users/chethan/anaconda3/lib/python3.7/site-packages/_pulsar.cpython-37m-darwin.so, 2): Library not loaded: /usr/local/opt/python/Frameworks/Python.framework/Versions/3.7/Python
Referenced from: /Users/chethan/anaconda3/lib/python3.7/site-packages/_pulsar.cpython-37m-darwin.so
Reason: image not found
```
**Desktop (please complete the following information):**
- OS: Mac 10.14.5 (18F132)
**Additional context**
Tried in both normal env and Conda env: 3.7, 2.7
Whats the possible solution?
Also, In official [docs](https://pulsar.apache.org/docs/en/client-libraries-python/): `pip install pulsar-client==2.3.2`
But, I got error while installing:
Collecting pulsar-client==2.3.2
```
ERROR: Could not find a version that satisfies the requirement pulsar-client==2.3.2 (from versions: 1.18.dev1, 1.19.dev1, 1.19.dev2, 1.19.0, 1.20.0, 1.21.0, 1.22.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, 2.3.0, 2.3.0.post1, 2.3.1)
ERROR: No matching distribution found for pulsar-client==2.3.2
```
Thanks!. | non_priority | pulsar client has no support in mac describe the bug python pulsar client say import pulsar importerror reason image not found to reproduce steps to reproduce the behavior in mac pip install pulsar client upgrade python consumer py traceback most recent call last file consumer py line in import pulsar file users chethan lib site packages pulsar init py line in import pulsar importerror dlopen users chethan lib site packages pulsar cpython darwin so library not loaded usr local opt python frameworks python framework versions python referenced from users chethan lib site packages pulsar cpython darwin so reason image not found desktop please complete the following information os mac additional context tried in both normal env and conda env whats the possible solution also in official pip install pulsar client but i got error while installing collecting pulsar client error could not find a version that satisfies the requirement pulsar client from versions error no matching distribution found for pulsar client thanks | 0 |
95,298 | 8,555,447,327 | IssuesEvent | 2018-11-08 10:03:58 | humera987/FXLabs-Test-Automation | https://api.github.com/repos/humera987/FXLabs-Test-Automation | reopened | testing8 : ApiV1VaultGetPathParamPagesizeMysqlSqlInjectionTimebound | testing8 testing8 | Project : testing8
Job : UAT
Env : UAT
Region : US_WEST_3
Result : fail
Status Code : 404
Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Thu, 08 Nov 2018 09:57:39 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/vault?pageSize=' AND sleep(7)=0; --
Request :
Response :
{
"timestamp" : "2018-11-08T09:57:39.867+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/vault"
}
Logs :
Assertion [@ResponseTime < 7000 OR @ResponseTime > 10000] resolved-to [2098 < 7000 OR 2098 > 10000] result [Passed]Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]
--- FX Bot --- | 2.0 | testing8 : ApiV1VaultGetPathParamPagesizeMysqlSqlInjectionTimebound - Project : testing8
Job : UAT
Env : UAT
Region : US_WEST_3
Result : fail
Status Code : 404
Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Thu, 08 Nov 2018 09:57:39 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/vault?pageSize=' AND sleep(7)=0; --
Request :
Response :
{
"timestamp" : "2018-11-08T09:57:39.867+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/vault"
}
Logs :
Assertion [@ResponseTime < 7000 OR @ResponseTime > 10000] resolved-to [2098 < 7000 OR 2098 > 10000] result [Passed]Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]
--- FX Bot --- | non_priority | project job uat env uat region us west result fail status code headers x content type options x xss protection cache control pragma expires x frame options content type transfer encoding date endpoint and sleep request response timestamp status error not found message no message available path api api vault logs assertion resolved to result assertion resolved to result fx bot | 0 |
21,048 | 14,289,308,466 | IssuesEvent | 2020-11-23 19:03:04 | 18F/tts-tech-portfolio | https://api.github.com/repos/18F/tts-tech-portfolio | opened | gather infrastructure roadmap from each TTS team | g: accepted i: infrastructure improvement t: weeks | ## Background Information
<!--Description, links, [user stories](https://www.agilealliance.org/glossary/user-stories/), what is the problem we are trying to solve, etc. If the work is described/tracked elsewhere, feel free to simply link there. Use the [INVEST](https://www.agilealliance.org/glossary/invest) method to assess completeness.-->
Prerequisite/parallel to https://github.com/18F/tts-tech-portfolio/issues/827. Rather than thinking top-down in terms of goals, it could be helpful to find what TTS teams are planning to do around their systems and find commonalities there.
## Implementation Steps
- [ ] Create a template
- [ ] Current and desired states are reflected
## Acceptance Criteria
<!--[Definition of Done](https://www.agilealliance.org/glossary/definition-of-done)-->
- [ ] There is a documented roadmap around infrastructure for all systems at TTS
| 1.0 | gather infrastructure roadmap from each TTS team - ## Background Information
<!--Description, links, [user stories](https://www.agilealliance.org/glossary/user-stories/), what is the problem we are trying to solve, etc. If the work is described/tracked elsewhere, feel free to simply link there. Use the [INVEST](https://www.agilealliance.org/glossary/invest) method to assess completeness.-->
Prerequisite/parallel to https://github.com/18F/tts-tech-portfolio/issues/827. Rather than thinking top-down in terms of goals, it could be helpful to find what TTS teams are planning to do around their systems and find commonalities there.
## Implementation Steps
- [ ] Create a template
- [ ] Current and desired states are reflected
## Acceptance Criteria
<!--[Definition of Done](https://www.agilealliance.org/glossary/definition-of-done)-->
- [ ] There is a documented roadmap around infrastructure for all systems at TTS
| non_priority | gather infrastructure roadmap from each tts team background information prerequisite parallel to rather than thinking top down in terms of goals it could be helpful to find what tts teams are planning to do around their systems and find commonalities there implementation steps create a template current and desired states are reflected acceptance criteria there is a documented roadmap around infrastructure for all systems at tts | 0 |
215 | 4,755,158,692 | IssuesEvent | 2016-10-24 09:52:55 | cf-tm-bot/openstack_cpi | https://api.github.com/repos/cf-tm-bot/openstack_cpi | opened | Use terraform resource for automated setup in BATS and E2E - Story Id: 132996553 | env-creation-automation feature pipeline unstarted | Same as in https://www.pivotaltracker.com/story/show/119565681
---
Mirrors: [story 132996553](https://www.pivotaltracker.com/story/show/132996553) submitted on Oct 24, 2016 UTC
- **Requester**: Marco Voelz
- **Estimate**: 0.0 | 1.0 | Use terraform resource for automated setup in BATS and E2E - Story Id: 132996553 - Same as in https://www.pivotaltracker.com/story/show/119565681
---
Mirrors: [story 132996553](https://www.pivotaltracker.com/story/show/132996553) submitted on Oct 24, 2016 UTC
- **Requester**: Marco Voelz
- **Estimate**: 0.0 | non_priority | use terraform resource for automated setup in bats and story id same as in mirrors submitted on oct utc requester marco voelz estimate | 0 |
315,669 | 27,093,920,664 | IssuesEvent | 2023-02-15 00:06:22 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | roachtest: tpcc/mixed-headroom/multiple-upgrades/n5cpu16 failed | C-test-failure O-robot O-roachtest branch-master release-blocker T-testeng | roachtest.tpcc/mixed-headroom/multiple-upgrades/n5cpu16 [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/7952891?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/7952891?buildTab=artifacts#/tpcc/mixed-headroom/multiple-upgrades/n5cpu16) on master @ [052acc88ad9d7296ce6b8b441627fb469cc74d95](https://github.com/cockroachdb/cockroach/commits/052acc88ad9d7296ce6b8b441627fb469cc74d95):
```
test artifacts and logs in: /artifacts/tpcc/mixed-headroom/multiple-upgrades/n5cpu16/run_1
(test_impl.go:291).Fatal: 4: expected version 1000022.2-16, got 1000022.1-18
(test_impl.go:291).Fatal: monitor failure: monitor task failed: output in run_172308.167707597_n5_cockroach_workload_run_tpcc: ./cockroach workload run tpcc --warehouses=909 --histograms=perf/stats.json --ramp=5m0s --duration=1h40m0s --prometheus-port=2112 --pprofport=33333 {pgurl:1-4} returned: context canceled
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=16</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/test-eng
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*tpcc/mixed-headroom/multiple-upgrades/n5cpu16.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-22441 | 3.0 | roachtest: tpcc/mixed-headroom/multiple-upgrades/n5cpu16 failed - roachtest.tpcc/mixed-headroom/multiple-upgrades/n5cpu16 [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/7952891?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/7952891?buildTab=artifacts#/tpcc/mixed-headroom/multiple-upgrades/n5cpu16) on master @ [052acc88ad9d7296ce6b8b441627fb469cc74d95](https://github.com/cockroachdb/cockroach/commits/052acc88ad9d7296ce6b8b441627fb469cc74d95):
```
test artifacts and logs in: /artifacts/tpcc/mixed-headroom/multiple-upgrades/n5cpu16/run_1
(test_impl.go:291).Fatal: 4: expected version 1000022.2-16, got 1000022.1-18
(test_impl.go:291).Fatal: monitor failure: monitor task failed: output in run_172308.167707597_n5_cockroach_workload_run_tpcc: ./cockroach workload run tpcc --warehouses=909 --histograms=perf/stats.json --ramp=5m0s --duration=1h40m0s --prometheus-port=2112 --pprofport=33333 {pgurl:1-4} returned: context canceled
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=16</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/test-eng
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*tpcc/mixed-headroom/multiple-upgrades/n5cpu16.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-22441 | non_priority | roachtest tpcc mixed headroom multiple upgrades failed roachtest tpcc mixed headroom multiple upgrades with on master test artifacts and logs in artifacts tpcc mixed headroom multiple upgrades run test impl go fatal expected version got test impl go fatal monitor failure monitor task failed output in run cockroach workload run tpcc cockroach workload run tpcc warehouses histograms perf stats json ramp duration prometheus port pprofport pgurl returned context canceled parameters roachtest cloud gce roachtest cpu roachtest encrypted false roachtest fs roachtest localssd true roachtest ssd help see see cc cockroachdb test eng jira issue crdb | 0 |
19,535 | 14,216,158,205 | IssuesEvent | 2020-11-17 08:35:11 | Bitmessage/PyBitmessage | https://api.github.com/repos/Bitmessage/PyBitmessage | opened | Going offline doesn't clear list of network connections | bug usability | Even though going offline drops the network connections, they remain shown in the "Network Status" tab. | True | Going offline doesn't clear list of network connections - Even though going offline drops the network connections, they remain shown in the "Network Status" tab. | non_priority | going offline doesn t clear list of network connections even though going offline drops the network connections they remain shown in the network status tab | 0 |
8,316 | 6,515,193,192 | IssuesEvent | 2017-08-26 12:22:02 | webpack/webpack | https://api.github.com/repos/webpack/webpack | closed | Allow loaders to emit files on demand in development environment | D2: Medium (Contrib. Difficulty) D3: Hard (Contrib. Difficulty) enhancement inactive P4: Nice To Have performance X5: work required (PR / Help Wanted) | **I'm submitting a feature request**
**Webpack version:**
2.x
**Current behavior:**
emitFile requires a string or buffer for the file
**Expected/desired behavior:**
emitFile allows a function or stream
**What is the motivation / use case for changing the behavior?**
To allow loaders to change files when the file is requested when running a development environment. This would allow loaders to modify images with resize or filters, operations that takes time, and to allow a Webpack dev server to start fast. The problem with the current approach is that the loaders will need to resize or edit images when starting the Webpack dev server, this adds up really fast when using multiple or large resources to a point where it is no longer usable.
Maybe this should only be enabled on a dev environment because there is no point in having this for a production environment.
| True | Allow loaders to emit files on demand in development environment - **I'm submitting a feature request**
**Webpack version:**
2.x
**Current behavior:**
emitFile requires a string or buffer for the file
**Expected/desired behavior:**
emitFile allows a function or stream
**What is the motivation / use case for changing the behavior?**
To allow loaders to change files when the file is requested when running a development environment. This would allow loaders to modify images with resize or filters, operations that takes time, and to allow a Webpack dev server to start fast. The problem with the current approach is that the loaders will need to resize or edit images when starting the Webpack dev server, this adds up really fast when using multiple or large resources to a point where it is no longer usable.
Maybe this should only be enabled on a dev environment because there is no point in having this for a production environment.
| non_priority | allow loaders to emit files on demand in development environment i m submitting a feature request webpack version x current behavior emitfile requires a string or buffer for the file expected desired behavior emitfile allows a function or stream what is the motivation use case for changing the behavior to allow loaders to change files when the file is requested when running a development environment this would allow loaders to modify images with resize or filters operations that takes time and to allow a webpack dev server to start fast the problem with the current approach is that the loaders will need to resize or edit images when starting the webpack dev server this adds up really fast when using multiple or large resources to a point where it is no longer usable maybe this should only be enabled on a dev environment because there is no point in having this for a production environment | 0 |
146,460 | 23,071,645,601 | IssuesEvent | 2022-07-25 18:40:39 | Azure/autorest.csharp | https://api.github.com/repos/Azure/autorest.csharp | opened | Generate options parameters types in convenience methods with long parameter lists | v3 Client needs-design DPG/RLC v1.1 | As described in [the guidelines](https://azure.github.io/azure-sdk/dotnet_introduction.html#dotnet-parameters) and designed in https://github.com/Azure/autorest.csharp/issues/2475. | 1.0 | Generate options parameters types in convenience methods with long parameter lists - As described in [the guidelines](https://azure.github.io/azure-sdk/dotnet_introduction.html#dotnet-parameters) and designed in https://github.com/Azure/autorest.csharp/issues/2475. | non_priority | generate options parameters types in convenience methods with long parameter lists as described in and designed in | 0 |
27,183 | 12,521,622,870 | IssuesEvent | 2020-06-03 17:42:45 | microsoft/BotFramework-WebChat | https://api.github.com/repos/microsoft/BotFramework-WebChat | closed | DirectLine welcome message from standard bot and examples | Bot Services Question customer-replied-to customer-reported | Hi,
Author ask me to open new issue if I have got something new
This is continue for
https://github.com/microsoft/BotFramework-WebChat/issues/3187#event-3394224413
I have got standard QnA maker setup. Publish bot to azure. Add DirectLine channel.
download https://github.com/Microsoft/BotBuilder-Samples.git
go to samples/javascript_es6/70.styling-webchat
setup my secret
```json
window.WebChat.renderWebChat({
directLine: window.WebChat.createDirectLine({ secret: 'secret from directline channel' }),
// directLine: window.WebChat.createDirectLine({ token }),
styleOptions
}, document.getElementById('webchat'));
```
run `npx serve`
when I open bot page 'localhost:5000' - I have no saw welcome message.
What I expect to get: Welcome message from QnA bot
Actual result: I have got welcome message ONLY after send first message.
I think we should fix example or fix standard bot for QnA maker.
Same behavior with 01.getting-started/g.hybrid-react-npm/ example
Thanks
Regards,
Vitaliy | 1.0 | DirectLine welcome message from standard bot and examples - Hi,
Author ask me to open new issue if I have got something new
This is continue for
https://github.com/microsoft/BotFramework-WebChat/issues/3187#event-3394224413
I have got standard QnA maker setup. Publish bot to azure. Add DirectLine channel.
download https://github.com/Microsoft/BotBuilder-Samples.git
go to samples/javascript_es6/70.styling-webchat
setup my secret
```json
window.WebChat.renderWebChat({
directLine: window.WebChat.createDirectLine({ secret: 'secret from directline channel' }),
// directLine: window.WebChat.createDirectLine({ token }),
styleOptions
}, document.getElementById('webchat'));
```
run `npx serve`
when I open bot page 'localhost:5000' - I have no saw welcome message.
What I expect to get: Welcome message from QnA bot
Actual result: I have got welcome message ONLY after send first message.
I think we should fix example or fix standard bot for QnA maker.
Same behavior with 01.getting-started/g.hybrid-react-npm/ example
Thanks
Regards,
Vitaliy | non_priority | directline welcome message from standard bot and examples hi author ask me to open new issue if i have got something new this is continue for i have got standard qna maker setup publish bot to azure add directline channel download go to samples javascript styling webchat setup my secret json window webchat renderwebchat directline window webchat createdirectline secret secret from directline channel directline window webchat createdirectline token styleoptions document getelementbyid webchat run npx serve when i open bot page localhost i have no saw welcome message what i expect to get welcome message from qna bot actual result i have got welcome message only after send first message i think we should fix example or fix standard bot for qna maker same behavior with getting started g hybrid react npm example thanks regards vitaliy | 0 |
8,805 | 27,172,278,654 | IssuesEvent | 2023-02-17 20:37:39 | OneDrive/onedrive-api-docs | https://api.github.com/repos/OneDrive/onedrive-api-docs | closed | Upload large file The uploaded fragment is not contiguous with the last one | Needs: Triage :mag: automation:Closed | 1st session uploaded. 2nd session never though I am sending the expected range. Please let me know what's this issue here?
array(2) {
["postBody"]=>
object(GuzzleHttp\Psr7\Stream)#6 (7) {
["stream":"GuzzleHttp\Psr7\Stream":private]=>
resource(8) of type (stream)
["size":"GuzzleHttp\Psr7\Stream":private]=>
NULL
["seekable":"GuzzleHttp\Psr7\Stream":private]=>
bool(true)
["readable":"GuzzleHttp\Psr7\Stream":private]=>
bool(true)
["writable":"GuzzleHttp\Psr7\Stream":private]=>
bool(true)
["uri":"GuzzleHttp\Psr7\Stream":private]=>
string(10) "php://temp"
["customMetadata":"GuzzleHttp\Psr7\Stream":private]=>
array(0) {
}
}
["headers"]=>
array(2) {
["Content-Length"]=>
int(5242880)
["Content-Range"]=>
string(23) "bytes 0-5242879/8255206"
}
}
array(2) {
["expirationDateTime"]=>
string(24) "2020-05-10T14:46:37.498Z"
["nextExpectedRanges"]=>
array(1) {
[0]=>
string(15) "5242880-8255205"
}
}
array(2) {
["postBody"]=>
object(GuzzleHttp\Psr7\Stream)#6 (7) {
["stream":"GuzzleHttp\Psr7\Stream":private]=>
resource(22) of type (stream)
["size":"GuzzleHttp\Psr7\Stream":private]=>
NULL
["seekable":"GuzzleHttp\Psr7\Stream":private]=>
bool(true)
["readable":"GuzzleHttp\Psr7\Stream":private]=>
bool(true)
["writable":"GuzzleHttp\Psr7\Stream":private]=>
bool(true)
["uri":"GuzzleHttp\Psr7\Stream":private]=>
string(10) "php://temp"
["customMetadata":"GuzzleHttp\Psr7\Stream":private]=>
array(0) {
}
}
["headers"]=>
array(2) {
["Content-Length"]=>
int(3012326)
["Content-Range"]=>
string(29) "bytes 5242880-8255205/8255206"
}
}
string(1205) "Client error: `PUT https://api.onedrive.com/rup/8653f7cfbe8f5ceb/eyJSZXNvdXJjZUlEIjoiODY1M0Y3Q0ZCRThGNUNFQiE4NjY5OSIsIlJlbGF0aW9uc2hpcE5hbWUiOiJzY3JyLm1vdiJ9/4my5v0-oqYXPv_hIdc3LcYaZJmfyvixEPQnqsKNodbUEAg5I91U1oB6afvzKdyUR6tmCQqDheoU59dkBmUdAlU4vesGELKuDp0BEmcEJIEOnQ/eyJuYW1lIjoic2Nyci5tb3YiLCJkZXNjcmlwdGlvbiI6IiIsIkBuYW1lLmNvbmZsaWN0QmVoYXZpb3IiOiJyZW5hbWUifQ/4wFN_ylnu7E1H-7J8S9Sh4gYzKzPUSIPD_CFEzV3NwkfR77b34G4TxFmNADPppVdbwKcmdvGRuGTEMAaeHUH6esnnFBBCHnDVJkP7Afl00dAdbF0ffTpbaPCXc6OZo7Hc6Ym43ZoD3e1bGbfEOmFSpKX7zz--Sv7V-v_57h4qSxX3AkHCSfFGeMv0faDEIQBeOMnZkf-_ADQUymncGvALpUXTWz4n7tNX4TzVLCUGgyGYI-jLQfoxk_1DUNhwByC2sNgkfD9ss2YERJBmfzw2BvIs2sA-B3ACyBT1r0CoShk_FR-Z7ko6wMbfYEcpJLnXkAEZQxEj_aMMuNggCOnGhIzdQny76alEcorHkLXICYfeowfFYD1j40Pmrfb8oKEQoJb8d8tUBv835BGBRkoS9MbywWDmrG0yw-T3rdXKQ0FjDTI0qAfj4-YXdbaXNipjV0dS6Y9FpUfXChiz11anqIlAIlPHaxQN9Y0RITv8acnG0OVJzzaCNFBL4YtBA48Wv_SoXQaTv_A87i8DbVE7GuMOMYOI68rF6aoeZ7QFtIlJrSP4r4zaux5OINkTaVyvYQLNlH7Bqb6ofpaAGuT5X2Sq4SvEEz0LNv8trsT6v75iLTzX5SSvMoi13J3XYRCHk` resulted in a `416 Requested Range Not Satisfiable` response:
{"error":{"code":"invalidRange","message":"The uploaded fragment is not contiguous with the last one.","innererror":{"co (truncated...)
"
int(416)
| 1.0 | Upload large file The uploaded fragment is not contiguous with the last one - 1st session uploaded. 2nd session never though I am sending the expected range. Please let me know what's this issue here?
array(2) {
["postBody"]=>
object(GuzzleHttp\Psr7\Stream)#6 (7) {
["stream":"GuzzleHttp\Psr7\Stream":private]=>
resource(8) of type (stream)
["size":"GuzzleHttp\Psr7\Stream":private]=>
NULL
["seekable":"GuzzleHttp\Psr7\Stream":private]=>
bool(true)
["readable":"GuzzleHttp\Psr7\Stream":private]=>
bool(true)
["writable":"GuzzleHttp\Psr7\Stream":private]=>
bool(true)
["uri":"GuzzleHttp\Psr7\Stream":private]=>
string(10) "php://temp"
["customMetadata":"GuzzleHttp\Psr7\Stream":private]=>
array(0) {
}
}
["headers"]=>
array(2) {
["Content-Length"]=>
int(5242880)
["Content-Range"]=>
string(23) "bytes 0-5242879/8255206"
}
}
array(2) {
["expirationDateTime"]=>
string(24) "2020-05-10T14:46:37.498Z"
["nextExpectedRanges"]=>
array(1) {
[0]=>
string(15) "5242880-8255205"
}
}
array(2) {
["postBody"]=>
object(GuzzleHttp\Psr7\Stream)#6 (7) {
["stream":"GuzzleHttp\Psr7\Stream":private]=>
resource(22) of type (stream)
["size":"GuzzleHttp\Psr7\Stream":private]=>
NULL
["seekable":"GuzzleHttp\Psr7\Stream":private]=>
bool(true)
["readable":"GuzzleHttp\Psr7\Stream":private]=>
bool(true)
["writable":"GuzzleHttp\Psr7\Stream":private]=>
bool(true)
["uri":"GuzzleHttp\Psr7\Stream":private]=>
string(10) "php://temp"
["customMetadata":"GuzzleHttp\Psr7\Stream":private]=>
array(0) {
}
}
["headers"]=>
array(2) {
["Content-Length"]=>
int(3012326)
["Content-Range"]=>
string(29) "bytes 5242880-8255205/8255206"
}
}
string(1205) "Client error: `PUT https://api.onedrive.com/rup/8653f7cfbe8f5ceb/eyJSZXNvdXJjZUlEIjoiODY1M0Y3Q0ZCRThGNUNFQiE4NjY5OSIsIlJlbGF0aW9uc2hpcE5hbWUiOiJzY3JyLm1vdiJ9/4my5v0-oqYXPv_hIdc3LcYaZJmfyvixEPQnqsKNodbUEAg5I91U1oB6afvzKdyUR6tmCQqDheoU59dkBmUdAlU4vesGELKuDp0BEmcEJIEOnQ/eyJuYW1lIjoic2Nyci5tb3YiLCJkZXNjcmlwdGlvbiI6IiIsIkBuYW1lLmNvbmZsaWN0QmVoYXZpb3IiOiJyZW5hbWUifQ/4wFN_ylnu7E1H-7J8S9Sh4gYzKzPUSIPD_CFEzV3NwkfR77b34G4TxFmNADPppVdbwKcmdvGRuGTEMAaeHUH6esnnFBBCHnDVJkP7Afl00dAdbF0ffTpbaPCXc6OZo7Hc6Ym43ZoD3e1bGbfEOmFSpKX7zz--Sv7V-v_57h4qSxX3AkHCSfFGeMv0faDEIQBeOMnZkf-_ADQUymncGvALpUXTWz4n7tNX4TzVLCUGgyGYI-jLQfoxk_1DUNhwByC2sNgkfD9ss2YERJBmfzw2BvIs2sA-B3ACyBT1r0CoShk_FR-Z7ko6wMbfYEcpJLnXkAEZQxEj_aMMuNggCOnGhIzdQny76alEcorHkLXICYfeowfFYD1j40Pmrfb8oKEQoJb8d8tUBv835BGBRkoS9MbywWDmrG0yw-T3rdXKQ0FjDTI0qAfj4-YXdbaXNipjV0dS6Y9FpUfXChiz11anqIlAIlPHaxQN9Y0RITv8acnG0OVJzzaCNFBL4YtBA48Wv_SoXQaTv_A87i8DbVE7GuMOMYOI68rF6aoeZ7QFtIlJrSP4r4zaux5OINkTaVyvYQLNlH7Bqb6ofpaAGuT5X2Sq4SvEEz0LNv8trsT6v75iLTzX5SSvMoi13J3XYRCHk` resulted in a `416 Requested Range Not Satisfiable` response:
{"error":{"code":"invalidRange","message":"The uploaded fragment is not contiguous with the last one.","innererror":{"co (truncated...)
"
int(416)
| non_priority | upload large file the uploaded fragment is not contiguous with the last one session uploaded session never though i am sending the expected range please let me know what s this issue here array object guzzlehttp stream resource of type stream null bool true bool true bool true string php temp array array int string bytes array string array string array object guzzlehttp stream resource of type stream null bool true bool true bool true string php temp array array int string bytes string client error put resulted in a requested range not satisfiable response error code invalidrange message the uploaded fragment is not contiguous with the last one innererror co truncated int | 0 |
177,698 | 29,040,854,234 | IssuesEvent | 2023-05-13 00:31:03 | devssa/onde-codar-em-salvador | https://api.github.com/repos/devssa/onde-codar-em-salvador | closed | [Remoto] Python Developer na Coodesh | SALVADOR HOME OFFICE BACK-END BANCO DE DADOS REDES PYTHON MONGODB PLENO VISÃO COMPUTACIONAL ORIENTAÇÃO A OBJETOS DOCKER KUBERNETES DEVOPS DJANGO AWS REQUISITOS REMOTO Telecomunicações PROCESSOS GITHUB AZURE E-COMMERCE UMA DESIGN PATTERNS FLASK VENDAS PADRÕ METODOLOGIAS ÁGEIS MACHINE LEARNING NEGÓCIOS GCP PROGRAMAÇÃO FUNCIONAL ARQUITETURA DE SOFTWARE MONITORAMENTO ONBOARDING Stale | ## Descrição da vaga:
Esta é uma vaga de um parceiro da plataforma Coodesh, ao candidatar-se você terá acesso as informações completas sobre a empresa e benefícios.
Fique atento ao redirecionamento que vai te levar para uma url [https://coodesh.com](https://coodesh.com/vagas/pessoa-desenvolvedora-python-pleno-100percent-remoto-174847023?utm_source=github&utm_medium=devssa-onde-codar-em-salvador&modal=open) com o pop-up personalizado de candidatura. 👋
<p>A <strong>ClearSale</strong> está em busca de <strong><ins>Python Developer</ins></strong> para compor seu time!</p>
<p>A Diretoria do TechLabs é a área de tecnologia da ClearSale que atua no mercado de onboarding digital voltado a identificação de fraudes e criação de processos seguros e com experiência sem atrito - frictionless.</p>
<p></p>
<p><strong>Responsabilidades: </strong></p>
<ul>
<li>Desenvolvimento de API's em Python;</li>
<li>Implementação de modelos criados de machine learning na área de visão computacional e processamento de documentos;</li>
<li>Experimentar novas tecnologias e formas de resolver problemas que questionem o status quo;</li>
<li>Atuação em análise e correção de incidentes em ambientes de produção;</li>
<li>Participação ativa nos chapters e ritos dos times e squads;</li>
<li>Discussões técnicas de melhoria de performance e novas tecnologias.</li>
</ul>
<p></p>
<p><strong>Vem com a gente se você é uma pessoa com:</strong></p>
<p>Habilidade de entender os problemas e procurar soluções;</p>
<p>Curiosidade e motivação para se manter atualizado com novas tecnologias de mercado e identificar se estas podem ser incorporadas à solução;</p>
<p>Relacional, interesse e motivação para se comunicar entre squads e clientes;</p>
<p>Interesse por trabalhar tanto em projetos estruturantes de longo prazo como em resolução de incidentes.</p>
<p></p>
<p>Local de Trabalho: Estamos de mudança para Barueri, mas adotamos o Remote First e você é livre para trabalhar de qualquer lugar!</p>
## ClearSale:
<p>A ClearSale (CLSA3) é referência em inteligência de dados com múltiplas soluções para prevenção a riscos em diferentes mercados, como e-commerce, mercado financeiro, vendas diretas, telecomunicações, entre outros. É a empresa que mais conhece o comportamento do consumidor digital brasileiro, o que a faz impulsionar negócios em todo o ecossistema da economia digital.</p>
<p>Por meio do seu time de especialistas, a ClearSale tem o propósito de gerar um efeito de rede de proteção no mercado digital, identificando padrões de ataques, protegendo os mais variados segmentos de negócio e promovendo impacto positivo, para garantir a melhor experiência ao usuário, com mínima fricção, do onboarding ao transacional.</p><a href='https://coodesh.com/empresas/clearsale'>Veja mais no site</a>
## Habilidades:
- Python
- Web Services
- Microsserviços
## Local:
100% Remoto
## Requisitos:
- Ensino superior completo nas áreas de computação ou conhecimento comprovado em experiências profissionais anteriores sólidas;
- Conhecimento em Python;
- Conhecimento em Web Services (Flask ou Django ou FastApi ou equivalentes);
- Conhecimento em Microsserviços;
- Conhecimento em monitoramento e alarmes de microsserviços;
- Ter atuado com a utilização de metodologias ágeis;
- Ter atuado com utilização de ambientes de Cloud (Azure ou AWS ou GCP);
- Conhecimento em banco de dados de documentos (MongoDB ou CosmosDB ou DynamoDB ou equivalentes);
- Conhecimento de Orientação a Objetos, Design Patterns e Arquitetura de Software.
## Diferenciais:
- Conhecimento e utilização de Kubernetes e Docker;
- Utilização da plataforma Azure Devops e Cloud Azure;
- Visão e planejamento estratégico com foco no negócio;
- Conhecimento em programação funcional.
## Benefícios:
- PLR (Participação nos Lucros e Resultados);
- Vale Refeição ou Vale Alimentação;
- Auxílio Creche para crianças até 4 anos e 11 meses;
- Seguro de Vida;
- Gympass;
- Sesc;
- Cartão Multibenefícios Alelo – (com desconto na compra de diversos itens na rede credenciada, incluindo medicamentos em diversas redes de farmácias);
- Assistência Médica e Odontológica Bradesco;
- Atualmente estamos em home office, e a empresa fornece todos os equipamentos necessários;
- Política Educacional para Graduação e Pós-graduação;
- Programa eu Saudável (Acompanhamento de saúde e bem-estar);
- Programa Primeiros Laços (Acompanhamento Gestacional);
- Consultas médicas remotas;
- Palestras de desenvolvimento pessoal e profissional.
## Como se candidatar:
Candidatar-se exclusivamente através da plataforma Coodesh no link a seguir: [Python Developer na ClearSale](https://coodesh.com/vagas/pessoa-desenvolvedora-python-pleno-100percent-remoto-174847023?utm_source=github&utm_medium=devssa-onde-codar-em-salvador&modal=open)
Após candidatar-se via plataforma Coodesh e validar o seu login, você poderá acompanhar e receber todas as interações do processo por lá. Utilize a opção **Pedir Feedback** entre uma etapa e outra na vaga que se candidatou. Isso fará com que a pessoa **Recruiter** responsável pelo processo na empresa receba a notificação.
## Labels
#### Alocação
Remoto
#### Regime
CLT
#### Categoria
Back-End | 1.0 | [Remoto] Python Developer na Coodesh - ## Descrição da vaga:
Esta é uma vaga de um parceiro da plataforma Coodesh, ao candidatar-se você terá acesso as informações completas sobre a empresa e benefícios.
Fique atento ao redirecionamento que vai te levar para uma url [https://coodesh.com](https://coodesh.com/vagas/pessoa-desenvolvedora-python-pleno-100percent-remoto-174847023?utm_source=github&utm_medium=devssa-onde-codar-em-salvador&modal=open) com o pop-up personalizado de candidatura. 👋
<p>A <strong>ClearSale</strong> está em busca de <strong><ins>Python Developer</ins></strong> para compor seu time!</p>
<p>A Diretoria do TechLabs é a área de tecnologia da ClearSale que atua no mercado de onboarding digital voltado a identificação de fraudes e criação de processos seguros e com experiência sem atrito - frictionless.</p>
<p></p>
<p><strong>Responsabilidades: </strong></p>
<ul>
<li>Desenvolvimento de API's em Python;</li>
<li>Implementação de modelos criados de machine learning na área de visão computacional e processamento de documentos;</li>
<li>Experimentar novas tecnologias e formas de resolver problemas que questionem o status quo;</li>
<li>Atuação em análise e correção de incidentes em ambientes de produção;</li>
<li>Participação ativa nos chapters e ritos dos times e squads;</li>
<li>Discussões técnicas de melhoria de performance e novas tecnologias.</li>
</ul>
<p></p>
<p><strong>Vem com a gente se você é uma pessoa com:</strong></p>
<p>Habilidade de entender os problemas e procurar soluções;</p>
<p>Curiosidade e motivação para se manter atualizado com novas tecnologias de mercado e identificar se estas podem ser incorporadas à solução;</p>
<p>Relacional, interesse e motivação para se comunicar entre squads e clientes;</p>
<p>Interesse por trabalhar tanto em projetos estruturantes de longo prazo como em resolução de incidentes.</p>
<p></p>
<p>Local de Trabalho: Estamos de mudança para Barueri, mas adotamos o Remote First e você é livre para trabalhar de qualquer lugar!</p>
## ClearSale:
<p>A ClearSale (CLSA3) é referência em inteligência de dados com múltiplas soluções para prevenção a riscos em diferentes mercados, como e-commerce, mercado financeiro, vendas diretas, telecomunicações, entre outros. É a empresa que mais conhece o comportamento do consumidor digital brasileiro, o que a faz impulsionar negócios em todo o ecossistema da economia digital.</p>
<p>Por meio do seu time de especialistas, a ClearSale tem o propósito de gerar um efeito de rede de proteção no mercado digital, identificando padrões de ataques, protegendo os mais variados segmentos de negócio e promovendo impacto positivo, para garantir a melhor experiência ao usuário, com mínima fricção, do onboarding ao transacional.</p><a href='https://coodesh.com/empresas/clearsale'>Veja mais no site</a>
## Habilidades:
- Python
- Web Services
- Microsserviços
## Local:
100% Remoto
## Requisitos:
- Ensino superior completo nas áreas de computação ou conhecimento comprovado em experiências profissionais anteriores sólidas;
- Conhecimento em Python;
- Conhecimento em Web Services (Flask ou Django ou FastApi ou equivalentes);
- Conhecimento em Microsserviços;
- Conhecimento em monitoramento e alarmes de microsserviços;
- Ter atuado com a utilização de metodologias ágeis;
- Ter atuado com utilização de ambientes de Cloud (Azure ou AWS ou GCP);
- Conhecimento em banco de dados de documentos (MongoDB ou CosmosDB ou DynamoDB ou equivalentes);
- Conhecimento de Orientação a Objetos, Design Patterns e Arquitetura de Software.
## Diferenciais:
- Conhecimento e utilização de Kubernetes e Docker;
- Utilização da plataforma Azure Devops e Cloud Azure;
- Visão e planejamento estratégico com foco no negócio;
- Conhecimento em programação funcional.
## Benefícios:
- PLR (Participação nos Lucros e Resultados);
- Vale Refeição ou Vale Alimentação;
- Auxílio Creche para crianças até 4 anos e 11 meses;
- Seguro de Vida;
- Gympass;
- Sesc;
- Cartão Multibenefícios Alelo – (com desconto na compra de diversos itens na rede credenciada, incluindo medicamentos em diversas redes de farmácias);
- Assistência Médica e Odontológica Bradesco;
- Atualmente estamos em home office, e a empresa fornece todos os equipamentos necessários;
- Política Educacional para Graduação e Pós-graduação;
- Programa eu Saudável (Acompanhamento de saúde e bem-estar);
- Programa Primeiros Laços (Acompanhamento Gestacional);
- Consultas médicas remotas;
- Palestras de desenvolvimento pessoal e profissional.
## Como se candidatar:
Candidatar-se exclusivamente através da plataforma Coodesh no link a seguir: [Python Developer na ClearSale](https://coodesh.com/vagas/pessoa-desenvolvedora-python-pleno-100percent-remoto-174847023?utm_source=github&utm_medium=devssa-onde-codar-em-salvador&modal=open)
Após candidatar-se via plataforma Coodesh e validar o seu login, você poderá acompanhar e receber todas as interações do processo por lá. Utilize a opção **Pedir Feedback** entre uma etapa e outra na vaga que se candidatou. Isso fará com que a pessoa **Recruiter** responsável pelo processo na empresa receba a notificação.
## Labels
#### Alocação
Remoto
#### Regime
CLT
#### Categoria
Back-End | non_priority | python developer na coodesh descrição da vaga esta é uma vaga de um parceiro da plataforma coodesh ao candidatar se você terá acesso as informações completas sobre a empresa e benefícios fique atento ao redirecionamento que vai te levar para uma url com o pop up personalizado de candidatura 👋 a clearsale está em busca de python developer para compor seu time a diretoria do techlabs é a área de tecnologia da clearsale que atua no mercado de onboarding digital voltado a identificação de fraudes e criação de processos seguros e com experiência sem atrito frictionless responsabilidades desenvolvimento de api s em python implementação de modelos criados de machine learning na área de visão computacional e processamento de documentos experimentar novas tecnologias e formas de resolver problemas que questionem o status quo atuação em análise e correção de incidentes em ambientes de produção participação ativa nos chapters e ritos dos times e squads discussões técnicas de melhoria de performance e novas tecnologias vem com a gente se você é uma pessoa com habilidade de entender os problemas e procurar soluções curiosidade e motivação para se manter atualizado com novas tecnologias de mercado e identificar se estas podem ser incorporadas à solução relacional interesse e motivação para se comunicar entre squads e clientes interesse por trabalhar tanto em projetos estruturantes de longo prazo como em resolução de incidentes local de trabalho estamos de mudança para barueri mas adotamos o remote first e você é livre para trabalhar de qualquer lugar clearsale a clearsale é referência em inteligência de dados com múltiplas soluções para prevenção a riscos em diferentes mercados como e commerce mercado financeiro vendas diretas telecomunicações entre outros é a empresa que mais conhece o comportamento do consumidor digital brasileiro o que a faz impulsionar negócios em todo o ecossistema da economia digital por meio do seu time de especialistas a clearsale tem o propósito de gerar um efeito de rede de proteção no mercado digital identificando padrões de ataques protegendo os mais variados segmentos de negócio e promovendo impacto positivo para garantir a melhor experiência ao usuário com mínima fricção do onboarding ao transacional habilidades python web services microsserviços local remoto requisitos ensino superior completo nas áreas de computação ou conhecimento comprovado em experiências profissionais anteriores sólidas conhecimento em python conhecimento em web services flask ou django ou fastapi ou equivalentes conhecimento em microsserviços conhecimento em monitoramento e alarmes de microsserviços ter atuado com a utilização de metodologias ágeis ter atuado com utilização de ambientes de cloud azure ou aws ou gcp conhecimento em banco de dados de documentos mongodb ou cosmosdb ou dynamodb ou equivalentes conhecimento de orientação a objetos design patterns e arquitetura de software diferenciais conhecimento e utilização de kubernetes e docker utilização da plataforma azure devops e cloud azure visão e planejamento estratégico com foco no negócio conhecimento em programação funcional benefícios plr participação nos lucros e resultados vale refeição ou vale alimentação auxílio creche para crianças até anos e meses seguro de vida gympass sesc cartão multibenefícios alelo – com desconto na compra de diversos itens na rede credenciada incluindo medicamentos em diversas redes de farmácias assistência médica e odontológica bradesco atualmente estamos em home office e a empresa fornece todos os equipamentos necessários política educacional para graduação e pós graduação programa eu saudável acompanhamento de saúde e bem estar programa primeiros laços acompanhamento gestacional consultas médicas remotas palestras de desenvolvimento pessoal e profissional como se candidatar candidatar se exclusivamente através da plataforma coodesh no link a seguir após candidatar se via plataforma coodesh e validar o seu login você poderá acompanhar e receber todas as interações do processo por lá utilize a opção pedir feedback entre uma etapa e outra na vaga que se candidatou isso fará com que a pessoa recruiter responsável pelo processo na empresa receba a notificação labels alocação remoto regime clt categoria back end | 0 |
116,354 | 17,364,769,106 | IssuesEvent | 2021-07-30 05:05:32 | artsking/sqlite3 | https://api.github.com/repos/artsking/sqlite3 | opened | CVE-2017-13685 (Medium) detected in sqliteversion-3.22.0 | security vulnerability | ## CVE-2017-13685 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>sqliteversion-3.22.0</b></p></summary>
<p>
<p>Official Git mirror of the SQLite source tree</p>
<p>Library home page: <a href=https://github.com/sqlite/sqlite.git>https://github.com/sqlite/sqlite.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/artsking/sqlite3/commit/8feba61bbe735481dcb48cb4626c2026d4b5e02a">8feba61bbe735481dcb48cb4626c2026d4b5e02a</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>sqlite3/ext/misc/dbdump.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The dump_callback function in SQLite 3.20.0 allows remote attackers to cause a denial of service (EXC_BAD_ACCESS and application crash) via a crafted file.
<p>Publish Date: 2017-08-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-13685>CVE-2017-13685</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://security-tracker.debian.org/tracker/CVE-2017-13685">https://security-tracker.debian.org/tracker/CVE-2017-13685</a></p>
<p>Release Date: 2017-08-29</p>
<p>Fix Resolution: 3.20.1</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-2017-13685 (Medium) detected in sqliteversion-3.22.0 - ## CVE-2017-13685 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>sqliteversion-3.22.0</b></p></summary>
<p>
<p>Official Git mirror of the SQLite source tree</p>
<p>Library home page: <a href=https://github.com/sqlite/sqlite.git>https://github.com/sqlite/sqlite.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/artsking/sqlite3/commit/8feba61bbe735481dcb48cb4626c2026d4b5e02a">8feba61bbe735481dcb48cb4626c2026d4b5e02a</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>sqlite3/ext/misc/dbdump.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The dump_callback function in SQLite 3.20.0 allows remote attackers to cause a denial of service (EXC_BAD_ACCESS and application crash) via a crafted file.
<p>Publish Date: 2017-08-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-13685>CVE-2017-13685</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://security-tracker.debian.org/tracker/CVE-2017-13685">https://security-tracker.debian.org/tracker/CVE-2017-13685</a></p>
<p>Release Date: 2017-08-29</p>
<p>Fix Resolution: 3.20.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in sqliteversion cve medium severity vulnerability vulnerable library sqliteversion official git mirror of the sqlite source tree library home page a href found in head commit a href found in base branch master vulnerable source files ext misc dbdump c vulnerability details the dump callback function in sqlite allows remote attackers to cause a denial of service exc bad access and application crash via a crafted file publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
326,527 | 27,998,024,619 | IssuesEvent | 2023-03-27 09:47:16 | Jersey-Electricity-plc/intsys-issues | https://api.github.com/repos/Jersey-Electricity-plc/intsys-issues | closed | Power BI Report Error Checks | enhancement readyToTest | From #22
Timesheet Check for errors does show if a "Department Code" is missing when J1007 is used but Power BI does not. | 1.0 | Power BI Report Error Checks - From #22
Timesheet Check for errors does show if a "Department Code" is missing when J1007 is used but Power BI does not. | non_priority | power bi report error checks from timesheet check for errors does show if a department code is missing when is used but power bi does not | 0 |
51,083 | 13,188,092,348 | IssuesEvent | 2020-08-13 05:32:00 | icecube-trac/tix3 | https://api.github.com/repos/icecube-trac/tix3 | closed | [simulation] error in MC afterprocessing (MCPulseSeriesParticleIDMap) (Trac #1942) | Migrated from Trac combo simulation defect | I was again on the search for simulation of some MCstudies, for which I need the complete I3MCPulse-info (MCPulseMap, ParticleIDMap and I3MCTRee); It took me some while to locate an appropriate one, which I found in dataset 11843 resp. 11642 (IC86:2013 GENIE simulation), one of the latest produced datasets
This dataset was produced with icesim.V04-01-11-G4C (whatever this means). All other datasets I found which are produced with an olderor similar release candidate (icesim.V04-01-11) have the necessary objects, but the after-processing for Noise-MCPulses is flawed: there are no entries in the ParticleIDMap for those pulses as originated from ParticleID(0,0)
This can be identified by inspecting the I3MCPulseSeriesParticleIDMap in the frame finding no entries for the major/minor-ID(0,0) and in general a lot of entries with only a single OMKey as key and an empty vector for the value in this I3Map<OMKey, vector<...> >
So whatever is the difference between these meta-releases, somebody should have a look into that the after-processing is done correctly, otherwise MC-information is permanently lost!
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/ticket/1942">https://code.icecube.wisc.edu/ticket/1942</a>, reported by mzoll and owned by juancarlos</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2017-02-21T17:32:43",
"description": "I was again on the search for simulation of some MCstudies, for which I need the complete I3MCPulse-info (MCPulseMap, ParticleIDMap and I3MCTRee); It took me some while to locate an appropriate one, which I found in dataset 11843 resp. 11642 (IC86:2013 GENIE simulation), one of the latest produced datasets\n\nThis dataset was produced with icesim.V04-01-11-G4C (whatever this means). All other datasets I found which are produced with an olderor similar release candidate (icesim.V04-01-11) have the necessary objects, but the after-processing for Noise-MCPulses is flawed: there are no entries in the ParticleIDMap for those pulses as originated from ParticleID(0,0)\n\nThis can be identified by inspecting the I3MCPulseSeriesParticleIDMap in the frame finding no entries for the major/minor-ID(0,0) and in general a lot of entries with only a single OMKey as key and an empty vector for the value in this I3Map<OMKey, vector<...> >\n\nSo whatever is the difference between these meta-releases, somebody should have a look into that the after-processing is done correctly, otherwise MC-information is permanently lost!",
"reporter": "mzoll",
"cc": "olivas, cweaver",
"resolution": "fixed",
"_ts": "1487698363713061",
"component": "combo simulation",
"summary": "[simulation] error in MC afterprocessing (MCPulseSeriesParticleIDMap)",
"priority": "critical",
"keywords": "MC simulation MCPulse",
"time": "2017-01-26T09:02:15",
"milestone": "",
"owner": "juancarlos",
"type": "defect"
}
```
</p>
</details>
| 1.0 | [simulation] error in MC afterprocessing (MCPulseSeriesParticleIDMap) (Trac #1942) - I was again on the search for simulation of some MCstudies, for which I need the complete I3MCPulse-info (MCPulseMap, ParticleIDMap and I3MCTRee); It took me some while to locate an appropriate one, which I found in dataset 11843 resp. 11642 (IC86:2013 GENIE simulation), one of the latest produced datasets
This dataset was produced with icesim.V04-01-11-G4C (whatever this means). All other datasets I found which are produced with an olderor similar release candidate (icesim.V04-01-11) have the necessary objects, but the after-processing for Noise-MCPulses is flawed: there are no entries in the ParticleIDMap for those pulses as originated from ParticleID(0,0)
This can be identified by inspecting the I3MCPulseSeriesParticleIDMap in the frame finding no entries for the major/minor-ID(0,0) and in general a lot of entries with only a single OMKey as key and an empty vector for the value in this I3Map<OMKey, vector<...> >
So whatever is the difference between these meta-releases, somebody should have a look into that the after-processing is done correctly, otherwise MC-information is permanently lost!
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/ticket/1942">https://code.icecube.wisc.edu/ticket/1942</a>, reported by mzoll and owned by juancarlos</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2017-02-21T17:32:43",
"description": "I was again on the search for simulation of some MCstudies, for which I need the complete I3MCPulse-info (MCPulseMap, ParticleIDMap and I3MCTRee); It took me some while to locate an appropriate one, which I found in dataset 11843 resp. 11642 (IC86:2013 GENIE simulation), one of the latest produced datasets\n\nThis dataset was produced with icesim.V04-01-11-G4C (whatever this means). All other datasets I found which are produced with an olderor similar release candidate (icesim.V04-01-11) have the necessary objects, but the after-processing for Noise-MCPulses is flawed: there are no entries in the ParticleIDMap for those pulses as originated from ParticleID(0,0)\n\nThis can be identified by inspecting the I3MCPulseSeriesParticleIDMap in the frame finding no entries for the major/minor-ID(0,0) and in general a lot of entries with only a single OMKey as key and an empty vector for the value in this I3Map<OMKey, vector<...> >\n\nSo whatever is the difference between these meta-releases, somebody should have a look into that the after-processing is done correctly, otherwise MC-information is permanently lost!",
"reporter": "mzoll",
"cc": "olivas, cweaver",
"resolution": "fixed",
"_ts": "1487698363713061",
"component": "combo simulation",
"summary": "[simulation] error in MC afterprocessing (MCPulseSeriesParticleIDMap)",
"priority": "critical",
"keywords": "MC simulation MCPulse",
"time": "2017-01-26T09:02:15",
"milestone": "",
"owner": "juancarlos",
"type": "defect"
}
```
</p>
</details>
| non_priority | error in mc afterprocessing mcpulseseriesparticleidmap trac i was again on the search for simulation of some mcstudies for which i need the complete info mcpulsemap particleidmap and it took me some while to locate an appropriate one which i found in dataset resp genie simulation one of the latest produced datasets this dataset was produced with icesim whatever this means all other datasets i found which are produced with an olderor similar release candidate icesim have the necessary objects but the after processing for noise mcpulses is flawed there are no entries in the particleidmap for those pulses as originated from particleid this can be identified by inspecting the in the frame finding no entries for the major minor id and in general a lot of entries with only a single omkey as key and an empty vector for the value in this so whatever is the difference between these meta releases somebody should have a look into that the after processing is done correctly otherwise mc information is permanently lost migrated from json status closed changetime description i was again on the search for simulation of some mcstudies for which i need the complete info mcpulsemap particleidmap and it took me some while to locate an appropriate one which i found in dataset resp genie simulation one of the latest produced datasets n nthis dataset was produced with icesim whatever this means all other datasets i found which are produced with an olderor similar release candidate icesim have the necessary objects but the after processing for noise mcpulses is flawed there are no entries in the particleidmap for those pulses as originated from particleid n nthis can be identified by inspecting the in the frame finding no entries for the major minor id and in general a lot of entries with only a single omkey as key and an empty vector for the value in this n nso whatever is the difference between these meta releases somebody should have a look into that the after processing is done correctly otherwise mc information is permanently lost reporter mzoll cc olivas cweaver resolution fixed ts component combo simulation summary error in mc afterprocessing mcpulseseriesparticleidmap priority critical keywords mc simulation mcpulse time milestone owner juancarlos type defect | 0 |
231,418 | 18,766,073,995 | IssuesEvent | 2021-11-06 00:43:20 | elastic/kibana | https://api.github.com/repos/elastic/kibana | opened | Failing test: Jest Tests.x-pack/plugins/security_solution/public/management/pages/event_filters/view - When on the Event Filters List Page And data exists should show modal when delete is clicked on a card | failed-test | A test failed on a tracked branch
```
Error: thrown: "Exceeded timeout of 5000 ms for a test.
Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."
at /opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/x-pack/plugins/security_solution/public/management/pages/event_filters/view/event_filters_list_page.test.tsx:139:5
at _dispatchDescribe (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:67:26)
at describe (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:30:5)
at /opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/x-pack/plugins/security_solution/public/management/pages/event_filters/view/event_filters_list_page.test.tsx:84:3
at _dispatchDescribe (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:67:26)
at describe (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:30:5)
at Object.<anonymous> (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/x-pack/plugins/security_solution/public/management/pages/event_filters/view/event_filters_list_page.test.tsx:19:1)
at Runtime._execModule (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-runtime/build/index.js:1299:24)
at Runtime._loadModule (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-runtime/build/index.js:898:12)
at Runtime.requireModule (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-runtime/build/index.js:746:10)
at jestAdapter (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:106:13)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at runTestInternal (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/runTest.js:380:16)
at runTest (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/runTest.js:472:34)
at Object.worker (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/testWorker.js:133:12)
```
First failure: [CI Build - 7.16](https://buildkite.com/elastic/kibana-hourly/builds/2682#8260c17e-c430-4ec2-95a6-c17bef765d2c)
<!-- kibanaCiData = {"failed-test":{"test.class":"Jest Tests.x-pack/plugins/security_solution/public/management/pages/event_filters/view","test.name":"When on the Event Filters List Page And data exists should show modal when delete is clicked on a card","test.failCount":1}} --> | 1.0 | Failing test: Jest Tests.x-pack/plugins/security_solution/public/management/pages/event_filters/view - When on the Event Filters List Page And data exists should show modal when delete is clicked on a card - A test failed on a tracked branch
```
Error: thrown: "Exceeded timeout of 5000 ms for a test.
Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."
at /opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/x-pack/plugins/security_solution/public/management/pages/event_filters/view/event_filters_list_page.test.tsx:139:5
at _dispatchDescribe (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:67:26)
at describe (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:30:5)
at /opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/x-pack/plugins/security_solution/public/management/pages/event_filters/view/event_filters_list_page.test.tsx:84:3
at _dispatchDescribe (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:67:26)
at describe (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:30:5)
at Object.<anonymous> (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/x-pack/plugins/security_solution/public/management/pages/event_filters/view/event_filters_list_page.test.tsx:19:1)
at Runtime._execModule (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-runtime/build/index.js:1299:24)
at Runtime._loadModule (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-runtime/build/index.js:898:12)
at Runtime.requireModule (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-runtime/build/index.js:746:10)
at jestAdapter (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:106:13)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at runTestInternal (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/runTest.js:380:16)
at runTest (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/runTest.js:472:34)
at Object.worker (/opt/local-ssd/buildkite/builds/kb-c2-16-e978b8db8a38a0ac/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/testWorker.js:133:12)
```
First failure: [CI Build - 7.16](https://buildkite.com/elastic/kibana-hourly/builds/2682#8260c17e-c430-4ec2-95a6-c17bef765d2c)
<!-- kibanaCiData = {"failed-test":{"test.class":"Jest Tests.x-pack/plugins/security_solution/public/management/pages/event_filters/view","test.name":"When on the Event Filters List Page And data exists should show modal when delete is clicked on a card","test.failCount":1}} --> | non_priority | failing test jest tests x pack plugins security solution public management pages event filters view when on the event filters list page and data exists should show modal when delete is clicked on a card a test failed on a tracked branch error thrown exceeded timeout of ms for a test use jest settimeout newtimeout to increase the timeout value if this is a long running test at opt local ssd buildkite builds kb elastic kibana hourly kibana x pack plugins security solution public management pages event filters view event filters list page test tsx at dispatchdescribe opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build index js at describe opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build index js at opt local ssd buildkite builds kb elastic kibana hourly kibana x pack plugins security solution public management pages event filters view event filters list page test tsx at dispatchdescribe opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build index js at describe opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build index js at object opt local ssd buildkite builds kb elastic kibana hourly kibana x pack plugins security solution public management pages event filters view event filters list page test tsx at runtime execmodule opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest runtime build index js at runtime loadmodule opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest runtime build index js at runtime requiremodule opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest runtime build index js at jestadapter opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build legacy code todo rewrite jestadapter js at processticksandrejections node internal process task queues at runtestinternal opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest runner build runtest js at runtest opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest runner build runtest js at object worker opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest runner build testworker js first failure | 0 |
2,995 | 5,890,926,443 | IssuesEvent | 2017-05-17 15:54:39 | AdguardTeam/AdguardForWindows | https://api.github.com/repos/AdguardTeam/AdguardForWindows | closed | Adguard cannot filter Edge https traffic when TCP Fast Open is turned ON | Bug Compatibility | Critical issue, must be fixed asap.
https://forum.adguard.com/index.php?threads/adguard-6-0-226-1108-in-ms-edge-didnt-block-youtube-ads.10316/
https://forum.adguard.com/index.php?threads/windows-10-build-14342-%D0%B8-adguard-6-0-226-1108.10299/
**EDIT:**
Partially resolved:
https://github.com/AdguardTeam/AdguardForWindows/issues/1093#issuecomment-224735132
| True | Adguard cannot filter Edge https traffic when TCP Fast Open is turned ON - Critical issue, must be fixed asap.
https://forum.adguard.com/index.php?threads/adguard-6-0-226-1108-in-ms-edge-didnt-block-youtube-ads.10316/
https://forum.adguard.com/index.php?threads/windows-10-build-14342-%D0%B8-adguard-6-0-226-1108.10299/
**EDIT:**
Partially resolved:
https://github.com/AdguardTeam/AdguardForWindows/issues/1093#issuecomment-224735132
| non_priority | adguard cannot filter edge https traffic when tcp fast open is turned on critical issue must be fixed asap edit partially resolved | 0 |
228,358 | 18,172,000,553 | IssuesEvent | 2021-09-27 21:09:59 | flutter/flutter | https://api.github.com/repos/flutter/flutter | opened | Test Engine custom toolchain support on CI | a: tests engine e: embedder P4 | We should test on CI that building the Engine with a custom toolchain and sysroot continue to work (that is, that the gn and ninja steps here https://medium.com/flutter/flutter-on-raspberry-pi-mostly-from-scratch-2824c5e7dcb1 continue to work). One way to do that might be to use the Linux clang toolchain we already pull and use it to build a libflutter_engine.so for armv7. | 1.0 | Test Engine custom toolchain support on CI - We should test on CI that building the Engine with a custom toolchain and sysroot continue to work (that is, that the gn and ninja steps here https://medium.com/flutter/flutter-on-raspberry-pi-mostly-from-scratch-2824c5e7dcb1 continue to work). One way to do that might be to use the Linux clang toolchain we already pull and use it to build a libflutter_engine.so for armv7. | non_priority | test engine custom toolchain support on ci we should test on ci that building the engine with a custom toolchain and sysroot continue to work that is that the gn and ninja steps here continue to work one way to do that might be to use the linux clang toolchain we already pull and use it to build a libflutter engine so for | 0 |
22,221 | 3,941,872,003 | IssuesEvent | 2016-04-27 09:35:31 | Microsoft/vscode | https://api.github.com/repos/Microsoft/vscode | closed | Verify telemetry | testplan-item | @isidorn
* [ ] any os
The telemetry services have been refactored. Verify that
* error telemetry shows extension errors
* error telemetry shows vscode errors
* error telemetry contains no PII
* data telemetry works | 1.0 | Verify telemetry - @isidorn
* [ ] any os
The telemetry services have been refactored. Verify that
* error telemetry shows extension errors
* error telemetry shows vscode errors
* error telemetry contains no PII
* data telemetry works | non_priority | verify telemetry isidorn any os the telemetry services have been refactored verify that error telemetry shows extension errors error telemetry shows vscode errors error telemetry contains no pii data telemetry works | 0 |
133,124 | 12,532,430,000 | IssuesEvent | 2020-06-04 15:56:25 | flutter/flutter | https://api.github.com/repos/flutter/flutter | opened | path_provider mock example needs to be updated | d: cookbook documentation | https://flutter.dev/docs/cookbook/persistence/reading-writing-files#testing demonstrates mocking the method channel for path provider, but not all path provider implementations use a method channel (notably, `path_provider_linux`; see [discussion](https://github.com/flutter/plugins/pull/2789#issuecomment-638929577))
Instead it should be showing mocking out the platform provider, as is done [here](https://github.com/flutter/plugins/blob/master/packages/path_provider/path_provider/test/path_provider_test.dart), since that's the recommended way of mocking out plugins that are using the new platform interface structure. | 1.0 | path_provider mock example needs to be updated - https://flutter.dev/docs/cookbook/persistence/reading-writing-files#testing demonstrates mocking the method channel for path provider, but not all path provider implementations use a method channel (notably, `path_provider_linux`; see [discussion](https://github.com/flutter/plugins/pull/2789#issuecomment-638929577))
Instead it should be showing mocking out the platform provider, as is done [here](https://github.com/flutter/plugins/blob/master/packages/path_provider/path_provider/test/path_provider_test.dart), since that's the recommended way of mocking out plugins that are using the new platform interface structure. | non_priority | path provider mock example needs to be updated demonstrates mocking the method channel for path provider but not all path provider implementations use a method channel notably path provider linux see instead it should be showing mocking out the platform provider as is done since that s the recommended way of mocking out plugins that are using the new platform interface structure | 0 |
120,097 | 17,644,017,627 | IssuesEvent | 2021-08-20 01:28:25 | AkshayMukkavilli/Analyzing-the-Significance-of-Structure-in-Amazon-Review-Data-Using-Machine-Learning-Approaches | https://api.github.com/repos/AkshayMukkavilli/Analyzing-the-Significance-of-Structure-in-Amazon-Review-Data-Using-Machine-Learning-Approaches | opened | CVE-2021-29610 (High) detected in tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl | security vulnerability | ## CVE-2021-29610 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/d2/ea/ab2c8c0e81bd051cc1180b104c75a865ab0fc66c89be992c4b20bbf6d624/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/d2/ea/ab2c8c0e81bd051cc1180b104c75a865ab0fc66c89be992c4b20bbf6d624/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: /FinalProject/requirements.txt</p>
<p>Path to vulnerable library: teSource-ArchiveExtractor_8b9e071c-3b11-4aa9-ba60-cdeb60d053b7/20190525011350_65403/20190525011256_depth_0/9/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64/tensorflow-1.13.1.data/purelib/tensorflow</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl** (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>
TensorFlow is an end-to-end open source platform for machine learning. The validation in `tf.raw_ops.QuantizeAndDequantizeV2` allows invalid values for `axis` argument:. The validation(https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L74-L77) uses `||` to mix two different conditions. If `axis_ < -1` the condition in `OP_REQUIRES` will still be true, but this value of `axis_` results in heap underflow. This allows attackers to read/write to other data on the heap. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
<p>Publish Date: 2021-05-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29610>CVE-2021-29610</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mq5c-prh3-3f3h">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mq5c-prh3-3f3h</a></p>
<p>Release Date: 2021-05-14</p>
<p>Fix Resolution: tensorflow - 2.5.0, tensorflow-cpu - 2.5.0, tensorflow-gpu - 2.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-29610 (High) detected in tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl - ## CVE-2021-29610 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/d2/ea/ab2c8c0e81bd051cc1180b104c75a865ab0fc66c89be992c4b20bbf6d624/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/d2/ea/ab2c8c0e81bd051cc1180b104c75a865ab0fc66c89be992c4b20bbf6d624/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: /FinalProject/requirements.txt</p>
<p>Path to vulnerable library: teSource-ArchiveExtractor_8b9e071c-3b11-4aa9-ba60-cdeb60d053b7/20190525011350_65403/20190525011256_depth_0/9/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64/tensorflow-1.13.1.data/purelib/tensorflow</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl** (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>
TensorFlow is an end-to-end open source platform for machine learning. The validation in `tf.raw_ops.QuantizeAndDequantizeV2` allows invalid values for `axis` argument:. The validation(https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L74-L77) uses `||` to mix two different conditions. If `axis_ < -1` the condition in `OP_REQUIRES` will still be true, but this value of `axis_` results in heap underflow. This allows attackers to read/write to other data on the heap. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
<p>Publish Date: 2021-05-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29610>CVE-2021-29610</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mq5c-prh3-3f3h">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mq5c-prh3-3f3h</a></p>
<p>Release Date: 2021-05-14</p>
<p>Fix Resolution: tensorflow - 2.5.0, tensorflow-cpu - 2.5.0, tensorflow-gpu - 2.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in tensorflow whl cve high severity vulnerability vulnerable library tensorflow whl tensorflow is an open source machine learning framework for everyone library home page a href path to dependency file finalproject requirements txt path to vulnerable library tesource archiveextractor depth tensorflow tensorflow data purelib tensorflow dependency hierarchy x tensorflow whl vulnerable library vulnerability details tensorflow is an end to end open source platform for machine learning the validation in tf raw ops allows invalid values for axis argument the validation uses to mix two different conditions if axis the condition in op requires will still be true but this value of axis results in heap underflow this allows attackers to read write to other data on the heap the fix will be included in tensorflow we will also cherrypick this commit on tensorflow tensorflow tensorflow and tensorflow as these are also affected and still in supported range publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact 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 tensorflow tensorflow cpu tensorflow gpu step up your open source security game with whitesource | 0 |
77,641 | 27,090,399,244 | IssuesEvent | 2023-02-14 20:31:25 | bigbluebutton/bigbluebutton | https://api.github.com/repos/bigbluebutton/bigbluebutton | closed | RTL Tools > Text Issue | type: defect target: localization component: whiteboard module: client status: stale | <!--PLEASE DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS.
This issue tracker is only for bbb development related issues.-->
**Describe the bug**
When i use `Tools > Text` in RTL language like Persian, after enter text the text goes to the left side. Actually RTL mean Right To Left so it would be goes to the right side instead of left side.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to Tools
2. Click on Text
3. Type something in Persian (or any RTL language)
**Expected behavior**
I expect after typing done it is stay in right side.
**Actual behavior**
After typing done the text will be go to left side of text box.
**Screenshots**
**Desktop:**
- OS: Linux x64_86
- Browser Firefox
- Version 68.9.0esr
**Additional context**
Add any other context about the problem here.
| 1.0 | RTL Tools > Text Issue - <!--PLEASE DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS.
This issue tracker is only for bbb development related issues.-->
**Describe the bug**
When i use `Tools > Text` in RTL language like Persian, after enter text the text goes to the left side. Actually RTL mean Right To Left so it would be goes to the right side instead of left side.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to Tools
2. Click on Text
3. Type something in Persian (or any RTL language)
**Expected behavior**
I expect after typing done it is stay in right side.
**Actual behavior**
After typing done the text will be go to left side of text box.
**Screenshots**
**Desktop:**
- OS: Linux x64_86
- Browser Firefox
- Version 68.9.0esr
**Additional context**
Add any other context about the problem here.
| non_priority | rtl tools text issue please do not file issues for general support questions this issue tracker is only for bbb development related issues describe the bug when i use tools text in rtl language like persian after enter text the text goes to the left side actually rtl mean right to left so it would be goes to the right side instead of left side to reproduce steps to reproduce the behavior go to tools click on text type something in persian or any rtl language expected behavior i expect after typing done it is stay in right side actual behavior after typing done the text will be go to left side of text box screenshots desktop os linux browser firefox version additional context add any other context about the problem here | 0 |
89,713 | 8,212,559,622 | IssuesEvent | 2018-09-04 16:41:55 | saltstack/salt | https://api.github.com/repos/saltstack/salt | closed | memusage beacon isn't working properly with states.beacon.present | Beacon Bug Core Has Testcase High Severity P4 State Module stale | ### Description of Issue/Question
If I follow the documentation for this beacon and put the snippet in `/etc/salt/minion.d/beacons.conf`:
```
beacons:
memusage:
- percent: 63%
```
The beacons works fine. However, I prefer using the state configuration, and hence I did put in my `bootstrap.sls` state the following:
```
beacons_fun:
beacon.present:
- enable: True
- name: load
- 1m:
- 0.0
- 2.0
- 5m:
- 0.0
- 1.5
- 15m:
- 0.1
- 1.0
# beacons no fun, this won't work
memusage:
beacon.present:
- percent: 3%
```
After running the state I see the following on the master:
```
# salt "mi*1*" beacons.list
minion1.local:
beacons:
load:
15m:
- 0.1
- 1.0
1m:
- 0.0
- 2.0
5m:
- 0.0
- 1.5
enable: true
memusage:
enable: true
percent:
- 3%
```
Which seems fine, but the logs on the minion show:
```
2017-01-24 09:48:08,475 [salt.loaded.int.beacons.load][DEBUG ][30134] Emit because 0.04 < 0.1 or > 1.0
2017-01-24 09:48:08,476 [salt.minion ][CRITICAL][30134] The beacon errored:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/salt/minion.py", line 2153, in handle_beacons
beacons = self.process_beacons(self.functions)
File "/usr/lib/python2.7/dist-packages/salt/minion.py", line 409, in process_beacons
return self.beacons.process(b_conf, self.opts['grains']) # pylint: disable=no-member
File "/usr/lib/python2.7/dist-packages/salt/beacons/__init__.py", line 100, in process
raw = self.beacons[fun_str](b_config[mod])
File "/usr/lib/python2.7/dist-packages/salt/beacons/memusage.py", line 64, in beacon
mount = memusage.keys()[0]
AttributeError: 'str' object has no attribute 'keys'
```
So my question is - how do I configure this beacon to work properly within the state?
### Versions Report
```
salt --versions-report
Salt Version:
Salt: 2016.11.1
Dependency Versions:
cffi: Not Installed
cherrypy: Not Installed
dateutil: 2.4.2
gitdb: 0.6.4
gitpython: 1.0.1
ioflo: Not Installed
Jinja2: 2.8
libgit2: Not Installed
libnacl: Not Installed
M2Crypto: Not Installed
Mako: 1.0.3
msgpack-pure: Not Installed
msgpack-python: 0.4.6
mysql-python: Not Installed
pycparser: Not Installed
pycrypto: 2.6.1
pygit2: Not Installed
Python: 2.7.12 (default, Nov 19 2016, 06:48:10)
python-gnupg: Not Installed
PyYAML: 3.11
PyZMQ: 15.2.0
RAET: Not Installed
smmap: 0.9.0
timelib: Not Installed
Tornado: 4.2.1
ZMQ: 4.1.4
System Versions:
dist: Ubuntu 16.04 xenial
machine: x86_64
release: 4.4.0-51-generic
system: Linux
version: Ubuntu 16.04 xenial
``` | 1.0 | memusage beacon isn't working properly with states.beacon.present - ### Description of Issue/Question
If I follow the documentation for this beacon and put the snippet in `/etc/salt/minion.d/beacons.conf`:
```
beacons:
memusage:
- percent: 63%
```
The beacons works fine. However, I prefer using the state configuration, and hence I did put in my `bootstrap.sls` state the following:
```
beacons_fun:
beacon.present:
- enable: True
- name: load
- 1m:
- 0.0
- 2.0
- 5m:
- 0.0
- 1.5
- 15m:
- 0.1
- 1.0
# beacons no fun, this won't work
memusage:
beacon.present:
- percent: 3%
```
After running the state I see the following on the master:
```
# salt "mi*1*" beacons.list
minion1.local:
beacons:
load:
15m:
- 0.1
- 1.0
1m:
- 0.0
- 2.0
5m:
- 0.0
- 1.5
enable: true
memusage:
enable: true
percent:
- 3%
```
Which seems fine, but the logs on the minion show:
```
2017-01-24 09:48:08,475 [salt.loaded.int.beacons.load][DEBUG ][30134] Emit because 0.04 < 0.1 or > 1.0
2017-01-24 09:48:08,476 [salt.minion ][CRITICAL][30134] The beacon errored:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/salt/minion.py", line 2153, in handle_beacons
beacons = self.process_beacons(self.functions)
File "/usr/lib/python2.7/dist-packages/salt/minion.py", line 409, in process_beacons
return self.beacons.process(b_conf, self.opts['grains']) # pylint: disable=no-member
File "/usr/lib/python2.7/dist-packages/salt/beacons/__init__.py", line 100, in process
raw = self.beacons[fun_str](b_config[mod])
File "/usr/lib/python2.7/dist-packages/salt/beacons/memusage.py", line 64, in beacon
mount = memusage.keys()[0]
AttributeError: 'str' object has no attribute 'keys'
```
So my question is - how do I configure this beacon to work properly within the state?
### Versions Report
```
salt --versions-report
Salt Version:
Salt: 2016.11.1
Dependency Versions:
cffi: Not Installed
cherrypy: Not Installed
dateutil: 2.4.2
gitdb: 0.6.4
gitpython: 1.0.1
ioflo: Not Installed
Jinja2: 2.8
libgit2: Not Installed
libnacl: Not Installed
M2Crypto: Not Installed
Mako: 1.0.3
msgpack-pure: Not Installed
msgpack-python: 0.4.6
mysql-python: Not Installed
pycparser: Not Installed
pycrypto: 2.6.1
pygit2: Not Installed
Python: 2.7.12 (default, Nov 19 2016, 06:48:10)
python-gnupg: Not Installed
PyYAML: 3.11
PyZMQ: 15.2.0
RAET: Not Installed
smmap: 0.9.0
timelib: Not Installed
Tornado: 4.2.1
ZMQ: 4.1.4
System Versions:
dist: Ubuntu 16.04 xenial
machine: x86_64
release: 4.4.0-51-generic
system: Linux
version: Ubuntu 16.04 xenial
``` | non_priority | memusage beacon isn t working properly with states beacon present description of issue question if i follow the documentation for this beacon and put the snippet in etc salt minion d beacons conf beacons memusage percent the beacons works fine however i prefer using the state configuration and hence i did put in my bootstrap sls state the following beacons fun beacon present enable true name load beacons no fun this won t work memusage beacon present percent after running the state i see the following on the master salt mi beacons list local beacons load enable true memusage enable true percent which seems fine but the logs on the minion show emit because the beacon errored traceback most recent call last file usr lib dist packages salt minion py line in handle beacons beacons self process beacons self functions file usr lib dist packages salt minion py line in process beacons return self beacons process b conf self opts pylint disable no member file usr lib dist packages salt beacons init py line in process raw self beacons b config file usr lib dist packages salt beacons memusage py line in beacon mount memusage keys attributeerror str object has no attribute keys so my question is how do i configure this beacon to work properly within the state versions report salt versions report salt version salt dependency versions cffi not installed cherrypy not installed dateutil gitdb gitpython ioflo not installed not installed libnacl not installed not installed mako msgpack pure not installed msgpack python mysql python not installed pycparser not installed pycrypto not installed python default nov python gnupg not installed pyyaml pyzmq raet not installed smmap timelib not installed tornado zmq system versions dist ubuntu xenial machine release generic system linux version ubuntu xenial | 0 |
203,401 | 15,365,668,079 | IssuesEvent | 2021-03-02 00:03:20 | addwiki/addwiki | https://api.github.com/repos/addwiki/addwiki | opened | [mediawiki-api-base] Add unit test for MediaWikiApi multipart stuff | test | It broke at some point, and was only covered by an integration test.
It would make it easier to see if things go wrong with a couple of unit tests.
The fix was in https://github.com/addwiki/addwiki/pull/66/commits/a9c73c57e77d42fdf03254e33b7ef78e1898ce65 | 1.0 | [mediawiki-api-base] Add unit test for MediaWikiApi multipart stuff - It broke at some point, and was only covered by an integration test.
It would make it easier to see if things go wrong with a couple of unit tests.
The fix was in https://github.com/addwiki/addwiki/pull/66/commits/a9c73c57e77d42fdf03254e33b7ef78e1898ce65 | non_priority | add unit test for mediawikiapi multipart stuff it broke at some point and was only covered by an integration test it would make it easier to see if things go wrong with a couple of unit tests the fix was in | 0 |
86,317 | 8,031,931,931 | IssuesEvent | 2018-07-28 08:45:21 | godotengine/godot | https://api.github.com/repos/godotengine/godot | closed | Godot Crash on when I try run non-existing function form script that extends another script | bug needs testing topic:gdscript | I have script that extends from node with some code.
When I try execute some non-existing function(because I make mistake) in script that extends first script godot crashes entirely.
First Error message I always get second is crash.
```
OpenGL ES 3.0 Renderer: AMD CARRIZO (DRM 3.23.0 / 4.15.0-041500-generic, LLVM 6.0.0)
ERROR: texture_set_size_override: Condition ' p_width <= 0 || p_width > 16384 ' is true.
At: drivers/gles3/rasterizer_storage_gles3.cpp:1040.
ERROR: operator[]: FATAL: Index p_index=33 out of size (size()=33)
At: core/vector.h:138.
handle_crash: Program crashed with signal 4
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x7fb4bcdf54b0] (??:0)
[2] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0x17d8c77] (??:?)
[3] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0x9e73d8] (<artificial>:?)
[4] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0xa1f4ec] (<artificial>:?)
[5] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0x19c0334] (??:?)
[6] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0xf79ab9] (<artificial>:?)
[7] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0xfe83c7] (??:?)
[8] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0x4c55e8] (??:?)
[9] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0x45411d] (??:?)
[10] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fb4bcde0830] (??:0)
[11] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0x45fe6f] (??:?)
-- END OF BACKTRACE --
```
Godot: 3.0.1 x64 stable - official build
OS: Ubuntu Mate 16.04 x64 with Mesa everyday build
CPU: AMD A10-9600P RADEON R5
GPU: AMD CARRIZO
RAM: 12GB | 1.0 | Godot Crash on when I try run non-existing function form script that extends another script - I have script that extends from node with some code.
When I try execute some non-existing function(because I make mistake) in script that extends first script godot crashes entirely.
First Error message I always get second is crash.
```
OpenGL ES 3.0 Renderer: AMD CARRIZO (DRM 3.23.0 / 4.15.0-041500-generic, LLVM 6.0.0)
ERROR: texture_set_size_override: Condition ' p_width <= 0 || p_width > 16384 ' is true.
At: drivers/gles3/rasterizer_storage_gles3.cpp:1040.
ERROR: operator[]: FATAL: Index p_index=33 out of size (size()=33)
At: core/vector.h:138.
handle_crash: Program crashed with signal 4
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x7fb4bcdf54b0] (??:0)
[2] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0x17d8c77] (??:?)
[3] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0x9e73d8] (<artificial>:?)
[4] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0xa1f4ec] (<artificial>:?)
[5] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0x19c0334] (??:?)
[6] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0xf79ab9] (<artificial>:?)
[7] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0xfe83c7] (??:?)
[8] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0x4c55e8] (??:?)
[9] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0x45411d] (??:?)
[10] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fb4bcde0830] (??:0)
[11] /home/jeremi360/Apps/Godot_v3.0.1-stable_x11.64() [0x45fe6f] (??:?)
-- END OF BACKTRACE --
```
Godot: 3.0.1 x64 stable - official build
OS: Ubuntu Mate 16.04 x64 with Mesa everyday build
CPU: AMD A10-9600P RADEON R5
GPU: AMD CARRIZO
RAM: 12GB | non_priority | godot crash on when i try run non existing function form script that extends another script i have script that extends from node with some code when i try execute some non existing function because i make mistake in script that extends first script godot crashes entirely first error message i always get second is crash opengl es renderer amd carrizo drm generic llvm error texture set size override condition p width is true at drivers rasterizer storage cpp error operator fatal index p index out of size size at core vector h handle crash program crashed with signal dumping the backtrace please include this when reporting the bug on lib linux gnu libc so home apps godot stable home apps godot stable home apps godot stable home apps godot stable home apps godot stable home apps godot stable home apps godot stable home apps godot stable lib linux gnu libc so libc start main home apps godot stable end of backtrace godot stable official build os ubuntu mate with mesa everyday build cpu amd radeon gpu amd carrizo ram | 0 |
26,097 | 19,662,289,157 | IssuesEvent | 2022-01-10 18:17:53 | astropy/astropy-tutorials | https://api.github.com/repos/astropy/astropy-tutorials | closed | Update README | infrastructure | Update README to describe relationship to learn-astropy repo and link to new contributing docs and what not. | 1.0 | Update README - Update README to describe relationship to learn-astropy repo and link to new contributing docs and what not. | non_priority | update readme update readme to describe relationship to learn astropy repo and link to new contributing docs and what not | 0 |
239,882 | 26,236,724,200 | IssuesEvent | 2023-01-05 08:01:25 | dbankws-test/bootstrap | https://api.github.com/repos/dbankws-test/bootstrap | closed | WS-2018-0650 (High) detected in useragent-2.3.0.tgz - autoclosed | security vulnerability | ## WS-2018-0650 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>useragent-2.3.0.tgz</b></p></summary>
<p>Fastest, most accurate & effecient user agent string parser, uses Browserscope's research for parsing</p>
<p>Library home page: <a href="https://registry.npmjs.org/useragent/-/useragent-2.3.0.tgz">https://registry.npmjs.org/useragent/-/useragent-2.3.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/useragent/package.json</p>
<p>
Dependency Hierarchy:
- karma-0.13.22.tgz (Root Library)
- :x: **useragent-2.3.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/dbankws-test/bootstrap/commit/c977b86ccad42153837b2630ab4823d952449f3c">c977b86ccad42153837b2630ab4823d952449f3c</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>
Regular Expression Denial of Service (ReDoS) vulnerability was found in useragent through 2.3.0.
<p>Publish Date: 2018-02-27
<p>URL: <a href=https://hackerone.com/reports/320159>WS-2018-0650</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/WS-2018-0650">https://nvd.nist.gov/vuln/detail/WS-2018-0650</a></p>
<p>Release Date: 2018-02-27</p>
<p>Fix Resolution: NorDroN.AngularTemplate - 0.1.6;dotnetng.template - 1.0.0.4;JetBrains.Rider.Frontend5 - 213.0.20211008.154703-eap03;MIDIator.WebClient - 1.0.105</p>
</p>
</details>
<p></p>
| True | WS-2018-0650 (High) detected in useragent-2.3.0.tgz - autoclosed - ## WS-2018-0650 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>useragent-2.3.0.tgz</b></p></summary>
<p>Fastest, most accurate & effecient user agent string parser, uses Browserscope's research for parsing</p>
<p>Library home page: <a href="https://registry.npmjs.org/useragent/-/useragent-2.3.0.tgz">https://registry.npmjs.org/useragent/-/useragent-2.3.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/useragent/package.json</p>
<p>
Dependency Hierarchy:
- karma-0.13.22.tgz (Root Library)
- :x: **useragent-2.3.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/dbankws-test/bootstrap/commit/c977b86ccad42153837b2630ab4823d952449f3c">c977b86ccad42153837b2630ab4823d952449f3c</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>
Regular Expression Denial of Service (ReDoS) vulnerability was found in useragent through 2.3.0.
<p>Publish Date: 2018-02-27
<p>URL: <a href=https://hackerone.com/reports/320159>WS-2018-0650</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/WS-2018-0650">https://nvd.nist.gov/vuln/detail/WS-2018-0650</a></p>
<p>Release Date: 2018-02-27</p>
<p>Fix Resolution: NorDroN.AngularTemplate - 0.1.6;dotnetng.template - 1.0.0.4;JetBrains.Rider.Frontend5 - 213.0.20211008.154703-eap03;MIDIator.WebClient - 1.0.105</p>
</p>
</details>
<p></p>
| non_priority | ws high detected in useragent tgz autoclosed ws high severity vulnerability vulnerable library useragent tgz fastest most accurate effecient user agent string parser uses browserscope s research for parsing library home page a href path to dependency file package json path to vulnerable library node modules useragent package json dependency hierarchy karma tgz root library x useragent tgz vulnerable library found in head commit a href found in base branch master vulnerability details regular expression denial of service redos vulnerability was found in useragent through publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution nordron angulartemplate dotnetng template jetbrains rider midiator webclient | 0 |
424,382 | 29,058,802,561 | IssuesEvent | 2023-05-15 02:16:35 | AreWeAntiCheatYet/AreWeAntiCheatYet | https://api.github.com/repos/AreWeAntiCheatYet/AreWeAntiCheatYet | closed | Request Roblox | documentation | ### Game Title
Roblox
### Game Website
https://roblox.com
### Anti-Cheat Software
Planned
### Status of the Anti-Cheat
Denied
### Tinkering Steps
~~`roblox-player:1+launchmode:app+channel:zlive` to revert x64 client, won't work once fully rolled out~~ It's fully rolled out
### Proof of Mention
https://devforum.roblox.com/t/the-new-roblox-64-bit-byfron-client-forbids-wine-users-from-using-it-most-likely-unintentional/2305528/2 | 1.0 | Request Roblox - ### Game Title
Roblox
### Game Website
https://roblox.com
### Anti-Cheat Software
Planned
### Status of the Anti-Cheat
Denied
### Tinkering Steps
~~`roblox-player:1+launchmode:app+channel:zlive` to revert x64 client, won't work once fully rolled out~~ It's fully rolled out
### Proof of Mention
https://devforum.roblox.com/t/the-new-roblox-64-bit-byfron-client-forbids-wine-users-from-using-it-most-likely-unintentional/2305528/2 | non_priority | request roblox game title roblox game website anti cheat software planned status of the anti cheat denied tinkering steps roblox player launchmode app channel zlive to revert client won t work once fully rolled out it s fully rolled out proof of mention | 0 |
6,307 | 7,565,527,511 | IssuesEvent | 2018-04-21 11:01:13 | odoo/odoo | https://api.github.com/repos/odoo/odoo | closed | [11.0] Mark as paid button is always shown even the payment transaction is done | 11.0 Services | Impacted versions:
11.0
Steps to reproduce:
1. Make an eCommerce order by choosing the payment method "Wire Transfer". So, the order number has been generated.
2. Go to the backend Sales / Quotations, Choose the order number which generated by pre-step.
3. On the order form, click the "Mark as paid" button. The state of the payment transaction of the order has been changed as done.
Current behavior:
the "Mark as paid" button is still alive on the order form next to "Create invoice" button.
Expected behavior:
the "Mark as paid" button should be hide once clicked.
Video/Screenshot link (optional):
| 1.0 | [11.0] Mark as paid button is always shown even the payment transaction is done - Impacted versions:
11.0
Steps to reproduce:
1. Make an eCommerce order by choosing the payment method "Wire Transfer". So, the order number has been generated.
2. Go to the backend Sales / Quotations, Choose the order number which generated by pre-step.
3. On the order form, click the "Mark as paid" button. The state of the payment transaction of the order has been changed as done.
Current behavior:
the "Mark as paid" button is still alive on the order form next to "Create invoice" button.
Expected behavior:
the "Mark as paid" button should be hide once clicked.
Video/Screenshot link (optional):
| non_priority | mark as paid button is always shown even the payment transaction is done impacted versions steps to reproduce make an ecommerce order by choosing the payment method wire transfer so the order number has been generated go to the backend sales quotations choose the order number which generated by pre step on the order form click the mark as paid button the state of the payment transaction of the order has been changed as done current behavior the mark as paid button is still alive on the order form next to create invoice button expected behavior the mark as paid button should be hide once clicked video screenshot link optional | 0 |
72,056 | 31,150,333,308 | IssuesEvent | 2023-08-16 09:30:33 | MicrosoftDocs/azure-docs | https://api.github.com/repos/MicrosoftDocs/azure-docs | closed | Connecting to SQL should use new Microsoft.Sql.Client | app-service/svc triaged assigned-to-author doc-enhancement Pri2 | The new Microsoft.Sql.Client library handles retrieving the token from the endpoint.
https://docs.microsoft.com/en-us/sql/connect/ado-net/sql/azure-active-directory-authentication?view=sql-server-ver15#using-active-directory-default-authentication
https://github.com/dotnet/SqlClient/pull/730
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 1e119045-e113-d9d1-1b5e-a87e6befe3aa
* Version Independent ID: 98fcc13e-5da6-7251-d702-d9ee07c00581
* Content: [Tutorial: Access data with managed identity - Azure App Service](https://docs.microsoft.com/en-us/azure/app-service/tutorial-connect-msi-sql-database?tabs=windowsclient%2Cef%2Cdotnet)
* Content Source: [articles/app-service/tutorial-connect-msi-sql-database.md](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-connect-msi-sql-database.md)
* Service: **app-service**
* GitHub Login: @cephalin
* Microsoft Alias: **cephalin** | 1.0 | Connecting to SQL should use new Microsoft.Sql.Client - The new Microsoft.Sql.Client library handles retrieving the token from the endpoint.
https://docs.microsoft.com/en-us/sql/connect/ado-net/sql/azure-active-directory-authentication?view=sql-server-ver15#using-active-directory-default-authentication
https://github.com/dotnet/SqlClient/pull/730
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 1e119045-e113-d9d1-1b5e-a87e6befe3aa
* Version Independent ID: 98fcc13e-5da6-7251-d702-d9ee07c00581
* Content: [Tutorial: Access data with managed identity - Azure App Service](https://docs.microsoft.com/en-us/azure/app-service/tutorial-connect-msi-sql-database?tabs=windowsclient%2Cef%2Cdotnet)
* Content Source: [articles/app-service/tutorial-connect-msi-sql-database.md](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-connect-msi-sql-database.md)
* Service: **app-service**
* GitHub Login: @cephalin
* Microsoft Alias: **cephalin** | non_priority | connecting to sql should use new microsoft sql client the new microsoft sql client library handles retrieving the token from the endpoint document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service app service github login cephalin microsoft alias cephalin | 0 |
4,180 | 4,957,295,657 | IssuesEvent | 2016-12-02 03:34:56 | brave/browser-laptop | https://api.github.com/repos/brave/browser-laptop | closed | HTML5 Battery Status API | privacy security | The API does not require user permission to read the battery information, any website or third-party scripts included on them, can use the API. The API also does not require browsers to notify users when the battery information is accessed. That allows website and third-party scripts to access the battery information transparently – without users’ awareness.
http://techcrunch.com/2015/08/04/battery-attributes-can-be-used-to-track-web-users/
| True | HTML5 Battery Status API - The API does not require user permission to read the battery information, any website or third-party scripts included on them, can use the API. The API also does not require browsers to notify users when the battery information is accessed. That allows website and third-party scripts to access the battery information transparently – without users’ awareness.
http://techcrunch.com/2015/08/04/battery-attributes-can-be-used-to-track-web-users/
| non_priority | battery status api the api does not require user permission to read the battery information any website or third party scripts included on them can use the api the api also does not require browsers to notify users when the battery information is accessed that allows website and third party scripts to access the battery information transparently – without users’ awareness | 0 |
98,270 | 29,577,767,485 | IssuesEvent | 2023-06-07 01:21:05 | dotnet/dnceng | https://api.github.com/repos/dotnet/dnceng | opened | Build failed: dotnet-arcade-validation-official/main #20230606.1 | Build Failed | Build [#20230606.1](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_build/results?buildId=2195077) failed
## :x: : internal / dotnet-arcade-validation-official failed
### Summary
**Finished** - Wed, 07 Jun 2023 01:20:51 GMT
**Duration** - 78 minutes
**Requested for** - Microsoft.VisualStudio.Services.TFS
**Reason** - schedule
### Details
#### Build
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2195077/logs/140) - The job running on agent NetCore1ESPool-Internal-Int 2 ran longer than the maximum time of 60 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2195077/logs/135) - The operation was canceled.
### Changes
| 1.0 | Build failed: dotnet-arcade-validation-official/main #20230606.1 - Build [#20230606.1](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_build/results?buildId=2195077) failed
## :x: : internal / dotnet-arcade-validation-official failed
### Summary
**Finished** - Wed, 07 Jun 2023 01:20:51 GMT
**Duration** - 78 minutes
**Requested for** - Microsoft.VisualStudio.Services.TFS
**Reason** - schedule
### Details
#### Build
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2195077/logs/140) - The job running on agent NetCore1ESPool-Internal-Int 2 ran longer than the maximum time of 60 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2195077/logs/135) - The operation was canceled.
### Changes
| non_priority | build failed dotnet arcade validation official main build failed x internal dotnet arcade validation official failed summary finished wed jun gmt duration minutes requested for microsoft visualstudio services tfs reason schedule details build x the job running on agent internal int ran longer than the maximum time of minutes for more information see x the operation was canceled changes | 0 |
58,144 | 24,347,080,314 | IssuesEvent | 2022-10-02 13:10:04 | CS3219-AY2223S1/cs3219-project-ay2223s1-g12 | https://api.github.com/repos/CS3219-AY2223S1/cs3219-project-ay2223s1-g12 | closed | Add Authorisations to backend API | backend user-service | 1. Notice that currently, any user can call any API, whether or not they are authenticated and logged in.
2. APIs users should only be authorized to call if they are logged in - Change Password, Account Deletion, Logout
3. For these APIs, verify the user’s JWT before handling the requests | 1.0 | Add Authorisations to backend API - 1. Notice that currently, any user can call any API, whether or not they are authenticated and logged in.
2. APIs users should only be authorized to call if they are logged in - Change Password, Account Deletion, Logout
3. For these APIs, verify the user’s JWT before handling the requests | non_priority | add authorisations to backend api notice that currently any user can call any api whether or not they are authenticated and logged in apis users should only be authorized to call if they are logged in change password account deletion logout for these apis verify the user’s jwt before handling the requests | 0 |
360,589 | 25,297,581,804 | IssuesEvent | 2022-11-17 08:13:09 | acdh-oeaw/apis-ampel | https://api.github.com/repos/acdh-oeaw/apis-ampel | opened | Update Documentation | documentation | - Add Screenshots
- Remove edit-views from documentation (Ampel was removed from the edit-views, as it broke the ajax-forms) | 1.0 | Update Documentation - - Add Screenshots
- Remove edit-views from documentation (Ampel was removed from the edit-views, as it broke the ajax-forms) | non_priority | update documentation add screenshots remove edit views from documentation ampel was removed from the edit views as it broke the ajax forms | 0 |
206,521 | 16,044,953,311 | IssuesEvent | 2021-04-22 12:39:26 | pykale/pykale | https://api.github.com/repos/pykale/pykale | opened | [Docs] Test guidelines url cannot be found in CONTRIBUTING | documentation | # 📚 Documentation
The test guidelines url seems to incorrect in [there](https://github.com/pykale/pykale/blob/main/.github/CONTRIBUTING.md#testing). It is https://github.com/pykale/pykale/blob/main/.github/tests/readme.md and cannot be found. I think whether the correct one should be https://github.com/pykale/pykale/blob/main/tests/readme.md? | 1.0 | [Docs] Test guidelines url cannot be found in CONTRIBUTING - # 📚 Documentation
The test guidelines url seems to incorrect in [there](https://github.com/pykale/pykale/blob/main/.github/CONTRIBUTING.md#testing). It is https://github.com/pykale/pykale/blob/main/.github/tests/readme.md and cannot be found. I think whether the correct one should be https://github.com/pykale/pykale/blob/main/tests/readme.md? | non_priority | test guidelines url cannot be found in contributing 📚 documentation the test guidelines url seems to incorrect in it is and cannot be found i think whether the correct one should be | 0 |
91,885 | 26,512,116,195 | IssuesEvent | 2023-01-18 17:55:18 | tensorflow/tensorflow | https://api.github.com/repos/tensorflow/tensorflow | closed | Make tf.io.gfile / tf.data separate (standalone) packages? | stat:awaiting response type:feature type:build/install stalled comp:ops comp:data | **System information**
- TensorFlow version (you are using): 2.4.x
- Are you willing to contribute it (Yes/No): No (time constraints)
**Describe the feature and the current behavior/state.**
At the moment we have to install `tensorflow` as a whole even though our data-processing pipeline only requires access to `tf.gfile` and/or `tf.data`.
Imo it could be beneficial if it was possible to install these two packages separately (standalone) without having to install the rest of Tensorflow. Especially `tf.gfile` could be useful in projects where not a single line related to machine-learning is written so this would be a candidate to become its own `pip`-installable package maybe with the option to install the `tf.data` functionalities.
```
pip install tensorflow_gfile # gfile only
pip install tensorflow_gfile[data] # gfile + data
pip install tensorflow # All the things
```
**Will this change the current api? How?**
The API should not change, only the fact that packages can be selectively installed.
**Who will benefit with this feature?**
Everyone who works on larger projects.
| 1.0 | Make tf.io.gfile / tf.data separate (standalone) packages? - **System information**
- TensorFlow version (you are using): 2.4.x
- Are you willing to contribute it (Yes/No): No (time constraints)
**Describe the feature and the current behavior/state.**
At the moment we have to install `tensorflow` as a whole even though our data-processing pipeline only requires access to `tf.gfile` and/or `tf.data`.
Imo it could be beneficial if it was possible to install these two packages separately (standalone) without having to install the rest of Tensorflow. Especially `tf.gfile` could be useful in projects where not a single line related to machine-learning is written so this would be a candidate to become its own `pip`-installable package maybe with the option to install the `tf.data` functionalities.
```
pip install tensorflow_gfile # gfile only
pip install tensorflow_gfile[data] # gfile + data
pip install tensorflow # All the things
```
**Will this change the current api? How?**
The API should not change, only the fact that packages can be selectively installed.
**Who will benefit with this feature?**
Everyone who works on larger projects.
| non_priority | make tf io gfile tf data separate standalone packages system information tensorflow version you are using x are you willing to contribute it yes no no time constraints describe the feature and the current behavior state at the moment we have to install tensorflow as a whole even though our data processing pipeline only requires access to tf gfile and or tf data imo it could be beneficial if it was possible to install these two packages separately standalone without having to install the rest of tensorflow especially tf gfile could be useful in projects where not a single line related to machine learning is written so this would be a candidate to become its own pip installable package maybe with the option to install the tf data functionalities pip install tensorflow gfile gfile only pip install tensorflow gfile gfile data pip install tensorflow all the things will this change the current api how the api should not change only the fact that packages can be selectively installed who will benefit with this feature everyone who works on larger projects | 0 |
169,709 | 14,228,482,063 | IssuesEvent | 2020-11-18 03:55:29 | futurewei-cloud/zeta | https://api.github.com/repos/futurewei-cloud/zeta | closed | Zeta Target Deployment | Management Plane documentation enhancement | **User Story**
As a developer, I want a consistent deployment mechanism so that I can easily test/deploy Zeta services on AWS cloud, Lab Servers and localhost
**Is your feature request related to a problem? Please describe.**
I'm always frustrated when test or integrate Zeta on different environments, the setting up, orchestration requires a lot of care and repeated work.
**Describe the solution you'd like**
I want to use Ansible playbook to manage target inventories and credentials, switch context automatically based on deployment environment and fully automate the deployment and orchestration procedure for me:
Overall procedure:
1. Config Ansible inventories/credentials for different deployment environments
2. CLI option to choose deployment environment
3. Deploy K8S cluster on Zeta management hosts
4. Deploy Zeta management CRD/services on K8S
5. Deploy Zeta Data plane Apps on Zeta networking hosts
6. Deploy OpenStack control plane services on OpenStack controller hosts (Optional)
7. Deploy OpenStack data plane services on OpenStack compute hosts (Optional)
8. Deploy Alcor controller on OpenStack controller hosts (Optional)
9. Deploy Alcor Controller Agent on OpenStack compute hosts
10. Validate Zeta NBI APIs
11. Validate ACA NBI APIs (Optional)
**Describe alternatives you've considered**
Manual and script based procedure are hard to maintain and less flexible
**Additional context**
None | 1.0 | Zeta Target Deployment - **User Story**
As a developer, I want a consistent deployment mechanism so that I can easily test/deploy Zeta services on AWS cloud, Lab Servers and localhost
**Is your feature request related to a problem? Please describe.**
I'm always frustrated when test or integrate Zeta on different environments, the setting up, orchestration requires a lot of care and repeated work.
**Describe the solution you'd like**
I want to use Ansible playbook to manage target inventories and credentials, switch context automatically based on deployment environment and fully automate the deployment and orchestration procedure for me:
Overall procedure:
1. Config Ansible inventories/credentials for different deployment environments
2. CLI option to choose deployment environment
3. Deploy K8S cluster on Zeta management hosts
4. Deploy Zeta management CRD/services on K8S
5. Deploy Zeta Data plane Apps on Zeta networking hosts
6. Deploy OpenStack control plane services on OpenStack controller hosts (Optional)
7. Deploy OpenStack data plane services on OpenStack compute hosts (Optional)
8. Deploy Alcor controller on OpenStack controller hosts (Optional)
9. Deploy Alcor Controller Agent on OpenStack compute hosts
10. Validate Zeta NBI APIs
11. Validate ACA NBI APIs (Optional)
**Describe alternatives you've considered**
Manual and script based procedure are hard to maintain and less flexible
**Additional context**
None | non_priority | zeta target deployment user story as a developer i want a consistent deployment mechanism so that i can easily test deploy zeta services on aws cloud lab servers and localhost is your feature request related to a problem please describe i m always frustrated when test or integrate zeta on different environments the setting up orchestration requires a lot of care and repeated work describe the solution you d like i want to use ansible playbook to manage target inventories and credentials switch context automatically based on deployment environment and fully automate the deployment and orchestration procedure for me overall procedure config ansible inventories credentials for different deployment environments cli option to choose deployment environment deploy cluster on zeta management hosts deploy zeta management crd services on deploy zeta data plane apps on zeta networking hosts deploy openstack control plane services on openstack controller hosts optional deploy openstack data plane services on openstack compute hosts optional deploy alcor controller on openstack controller hosts optional deploy alcor controller agent on openstack compute hosts validate zeta nbi apis validate aca nbi apis optional describe alternatives you ve considered manual and script based procedure are hard to maintain and less flexible additional context none | 0 |
116,307 | 17,360,125,405 | IssuesEvent | 2021-07-29 19:20:12 | lukebroganws/JS-Demo | https://api.github.com/repos/lukebroganws/JS-Demo | opened | CVE-2020-8116 (High) detected in dot-prop-4.2.0.tgz | security vulnerability | ## CVE-2020-8116 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>dot-prop-4.2.0.tgz</b></p></summary>
<p>Get, set, or delete a property from a nested object using a dot path</p>
<p>Library home page: <a href="https://registry.npmjs.org/dot-prop/-/dot-prop-4.2.0.tgz">https://registry.npmjs.org/dot-prop/-/dot-prop-4.2.0.tgz</a></p>
<p>Path to dependency file: JS-Demo/package.json</p>
<p>Path to vulnerable library: JS-Demo/node_modules/dot-prop/package.json</p>
<p>
Dependency Hierarchy:
- nodemon-1.19.1.tgz (Root Library)
- update-notifier-2.5.0.tgz
- configstore-3.1.2.tgz
- :x: **dot-prop-4.2.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/lukebroganws/JS-Demo/commit/ad02c7350709424606f9242b8b5a7eb8a9d174c0">ad02c7350709424606f9242b8b5a7eb8a9d174c0</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>
Prototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.
<p>Publish Date: 2020-02-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8116>CVE-2020-8116</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.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8116">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8116</a></p>
<p>Release Date: 2020-02-04</p>
<p>Fix Resolution: dot-prop - 5.1.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"dot-prop","packageVersion":"4.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"nodemon:1.19.1;update-notifier:2.5.0;configstore:3.1.2;dot-prop:4.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"dot-prop - 5.1.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-8116","vulnerabilityDetails":"Prototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8116","cvss3Severity":"high","cvss3Score":"7.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-8116 (High) detected in dot-prop-4.2.0.tgz - ## CVE-2020-8116 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>dot-prop-4.2.0.tgz</b></p></summary>
<p>Get, set, or delete a property from a nested object using a dot path</p>
<p>Library home page: <a href="https://registry.npmjs.org/dot-prop/-/dot-prop-4.2.0.tgz">https://registry.npmjs.org/dot-prop/-/dot-prop-4.2.0.tgz</a></p>
<p>Path to dependency file: JS-Demo/package.json</p>
<p>Path to vulnerable library: JS-Demo/node_modules/dot-prop/package.json</p>
<p>
Dependency Hierarchy:
- nodemon-1.19.1.tgz (Root Library)
- update-notifier-2.5.0.tgz
- configstore-3.1.2.tgz
- :x: **dot-prop-4.2.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/lukebroganws/JS-Demo/commit/ad02c7350709424606f9242b8b5a7eb8a9d174c0">ad02c7350709424606f9242b8b5a7eb8a9d174c0</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>
Prototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.
<p>Publish Date: 2020-02-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8116>CVE-2020-8116</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.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8116">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8116</a></p>
<p>Release Date: 2020-02-04</p>
<p>Fix Resolution: dot-prop - 5.1.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"dot-prop","packageVersion":"4.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"nodemon:1.19.1;update-notifier:2.5.0;configstore:3.1.2;dot-prop:4.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"dot-prop - 5.1.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-8116","vulnerabilityDetails":"Prototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8116","cvss3Severity":"high","cvss3Score":"7.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in dot prop tgz cve high severity vulnerability vulnerable library dot prop tgz get set or delete a property from a nested object using a dot path library home page a href path to dependency file js demo package json path to vulnerable library js demo node modules dot prop package json dependency hierarchy nodemon tgz root library update notifier tgz configstore tgz x dot prop tgz vulnerable library found in head commit a href found in base branch master vulnerability details prototype pollution vulnerability in dot prop npm package versions before and versions x before allows an attacker to add arbitrary properties to javascript language constructs such as objects 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 low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution dot prop isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree nodemon update notifier configstore dot prop isminimumfixversionavailable true minimumfixversion dot prop basebranches vulnerabilityidentifier cve vulnerabilitydetails prototype pollution vulnerability in dot prop npm package versions before and versions x before allows an attacker to add arbitrary properties to javascript language constructs such as objects vulnerabilityurl | 0 |
15,353 | 8,852,580,621 | IssuesEvent | 2019-01-08 18:45:55 | webhintio/hint | https://api.github.com/repos/webhintio/hint | reopened | Rule for flagging offscreen images in the page | area:hint hint-category:performance | Majority of the end users are not lucky like @alrra to[ have a tall/wide monitor](https://twitter.com/alrra/status/690212838942621700)!
We should consider building a rule which recommends lazy loading of offscreen images
https://developers.google.com/web/tools/lighthouse/audits/offscreen-images
| True | Rule for flagging offscreen images in the page - Majority of the end users are not lucky like @alrra to[ have a tall/wide monitor](https://twitter.com/alrra/status/690212838942621700)!
We should consider building a rule which recommends lazy loading of offscreen images
https://developers.google.com/web/tools/lighthouse/audits/offscreen-images
| non_priority | rule for flagging offscreen images in the page majority of the end users are not lucky like alrra to we should consider building a rule which recommends lazy loading of offscreen images | 0 |
83,739 | 24,134,060,779 | IssuesEvent | 2022-09-21 09:47:05 | speedb-io/speedb | https://api.github.com/repos/speedb-io/speedb | opened | build: support ccache and sccache in the Makefile | Upstreamable build | Using ccache and sccache to speed up build times is already supported by the CMake configuration. It saves a lot of time during the development cycle when debugging or when switching branches and build configurations frequently.
Add the support by detecting the availability of sccache/ccache in the `build_detect_platform` script and using that information in the Makefile. | 1.0 | build: support ccache and sccache in the Makefile - Using ccache and sccache to speed up build times is already supported by the CMake configuration. It saves a lot of time during the development cycle when debugging or when switching branches and build configurations frequently.
Add the support by detecting the availability of sccache/ccache in the `build_detect_platform` script and using that information in the Makefile. | non_priority | build support ccache and sccache in the makefile using ccache and sccache to speed up build times is already supported by the cmake configuration it saves a lot of time during the development cycle when debugging or when switching branches and build configurations frequently add the support by detecting the availability of sccache ccache in the build detect platform script and using that information in the makefile | 0 |
30,010 | 5,718,404,483 | IssuesEvent | 2017-04-19 19:28:07 | aws/aws-sdk-js | https://api.github.com/repos/aws/aws-sdk-js | closed | Assume Role Profiles don't follow the CLI and Boto Convention for Configuration | Documentation Feature Request | https://github.com/aws/aws-sdk-js/pull/926 apparently added the ability to have assumeRole items in the aws credentials file
but the set up for this doesn't seem to be documented anywhere and it also doesn't follow what works in CLI and Boto and IS documented here: http://docs.aws.amazon.com/cli/latest/topic/config-vars.html#using-aws-iam-roles
so now if i want to use the cli on my machine and the aws sdk my config file and my credentials file needs
```
...
[assumeroleprofile]
role_arn = arn:aws:iam::accountnum:role/SuperRole
source_profile = main
...
```
could we just get the JS sdk to read the ~/.aws/config like both the CLI and Boto do?
| 1.0 | Assume Role Profiles don't follow the CLI and Boto Convention for Configuration - https://github.com/aws/aws-sdk-js/pull/926 apparently added the ability to have assumeRole items in the aws credentials file
but the set up for this doesn't seem to be documented anywhere and it also doesn't follow what works in CLI and Boto and IS documented here: http://docs.aws.amazon.com/cli/latest/topic/config-vars.html#using-aws-iam-roles
so now if i want to use the cli on my machine and the aws sdk my config file and my credentials file needs
```
...
[assumeroleprofile]
role_arn = arn:aws:iam::accountnum:role/SuperRole
source_profile = main
...
```
could we just get the JS sdk to read the ~/.aws/config like both the CLI and Boto do?
| non_priority | assume role profiles don t follow the cli and boto convention for configuration apparently added the ability to have assumerole items in the aws credentials file but the set up for this doesn t seem to be documented anywhere and it also doesn t follow what works in cli and boto and is documented here so now if i want to use the cli on my machine and the aws sdk my config file and my credentials file needs role arn arn aws iam accountnum role superrole source profile main could we just get the js sdk to read the aws config like both the cli and boto do | 0 |
26,522 | 20,189,573,208 | IssuesEvent | 2022-02-11 03:18:02 | dotnet/project-system | https://api.github.com/repos/dotnet/project-system | opened | Remove use of \\cpvsbuild\drops\Roslyn for symbol publishing | Area-Infrastructure | Currently, our [release pipeline](https://devdiv.visualstudio.com/DevDiv/_release?view=all&_a=releases&definitionId=1242) has a task after an insertion is made to publish the symbols. These symbols are stored in a DevOps feed and checked via a Symbol Check in the VS insertion PR. The issue is our current process requires us to use a fileshare called `\\cpvsbuild\drops\Roslyn`. I was informed last year they want to deprecate this fileshare.
I attempted to resolve this previously but failed. Fortunately, there is a [guide on symbol publishing](https://devdiv.visualstudio.com/DevDiv/_wiki/wikis/DevDiv.wiki/671/Manage-Your-Symbols) that we should be able to use to resolve this issue. The main thing to recognize is that our release pipeline is specifying this fileshare in the Advanced section of the MicroBuild Publish Symbols task. Simply removing the fileshare path from the task fails to publish the symbols.
My initial investigation from a rather long email chain can be found here:
https://gist.github.com/MiYanni/81b8650c42a0d76e4dfc405bca1500e3
Some information about the artifacts required for the release pipeline for symbol publishing can be seen in what I wrote in our `official.yml`:
https://github.com/dotnet/project-system/blob/c8137374c0f7e6458397627b530ddb14099cb6b9/build/ci/official.yml#L138-L148 | 1.0 | Remove use of \\cpvsbuild\drops\Roslyn for symbol publishing - Currently, our [release pipeline](https://devdiv.visualstudio.com/DevDiv/_release?view=all&_a=releases&definitionId=1242) has a task after an insertion is made to publish the symbols. These symbols are stored in a DevOps feed and checked via a Symbol Check in the VS insertion PR. The issue is our current process requires us to use a fileshare called `\\cpvsbuild\drops\Roslyn`. I was informed last year they want to deprecate this fileshare.
I attempted to resolve this previously but failed. Fortunately, there is a [guide on symbol publishing](https://devdiv.visualstudio.com/DevDiv/_wiki/wikis/DevDiv.wiki/671/Manage-Your-Symbols) that we should be able to use to resolve this issue. The main thing to recognize is that our release pipeline is specifying this fileshare in the Advanced section of the MicroBuild Publish Symbols task. Simply removing the fileshare path from the task fails to publish the symbols.
My initial investigation from a rather long email chain can be found here:
https://gist.github.com/MiYanni/81b8650c42a0d76e4dfc405bca1500e3
Some information about the artifacts required for the release pipeline for symbol publishing can be seen in what I wrote in our `official.yml`:
https://github.com/dotnet/project-system/blob/c8137374c0f7e6458397627b530ddb14099cb6b9/build/ci/official.yml#L138-L148 | non_priority | remove use of cpvsbuild drops roslyn for symbol publishing currently our has a task after an insertion is made to publish the symbols these symbols are stored in a devops feed and checked via a symbol check in the vs insertion pr the issue is our current process requires us to use a fileshare called cpvsbuild drops roslyn i was informed last year they want to deprecate this fileshare i attempted to resolve this previously but failed fortunately there is a that we should be able to use to resolve this issue the main thing to recognize is that our release pipeline is specifying this fileshare in the advanced section of the microbuild publish symbols task simply removing the fileshare path from the task fails to publish the symbols my initial investigation from a rather long email chain can be found here some information about the artifacts required for the release pipeline for symbol publishing can be seen in what i wrote in our official yml | 0 |
3,085 | 2,734,505,401 | IssuesEvent | 2015-04-17 20:21:43 | gizmoboard/gizmoboard | https://api.github.com/repos/gizmoboard/gizmoboard | opened | Add Centralized Data Source Deployment instructions to the README | documentation | Add instructions to the README that provide instructions on how to centralize a data source for multiple dashboards. | 1.0 | Add Centralized Data Source Deployment instructions to the README - Add instructions to the README that provide instructions on how to centralize a data source for multiple dashboards. | non_priority | add centralized data source deployment instructions to the readme add instructions to the readme that provide instructions on how to centralize a data source for multiple dashboards | 0 |
337,358 | 30,247,561,388 | IssuesEvent | 2023-07-06 17:42:58 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | reopened | Fix general.test_numpy_can_cast | NumPy Frontend Sub Task Failing Test | | | |
|---|---|
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5478319447"><img src=https://img.shields.io/badge/-failure-red></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5478319447"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5478319447"><img src=https://img.shields.io/badge/-failure-red></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5429850340/jobs/9875159514"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5478319447"><img src=https://img.shields.io/badge/-success-success></a>
| 1.0 | Fix general.test_numpy_can_cast - | | |
|---|---|
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5478319447"><img src=https://img.shields.io/badge/-failure-red></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5478319447"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5478319447"><img src=https://img.shields.io/badge/-failure-red></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5429850340/jobs/9875159514"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5478319447"><img src=https://img.shields.io/badge/-success-success></a>
| non_priority | fix general test numpy can cast numpy a href src torch a href src tensorflow a href src jax a href src paddle a href src | 0 |
75,030 | 20,606,059,438 | IssuesEvent | 2022-03-07 00:20:20 | NVIDIA/spark-rapids | https://api.github.com/repos/NVIDIA/spark-rapids | closed | Add diagnostics what shims cause "git revisions between shims are not equal" | build | When the dist module build encounters
`Check Failed: git revisions between shims are not equal`, the developer has to retrace the logic of the script to figure out what shims triggered it instead of being presented with this information right away.
_Originally posted by @gerashegalov in https://github.com/NVIDIA/spark-rapids/pull/4436#discussion_r776495728_ | 1.0 | Add diagnostics what shims cause "git revisions between shims are not equal" - When the dist module build encounters
`Check Failed: git revisions between shims are not equal`, the developer has to retrace the logic of the script to figure out what shims triggered it instead of being presented with this information right away.
_Originally posted by @gerashegalov in https://github.com/NVIDIA/spark-rapids/pull/4436#discussion_r776495728_ | non_priority | add diagnostics what shims cause git revisions between shims are not equal when the dist module build encounters check failed git revisions between shims are not equal the developer has to retrace the logic of the script to figure out what shims triggered it instead of being presented with this information right away originally posted by gerashegalov in | 0 |
23,410 | 7,327,646,972 | IssuesEvent | 2018-03-04 12:47:34 | godotengine/godot | https://api.github.com/repos/godotengine/godot | closed | Server platform underlinking issue with pcre2 module | bug platform:linuxbsd topic:buildsystem | **Godot version:**
Godot 3.0.2-stable, likely *master* too
**OS/device including version:**
Mageia 7 i586, GCC 7.3.0, pcre2 10.23
**Issue description:**
Building the `server` platform of Godot 3.0.2-stable on Mageia 7 against system libpcre2 fails linking with:
```
Linking Static Library ==> servers/libservers.server.opt.tools.32.a
Ranlib Library ==> servers/libservers.server.opt.tools.32.a
Linking Static Library ==> core/libcore.server.opt.tools.32.a
Ranlib Library ==> core/libcore.server.opt.tools.32.a
Linking Program ==> bin/godot_server.server.opt.tools.32
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::_pattern_info(unsigned int, void*) const':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:173: undefined reference to `pcre2_pattern_info_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:173: undefined reference to `pcre2_pattern_info_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:173: undefined reference to `pcre2_pattern_info_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:173: undefined reference to `pcre2_pattern_info_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::RegEx()':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:476: undefined reference to `pcre2_general_context_create_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::~RegEx()':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:506: undefined reference to `pcre2_code_free_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:507: undefined reference to `pcre2_general_context_free_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::clear()':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:187: undefined reference to `pcre2_code_free_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::compile(String const&)':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:219: undefined reference to `pcre2_compile_context_create_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:222: undefined reference to `pcre2_compile_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:226: undefined reference to `pcre2_get_error_message_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::RegEx(String const&)':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:489: undefined reference to `pcre2_general_context_create_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::sub(String const&, String const&, bool, int, int) const':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:397: undefined reference to `pcre2_match_context_create_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:402: undefined reference to `pcre2_match_data_create_from_pattern_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:404: undefined reference to `pcre2_substitute_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:412: undefined reference to `pcre2_match_data_free_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:413: undefined reference to `pcre2_match_context_free_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:409: undefined reference to `pcre2_substitute_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::search(String const&, int, int) const':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:279: undefined reference to `pcre2_match_context_create_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:282: undefined reference to `pcre2_match_data_create_from_pattern_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:284: undefined reference to `pcre2_match_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:291: undefined reference to `pcre2_get_ovector_count_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:292: undefined reference to `pcre2_get_ovector_pointer_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:287: undefined reference to `pcre2_match_data_free_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:302: undefined reference to `pcre2_match_data_free_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:303: undefined reference to `pcre2_match_context_free_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::_pattern_info(unsigned int, void*) const':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:173: undefined reference to `pcre2_pattern_info_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:173: undefined reference to `pcre2_pattern_info_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:173: undefined reference to `pcre2_pattern_info_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::clear()':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:187: undefined reference to `pcre2_code_free_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::_pattern_info(unsigned int, void*) const':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:173: undefined reference to `pcre2_pattern_info_32'
```
**Steps to reproduce:**
```
/usr/bin/scons -j24 'CCFLAGS=-O2 -g -pipe -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fomit-frame-pointer -march=i586 -mtune=generic -fasynchronous-unwind-tables' 'LINKFLAGS= -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-O1 -Wl,--build-id -Wl,--enable-new-dtags' builtin_freetype=no builtin_libogg=no builtin_libpng=no builtin_libtheora=no builtin_libvorbis=no builtin_libvpx=no builtin_libwebp=no builtin_openssl=no builtin_opus=no builtin_pcre2=no builtin_zlib=no udev=yes progress=no p=server tools=yes target=release_debug
``` | 1.0 | Server platform underlinking issue with pcre2 module - **Godot version:**
Godot 3.0.2-stable, likely *master* too
**OS/device including version:**
Mageia 7 i586, GCC 7.3.0, pcre2 10.23
**Issue description:**
Building the `server` platform of Godot 3.0.2-stable on Mageia 7 against system libpcre2 fails linking with:
```
Linking Static Library ==> servers/libservers.server.opt.tools.32.a
Ranlib Library ==> servers/libservers.server.opt.tools.32.a
Linking Static Library ==> core/libcore.server.opt.tools.32.a
Ranlib Library ==> core/libcore.server.opt.tools.32.a
Linking Program ==> bin/godot_server.server.opt.tools.32
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::_pattern_info(unsigned int, void*) const':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:173: undefined reference to `pcre2_pattern_info_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:173: undefined reference to `pcre2_pattern_info_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:173: undefined reference to `pcre2_pattern_info_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:173: undefined reference to `pcre2_pattern_info_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::RegEx()':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:476: undefined reference to `pcre2_general_context_create_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::~RegEx()':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:506: undefined reference to `pcre2_code_free_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:507: undefined reference to `pcre2_general_context_free_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::clear()':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:187: undefined reference to `pcre2_code_free_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::compile(String const&)':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:219: undefined reference to `pcre2_compile_context_create_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:222: undefined reference to `pcre2_compile_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:226: undefined reference to `pcre2_get_error_message_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::RegEx(String const&)':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:489: undefined reference to `pcre2_general_context_create_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::sub(String const&, String const&, bool, int, int) const':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:397: undefined reference to `pcre2_match_context_create_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:402: undefined reference to `pcre2_match_data_create_from_pattern_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:404: undefined reference to `pcre2_substitute_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:412: undefined reference to `pcre2_match_data_free_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:413: undefined reference to `pcre2_match_context_free_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:409: undefined reference to `pcre2_substitute_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::search(String const&, int, int) const':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:279: undefined reference to `pcre2_match_context_create_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:282: undefined reference to `pcre2_match_data_create_from_pattern_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:284: undefined reference to `pcre2_match_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:291: undefined reference to `pcre2_get_ovector_count_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:292: undefined reference to `pcre2_get_ovector_pointer_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:287: undefined reference to `pcre2_match_data_free_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:302: undefined reference to `pcre2_match_data_free_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:303: undefined reference to `pcre2_match_context_free_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::_pattern_info(unsigned int, void*) const':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:173: undefined reference to `pcre2_pattern_info_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:173: undefined reference to `pcre2_pattern_info_32'
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:173: undefined reference to `pcre2_pattern_info_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::clear()':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:187: undefined reference to `pcre2_code_free_32'
modules/libmodules.server.opt.tools.32.a(regex.server.opt.tools.32.o): In function `RegEx::_pattern_info(unsigned int, void*) const':
/home/iurt/rpmbuild/BUILD/godot-3.0.2-stable/modules/regex/regex.cpp:173: undefined reference to `pcre2_pattern_info_32'
```
**Steps to reproduce:**
```
/usr/bin/scons -j24 'CCFLAGS=-O2 -g -pipe -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fomit-frame-pointer -march=i586 -mtune=generic -fasynchronous-unwind-tables' 'LINKFLAGS= -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-O1 -Wl,--build-id -Wl,--enable-new-dtags' builtin_freetype=no builtin_libogg=no builtin_libpng=no builtin_libtheora=no builtin_libvorbis=no builtin_libvpx=no builtin_libwebp=no builtin_openssl=no builtin_opus=no builtin_pcre2=no builtin_zlib=no udev=yes progress=no p=server tools=yes target=release_debug
``` | non_priority | server platform underlinking issue with module godot version godot stable likely master too os device including version mageia gcc issue description building the server platform of godot stable on mageia against system fails linking with linking static library servers libservers server opt tools a ranlib library servers libservers server opt tools a linking static library core libcore server opt tools a ranlib library core libcore server opt tools a linking program bin godot server server opt tools modules libmodules server opt tools a regex server opt tools o in function regex pattern info unsigned int void const home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to pattern info home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to pattern info home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to pattern info home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to pattern info modules libmodules server opt tools a regex server opt tools o in function regex regex home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to general context create modules libmodules server opt tools a regex server opt tools o in function regex regex home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to code free home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to general context free modules libmodules server opt tools a regex server opt tools o in function regex clear home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to code free modules libmodules server opt tools a regex server opt tools o in function regex compile string const home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to compile context create home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to compile home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to get error message modules libmodules server opt tools a regex server opt tools o in function regex regex string const home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to general context create modules libmodules server opt tools a regex server opt tools o in function regex sub string const string const bool int int const home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to match context create home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to match data create from pattern home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to substitute home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to match data free home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to match context free home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to substitute modules libmodules server opt tools a regex server opt tools o in function regex search string const int int const home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to match context create home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to match data create from pattern home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to match home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to get ovector count home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to get ovector pointer home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to match data free home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to match data free home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to match context free modules libmodules server opt tools a regex server opt tools o in function regex pattern info unsigned int void const home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to pattern info home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to pattern info home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to pattern info modules libmodules server opt tools a regex server opt tools o in function regex clear home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to code free modules libmodules server opt tools a regex server opt tools o in function regex pattern info unsigned int void const home iurt rpmbuild build godot stable modules regex regex cpp undefined reference to pattern info steps to reproduce usr bin scons ccflags g pipe wformat werror format security wp d fortify source fstack protector param ssp buffer size fomit frame pointer march mtune generic fasynchronous unwind tables linkflags wl as needed wl no undefined wl z relro wl wl build id wl enable new dtags builtin freetype no builtin libogg no builtin libpng no builtin libtheora no builtin libvorbis no builtin libvpx no builtin libwebp no builtin openssl no builtin opus no builtin no builtin zlib no udev yes progress no p server tools yes target release debug | 0 |
115,204 | 14,703,595,089 | IssuesEvent | 2021-01-04 15:16:13 | dusk-network/plonk | https://api.github.com/repos/dusk-network/plonk | opened | Implement min constant generics | API-design area:cryptography constraint_system type:feature | Currently, the api allows the user to build two different arity lookup tables. Either 3 or 4.
The former is for witness of single operations types for lookups and the latter is for concatenated lookups. Instead of having both structs, we should implement min constant generics to have rules that permeates both use cases. | 1.0 | Implement min constant generics - Currently, the api allows the user to build two different arity lookup tables. Either 3 or 4.
The former is for witness of single operations types for lookups and the latter is for concatenated lookups. Instead of having both structs, we should implement min constant generics to have rules that permeates both use cases. | non_priority | implement min constant generics currently the api allows the user to build two different arity lookup tables either or the former is for witness of single operations types for lookups and the latter is for concatenated lookups instead of having both structs we should implement min constant generics to have rules that permeates both use cases | 0 |
100,902 | 30,811,330,451 | IssuesEvent | 2023-08-01 10:34:59 | helidon-io/helidon | https://api.github.com/repos/helidon-io/helidon | closed | 4.x: Builder interceptor to decorator | 4.x builder | Builder interceptor - either change the generated code to use the return value, or change the interface and name to only accept builder instance (to allow mutation, not replacement) | 1.0 | 4.x: Builder interceptor to decorator - Builder interceptor - either change the generated code to use the return value, or change the interface and name to only accept builder instance (to allow mutation, not replacement) | non_priority | x builder interceptor to decorator builder interceptor either change the generated code to use the return value or change the interface and name to only accept builder instance to allow mutation not replacement | 0 |
44,044 | 5,582,076,510 | IssuesEvent | 2017-03-28 20:23:53 | Microsoft/vscode | https://api.github.com/repos/Microsoft/vscode | closed | Test: Output appending improvements | testplan-item | - [ ] any os - @kieferrm
- [x] any os - @sandy081
As per #22804 we have made improvements in how we are appending content to the output channels. Verify:
* All output channels behave as before and that the output select dropdown nicely reflects the currently opened output
* You can create / delete new output channels from an extension and send output to that channel
* When there is too much output we show the last recieved output and stop showing the oldest
* You can spam the output from an extension and vscode will not crash (though it might be unresponsive for a couple of seconds due to JSON parseing and sending) | 1.0 | Test: Output appending improvements - - [ ] any os - @kieferrm
- [x] any os - @sandy081
As per #22804 we have made improvements in how we are appending content to the output channels. Verify:
* All output channels behave as before and that the output select dropdown nicely reflects the currently opened output
* You can create / delete new output channels from an extension and send output to that channel
* When there is too much output we show the last recieved output and stop showing the oldest
* You can spam the output from an extension and vscode will not crash (though it might be unresponsive for a couple of seconds due to JSON parseing and sending) | non_priority | test output appending improvements any os kieferrm any os as per we have made improvements in how we are appending content to the output channels verify all output channels behave as before and that the output select dropdown nicely reflects the currently opened output you can create delete new output channels from an extension and send output to that channel when there is too much output we show the last recieved output and stop showing the oldest you can spam the output from an extension and vscode will not crash though it might be unresponsive for a couple of seconds due to json parseing and sending | 0 |
218,773 | 16,770,780,982 | IssuesEvent | 2021-06-14 14:33:53 | sqlalchemy/sqlalchemy | https://api.github.com/repos/sqlalchemy/sqlalchemy | closed | confusing docs around one-to-one relationships | documentation question | **Describe the bug**
very minor docs only nitpick, I was trying to remind myself what `uselist=False` was called, when i noticed that the docs on one-to-one relationships suddenly switch to talking about many-to-one relationships then 180 back to one-to-one... this was a bit awkward to read.
Would the docs be improved if the whole many-to-one code example was removed? its identical to the second example in the many-to-one section just above.
**Versions.**
- SQLAlchemy: 1.4
**Additional context**
https://docs.sqlalchemy.org/en/14/orm/basic_relationships.html#one-to-one
| 1.0 | confusing docs around one-to-one relationships - **Describe the bug**
very minor docs only nitpick, I was trying to remind myself what `uselist=False` was called, when i noticed that the docs on one-to-one relationships suddenly switch to talking about many-to-one relationships then 180 back to one-to-one... this was a bit awkward to read.
Would the docs be improved if the whole many-to-one code example was removed? its identical to the second example in the many-to-one section just above.
**Versions.**
- SQLAlchemy: 1.4
**Additional context**
https://docs.sqlalchemy.org/en/14/orm/basic_relationships.html#one-to-one
| non_priority | confusing docs around one to one relationships describe the bug very minor docs only nitpick i was trying to remind myself what uselist false was called when i noticed that the docs on one to one relationships suddenly switch to talking about many to one relationships then back to one to one this was a bit awkward to read would the docs be improved if the whole many to one code example was removed its identical to the second example in the many to one section just above versions sqlalchemy additional context | 0 |
10,495 | 8,958,154,538 | IssuesEvent | 2019-01-27 11:55:42 | ionide/ionide-vscode-fsharp | https://api.github.com/repos/ionide/ionide-vscode-fsharp | closed | file not found if "fsacRuntime"="netcore" | bug fsac .netcore language services | File not found error if subject option is `netcore` in new ionide, `net` works as always before.
```
[17:49:15 DEBUG] RES (1314) <- {parse} in 43 ms: Kind={"info"}
Data="Request cancelled (exn was System.ComponentModel.Win32Exception (0x80004005): Das System kann die angegebene Datei nicht finden
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at FsAutoComplete.Utils.runProcess(FSharpFunc`2 log, String workingDir, String exePath, String args)
at Dotnet.ProjInfo.Inspect.msbuild[a](MSBuildExePath msbuildExe, FSharpFunc`2 run, String project, FSharpList`1 args)
at Dotnet.ProjInfo.Inspect.getProjectInfoOldSdk[a,b,c,d](FSharpFunc`2 log, FSharpFunc`2 msbuildExec, FSharpFunc`2 getArgs, FSharpList`1 additionalArgs, a projPath)
at FsAutoComplete.NETFrameworkInfoProvider.getInfoFromMsbuild[a](FSharpFunc`2 getArgs, FSharpList`1 additionalProps)
at FsAutoComplete.NETFrameworkInfoProvider.getInstalledNETVersions() in D:\\Programowanie\\ionide\\paket-files\\github.com\\fsharp\\FsAutoComplete\\src\\FsAutoComplete.Core\\NETFrameworkInfoProvider.fs:line 99
at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Lazy`1.CreateValue()
at FsAutoComplete.Environment.netReferecesAssembliesTFMLatest() in D:\\Programowanie\\ionide\\paket-files\\github.com\\fsharp\\FsAutoComplete\\src\\FsAutoComplete.Core\\Environment.fs:line 42
at <StartupCode$FsAutoComplete-Core>.$CompilerServiceInterface.GetProjectOptionsFromScript@328.Invoke(Unit unitVar) in D:\\Programowanie\\ionide\\paket-files\\github.com\\fsharp\\FsAutoComplete\\src\\FsAutoComplete.Core\\CompilerServiceInterface.fs:line 328
at Microsoft.FSharp.Control.AsyncBuilderImpl.callA@839.Invoke(AsyncParams`1 args))"
```
windows 10
VSCode: 1.18.1
Ionide: 3.13.0
dotnet --version: 2.0.2 | 1.0 | file not found if "fsacRuntime"="netcore" - File not found error if subject option is `netcore` in new ionide, `net` works as always before.
```
[17:49:15 DEBUG] RES (1314) <- {parse} in 43 ms: Kind={"info"}
Data="Request cancelled (exn was System.ComponentModel.Win32Exception (0x80004005): Das System kann die angegebene Datei nicht finden
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at FsAutoComplete.Utils.runProcess(FSharpFunc`2 log, String workingDir, String exePath, String args)
at Dotnet.ProjInfo.Inspect.msbuild[a](MSBuildExePath msbuildExe, FSharpFunc`2 run, String project, FSharpList`1 args)
at Dotnet.ProjInfo.Inspect.getProjectInfoOldSdk[a,b,c,d](FSharpFunc`2 log, FSharpFunc`2 msbuildExec, FSharpFunc`2 getArgs, FSharpList`1 additionalArgs, a projPath)
at FsAutoComplete.NETFrameworkInfoProvider.getInfoFromMsbuild[a](FSharpFunc`2 getArgs, FSharpList`1 additionalProps)
at FsAutoComplete.NETFrameworkInfoProvider.getInstalledNETVersions() in D:\\Programowanie\\ionide\\paket-files\\github.com\\fsharp\\FsAutoComplete\\src\\FsAutoComplete.Core\\NETFrameworkInfoProvider.fs:line 99
at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Lazy`1.CreateValue()
at FsAutoComplete.Environment.netReferecesAssembliesTFMLatest() in D:\\Programowanie\\ionide\\paket-files\\github.com\\fsharp\\FsAutoComplete\\src\\FsAutoComplete.Core\\Environment.fs:line 42
at <StartupCode$FsAutoComplete-Core>.$CompilerServiceInterface.GetProjectOptionsFromScript@328.Invoke(Unit unitVar) in D:\\Programowanie\\ionide\\paket-files\\github.com\\fsharp\\FsAutoComplete\\src\\FsAutoComplete.Core\\CompilerServiceInterface.fs:line 328
at Microsoft.FSharp.Control.AsyncBuilderImpl.callA@839.Invoke(AsyncParams`1 args))"
```
windows 10
VSCode: 1.18.1
Ionide: 3.13.0
dotnet --version: 2.0.2 | non_priority | file not found if fsacruntime netcore file not found error if subject option is netcore in new ionide net works as always before res parse in ms kind info data request cancelled exn was system componentmodel das system kann die angegebene datei nicht finden at system diagnostics process startwithcreateprocess processstartinfo startinfo at system diagnostics process start at fsautocomplete utils runprocess fsharpfunc log string workingdir string exepath string args at dotnet projinfo inspect msbuild msbuildexepath msbuildexe fsharpfunc run string project fsharplist args at dotnet projinfo inspect getprojectinfooldsdk fsharpfunc log fsharpfunc msbuildexec fsharpfunc getargs fsharplist additionalargs a projpath at fsautocomplete netframeworkinfoprovider getinfofrommsbuild fsharpfunc getargs fsharplist additionalprops at fsautocomplete netframeworkinfoprovider getinstallednetversions in d programowanie ionide paket files github com fsharp fsautocomplete src fsautocomplete core netframeworkinfoprovider fs line at system lazy viafactory lazythreadsafetymode mode end of stack trace from previous location where exception was thrown at system runtime exceptionservices exceptiondispatchinfo throw at system lazy createvalue at fsautocomplete environment netreferecesassembliestfmlatest in d programowanie ionide paket files github com fsharp fsautocomplete src fsautocomplete core environment fs line at compilerserviceinterface getprojectoptionsfromscript invoke unit unitvar in d programowanie ionide paket files github com fsharp fsautocomplete src fsautocomplete core compilerserviceinterface fs line at microsoft fsharp control asyncbuilderimpl calla invoke asyncparams args windows vscode ionide dotnet version | 0 |
86,659 | 8,042,451,995 | IssuesEvent | 2018-07-31 08:12:01 | ClassicWoW/Nefarian_1.12.1_Bugtracker | https://api.github.com/repos/ClassicWoW/Nefarian_1.12.1_Bugtracker | closed | wow error als Plündermeister im Raid | Mehr Input/Recherche/Tests nötig | Welches Verhalten wird beobachtet?
Fungiert man als Plündermeister im 20er/40er Raid kommt es nahezu jedes mal zu einem wow error, wenn der gesamte raid schon weiter gezogen ist.
Beispiel: lootverteilung bei viscidus in AQ40. Der Pm mountet nach lootvergabe auf und reitet dem Raid hinterher. Bevor man wieder in der standard Ebene eintrifft schließt sich das Spiel. Das selbe gilt bei fast jedem Boss in Zul Gurub. Da dieses Phänomen viele Spieler betrifft könnte das mal überprüft werden.
Wie sollte es sich verhalten?
Das sollte allgemein gar nicht passieren dürfen.
Schritte zur Reproduzierung
-
Zusätzliche Informationen (Screenshots, Videos, Klasse, Rasse, Level, etc.)
ein Video könnte, sofern erforderlich demnächst ergänzt werden.
Alle Kreaturen, Items, Objekte, Quests, Zauber etc. müssen aus unserer Datenbank verlinkt sein.
| 1.0 | wow error als Plündermeister im Raid - Welches Verhalten wird beobachtet?
Fungiert man als Plündermeister im 20er/40er Raid kommt es nahezu jedes mal zu einem wow error, wenn der gesamte raid schon weiter gezogen ist.
Beispiel: lootverteilung bei viscidus in AQ40. Der Pm mountet nach lootvergabe auf und reitet dem Raid hinterher. Bevor man wieder in der standard Ebene eintrifft schließt sich das Spiel. Das selbe gilt bei fast jedem Boss in Zul Gurub. Da dieses Phänomen viele Spieler betrifft könnte das mal überprüft werden.
Wie sollte es sich verhalten?
Das sollte allgemein gar nicht passieren dürfen.
Schritte zur Reproduzierung
-
Zusätzliche Informationen (Screenshots, Videos, Klasse, Rasse, Level, etc.)
ein Video könnte, sofern erforderlich demnächst ergänzt werden.
Alle Kreaturen, Items, Objekte, Quests, Zauber etc. müssen aus unserer Datenbank verlinkt sein.
| non_priority | wow error als plündermeister im raid welches verhalten wird beobachtet fungiert man als plündermeister im raid kommt es nahezu jedes mal zu einem wow error wenn der gesamte raid schon weiter gezogen ist beispiel lootverteilung bei viscidus in der pm mountet nach lootvergabe auf und reitet dem raid hinterher bevor man wieder in der standard ebene eintrifft schließt sich das spiel das selbe gilt bei fast jedem boss in zul gurub da dieses phänomen viele spieler betrifft könnte das mal überprüft werden wie sollte es sich verhalten das sollte allgemein gar nicht passieren dürfen schritte zur reproduzierung zusätzliche informationen screenshots videos klasse rasse level etc ein video könnte sofern erforderlich demnächst ergänzt werden alle kreaturen items objekte quests zauber etc müssen aus unserer datenbank verlinkt sein | 0 |
24,451 | 6,544,286,349 | IssuesEvent | 2017-09-03 14:18:28 | akamsteeg/AtleX.CommandLineArguments | https://api.github.com/repos/akamsteeg/AtleX.CommandLineArguments | closed | Replace temporary out variable with discard in CommandLineArguments. TryParse<T>(string[], out T) | code quality | In `CommandLineArguments. TryParse<T>(string[], out T)` we call the overload `CommandLineArguments. TryParse<T>(string[], out T, out IEnumerable<ValidationError>)` with a temporary out variable for the last parameter. However, C#7 has discards for that purpose and we should use that to make it clear we're not doing anything with that result. | 1.0 | Replace temporary out variable with discard in CommandLineArguments. TryParse<T>(string[], out T) - In `CommandLineArguments. TryParse<T>(string[], out T)` we call the overload `CommandLineArguments. TryParse<T>(string[], out T, out IEnumerable<ValidationError>)` with a temporary out variable for the last parameter. However, C#7 has discards for that purpose and we should use that to make it clear we're not doing anything with that result. | non_priority | replace temporary out variable with discard in commandlinearguments tryparse string out t in commandlinearguments tryparse string out t we call the overload commandlinearguments tryparse string out t out ienumerable with a temporary out variable for the last parameter however c has discards for that purpose and we should use that to make it clear we re not doing anything with that result | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.