Split (1)

train · 1.11M rows

Unnamed: 0 int64 0 832k	id float64 2.49B 32.1B	type stringclasses 1 value	created_at stringlengths 19 19	repo stringlengths 5 112	repo_url stringlengths 34 141	action stringclasses 3 values	title stringlengths 1 1k	labels stringlengths 4 1.38k	body stringlengths 1 262k	index stringclasses 16 values	text_combine stringlengths 96 262k	label stringclasses 2 values	text stringlengths 96 252k	binary_label int64 0 1
213,426	7,253,623,658	IssuesEvent	2018-02-16 06:59:05	STEP-tw/battleship-phoenix	https://api.github.com/repos/STEP-tw/battleship-phoenix	opened	Place a ship at center	High Priority medium	As a _player_ I want to _place a ship at centre_ So that I can _arrange my fleet_ Additional Details 1. Player have ships and ocean grid. Acceptance Criteria - [ ] Criteria 1 - Given _ocean grid and ships_ - When _i select a ship and place it on (4,4)_ - Then _ship should be placed on that position_ - [ ] Criteria 2 - Given _ocean grid and ships_ - When _i select a ship and place it on (4,4)_ - Then _should disappear from dock_	1.0	Place a ship at center - As a _player_ I want to _place a ship at centre_ So that I can _arrange my fleet_ Additional Details 1. Player have ships and ocean grid. Acceptance Criteria - [ ] Criteria 1 - Given _ocean grid and ships_ - When _i select a ship and place it on (4,4)_ - Then _ship should be placed on that position_ - [ ] Criteria 2 - Given _ocean grid and ships_ - When _i select a ship and place it on (4,4)_ - Then _should disappear from dock_	priority	place a ship at center as a player i want to place a ship at centre so that i can arrange my fleet additional details player have ships and ocean grid acceptance criteria criteria given ocean grid and ships when i select a ship and place it on then ship should be placed on that position criteria given ocean grid and ships when i select a ship and place it on then should disappear from dock	1
228,332	17,456,709,101	IssuesEvent	2021-08-06 03:05:38	rkyv/rkyv	https://api.github.com/repos/rkyv/rkyv	closed	rkyv: test failed on s390x and armv7hl	bug documentation	Hi! Test failed on fedora koji. The latest version was used. https://kojipkgs.fedoraproject.org//work/tasks/2677/73362677/build.log https://kojipkgs.fedoraproject.org//work/tasks/2672/73362672/build.log failures: ---- src/with/mod.rs - with::Atomic (line 286) stdout ---- error[E0277]: the trait bound `Atomic: ArchiveWith<AtomicU32>` is not satisfied --> src/with/mod.rs:290:10 \| 7 \| #[derive(Archive)] \| ^^^^^^^ the trait `ArchiveWith<AtomicU32>` is not implemented for `Atomic` \| = note: required because of the requirements on the impl of `Archive` for `With<AtomicU32, Atomic>` = help: see issue #48214 = help: add `#![feature(trivial_bounds)]` to the crate attributes to enable = note: this error originates in the derive macro `Archive` (in Nightly builds, run with -Z macro-backtrace for more info) error: aborting due to previous error	1.0	rkyv: test failed on s390x and armv7hl - Hi! Test failed on fedora koji. The latest version was used. https://kojipkgs.fedoraproject.org//work/tasks/2677/73362677/build.log https://kojipkgs.fedoraproject.org//work/tasks/2672/73362672/build.log failures: ---- src/with/mod.rs - with::Atomic (line 286) stdout ---- error[E0277]: the trait bound `Atomic: ArchiveWith<AtomicU32>` is not satisfied --> src/with/mod.rs:290:10 \| 7 \| #[derive(Archive)] \| ^^^^^^^ the trait `ArchiveWith<AtomicU32>` is not implemented for `Atomic` \| = note: required because of the requirements on the impl of `Archive` for `With<AtomicU32, Atomic>` = help: see issue #48214 = help: add `#![feature(trivial_bounds)]` to the crate attributes to enable = note: this error originates in the derive macro `Archive` (in Nightly builds, run with -Z macro-backtrace for more info) error: aborting due to previous error	non_priority	rkyv test failed on and hi test failed on fedora koji the latest version was used failures src with mod rs with atomic line stdout error the trait bound atomic archivewith is not satisfied src with mod rs the trait archivewith is not implemented for atomic note required because of the requirements on the impl of archive for with help see issue help add to the crate attributes to enable note this error originates in the derive macro archive in nightly builds run with z macro backtrace for more info error aborting due to previous error	0
213,594	24,009,227,895	IssuesEvent	2022-09-14 17:14:41	sast-automation-dev/hackme-23	https://api.github.com/repos/sast-automation-dev/hackme-23	opened	rails-3.0.9.gem: 52 vulnerabilities (highest severity is: 8.6)	security vulnerability	<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>rails-3.0.9.gem</b></p></summary> <p>Ruby on Rails is a full-stack web framework optimized for programmer happiness and sustainable productivity. It encourages beautiful code by favoring convention over configuration.</p> <p>Library home page: <a href="https://rubygems.org/gems/rails-3.0.9.gem">https://rubygems.org/gems/rails-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /m/ruby/2.7.0/cache/rails-3.0.9.gem</p> <p> <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p></details> ## Vulnerabilities \| CVE \| Severity \| <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS \| Dependency \| Type \| Fixed in \| Remediation Available \| \| ------------- \| ------------- \| ----- \| ----- \| ----- \| --- \| --- \| \| [CVE-2020-8161](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8161) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 8.6 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2020-8184](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8184) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2021-22885](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-22885) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2019-5418](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-5418) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2016-0752](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-0752) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| rails-3.0.9.gem \| Direct \| 3.2.22.1,4.1.14.1,4.2.5.1,5.0.0.beta1.1 \| ✅ \| \| [CVE-2016-0751](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-0751) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| detected in multiple dependencies \| Direct \| 3.2.22.1,4.1.14.1,4.2.5.1,5.0.0.beta1.1 \| ✅ \| \| [CVE-2014-10077](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-10077) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| i18n-0.5.0.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-0156](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0156) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| activesupport-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-2695](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-2695) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| activerecord-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-6496](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-6496) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| activerecord-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2016-2098](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2098) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| detected in multiple dependencies \| Direct \| 3.2.22.2,4.1.14.2,4.2.5.2 \| ✅ \| \| [CVE-2013-0333](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0333) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| activesupport-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2014-3482](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-3482) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| activerecord-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-2140](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-2140) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| mail-2.2.19.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-6417](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-6417) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-3221](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-3221) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| activerecord-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-0155](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0155) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| activerecord-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-2660](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-2660) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2020-8167](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8167) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| rails-3.0.9.gem \| Direct \| 6.0.3.1,5.2.4.3 \| ✅ \| \| [CVE-2010-3299](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2010-3299) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| rails-3.0.9.gem \| Direct \| rails - 5.2.0.beta1 \| ✅ \| \| [CVE-2020-8130](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8130) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.4 \| rake-0.9.2.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2018-16471](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16471) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.1 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2016-6316](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-6316) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.1 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2015-9097](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-9097) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.1 \| mail-2.2.19.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2019-16782](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16782) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.9 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-0263](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0263) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.6 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2011-2930](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2011-2930) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.5 \| rails-3.0.9.gem \| Direct \| 2.3.13,3.0.10,3.1.0.rc5 \| ✅ \| \| [CVE-2013-6414](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-6414) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [WS-2017-0283](https://github.com/rack/rack/commit/6a0e0ee8fcd982bccf30077ec94cb55018bbed91) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-3424](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-3424) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-2139](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-2139) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| mail-2.2.19.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2011-5036](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2011-5036) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2015-3225](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-3225) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-2661](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-2661) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| activerecord-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2016-2097](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2097) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| rails-3.0.9.gem \| Direct \| 3.2.22.2,4.1.14.2 \| ✅ \| \| [CVE-2011-2929](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2011-2929) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2014-0082](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0082) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-6415](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-6415) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-3463](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-3463) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-3465](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-3465) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-3464](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-3464) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| activesupport-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-1855](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-1855) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-1857](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-1857) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2011-2932](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2011-2932) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| rails-3.0.9.gem \| Direct \| 2.3.13,3.0.10,3.1.0.rc5 \| ✅ \| \| [CVE-2012-6109](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-6109) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-4491](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-4491) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-4492](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-4492) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| i18n-0.5.0.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-0256](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0256) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| rdoc-3.8.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2014-0130](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0130) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2015-7576](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-7576) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-0184](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0184) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2014-0081](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0081) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| ## Details > Partial details (21 vulnerabilities) are displayed below due to a content size limitation in GitHub. To view information on the remaining vulnerabilities, navigate to the Mend Application.<br> <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-8161</summary> ### Vulnerable Library - <b>rack-1.2.3.gem</b></p> <p>Rack provides minimal, modular and adaptable interface for developing web applications in Ruby. By wrapping HTTP requests and responses in the simplest way possible, it unifies and distills the API for web servers, web frameworks, and software in between (the so-called middleware) into a single method call. Also see http://rack.rubyforge.org. </p> <p>Library home page: <a href="https://rubygems.org/gems/rack-1.2.3.gem">https://rubygems.org/gems/rack-1.2.3.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/rack-1.2.3.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - actionpack-3.0.9.gem - :x: rack-1.2.3.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A directory traversal vulnerability exists in rack < 2.2.0 that allows an attacker perform directory traversal vulnerability in the Rack::Directory app that is bundled with Rack which could result in information disclosure. <p>Publish Date: 2020-07-02 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8161>CVE-2020-8161</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>8.6</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Changed - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Release Date: 2020-10-05</p> <p>Fix Resolution: 2.2.0,2.1.3</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-8184</summary> ### Vulnerable Library - <b>rack-1.2.3.gem</b></p> <p>Rack provides minimal, modular and adaptable interface for developing web applications in Ruby. By wrapping HTTP requests and responses in the simplest way possible, it unifies and distills the API for web servers, web frameworks, and software in between (the so-called middleware) into a single method call. Also see http://rack.rubyforge.org. </p> <p>Library home page: <a href="https://rubygems.org/gems/rack-1.2.3.gem">https://rubygems.org/gems/rack-1.2.3.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/rack-1.2.3.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - actionpack-3.0.9.gem - :x: rack-1.2.3.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A reliance on cookies without validation/integrity check security vulnerability exists in rack < 2.2.3, rack < 2.1.4 that makes it is possible for an attacker to forge a secure or host-only cookie prefix. <p>Publish Date: 2020-06-19 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8184>CVE-2020-8184</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://groups.google.com/forum/#!topic/rubyonrails-security/OWtmozPH9Ak">https://groups.google.com/forum/#!topic/rubyonrails-security/OWtmozPH9Ak</a></p> <p>Release Date: 2020-10-05</p> <p>Fix Resolution: rack - 2.1.4, 2.2.3</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-22885</summary> ### Vulnerable Library - <b>actionpack-3.0.9.gem</b></p> <p>Web apps on Rails. Simple, battle-tested conventions for building and testing MVC web applications. Works with any Rack-compatible server.</p> <p>Library home page: <a href="https://rubygems.org/gems/actionpack-3.0.9.gem">https://rubygems.org/gems/actionpack-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/actionpack-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: actionpack-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A possible information disclosure / unintended method execution vulnerability in Action Pack >= 2.0.0 when using the `redirect_to` or `polymorphic_url`helper with untrusted user input. <p>Publish Date: 2021-05-27 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-22885>CVE-2021-22885</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-hjg4-8q5f-x6fm">https://github.com/advisories/GHSA-hjg4-8q5f-x6fm</a></p> <p>Release Date: 2021-05-27</p> <p>Fix Resolution: actionpack - 5.2.4.6,5.2.6,6.0.3.7,6.1.3.2</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-5418</summary> ### Vulnerable Library - <b>actionpack-3.0.9.gem</b></p> <p>Web apps on Rails. Simple, battle-tested conventions for building and testing MVC web applications. Works with any Rack-compatible server.</p> <p>Library home page: <a href="https://rubygems.org/gems/actionpack-3.0.9.gem">https://rubygems.org/gems/actionpack-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/actionpack-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: actionpack-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> There is a File Content Disclosure vulnerability in Action View <5.2.2.1, <5.1.6.2, <5.0.7.2, <4.2.11.1 and v3 where specially crafted accept headers can cause contents of arbitrary files on the target system's filesystem to be exposed. <p>Publish Date: 2019-03-27 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-5418>CVE-2019-5418</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://weblog.rubyonrails.org/2019/3/13/Rails-4-2-5-1-5-1-6-2-have-been-released/">https://weblog.rubyonrails.org/2019/3/13/Rails-4-2-5-1-5-1-6-2-have-been-released/</a></p> <p>Release Date: 2020-10-16</p> <p>Fix Resolution: 4.2.11.1, 5.0.7.2, 5.1.6.2, 5.2.2.1</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-0752</summary> ### Vulnerable Library - <b>rails-3.0.9.gem</b></p> <p>Ruby on Rails is a full-stack web framework optimized for programmer happiness and sustainable productivity. It encourages beautiful code by favoring convention over configuration.</p> <p>Library home page: <a href="https://rubygems.org/gems/rails-3.0.9.gem">https://rubygems.org/gems/rails-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /m/ruby/2.7.0/cache/rails-3.0.9.gem</p> <p> Dependency Hierarchy: - :x: rails-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Directory traversal vulnerability in Action View in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 allows remote attackers to read arbitrary files by leveraging an application's unrestricted use of the render method and providing a .. (dot dot) in a pathname. <p>Publish Date: 2016-02-16 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-0752>CVE-2016-0752</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-0752">https://nvd.nist.gov/vuln/detail/CVE-2016-0752</a></p> <p>Release Date: 2016-02-16</p> <p>Fix Resolution: 3.2.22.1,4.1.14.1,4.2.5.1,5.0.0.beta1.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-0751</summary> ### Vulnerable Libraries - <b>rails-3.0.9.gem</b>, <b>actionpack-3.0.9.gem</b></p> <p> ### <b>rails-3.0.9.gem</b></p> <p>Ruby on Rails is a full-stack web framework optimized for programmer happiness and sustainable productivity. It encourages beautiful code by favoring convention over configuration.</p> <p>Library home page: <a href="https://rubygems.org/gems/rails-3.0.9.gem">https://rubygems.org/gems/rails-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /m/ruby/2.7.0/cache/rails-3.0.9.gem</p> <p> Dependency Hierarchy: - :x: rails-3.0.9.gem (Vulnerable Library) ### <b>actionpack-3.0.9.gem</b></p> <p>Web apps on Rails. Simple, battle-tested conventions for building and testing MVC web applications. Works with any Rack-compatible server.</p> <p>Library home page: <a href="https://rubygems.org/gems/actionpack-3.0.9.gem">https://rubygems.org/gems/actionpack-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/actionpack-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: actionpack-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> actionpack/lib/action_dispatch/http/mime_type.rb in Action Pack in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 does not properly restrict use of the MIME type cache, which allows remote attackers to cause a denial of service (memory consumption) via a crafted HTTP Accept header. <p>Publish Date: 2016-02-16 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-0751>CVE-2016-0751</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-0751">https://nvd.nist.gov/vuln/detail/CVE-2016-0751</a></p> <p>Release Date: 2016-02-16</p> <p>Fix Resolution: 3.2.22.1,4.1.14.1,4.2.5.1,5.0.0.beta1.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2014-10077</summary> ### Vulnerable Library - <b>i18n-0.5.0.gem</b></p> <p>New wave Internationalization support for Ruby.</p> <p>Library home page: <a href="https://rubygems.org/gems/i18n-0.5.0.gem">https://rubygems.org/gems/i18n-0.5.0.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/i18n-0.5.0.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - activeresource-3.0.9.gem - activemodel-3.0.9.gem - :x: i18n-0.5.0.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Hash#slice in lib/i18n/core_ext/hash.rb in the i18n gem before 0.8.0 for Ruby allows remote attackers to cause a denial of service (application crash) via a call in a situation where :some_key is present in keep_keys but not present in the hash. <p>Publish Date: 2018-11-06 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-10077>CVE-2014-10077</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-10077">https://nvd.nist.gov/vuln/detail/CVE-2014-10077</a></p> <p>Release Date: 2018-11-06</p> <p>Fix Resolution: 0.8.0</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2013-0156</summary> ### Vulnerable Library - <b>activesupport-3.0.9.gem</b></p> <p>A toolkit of support libraries and Ruby core extensions extracted from the Rails framework. Rich support for multibyte strings, internationalization, time zones, and testing.</p> <p>Library home page: <a href="https://rubygems.org/gems/activesupport-3.0.9.gem">https://rubygems.org/gems/activesupport-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/activesupport-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: activesupport-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> active_support/core_ext/hash/conversions.rb in Ruby on Rails before 2.3.15, 3.0.x before 3.0.19, 3.1.x before 3.1.10, and 3.2.x before 3.2.11 does not properly restrict casts of string values, which allows remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) involving nested XML entity references, by leveraging Action Pack support for (1) YAML type conversion or (2) Symbol type conversion. <p>Publish Date: 2013-01-13 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0156>CVE-2013-0156</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2013-0156">https://nvd.nist.gov/vuln/detail/CVE-2013-0156</a></p> <p>Release Date: 2013-01-13</p> <p>Fix Resolution: 2.3.15,3.0.19,3.1.10,3.2.11</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2012-2695</summary> ### Vulnerable Library - <b>activerecord-3.0.9.gem</b></p> <p>Databases on Rails. Build a persistent domain model by mapping database tables to Ruby classes. Strong conventions for associations, validations, aggregations, migrations, and testing come baked-in.</p> <p>Library home page: <a href="https://rubygems.org/gems/activerecord-3.0.9.gem">https://rubygems.org/gems/activerecord-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/activerecord-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: activerecord-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The Active Record component in Ruby on Rails before 3.0.14, 3.1.x before 3.1.6, and 3.2.x before 3.2.6 does not properly implement the passing of request data to a where method in an ActiveRecord class, which allows remote attackers to conduct certain SQL injection attacks via nested query parameters that leverage improper handling of nested hashes, a related issue to CVE-2012-2661. <p>Publish Date: 2012-06-22 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-2695>CVE-2012-2695</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2012-2695">https://nvd.nist.gov/vuln/detail/CVE-2012-2695</a></p> <p>Release Date: 2012-06-22</p> <p>Fix Resolution: 3.0.14,3.1.6,3.2.6</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2012-6496</summary> ### Vulnerable Library - <b>activerecord-3.0.9.gem</b></p> <p>Databases on Rails. Build a persistent domain model by mapping database tables to Ruby classes. Strong conventions for associations, validations, aggregations, migrations, and testing come baked-in.</p> <p>Library home page: <a href="https://rubygems.org/gems/activerecord-3.0.9.gem">https://rubygems.org/gems/activerecord-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/activerecord-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: activerecord-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> SQL injection vulnerability in the Active Record component in Ruby on Rails before 3.0.18, 3.1.x before 3.1.9, and 3.2.x before 3.2.10 allows remote attackers to execute arbitrary SQL commands via a crafted request that leverages incorrect behavior of dynamic finders in applications that can use unexpected data types in certain find_by_ method calls. <p>Publish Date: 2013-01-04 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-6496>CVE-2012-6496</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2012-6496">https://nvd.nist.gov/vuln/detail/CVE-2012-6496</a></p> <p>Release Date: 2013-01-04</p> <p>Fix Resolution: 3.0.18,3.1.9,3.2.10</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-2098</summary> ### Vulnerable Libraries - <b>rails-3.0.9.gem</b>, <b>actionpack-3.0.9.gem</b></p> <p> ### <b>rails-3.0.9.gem</b></p> <p>Ruby on Rails is a full-stack web framework optimized for programmer happiness and sustainable productivity. It encourages beautiful code by favoring convention over configuration.</p> <p>Library home page: <a href="https://rubygems.org/gems/rails-3.0.9.gem">https://rubygems.org/gems/rails-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /m/ruby/2.7.0/cache/rails-3.0.9.gem</p> <p> Dependency Hierarchy: - :x: rails-3.0.9.gem (Vulnerable Library) ### <b>actionpack-3.0.9.gem</b></p> <p>Web apps on Rails. Simple, battle-tested conventions for building and testing MVC web applications. Works with any Rack-compatible server.</p> <p>Library home page: <a href="https://rubygems.org/gems/actionpack-3.0.9.gem">https://rubygems.org/gems/actionpack-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/actionpack-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: actionpack-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Action Pack in Ruby on Rails before 3.2.22.2, 4.x before 4.1.14.2, and 4.2.x before 4.2.5.2 allows remote attackers to execute arbitrary Ruby code by leveraging an application's unrestricted use of the render method. <p>Publish Date: 2016-04-07 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2098>CVE-2016-2098</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-2098">https://nvd.nist.gov/vuln/detail/CVE-2016-2098</a></p> <p>Release Date: 2016-04-07</p> <p>Fix Resolution: 3.2.22.2,4.1.14.2,4.2.5.2</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2013-0333</summary> ### Vulnerable Library - <b>activesupport-3.0.9.gem</b></p> <p>A toolkit of support libraries and Ruby core extensions extracted from the Rails framework. Rich support for multibyte strings, internationalization, time zones, and testing.</p> <p>Library home page: <a href="https://rubygems.org/gems/activesupport-3.0.9.gem">https://rubygems.org/gems/activesupport-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/activesupport-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: activesupport-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> lib/active_support/json/backends/yaml.rb in Ruby on Rails 2.3.x before 2.3.16 and 3.0.x before 3.0.20 does not properly convert JSON data to YAML data for processing by a YAML parser, which allows remote attackers to execute arbitrary code, conduct SQL injection attacks, or bypass authentication via crafted data that triggers unsafe decoding, a different vulnerability than CVE-2013-0156. <p>Publish Date: 2013-01-30 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0333>CVE-2013-0333</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2013-0333">https://nvd.nist.gov/vuln/detail/CVE-2013-0333</a></p> <p>Release Date: 2013-01-30</p> <p>Fix Resolution: 2.3.16,3.0.20</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2014-3482</summary> ### Vulnerable Library - <b>activerecord-3.0.9.gem</b></p> <p>Databases on Rails. Build a persistent domain model by mapping database tables to Ruby classes. Strong conventions for associations, validations, aggregations, migrations, and testing come baked-in.</p> <p>Library home page: <a href="https://rubygems.org/gems/activerecord-3.0.9.gem">https://rubygems.org/gems/activerecord-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/activerecord-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: activerecord-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> SQL injection vulnerability in activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb in the PostgreSQL adapter for Active Record in Ruby on Rails 2.x and 3.x before 3.2.19 allows remote attackers to execute arbitrary SQL commands by leveraging improper bitstring quoting. <p>Publish Date: 2014-07-07 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-3482>CVE-2014-3482</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-3482">https://nvd.nist.gov/vuln/detail/CVE-2014-3482</a></p> <p>Release Date: 2014-07-07</p> <p>Fix Resolution: 3.2.19</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2012-2140</summary> ### Vulnerable Library - <b>mail-2.2.19.gem</b></p> <p>A really Ruby Mail handler.</p> <p>Library home page: <a href="https://rubygems.org/gems/mail-2.2.19.gem">https://rubygems.org/gems/mail-2.2.19.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/mail-2.2.19.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - actionmailer-3.0.9.gem - :x: mail-2.2.19.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The Mail gem before 2.4.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a (1) sendmail or (2) exim delivery. <p>Publish Date: 2012-07-18 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-2140>CVE-2012-2140</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2012-2140">https://nvd.nist.gov/vuln/detail/CVE-2012-2140</a></p> <p>Release Date: 2012-07-18</p> <p>Fix Resolution: 2.4.3</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2013-6417</summary> ### Vulnerable Library - <b>actionpack-3.0.9.gem</b></p> <p>Web apps on Rails. Simple, battle-tested conventions for building and testing MVC web applications. Works with any Rack-compatible server.</p> <p>Library home page: <a href="https://rubygems.org/gems/actionpack-3.0.9.gem">https://rubygems.org/gems/actionpack-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/actionpack-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: actionpack-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> actionpack/lib/action_dispatch/http/request.rb in Ruby on Rails before 3.2.16 and 4.x before 4.0.2 does not properly consider differences in parameter handling between the Active Record component and the JSON implementation, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks or trigger missing WHERE clauses via a crafted request that leverages (1) third-party Rack middleware or (2) custom Rack middleware. NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-0155. <p>Publish Date: 2013-12-07 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-6417>CVE-2013-6417</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <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: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2013-6417">https://nvd.nist.gov/vuln/detail/CVE-2013-6417</a></p> <p>Release Date: 2013-12-07</p> <p>Fix Resolution: 3.2.16,4.0.2</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2013-3221</summary> ### Vulnerable Library - <b>activerecord-3.0.9.gem</b></p> <p>Databases on Rails. Build a persistent domain model by mapping database tables to Ruby classes. Strong conventions for associations, validations, aggregations, migrations, and testing come baked-in.</p> <p>Library home page: <a href="https://rubygems.org/gems/activerecord-3.0.9.gem">https://rubygems.org/gems/activerecord-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/activerecord-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: activerecord-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The Active Record component in Ruby on Rails 2.3.x, 3.0.x, 3.1.x, and 3.2.x does not ensure that the declared data type of a database column is used during comparisons of input values to stored values in that column, which makes it easier for remote attackers to conduct data-type injection attacks against Ruby on Rails applications via a crafted value, as demonstrated by unintended interaction between the "typed XML" feature and a MySQL database. <p>Publish Date: 2013-04-22 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-3221>CVE-2013-3221</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <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: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-3221">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-3221</a></p> <p>Release Date: 2013-04-22</p> <p>Fix Resolution: 4.0.0.rc1</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2013-0155</summary> ### Vulnerable Library - <b>activerecord-3.0.9.gem</b></p> <p>Databases on Rails. Build a persistent domain model by mapping database tables to Ruby classes. Strong conventions for associations, validations, aggregations, migrations, and testing come baked-in.</p> <p>Library home page: <a href="https://rubygems.org/gems/activerecord-3.0.9.gem">https://rubygems.org/gems/activerecord-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/activerecord-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: activerecord-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Ruby on Rails 3.0.x before 3.0.19, 3.1.x before 3.1.10, and 3.2.x before 3.2.11 does not properly consider differences in parameter handling between the Active Record component and the JSON implementation, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks or trigger missing WHERE clauses via a crafted request, as demonstrated by certain "[nil]" values, a related issue to CVE-2012-2660 and CVE-2012-2694. <p>Publish Date: 2013-01-13 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0155>CVE-2013-0155</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <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: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2013-0155">https://nvd.nist.gov/vuln/detail/CVE-2013-0155</a></p> <p>Release Date: 2013-01-13</p> <p>Fix Resolution: 3.0.19,3.1.10,3.2.11</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2012-2660</summary> ### Vulnerable Library - <b>actionpack-3.0.9.gem</b></p> <p>Web apps on Rails. Simple, battle-tested conventions for building and testing MVC web applications. Works with any Rack-compatible server.</p> <p>Library home page: <a href="https://rubygems.org/gems/actionpack-3.0.9.gem">https://rubygems.org/gems/actionpack-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/actionpack-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: actionpack-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> actionpack/lib/action_dispatch/http/request.rb in Ruby on Rails before 3.0.13, 3.1.x before 3.1.5, and 3.2.x before 3.2.4 does not properly consider differences in parameter handling between the Active Record component and the Rack interface, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks via a crafted request, as demonstrated by certain "[nil]" values, a related issue to CVE-2012-2694. <p>Publish Date: 2012-06-22 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-2660>CVE-2012-2660</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <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: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2012-2660">https://nvd.nist.gov/vuln/detail/CVE-2012-2660</a></p> <p>Release Date: 2012-06-22</p> <p>Fix Resolution: 3.0.13,3.1.5,3.2.4</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-8167</summary> ### Vulnerable Library - <b>rails-3.0.9.gem</b></p> <p>Ruby on Rails is a full-stack web framework optimized for programmer happiness and sustainable productivity. It encourages beautiful code by favoring convention over configuration.</p> <p>Library home page: <a href="https://rubygems.org/gems/rails-3.0.9.gem">https://rubygems.org/gems/rails-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /m/ruby/2.7.0/cache/rails-3.0.9.gem</p> <p> Dependency Hierarchy: - :x: rails-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A CSRF vulnerability exists in rails <= 6.0.3 rails-ujs module that could allow attackers to send CSRF tokens to wrong domains. <p>Publish Date: 2020-06-19 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8167>CVE-2020-8167</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://rubygems.org/gems/rails/versions/6.0.3.1">https://rubygems.org/gems/rails/versions/6.0.3.1</a></p> <p>Release Date: 2020-06-19</p> <p>Fix Resolution: 6.0.3.1,5.2.4.3</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2010-3299</summary> ### Vulnerable Library - <b>rails-3.0.9.gem</b></p> <p>Ruby on Rails is a full-stack web framework optimized for programmer happiness and sustainable productivity. It encourages beautiful code by favoring convention over configuration.</p> <p>Library home page: <a href="https://rubygems.org/gems/rails-3.0.9.gem">https://rubygems.org/gems/rails-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /m/ruby/2.7.0/cache/rails-3.0.9.gem</p> <p> Dependency Hierarchy: - :x: rails-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The encrypt/decrypt functions in Ruby on Rails 2.3 are vulnerable to padding oracle attacks. <p>Publish Date: 2019-11-12 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2010-3299>CVE-2010-3299</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3299">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3299</a></p> <p>Release Date: 2019-11-12</p> <p>Fix Resolution: rails - 5.2.0.beta1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-8130</summary> ### Vulnerable Library - <b>rake-0.9.2.gem</b></p> <p> Rake is a Make-like program implemented in Ruby. Tasks and dependencies are specified in standard Ruby syntax. </p> <p>Library home page: <a href="https://rubygems.org/gems/rake-0.9.2.gem">https://rubygems.org/gems/rake-0.9.2.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/rake-0.9.2.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - railties-3.0.9.gem - :x: rake-0.9.2.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> There is an OS command injection vulnerability in Ruby Rake < 12.3.3 in Rake::FileList when supplying a filename that begins with the pipe character `\|`. <p>Publish Date: 2020-02-24 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8130>CVE-2020-8130</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.4</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: High - Privileges Required: High - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8130">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8130</a></p> <p>Release Date: 2020-06-30</p> <p>Fix Resolution: v12.3.3</p> </p> <p></p> </details> *** <p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>	True	rails-3.0.9.gem: 52 vulnerabilities (highest severity is: 8.6) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>rails-3.0.9.gem</b></p></summary> <p>Ruby on Rails is a full-stack web framework optimized for programmer happiness and sustainable productivity. It encourages beautiful code by favoring convention over configuration.</p> <p>Library home page: <a href="https://rubygems.org/gems/rails-3.0.9.gem">https://rubygems.org/gems/rails-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /m/ruby/2.7.0/cache/rails-3.0.9.gem</p> <p> <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p></details> ## Vulnerabilities \| CVE \| Severity \| <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS \| Dependency \| Type \| Fixed in \| Remediation Available \| \| ------------- \| ------------- \| ----- \| ----- \| ----- \| --- \| --- \| \| [CVE-2020-8161](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8161) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 8.6 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2020-8184](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8184) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2021-22885](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-22885) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2019-5418](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-5418) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2016-0752](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-0752) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| rails-3.0.9.gem \| Direct \| 3.2.22.1,4.1.14.1,4.2.5.1,5.0.0.beta1.1 \| ✅ \| \| [CVE-2016-0751](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-0751) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| detected in multiple dependencies \| Direct \| 3.2.22.1,4.1.14.1,4.2.5.1,5.0.0.beta1.1 \| ✅ \| \| [CVE-2014-10077](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-10077) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| i18n-0.5.0.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-0156](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0156) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| activesupport-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-2695](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-2695) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| activerecord-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-6496](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-6496) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| activerecord-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2016-2098](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2098) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| detected in multiple dependencies \| Direct \| 3.2.22.2,4.1.14.2,4.2.5.2 \| ✅ \| \| [CVE-2013-0333](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0333) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| activesupport-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2014-3482](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-3482) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| activerecord-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-2140](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-2140) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| mail-2.2.19.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-6417](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-6417) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-3221](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-3221) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| activerecord-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-0155](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0155) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| activerecord-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-2660](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-2660) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2020-8167](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8167) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| rails-3.0.9.gem \| Direct \| 6.0.3.1,5.2.4.3 \| ✅ \| \| [CVE-2010-3299](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2010-3299) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| rails-3.0.9.gem \| Direct \| rails - 5.2.0.beta1 \| ✅ \| \| [CVE-2020-8130](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8130) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.4 \| rake-0.9.2.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2018-16471](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16471) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.1 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2016-6316](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-6316) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.1 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2015-9097](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-9097) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.1 \| mail-2.2.19.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2019-16782](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16782) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.9 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-0263](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0263) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.6 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2011-2930](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2011-2930) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.5 \| rails-3.0.9.gem \| Direct \| 2.3.13,3.0.10,3.1.0.rc5 \| ✅ \| \| [CVE-2013-6414](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-6414) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [WS-2017-0283](https://github.com/rack/rack/commit/6a0e0ee8fcd982bccf30077ec94cb55018bbed91) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-3424](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-3424) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-2139](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-2139) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| mail-2.2.19.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2011-5036](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2011-5036) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2015-3225](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-3225) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-2661](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-2661) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| activerecord-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2016-2097](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2097) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| rails-3.0.9.gem \| Direct \| 3.2.22.2,4.1.14.2 \| ✅ \| \| [CVE-2011-2929](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2011-2929) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2014-0082](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0082) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-6415](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-6415) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-3463](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-3463) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-3465](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-3465) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2012-3464](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-3464) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| activesupport-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-1855](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-1855) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-1857](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-1857) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2011-2932](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2011-2932) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| rails-3.0.9.gem \| Direct \| 2.3.13,3.0.10,3.1.0.rc5 \| ✅ \| \| [CVE-2012-6109](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-6109) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-4491](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-4491) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-4492](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-4492) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| i18n-0.5.0.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-0256](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0256) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| rdoc-3.8.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2014-0130](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0130) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2015-7576](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-7576) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2013-0184](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0184) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| rack-1.2.3.gem \| Transitive \| N/A \| ❌ \| \| [CVE-2014-0081](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0081) \| <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low \| 3.7 \| actionpack-3.0.9.gem \| Transitive \| N/A \| ❌ \| ## Details > Partial details (21 vulnerabilities) are displayed below due to a content size limitation in GitHub. To view information on the remaining vulnerabilities, navigate to the Mend Application.<br> <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-8161</summary> ### Vulnerable Library - <b>rack-1.2.3.gem</b></p> <p>Rack provides minimal, modular and adaptable interface for developing web applications in Ruby. By wrapping HTTP requests and responses in the simplest way possible, it unifies and distills the API for web servers, web frameworks, and software in between (the so-called middleware) into a single method call. Also see http://rack.rubyforge.org. </p> <p>Library home page: <a href="https://rubygems.org/gems/rack-1.2.3.gem">https://rubygems.org/gems/rack-1.2.3.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/rack-1.2.3.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - actionpack-3.0.9.gem - :x: rack-1.2.3.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A directory traversal vulnerability exists in rack < 2.2.0 that allows an attacker perform directory traversal vulnerability in the Rack::Directory app that is bundled with Rack which could result in information disclosure. <p>Publish Date: 2020-07-02 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8161>CVE-2020-8161</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>8.6</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Changed - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Release Date: 2020-10-05</p> <p>Fix Resolution: 2.2.0,2.1.3</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-8184</summary> ### Vulnerable Library - <b>rack-1.2.3.gem</b></p> <p>Rack provides minimal, modular and adaptable interface for developing web applications in Ruby. By wrapping HTTP requests and responses in the simplest way possible, it unifies and distills the API for web servers, web frameworks, and software in between (the so-called middleware) into a single method call. Also see http://rack.rubyforge.org. </p> <p>Library home page: <a href="https://rubygems.org/gems/rack-1.2.3.gem">https://rubygems.org/gems/rack-1.2.3.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/rack-1.2.3.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - actionpack-3.0.9.gem - :x: rack-1.2.3.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A reliance on cookies without validation/integrity check security vulnerability exists in rack < 2.2.3, rack < 2.1.4 that makes it is possible for an attacker to forge a secure or host-only cookie prefix. <p>Publish Date: 2020-06-19 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8184>CVE-2020-8184</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://groups.google.com/forum/#!topic/rubyonrails-security/OWtmozPH9Ak">https://groups.google.com/forum/#!topic/rubyonrails-security/OWtmozPH9Ak</a></p> <p>Release Date: 2020-10-05</p> <p>Fix Resolution: rack - 2.1.4, 2.2.3</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-22885</summary> ### Vulnerable Library - <b>actionpack-3.0.9.gem</b></p> <p>Web apps on Rails. Simple, battle-tested conventions for building and testing MVC web applications. Works with any Rack-compatible server.</p> <p>Library home page: <a href="https://rubygems.org/gems/actionpack-3.0.9.gem">https://rubygems.org/gems/actionpack-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/actionpack-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: actionpack-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A possible information disclosure / unintended method execution vulnerability in Action Pack >= 2.0.0 when using the `redirect_to` or `polymorphic_url`helper with untrusted user input. <p>Publish Date: 2021-05-27 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-22885>CVE-2021-22885</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-hjg4-8q5f-x6fm">https://github.com/advisories/GHSA-hjg4-8q5f-x6fm</a></p> <p>Release Date: 2021-05-27</p> <p>Fix Resolution: actionpack - 5.2.4.6,5.2.6,6.0.3.7,6.1.3.2</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-5418</summary> ### Vulnerable Library - <b>actionpack-3.0.9.gem</b></p> <p>Web apps on Rails. Simple, battle-tested conventions for building and testing MVC web applications. Works with any Rack-compatible server.</p> <p>Library home page: <a href="https://rubygems.org/gems/actionpack-3.0.9.gem">https://rubygems.org/gems/actionpack-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/actionpack-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: actionpack-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> There is a File Content Disclosure vulnerability in Action View <5.2.2.1, <5.1.6.2, <5.0.7.2, <4.2.11.1 and v3 where specially crafted accept headers can cause contents of arbitrary files on the target system's filesystem to be exposed. <p>Publish Date: 2019-03-27 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-5418>CVE-2019-5418</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://weblog.rubyonrails.org/2019/3/13/Rails-4-2-5-1-5-1-6-2-have-been-released/">https://weblog.rubyonrails.org/2019/3/13/Rails-4-2-5-1-5-1-6-2-have-been-released/</a></p> <p>Release Date: 2020-10-16</p> <p>Fix Resolution: 4.2.11.1, 5.0.7.2, 5.1.6.2, 5.2.2.1</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-0752</summary> ### Vulnerable Library - <b>rails-3.0.9.gem</b></p> <p>Ruby on Rails is a full-stack web framework optimized for programmer happiness and sustainable productivity. It encourages beautiful code by favoring convention over configuration.</p> <p>Library home page: <a href="https://rubygems.org/gems/rails-3.0.9.gem">https://rubygems.org/gems/rails-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /m/ruby/2.7.0/cache/rails-3.0.9.gem</p> <p> Dependency Hierarchy: - :x: rails-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Directory traversal vulnerability in Action View in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 allows remote attackers to read arbitrary files by leveraging an application's unrestricted use of the render method and providing a .. (dot dot) in a pathname. <p>Publish Date: 2016-02-16 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-0752>CVE-2016-0752</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-0752">https://nvd.nist.gov/vuln/detail/CVE-2016-0752</a></p> <p>Release Date: 2016-02-16</p> <p>Fix Resolution: 3.2.22.1,4.1.14.1,4.2.5.1,5.0.0.beta1.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-0751</summary> ### Vulnerable Libraries - <b>rails-3.0.9.gem</b>, <b>actionpack-3.0.9.gem</b></p> <p> ### <b>rails-3.0.9.gem</b></p> <p>Ruby on Rails is a full-stack web framework optimized for programmer happiness and sustainable productivity. It encourages beautiful code by favoring convention over configuration.</p> <p>Library home page: <a href="https://rubygems.org/gems/rails-3.0.9.gem">https://rubygems.org/gems/rails-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /m/ruby/2.7.0/cache/rails-3.0.9.gem</p> <p> Dependency Hierarchy: - :x: rails-3.0.9.gem (Vulnerable Library) ### <b>actionpack-3.0.9.gem</b></p> <p>Web apps on Rails. Simple, battle-tested conventions for building and testing MVC web applications. Works with any Rack-compatible server.</p> <p>Library home page: <a href="https://rubygems.org/gems/actionpack-3.0.9.gem">https://rubygems.org/gems/actionpack-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/actionpack-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: actionpack-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> actionpack/lib/action_dispatch/http/mime_type.rb in Action Pack in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 does not properly restrict use of the MIME type cache, which allows remote attackers to cause a denial of service (memory consumption) via a crafted HTTP Accept header. <p>Publish Date: 2016-02-16 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-0751>CVE-2016-0751</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-0751">https://nvd.nist.gov/vuln/detail/CVE-2016-0751</a></p> <p>Release Date: 2016-02-16</p> <p>Fix Resolution: 3.2.22.1,4.1.14.1,4.2.5.1,5.0.0.beta1.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2014-10077</summary> ### Vulnerable Library - <b>i18n-0.5.0.gem</b></p> <p>New wave Internationalization support for Ruby.</p> <p>Library home page: <a href="https://rubygems.org/gems/i18n-0.5.0.gem">https://rubygems.org/gems/i18n-0.5.0.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/i18n-0.5.0.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - activeresource-3.0.9.gem - activemodel-3.0.9.gem - :x: i18n-0.5.0.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Hash#slice in lib/i18n/core_ext/hash.rb in the i18n gem before 0.8.0 for Ruby allows remote attackers to cause a denial of service (application crash) via a call in a situation where :some_key is present in keep_keys but not present in the hash. <p>Publish Date: 2018-11-06 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-10077>CVE-2014-10077</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-10077">https://nvd.nist.gov/vuln/detail/CVE-2014-10077</a></p> <p>Release Date: 2018-11-06</p> <p>Fix Resolution: 0.8.0</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2013-0156</summary> ### Vulnerable Library - <b>activesupport-3.0.9.gem</b></p> <p>A toolkit of support libraries and Ruby core extensions extracted from the Rails framework. Rich support for multibyte strings, internationalization, time zones, and testing.</p> <p>Library home page: <a href="https://rubygems.org/gems/activesupport-3.0.9.gem">https://rubygems.org/gems/activesupport-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/activesupport-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: activesupport-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> active_support/core_ext/hash/conversions.rb in Ruby on Rails before 2.3.15, 3.0.x before 3.0.19, 3.1.x before 3.1.10, and 3.2.x before 3.2.11 does not properly restrict casts of string values, which allows remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) involving nested XML entity references, by leveraging Action Pack support for (1) YAML type conversion or (2) Symbol type conversion. <p>Publish Date: 2013-01-13 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0156>CVE-2013-0156</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2013-0156">https://nvd.nist.gov/vuln/detail/CVE-2013-0156</a></p> <p>Release Date: 2013-01-13</p> <p>Fix Resolution: 2.3.15,3.0.19,3.1.10,3.2.11</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2012-2695</summary> ### Vulnerable Library - <b>activerecord-3.0.9.gem</b></p> <p>Databases on Rails. Build a persistent domain model by mapping database tables to Ruby classes. Strong conventions for associations, validations, aggregations, migrations, and testing come baked-in.</p> <p>Library home page: <a href="https://rubygems.org/gems/activerecord-3.0.9.gem">https://rubygems.org/gems/activerecord-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/activerecord-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: activerecord-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The Active Record component in Ruby on Rails before 3.0.14, 3.1.x before 3.1.6, and 3.2.x before 3.2.6 does not properly implement the passing of request data to a where method in an ActiveRecord class, which allows remote attackers to conduct certain SQL injection attacks via nested query parameters that leverage improper handling of nested hashes, a related issue to CVE-2012-2661. <p>Publish Date: 2012-06-22 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-2695>CVE-2012-2695</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2012-2695">https://nvd.nist.gov/vuln/detail/CVE-2012-2695</a></p> <p>Release Date: 2012-06-22</p> <p>Fix Resolution: 3.0.14,3.1.6,3.2.6</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2012-6496</summary> ### Vulnerable Library - <b>activerecord-3.0.9.gem</b></p> <p>Databases on Rails. Build a persistent domain model by mapping database tables to Ruby classes. Strong conventions for associations, validations, aggregations, migrations, and testing come baked-in.</p> <p>Library home page: <a href="https://rubygems.org/gems/activerecord-3.0.9.gem">https://rubygems.org/gems/activerecord-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/activerecord-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: activerecord-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> SQL injection vulnerability in the Active Record component in Ruby on Rails before 3.0.18, 3.1.x before 3.1.9, and 3.2.x before 3.2.10 allows remote attackers to execute arbitrary SQL commands via a crafted request that leverages incorrect behavior of dynamic finders in applications that can use unexpected data types in certain find_by_ method calls. <p>Publish Date: 2013-01-04 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-6496>CVE-2012-6496</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2012-6496">https://nvd.nist.gov/vuln/detail/CVE-2012-6496</a></p> <p>Release Date: 2013-01-04</p> <p>Fix Resolution: 3.0.18,3.1.9,3.2.10</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-2098</summary> ### Vulnerable Libraries - <b>rails-3.0.9.gem</b>, <b>actionpack-3.0.9.gem</b></p> <p> ### <b>rails-3.0.9.gem</b></p> <p>Ruby on Rails is a full-stack web framework optimized for programmer happiness and sustainable productivity. It encourages beautiful code by favoring convention over configuration.</p> <p>Library home page: <a href="https://rubygems.org/gems/rails-3.0.9.gem">https://rubygems.org/gems/rails-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /m/ruby/2.7.0/cache/rails-3.0.9.gem</p> <p> Dependency Hierarchy: - :x: rails-3.0.9.gem (Vulnerable Library) ### <b>actionpack-3.0.9.gem</b></p> <p>Web apps on Rails. Simple, battle-tested conventions for building and testing MVC web applications. Works with any Rack-compatible server.</p> <p>Library home page: <a href="https://rubygems.org/gems/actionpack-3.0.9.gem">https://rubygems.org/gems/actionpack-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/actionpack-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: actionpack-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Action Pack in Ruby on Rails before 3.2.22.2, 4.x before 4.1.14.2, and 4.2.x before 4.2.5.2 allows remote attackers to execute arbitrary Ruby code by leveraging an application's unrestricted use of the render method. <p>Publish Date: 2016-04-07 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2098>CVE-2016-2098</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-2098">https://nvd.nist.gov/vuln/detail/CVE-2016-2098</a></p> <p>Release Date: 2016-04-07</p> <p>Fix Resolution: 3.2.22.2,4.1.14.2,4.2.5.2</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2013-0333</summary> ### Vulnerable Library - <b>activesupport-3.0.9.gem</b></p> <p>A toolkit of support libraries and Ruby core extensions extracted from the Rails framework. Rich support for multibyte strings, internationalization, time zones, and testing.</p> <p>Library home page: <a href="https://rubygems.org/gems/activesupport-3.0.9.gem">https://rubygems.org/gems/activesupport-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/activesupport-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: activesupport-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> lib/active_support/json/backends/yaml.rb in Ruby on Rails 2.3.x before 2.3.16 and 3.0.x before 3.0.20 does not properly convert JSON data to YAML data for processing by a YAML parser, which allows remote attackers to execute arbitrary code, conduct SQL injection attacks, or bypass authentication via crafted data that triggers unsafe decoding, a different vulnerability than CVE-2013-0156. <p>Publish Date: 2013-01-30 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0333>CVE-2013-0333</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2013-0333">https://nvd.nist.gov/vuln/detail/CVE-2013-0333</a></p> <p>Release Date: 2013-01-30</p> <p>Fix Resolution: 2.3.16,3.0.20</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2014-3482</summary> ### Vulnerable Library - <b>activerecord-3.0.9.gem</b></p> <p>Databases on Rails. Build a persistent domain model by mapping database tables to Ruby classes. Strong conventions for associations, validations, aggregations, migrations, and testing come baked-in.</p> <p>Library home page: <a href="https://rubygems.org/gems/activerecord-3.0.9.gem">https://rubygems.org/gems/activerecord-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/activerecord-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: activerecord-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> SQL injection vulnerability in activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb in the PostgreSQL adapter for Active Record in Ruby on Rails 2.x and 3.x before 3.2.19 allows remote attackers to execute arbitrary SQL commands by leveraging improper bitstring quoting. <p>Publish Date: 2014-07-07 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-3482>CVE-2014-3482</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-3482">https://nvd.nist.gov/vuln/detail/CVE-2014-3482</a></p> <p>Release Date: 2014-07-07</p> <p>Fix Resolution: 3.2.19</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2012-2140</summary> ### Vulnerable Library - <b>mail-2.2.19.gem</b></p> <p>A really Ruby Mail handler.</p> <p>Library home page: <a href="https://rubygems.org/gems/mail-2.2.19.gem">https://rubygems.org/gems/mail-2.2.19.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/mail-2.2.19.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - actionmailer-3.0.9.gem - :x: mail-2.2.19.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The Mail gem before 2.4.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a (1) sendmail or (2) exim delivery. <p>Publish Date: 2012-07-18 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-2140>CVE-2012-2140</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2012-2140">https://nvd.nist.gov/vuln/detail/CVE-2012-2140</a></p> <p>Release Date: 2012-07-18</p> <p>Fix Resolution: 2.4.3</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2013-6417</summary> ### Vulnerable Library - <b>actionpack-3.0.9.gem</b></p> <p>Web apps on Rails. Simple, battle-tested conventions for building and testing MVC web applications. Works with any Rack-compatible server.</p> <p>Library home page: <a href="https://rubygems.org/gems/actionpack-3.0.9.gem">https://rubygems.org/gems/actionpack-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/actionpack-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: actionpack-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> actionpack/lib/action_dispatch/http/request.rb in Ruby on Rails before 3.2.16 and 4.x before 4.0.2 does not properly consider differences in parameter handling between the Active Record component and the JSON implementation, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks or trigger missing WHERE clauses via a crafted request that leverages (1) third-party Rack middleware or (2) custom Rack middleware. NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-0155. <p>Publish Date: 2013-12-07 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-6417>CVE-2013-6417</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <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: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2013-6417">https://nvd.nist.gov/vuln/detail/CVE-2013-6417</a></p> <p>Release Date: 2013-12-07</p> <p>Fix Resolution: 3.2.16,4.0.2</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2013-3221</summary> ### Vulnerable Library - <b>activerecord-3.0.9.gem</b></p> <p>Databases on Rails. Build a persistent domain model by mapping database tables to Ruby classes. Strong conventions for associations, validations, aggregations, migrations, and testing come baked-in.</p> <p>Library home page: <a href="https://rubygems.org/gems/activerecord-3.0.9.gem">https://rubygems.org/gems/activerecord-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/activerecord-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: activerecord-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The Active Record component in Ruby on Rails 2.3.x, 3.0.x, 3.1.x, and 3.2.x does not ensure that the declared data type of a database column is used during comparisons of input values to stored values in that column, which makes it easier for remote attackers to conduct data-type injection attacks against Ruby on Rails applications via a crafted value, as demonstrated by unintended interaction between the "typed XML" feature and a MySQL database. <p>Publish Date: 2013-04-22 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-3221>CVE-2013-3221</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <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: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-3221">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-3221</a></p> <p>Release Date: 2013-04-22</p> <p>Fix Resolution: 4.0.0.rc1</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2013-0155</summary> ### Vulnerable Library - <b>activerecord-3.0.9.gem</b></p> <p>Databases on Rails. Build a persistent domain model by mapping database tables to Ruby classes. Strong conventions for associations, validations, aggregations, migrations, and testing come baked-in.</p> <p>Library home page: <a href="https://rubygems.org/gems/activerecord-3.0.9.gem">https://rubygems.org/gems/activerecord-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/activerecord-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: activerecord-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Ruby on Rails 3.0.x before 3.0.19, 3.1.x before 3.1.10, and 3.2.x before 3.2.11 does not properly consider differences in parameter handling between the Active Record component and the JSON implementation, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks or trigger missing WHERE clauses via a crafted request, as demonstrated by certain "[nil]" values, a related issue to CVE-2012-2660 and CVE-2012-2694. <p>Publish Date: 2013-01-13 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-0155>CVE-2013-0155</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <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: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2013-0155">https://nvd.nist.gov/vuln/detail/CVE-2013-0155</a></p> <p>Release Date: 2013-01-13</p> <p>Fix Resolution: 3.0.19,3.1.10,3.2.11</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2012-2660</summary> ### Vulnerable Library - <b>actionpack-3.0.9.gem</b></p> <p>Web apps on Rails. Simple, battle-tested conventions for building and testing MVC web applications. Works with any Rack-compatible server.</p> <p>Library home page: <a href="https://rubygems.org/gems/actionpack-3.0.9.gem">https://rubygems.org/gems/actionpack-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/actionpack-3.0.9.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - :x: actionpack-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> actionpack/lib/action_dispatch/http/request.rb in Ruby on Rails before 3.0.13, 3.1.x before 3.1.5, and 3.2.x before 3.2.4 does not properly consider differences in parameter handling between the Active Record component and the Rack interface, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks via a crafted request, as demonstrated by certain "[nil]" values, a related issue to CVE-2012-2694. <p>Publish Date: 2012-06-22 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-2660>CVE-2012-2660</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <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: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2012-2660">https://nvd.nist.gov/vuln/detail/CVE-2012-2660</a></p> <p>Release Date: 2012-06-22</p> <p>Fix Resolution: 3.0.13,3.1.5,3.2.4</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-8167</summary> ### Vulnerable Library - <b>rails-3.0.9.gem</b></p> <p>Ruby on Rails is a full-stack web framework optimized for programmer happiness and sustainable productivity. It encourages beautiful code by favoring convention over configuration.</p> <p>Library home page: <a href="https://rubygems.org/gems/rails-3.0.9.gem">https://rubygems.org/gems/rails-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /m/ruby/2.7.0/cache/rails-3.0.9.gem</p> <p> Dependency Hierarchy: - :x: rails-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A CSRF vulnerability exists in rails <= 6.0.3 rails-ujs module that could allow attackers to send CSRF tokens to wrong domains. <p>Publish Date: 2020-06-19 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8167>CVE-2020-8167</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://rubygems.org/gems/rails/versions/6.0.3.1">https://rubygems.org/gems/rails/versions/6.0.3.1</a></p> <p>Release Date: 2020-06-19</p> <p>Fix Resolution: 6.0.3.1,5.2.4.3</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2010-3299</summary> ### Vulnerable Library - <b>rails-3.0.9.gem</b></p> <p>Ruby on Rails is a full-stack web framework optimized for programmer happiness and sustainable productivity. It encourages beautiful code by favoring convention over configuration.</p> <p>Library home page: <a href="https://rubygems.org/gems/rails-3.0.9.gem">https://rubygems.org/gems/rails-3.0.9.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /m/ruby/2.7.0/cache/rails-3.0.9.gem</p> <p> Dependency Hierarchy: - :x: rails-3.0.9.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The encrypt/decrypt functions in Ruby on Rails 2.3 are vulnerable to padding oracle attacks. <p>Publish Date: 2019-11-12 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2010-3299>CVE-2010-3299</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3299">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3299</a></p> <p>Release Date: 2019-11-12</p> <p>Fix Resolution: rails - 5.2.0.beta1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-8130</summary> ### Vulnerable Library - <b>rake-0.9.2.gem</b></p> <p> Rake is a Make-like program implemented in Ruby. Tasks and dependencies are specified in standard Ruby syntax. </p> <p>Library home page: <a href="https://rubygems.org/gems/rake-0.9.2.gem">https://rubygems.org/gems/rake-0.9.2.gem</a></p> <p>Path to dependency file: /Gemfile.lock</p> <p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/rake-0.9.2.gem</p> <p> Dependency Hierarchy: - rails-3.0.9.gem (Root Library) - railties-3.0.9.gem - :x: rake-0.9.2.gem (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/hackme-23/commit/e68e88a92dda80af686db468b2b5c1bcb858b76f">e68e88a92dda80af686db468b2b5c1bcb858b76f</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> There is an OS command injection vulnerability in Ruby Rake < 12.3.3 in Rake::FileList when supplying a filename that begins with the pipe character `\|`. <p>Publish Date: 2020-02-24 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8130>CVE-2020-8130</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.4</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: High - Privileges Required: High - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8130">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8130</a></p> <p>Release Date: 2020-06-30</p> <p>Fix Resolution: v12.3.3</p> </p> <p></p> </details> *** <p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>	non_priority	rails gem vulnerabilities highest severity is vulnerable library rails gem ruby on rails is a full stack web framework optimized for programmer happiness and sustainable productivity it encourages beautiful code by favoring convention over configuration library home page a href path to dependency file gemfile lock path to vulnerable library m ruby cache rails gem found in head commit a href vulnerabilities cve severity cvss dependency type fixed in remediation available high rack gem transitive n a high rack gem transitive n a high actionpack gem transitive n a high actionpack gem transitive n a high rails gem direct high detected in multiple dependencies direct high gem transitive n a high activesupport gem transitive n a high activerecord gem transitive n a high activerecord gem transitive n a high detected in multiple dependencies direct high activesupport gem transitive n a high activerecord gem transitive n a high mail gem transitive n a medium actionpack gem transitive n a medium activerecord gem transitive n a medium activerecord gem transitive n a medium actionpack gem transitive n a medium rails gem direct medium rails gem direct rails medium rake gem transitive n a medium rack gem transitive n a medium actionpack gem transitive n a medium mail gem transitive n a medium rack gem transitive n a medium rack gem transitive n a medium rails gem direct medium actionpack gem transitive n a medium rack gem transitive n a medium actionpack gem transitive n a medium mail gem transitive n a medium rack gem transitive n a medium rack gem transitive n a medium activerecord gem transitive n a medium rails gem direct medium actionpack gem transitive n a medium actionpack gem transitive n a low actionpack gem transitive n a low actionpack gem transitive n a low actionpack gem transitive n a low activesupport gem transitive n a low actionpack gem transitive n a low actionpack gem transitive n a low rails gem direct low rack gem transitive n a low actionpack gem transitive n a low gem transitive n a low rdoc gem transitive n a low actionpack gem transitive n a low actionpack gem transitive n a low rack gem transitive n a low actionpack gem transitive n a details partial details vulnerabilities are displayed below due to a content size limitation in github to view information on the remaining vulnerabilities navigate to the mend application cve vulnerable library rack gem rack provides minimal modular and adaptable interface for developing web applications in ruby by wrapping http requests and responses in the simplest way possible it unifies and distills the api for web servers web frameworks and software in between the so called middleware into a single method call also see library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache rack gem dependency hierarchy rails gem root library actionpack gem x rack gem vulnerable library found in head commit a href found in base branch master vulnerability details a directory traversal vulnerability exists in rack that allows an attacker perform directory traversal vulnerability in the rack directory app that is bundled with rack which could result in information disclosure 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 changed impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version release date fix resolution cve vulnerable library rack gem rack provides minimal modular and adaptable interface for developing web applications in ruby by wrapping http requests and responses in the simplest way possible it unifies and distills the api for web servers web frameworks and software in between the so called middleware into a single method call also see library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache rack gem dependency hierarchy rails gem root library actionpack gem x rack gem vulnerable library found in head commit a href found in base branch master vulnerability details a reliance on cookies without validation integrity check security vulnerability exists in rack rack that makes it is possible for an attacker to forge a secure or host only cookie prefix publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rack cve vulnerable library actionpack gem web apps on rails simple battle tested conventions for building and testing mvc web applications works with any rack compatible server library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache actionpack gem dependency hierarchy rails gem root library x actionpack gem vulnerable library found in head commit a href found in base branch master vulnerability details a possible information disclosure unintended method execution vulnerability in action pack when using the redirect to or polymorphic url helper with untrusted user input publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution actionpack cve vulnerable library actionpack gem web apps on rails simple battle tested conventions for building and testing mvc web applications works with any rack compatible server library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache actionpack gem dependency hierarchy rails gem root library x actionpack gem vulnerable library found in head commit a href found in base branch master vulnerability details there is a file content disclosure vulnerability in action view and where specially crafted accept headers can cause contents of arbitrary files on the target system s filesystem to be exposed publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution cve vulnerable library rails gem ruby on rails is a full stack web framework optimized for programmer happiness and sustainable productivity it encourages beautiful code by favoring convention over configuration library home page a href path to dependency file gemfile lock path to vulnerable library m ruby cache rails gem dependency hierarchy x rails gem vulnerable library found in head commit a href found in base branch master vulnerability details directory traversal vulnerability in action view in ruby on rails before x and x before x before and x before allows remote attackers to read arbitrary files by leveraging an application s unrestricted use of the render method and providing a dot dot in a pathname publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable libraries rails gem actionpack gem rails gem ruby on rails is a full stack web framework optimized for programmer happiness and sustainable productivity it encourages beautiful code by favoring convention over configuration library home page a href path to dependency file gemfile lock path to vulnerable library m ruby cache rails gem dependency hierarchy x rails gem vulnerable library actionpack gem web apps on rails simple battle tested conventions for building and testing mvc web applications works with any rack compatible server library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache actionpack gem dependency hierarchy rails gem root library x actionpack gem vulnerable library found in head commit a href found in base branch master vulnerability details actionpack lib action dispatch http mime type rb in action pack in ruby on rails before x and x before x before and x before does not properly restrict use of the mime type cache which allows remote attackers to cause a denial of service memory consumption via a crafted http accept header 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 rescue worker helmet automatic remediation is available for this issue cve vulnerable library gem new wave internationalization support for ruby library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache gem dependency hierarchy rails gem root library activeresource gem activemodel gem x gem vulnerable library found in head commit a href found in base branch master vulnerability details hash slice in lib core ext hash rb in the gem before for ruby allows remote attackers to cause a denial of service application crash via a call in a situation where some key is present in keep keys but not present in the hash 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 cve vulnerable library activesupport gem a toolkit of support libraries and ruby core extensions extracted from the rails framework rich support for multibyte strings internationalization time zones and testing library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache activesupport gem dependency hierarchy rails gem root library x activesupport gem vulnerable library found in head commit a href found in base branch master vulnerability details active support core ext hash conversions rb in ruby on rails before x before x before and x before does not properly restrict casts of string values which allows remote attackers to conduct object injection attacks and execute arbitrary code or cause a denial of service memory and cpu consumption involving nested xml entity references by leveraging action pack support for yaml type conversion or symbol type conversion 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 cve vulnerable library activerecord gem databases on rails build a persistent domain model by mapping database tables to ruby classes strong conventions for associations validations aggregations migrations and testing come baked in library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache activerecord gem dependency hierarchy rails gem root library x activerecord gem vulnerable library found in head commit a href found in base branch master vulnerability details the active record component in ruby on rails before x before and x before does not properly implement the passing of request data to a where method in an activerecord class which allows remote attackers to conduct certain sql injection attacks via nested query parameters that leverage improper handling of nested hashes a related issue to cve 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 cve vulnerable library activerecord gem databases on rails build a persistent domain model by mapping database tables to ruby classes strong conventions for associations validations aggregations migrations and testing come baked in library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache activerecord gem dependency hierarchy rails gem root library x activerecord gem vulnerable library found in head commit a href found in base branch master vulnerability details sql injection vulnerability in the active record component in ruby on rails before x before and x before allows remote attackers to execute arbitrary sql commands via a crafted request that leverages incorrect behavior of dynamic finders in applications that can use unexpected data types in certain find by method calls 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 cve vulnerable libraries rails gem actionpack gem rails gem ruby on rails is a full stack web framework optimized for programmer happiness and sustainable productivity it encourages beautiful code by favoring convention over configuration library home page a href path to dependency file gemfile lock path to vulnerable library m ruby cache rails gem dependency hierarchy x rails gem vulnerable library actionpack gem web apps on rails simple battle tested conventions for building and testing mvc web applications works with any rack compatible server library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache actionpack gem dependency hierarchy rails gem root library x actionpack gem vulnerable library found in head commit a href found in base branch master vulnerability details action pack in ruby on rails before x before and x before allows remote attackers to execute arbitrary ruby code by leveraging an application s unrestricted use of the render method 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 rescue worker helmet automatic remediation is available for this issue cve vulnerable library activesupport gem a toolkit of support libraries and ruby core extensions extracted from the rails framework rich support for multibyte strings internationalization time zones and testing library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache activesupport gem dependency hierarchy rails gem root library x activesupport gem vulnerable library found in head commit a href found in base branch master vulnerability details lib active support json backends yaml rb in ruby on rails x before and x before does not properly convert json data to yaml data for processing by a yaml parser which allows remote attackers to execute arbitrary code conduct sql injection attacks or bypass authentication via crafted data that triggers unsafe decoding a different vulnerability than cve 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 cve vulnerable library activerecord gem databases on rails build a persistent domain model by mapping database tables to ruby classes strong conventions for associations validations aggregations migrations and testing come baked in library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache activerecord gem dependency hierarchy rails gem root library x activerecord gem vulnerable library found in head commit a href found in base branch master vulnerability details sql injection vulnerability in activerecord lib active record connection adapters postgresql adapter rb in the postgresql adapter for active record in ruby on rails x and x before allows remote attackers to execute arbitrary sql commands by leveraging improper bitstring quoting 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 cve vulnerable library mail gem a really ruby mail handler library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache mail gem dependency hierarchy rails gem root library actionmailer gem x mail gem vulnerable library found in head commit a href found in base branch master vulnerability details the mail gem before for ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a sendmail or exim delivery 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 cve vulnerable library actionpack gem web apps on rails simple battle tested conventions for building and testing mvc web applications works with any rack compatible server library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache actionpack gem dependency hierarchy rails gem root library x actionpack gem vulnerable library found in head commit a href found in base branch master vulnerability details actionpack lib action dispatch http request rb in ruby on rails before and x before does not properly consider differences in parameter handling between the active record component and the json implementation which allows remote attackers to bypass intended database query restrictions and perform null checks or trigger missing where clauses via a crafted request that leverages third party rack middleware or custom rack middleware note this vulnerability exists because of an incomplete fix for cve 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 none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution cve vulnerable library activerecord gem databases on rails build a persistent domain model by mapping database tables to ruby classes strong conventions for associations validations aggregations migrations and testing come baked in library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache activerecord gem dependency hierarchy rails gem root library x activerecord gem vulnerable library found in head commit a href found in base branch master vulnerability details the active record component in ruby on rails x x x and x does not ensure that the declared data type of a database column is used during comparisons of input values to stored values in that column which makes it easier for remote attackers to conduct data type injection attacks against ruby on rails applications via a crafted value as demonstrated by unintended interaction between the typed xml feature and a mysql database 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 none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution cve vulnerable library activerecord gem databases on rails build a persistent domain model by mapping database tables to ruby classes strong conventions for associations validations aggregations migrations and testing come baked in library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache activerecord gem dependency hierarchy rails gem root library x activerecord gem vulnerable library found in head commit a href found in base branch master vulnerability details ruby on rails x before x before and x before does not properly consider differences in parameter handling between the active record component and the json implementation which allows remote attackers to bypass intended database query restrictions and perform null checks or trigger missing where clauses via a crafted request as demonstrated by certain values a related issue to cve and cve 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 none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution cve vulnerable library actionpack gem web apps on rails simple battle tested conventions for building and testing mvc web applications works with any rack compatible server library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache actionpack gem dependency hierarchy rails gem root library x actionpack gem vulnerable library found in head commit a href found in base branch master vulnerability details actionpack lib action dispatch http request rb in ruby on rails before x before and x before does not properly consider differences in parameter handling between the active record component and the rack interface which allows remote attackers to bypass intended database query restrictions and perform null checks via a crafted request as demonstrated by certain values a related issue to cve 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 none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution cve vulnerable library rails gem ruby on rails is a full stack web framework optimized for programmer happiness and sustainable productivity it encourages beautiful code by favoring convention over configuration library home page a href path to dependency file gemfile lock path to vulnerable library m ruby cache rails gem dependency hierarchy x rails gem vulnerable library found in head commit a href found in base branch master vulnerability details a csrf vulnerability exists in rails rails ujs module that could allow attackers to send csrf tokens to wrong domains publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library rails gem ruby on rails is a full stack web framework optimized for programmer happiness and sustainable productivity it encourages beautiful code by favoring convention over configuration library home page a href path to dependency file gemfile lock path to vulnerable library m ruby cache rails gem dependency hierarchy x rails gem vulnerable library found in head commit a href found in base branch master vulnerability details the encrypt decrypt functions in ruby on rails are vulnerable to padding oracle attacks publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rails rescue worker helmet automatic remediation is available for this issue cve vulnerable library rake gem rake is a make like program implemented in ruby tasks and dependencies are specified in standard ruby syntax library home page a href path to dependency file gemfile lock path to vulnerable library home wss scanner gem ruby cache rake gem dependency hierarchy rails gem root library railties gem x rake gem vulnerable library found in head commit a href found in base branch master vulnerability details there is an os command injection vulnerability in ruby rake in rake filelist when supplying a filename that begins with the pipe character publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required high user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue	0
713,050	24,515,582,116	IssuesEvent	2022-10-11 04:30:50	googleapis/nodejs-ai-platform	https://api.github.com/repos/googleapis/nodejs-ai-platform	closed	AI platform create training pipeline tables classification: "after all" hook: should cancel the training pipeline and delete it for "should create a new tables classification training pipeline" failed	type: bug priority: p1 flakybot: issue api: vertex-ai	This test failed! To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot). If I'm commenting on this issue too often, add the `flakybot: quiet` label and I will stop commenting. --- commit: e1c5cd6b5d03afb03911ba9aa685457aa359a602 buildURL: [Build Status](https://source.cloud.google.com/results/invocations/69dc3b23-298d-461c-9279-cd7551a90fc9), [Sponge](http://sponge2/69dc3b23-298d-461c-9279-cd7551a90fc9) status: failed <details><summary>Test output</summary><br><pre>Cannot read property 'toString' of undefined TypeError: Cannot read property 'toString' of undefined at PathTemplate.render (/workspace/node_modules/google-gax/build/src/pathTemplate.js:114:37) -> /workspace/node_modules/google-gax/src/pathTemplate.ts:144:31 at PipelineServiceClient.trainingPipelinePath (/workspace/build/src/v1/pipeline_service_client.js:3767:64) -> /workspace/src/v1/pipeline_service_client.ts:5458:60 at Context.<anonymous> (test/create-training-pipeline-tabular-classification.test.js:70:40) at processImmediate (internal/timers.js:461:21)</pre></details>	1.0	AI platform create training pipeline tables classification: "after all" hook: should cancel the training pipeline and delete it for "should create a new tables classification training pipeline" failed - This test failed! To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot). If I'm commenting on this issue too often, add the `flakybot: quiet` label and I will stop commenting. --- commit: e1c5cd6b5d03afb03911ba9aa685457aa359a602 buildURL: [Build Status](https://source.cloud.google.com/results/invocations/69dc3b23-298d-461c-9279-cd7551a90fc9), [Sponge](http://sponge2/69dc3b23-298d-461c-9279-cd7551a90fc9) status: failed <details><summary>Test output</summary><br><pre>Cannot read property 'toString' of undefined TypeError: Cannot read property 'toString' of undefined at PathTemplate.render (/workspace/node_modules/google-gax/build/src/pathTemplate.js:114:37) -> /workspace/node_modules/google-gax/src/pathTemplate.ts:144:31 at PipelineServiceClient.trainingPipelinePath (/workspace/build/src/v1/pipeline_service_client.js:3767:64) -> /workspace/src/v1/pipeline_service_client.ts:5458:60 at Context.<anonymous> (test/create-training-pipeline-tabular-classification.test.js:70:40) at processImmediate (internal/timers.js:461:21)</pre></details>	priority	ai platform create training pipeline tables classification after all hook should cancel the training pipeline and delete it for should create a new tables classification training pipeline failed this test failed to configure my behavior see if i m commenting on this issue too often add the flakybot quiet label and i will stop commenting commit buildurl status failed test output cannot read property tostring of undefined typeerror cannot read property tostring of undefined at pathtemplate render workspace node modules google gax build src pathtemplate js workspace node modules google gax src pathtemplate ts at pipelineserviceclient trainingpipelinepath workspace build src pipeline service client js workspace src pipeline service client ts at context test create training pipeline tabular classification test js at processimmediate internal timers js	1
101,426	16,510,078,224	IssuesEvent	2021-05-26 02:10:02	kijunb33/b	https://api.github.com/repos/kijunb33/b	opened	CVE-2019-0221 (Medium) detected in tomcat-embed-core-7.0.90.jar	security vulnerability	## CVE-2019-0221 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-7.0.90.jar</b></p></summary> <p>Core Tomcat implementation</p> <p>Library home page: <a href="https://tomcat.apache.org/">https://tomcat.apache.org/</a></p> <p>Path to vulnerable library: b/tomcat-embed-core-7.0.90.jar</p> <p> Dependency Hierarchy: - :x: tomcat-embed-core-7.0.90.jar (Vulnerable Library) <p>Found in HEAD commit: <a href="https://api.github.com/repos/kijunb33/b/commits/e46c3041de1af15e2ec9373552e1df64074ec421">e46c3041de1af15e2ec9373552e1df64074ec421</a></p> <p>Found in base branch: <b>main</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> The SSI printenv command in Apache Tomcat 9.0.0.M1 to 9.0.0.17, 8.5.0 to 8.5.39 and 7.0.0 to 7.0.93 echoes user provided data without escaping and is, therefore, vulnerable to XSS. SSI is disabled by default. The printenv command is intended for debugging and is unlikely to be present in a production website. <p>Publish Date: 2019-05-28 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-0221>CVE-2019-0221</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>6.1</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0221">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0221</a></p> <p>Release Date: 2019-05-28</p> <p>Fix Resolution: 9.0.0.18,8.5.40,7.0.94</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-2019-0221 (Medium) detected in tomcat-embed-core-7.0.90.jar - ## CVE-2019-0221 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-7.0.90.jar</b></p></summary> <p>Core Tomcat implementation</p> <p>Library home page: <a href="https://tomcat.apache.org/">https://tomcat.apache.org/</a></p> <p>Path to vulnerable library: b/tomcat-embed-core-7.0.90.jar</p> <p> Dependency Hierarchy: - :x: tomcat-embed-core-7.0.90.jar (Vulnerable Library) <p>Found in HEAD commit: <a href="https://api.github.com/repos/kijunb33/b/commits/e46c3041de1af15e2ec9373552e1df64074ec421">e46c3041de1af15e2ec9373552e1df64074ec421</a></p> <p>Found in base branch: <b>main</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> The SSI printenv command in Apache Tomcat 9.0.0.M1 to 9.0.0.17, 8.5.0 to 8.5.39 and 7.0.0 to 7.0.93 echoes user provided data without escaping and is, therefore, vulnerable to XSS. SSI is disabled by default. The printenv command is intended for debugging and is unlikely to be present in a production website. <p>Publish Date: 2019-05-28 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-0221>CVE-2019-0221</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>6.1</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0221">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0221</a></p> <p>Release Date: 2019-05-28</p> <p>Fix Resolution: 9.0.0.18,8.5.40,7.0.94</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 tomcat embed core jar cve medium severity vulnerability vulnerable library tomcat embed core jar core tomcat implementation library home page a href path to vulnerable library b tomcat embed core jar dependency hierarchy x tomcat embed core jar vulnerable library found in head commit a href found in base branch main vulnerability details the ssi printenv command in apache tomcat to to and to echoes user provided data without escaping and is therefore vulnerable to xss ssi is disabled by default the printenv command is intended for debugging and is unlikely to be present in a production website publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource	0
403,116	11,836,274,082	IssuesEvent	2020-03-23 12:12:44	EpicMorg/docker-scripts	https://api.github.com/repos/EpicMorg/docker-scripts	closed	fix installing latest dotnetcore via normal docs in tc-agent	Regular Priority bug	fix installing latest dotnetcore via normal docs in tc-agent https://docs.microsoft.com/en-us/dotnet/core/install/linux-package-manager-debian10	1.0	fix installing latest dotnetcore via normal docs in tc-agent - fix installing latest dotnetcore via normal docs in tc-agent https://docs.microsoft.com/en-us/dotnet/core/install/linux-package-manager-debian10	priority	fix installing latest dotnetcore via normal docs in tc agent fix installing latest dotnetcore via normal docs in tc agent	1
300,251	9,206,300,228	IssuesEvent	2019-03-08 13:21:39	qissue-bot/QGIS	https://api.github.com/repos/qissue-bot/QGIS	closed	Untranslatable "Close" button in QGIS 1.1.0	Category: GUI Component: Affected QGIS version Component: Crashes QGIS or corrupts data Component: Easy fix? Component: Operating System Component: Pull Request or Patch supplied Component: Regression? Component: Resolution Priority: Low Project: QGIS Application Status: Closed Tracker: Bug report	--- Author Name: artfwo - (artfwo -) Original Redmine Issue: 1569, https://issues.qgis.org/issues/1569 Original Assignee: nobody - --- The button "Close" in all dialogs (like file opening) in 1.1.0 appears untranslated, (when built and started with Qt 4.5). The text itself is translated everywhere in qgis_ru.ts and qt_ru.ts. Please fix!	1.0	Untranslatable "Close" button in QGIS 1.1.0 - --- Author Name: artfwo - (artfwo -) Original Redmine Issue: 1569, https://issues.qgis.org/issues/1569 Original Assignee: nobody - --- The button "Close" in all dialogs (like file opening) in 1.1.0 appears untranslated, (when built and started with Qt 4.5). The text itself is translated everywhere in qgis_ru.ts and qt_ru.ts. Please fix!	priority	untranslatable close button in qgis author name artfwo artfwo original redmine issue original assignee nobody the button close in all dialogs like file opening in appears untranslated when built and started with qt the text itself is translated everywhere in qgis ru ts and qt ru ts please fix	1
575,990	17,068,241,244	IssuesEvent	2021-07-07 10:00:40	hermeznetwork/wallet-ui	https://api.github.com/repos/hermeznetwork/wallet-ui	closed	Token Swap/Create General View + Store	priority: high type: enhancement	Abstract structure for general view + store for a multi step process. Add button from Home/Account Details to go to Swap view (check if it goes in Account Details)	1.0	Token Swap/Create General View + Store - Abstract structure for general view + store for a multi step process. Add button from Home/Account Details to go to Swap view (check if it goes in Account Details)	priority	token swap create general view store abstract structure for general view store for a multi step process add button from home account details to go to swap view check if it goes in account details	1
5,591	2,952,000,840	IssuesEvent	2015-07-07 05:24:28	mitchellh/vagrant	https://api.github.com/repos/mitchellh/vagrant	closed	Documentation of Vagrant vs Provisioner attributes	documentation	As indicated by https://github.com/mitchellh/vagrant/issues/4583 there are two places to add attributes when making a call to `vagrant.vm.provision` Attributes related to Vagrant itself belong in the `provision` method call, while attributes on the provisioner belong inside the block. This is not well documented, and is made more confusing by the one-line style provision calls which seem to blend both types of attributes. config.vm.provision "shell", inline: "echo foo", id: "foo" We need some clarification regarding which attributes can go in the method call, which belong in the block, and which may work in the one-liner. Furthermore, in places that the one-liner is used in examples, it would be good to add an additional example that has the block syntax, for clarity sake. Finally, it would be nice to have a page dedicated to listing and explaining the attributes which can be set inside the method call (such as :id).	1.0	Documentation of Vagrant vs Provisioner attributes - As indicated by https://github.com/mitchellh/vagrant/issues/4583 there are two places to add attributes when making a call to `vagrant.vm.provision` Attributes related to Vagrant itself belong in the `provision` method call, while attributes on the provisioner belong inside the block. This is not well documented, and is made more confusing by the one-line style provision calls which seem to blend both types of attributes. config.vm.provision "shell", inline: "echo foo", id: "foo" We need some clarification regarding which attributes can go in the method call, which belong in the block, and which may work in the one-liner. Furthermore, in places that the one-liner is used in examples, it would be good to add an additional example that has the block syntax, for clarity sake. Finally, it would be nice to have a page dedicated to listing and explaining the attributes which can be set inside the method call (such as :id).	non_priority	documentation of vagrant vs provisioner attributes as indicated by there are two places to add attributes when making a call to vagrant vm provision attributes related to vagrant itself belong in the provision method call while attributes on the provisioner belong inside the block this is not well documented and is made more confusing by the one line style provision calls which seem to blend both types of attributes config vm provision shell inline echo foo id foo we need some clarification regarding which attributes can go in the method call which belong in the block and which may work in the one liner furthermore in places that the one liner is used in examples it would be good to add an additional example that has the block syntax for clarity sake finally it would be nice to have a page dedicated to listing and explaining the attributes which can be set inside the method call such as id	0
85,743	15,755,226,191	IssuesEvent	2021-03-31 01:24:18	akshat702/map-ionic	https://api.github.com/repos/akshat702/map-ionic	opened	CVE-2020-11023 (Medium) detected in jquery-3.3.1.tgz	security vulnerability	## CVE-2020-11023 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-3.3.1.tgz</b></p></summary> <p>JavaScript library for DOM operations</p> <p>Library home page: <a href="https://registry.npmjs.org/jquery/-/jquery-3.3.1.tgz">https://registry.npmjs.org/jquery/-/jquery-3.3.1.tgz</a></p> <p>Path to dependency file: map-ionic/angular-latest-19-02-19/package.json</p> <p>Path to vulnerable library: map-ionic/angular-latest-19-02-19/node_modules/jquery/package.json</p> <p> Dependency Hierarchy: - :x: jquery-3.3.1.tgz (Vulnerable Library) </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. <p>Publish Date: 2020-04-29 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11023>CVE-2020-11023</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>6.1</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11023">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11023</a></p> <p>Release Date: 2020-04-29</p> <p>Fix Resolution: jquery - 3.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-2020-11023 (Medium) detected in jquery-3.3.1.tgz - ## CVE-2020-11023 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-3.3.1.tgz</b></p></summary> <p>JavaScript library for DOM operations</p> <p>Library home page: <a href="https://registry.npmjs.org/jquery/-/jquery-3.3.1.tgz">https://registry.npmjs.org/jquery/-/jquery-3.3.1.tgz</a></p> <p>Path to dependency file: map-ionic/angular-latest-19-02-19/package.json</p> <p>Path to vulnerable library: map-ionic/angular-latest-19-02-19/node_modules/jquery/package.json</p> <p> Dependency Hierarchy: - :x: jquery-3.3.1.tgz (Vulnerable Library) </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. <p>Publish Date: 2020-04-29 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11023>CVE-2020-11023</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>6.1</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11023">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11023</a></p> <p>Release Date: 2020-04-29</p> <p>Fix Resolution: jquery - 3.5.0</p> </p> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)	non_priority	cve medium detected in jquery tgz cve medium severity vulnerability vulnerable library jquery tgz javascript library for dom operations library home page a href path to dependency file map ionic angular latest package json path to vulnerable library map ionic angular latest node modules jquery package json dependency hierarchy x jquery tgz vulnerable library vulnerability details in jquery versions greater than or equal to and before passing html containing elements from untrusted sources even after sanitizing it to one of jquery s dom manipulation methods i e html append and others may execute untrusted code this problem is patched in jquery publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jquery step up your open source security game with whitesource	0
215,064	16,626,079,458	IssuesEvent	2021-06-03 09:43:14	dart-lang/sdk	https://api.github.com/repos/dart-lang/sdk	opened	Validate that all constructor tearoffs related tests are passing, prior to release	area-test	This issue tracks support of the [constructor tearoffs feature](https://github.com/dart-lang/language/blob/master/working/0216%20-%20constructor%20tearoffs/proposal.md). See the [enclosing meta-issue](https://github.com/dart-lang/sdk/issues/46228) for details. The implementation issues for this feature are needed in order to have a reference when approving test failures. Further information will be added here when the implementation work starts.	1.0	Validate that all constructor tearoffs related tests are passing, prior to release - This issue tracks support of the [constructor tearoffs feature](https://github.com/dart-lang/language/blob/master/working/0216%20-%20constructor%20tearoffs/proposal.md). See the [enclosing meta-issue](https://github.com/dart-lang/sdk/issues/46228) for details. The implementation issues for this feature are needed in order to have a reference when approving test failures. Further information will be added here when the implementation work starts.	non_priority	validate that all constructor tearoffs related tests are passing prior to release this issue tracks support of the see the for details the implementation issues for this feature are needed in order to have a reference when approving test failures further information will be added here when the implementation work starts	0
310,643	23,346,664,210	IssuesEvent	2022-08-09 18:39:54	JanPalasek/pretty-jupyter	https://api.github.com/repos/JanPalasek/pretty-jupyter	opened	Export to pdf	documentation enhancement	The export to pdf is not goal of this project. However if one chooses to do so, it would be good to at least do the following things: - [ ] Hide Jinja Markdown input cells by default.	1.0	Export to pdf - The export to pdf is not goal of this project. However if one chooses to do so, it would be good to at least do the following things: - [ ] Hide Jinja Markdown input cells by default.	non_priority	export to pdf the export to pdf is not goal of this project however if one chooses to do so it would be good to at least do the following things hide jinja markdown input cells by default	0
536,331	15,707,598,260	IssuesEvent	2021-03-26 19:08:10	CreeperMagnet/the-creepers-code	https://api.github.com/repos/CreeperMagnet/the-creepers-code	closed	Phantom item frames break when a block is placed on top of them	priority: high	They turn into an item frame and spit out their item. This can be fixed by adding another condition to the break function.	1.0	Phantom item frames break when a block is placed on top of them - They turn into an item frame and spit out their item. This can be fixed by adding another condition to the break function.	priority	phantom item frames break when a block is placed on top of them they turn into an item frame and spit out their item this can be fixed by adding another condition to the break function	1
814,765	30,521,209,912	IssuesEvent	2023-07-19 08:12:50	aidenybai/million	https://api.github.com/repos/aidenybai/million	opened	feat: cross file blocks + ui component library support	enhancement help wanted 🤖 aspect: dx 🟥 priority: critical	Currently, we only support using `block()` in the same file as the original component, like so: ```jsx import { block } from 'million/react'; function Component() { // ... } const ComponentBlock = block(Component); ``` But what if we could do cross file blocks? ```jsx // file1.jsx export function Component() { // ... } // file2.jsx import { block } from 'million/react'; import { Component } from './file1'; const ComponentBlock = block(Component); ``` And what if we could do this within modules? ```jsx import { Button } from 'chakraui'; const ButtonBlock = block(Button); ```	1.0	feat: cross file blocks + ui component library support - Currently, we only support using `block()` in the same file as the original component, like so: ```jsx import { block } from 'million/react'; function Component() { // ... } const ComponentBlock = block(Component); ``` But what if we could do cross file blocks? ```jsx // file1.jsx export function Component() { // ... } // file2.jsx import { block } from 'million/react'; import { Component } from './file1'; const ComponentBlock = block(Component); ``` And what if we could do this within modules? ```jsx import { Button } from 'chakraui'; const ButtonBlock = block(Button); ```	priority	feat cross file blocks ui component library support currently we only support using block in the same file as the original component like so jsx import block from million react function component const componentblock block component but what if we could do cross file blocks jsx jsx export function component jsx import block from million react import component from const componentblock block component and what if we could do this within modules jsx import button from chakraui const buttonblock block button	1
40,780	21,111,137,445	IssuesEvent	2022-04-05 01:49:23	airbytehq/airbyte	https://api.github.com/repos/airbytehq/airbyte	closed	Load onboarding state via backend API	area/frontend performance	Currently we do a lot of calls (list all connections, sources, destinations) in the UI to determine the state of the onboarding of a user. We only need the count of connections, sources, destinations though to determine this. This could be solved way quicker if we'd calculate the count via the DB and have one web_backend API to actually get the count of all three. The UI would then only need to make one (faster) API call to determine the state.	True	Load onboarding state via backend API - Currently we do a lot of calls (list all connections, sources, destinations) in the UI to determine the state of the onboarding of a user. We only need the count of connections, sources, destinations though to determine this. This could be solved way quicker if we'd calculate the count via the DB and have one web_backend API to actually get the count of all three. The UI would then only need to make one (faster) API call to determine the state.	non_priority	load onboarding state via backend api currently we do a lot of calls list all connections sources destinations in the ui to determine the state of the onboarding of a user we only need the count of connections sources destinations though to determine this this could be solved way quicker if we d calculate the count via the db and have one web backend api to actually get the count of all three the ui would then only need to make one faster api call to determine the state	0
607,279	18,779,019,712	IssuesEvent	2021-11-08 02:31:23	space-wizards/space-station-14	https://api.github.com/repos/space-wizards/space-station-14	reopened	Restarting the round via vote while the round is ending causes improper restart	Type: Bug Priority: 2-Before Release Difficulty: 2-Medium	I think I've finally figured out what makes this happen and I haven't seen any reports about it, so.. How to reproduce: - Call the shuttle and wait until the shuttle has nearly arrived (10-15 seconds). - Call a restart vote and vote yes so the restart vote goes off at the same time as the shuttle's arrival The server will then go into this weird state where the round will end, it'll dump everyone back to the lobby, but won't properly reset the map. Instead, it'll respawn people onto the map from last round and the map will not be reset until an admin restarts the server.	1.0	Restarting the round via vote while the round is ending causes improper restart - I think I've finally figured out what makes this happen and I haven't seen any reports about it, so.. How to reproduce: - Call the shuttle and wait until the shuttle has nearly arrived (10-15 seconds). - Call a restart vote and vote yes so the restart vote goes off at the same time as the shuttle's arrival The server will then go into this weird state where the round will end, it'll dump everyone back to the lobby, but won't properly reset the map. Instead, it'll respawn people onto the map from last round and the map will not be reset until an admin restarts the server.	priority	restarting the round via vote while the round is ending causes improper restart i think i ve finally figured out what makes this happen and i haven t seen any reports about it so how to reproduce call the shuttle and wait until the shuttle has nearly arrived seconds call a restart vote and vote yes so the restart vote goes off at the same time as the shuttle s arrival the server will then go into this weird state where the round will end it ll dump everyone back to the lobby but won t properly reset the map instead it ll respawn people onto the map from last round and the map will not be reset until an admin restarts the server	1
182,934	6,674,098,269	IssuesEvent	2017-10-04 17:16:48	webcompat/web-bugs	https://api.github.com/repos/webcompat/web-bugs	closed	en.savefrom.net - see bug description	browser-firefox priority-important status-needstriage	<!-- @browser: Firefox 58.0 --> <!-- @ua_header: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0 --> <!-- @reported_with: addon-reporter-firefox --> URL: http://en.savefrom.net/ Browser / Version: Firefox 58.0 Operating System: Linux Tested Another Browser: Yes Problem type: Something else Description: It doesnt work sometimes Steps to Reproduce: [![Screenshot Description](https://webcompat.com/uploads/2017/10/6bfe1898-7f64-41a2-b303-db02b3dec479-thumb.jpg)](https://webcompat.com/uploads/2017/10/6bfe1898-7f64-41a2-b303-db02b3dec479.jpg) _From [webcompat.com](https://webcompat.com/) with ❤️_	1.0	en.savefrom.net - see bug description - <!-- @browser: Firefox 58.0 --> <!-- @ua_header: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0 --> <!-- @reported_with: addon-reporter-firefox --> URL: http://en.savefrom.net/ Browser / Version: Firefox 58.0 Operating System: Linux Tested Another Browser: Yes Problem type: Something else Description: It doesnt work sometimes Steps to Reproduce: [![Screenshot Description](https://webcompat.com/uploads/2017/10/6bfe1898-7f64-41a2-b303-db02b3dec479-thumb.jpg)](https://webcompat.com/uploads/2017/10/6bfe1898-7f64-41a2-b303-db02b3dec479.jpg) _From [webcompat.com](https://webcompat.com/) with ❤️_	priority	en savefrom net see bug description url browser version firefox operating system linux tested another browser yes problem type something else description it doesnt work sometimes steps to reproduce from with ❤️	1
493,238	14,229,390,322	IssuesEvent	2020-11-18 06:08:45	carbon-design-system/carbon-for-ibm-dotcom	https://api.github.com/repos/carbon-design-system/carbon-for-ibm-dotcom	closed	<dds-masthead-container>, etc: User-set data should take the precedence	Airtable Done Feature request dev package: web components priority: low	### The problem As of today, `<dds-masthead-container>` overrides its nav links data when it's available from API, even if it's set explicitly via application code. Such approach is hostile to one of recent user requirements: #3848 ### The solution Change such logic to make it take user-set value the precedence.	1.0	<dds-masthead-container>, etc: User-set data should take the precedence - ### The problem As of today, `<dds-masthead-container>` overrides its nav links data when it's available from API, even if it's set explicitly via application code. Such approach is hostile to one of recent user requirements: #3848 ### The solution Change such logic to make it take user-set value the precedence.	priority	etc user set data should take the precedence the problem as of today overrides its nav links data when it s available from api even if it s set explicitly via application code such approach is hostile to one of recent user requirements the solution change such logic to make it take user set value the precedence	1
534,953	15,679,314,215	IssuesEvent	2021-03-25 00:14:07	JuezUN/INGInious	https://api.github.com/repos/JuezUN/INGInious	closed	When grades are downloaded from the students option, use task name	Bug Change request Course Administration High Priority	Is your feature request related to a problem? Please describe. Currently, when the grades are downloaded as CSV, the task id is shown rather than the name. Describe the solution you'd like Show the name rather than the ID.	1.0	When grades are downloaded from the students option, use task name - Is your feature request related to a problem? Please describe. Currently, when the grades are downloaded as CSV, the task id is shown rather than the name. Describe the solution you'd like Show the name rather than the ID.	priority	when grades are downloaded from the students option use task name is your feature request related to a problem please describe currently when the grades are downloaded as csv the task id is shown rather than the name describe the solution you d like show the name rather than the id	1
794,962	28,056,728,321	IssuesEvent	2023-03-29 09:51:35	gitpod-io/gitpod	https://api.github.com/repos/gitpod-io/gitpod	opened	preview envs are flaky because of instable minio secret	type: bug priority: high (dev loop impact)	### Bug description see https://gitpod.slack.com/archives/C032A46PWR0/p1680083142076439 ### Steps to reproduce see above ### Workspace affected _No response_ ### Expected behavior _No response_ ### Example repository _No response_ ### Anything else? _No response_	1.0	preview envs are flaky because of instable minio secret - ### Bug description see https://gitpod.slack.com/archives/C032A46PWR0/p1680083142076439 ### Steps to reproduce see above ### Workspace affected _No response_ ### Expected behavior _No response_ ### Example repository _No response_ ### Anything else? _No response_	priority	preview envs are flaky because of instable minio secret bug description see steps to reproduce see above workspace affected no response expected behavior no response example repository no response anything else no response	1
269,471	20,383,449,940	IssuesEvent	2022-02-22 02:30:36	submariner-io/submariner-website	https://api.github.com/repos/submariner-io/submariner-website	closed	Decide on, and document, our Kubernetes support policy	documentation automation	The release of Kubernetes 1.23 raises the issue of what versions of Kubernetes we test against, in relation to the Kubernetes support matrix. Currently we test against 1.19 through 1.22; https://github.com/submariner-io/shipyard/pull/688 adds support for 1.23 but doesn’t change the tests (except for the “consuming e2e” Shipyard test). We should document our criteria for our Kubernetes test matrix: do we test only against currently-supported versions, or are there reasons to (a) continue testing against older releases and (b) delay testing against newer releases?	1.0	Decide on, and document, our Kubernetes support policy - The release of Kubernetes 1.23 raises the issue of what versions of Kubernetes we test against, in relation to the Kubernetes support matrix. Currently we test against 1.19 through 1.22; https://github.com/submariner-io/shipyard/pull/688 adds support for 1.23 but doesn’t change the tests (except for the “consuming e2e” Shipyard test). We should document our criteria for our Kubernetes test matrix: do we test only against currently-supported versions, or are there reasons to (a) continue testing against older releases and (b) delay testing against newer releases?	non_priority	decide on and document our kubernetes support policy the release of kubernetes raises the issue of what versions of kubernetes we test against in relation to the kubernetes support matrix currently we test against through adds support for but doesn’t change the tests except for the “consuming ” shipyard test we should document our criteria for our kubernetes test matrix do we test only against currently supported versions or are there reasons to a continue testing against older releases and b delay testing against newer releases	0
174,315	27,617,581,745	IssuesEvent	2023-03-09 20:42:01	dotnet/project-system	https://api.github.com/repos/dotnet/project-system	closed	Avoid horizontal scroll bar in launch profile arguments text box	Tenet-User Friendly Triage-Approved Feature-Project-Properties-Designer	#7919 allowed newlines in launch profile arguments for executables. If you have one very long argument then a horizontal scroll bar is introduced, making the text box harder to work with. Anecdotally, launch arguments are often file paths, which tend to be lengthy and can end up looking this like: ![image](https://user-images.githubusercontent.com/350947/161406814-9aca97a8-f431-440e-a3e0-051fce8cb23a.png) We should investigate wrapping text when it overflows here. When addressing this, we should consider whether we want to control wrapping on a per-property basis. For example, we may not wish to have wrapping for build pre/post events, which tend to contain executable code. Executable code does not format well with wrapping.	1.0	Avoid horizontal scroll bar in launch profile arguments text box - #7919 allowed newlines in launch profile arguments for executables. If you have one very long argument then a horizontal scroll bar is introduced, making the text box harder to work with. Anecdotally, launch arguments are often file paths, which tend to be lengthy and can end up looking this like: ![image](https://user-images.githubusercontent.com/350947/161406814-9aca97a8-f431-440e-a3e0-051fce8cb23a.png) We should investigate wrapping text when it overflows here. When addressing this, we should consider whether we want to control wrapping on a per-property basis. For example, we may not wish to have wrapping for build pre/post events, which tend to contain executable code. Executable code does not format well with wrapping.	non_priority	avoid horizontal scroll bar in launch profile arguments text box allowed newlines in launch profile arguments for executables if you have one very long argument then a horizontal scroll bar is introduced making the text box harder to work with anecdotally launch arguments are often file paths which tend to be lengthy and can end up looking this like we should investigate wrapping text when it overflows here when addressing this we should consider whether we want to control wrapping on a per property basis for example we may not wish to have wrapping for build pre post events which tend to contain executable code executable code does not format well with wrapping	0
9,612	3,295,841,180	IssuesEvent	2015-11-01 10:16:49	openhatch/oh-mainline	https://api.github.com/repos/openhatch/oh-mainline	closed	Add botbot.me guide to IRC to our resources and documentation	bitesize documentation links pri:feature stat:unread	There's a good IRC guide here: https://botbot.me/irc-guide/ We should share it with others.	1.0	Add botbot.me guide to IRC to our resources and documentation - There's a good IRC guide here: https://botbot.me/irc-guide/ We should share it with others.	non_priority	add botbot me guide to irc to our resources and documentation there s a good irc guide here we should share it with others	0
71,948	7,273,624,187	IssuesEvent	2018-02-21 06:18:27	minio/mint	https://api.github.com/repos/minio/mint	closed	[test] Add tests for Server silently accepts Notification config with TopicConfiguration even though no notification service is present on server	priority: medium testcase	Add a test case to validate https://github.com/minio/minio/issues/4813	1.0	[test] Add tests for Server silently accepts Notification config with TopicConfiguration even though no notification service is present on server - Add a test case to validate https://github.com/minio/minio/issues/4813	non_priority	add tests for server silently accepts notification config with topicconfiguration even though no notification service is present on server add a test case to validate	0
4,298	2,550,022,548	IssuesEvent	2015-02-01 01:47:40	pufexi/multiorder	https://api.github.com/repos/pufexi/multiorder	closed	Notifikacni emaily	enhancement high priority	TBD - to be done - dodelam Je treba vytvorit nasledujici emaily a fce, netreba aby se dali upravovat nekde... staci je napevno hodit do zdrojaku. Pri volbe "platba predem" ci "proforma" je treba zaslat EMAIL S PLATEBNIMI UDAJI	1.0	Notifikacni emaily - TBD - to be done - dodelam Je treba vytvorit nasledujici emaily a fce, netreba aby se dali upravovat nekde... staci je napevno hodit do zdrojaku. Pri volbe "platba predem" ci "proforma" je treba zaslat EMAIL S PLATEBNIMI UDAJI	priority	notifikacni emaily tbd to be done dodelam je treba vytvorit nasledujici emaily a fce netreba aby se dali upravovat nekde staci je napevno hodit do zdrojaku pri volbe platba predem ci proforma je treba zaslat email s platebnimi udaji	1
103,504	4,174,344,078	IssuesEvent	2016-06-21 13:48:28	bazingatechnologies/FSharp.Data.GraphQL	https://api.github.com/repos/bazingatechnologies/FSharp.Data.GraphQL	closed	Remove exceptions thrown in execution engine	enhancement medium-priority	Currently there are multiple places, where `GraphQLException`-like errors are thrown. I believe it's not necessary in most of these places, as we can collect possible errors in `ExecutionContext` object itself and return empty values (which we do most of the time anyway).	1.0	Remove exceptions thrown in execution engine - Currently there are multiple places, where `GraphQLException`-like errors are thrown. I believe it's not necessary in most of these places, as we can collect possible errors in `ExecutionContext` object itself and return empty values (which we do most of the time anyway).	priority	remove exceptions thrown in execution engine currently there are multiple places where graphqlexception like errors are thrown i believe it s not necessary in most of these places as we can collect possible errors in executioncontext object itself and return empty values which we do most of the time anyway	1
66,211	20,052,860,457	IssuesEvent	2022-02-03 08:55:50	vector-im/element-web	https://api.github.com/repos/vector-im/element-web	closed	Link to room without alias don't work between develop and Nightly	T-Defect X-Regression S-Minor A-Matrix.to A-Pills O-Occasional	### Steps to reproduce 1. Send `[Room](roomid)` link like `[Testing](!CMjQWAjoxImKwLBMzX:matrix.org)` 2. Send `[Room](#/room/!CMjQWAjoxImKwLBMzX:matrix.org)` ### Outcome #### What did you expect? Room is pillified and openable in both cases #### What happened instead? I can open the second link from develop, but Michael can't open it in Nightly Source: `"formatted_body": "<a href=\"#/room/!CMjQWAjoxImKwLBMzX:matrix.org\">Room</a>"` ### Operating system _No response_ ### Browser information Chromium 96.0.4664.45 (Official Build) Arch Linux (64-bit) ### URL for webapp develop.element.io ### Application version Element version: cfa97212f73e-react-074fec359b9f-js-7d2a5afa6dc9 Olm version: 3.2.8 ### Homeserver _No response_ ### Will you send logs? No	1.0	Link to room without alias don't work between develop and Nightly - ### Steps to reproduce 1. Send `[Room](roomid)` link like `[Testing](!CMjQWAjoxImKwLBMzX:matrix.org)` 2. Send `[Room](#/room/!CMjQWAjoxImKwLBMzX:matrix.org)` ### Outcome #### What did you expect? Room is pillified and openable in both cases #### What happened instead? I can open the second link from develop, but Michael can't open it in Nightly Source: `"formatted_body": "<a href=\"#/room/!CMjQWAjoxImKwLBMzX:matrix.org\">Room</a>"` ### Operating system _No response_ ### Browser information Chromium 96.0.4664.45 (Official Build) Arch Linux (64-bit) ### URL for webapp develop.element.io ### Application version Element version: cfa97212f73e-react-074fec359b9f-js-7d2a5afa6dc9 Olm version: 3.2.8 ### Homeserver _No response_ ### Will you send logs? No	non_priority	link to room without alias don t work between develop and nightly steps to reproduce send roomid link like cmjqwajoximkwlbmzx matrix org send room cmjqwajoximkwlbmzx matrix org outcome what did you expect room is pillified and openable in both cases what happened instead i can open the second link from develop but michael can t open it in nightly source formatted body room operating system no response browser information chromium official build arch linux bit url for webapp develop element io application version element version react js olm version homeserver no response will you send logs no	0
323,543	27,733,739,866	IssuesEvent	2023-03-15 09:50:06	Mbed-TLS/mbedtls	https://api.github.com/repos/Mbed-TLS/mbedtls	closed	Move TLS connection helper code out of test_suite_ssl.function	enhancement size-m component-test	`test_suite_ssl.function` contains many functions that are used to set up a TLS connection. Move those functions (and the types they use) to a new file `tests/src/ssl_helpers.c` with declarations in `tests/include/test/ssl_helpers.h`. Many of these functions are currently `static`, but will need to be exported from the new source file. They will need to be renamed so that they always start with `mbedtls_test_`. Use separate commits for separate things, so that the history is easy to understand and review. 1. Create the new source files (with just comments explaining the content, include guards, and perhaps a few `#include` that you know you'll need) and add them to the build. 2. Rename the types that need to move to have an `mbedtls_test_` prefix. If it isn't apparent from the name that the type is related to SSL, give it a prefix like `mbedtls_test_ssl_`. For example: `mbedtls_endpoint` → `mbedtls_test_ssl_endpoint`. 3. Move the `typedef` statements to the new header file. For this commit, `git show --color-moved` should show a lot of moved lines but few or no added/removed lines. 4. Rename functions that will need to be exported and make them non-static. If it isn't apparent from the name that the type is related to SSL, give it a prefix like `mbedtls_test_ssl_`. Note that functions don't need to be renamed or made non-static if they are only used by other auxiliary functions and not directly by test code. 5. If some lines have become too long due to the longer names, rewrap the lines in a separate commit. We normally limit lines to 80 characters. 6. Move those functions to the new source files. For this commit, `git show --color-moved` should show a lot of moved lines but few or no added/removed lines. Needs to be backported, so that the test code has the same structure in 2.28 and in development. Rationale: we want to have multiple test suites using these functions (`test_suite_ssl` is already too big).	1.0	Move TLS connection helper code out of test_suite_ssl.function - `test_suite_ssl.function` contains many functions that are used to set up a TLS connection. Move those functions (and the types they use) to a new file `tests/src/ssl_helpers.c` with declarations in `tests/include/test/ssl_helpers.h`. Many of these functions are currently `static`, but will need to be exported from the new source file. They will need to be renamed so that they always start with `mbedtls_test_`. Use separate commits for separate things, so that the history is easy to understand and review. 1. Create the new source files (with just comments explaining the content, include guards, and perhaps a few `#include` that you know you'll need) and add them to the build. 2. Rename the types that need to move to have an `mbedtls_test_` prefix. If it isn't apparent from the name that the type is related to SSL, give it a prefix like `mbedtls_test_ssl_`. For example: `mbedtls_endpoint` → `mbedtls_test_ssl_endpoint`. 3. Move the `typedef` statements to the new header file. For this commit, `git show --color-moved` should show a lot of moved lines but few or no added/removed lines. 4. Rename functions that will need to be exported and make them non-static. If it isn't apparent from the name that the type is related to SSL, give it a prefix like `mbedtls_test_ssl_`. Note that functions don't need to be renamed or made non-static if they are only used by other auxiliary functions and not directly by test code. 5. If some lines have become too long due to the longer names, rewrap the lines in a separate commit. We normally limit lines to 80 characters. 6. Move those functions to the new source files. For this commit, `git show --color-moved` should show a lot of moved lines but few or no added/removed lines. Needs to be backported, so that the test code has the same structure in 2.28 and in development. Rationale: we want to have multiple test suites using these functions (`test_suite_ssl` is already too big).	non_priority	move tls connection helper code out of test suite ssl function test suite ssl function contains many functions that are used to set up a tls connection move those functions and the types they use to a new file tests src ssl helpers c with declarations in tests include test ssl helpers h many of these functions are currently static but will need to be exported from the new source file they will need to be renamed so that they always start with mbedtls test use separate commits for separate things so that the history is easy to understand and review create the new source files with just comments explaining the content include guards and perhaps a few include that you know you ll need and add them to the build rename the types that need to move to have an mbedtls test prefix if it isn t apparent from the name that the type is related to ssl give it a prefix like mbedtls test ssl for example mbedtls endpoint → mbedtls test ssl endpoint move the typedef statements to the new header file for this commit git show color moved should show a lot of moved lines but few or no added removed lines rename functions that will need to be exported and make them non static if it isn t apparent from the name that the type is related to ssl give it a prefix like mbedtls test ssl note that functions don t need to be renamed or made non static if they are only used by other auxiliary functions and not directly by test code if some lines have become too long due to the longer names rewrap the lines in a separate commit we normally limit lines to characters move those functions to the new source files for this commit git show color moved should show a lot of moved lines but few or no added removed lines needs to be backported so that the test code has the same structure in and in development rationale we want to have multiple test suites using these functions test suite ssl is already too big	0
204,845	7,091,446,722	IssuesEvent	2018-01-12 13:07:31	status-im/status-react	https://api.github.com/repos/status-im/status-react	closed	"Invalid arity: 0" error if open transaction history on iOS [release]	bug high-priority release	### Description [comment]: # (Feature or Bug? i.e Type: Bug) Type: Bug [comment]: # (Describe the feature you would like, or briefly summarise the bug and what you did, what you expected to happen, and what actually happens. Sections below) Summary: Only on release build (ok in develop), so maybe some commit is not included? if open transaction history then error "Invalid arity: 0" is shown. IF close it then white screen is shown instead of Wallet ![img_1943](https://user-images.githubusercontent.com/6584810/34744823-c6bd01b2-f58e-11e7-9b84-a798a6b7e8ec.jpg) #### Expected behavior [comment]: # (Describe what you expected to happen.) Transaction history screen is shown #### Actual behavior [comment]: # (Describe what actually happened.) error "Invalid arity: 0" ### Reproduction [comment]: # (Describe how we can replicate the bug step by step.) tf: https://app.testfairy.com/projects/4803590-status/builds/7463701/sessions/4/?accessToken=nNDsguyRwKPCFqxWaf0eTC0JLFg - Open Status - Open Wallet - Open Transaction history ### Additional Information [comment]: # (Please do your best to fill this out.) * Status version: 0.9.11d538 Release build from Jan 9, 18:03 (from slack) Android: http://artifacts.status.im:8081/artifactory/nightlies-local/im.status.ethereum-bb35e4.apk iOS: https://i.diawi.com/M8qnkF Develop build where it works fine: Branch: status-im:develop Jan 9, 18:55 (from slack) Android: https://i.diawi.com/U2MSdm iOS: https://i.diawi.com/2MsZf8 * Operating System: only iOS	1.0	"Invalid arity: 0" error if open transaction history on iOS [release] - ### Description [comment]: # (Feature or Bug? i.e Type: Bug) Type: Bug [comment]: # (Describe the feature you would like, or briefly summarise the bug and what you did, what you expected to happen, and what actually happens. Sections below) Summary: Only on release build (ok in develop), so maybe some commit is not included? if open transaction history then error "Invalid arity: 0" is shown. IF close it then white screen is shown instead of Wallet ![img_1943](https://user-images.githubusercontent.com/6584810/34744823-c6bd01b2-f58e-11e7-9b84-a798a6b7e8ec.jpg) #### Expected behavior [comment]: # (Describe what you expected to happen.) Transaction history screen is shown #### Actual behavior [comment]: # (Describe what actually happened.) error "Invalid arity: 0" ### Reproduction [comment]: # (Describe how we can replicate the bug step by step.) tf: https://app.testfairy.com/projects/4803590-status/builds/7463701/sessions/4/?accessToken=nNDsguyRwKPCFqxWaf0eTC0JLFg - Open Status - Open Wallet - Open Transaction history ### Additional Information [comment]: # (Please do your best to fill this out.) * Status version: 0.9.11d538 Release build from Jan 9, 18:03 (from slack) Android: http://artifacts.status.im:8081/artifactory/nightlies-local/im.status.ethereum-bb35e4.apk iOS: https://i.diawi.com/M8qnkF Develop build where it works fine: Branch: status-im:develop Jan 9, 18:55 (from slack) Android: https://i.diawi.com/U2MSdm iOS: https://i.diawi.com/2MsZf8 * Operating System: only iOS	priority	invalid arity error if open transaction history on ios description feature or bug i e type bug type bug describe the feature you would like or briefly summarise the bug and what you did what you expected to happen and what actually happens sections below summary only on release build ok in develop so maybe some commit is not included if open transaction history then error invalid arity is shown if close it then white screen is shown instead of wallet expected behavior describe what you expected to happen transaction history screen is shown actual behavior describe what actually happened error invalid arity reproduction describe how we can replicate the bug step by step tf open status open wallet open transaction history additional information please do your best to fill this out status version release build from jan from slack android ios develop build where it works fine branch status im develop jan from slack android ios operating system only ios	1
641,652	20,831,449,516	IssuesEvent	2022-03-19 14:07:25	apache/dolphinscheduler	https://api.github.com/repos/apache/dolphinscheduler	closed	[Feature][python] Add asc file for python api release file	new feature Python priority:high	### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement. ### Description In #8343 we already add python tarball and wheel to final distribute files. But it do not add asc file to it(main apache bin and src tarball have). we have to generate asc file by ```sh gpg --yes --armor --local-user "zhongjiajie@apache.org" --output "apache-dolphinscheduler-2.0.5.tar.gz.asc" --detach-sig "apache-dolphinscheduler-2.0.5.tar.gz" gpg --yes --armor --local-user "zhongjiajie@apache.org" --output "apache_dolphinscheduler-2.0.5-py3-none-any.whl.asc" --detach-sig "apache_dolphinscheduler-2.0.5-py3-none-any.whl" ``` we should better make it auto generate. ### Use case _No response_ ### Related issues _No response_ ### Are you willing to submit a PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)	1.0	[Feature][python] Add asc file for python api release file - ### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement. ### Description In #8343 we already add python tarball and wheel to final distribute files. But it do not add asc file to it(main apache bin and src tarball have). we have to generate asc file by ```sh gpg --yes --armor --local-user "zhongjiajie@apache.org" --output "apache-dolphinscheduler-2.0.5.tar.gz.asc" --detach-sig "apache-dolphinscheduler-2.0.5.tar.gz" gpg --yes --armor --local-user "zhongjiajie@apache.org" --output "apache_dolphinscheduler-2.0.5-py3-none-any.whl.asc" --detach-sig "apache_dolphinscheduler-2.0.5-py3-none-any.whl" ``` we should better make it auto generate. ### Use case _No response_ ### Related issues _No response_ ### Are you willing to submit a PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)	priority	add asc file for python api release file search before asking i had searched in the and found no similar feature requirement description in we already add python tarball and wheel to final distribute files but it do not add asc file to it main apache bin and src tarball have we have to generate asc file by sh gpg yes armor local user zhongjiajie apache org output apache dolphinscheduler tar gz asc detach sig apache dolphinscheduler tar gz gpg yes armor local user zhongjiajie apache org output apache dolphinscheduler none any whl asc detach sig apache dolphinscheduler none any whl we should better make it auto generate use case no response related issues no response are you willing to submit a pr yes i am willing to submit a pr code of conduct i agree to follow this project s	1
135,862	19,678,044,026	IssuesEvent	2022-01-11 14:19:16	chatwoot/chatwoot	https://api.github.com/repos/chatwoot/chatwoot	opened	feat: Show context of original tweet on reyteets	Need Design	Context When retweets come in conversations, it's difficult to understand what's the parent tweet or link about parent tweet. ![image](https://user-images.githubusercontent.com/1277421/148959318-a8968e23-a196-47e4-aa7f-e89f6c25fc7b.png)	1.0	feat: Show context of original tweet on reyteets - Context When retweets come in conversations, it's difficult to understand what's the parent tweet or link about parent tweet. ![image](https://user-images.githubusercontent.com/1277421/148959318-a8968e23-a196-47e4-aa7f-e89f6c25fc7b.png)	non_priority	feat show context of original tweet on reyteets context when retweets come in conversations it s difficult to understand what s the parent tweet or link about parent tweet	0
769,050	26,991,781,272	IssuesEvent	2023-02-09 20:33:45	autogluon/autogluon	https://api.github.com/repos/autogluon/autogluon	closed	Different pytorch-lightning version ranges between autogluon.multimodal and autogluon.timeseries	module: timeseries module: multimodal dependency priority: 0	Multimodal and TimeSeries have different version ranges of pytorch-lightning Mulitmodal: https://github.com/autogluon/autogluon/blob/master/multimodal/setup.py#L40 "pytorch-lightning>=1.8.0,<1.10.0", TimeSeries: https://github.com/autogluon/autogluon/blob/master/timeseries/setup.py#L33 "pytorch-lightning>=1.7.4,<1.9.0", @sxjscience @canerturkmen Please see if we can align on a unified version range, and move the version range to `core/_setup_utils.py` to avoid code dupe.	1.0	Different pytorch-lightning version ranges between autogluon.multimodal and autogluon.timeseries - Multimodal and TimeSeries have different version ranges of pytorch-lightning Mulitmodal: https://github.com/autogluon/autogluon/blob/master/multimodal/setup.py#L40 "pytorch-lightning>=1.8.0,<1.10.0", TimeSeries: https://github.com/autogluon/autogluon/blob/master/timeseries/setup.py#L33 "pytorch-lightning>=1.7.4,<1.9.0", @sxjscience @canerturkmen Please see if we can align on a unified version range, and move the version range to `core/_setup_utils.py` to avoid code dupe.	priority	different pytorch lightning version ranges between autogluon multimodal and autogluon timeseries multimodal and timeseries have different version ranges of pytorch lightning mulitmodal pytorch lightning timeseries pytorch lightning sxjscience canerturkmen please see if we can align on a unified version range and move the version range to core setup utils py to avoid code dupe	1
91,732	3,862,270,924	IssuesEvent	2016-04-08 01:35:50	Captianrock/android_PV	https://api.github.com/repos/Captianrock/android_PV	closed	Flame graphs	High Priority New Feature	As a user of the web client, I would like to visualize the execution logs using flame graphs.	1.0	Flame graphs - As a user of the web client, I would like to visualize the execution logs using flame graphs.	priority	flame graphs as a user of the web client i would like to visualize the execution logs using flame graphs	1
125,650	16,823,204,924	IssuesEvent	2021-06-17 15:16:09	USDA-FSA/fsa-style	https://api.github.com/repos/USDA-FSA/fsa-style	opened	Revisit em-based spacing	P2 source: internal FBCSS type: design	Many components use `em`-based spacing, resulting in slightly-against-the-grain of [spacing system](https://usda-fsa.github.io/fsa-design-system/visual-style/size-and-space/).	1.0	Revisit em-based spacing - Many components use `em`-based spacing, resulting in slightly-against-the-grain of [spacing system](https://usda-fsa.github.io/fsa-design-system/visual-style/size-and-space/).	non_priority	revisit em based spacing many components use em based spacing resulting in slightly against the grain of	0
481,645	13,889,693,789	IssuesEvent	2020-10-19 08:15:56	teamforus/general	https://api.github.com/repos/teamforus/general	closed	Assign voucher with BSN to identity which logges in with DigiD	Approval: Not requested Priority: Must have Scope: Medium Status: Not Planned Type: Change request project-139	Learn more about change requests here: https://bit.ly/39CWeEE ### Requested by: Client ### Change description As a sponsor I would like to give out a voucher trough the voucher generator, and to allow a requester to apply to the same fund and automatically receive the voucher in their account. Sponsor workflow example: * Sponsor assigns (product/budget) vouchers (on bsn: #299) using the voucher generator (todo: check this userflow) * A requester receives the voucher /(activates?) * A requestor goes to the fund signup flow and requests the voucher again * requestor gets redirected to their existing voucher :) ## Goal A user that has received a voucher using the voucher generator, should not be able to also request a voucher with DigiD. ## Proposal Save BSNs & Email adresses that have recieved a voucher with the voucher generator for this fund, and when somebody later applies with DigiD, don't give out the voucher. The list with BSN numbers could be provided in any format.	1.0	Assign voucher with BSN to identity which logges in with DigiD - Learn more about change requests here: https://bit.ly/39CWeEE ### Requested by: Client ### Change description As a sponsor I would like to give out a voucher trough the voucher generator, and to allow a requester to apply to the same fund and automatically receive the voucher in their account. Sponsor workflow example: * Sponsor assigns (product/budget) vouchers (on bsn: #299) using the voucher generator (todo: check this userflow) * A requester receives the voucher /(activates?) * A requestor goes to the fund signup flow and requests the voucher again * requestor gets redirected to their existing voucher :) ## Goal A user that has received a voucher using the voucher generator, should not be able to also request a voucher with DigiD. ## Proposal Save BSNs & Email adresses that have recieved a voucher with the voucher generator for this fund, and when somebody later applies with DigiD, don't give out the voucher. The list with BSN numbers could be provided in any format.	priority	assign voucher with bsn to identity which logges in with digid learn more about change requests here requested by client change description as a sponsor i would like to give out a voucher trough the voucher generator and to allow a requester to apply to the same fund and automatically receive the voucher in their account sponsor workflow example sponsor assigns product budget vouchers on bsn using the voucher generator todo check this userflow a requester receives the voucher activates a requestor goes to the fund signup flow and requests the voucher again requestor gets redirected to their existing voucher goal a user that has received a voucher using the voucher generator should not be able to also request a voucher with digid proposal save bsns email adresses that have recieved a voucher with the voucher generator for this fund and when somebody later applies with digid don t give out the voucher the list with bsn numbers could be provided in any format	1
453,778	13,090,350,380	IssuesEvent	2020-08-03 03:01:50	kubesphere/kubesphere	https://api.github.com/repos/kubesphere/kubesphere	opened	custom project role permission - 2	area/console area/iam kind/bug priority/high	Describe the Bug A user with custom project role `Volume Snapshots View / Volume Snapshots Management` logs in. There are a few problems here. 1. Should not show overview page for this user. 2. No volume snapshot menu appears ![Screen Shot 2020-08-03 at 10 59 07 AM](https://user-images.githubusercontent.com/28859385/89141947-a50b6280-d578-11ea-81e1-edb9efc938db.png) ![Screen Shot 2020-08-03 at 10 58 57 AM](https://user-images.githubusercontent.com/28859385/89141961-ad639d80-d578-11ea-90a5-353c96a0dddd.png) Versions Used KubeSphere: 3.0.0-dev	1.0	custom project role permission - 2 - Describe the Bug A user with custom project role `Volume Snapshots View / Volume Snapshots Management` logs in. There are a few problems here. 1. Should not show overview page for this user. 2. No volume snapshot menu appears ![Screen Shot 2020-08-03 at 10 59 07 AM](https://user-images.githubusercontent.com/28859385/89141947-a50b6280-d578-11ea-81e1-edb9efc938db.png) ![Screen Shot 2020-08-03 at 10 58 57 AM](https://user-images.githubusercontent.com/28859385/89141961-ad639d80-d578-11ea-90a5-353c96a0dddd.png) Versions Used KubeSphere: 3.0.0-dev	priority	custom project role permission describe the bug a user with custom project role volume snapshots view volume snapshots management logs in there are a few problems here should not show overview page for this user no volume snapshot menu appears versions used kubesphere dev	1
435,385	12,534,944,621	IssuesEvent	2020-06-04 20:24:24	OaklandDevTeam/umbrella	https://api.github.com/repos/OaklandDevTeam/umbrella	closed	Endpoint to modify/delete drops	Priority: Low back-end enhancement	## Description Admin users and drop owners should have the ability to delete a drop and modify its description. ## Proposed endpoints * __PUT__ `/drops/<dropname>/update` ### Parameters \| Parameter \| Description \| \| :------------ \| :------------------------------------------ \| \| drop_id \| The ID of the drop being modified / updated \| \| description \| The updated description body \| ### Returns JSON \| Field \| Description \| \| :-------- \| :------------------------------------------ \| \| drop_id \| Drop ID in which modification was attempted \| \| status \| "OK", "Drop not found", "Not Authorized" \| * __DELETE__ `/drops/<dropname>/delete` ### Parameters \| Parameter \| Description \| \| :-------- \| :------------------------------- \| \| drop_id \| The ID of the drop being deleted \| ### Returns JSON \| Field \| Description \| \| :-------- \| :--------------------------------------- \| \| drop_id \| The ID of the drop being deleted \| \| status \| "OK", "Drop not found", "Not Authorized" \| ## Documentation Requirements All code should be [javadoc](https://www.jetbrains.com/help/idea/working-with-code-documentation.html) commented. The API endpoint documentation in the Github wiki needs to be updated. ## Resources * [Mongo Write operations](https://mongodb.github.io/mongo-java-driver/4.0/driver/tutorials/perform-write-operations/) * [Using Mongojack](https://mongojack.org/tutorial.html) * [Using Jackson ](https://www.baeldung.com/jackson) * [More on JSON](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON) * [Spark Docs](http://sparkjava.com/documentation) * Our Github Wiki	1.0	Endpoint to modify/delete drops - ## Description Admin users and drop owners should have the ability to delete a drop and modify its description. ## Proposed endpoints * __PUT__ `/drops/<dropname>/update` ### Parameters \| Parameter \| Description \| \| :------------ \| :------------------------------------------ \| \| drop_id \| The ID of the drop being modified / updated \| \| description \| The updated description body \| ### Returns JSON \| Field \| Description \| \| :-------- \| :------------------------------------------ \| \| drop_id \| Drop ID in which modification was attempted \| \| status \| "OK", "Drop not found", "Not Authorized" \| * __DELETE__ `/drops/<dropname>/delete` ### Parameters \| Parameter \| Description \| \| :-------- \| :------------------------------- \| \| drop_id \| The ID of the drop being deleted \| ### Returns JSON \| Field \| Description \| \| :-------- \| :--------------------------------------- \| \| drop_id \| The ID of the drop being deleted \| \| status \| "OK", "Drop not found", "Not Authorized" \| ## Documentation Requirements All code should be [javadoc](https://www.jetbrains.com/help/idea/working-with-code-documentation.html) commented. The API endpoint documentation in the Github wiki needs to be updated. ## Resources * [Mongo Write operations](https://mongodb.github.io/mongo-java-driver/4.0/driver/tutorials/perform-write-operations/) * [Using Mongojack](https://mongojack.org/tutorial.html) * [Using Jackson ](https://www.baeldung.com/jackson) * [More on JSON](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON) * [Spark Docs](http://sparkjava.com/documentation) * Our Github Wiki	priority	endpoint to modify delete drops description admin users and drop owners should have the ability to delete a drop and modify its description proposed endpoints put drops update parameters parameter description drop id the id of the drop being modified updated description the updated description body returns json field description drop id drop id in which modification was attempted status ok drop not found not authorized delete drops delete parameters parameter description drop id the id of the drop being deleted returns json field description drop id the id of the drop being deleted status ok drop not found not authorized documentation requirements all code should be commented the api endpoint documentation in the github wiki needs to be updated resources our github wiki	1
312,832	9,553,722,857	IssuesEvent	2019-05-02 20:02:25	TrinityCore/TrinityCore	https://api.github.com/repos/TrinityCore/TrinityCore	closed	[Bug] Unable to loot nodes/chests	Branch-3.3.5a Branch-master Comp-Core Priority-Low	This bug is easy to replicate, and applies to at least treasure chests and mining nodes: If you farm a node or a chest from the maximum allowable distance, the node or chest will state that "This item is already being used.", and you will be unable to loot those chests/nodes. Core: 8edecb0 DB: 335_54 ## <bountysource-plugin> Want to back this issue? [Post a bounty on it!](https://www.bountysource.com/issues/3170751-bug-unable-to-loot-nodes-chests?utm_campaign=plugin&utm_content=tracker%2F1310&utm_medium=issues&utm_source=github) We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1310&utm_medium=issues&utm_source=github). </bountysource-plugin>	1.0	[Bug] Unable to loot nodes/chests - This bug is easy to replicate, and applies to at least treasure chests and mining nodes: If you farm a node or a chest from the maximum allowable distance, the node or chest will state that "This item is already being used.", and you will be unable to loot those chests/nodes. Core: 8edecb0 DB: 335_54 ## <bountysource-plugin> Want to back this issue? [Post a bounty on it!](https://www.bountysource.com/issues/3170751-bug-unable-to-loot-nodes-chests?utm_campaign=plugin&utm_content=tracker%2F1310&utm_medium=issues&utm_source=github) We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1310&utm_medium=issues&utm_source=github). </bountysource-plugin>	priority	unable to loot nodes chests this bug is easy to replicate and applies to at least treasure chests and mining nodes if you farm a node or a chest from the maximum allowable distance the node or chest will state that this item is already being used and you will be unable to loot those chests nodes core db want to back this issue we accept bounties via	1
299,206	25,889,994,228	IssuesEvent	2022-12-14 17:10:17	ibm-openbmc/dev	https://api.github.com/repos/ibm-openbmc/dev	closed	DevOps : QEMU	prio_low devops Test NA	<a href="https://github.com/rfrandse"><img src="https://avatars3.githubusercontent.com/u/15894767?v=4" align="left" width="96" height="96" hspace="10"></img></a> Issue by [rfrandse](https://github.com/rfrandse) _Tuesday Mar 21, 2017 at 21:19 GMT_ _Originally opened as https://github.com/openbmc/openbmc/issues/1365_ ---- Someone to get the 200 docker QEMU sessions running Someone to introduce new state changes to make it all work August timeframe so we have time	1.0	DevOps : QEMU - <a href="https://github.com/rfrandse"><img src="https://avatars3.githubusercontent.com/u/15894767?v=4" align="left" width="96" height="96" hspace="10"></img></a> Issue by [rfrandse](https://github.com/rfrandse) _Tuesday Mar 21, 2017 at 21:19 GMT_ _Originally opened as https://github.com/openbmc/openbmc/issues/1365_ ---- Someone to get the 200 docker QEMU sessions running Someone to introduce new state changes to make it all work August timeframe so we have time	non_priority	devops qemu issue by tuesday mar at gmt originally opened as someone to get the docker qemu sessions running someone to introduce new state changes to make it all work august timeframe so we have time	0
661,904	22,095,394,363	IssuesEvent	2022-06-01 09:32:47	wso2/api-manager	https://api.github.com/repos/wso2/api-manager	opened	WSO2 API-M 4.1.0: Getting 404 API not found when using DB other than the default	Type/Bug Priority/Normal	### Description Changed the wso2 apim and shared db to postgresql and created the API's successfully. I can also view them in the DB. But, when I try to invoke, am getting 404. I even restarted the APIM and was able to see those API's are getting deployed from the startup logs but on calling the API, getting 404 API not found error. The same scenario and the API's worked fine in the version 3.2.0. Below are from my deployment toml file for storing and fetching the api's from DB. [apim.sync_runtime_artifacts.gateway] enable = true gateway_labels =["Default"] [apim.sync_runtime_artifacts.publisher] artifact_saver = "DBSaver" publish_directly_to_gateway = true ### Steps to Reproduce Change the APIM 4.1.0 apim and shared db to postgres, create api's ### Affected Component APIM ### Version 4.1.0 ### Environment Details (with versions) Docker OS Ubuntu 20:04 ### Relevant Log Output _No response_ ### Related Issues _No response_ ### Suggested Labels apim	1.0	WSO2 API-M 4.1.0: Getting 404 API not found when using DB other than the default - ### Description Changed the wso2 apim and shared db to postgresql and created the API's successfully. I can also view them in the DB. But, when I try to invoke, am getting 404. I even restarted the APIM and was able to see those API's are getting deployed from the startup logs but on calling the API, getting 404 API not found error. The same scenario and the API's worked fine in the version 3.2.0. Below are from my deployment toml file for storing and fetching the api's from DB. [apim.sync_runtime_artifacts.gateway] enable = true gateway_labels =["Default"] [apim.sync_runtime_artifacts.publisher] artifact_saver = "DBSaver" publish_directly_to_gateway = true ### Steps to Reproduce Change the APIM 4.1.0 apim and shared db to postgres, create api's ### Affected Component APIM ### Version 4.1.0 ### Environment Details (with versions) Docker OS Ubuntu 20:04 ### Relevant Log Output _No response_ ### Related Issues _No response_ ### Suggested Labels apim	priority	api m getting api not found when using db other than the default description changed the apim and shared db to postgresql and created the api s successfully i can also view them in the db but when i try to invoke am getting i even restarted the apim and was able to see those api s are getting deployed from the startup logs but on calling the api getting api not found error the same scenario and the api s worked fine in the version below are from my deployment toml file for storing and fetching the api s from db enable true gateway labels artifact saver dbsaver publish directly to gateway true steps to reproduce change the apim apim and shared db to postgres create api s affected component apim version environment details with versions docker os ubuntu relevant log output no response related issues no response suggested labels apim	1
683,627	23,389,256,626	IssuesEvent	2022-08-11 16:12:08	2G2C/nanotrasen-simulator	https://api.github.com/repos/2G2C/nanotrasen-simulator	closed	Crew/CPPC doesn't save	Issue: Needs Fix Priority: 2 - Medium Category: Saving	I hate saving I hate saving I hate saving While @ it, seperate saving code from index.js, stop cramming everything in index.js	1.0	Crew/CPPC doesn't save - I hate saving I hate saving I hate saving While @ it, seperate saving code from index.js, stop cramming everything in index.js	priority	crew cppc doesn t save i hate saving i hate saving i hate saving while it seperate saving code from index js stop cramming everything in index js	1
2,320	2,525,203,644	IssuesEvent	2015-01-20 22:53:06	AtlasOfLivingAustralia/biocache-service	https://api.github.com/repos/AtlasOfLivingAustralia/biocache-service	opened	Rationalise i18n mappings	enhancement priority-medium status-accepted type-enhancement	_From @djtfmartin on August 19, 2014 13:20_ migrated from: https://code.google.com/p/ala/issues/detail?id=697 date: Thu Jun 12 18:33:27 2014 author: moyesyside --- 1. Take out duplicate from messages.properties & download.properties (with download.properties being the primary source). 2. Take out all references to EL and CL layers from both. 3. Support darwin core fields in downloads with a dwcHeaders=true request params - leaving the default as is. 4. Add the description into the /search/grouped/facets service. 5. Move i18n properties in message.properties into download.properties (e.g. [http://biocache.ala.org.au/ws/index/fields](http://biocache.ala.org.au/ws/index/fields)) 6. If dwcHeaders=true, then use cl### field for headers for sampled fields. 7. Provide dwc.***** mapping in download.properties for index fields and include a dwcTerm field in /index/fields and /search/grouped/facets 8. Add sorts values (index or count). 9. Rename download.properties to fields.properties 10. Consider merging message.properties and download.properties and adding doco. _Copied from original issue: AtlasOfLivingAustralia/biocache-hubs#83_	1.0	Rationalise i18n mappings - _From @djtfmartin on August 19, 2014 13:20_ migrated from: https://code.google.com/p/ala/issues/detail?id=697 date: Thu Jun 12 18:33:27 2014 author: moyesyside --- 1. Take out duplicate from messages.properties & download.properties (with download.properties being the primary source). 2. Take out all references to EL and CL layers from both. 3. Support darwin core fields in downloads with a dwcHeaders=true request params - leaving the default as is. 4. Add the description into the /search/grouped/facets service. 5. Move i18n properties in message.properties into download.properties (e.g. [http://biocache.ala.org.au/ws/index/fields](http://biocache.ala.org.au/ws/index/fields)) 6. If dwcHeaders=true, then use cl### field for headers for sampled fields. 7. Provide dwc.***** mapping in download.properties for index fields and include a dwcTerm field in /index/fields and /search/grouped/facets 8. Add sorts values (index or count). 9. Rename download.properties to fields.properties 10. Consider merging message.properties and download.properties and adding doco. _Copied from original issue: AtlasOfLivingAustralia/biocache-hubs#83_	priority	rationalise mappings from djtfmartin on august migrated from date thu jun author moyesyside take out duplicate from messages properties download properties with download properties being the primary source take out all references to el and cl layers from both support darwin core fields in downloads with a dwcheaders true request params leaving the default as is add the description into the search grouped facets service move properties in message properties into download properties e g if dwcheaders true then use cl field for headers for sampled fields provide dwc mapping in download properties for index fields and include a dwcterm field in index fields and search grouped facets add sorts values index or count rename download properties to fields properties consider merging message properties and download properties and adding doco copied from original issue atlasoflivingaustralia biocache hubs	1
24,500	12,123,565,693	IssuesEvent	2020-04-22 12:56:02	Azure/azure-cli	https://api.github.com/repos/Azure/azure-cli	closed	[KeyVault] Enable/disable RbacAuthorization during creating or updating	KeyVault Service Team Support Request	Copied from https://github.com/Azure/azure-powershell/issues/10557 ## Description of the new feature A new key vault property is added and called RbacAuthorizationEnabled. When this is set to true the key vault will use Rbac to authorize, otherwise(false or null) it still use the legacy access policy authorization. The flag to set this including both creating new and update. ## Proposed implementation details (optional)	1.0	[KeyVault] Enable/disable RbacAuthorization during creating or updating - Copied from https://github.com/Azure/azure-powershell/issues/10557 ## Description of the new feature A new key vault property is added and called RbacAuthorizationEnabled. When this is set to true the key vault will use Rbac to authorize, otherwise(false or null) it still use the legacy access policy authorization. The flag to set this including both creating new and update. ## Proposed implementation details (optional)	non_priority	enable disable rbacauthorization during creating or updating copied from description of the new feature a new key vault property is added and called rbacauthorizationenabled when this is set to true the key vault will use rbac to authorize otherwise false or null it still use the legacy access policy authorization the flag to set this including both creating new and update proposed implementation details optional	0
746,503	26,032,576,825	IssuesEvent	2022-12-21 23:17:45	yugabyte/yugabyte-db	https://api.github.com/repos/yugabyte/yugabyte-db	closed	[DocDB] Fix the deadlock issue between CreateTable and ProcessTabletReportBatch	kind/bug area/docdb priority/medium	Jira Link: [DB-4483](https://yugabyte.atlassian.net/browse/DB-4483) ### Description There is a deadlock issue related to `CatalogManager::CreateTable` and `CatalogManager::ProcessTabletReportBatch` uncovered by tests: `org.yb.pgsql.TestYbBackup#testLegacyColocatedDBMigration` and `org.yb.pgsql.TestYbBackup#testColocatedDBWithColocationIdAlreadySet`. Test failure output for `org.yb.pgsql.TestYbBackup#testLegacyColocatedDBMigration` is attached. [org.yb.pgsql.TestYbBackup#testLegacyColocatedDBMigration.txt](https://github.com/yugabyte/yugabyte-db/files/10235157/org.yb.pgsql.TestYbBackup.testLegacyColocatedDBMigration.txt) Note: `org.yb.pgsql.TestYbBackup#testLegacyColocatedDBMigration` is a test included in an in-progress diff for #14887.	1.0	[DocDB] Fix the deadlock issue between CreateTable and ProcessTabletReportBatch - Jira Link: [DB-4483](https://yugabyte.atlassian.net/browse/DB-4483) ### Description There is a deadlock issue related to `CatalogManager::CreateTable` and `CatalogManager::ProcessTabletReportBatch` uncovered by tests: `org.yb.pgsql.TestYbBackup#testLegacyColocatedDBMigration` and `org.yb.pgsql.TestYbBackup#testColocatedDBWithColocationIdAlreadySet`. Test failure output for `org.yb.pgsql.TestYbBackup#testLegacyColocatedDBMigration` is attached. [org.yb.pgsql.TestYbBackup#testLegacyColocatedDBMigration.txt](https://github.com/yugabyte/yugabyte-db/files/10235157/org.yb.pgsql.TestYbBackup.testLegacyColocatedDBMigration.txt) Note: `org.yb.pgsql.TestYbBackup#testLegacyColocatedDBMigration` is a test included in an in-progress diff for #14887.	priority	fix the deadlock issue between createtable and processtabletreportbatch jira link description there is a deadlock issue related to catalogmanager createtable and catalogmanager processtabletreportbatch uncovered by tests org yb pgsql testybbackup testlegacycolocateddbmigration and org yb pgsql testybbackup testcolocateddbwithcolocationidalreadyset test failure output for org yb pgsql testybbackup testlegacycolocateddbmigration is attached note org yb pgsql testybbackup testlegacycolocateddbmigration is a test included in an in progress diff for	1
240,110	7,800,400,407	IssuesEvent	2018-06-09 08:58:19	tine20/Tine-2.0-Open-Source-Groupware-and-CRM	https://api.github.com/repos/tine20/Tine-2.0-Open-Source-Groupware-and-CRM	closed	0009188: some minor gui fixes	HumanResources Mantis low priority	Reported by astintzing on 31 Oct 2013 15:38 Version: Collin (2013.10.1) - on deleting vacation, sickness or extra vacation, the title of the dialog shows "(undefined.." instead of the description of the record	1.0	0009188: some minor gui fixes - Reported by astintzing on 31 Oct 2013 15:38 Version: Collin (2013.10.1) - on deleting vacation, sickness or extra vacation, the title of the dialog shows "(undefined.." instead of the description of the record	priority	some minor gui fixes reported by astintzing on oct version collin on deleting vacation sickness or extra vacation the title of the dialog shows quot undefined quot instead of the description of the record	1
573,784	17,023,707,768	IssuesEvent	2021-07-03 03:24:57	tomhughes/trac-tickets	https://api.github.com/repos/tomhughes/trac-tickets	closed	Substring of name not found - only full version or space separated version	Component: nominatim Priority: minor Resolution: fixed Type: enhancement	[Submitted to the original trac issue database at 11.43am, Friday, 29th April 2011] If one searches for "[http://open.mapquestapi.com/nominatim/v1/search.php?q=John-F.-Kennedy-Institut John-F.-Kennedy-Institut]" in Nominatim, no result is found. However, searching for "[http://open.mapquestapi.com/nominatim/v1/search.php?q=Kennedy+Institut Kennedy Institut]" finds: "John-F.-Kennedy-Institut fr Nordamerikastudien, Lansstrae, Dahlem, Steglitz-Zehlendorf, Berlin, Berlin, Stadt, Steglitz-Zehlendorf, Berlin, 14195, Germany (University)" ([http://www.openstreetmap.org/browse/node/586337277 OSM node]) (The full string also results in the correct result: "[http://open.mapquestapi.com/nominatim/v1/search.php?q=John-F.-Kennedy-Institut+fr+Nordamerikastudien John-F.-Kennedy-Institut fr Nordamerikastudien]".) Expected also for "John-F.-Kennedy-Institut" the node is found.	1.0	Substring of name not found - only full version or space separated version - [Submitted to the original trac issue database at 11.43am, Friday, 29th April 2011] If one searches for "[http://open.mapquestapi.com/nominatim/v1/search.php?q=John-F.-Kennedy-Institut John-F.-Kennedy-Institut]" in Nominatim, no result is found. However, searching for "[http://open.mapquestapi.com/nominatim/v1/search.php?q=Kennedy+Institut Kennedy Institut]" finds: "John-F.-Kennedy-Institut fr Nordamerikastudien, Lansstrae, Dahlem, Steglitz-Zehlendorf, Berlin, Berlin, Stadt, Steglitz-Zehlendorf, Berlin, 14195, Germany (University)" ([http://www.openstreetmap.org/browse/node/586337277 OSM node]) (The full string also results in the correct result: "[http://open.mapquestapi.com/nominatim/v1/search.php?q=John-F.-Kennedy-Institut+fr+Nordamerikastudien John-F.-Kennedy-Institut fr Nordamerikastudien]".) Expected also for "John-F.-Kennedy-Institut" the node is found.	priority	substring of name not found only full version or space separated version if one searches for in nominatim no result is found however searching for finds john f kennedy institut fr nordamerikastudien lansstrae dahlem steglitz zehlendorf berlin berlin stadt steglitz zehlendorf berlin germany university the full string also results in the correct result expected also for john f kennedy institut the node is found	1
380,918	11,271,487,502	IssuesEvent	2020-01-14 13:09:53	googleapis/elixir-google-api	https://api.github.com/repos/googleapis/elixir-google-api	opened	Synthesis failed for DeploymentManager	autosynth failure priority: p1 type: bug	Hello! Autosynth couldn't regenerate DeploymentManager. :broken_heart: Here's the output from running `synth.py`: ``` Cloning into 'working_repo'... Switched to branch 'autosynth-deploymentmanager' Traceback (most recent call last): File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 256, in <module> main() File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 196, in main last_synth_commit_hash = get_last_metadata_commit(args.metadata_path) File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 149, in get_last_metadata_commit text=True, File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 403, in run with Popen(popenargs, *kwargs) as process: TypeError: __init__() got an unexpected keyword argument 'text' ``` Google internal developers can see the full log [here](https://sponge/164839b8-e54e-409d-bb48-012d4d868e86).	1.0	Synthesis failed for DeploymentManager - Hello! Autosynth couldn't regenerate DeploymentManager. :broken_heart: Here's the output from running `synth.py`: ``` Cloning into 'working_repo'... Switched to branch 'autosynth-deploymentmanager' Traceback (most recent call last): File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 256, in <module> main() File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 196, in main last_synth_commit_hash = get_last_metadata_commit(args.metadata_path) File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 149, in get_last_metadata_commit text=True, File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 403, in run with Popen(popenargs, *kwargs) as process: TypeError: __init__() got an unexpected keyword argument 'text' ``` Google internal developers can see the full log [here](https://sponge/164839b8-e54e-409d-bb48-012d4d868e86).	priority	synthesis failed for deploymentmanager hello autosynth couldn t regenerate deploymentmanager broken heart here s the output from running synth py cloning into working repo switched to branch autosynth deploymentmanager traceback most recent call last file home kbuilder pyenv versions lib runpy py line in run module as main main mod spec file home kbuilder pyenv versions lib runpy py line in run code exec code run globals file tmpfs src git autosynth autosynth synth py line in main file tmpfs src git autosynth autosynth synth py line in main last synth commit hash get last metadata commit args metadata path file tmpfs src git autosynth autosynth synth py line in get last metadata commit text true file home kbuilder pyenv versions lib subprocess py line in run with popen popenargs kwargs as process typeerror init got an unexpected keyword argument text google internal developers can see the full log	1
51,706	21,781,679,622	IssuesEvent	2022-05-13 19:42:24	cityofaustin/atd-data-tech	https://api.github.com/repos/cityofaustin/atd-data-tech	closed	New account setup to access Data Tracker.	Workgroup: TED Type: IT Support Service: Apps Product: AMD Data Tracker	<!-- Email --> <!-- shanice.jackson@austintexas.gov --> > What application are you using? Data Tracker > Describe the problem. I am a new hire and need a new account setup to access Data Tracker. > How soon do you need this? Soon — This week > Requested By Shanice J. Request ID: DTS22-103985	1.0	New account setup to access Data Tracker. - <!-- Email --> <!-- shanice.jackson@austintexas.gov --> > What application are you using? Data Tracker > Describe the problem. I am a new hire and need a new account setup to access Data Tracker. > How soon do you need this? Soon — This week > Requested By Shanice J. Request ID: DTS22-103985	non_priority	new account setup to access data tracker what application are you using data tracker describe the problem i am a new hire and need a new account setup to access data tracker how soon do you need this soon — this week requested by shanice j request id	0
109,372	4,386,557,766	IssuesEvent	2016-08-08 13:15:11	raxod502/dotfiles	https://api.github.com/repos/raxod502/dotfiles	closed	Remove .zshrc.aliases	cleanup priority project zsh	As of 72fddc792cee869e460f8da80949ec2da1c9d10e, this file is no longer used. The whole system for managing it should probably go as well—I don't anticipate needing it in the future.	1.0	Remove .zshrc.aliases - As of 72fddc792cee869e460f8da80949ec2da1c9d10e, this file is no longer used. The whole system for managing it should probably go as well—I don't anticipate needing it in the future.	priority	remove zshrc aliases as of this file is no longer used the whole system for managing it should probably go as well—i don t anticipate needing it in the future	1
139,747	11,276,934,872	IssuesEvent	2020-01-15 00:56:38	brave/brave-browser	https://api.github.com/repos/brave/brave-browser	opened	webcompat reporter not remembering if a website has already been reported	QA/Test-Plan-Specified QA/Yes bug feature/shields/webcompat	<!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue. PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE. INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED--> ## Description <!--Provide a brief description of the issue--> The `webcompat reporter` under `Shields` isn't remembering if a particular website has already been reported as per the design mentioned via https://github.com/brave/brave-browser/issues/4262#issue-437884610. Example: > Shields should remember that the user has previously flagged a site for a webcompat issue. In this case, the Shields DOWN state will not have a "Report a broken site" button and instead persist the thank you message. Should be displaying the following if a website has already been reported before: ![64198693-9cc51780-ce3d-11e9-8e40-31775cf83763](https://user-images.githubusercontent.com/2602313/72395579-f4d32b00-3707-11ea-81fb-da9077bd69a7.png) ## Steps to Reproduce <!--Please add a series of steps to reproduce the issue--> 1. download & install `1.3.91 CR: 79.0.3945.117` 2. visit https://brave.com and disable shields 3. click on `Report a broken site` and select `Submit` 4. click on `Shields` again and you'll see the `Report a broken site` button again ## Actual result: <!--Please add screenshots if needed--> ![webcompatShields](https://user-images.githubusercontent.com/2602313/72395285-f819e700-3706-11ea-81a3-ff7cbea1d4b7.gif) ## Expected result: `Webcompat reporter` should remember if a user has already reported a specific site and shouldn't be displaying `Report a broken site`. ## Reproduces how often: <!--[Easily reproduced/Intermittent issue/No steps to reproduce]--> 100% reproducible when using the above STR. ## Brave version (brave://version info) <!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details--> Brave \| 1.3.91 Chromium: 79.0.3945.117 (Official Build) beta (64-bit) -- \| -- Revision \| 04f0a055010adab4484f7497fbfdbf312c307f1d-refs/branch-heads/3945@{#1019} OS \| macOS Version 10.15.2 (Build 19C57) ## Version/Channel Information: <!--Does this issue happen on any other channels? Or is it specific to a certain channel?--> - Can you reproduce this issue with the current release? `N/A` - Can you reproduce this issue with the beta channel? `Yes` - Can you reproduce this issue with the dev channel? `Yes` - Can you reproduce this issue with the nightly channel? `Yes` ## Other Additional Information: - Does the issue resolve itself when disabling Brave Shields? `N/A` - Does the issue resolve itself when disabling Brave Rewards? `N/A` - Is the issue reproducible on the latest version of Chrome? `N/A` ## Miscellaneous Information: <!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue--> CCing @cezaraugusto @karenkliu @rebron @brave/legacy_qa	1.0	webcompat reporter not remembering if a website has already been reported - <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue. PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE. INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED--> ## Description <!--Provide a brief description of the issue--> The `webcompat reporter` under `Shields` isn't remembering if a particular website has already been reported as per the design mentioned via https://github.com/brave/brave-browser/issues/4262#issue-437884610. Example: > Shields should remember that the user has previously flagged a site for a webcompat issue. In this case, the Shields DOWN state will not have a "Report a broken site" button and instead persist the thank you message. Should be displaying the following if a website has already been reported before: ![64198693-9cc51780-ce3d-11e9-8e40-31775cf83763](https://user-images.githubusercontent.com/2602313/72395579-f4d32b00-3707-11ea-81fb-da9077bd69a7.png) ## Steps to Reproduce <!--Please add a series of steps to reproduce the issue--> 1. download & install `1.3.91 CR: 79.0.3945.117` 2. visit https://brave.com and disable shields 3. click on `Report a broken site` and select `Submit` 4. click on `Shields` again and you'll see the `Report a broken site` button again ## Actual result: <!--Please add screenshots if needed--> ![webcompatShields](https://user-images.githubusercontent.com/2602313/72395285-f819e700-3706-11ea-81a3-ff7cbea1d4b7.gif) ## Expected result: `Webcompat reporter` should remember if a user has already reported a specific site and shouldn't be displaying `Report a broken site`. ## Reproduces how often: <!--[Easily reproduced/Intermittent issue/No steps to reproduce]--> 100% reproducible when using the above STR. ## Brave version (brave://version info) <!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details--> Brave \| 1.3.91 Chromium: 79.0.3945.117 (Official Build) beta (64-bit) -- \| -- Revision \| 04f0a055010adab4484f7497fbfdbf312c307f1d-refs/branch-heads/3945@{#1019} OS \| macOS Version 10.15.2 (Build 19C57) ## Version/Channel Information: <!--Does this issue happen on any other channels? Or is it specific to a certain channel?--> - Can you reproduce this issue with the current release? `N/A` - Can you reproduce this issue with the beta channel? `Yes` - Can you reproduce this issue with the dev channel? `Yes` - Can you reproduce this issue with the nightly channel? `Yes` ## Other Additional Information: - Does the issue resolve itself when disabling Brave Shields? `N/A` - Does the issue resolve itself when disabling Brave Rewards? `N/A` - Is the issue reproducible on the latest version of Chrome? `N/A` ## Miscellaneous Information: <!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue--> CCing @cezaraugusto @karenkliu @rebron @brave/legacy_qa	non_priority	webcompat reporter not remembering if a website has already been reported have you searched for similar issues before submitting this issue please check the open issues and add a note before logging a new issue please use the template below to provide information about the issue insufficient info will get the issue closed it will only be reopened after sufficient info is provided description the webcompat reporter under shields isn t remembering if a particular website has already been reported as per the design mentioned via example shields should remember that the user has previously flagged a site for a webcompat issue in this case the shields down state will not have a report a broken site button and instead persist the thank you message should be displaying the following if a website has already been reported before steps to reproduce download install cr visit and disable shields click on report a broken site and select submit click on shields again and you ll see the report a broken site button again actual result expected result webcompat reporter should remember if a user has already reported a specific site and shouldn t be displaying report a broken site reproduces how often reproducible when using the above str brave version brave version info brave chromium official build beta bit revision refs branch heads os macos version build version channel information can you reproduce this issue with the current release n a can you reproduce this issue with the beta channel yes can you reproduce this issue with the dev channel yes can you reproduce this issue with the nightly channel yes other additional information does the issue resolve itself when disabling brave shields n a does the issue resolve itself when disabling brave rewards n a is the issue reproducible on the latest version of chrome n a miscellaneous information ccing cezaraugusto karenkliu rebron brave legacy qa	0
237,453	26,085,145,552	IssuesEvent	2022-12-26 01:09:20	xlizaluizax/gridsome-forestry-starter	https://api.github.com/repos/xlizaluizax/gridsome-forestry-starter	opened	CVE-2022-37603 (High) detected in loader-utils-1.4.0.tgz	security vulnerability	## CVE-2022-37603 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>loader-utils-1.4.0.tgz</b></p></summary> <p>utils for webpack loaders</p> <p>Library home page: <a href="https://registry.npmjs.org/loader-utils/-/loader-utils-1.4.0.tgz">https://registry.npmjs.org/loader-utils/-/loader-utils-1.4.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/loader-utils/package.json</p> <p> Dependency Hierarchy: - gridsome-0.7.13.tgz (Root Library) - :x: loader-utils-1.4.0.tgz (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> A Regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils 2.0.0 via the url variable in interpolateName.js. <p>Publish Date: 2022-10-14 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-37603>CVE-2022-37603</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-3rfm-jhwj-7488">https://github.com/advisories/GHSA-3rfm-jhwj-7488</a></p> <p>Release Date: 2022-10-14</p> <p>Fix Resolution (loader-utils): 2.0.4</p> <p>Direct dependency fix Resolution (gridsome): 0.7.14</p> </p> </details> <p></p> *** Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)	True	CVE-2022-37603 (High) detected in loader-utils-1.4.0.tgz - ## CVE-2022-37603 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>loader-utils-1.4.0.tgz</b></p></summary> <p>utils for webpack loaders</p> <p>Library home page: <a href="https://registry.npmjs.org/loader-utils/-/loader-utils-1.4.0.tgz">https://registry.npmjs.org/loader-utils/-/loader-utils-1.4.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/loader-utils/package.json</p> <p> Dependency Hierarchy: - gridsome-0.7.13.tgz (Root Library) - :x: loader-utils-1.4.0.tgz (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> A Regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils 2.0.0 via the url variable in interpolateName.js. <p>Publish Date: 2022-10-14 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-37603>CVE-2022-37603</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-3rfm-jhwj-7488">https://github.com/advisories/GHSA-3rfm-jhwj-7488</a></p> <p>Release Date: 2022-10-14</p> <p>Fix Resolution (loader-utils): 2.0.4</p> <p>Direct dependency fix Resolution (gridsome): 0.7.14</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 loader utils tgz cve high severity vulnerability vulnerable library loader utils tgz utils for webpack loaders library home page a href path to dependency file package json path to vulnerable library node modules loader utils package json dependency hierarchy gridsome tgz root library x loader utils tgz vulnerable library found in base branch master vulnerability details a regular expression denial of service redos flaw was found in function interpolatename in interpolatename js in webpack loader utils via the url variable in interpolatename js 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 loader utils direct dependency fix resolution gridsome step up your open source security game with mend	0
306,028	26,429,973,261	IssuesEvent	2023-01-14 17:40:57	platformio/platformio-core	https://api.github.com/repos/platformio/platformio-core	closed	Incorrect test summary when testcase name includes colon (e.g. in different namespaces)	bug unit testing	What kind of issue is this? - [X] PlatformIO Core. ------------------------------------------------------------------ ### Configuration Operating system: Linux Mint 21.1 Vera PlatformIO Version: `PlatformIO Core, version 6.1.5` ### Description of problem Testcases which have a colon in their name are not correctly counted in the summary of `pio test`. This affects in particular all testcases functions residing in a different namespace. The summary always declares "0 test cases: 0 succeeded". #### Steps to Reproduce Create a project with a unique test located in a different namespace, e.g. `test::dummy` (see below) invoked with a fully qualified namespace. Alternatively, it's enough to test the following line: ``` test/test_main.cpp:5:test::dummy:FAIL: Expression Evaluated To FALSE ``` against [this `TESTCASE_PARSE_RE` regex](https://github.com/platformio/platformio-core/blob/cd8024c762bf5bae8caf210b9224548bee55ee04/platformio/test/runners/unity.py#L34). ### Actual Results ``` test/test_main.cpp:5:test::dummy:FAIL: Expression Evaluated To FALSE ----------------------- 1 Tests 1 Failures 0 Ignored FAIL ---------------- esp32:* [PASSED] Took 40.03 seconds ---------------- ============================== SUMMARY ============================== Environment Test Status Duration ------------- ------ -------- ------------ esp32 * SKIPPED 00:00:40.027 ============= 0 test cases: 0 succeeded in 00:00:40.027 ============= ``` ### Expected Results ``` ---------------- esp32:* [FAILED] Took 11.78 seconds ---------------- ============================== SUMMARY ============================== Environment Test Status Duration ------------- ------ -------- ------------ esp32 * FAILED 00:00:11.781 ______________________________ esp32:* ______________________________ test/test_main.cpp:5:test::dummy:FAIL: Expression Evaluated To FALSE ======== 1 test cases: 1 failed, 0 succeeded in 00:00:11.781 ======== ``` ### If problems with PlatformIO Build System: The content of `platformio.ini`: ```ini [env:esp32] platform=espressif32 framework=espidf board=esp32dev ``` Source file to reproduce issue: `test/test_main.cpp` ```cpp #include <unity.h> namespace test { void dummy() { TEST_ASSERT(false); } } extern "C" void app_main() { UNITY_BEGIN(); RUN_TEST(test::dummy); UNITY_END(); } ```	1.0	Incorrect test summary when testcase name includes colon (e.g. in different namespaces) - What kind of issue is this? - [X] PlatformIO Core. ------------------------------------------------------------------ ### Configuration Operating system: Linux Mint 21.1 Vera PlatformIO Version: `PlatformIO Core, version 6.1.5` ### Description of problem Testcases which have a colon in their name are not correctly counted in the summary of `pio test`. This affects in particular all testcases functions residing in a different namespace. The summary always declares "0 test cases: 0 succeeded". #### Steps to Reproduce Create a project with a unique test located in a different namespace, e.g. `test::dummy` (see below) invoked with a fully qualified namespace. Alternatively, it's enough to test the following line: ``` test/test_main.cpp:5:test::dummy:FAIL: Expression Evaluated To FALSE ``` against [this `TESTCASE_PARSE_RE` regex](https://github.com/platformio/platformio-core/blob/cd8024c762bf5bae8caf210b9224548bee55ee04/platformio/test/runners/unity.py#L34). ### Actual Results ``` test/test_main.cpp:5:test::dummy:FAIL: Expression Evaluated To FALSE ----------------------- 1 Tests 1 Failures 0 Ignored FAIL ---------------- esp32:* [PASSED] Took 40.03 seconds ---------------- ============================== SUMMARY ============================== Environment Test Status Duration ------------- ------ -------- ------------ esp32 * SKIPPED 00:00:40.027 ============= 0 test cases: 0 succeeded in 00:00:40.027 ============= ``` ### Expected Results ``` ---------------- esp32:* [FAILED] Took 11.78 seconds ---------------- ============================== SUMMARY ============================== Environment Test Status Duration ------------- ------ -------- ------------ esp32 * FAILED 00:00:11.781 ______________________________ esp32:* ______________________________ test/test_main.cpp:5:test::dummy:FAIL: Expression Evaluated To FALSE ======== 1 test cases: 1 failed, 0 succeeded in 00:00:11.781 ======== ``` ### If problems with PlatformIO Build System: The content of `platformio.ini`: ```ini [env:esp32] platform=espressif32 framework=espidf board=esp32dev ``` Source file to reproduce issue: `test/test_main.cpp` ```cpp #include <unity.h> namespace test { void dummy() { TEST_ASSERT(false); } } extern "C" void app_main() { UNITY_BEGIN(); RUN_TEST(test::dummy); UNITY_END(); } ```	non_priority	incorrect test summary when testcase name includes colon e g in different namespaces what kind of issue is this platformio core configuration operating system linux mint vera platformio version platformio core version description of problem testcases which have a colon in their name are not correctly counted in the summary of pio test this affects in particular all testcases functions residing in a different namespace the summary always declares test cases succeeded steps to reproduce create a project with a unique test located in a different namespace e g test dummy see below invoked with a fully qualified namespace alternatively it s enough to test the following line test test main cpp test dummy fail expression evaluated to false against actual results test test main cpp test dummy fail expression evaluated to false tests failures ignored fail took seconds summary environment test status duration skipped test cases succeeded in expected results took seconds summary environment test status duration failed test test main cpp test dummy fail expression evaluated to false test cases failed succeeded in if problems with platformio build system the content of platformio ini ini platform framework espidf board source file to reproduce issue test test main cpp cpp include namespace test void dummy test assert false extern c void app main unity begin run test test dummy unity end	0
117,781	25,194,826,341	IssuesEvent	2022-11-12 11:20:56	joomla/joomla-cms	https://api.github.com/repos/joomla/joomla-cms	closed	[4.0] Bug in published method in Joomla\CMS\HTML\Helpers\Grid class	No Code Attached Yet J4 Issue J4 Backend Template	### Steps to reproduce the issue The method published in Joomla\CMS\HTML\Helpers\Grid https://github.com/joomla/joomla-cms/blob/4.0-dev/libraries/src/HTML/Helpers/Grid.php#L190 is used to render published/unpublished icon and allow users to click on to unpublish/publish an item (usually used on list views backend) If you look at the code of the method, it looks for tick.png and publish_x.png icon under images/admin folder of administrator template, however, these icons are not available in the admin template for Joomla 4, so it is not rendered properly anymore ### Expected result The published/unpublished icon is displayed to allow clicking on to change state of the record ### Actual result The published/unpublished icon is not being displayed ### Additional comments Use published method from Joomla\CMS\HTML\Helpers\JGrid to replace this old method.	1.0	[4.0] Bug in published method in Joomla\CMS\HTML\Helpers\Grid class - ### Steps to reproduce the issue The method published in Joomla\CMS\HTML\Helpers\Grid https://github.com/joomla/joomla-cms/blob/4.0-dev/libraries/src/HTML/Helpers/Grid.php#L190 is used to render published/unpublished icon and allow users to click on to unpublish/publish an item (usually used on list views backend) If you look at the code of the method, it looks for tick.png and publish_x.png icon under images/admin folder of administrator template, however, these icons are not available in the admin template for Joomla 4, so it is not rendered properly anymore ### Expected result The published/unpublished icon is displayed to allow clicking on to change state of the record ### Actual result The published/unpublished icon is not being displayed ### Additional comments Use published method from Joomla\CMS\HTML\Helpers\JGrid to replace this old method.	non_priority	bug in published method in joomla cms html helpers grid class steps to reproduce the issue the method published in joomla cms html helpers grid is used to render published unpublished icon and allow users to click on to unpublish publish an item usually used on list views backend if you look at the code of the method it looks for tick png and publish x png icon under images admin folder of administrator template however these icons are not available in the admin template for joomla so it is not rendered properly anymore expected result the published unpublished icon is displayed to allow clicking on to change state of the record actual result the published unpublished icon is not being displayed additional comments use published method from joomla cms html helpers jgrid to replace this old method	0
110,322	4,425,194,961	IssuesEvent	2016-08-16 14:48:54	JMurk/Valve_Hydrant_Mobile_Issues	https://api.github.com/repos/JMurk/Valve_Hydrant_Mobile_Issues	closed	Valves & Hydrants - Save warning after save	bug moderate priority	If the user updates a valve and saves it, when they attempt to navigate back to the map they are met with the warning that unsaved changes will be lost. Please disable this warning if the user has already pressed the save button. ![image](https://cloud.githubusercontent.com/assets/7118831/17624568/1c9b3458-6073-11e6-81ce-8ade8c2f27f2.png)	1.0	Valves & Hydrants - Save warning after save - If the user updates a valve and saves it, when they attempt to navigate back to the map they are met with the warning that unsaved changes will be lost. Please disable this warning if the user has already pressed the save button. ![image](https://cloud.githubusercontent.com/assets/7118831/17624568/1c9b3458-6073-11e6-81ce-8ade8c2f27f2.png)	priority	valves hydrants save warning after save if the user updates a valve and saves it when they attempt to navigate back to the map they are met with the warning that unsaved changes will be lost please disable this warning if the user has already pressed the save button	1
61,187	14,943,088,526	IssuesEvent	2021-01-25 22:22:51	osquery/osquery	https://api.github.com/repos/osquery/osquery	closed	cannot build via cmake on Windows with a space in username	Windows build triage	<!-- Thank you for contributing to osquery! --> # Bug report osquery cannot be built with the supported workflow via cmake on Windows if you've gone through the setup assistant and created a user like a normal person. this probably isn't an issue on computers which are AD bound and don't have spaces in usernames, and isn't an issue for users who only provide one name at the setup assistant. i think this was an issue before the build system got redone too, but probably in separate places. ### What operating system and version are you using? windows 10 1903 64 bit ### What version of osquery are you using? 4.1.0 ### What steps did you take to reproduce the issue? - install windows 10 - create a user during the setup assistant with a space in it, like your real name. use that user for the rest of it. - install dependencies as required - build with `cmake --build . --config RelWithDebInfo -j10` as documented ### What did you expect to see? osquery builds ### What did you see instead? it errors out on at least one formula, the openssl one. example from error: ``` cl : Command line warning D9024: unrecognized source file type 'Keeley/osquery/build/libs/fb/zlib/zlib/1.2.11/include', object file assumed [C:\Users\Samuel Keeley\osquery\build\openssl\openssl.vcxproj] cl : Command line warning D9027: source file 'Keeley/osquery/build/libs/fb/zlib/zlib/1.2.11/include' ignored [C:\Users\Samuel Keeley\osquery\build\openssl\openssl.vcxproj] c_zlib.c ```	1.0	cannot build via cmake on Windows with a space in username - <!-- Thank you for contributing to osquery! --> # Bug report osquery cannot be built with the supported workflow via cmake on Windows if you've gone through the setup assistant and created a user like a normal person. this probably isn't an issue on computers which are AD bound and don't have spaces in usernames, and isn't an issue for users who only provide one name at the setup assistant. i think this was an issue before the build system got redone too, but probably in separate places. ### What operating system and version are you using? windows 10 1903 64 bit ### What version of osquery are you using? 4.1.0 ### What steps did you take to reproduce the issue? - install windows 10 - create a user during the setup assistant with a space in it, like your real name. use that user for the rest of it. - install dependencies as required - build with `cmake --build . --config RelWithDebInfo -j10` as documented ### What did you expect to see? osquery builds ### What did you see instead? it errors out on at least one formula, the openssl one. example from error: ``` cl : Command line warning D9024: unrecognized source file type 'Keeley/osquery/build/libs/fb/zlib/zlib/1.2.11/include', object file assumed [C:\Users\Samuel Keeley\osquery\build\openssl\openssl.vcxproj] cl : Command line warning D9027: source file 'Keeley/osquery/build/libs/fb/zlib/zlib/1.2.11/include' ignored [C:\Users\Samuel Keeley\osquery\build\openssl\openssl.vcxproj] c_zlib.c ```	non_priority	cannot build via cmake on windows with a space in username bug report osquery cannot be built with the supported workflow via cmake on windows if you ve gone through the setup assistant and created a user like a normal person this probably isn t an issue on computers which are ad bound and don t have spaces in usernames and isn t an issue for users who only provide one name at the setup assistant i think this was an issue before the build system got redone too but probably in separate places what operating system and version are you using windows bit what version of osquery are you using what steps did you take to reproduce the issue install windows create a user during the setup assistant with a space in it like your real name use that user for the rest of it install dependencies as required build with cmake build config relwithdebinfo as documented what did you expect to see osquery builds what did you see instead it errors out on at least one formula the openssl one example from error cl command line warning unrecognized source file type keeley osquery build libs fb zlib zlib include object file assumed cl command line warning source file keeley osquery build libs fb zlib zlib include ignored c zlib c	0
615,286	19,252,484,122	IssuesEvent	2021-12-09 07:36:51	pingcap/ticdc	https://api.github.com/repos/pingcap/ticdc	closed	owner changefeed info is not up to date which causes gc safepoint advances unexpectedly	type/bug priority/p0 difficulty/medium severity/major area/ticdc	## Bug Report Please answer these questions before submitting your issue. Thanks! 1. What did you do? If possible, provide a recipe for reproducing the error. 1. Set up a cdc cluster with 3 nodes and create two changefeeds, replicate to MySQL-1 and MySQL-2 respectively. The changefeeds work normally. 2. Shutdown MySQL-1, the changefeed-1 will soon stop. 3. Resume changefeed-1, the changefeed will retry but fail. 4. Change cdc owner 5. The new owner will try to start changefeed-1, but will fail at last. 6. The calculation of gc safepoint will not take changefeed-1 into consideration, after gc safepoint exceeds, the changefeed will become `failed` state. 2. What did you expect to see? The gc safepoint should not advance 3. What did you see instead? The gc safepoint advances 4. Versions of the cluster - Upstream TiDB cluster version (execute `SELECT tidb_version();` in a MySQL client): 5.0.0 - TiCDC version (execute `cdc version`): In 4.0.x, 5.0.0 and master	1.0	owner changefeed info is not up to date which causes gc safepoint advances unexpectedly - ## Bug Report Please answer these questions before submitting your issue. Thanks! 1. What did you do? If possible, provide a recipe for reproducing the error. 1. Set up a cdc cluster with 3 nodes and create two changefeeds, replicate to MySQL-1 and MySQL-2 respectively. The changefeeds work normally. 2. Shutdown MySQL-1, the changefeed-1 will soon stop. 3. Resume changefeed-1, the changefeed will retry but fail. 4. Change cdc owner 5. The new owner will try to start changefeed-1, but will fail at last. 6. The calculation of gc safepoint will not take changefeed-1 into consideration, after gc safepoint exceeds, the changefeed will become `failed` state. 2. What did you expect to see? The gc safepoint should not advance 3. What did you see instead? The gc safepoint advances 4. Versions of the cluster - Upstream TiDB cluster version (execute `SELECT tidb_version();` in a MySQL client): 5.0.0 - TiCDC version (execute `cdc version`): In 4.0.x, 5.0.0 and master	priority	owner changefeed info is not up to date which causes gc safepoint advances unexpectedly bug report please answer these questions before submitting your issue thanks what did you do if possible provide a recipe for reproducing the error set up a cdc cluster with nodes and create two changefeeds replicate to mysql and mysql respectively the changefeeds work normally shutdown mysql the changefeed will soon stop resume changefeed the changefeed will retry but fail change cdc owner the new owner will try to start changefeed but will fail at last the calculation of gc safepoint will not take changefeed into consideration after gc safepoint exceeds the changefeed will become failed state what did you expect to see the gc safepoint should not advance what did you see instead the gc safepoint advances versions of the cluster upstream tidb cluster version execute select tidb version in a mysql client ticdc version execute cdc version in x and master	1
205,518	23,340,995,915	IssuesEvent	2022-08-09 14:01:32	elastic/integrations	https://api.github.com/repos/elastic/integrations	closed	[ti_anomali] ECS 8.4.0 threat.indicator.type and threat.indicator.confidence expected value mismatch	bug Team:Security-External Integrations	When upgrading to ECS 8.4.0 you get the following error in limo datastream: ``` one or more errors found in document: [0] parsing field value failed: field "threat.indicator.type"'s value "unknown" is not one of the expected values (autonomous-system, artifact, directory, domain-name, email-addr, file, ipv4-addr, ipv6-addr, mac-addr, mutex, port, process, software, url, user-account, windows-registry-key, x509-certificate) ``` and following error in threatstream datastream: ``` one or more errors found in document: [0] parsing field value failed: field "threat.indicator.confidence"'s value "Med" is not one of the expected values (Not Specified, None, Low, Medium, High) [1] parsing field value failed: field "threat.indicator.marking.tlp"'s value "White" is not one of the expected values (WHITE, GREEN, AMBER, RED) ```	True	[ti_anomali] ECS 8.4.0 threat.indicator.type and threat.indicator.confidence expected value mismatch - When upgrading to ECS 8.4.0 you get the following error in limo datastream: ``` one or more errors found in document: [0] parsing field value failed: field "threat.indicator.type"'s value "unknown" is not one of the expected values (autonomous-system, artifact, directory, domain-name, email-addr, file, ipv4-addr, ipv6-addr, mac-addr, mutex, port, process, software, url, user-account, windows-registry-key, x509-certificate) ``` and following error in threatstream datastream: ``` one or more errors found in document: [0] parsing field value failed: field "threat.indicator.confidence"'s value "Med" is not one of the expected values (Not Specified, None, Low, Medium, High) [1] parsing field value failed: field "threat.indicator.marking.tlp"'s value "White" is not one of the expected values (WHITE, GREEN, AMBER, RED) ```	non_priority	ecs threat indicator type and threat indicator confidence expected value mismatch when upgrading to ecs you get the following error in limo datastream one or more errors found in document parsing field value failed field threat indicator type s value unknown is not one of the expected values autonomous system artifact directory domain name email addr file addr addr mac addr mutex port process software url user account windows registry key certificate and following error in threatstream datastream one or more errors found in document parsing field value failed field threat indicator confidence s value med is not one of the expected values not specified none low medium high parsing field value failed field threat indicator marking tlp s value white is not one of the expected values white green amber red	0
15,963	6,066,451,232	IssuesEvent	2017-06-14 18:31:02	docker/cli	https://api.github.com/repos/docker/cli	closed	"docker stack rm" results in "page not found"	area/builder area/swarm priority/P1 version/17.05	I'm guessing this is related to https://github.com/docker/cli/pull/162 I'm using a master build which I think has the fix for #162 ``` C:\Users\friism>docker version Client: Version: 17.06.0-dev API version: 1.29 (downgraded from 1.30) Go version: go1.8.3 Git commit: f82f61e Built: Sun Jun 11 23:59:54 2017 OS/Arch: windows/amd64 Server: Version: 17.05.0-ce API version: 1.29 (minimum version 1.12) Go version: go1.7.5 Git commit: 89658be Built: Thu May 4 22:10:54 2017 OS/Arch: linux/amd64 Experimental: false ``` ``` C:\code\atsea-sample-shop-app>docker service ls ID NAME MODE REPLICAS IMAGE PORTS 9sr4ophfuwmm atsea_reverse_proxy replicated 0/1 friism/reverse_proxy:latest hwcgsqn3kio3 atsea_database replicated 1/1 friism/atsea_db:latest :5432->5432/tcp ov06vkl99x6c dockercloud-server-proxy global 1/1 dockercloud/server-proxy:latest :2376->2376/tcp s45iwlnfbskp atsea_payment_gateway replicated 1/1 friism/payment_gateway:latest w8v9yf4aunyv atsea_appserver replicated 1/1 friism/atsea_app:latest :5005->5005/tcp,:8080->8080/tcp C:\code\atsea-sample-shop-app>docker stack ls NAME SERVICES atsea 4 C:\code\atsea-sample-shop-app>docker stack rm atsea Error response from daemon: page not found version: "3.1" services: reverse_proxy: build: ./reverse_proxy image: friism/reverse_proxy database: build: context: ./database image: friism/atsea_db environment: POSTGRES_USER: gordonuser POSTGRES_DB_PASSWORD_FILE: /run/secrets/postgres_password POSTGRES_DB: atsea ports: - "5432:5432" networks: - back-tier secrets: - postgres_password appserver: build: context: app dockerfile: Dockerfile image: friism/atsea_app ports: - "8080:8080" - "5005:5005" networks: - front-tier - back-tier secrets: - postgres_password payment_gateway: build: context: payment_gateway image: friism/payment_gateway networks: - payment secrets: - payment_token networks: front-tier: back-tier: payment: driver: overlay secrets: postgres_password: file: ./devsecrets/postgres_password payment_token: file: ./devsecrets/payment_token C:\code\atsea-sample-shop-app> ```	1.0	"docker stack rm" results in "page not found" - I'm guessing this is related to https://github.com/docker/cli/pull/162 I'm using a master build which I think has the fix for #162 ``` C:\Users\friism>docker version Client: Version: 17.06.0-dev API version: 1.29 (downgraded from 1.30) Go version: go1.8.3 Git commit: f82f61e Built: Sun Jun 11 23:59:54 2017 OS/Arch: windows/amd64 Server: Version: 17.05.0-ce API version: 1.29 (minimum version 1.12) Go version: go1.7.5 Git commit: 89658be Built: Thu May 4 22:10:54 2017 OS/Arch: linux/amd64 Experimental: false ``` ``` C:\code\atsea-sample-shop-app>docker service ls ID NAME MODE REPLICAS IMAGE PORTS 9sr4ophfuwmm atsea_reverse_proxy replicated 0/1 friism/reverse_proxy:latest hwcgsqn3kio3 atsea_database replicated 1/1 friism/atsea_db:latest :5432->5432/tcp ov06vkl99x6c dockercloud-server-proxy global 1/1 dockercloud/server-proxy:latest :2376->2376/tcp s45iwlnfbskp atsea_payment_gateway replicated 1/1 friism/payment_gateway:latest w8v9yf4aunyv atsea_appserver replicated 1/1 friism/atsea_app:latest :5005->5005/tcp,:8080->8080/tcp C:\code\atsea-sample-shop-app>docker stack ls NAME SERVICES atsea 4 C:\code\atsea-sample-shop-app>docker stack rm atsea Error response from daemon: page not found version: "3.1" services: reverse_proxy: build: ./reverse_proxy image: friism/reverse_proxy database: build: context: ./database image: friism/atsea_db environment: POSTGRES_USER: gordonuser POSTGRES_DB_PASSWORD_FILE: /run/secrets/postgres_password POSTGRES_DB: atsea ports: - "5432:5432" networks: - back-tier secrets: - postgres_password appserver: build: context: app dockerfile: Dockerfile image: friism/atsea_app ports: - "8080:8080" - "5005:5005" networks: - front-tier - back-tier secrets: - postgres_password payment_gateway: build: context: payment_gateway image: friism/payment_gateway networks: - payment secrets: - payment_token networks: front-tier: back-tier: payment: driver: overlay secrets: postgres_password: file: ./devsecrets/postgres_password payment_token: file: ./devsecrets/payment_token C:\code\atsea-sample-shop-app> ```	non_priority	docker stack rm results in page not found i m guessing this is related to i m using a master build which i think has the fix for c users friism docker version client version dev api version downgraded from go version git commit built sun jun os arch windows server version ce api version minimum version go version git commit built thu may os arch linux experimental false c code atsea sample shop app docker service ls id name mode replicas image ports atsea reverse proxy replicated friism reverse proxy latest atsea database replicated friism atsea db latest tcp dockercloud server proxy global dockercloud server proxy latest tcp atsea payment gateway replicated friism payment gateway latest atsea appserver replicated friism atsea app latest tcp tcp c code atsea sample shop app docker stack ls name services atsea c code atsea sample shop app docker stack rm atsea error response from daemon page not found version services reverse proxy build reverse proxy image friism reverse proxy database build context database image friism atsea db environment postgres user gordonuser postgres db password file run secrets postgres password postgres db atsea ports networks back tier secrets postgres password appserver build context app dockerfile dockerfile image friism atsea app ports networks front tier back tier secrets postgres password payment gateway build context payment gateway image friism payment gateway networks payment secrets payment token networks front tier back tier payment driver overlay secrets postgres password file devsecrets postgres password payment token file devsecrets payment token c code atsea sample shop app	0
808	2,920,250,806	IssuesEvent	2015-06-24 18:01:13	ualbertalib/discovery	https://api.github.com/repos/ualbertalib/discovery	opened	Update solrconfig	Infrastructure	I guess it should? <lib dir="/opt/solr/lib/contrib/analysis-extras/lib" /> <lib dir="/opt/solr/lib/contrib/analysis-extras/lucene-libs" /> <lib dir="/opt/solr/lib/contrib/extraction/lib" regex=".*\.jar" /> Please also change to the following in solrconfig.xml. I know this is different on Solr Jetty for Sam (LUCENE_40) <luceneMatchVersion>4.9</luceneMatchVersion>	1.0	Update solrconfig - I guess it should? <lib dir="/opt/solr/lib/contrib/analysis-extras/lib" /> <lib dir="/opt/solr/lib/contrib/analysis-extras/lucene-libs" /> <lib dir="/opt/solr/lib/contrib/extraction/lib" regex=".*\.jar" /> Please also change to the following in solrconfig.xml. I know this is different on Solr Jetty for Sam (LUCENE_40) <luceneMatchVersion>4.9</luceneMatchVersion>	non_priority	update solrconfig i guess it should please also change to the following in solrconfig xml i know this is different on solr jetty for sam lucene	0
177,297	6,576,389,569	IssuesEvent	2017-09-11 19:39:09	mlibrary/umrdr	https://api.github.com/repos/mlibrary/umrdr	closed	Add alert for large file issue	RDS Priority	## Background or Context We need to inform depositors that we cannot download files larger than 2GB. ## Desired Behavior/Capability This alert should be added to the "Deposit Work" page as well to the About page referencing file size: https://deepblue.lib.umich.edu/data/prepare-your-data to this bullet "For deposits exceeding 2 GB, we will work with depositors to ingest your data. Please contact us if your deposit exceeds 2 GB." Here is the alert language: 8/16/2017 - We are currently implementing a solution for downloading large datasets. Until this solution is in place, we are not accepting files larger than 2GB. We will post updates as they become available. In the meantime, please feel free to contact [Research Data Services](mailto:deepblue@umich.edu) with any related questions or concerns, so your data will be ready to be deposited when our system is ready to go. ## Existing Behavior/Capability ## Steps to reproduce or demonstrate	1.0	Add alert for large file issue - ## Background or Context We need to inform depositors that we cannot download files larger than 2GB. ## Desired Behavior/Capability This alert should be added to the "Deposit Work" page as well to the About page referencing file size: https://deepblue.lib.umich.edu/data/prepare-your-data to this bullet "For deposits exceeding 2 GB, we will work with depositors to ingest your data. Please contact us if your deposit exceeds 2 GB." Here is the alert language: 8/16/2017 - We are currently implementing a solution for downloading large datasets. Until this solution is in place, we are not accepting files larger than 2GB. We will post updates as they become available. In the meantime, please feel free to contact [Research Data Services](mailto:deepblue@umich.edu) with any related questions or concerns, so your data will be ready to be deposited when our system is ready to go. ## Existing Behavior/Capability ## Steps to reproduce or demonstrate	priority	add alert for large file issue background or context we need to inform depositors that we cannot download files larger than desired behavior capability this alert should be added to the deposit work page as well to the about page referencing file size to this bullet for deposits exceeding gb we will work with depositors to ingest your data please contact us if your deposit exceeds gb here is the alert language we are currently implementing a solution for downloading large datasets until this solution is in place we are not accepting files larger than we will post updates as they become available in the meantime please feel free to contact mailto deepblue umich edu with any related questions or concerns so your data will be ready to be deposited when our system is ready to go existing behavior capability steps to reproduce or demonstrate	1
578,744	17,151,180,935	IssuesEvent	2021-07-13 20:51:55	pytorch/pytorch	https://api.github.com/repos/pytorch/pytorch	closed	_unsafe_view returns copy if self has conjugate bit set	high priority module: complex triaged	Since `_unsafe_view`'s schema has no alias info, ConjugateFallback considers it an out-of-place operation, so the conjugate is always materialized, producing a copy. ``` auto a = torch::tensor(1., at::TensorOptions().dtype(at::ScalarType::ComplexDouble)).conj(); auto b = at::_unsafe_view(a, {1}); b += 1; std::cout << "a: " << a << "b: " << b << std::endl; ``` Output: ``` a: [W Copy.cpp:240] Warning: Casting complex values to real discards the imaginary part (function operator()) 1 [ CPUComplexDoubleType{} ] b: 2 [ CPUComplexDoubleType{1} ] ``` cc @ezyang @gchanan @zou3519 @bdhirsh @jbschlosser @anjali411 @dylanbespalko @mruberry @Lezcano @nikitaved	1.0	_unsafe_view returns copy if self has conjugate bit set - Since `_unsafe_view`'s schema has no alias info, ConjugateFallback considers it an out-of-place operation, so the conjugate is always materialized, producing a copy. ``` auto a = torch::tensor(1., at::TensorOptions().dtype(at::ScalarType::ComplexDouble)).conj(); auto b = at::_unsafe_view(a, {1}); b += 1; std::cout << "a: " << a << "b: " << b << std::endl; ``` Output: ``` a: [W Copy.cpp:240] Warning: Casting complex values to real discards the imaginary part (function operator()) 1 [ CPUComplexDoubleType{} ] b: 2 [ CPUComplexDoubleType{1} ] ``` cc @ezyang @gchanan @zou3519 @bdhirsh @jbschlosser @anjali411 @dylanbespalko @mruberry @Lezcano @nikitaved	priority	unsafe view returns copy if self has conjugate bit set since unsafe view s schema has no alias info conjugatefallback considers it an out of place operation so the conjugate is always materialized producing a copy auto a torch tensor at tensoroptions dtype at scalartype complexdouble conj auto b at unsafe view a b std cout a a b b std endl output a warning casting complex values to real discards the imaginary part function operator b cc ezyang gchanan bdhirsh jbschlosser dylanbespalko mruberry lezcano nikitaved	1
795,309	28,069,142,057	IssuesEvent	2023-03-29 17:40:59	SzFMV2023-Tavasz/AutomatedCar-A	https://api.github.com/repos/SzFMV2023-Tavasz/AutomatedCar-A	opened	Handling gear shift prohibitions	effort: low priority: high	The only possible sequence is P-R-N-D. ### Dependency: ► Gearbox ► IDriveChainInterface ### Acceptance criteria ► unit test for this function ► all tests are passed	1.0	Handling gear shift prohibitions - The only possible sequence is P-R-N-D. ### Dependency: ► Gearbox ► IDriveChainInterface ### Acceptance criteria ► unit test for this function ► all tests are passed	priority	handling gear shift prohibitions the only possible sequence is p r n d dependency ► gearbox ► idrivechaininterface acceptance criteria ► unit test for this function ► all tests are passed	1
795,461	28,073,831,893	IssuesEvent	2023-03-29 21:17:23	berkeley-dsep-infra/datahub	https://api.github.com/repos/berkeley-dsep-infra/datahub	closed	Change letsencrypt acme email address	bug priority: low maintenance window	### Bug description `support/templates/issuer.yaml` has the parameter `spec.acme.email=yuvipanda@gmail.com`. This should be changed to a service address like ds-instr or ds-infrastructure, though I don't know the full ramifications of doing so. It may briefly disrupt SSL service upon redeploy. Waiting until a maintenance window is probably fine. ### Environment & setup . ### How to reproduce .	1.0	Change letsencrypt acme email address - ### Bug description `support/templates/issuer.yaml` has the parameter `spec.acme.email=yuvipanda@gmail.com`. This should be changed to a service address like ds-instr or ds-infrastructure, though I don't know the full ramifications of doing so. It may briefly disrupt SSL service upon redeploy. Waiting until a maintenance window is probably fine. ### Environment & setup . ### How to reproduce .	priority	change letsencrypt acme email address bug description support templates issuer yaml has the parameter spec acme email yuvipanda gmail com this should be changed to a service address like ds instr or ds infrastructure though i don t know the full ramifications of doing so it may briefly disrupt ssl service upon redeploy waiting until a maintenance window is probably fine environment setup how to reproduce	1
180,768	30,564,925,844	IssuesEvent	2023-07-20 17:01:39	processing/p5.js-website	https://api.github.com/repos/processing/p5.js-website	closed	p5.js Accessibility Audit Discussion	Web Design Discussion	### Topic Hi everyone! As a part of my GSoC project, I completed an accessibility audit for the p5.js documentation site (excluding the editor). Before I begin fixing the issues I found, I wanted to see what issues everyone thinks should be prioritized (I have about a 3-4 week timeframe for this part of the project). You’re welcome to help fix these issues as well-- I think some of the ones I found might take a while to resolve. These are the issues I’d like to tackle: 1. Color contrast issues (the brand color and search bar) 2. UI component consistency across the site (buttons) 3. Filling out the footer with the primary nav links 4. Adding focus states to the Language section 5. Begin the discussion around the code block keyboard traps (?) Outside of those, I think the next most important issues to resolve are: Reference page tabbing issues, improving the Search bar(s), Horizontal scroll on mobile, tabbing issues on the Teach page, Reference page back button, and the 404 pages. This is up for debate, so if you’d like to propose a different prioritization order, feel free to comment and help make this list better. ## Scoping: This audit does not cover internationalization or translation issues, since others are already working on these. This audit does not cover the p5.js editor, only the documentation aspect of the site. I'm also mainly focusing on the most popular pages, especially the Home and Reference pages. The full audit I completed discusses some issues found on the Showcase page as well, but for the sake of time and scoping, I'll focus this next portion of the project on the pages usually involved in the main user journey(s). ## Accessibility Issues: ### High Severity: #### _Brand Color_ The pink brand color (#ED225D) [does not have enough contrast](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=245#contrast-minimum) on the site’s white background (WCAG 1.4.3). Also, the light gray applied to buttons and the search input is also inaccessible. There are a few ways to go about improving the color contrast of the site’s elements: 1. Make sure the pink brand color isn’t applied to any text or interactive elements (including the cards found on the site’s Download page) and choose a secondary brand color with enough contrast to visually distinguish these elements from the rest of the site’s elements. 2. As specified in the WCAG Sufficient Techniques, provide a control for the user to change the color of the “pink-ified” elements to a higher-contrast color. There’s been a petition for a [“dark theme” for the website](https://github.com/processing/p5.js-website/issues/956), which could also fit under the Sufficient Techniques category if the colors used in this theme contain a high enough contrast. #### _Consistent Button Styling_ Across the site, there are at least two different secondary button designs-- one of which has insufficient contrast against its background. When I first saw the buttons on the Reference page, I thought they were disabled with how invisible they were against the background. ![image](https://github.com/processing/p5.js-website/assets/59926191/cd9cd38e-332c-4f12-857b-6ab4d3f725da) Providing a consistent button design to use across the site will help with brand cohesion, predictability, and overall improved navigation. This may involve modifying, improving, or publicizing a design system for all contributors to easily access. For the time being, I think supplying a quick guide for basic components is sufficient, just to hold out until a larger redesign of the site is underway. #### _Modifying Search Input for Greater Affordance_ As discussed in this [search box](https://github.com/processing/p5.js-website/issues/1348) GitHub issue, the current search bar is very minimal, which causes some keyboard accessibility issues. “Tabbing” into the search bar is somewhat of a hit-and-miss, whether or not the focus will properly activate on the search bar and type in it. For greater keyboard accessibility and visual affordance, adding a “Go” button to the search input will allow keyboard-based and screen-reader-based users to have multiple ways to input a search query. #### _Tabbing Focus States and Order_ If you don’t select the “Skip to Main Content” button, there are about 5 to 6 tabs that are “lost” on the page, showing no active focus states for any interactive elements. These lost tabs appear to be the Language links in the top right corner. ![image](https://github.com/processing/p5.js-website/assets/59926191/0bddabc8-7c03-4596-b2fc-b78a23f40e50) #### _Keyboard Traps and Code Blocks_ When navigating the Reference page examples via keyboard or screen reader, the code blocks, if you edit the code, results in a keyboard trap where the user can’t exit the text box. #### _Reference Page Tabbing_ If you select the “Skip to Main Content” button on the Reference example pages, this button redirects a user viewing a function’s Reference page back to the overarching Reference index. My theory is because all of the Reference content exists on the same HTML file, and because the display styling of the `item-wrapper apidocs` div is changed when the user selects a specific function’s reference, the “Skip to main content page” somehow refreshes any JS-related styling changes and redirects the user back to the Reference index. The same issue with the “lost” tabbing sequence exists on this page as well. ![image](https://github.com/processing/p5.js-website/assets/59926191/b859f65a-e18f-456b-8829-fb1bb9c769e0) #### _Teach Page_ On the site’s Teach page, while navigating through all the interactive elements, it seems like the filters hidden by the “Search Filter” button are still visible to screen readers and keyboards. This results in a long sequence of “lost” tabbing through invisible elements on the page. ![image](https://github.com/processing/p5.js-website/assets/59926191/5e17b3b7-31cd-41cc-9123-be3bb7207711) ### Moderate Severity: #### _Improving Donate’s Slideshow_ On the Donate Page, some of the [alt text](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=245#non-text-content) in the image slideshow can be improved to better reflect the image content. There’s already a petition to revise the slideshow and add a [pause/play button](https://github.com/processing/p5.js-website/issues/635), which does comply with W3C’s idea that content should not move or change unless the user intentionally causes the interaction or animation (WCAG 1.1.1). Because these images aren’t necessarily required to fully understand the overall p5 experience, I’m placing them at moderate severity. That said, since this is a Level A requirement, the overall necessity to have proper alt text for photos is rudimentary for standard accessibility guidelines. #### _Removing Horizontal Scroll on Mobile_ On mobile devices, depending on the viewport size and its magnification, a [horizontal scroll](https://www.w3.org/WAI/WCAG21/quickref/#visual-presentation) may appear (WCAG 1.4.7). I think the social media links in the footer are causing most instances of the horizontal scroll, since it seems they don’t wrap when the viewport is adjusted to a width smaller than their list. A horizontal scroll also appears on some Reference sections when the formula’s name extends beyond the viewport’s width. In cases where the title or heading of a page is long, this CSS [word-wrap](https://www.w3schools.com/cssref/css3_pr_word-wrap.php) styling can be applied to break the word in cases where the word is too long to fit in the viewport. Since the text does resize and wrap, and since the navigation and other interactive elements aren’t clipped or unusable on smaller devices, I’ll place this issue at moderate severity. #### _Reference Page Back Button_ Adding a “back button” at the top of the main content could help users navigate between different Reference sub-pages. This isn’t important (mainly cosmetic), but I believe adding a way to navigate back that doesn’t rely on the main navigation sidebar might be more intuitive than the current navigation processes (hitting the back button in the browser, or selecting Reference from the sidebar). #### _Footer_ Adding the primary navigation links into the footer will help with overall accessibility and user-error prevention, so that users using screen readers or keyboard-based navigation don’t have to navigate back up to the top of the page to reach the main navigation again. ### Low Severity: #### _Improving the 404 Page_ As of now, the site’s 404 page is pretty dull and doesn’t redirect the user back to home, or their previously-viewed page. Some people have already designed a [possible 404 page](https://github.com/processing/p5.js-website/issues/1028) to adapt, and if there are no server-side or development-based issues with applying this 404 page to the site, this would be a great contribution to the overall usability of the site. Because the Showcase and Contributor pages have very different styling compared to the rest of the site, I believe this may involve creating three different 404 pages for each section of the site, ensuring that each instance of the 404 page matches each section’s unique styling. If you have any questions, feel free to reach out. Thank you!	1.0	p5.js Accessibility Audit Discussion - ### Topic Hi everyone! As a part of my GSoC project, I completed an accessibility audit for the p5.js documentation site (excluding the editor). Before I begin fixing the issues I found, I wanted to see what issues everyone thinks should be prioritized (I have about a 3-4 week timeframe for this part of the project). You’re welcome to help fix these issues as well-- I think some of the ones I found might take a while to resolve. These are the issues I’d like to tackle: 1. Color contrast issues (the brand color and search bar) 2. UI component consistency across the site (buttons) 3. Filling out the footer with the primary nav links 4. Adding focus states to the Language section 5. Begin the discussion around the code block keyboard traps (?) Outside of those, I think the next most important issues to resolve are: Reference page tabbing issues, improving the Search bar(s), Horizontal scroll on mobile, tabbing issues on the Teach page, Reference page back button, and the 404 pages. This is up for debate, so if you’d like to propose a different prioritization order, feel free to comment and help make this list better. ## Scoping: This audit does not cover internationalization or translation issues, since others are already working on these. This audit does not cover the p5.js editor, only the documentation aspect of the site. I'm also mainly focusing on the most popular pages, especially the Home and Reference pages. The full audit I completed discusses some issues found on the Showcase page as well, but for the sake of time and scoping, I'll focus this next portion of the project on the pages usually involved in the main user journey(s). ## Accessibility Issues: ### High Severity: #### _Brand Color_ The pink brand color (#ED225D) [does not have enough contrast](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=245#contrast-minimum) on the site’s white background (WCAG 1.4.3). Also, the light gray applied to buttons and the search input is also inaccessible. There are a few ways to go about improving the color contrast of the site’s elements: 1. Make sure the pink brand color isn’t applied to any text or interactive elements (including the cards found on the site’s Download page) and choose a secondary brand color with enough contrast to visually distinguish these elements from the rest of the site’s elements. 2. As specified in the WCAG Sufficient Techniques, provide a control for the user to change the color of the “pink-ified” elements to a higher-contrast color. There’s been a petition for a [“dark theme” for the website](https://github.com/processing/p5.js-website/issues/956), which could also fit under the Sufficient Techniques category if the colors used in this theme contain a high enough contrast. #### _Consistent Button Styling_ Across the site, there are at least two different secondary button designs-- one of which has insufficient contrast against its background. When I first saw the buttons on the Reference page, I thought they were disabled with how invisible they were against the background. ![image](https://github.com/processing/p5.js-website/assets/59926191/cd9cd38e-332c-4f12-857b-6ab4d3f725da) Providing a consistent button design to use across the site will help with brand cohesion, predictability, and overall improved navigation. This may involve modifying, improving, or publicizing a design system for all contributors to easily access. For the time being, I think supplying a quick guide for basic components is sufficient, just to hold out until a larger redesign of the site is underway. #### _Modifying Search Input for Greater Affordance_ As discussed in this [search box](https://github.com/processing/p5.js-website/issues/1348) GitHub issue, the current search bar is very minimal, which causes some keyboard accessibility issues. “Tabbing” into the search bar is somewhat of a hit-and-miss, whether or not the focus will properly activate on the search bar and type in it. For greater keyboard accessibility and visual affordance, adding a “Go” button to the search input will allow keyboard-based and screen-reader-based users to have multiple ways to input a search query. #### _Tabbing Focus States and Order_ If you don’t select the “Skip to Main Content” button, there are about 5 to 6 tabs that are “lost” on the page, showing no active focus states for any interactive elements. These lost tabs appear to be the Language links in the top right corner. ![image](https://github.com/processing/p5.js-website/assets/59926191/0bddabc8-7c03-4596-b2fc-b78a23f40e50) #### _Keyboard Traps and Code Blocks_ When navigating the Reference page examples via keyboard or screen reader, the code blocks, if you edit the code, results in a keyboard trap where the user can’t exit the text box. #### _Reference Page Tabbing_ If you select the “Skip to Main Content” button on the Reference example pages, this button redirects a user viewing a function’s Reference page back to the overarching Reference index. My theory is because all of the Reference content exists on the same HTML file, and because the display styling of the `item-wrapper apidocs` div is changed when the user selects a specific function’s reference, the “Skip to main content page” somehow refreshes any JS-related styling changes and redirects the user back to the Reference index. The same issue with the “lost” tabbing sequence exists on this page as well. ![image](https://github.com/processing/p5.js-website/assets/59926191/b859f65a-e18f-456b-8829-fb1bb9c769e0) #### _Teach Page_ On the site’s Teach page, while navigating through all the interactive elements, it seems like the filters hidden by the “Search Filter” button are still visible to screen readers and keyboards. This results in a long sequence of “lost” tabbing through invisible elements on the page. ![image](https://github.com/processing/p5.js-website/assets/59926191/5e17b3b7-31cd-41cc-9123-be3bb7207711) ### Moderate Severity: #### _Improving Donate’s Slideshow_ On the Donate Page, some of the [alt text](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=245#non-text-content) in the image slideshow can be improved to better reflect the image content. There’s already a petition to revise the slideshow and add a [pause/play button](https://github.com/processing/p5.js-website/issues/635), which does comply with W3C’s idea that content should not move or change unless the user intentionally causes the interaction or animation (WCAG 1.1.1). Because these images aren’t necessarily required to fully understand the overall p5 experience, I’m placing them at moderate severity. That said, since this is a Level A requirement, the overall necessity to have proper alt text for photos is rudimentary for standard accessibility guidelines. #### _Removing Horizontal Scroll on Mobile_ On mobile devices, depending on the viewport size and its magnification, a [horizontal scroll](https://www.w3.org/WAI/WCAG21/quickref/#visual-presentation) may appear (WCAG 1.4.7). I think the social media links in the footer are causing most instances of the horizontal scroll, since it seems they don’t wrap when the viewport is adjusted to a width smaller than their list. A horizontal scroll also appears on some Reference sections when the formula’s name extends beyond the viewport’s width. In cases where the title or heading of a page is long, this CSS [word-wrap](https://www.w3schools.com/cssref/css3_pr_word-wrap.php) styling can be applied to break the word in cases where the word is too long to fit in the viewport. Since the text does resize and wrap, and since the navigation and other interactive elements aren’t clipped or unusable on smaller devices, I’ll place this issue at moderate severity. #### _Reference Page Back Button_ Adding a “back button” at the top of the main content could help users navigate between different Reference sub-pages. This isn’t important (mainly cosmetic), but I believe adding a way to navigate back that doesn’t rely on the main navigation sidebar might be more intuitive than the current navigation processes (hitting the back button in the browser, or selecting Reference from the sidebar). #### _Footer_ Adding the primary navigation links into the footer will help with overall accessibility and user-error prevention, so that users using screen readers or keyboard-based navigation don’t have to navigate back up to the top of the page to reach the main navigation again. ### Low Severity: #### _Improving the 404 Page_ As of now, the site’s 404 page is pretty dull and doesn’t redirect the user back to home, or their previously-viewed page. Some people have already designed a [possible 404 page](https://github.com/processing/p5.js-website/issues/1028) to adapt, and if there are no server-side or development-based issues with applying this 404 page to the site, this would be a great contribution to the overall usability of the site. Because the Showcase and Contributor pages have very different styling compared to the rest of the site, I believe this may involve creating three different 404 pages for each section of the site, ensuring that each instance of the 404 page matches each section’s unique styling. If you have any questions, feel free to reach out. Thank you!	non_priority	js accessibility audit discussion topic hi everyone as a part of my gsoc project i completed an accessibility audit for the js documentation site excluding the editor before i begin fixing the issues i found i wanted to see what issues everyone thinks should be prioritized i have about a week timeframe for this part of the project you’re welcome to help fix these issues as well i think some of the ones i found might take a while to resolve these are the issues i’d like to tackle color contrast issues the brand color and search bar ui component consistency across the site buttons filling out the footer with the primary nav links adding focus states to the language section begin the discussion around the code block keyboard traps outside of those i think the next most important issues to resolve are reference page tabbing issues improving the search bar s horizontal scroll on mobile tabbing issues on the teach page reference page back button and the pages this is up for debate so if you’d like to propose a different prioritization order feel free to comment and help make this list better scoping this audit does not cover internationalization or translation issues since others are already working on these this audit does not cover the js editor only the documentation aspect of the site i m also mainly focusing on the most popular pages especially the home and reference pages the full audit i completed discusses some issues found on the showcase page as well but for the sake of time and scoping i ll focus this next portion of the project on the pages usually involved in the main user journey s accessibility issues high severity brand color the pink brand color on the site’s white background wcag also the light gray applied to buttons and the search input is also inaccessible there are a few ways to go about improving the color contrast of the site’s elements make sure the pink brand color isn’t applied to any text or interactive elements including the cards found on the site’s download page and choose a secondary brand color with enough contrast to visually distinguish these elements from the rest of the site’s elements as specified in the wcag sufficient techniques provide a control for the user to change the color of the “pink ified” elements to a higher contrast color there’s been a petition for a which could also fit under the sufficient techniques category if the colors used in this theme contain a high enough contrast consistent button styling across the site there are at least two different secondary button designs one of which has insufficient contrast against its background when i first saw the buttons on the reference page i thought they were disabled with how invisible they were against the background providing a consistent button design to use across the site will help with brand cohesion predictability and overall improved navigation this may involve modifying improving or publicizing a design system for all contributors to easily access for the time being i think supplying a quick guide for basic components is sufficient just to hold out until a larger redesign of the site is underway modifying search input for greater affordance as discussed in this github issue the current search bar is very minimal which causes some keyboard accessibility issues “tabbing” into the search bar is somewhat of a hit and miss whether or not the focus will properly activate on the search bar and type in it for greater keyboard accessibility and visual affordance adding a “go” button to the search input will allow keyboard based and screen reader based users to have multiple ways to input a search query tabbing focus states and order if you don’t select the “skip to main content” button there are about to tabs that are “lost” on the page showing no active focus states for any interactive elements these lost tabs appear to be the language links in the top right corner keyboard traps and code blocks when navigating the reference page examples via keyboard or screen reader the code blocks if you edit the code results in a keyboard trap where the user can’t exit the text box reference page tabbing if you select the “skip to main content” button on the reference example pages this button redirects a user viewing a function’s reference page back to the overarching reference index my theory is because all of the reference content exists on the same html file and because the display styling of the item wrapper apidocs div is changed when the user selects a specific function’s reference the “skip to main content page” somehow refreshes any js related styling changes and redirects the user back to the reference index the same issue with the “lost” tabbing sequence exists on this page as well teach page on the site’s teach page while navigating through all the interactive elements it seems like the filters hidden by the “search filter” button are still visible to screen readers and keyboards this results in a long sequence of “lost” tabbing through invisible elements on the page moderate severity improving donate’s slideshow on the donate page some of the in the image slideshow can be improved to better reflect the image content there’s already a petition to revise the slideshow and add a which does comply with ’s idea that content should not move or change unless the user intentionally causes the interaction or animation wcag because these images aren’t necessarily required to fully understand the overall experience i’m placing them at moderate severity that said since this is a level a requirement the overall necessity to have proper alt text for photos is rudimentary for standard accessibility guidelines removing horizontal scroll on mobile on mobile devices depending on the viewport size and its magnification a may appear wcag i think the social media links in the footer are causing most instances of the horizontal scroll since it seems they don’t wrap when the viewport is adjusted to a width smaller than their list a horizontal scroll also appears on some reference sections when the formula’s name extends beyond the viewport’s width in cases where the title or heading of a page is long this css styling can be applied to break the word in cases where the word is too long to fit in the viewport since the text does resize and wrap and since the navigation and other interactive elements aren’t clipped or unusable on smaller devices i’ll place this issue at moderate severity reference page back button adding a “back button” at the top of the main content could help users navigate between different reference sub pages this isn’t important mainly cosmetic but i believe adding a way to navigate back that doesn’t rely on the main navigation sidebar might be more intuitive than the current navigation processes hitting the back button in the browser or selecting reference from the sidebar footer adding the primary navigation links into the footer will help with overall accessibility and user error prevention so that users using screen readers or keyboard based navigation don’t have to navigate back up to the top of the page to reach the main navigation again low severity improving the page as of now the site’s page is pretty dull and doesn’t redirect the user back to home or their previously viewed page some people have already designed a to adapt and if there are no server side or development based issues with applying this page to the site this would be a great contribution to the overall usability of the site because the showcase and contributor pages have very different styling compared to the rest of the site i believe this may involve creating three different pages for each section of the site ensuring that each instance of the page matches each section’s unique styling if you have any questions feel free to reach out thank you	0
91,358	26,368,895,761	IssuesEvent	2023-01-11 18:52:23	LLNL/axom	https://api.github.com/repos/LLNL/axom	closed	CMake errors when building with the latest camp, umpire, and raja	Build system	CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/core/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/lumberjack/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/slic/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/slam/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/primal/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/sidre/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/mint/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/spin/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/inlet/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/klee/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/quest/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/multimat/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/core/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/lumberjack/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/slic/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/slam/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/primal/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/sidre/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/mint/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/spin/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/inlet/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/klee/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/quest/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/multimat/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/core/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/lumberjack/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/slic/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/slam/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/primal/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/sidre/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/mint/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/spin/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/inlet/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/klee/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/quest/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/multimat/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/core/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/lumberjack/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/slic/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/slam/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/primal/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/sidre/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/mint/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/spin/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/inlet/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/klee/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/quest/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/multimat/include" which is prefixed in the source directory.	1.0	CMake errors when building with the latest camp, umpire, and raja - CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/core/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/lumberjack/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/slic/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/slam/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/primal/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/sidre/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/mint/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/spin/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/inlet/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/klee/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/quest/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/multimat/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/core/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/lumberjack/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/slic/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/slam/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/primal/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/sidre/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/mint/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/spin/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/inlet/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/klee/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/quest/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/multimat/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/core/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/lumberjack/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/slic/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/slam/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/primal/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/sidre/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/mint/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/spin/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/inlet/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/klee/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/quest/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/multimat/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/core/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/lumberjack/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/slic/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/slam/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/primal/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/sidre/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/mint/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/spin/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/inlet/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/klee/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/quest/include" which is prefixed in the source directory. CMake Error in axom/CMakeLists.txt: Target "axom" INTERFACE_INCLUDE_DIRECTORIES property contains path: "/g/g17/dayton8/ale3d/update_compiler_branch/imports/axom/src/axom/multimat/include" which is prefixed in the source directory.	non_priority	cmake errors when building with the latest camp umpire and raja cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom core include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom lumberjack include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom slic include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom slam include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom primal include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom sidre include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom mint include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom spin include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom inlet include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom klee include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom quest include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom multimat include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom core include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom lumberjack include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom slic include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom slam include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom primal include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom sidre include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom mint include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom spin include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom inlet include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom klee include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom quest include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom multimat include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom core include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom lumberjack include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom slic include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom slam include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom primal include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom sidre include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom mint include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom spin include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom inlet include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom klee include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom quest include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom multimat include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom core include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom lumberjack include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom slic include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom slam include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom primal include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom sidre include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom mint include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom spin include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom inlet include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom klee include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom quest include which is prefixed in the source directory cmake error in axom cmakelists txt target axom interface include directories property contains path g update compiler branch imports axom src axom multimat include which is prefixed in the source directory	0
637,010	20,617,520,964	IssuesEvent	2022-03-07 14:34:14	pkp/pkp-lib	https://api.github.com/repos/pkp/pkp-lib	closed	Select language when using email templates	Community Priority Enhancement	When sending an email template, it should be possible to send an email template in the language appropriate for the recipient. - Ability to determine and auto-select recipient language where possible. - Override the default with the language we'd like. - All variables used in the email should be rendered in the correct language. There is an existing setting under the user profile for "Working Languages" that could be used. See https://forum.pkp.sfu.ca/t/ojs-3-x-x-choice-to-pick-language-for-forms-and-templates-when-sending-e-mails/31849 and #3523.	1.0	Select language when using email templates - When sending an email template, it should be possible to send an email template in the language appropriate for the recipient. - Ability to determine and auto-select recipient language where possible. - Override the default with the language we'd like. - All variables used in the email should be rendered in the correct language. There is an existing setting under the user profile for "Working Languages" that could be used. See https://forum.pkp.sfu.ca/t/ojs-3-x-x-choice-to-pick-language-for-forms-and-templates-when-sending-e-mails/31849 and #3523.	priority	select language when using email templates when sending an email template it should be possible to send an email template in the language appropriate for the recipient ability to determine and auto select recipient language where possible override the default with the language we d like all variables used in the email should be rendered in the correct language there is an existing setting under the user profile for working languages that could be used see and	1
236,650	18,104,763,699	IssuesEvent	2021-09-22 17:56:43	Open-MSS/MSS	https://api.github.com/repos/Open-MSS/MSS	closed	move retriever module into the documentation samples	documentation enhancement	The current mslib/retriever.py needs changes by an user to retrieve data or changes to create the plots the user wants. I think there is a high potential that this script always needs changes. We should remove it from the entry_points of the meta.yaml and move this script to docs/samples,	1.0	move retriever module into the documentation samples - The current mslib/retriever.py needs changes by an user to retrieve data or changes to create the plots the user wants. I think there is a high potential that this script always needs changes. We should remove it from the entry_points of the meta.yaml and move this script to docs/samples,	non_priority	move retriever module into the documentation samples the current mslib retriever py needs changes by an user to retrieve data or changes to create the plots the user wants i think there is a high potential that this script always needs changes we should remove it from the entry points of the meta yaml and move this script to docs samples	0
338,607	24,592,554,843	IssuesEvent	2022-10-14 04:37:59	open-metadata/OpenMetadata	https://api.github.com/repos/open-metadata/OpenMetadata	closed	Update doc for Databricks Usage and lineage	documentation	Add Databricks Usage and lineage details in the doc.	1.0	Update doc for Databricks Usage and lineage - Add Databricks Usage and lineage details in the doc.	non_priority	update doc for databricks usage and lineage add databricks usage and lineage details in the doc	0
118,774	4,755,744,170	IssuesEvent	2016-10-24 11:53:09	architecture-building-systems/CEAforArcGIS	https://api.github.com/repos/architecture-building-systems/CEAforArcGIS	reopened	Radiation data missing from reference-case-zug	bug easy peasy Priority 1	Steps to reproduce: 1. Download reference-case-zug from repo 2. run data helper 3. run Demand script with weather=Zug 4. ??? 5. Boom!! ``` Executing: DemandTool C:\reference-case-zug\baseline Zug Start Time: Thu Sep 29 16:28:43 2016 Running script DemandTool... Using python: C:\Python27\ArcGIS10.4\python.exe Path to demand script: C:\Users\darthoma\Documents\GitHub\CEAforArcGIS\cea\demand\demand_main.py Adding path to PYTHONPATH: C:\Users\darthoma\Documents\GitHub\CEAforArcGIS Running demand calculation for scenario C:\reference-case-zug\baseline Running demand calculation with weather file C:\Users\darthoma\Documents\GitHub\CEAforArcGIS\cea\databases\CH\Weather\Zug.epw reading input files Traceback (most recent call last): File "C:\Users\darthoma\Documents\GitHub\CEAforArcGIS\cea\demand\demand_main.py", line 187, in <module> run_as_script(scenario_path=args.scenario, weather_path=args.weather) File "C:\Users\darthoma\Documents\GitHub\CEAforArcGIS\cea\demand\demand_main.py", line 176, in run_as_script demand_calculation(locator=locator, weather_path=weather_path, gv=gv) File "C:\Users\darthoma\Documents\GitHub\CEAforArcGIS\cea\demand\demand_main.py", line 92, in demand_calculation building_properties = BuildingProperties(locator, gv) File "C:\Users\darthoma\Documents\GitHub\CEAforArcGIS\cea\demand\thermal_loads.py", line 849, in __init__ solar = pd.read_csv(locator.get_radiation()).set_index('Name') File "C:\Python27\ArcGIS10.4\lib\site-packages\pandas\io\parsers.py", line 474, in parser_f return _read(filepath_or_buffer, kwds) File "C:\Python27\ArcGIS10.4\lib\site-packages\pandas\io\parsers.py", line 250, in _read parser = TextFileReader(filepath_or_buffer, kwds) File "C:\Python27\ArcGIS10.4\lib\site-packages\pandas\io\parsers.py", line 566, in __init__ self._make_engine(self.engine) File "C:\Python27\ArcGIS10.4\lib\site-packages\pandas\io\parsers.py", line 705, in _make_engine self._engine = CParserWrapper(self.f, self.options) File "C:\Python27\ArcGIS10.4\lib\site-packages\pandas\io\parsers.py", line 1072, in __init__ self._reader = _parser.TextReader(src, **kwds) File "pandas\parser.pyx", line 350, in pandas.parser.TextReader.__cinit__ (pandas\parser.c:3160) File "pandas\parser.pyx", line 594, in pandas.parser.TextReader._setup_parser_source (pandas\parser.c:5905) IOError: File C:\reference-case-zug\baseline\outputs\data\solar-radiation\radiation.csv does not exist Completed script DemandTool... Succeeded at Thu Sep 29 16:28:49 2016 (Elapsed Time: 6.03 seconds) ```	1.0	Radiation data missing from reference-case-zug - Steps to reproduce: 1. Download reference-case-zug from repo 2. run data helper 3. run Demand script with weather=Zug 4. ??? 5. Boom!! ``` Executing: DemandTool C:\reference-case-zug\baseline Zug Start Time: Thu Sep 29 16:28:43 2016 Running script DemandTool... Using python: C:\Python27\ArcGIS10.4\python.exe Path to demand script: C:\Users\darthoma\Documents\GitHub\CEAforArcGIS\cea\demand\demand_main.py Adding path to PYTHONPATH: C:\Users\darthoma\Documents\GitHub\CEAforArcGIS Running demand calculation for scenario C:\reference-case-zug\baseline Running demand calculation with weather file C:\Users\darthoma\Documents\GitHub\CEAforArcGIS\cea\databases\CH\Weather\Zug.epw reading input files Traceback (most recent call last): File "C:\Users\darthoma\Documents\GitHub\CEAforArcGIS\cea\demand\demand_main.py", line 187, in <module> run_as_script(scenario_path=args.scenario, weather_path=args.weather) File "C:\Users\darthoma\Documents\GitHub\CEAforArcGIS\cea\demand\demand_main.py", line 176, in run_as_script demand_calculation(locator=locator, weather_path=weather_path, gv=gv) File "C:\Users\darthoma\Documents\GitHub\CEAforArcGIS\cea\demand\demand_main.py", line 92, in demand_calculation building_properties = BuildingProperties(locator, gv) File "C:\Users\darthoma\Documents\GitHub\CEAforArcGIS\cea\demand\thermal_loads.py", line 849, in __init__ solar = pd.read_csv(locator.get_radiation()).set_index('Name') File "C:\Python27\ArcGIS10.4\lib\site-packages\pandas\io\parsers.py", line 474, in parser_f return _read(filepath_or_buffer, kwds) File "C:\Python27\ArcGIS10.4\lib\site-packages\pandas\io\parsers.py", line 250, in _read parser = TextFileReader(filepath_or_buffer, kwds) File "C:\Python27\ArcGIS10.4\lib\site-packages\pandas\io\parsers.py", line 566, in __init__ self._make_engine(self.engine) File "C:\Python27\ArcGIS10.4\lib\site-packages\pandas\io\parsers.py", line 705, in _make_engine self._engine = CParserWrapper(self.f, self.options) File "C:\Python27\ArcGIS10.4\lib\site-packages\pandas\io\parsers.py", line 1072, in __init__ self._reader = _parser.TextReader(src, **kwds) File "pandas\parser.pyx", line 350, in pandas.parser.TextReader.__cinit__ (pandas\parser.c:3160) File "pandas\parser.pyx", line 594, in pandas.parser.TextReader._setup_parser_source (pandas\parser.c:5905) IOError: File C:\reference-case-zug\baseline\outputs\data\solar-radiation\radiation.csv does not exist Completed script DemandTool... Succeeded at Thu Sep 29 16:28:49 2016 (Elapsed Time: 6.03 seconds) ```	priority	radiation data missing from reference case zug steps to reproduce download reference case zug from repo run data helper run demand script with weather zug boom executing demandtool c reference case zug baseline zug start time thu sep running script demandtool using python c python exe path to demand script c users darthoma documents github ceaforarcgis cea demand demand main py adding path to pythonpath c users darthoma documents github ceaforarcgis running demand calculation for scenario c reference case zug baseline running demand calculation with weather file c users darthoma documents github ceaforarcgis cea databases ch weather zug epw reading input files traceback most recent call last file c users darthoma documents github ceaforarcgis cea demand demand main py line in run as script scenario path args scenario weather path args weather file c users darthoma documents github ceaforarcgis cea demand demand main py line in run as script demand calculation locator locator weather path weather path gv gv file c users darthoma documents github ceaforarcgis cea demand demand main py line in demand calculation building properties buildingproperties locator gv file c users darthoma documents github ceaforarcgis cea demand thermal loads py line in init solar pd read csv locator get radiation set index name file c lib site packages pandas io parsers py line in parser f return read filepath or buffer kwds file c lib site packages pandas io parsers py line in read parser textfilereader filepath or buffer kwds file c lib site packages pandas io parsers py line in init self make engine self engine file c lib site packages pandas io parsers py line in make engine self engine cparserwrapper self f self options file c lib site packages pandas io parsers py line in init self reader parser textreader src kwds file pandas parser pyx line in pandas parser textreader cinit pandas parser c file pandas parser pyx line in pandas parser textreader setup parser source pandas parser c ioerror file c reference case zug baseline outputs data solar radiation radiation csv does not exist completed script demandtool succeeded at thu sep elapsed time seconds	1
251,998	18,984,167,662	IssuesEvent	2021-11-21 12:32:29	nuxt/framework	https://api.github.com/repos/nuxt/framework	closed	Reference to Nuxt command in bridge migration	documentation	This is a bit confusing since just earlier it says to switch from `nuxt generate` to `nuxi generate`: https://github.com/nuxt/framework/blob/b2fd3f9840d308f10454c17115f96c5723bdf408/docs/content/1.getting-started/3.bridge.md?plain=1#L158	1.0	Reference to Nuxt command in bridge migration - This is a bit confusing since just earlier it says to switch from `nuxt generate` to `nuxi generate`: https://github.com/nuxt/framework/blob/b2fd3f9840d308f10454c17115f96c5723bdf408/docs/content/1.getting-started/3.bridge.md?plain=1#L158	non_priority	reference to nuxt command in bridge migration this is a bit confusing since just earlier it says to switch from nuxt generate to nuxi generate	0
339,495	10,255,357,507	IssuesEvent	2019-08-21 15:16:10	craftercms/craftercms	https://api.github.com/repos/craftercms/craftercms	closed	[studio] Studio fails to start after an upgrade from 3.1.0 to develop	bug priority: high	## Describe the bug Studio fails to start after upgrade from 3.1.0 to develop ` Incompatible database detected, unable to start` ## To Reproduce Steps to reproduce the behavior: 1. Download and run a `3.1.0` authoring bundle 2. Create a bundle from `develop` 3. Follow the guide https://docs.craftercms.org/en/3.1/system-administrators/upgrade/index.html#upgrading-crafter-cms-installed-from-a-bundle 4. During the upgrade use the option ` - (A)lways delete the file and and don't ask again for the rest of the upgrade` and ` - (A)lways overwrite files and don't ask again for the rest of the upgrade` 5. Start up authoring ## Expected behavior Authoring starts up successfully. ## Screenshots {{If applicable, add screenshots to help explain your problem.}} ## Logs https://gist.github.com/yacdaniel/6c1bcc4a7ba27b7f1599abe325c269d1 ## Specs ### Version Studio Version Number: 3.1.1-SNAPSHOT-d2a6e6 Build Number: d2a6e6c226aeff2ad39293a4389f408b6d7b9e55 Build Date/Time: 07-29-2019 17:10:05 -0600 ### OS Linux ### Browser {{What browser did you use to produce the bug.}} ## Additional context {{Add any other context about the problem here.}}	1.0	[studio] Studio fails to start after an upgrade from 3.1.0 to develop - ## Describe the bug Studio fails to start after upgrade from 3.1.0 to develop ` Incompatible database detected, unable to start` ## To Reproduce Steps to reproduce the behavior: 1. Download and run a `3.1.0` authoring bundle 2. Create a bundle from `develop` 3. Follow the guide https://docs.craftercms.org/en/3.1/system-administrators/upgrade/index.html#upgrading-crafter-cms-installed-from-a-bundle 4. During the upgrade use the option ` - (A)lways delete the file and and don't ask again for the rest of the upgrade` and ` - (A)lways overwrite files and don't ask again for the rest of the upgrade` 5. Start up authoring ## Expected behavior Authoring starts up successfully. ## Screenshots {{If applicable, add screenshots to help explain your problem.}} ## Logs https://gist.github.com/yacdaniel/6c1bcc4a7ba27b7f1599abe325c269d1 ## Specs ### Version Studio Version Number: 3.1.1-SNAPSHOT-d2a6e6 Build Number: d2a6e6c226aeff2ad39293a4389f408b6d7b9e55 Build Date/Time: 07-29-2019 17:10:05 -0600 ### OS Linux ### Browser {{What browser did you use to produce the bug.}} ## Additional context {{Add any other context about the problem here.}}	priority	studio fails to start after an upgrade from to develop describe the bug studio fails to start after upgrade from to develop incompatible database detected unable to start to reproduce steps to reproduce the behavior download and run a authoring bundle create a bundle from develop follow the guide during the upgrade use the option a lways delete the file and and don t ask again for the rest of the upgrade and a lways overwrite files and don t ask again for the rest of the upgrade start up authoring expected behavior authoring starts up successfully screenshots if applicable add screenshots to help explain your problem logs specs version studio version number snapshot build number build date time os linux browser what browser did you use to produce the bug additional context add any other context about the problem here	1
58,307	6,586,499,117	IssuesEvent	2017-09-13 17:29:46	yarnpkg/yarn	https://api.github.com/repos/yarnpkg/yarn	closed	yarn-homebrew #32 failed	failure test	Build '$JOB_NAME' is failing! Last 50 lines of build output: ``` ${BUILD_LOG, maxLines=50} ``` Changes since last successful build: ${CHANGES_SINCE_LAST_SUCCESS, format="%c", changesFormat="- [%a] %r - %m\n"} [View full output]($BUILD_URL) cc @Daniel15	1.0	yarn-homebrew #32 failed - Build '$JOB_NAME' is failing! Last 50 lines of build output: ``` ${BUILD_LOG, maxLines=50} ``` Changes since last successful build: ${CHANGES_SINCE_LAST_SUCCESS, format="%c", changesFormat="- [%a] %r - %m\n"} [View full output]($BUILD_URL) cc @Daniel15	non_priority	yarn homebrew failed build job name is failing last lines of build output build log maxlines changes since last successful build changes since last success format c changesformat r m n build url cc	0
375,391	11,103,736,492	IssuesEvent	2019-12-17 05:09:48	bounswe/bounswe2019group6	https://api.github.com/repos/bounswe/bounswe2019group6	closed	Separation of "other users profile" with "my profile"	priority:high related:frontend	In our system we can go to the other user's profile and see their portfolios and articles if the user is public or we follow him/her. In the second milestone we didn't implement this functionality, that is why when we enter a user's profile, there was a static text saying that "this user has not article/portfolio". Now we need to implement this functionality. When we enter a user's profile which we follow or already public, we need to see her/his portfolios and articles.	1.0	Separation of "other users profile" with "my profile" - In our system we can go to the other user's profile and see their portfolios and articles if the user is public or we follow him/her. In the second milestone we didn't implement this functionality, that is why when we enter a user's profile, there was a static text saying that "this user has not article/portfolio". Now we need to implement this functionality. When we enter a user's profile which we follow or already public, we need to see her/his portfolios and articles.	priority	separation of other users profile with my profile in our system we can go to the other user s profile and see their portfolios and articles if the user is public or we follow him her in the second milestone we didn t implement this functionality that is why when we enter a user s profile there was a static text saying that this user has not article portfolio now we need to implement this functionality when we enter a user s profile which we follow or already public we need to see her his portfolios and articles	1
53,180	22,648,301,118	IssuesEvent	2022-07-01 10:55:05	microsoft/BotBuilder-Samples	https://api.github.com/repos/microsoft/BotBuilder-Samples	closed	The file was uploaded successfully but the card indicates failure.	bug customer-reported Bot Services needs-triage	### Github issues for [C#](https://github.com/Microsoft/botbuilder-dotnet/issues) /[JS](https://github.com/Microsoft/botbuilder-js/issues) / [Java](https://github.com/Microsoft/botbuilder-java/issues)/ [Python](https://github.com/Microsoft/botbuilder-python/issues) should be used for bugs and feature requests. Use [Stack Overflow](https://stackoverflow.com/questions/tagged/botframework) for general "how-to" questions. ## Sample information [BotBuilder-Samples](https://github.com/microsoft/BotBuilder-Samples)/[samples](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples)/[csharp_dotnetcore](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore)/[56.teams-file-upload](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore/56.teams-file-upload) ## Describe the bug Give a clear and concise description of what the bug is. ## To Reproduce Steps to reproduce the behavior: 1. Deploy the sample in Azure 2. Try to use it ## Expected behavior The file was uploaded successfully but the card indicates failure. Normal circumstances should not prompt an error. ## Screenshots ![074a2870e06007dc46d5972c3b454ae](https://user-images.githubusercontent.com/41287016/176634226-37a31a9f-142f-47a9-a258-4a2e6732bf55.png)	1.0	The file was uploaded successfully but the card indicates failure. - ### Github issues for [C#](https://github.com/Microsoft/botbuilder-dotnet/issues) /[JS](https://github.com/Microsoft/botbuilder-js/issues) / [Java](https://github.com/Microsoft/botbuilder-java/issues)/ [Python](https://github.com/Microsoft/botbuilder-python/issues) should be used for bugs and feature requests. Use [Stack Overflow](https://stackoverflow.com/questions/tagged/botframework) for general "how-to" questions. ## Sample information [BotBuilder-Samples](https://github.com/microsoft/BotBuilder-Samples)/[samples](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples)/[csharp_dotnetcore](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore)/[56.teams-file-upload](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore/56.teams-file-upload) ## Describe the bug Give a clear and concise description of what the bug is. ## To Reproduce Steps to reproduce the behavior: 1. Deploy the sample in Azure 2. Try to use it ## Expected behavior The file was uploaded successfully but the card indicates failure. Normal circumstances should not prompt an error. ## Screenshots ![074a2870e06007dc46d5972c3b454ae](https://user-images.githubusercontent.com/41287016/176634226-37a31a9f-142f-47a9-a258-4a2e6732bf55.png)	non_priority	the file was uploaded successfully but the card indicates failure github issues for should be used for bugs and feature requests use for general how to questions sample information describe the bug give a clear and concise description of what the bug is to reproduce steps to reproduce the behavior deploy the sample in azure try to use it expected behavior the file was uploaded successfully but the card indicates failure normal circumstances should not prompt an error screenshots	0
272,062	29,794,977,567	IssuesEvent	2023-06-16 01:01:25	billmcchesney1/singleton	https://api.github.com/repos/billmcchesney1/singleton	closed	CVE-2022-22950 (Medium) detected in spring-expression-5.2.9.RELEASE.jar - autoclosed	Mend: dependency security vulnerability	## CVE-2022-22950 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-expression-5.2.9.RELEASE.jar</b></p></summary> <p>Spring Expression Language (SpEL)</p> <p>Path to dependency file: /g11n-ws/modules/md-data-initdb/build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-expression/5.2.9.RELEASE/c8584de306be115ef1715b7ed9d50fb2802867aa/spring-expression-5.2.9.RELEASE.jar</p> <p> Dependency Hierarchy: - md-restful-api-i18n-1.0 (Root Library) - springfox-swagger2-2.9.2.jar - spring-plugin-core-1.2.0.RELEASE.jar - spring-context-5.2.9.RELEASE.jar - :x: spring-expression-5.2.9.RELEASE.jar (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/billmcchesney1/singleton/commit/2bb883ae0b199f3e432621e91d0f801cfc406a89">2bb883ae0b199f3e432621e91d0f801cfc406a89</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> n Spring Framework versions 5.3.0 - 5.3.16 and older unsupported versions, it is possible for a user to provide a specially crafted SpEL expression that may cause a denial of service condition. <p>Publish Date: 2022-04-01 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22950>CVE-2022-22950</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>6.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://tanzu.vmware.com/security/cve-2022-22950">https://tanzu.vmware.com/security/cve-2022-22950</a></p> <p>Release Date: 2022-04-01</p> <p>Fix Resolution: org.springframework:spring-expression:5.2.20,5.3.17</p> </p> </details> <p></p>	True	CVE-2022-22950 (Medium) detected in spring-expression-5.2.9.RELEASE.jar - autoclosed - ## CVE-2022-22950 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-expression-5.2.9.RELEASE.jar</b></p></summary> <p>Spring Expression Language (SpEL)</p> <p>Path to dependency file: /g11n-ws/modules/md-data-initdb/build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-expression/5.2.9.RELEASE/c8584de306be115ef1715b7ed9d50fb2802867aa/spring-expression-5.2.9.RELEASE.jar</p> <p> Dependency Hierarchy: - md-restful-api-i18n-1.0 (Root Library) - springfox-swagger2-2.9.2.jar - spring-plugin-core-1.2.0.RELEASE.jar - spring-context-5.2.9.RELEASE.jar - :x: spring-expression-5.2.9.RELEASE.jar (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/billmcchesney1/singleton/commit/2bb883ae0b199f3e432621e91d0f801cfc406a89">2bb883ae0b199f3e432621e91d0f801cfc406a89</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> n Spring Framework versions 5.3.0 - 5.3.16 and older unsupported versions, it is possible for a user to provide a specially crafted SpEL expression that may cause a denial of service condition. <p>Publish Date: 2022-04-01 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22950>CVE-2022-22950</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>6.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://tanzu.vmware.com/security/cve-2022-22950">https://tanzu.vmware.com/security/cve-2022-22950</a></p> <p>Release Date: 2022-04-01</p> <p>Fix Resolution: org.springframework:spring-expression:5.2.20,5.3.17</p> </p> </details> <p></p>	non_priority	cve medium detected in spring expression release jar autoclosed cve medium severity vulnerability vulnerable library spring expression release jar spring expression language spel path to dependency file ws modules md data initdb build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring expression release spring expression release jar dependency hierarchy md restful api root library springfox jar spring plugin core release jar spring context release jar x spring expression release jar vulnerable library found in head commit a href found in base branch master vulnerability details n spring framework versions and older unsupported versions it is possible for a user to provide a specially crafted spel expression that may cause a denial of service condition publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org springframework spring expression	0
792,306	27,954,338,019	IssuesEvent	2023-03-24 11:12:15	Gilded-Games/The-Aether	https://api.github.com/repos/Gilded-Games/The-Aether	closed	Bug: Shift-clicking a curio that is already equipped moves it to the destroy item slot	priority/medium type/bug feat/gui	How to reproduce: 1. Equip a pair of gloves 2. Attempt to shift-click another pair of gloves into the slot	1.0	Bug: Shift-clicking a curio that is already equipped moves it to the destroy item slot - How to reproduce: 1. Equip a pair of gloves 2. Attempt to shift-click another pair of gloves into the slot	priority	bug shift clicking a curio that is already equipped moves it to the destroy item slot how to reproduce equip a pair of gloves attempt to shift click another pair of gloves into the slot	1
532,586	15,559,796,047	IssuesEvent	2021-03-16 11:57:29	googleapis/google-cloud-dotnet	https://api.github.com/repos/googleapis/google-cloud-dotnet	closed	Synthesis failed for Google.Cloud.Billing.Budgets.V1Beta1	autosynth failure priority: p1 type: bug	Hello! Autosynth couldn't regenerate Google.Cloud.Billing.Budgets.V1Beta1. :broken_heart: Please investigate and fix this issue within 5 business days. While it remains broken, this library cannot be updated with changes to the Google.Cloud.Billing.Budgets.V1Beta1 API, and the library grows stale. See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md for trouble shooting tips. Here's the output from running `synth.py`: ``` 89d6b6d394f2c5a15e77112ee42c391033bd5f 2021-03-15 22:43:04,929 autosynth [DEBUG] > Running: git log -1 --pretty=%at 5477122b3e8037a1dc5bc920536158edbd151dc4 2021-03-15 22:43:04,932 autosynth [DEBUG] > Running: git log -1 --pretty=%at 458338f8ca444e43b9df96b984b68f3978852b74 2021-03-15 22:43:04,935 autosynth [DEBUG] > Running: git log -1 --pretty=%at 0e915217fb5261c1e57bfaf0e16ee5c7feaaba89 2021-03-15 22:43:04,938 autosynth [DEBUG] > Running: git log -1 --pretty=%at 65d71a60baf9650404a4d9d65f29e9ba8db490d1 2021-03-15 22:43:04,941 autosynth [DEBUG] > Running: git log -1 --pretty=%at 8e71120af081ab9402669df1f290beeae9629e16 2021-03-15 22:43:04,944 autosynth [DEBUG] > Running: git log -1 --pretty=%at 63a8c9c9f5fc9edf4f7c1a048151f73933f5a080 2021-03-15 22:43:04,947 autosynth [DEBUG] > Running: git log -1 --pretty=%at 0c6dd7aa98ebee634ec62568237f7ee17034ad08 2021-03-15 22:43:04,950 autosynth [DEBUG] > Running: git log -1 --pretty=%at d060a12e9731b05fccb56aee4d4bf176892b7911 2021-03-15 22:43:04,953 autosynth [DEBUG] > Running: git log -1 --pretty=%at 28a591963253d52ce3a25a918cafbdd9928de8cf 2021-03-15 22:43:04,957 autosynth [DEBUG] > Running: git log -1 --pretty=%at 3aeb3a70f66457a9e6b07caff841719bb9873b57 2021-03-15 22:43:04,960 autosynth [DEBUG] > Running: git log -1 --pretty=%at cd6119f83636cf9c0d2bee86db7456dc49c56c47 2021-03-15 22:43:04,963 autosynth [DEBUG] > Running: git log -1 --pretty=%at 32c7223450155807fbad64de1a7a5eded95cfec0 2021-03-15 22:43:04,967 autosynth [DEBUG] > Running: git log -1 --pretty=%at 68fdb1b7dc47ff7a3bda6b7744f5e01887b94d3b 2021-03-15 22:43:04,970 autosynth [DEBUG] > Running: git log -1 --pretty=%at 4b16c60a8fffe213d3a5002f85696fef2b6a8172 2021-03-15 22:43:04,973 autosynth [DEBUG] > Running: git log -1 --pretty=%at 3efec25aa7e225dac913be6d759cacfe7898fa8c 2021-03-15 22:43:04,976 autosynth [DEBUG] > Running: git log -1 --pretty=%at d652c6370bf66e325da6ac9ad82989fe7ee7bb4b 2021-03-15 22:43:04,979 autosynth [DEBUG] > Running: git log -1 --pretty=%at b6ebac16c3aecb798d4f25443d96df2f42a965ca 2021-03-15 22:43:04,983 autosynth [DEBUG] > Running: git log -1 --pretty=%at 3e9b231b098d514c9a51ba8c59e416f45837b195 2021-03-15 22:43:04,986 autosynth [DEBUG] > Running: git log -1 --pretty=%at d7559898a37485bf9de44a6e2d22d66d1bad2eb0 2021-03-15 22:43:04,988 autosynth [DEBUG] > Running: git log -1 --pretty=%at 4112ccbe6566f63d5b1008ca52eee54cc2896aa9 2021-03-15 22:43:04,992 autosynth [DEBUG] > Running: git log -1 --pretty=%at a0d282daa691e95ec51131c81c3777fc95abf7f8 2021-03-15 22:43:04,995 autosynth [DEBUG] > Running: git log -1 --pretty=%at 1305ca41d554eb0725237561e34129373bb8cbc1 2021-03-15 22:43:04,998 autosynth [DEBUG] > Running: git log -1 --pretty=%at 81e30251959461b6220ed3121747e86d7b17bb5a 2021-03-15 22:43:05,001 autosynth [DEBUG] > Running: git log -1 --pretty=%at 72326861be446be27d53af95c87e6e313367c371 2021-03-15 22:43:05,004 autosynth [DEBUG] > Running: git log -1 --pretty=%at cb631dd3ffe0d6f77f7b01c5168e357771c74b51 2021-03-15 22:43:05,008 autosynth [DEBUG] > Running: git log -1 --pretty=%at a1ba4568e228b25124f9a6689cfe3bcab75498a6 2021-03-15 22:43:05,011 autosynth [DEBUG] > Running: git log -1 --pretty=%at 0dafa3963ef6fcb8a7f5daaa4bec12adb04de518 2021-03-15 22:43:05,014 autosynth [DEBUG] > Running: git log -1 --pretty=%at a4ee234c9499483cc966669669e7900b3b781192 2021-03-15 22:43:05,017 autosynth [DEBUG] > Running: git log -1 --pretty=%at e1654206ff59f3a2a226828f9c9f354c253b36e4 2021-03-15 22:43:05,021 autosynth [DEBUG] > Running: git checkout 1b5aa430660e3309246f48476f70efe6905046c9 Note: checking out '1b5aa430660e3309246f48476f70efe6905046c9'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at 1b5aa4306 chore: remove obsolete configuration file 2021-03-15 22:43:05,041 autosynth [DEBUG] > Running: git checkout e1654206ff59f3a2a226828f9c9f354c253b36e4 Note: checking out 'e1654206ff59f3a2a226828f9c9f354c253b36e4'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at e1654206 chore: Use correct markdown for code block 2021-03-15 22:43:05,056 autosynth [DEBUG] > Running: git branch -f autosynth-Google.Cloud.Billing.Budgets.V1Beta1-122 2021-03-15 22:43:05,060 autosynth [DEBUG] > Running: git checkout autosynth-Google.Cloud.Billing.Budgets.V1Beta1-122 Switched to branch 'autosynth-Google.Cloud.Billing.Budgets.V1Beta1-122' 2021-03-15 22:43:05,080 autosynth [INFO] > Running synthtool 2021-03-15 22:43:05,080 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--'] 2021-03-15 22:43:05,080 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/Google.Cloud.Billing.Budgets.V1Beta1/122/sponge_log.log 2021-03-15 22:43:05,083 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata synth.metadata synth.py -- 2021-03-15 22:43:05,331 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/google-cloud-dotnet/apis/Google.Cloud.Billing.Budgets.V1Beta1/synth.py. On branch autosynth-Google.Cloud.Billing.Budgets.V1Beta1-122 nothing to commit, working tree clean Skipping microgenerator fetch/build: already built, and running on Kokoro Building existing version of Google.Cloud.Billing.Budgets.V1Beta1 for compatibility checking Generating Google.Cloud.Billing.Budgets.V1Beta1 Stack overflow. --gapic_out: protoc-gen-gapic: Plugin killed by signal 6. rm: missing operand Try 'rm --help' for more information. 2021-03-15 22:43:10,271 synthtool [ERROR] > Failed executing /bin/bash generateapis.sh --check_compatibility Google.Cloud.Billing.Budgets.V1Beta1: None Traceback (most recent call last): File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module> main() File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__ return self.main(args, kwargs) File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main rv = self.invoke(ctx) File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke return ctx.invoke(self.callback, ctx.params) File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke return callback(args, **kwargs) File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main spec.loader.exec_module(synth_module) # type: ignore File "<frozen importlib._bootstrap_external>", line 678, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/home/kbuilder/.cache/synthtool/google-cloud-dotnet/apis/Google.Cloud.Billing.Budgets.V1Beta1/synth.py", line 26, in <module> hide_output = False) File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run raise exc File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run encoding="utf-8", File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '('/bin/bash', 'generateapis.sh', '--check_compatibility', 'Google.Cloud.Billing.Budgets.V1Beta1')' returned non-zero exit status 1. 2021-03-15 22:43:10,296 autosynth [ERROR] > Synthesis failed 2021-03-15 22:43:10,296 autosynth [DEBUG] > Running: git reset --hard HEAD HEAD is now at 1b5aa4306 chore: remove obsolete configuration file 2021-03-15 22:43:10,327 autosynth [DEBUG] > Running: git checkout autosynth-Google.Cloud.Billing.Budgets.V1Beta1 Switched to branch 'autosynth-Google.Cloud.Billing.Budgets.V1Beta1' Traceback (most recent call last): File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module> main() File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main return _inner_main(temp_dir) File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 334, in _inner_main commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer) File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 65, in synthesize_loop has_changes = toolbox.synthesize_version_in_new_branch(synthesizer, youngest) File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 259, in synthesize_version_in_new_branch synthesizer.synthesize(synth_log_path, self.environ) File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize synth_proc.check_returncode() # Raise an exception. File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode self.stderr) subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1. ``` Google internal developers can see the full log [here](http://sponge2/results/invocations/f1b7e0c2-a734-4c4b-ab01-5a91847bad42/targets/github%2Fsynthtool;config=default/tests;query=google-cloud-dotnet;failed=false).	1.0	Synthesis failed for Google.Cloud.Billing.Budgets.V1Beta1 - Hello! Autosynth couldn't regenerate Google.Cloud.Billing.Budgets.V1Beta1. :broken_heart: Please investigate and fix this issue within 5 business days. While it remains broken, this library cannot be updated with changes to the Google.Cloud.Billing.Budgets.V1Beta1 API, and the library grows stale. See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md for trouble shooting tips. Here's the output from running `synth.py`: ``` 89d6b6d394f2c5a15e77112ee42c391033bd5f 2021-03-15 22:43:04,929 autosynth [DEBUG] > Running: git log -1 --pretty=%at 5477122b3e8037a1dc5bc920536158edbd151dc4 2021-03-15 22:43:04,932 autosynth [DEBUG] > Running: git log -1 --pretty=%at 458338f8ca444e43b9df96b984b68f3978852b74 2021-03-15 22:43:04,935 autosynth [DEBUG] > Running: git log -1 --pretty=%at 0e915217fb5261c1e57bfaf0e16ee5c7feaaba89 2021-03-15 22:43:04,938 autosynth [DEBUG] > Running: git log -1 --pretty=%at 65d71a60baf9650404a4d9d65f29e9ba8db490d1 2021-03-15 22:43:04,941 autosynth [DEBUG] > Running: git log -1 --pretty=%at 8e71120af081ab9402669df1f290beeae9629e16 2021-03-15 22:43:04,944 autosynth [DEBUG] > Running: git log -1 --pretty=%at 63a8c9c9f5fc9edf4f7c1a048151f73933f5a080 2021-03-15 22:43:04,947 autosynth [DEBUG] > Running: git log -1 --pretty=%at 0c6dd7aa98ebee634ec62568237f7ee17034ad08 2021-03-15 22:43:04,950 autosynth [DEBUG] > Running: git log -1 --pretty=%at d060a12e9731b05fccb56aee4d4bf176892b7911 2021-03-15 22:43:04,953 autosynth [DEBUG] > Running: git log -1 --pretty=%at 28a591963253d52ce3a25a918cafbdd9928de8cf 2021-03-15 22:43:04,957 autosynth [DEBUG] > Running: git log -1 --pretty=%at 3aeb3a70f66457a9e6b07caff841719bb9873b57 2021-03-15 22:43:04,960 autosynth [DEBUG] > Running: git log -1 --pretty=%at cd6119f83636cf9c0d2bee86db7456dc49c56c47 2021-03-15 22:43:04,963 autosynth [DEBUG] > Running: git log -1 --pretty=%at 32c7223450155807fbad64de1a7a5eded95cfec0 2021-03-15 22:43:04,967 autosynth [DEBUG] > Running: git log -1 --pretty=%at 68fdb1b7dc47ff7a3bda6b7744f5e01887b94d3b 2021-03-15 22:43:04,970 autosynth [DEBUG] > Running: git log -1 --pretty=%at 4b16c60a8fffe213d3a5002f85696fef2b6a8172 2021-03-15 22:43:04,973 autosynth [DEBUG] > Running: git log -1 --pretty=%at 3efec25aa7e225dac913be6d759cacfe7898fa8c 2021-03-15 22:43:04,976 autosynth [DEBUG] > Running: git log -1 --pretty=%at d652c6370bf66e325da6ac9ad82989fe7ee7bb4b 2021-03-15 22:43:04,979 autosynth [DEBUG] > Running: git log -1 --pretty=%at b6ebac16c3aecb798d4f25443d96df2f42a965ca 2021-03-15 22:43:04,983 autosynth [DEBUG] > Running: git log -1 --pretty=%at 3e9b231b098d514c9a51ba8c59e416f45837b195 2021-03-15 22:43:04,986 autosynth [DEBUG] > Running: git log -1 --pretty=%at d7559898a37485bf9de44a6e2d22d66d1bad2eb0 2021-03-15 22:43:04,988 autosynth [DEBUG] > Running: git log -1 --pretty=%at 4112ccbe6566f63d5b1008ca52eee54cc2896aa9 2021-03-15 22:43:04,992 autosynth [DEBUG] > Running: git log -1 --pretty=%at a0d282daa691e95ec51131c81c3777fc95abf7f8 2021-03-15 22:43:04,995 autosynth [DEBUG] > Running: git log -1 --pretty=%at 1305ca41d554eb0725237561e34129373bb8cbc1 2021-03-15 22:43:04,998 autosynth [DEBUG] > Running: git log -1 --pretty=%at 81e30251959461b6220ed3121747e86d7b17bb5a 2021-03-15 22:43:05,001 autosynth [DEBUG] > Running: git log -1 --pretty=%at 72326861be446be27d53af95c87e6e313367c371 2021-03-15 22:43:05,004 autosynth [DEBUG] > Running: git log -1 --pretty=%at cb631dd3ffe0d6f77f7b01c5168e357771c74b51 2021-03-15 22:43:05,008 autosynth [DEBUG] > Running: git log -1 --pretty=%at a1ba4568e228b25124f9a6689cfe3bcab75498a6 2021-03-15 22:43:05,011 autosynth [DEBUG] > Running: git log -1 --pretty=%at 0dafa3963ef6fcb8a7f5daaa4bec12adb04de518 2021-03-15 22:43:05,014 autosynth [DEBUG] > Running: git log -1 --pretty=%at a4ee234c9499483cc966669669e7900b3b781192 2021-03-15 22:43:05,017 autosynth [DEBUG] > Running: git log -1 --pretty=%at e1654206ff59f3a2a226828f9c9f354c253b36e4 2021-03-15 22:43:05,021 autosynth [DEBUG] > Running: git checkout 1b5aa430660e3309246f48476f70efe6905046c9 Note: checking out '1b5aa430660e3309246f48476f70efe6905046c9'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at 1b5aa4306 chore: remove obsolete configuration file 2021-03-15 22:43:05,041 autosynth [DEBUG] > Running: git checkout e1654206ff59f3a2a226828f9c9f354c253b36e4 Note: checking out 'e1654206ff59f3a2a226828f9c9f354c253b36e4'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at e1654206 chore: Use correct markdown for code block 2021-03-15 22:43:05,056 autosynth [DEBUG] > Running: git branch -f autosynth-Google.Cloud.Billing.Budgets.V1Beta1-122 2021-03-15 22:43:05,060 autosynth [DEBUG] > Running: git checkout autosynth-Google.Cloud.Billing.Budgets.V1Beta1-122 Switched to branch 'autosynth-Google.Cloud.Billing.Budgets.V1Beta1-122' 2021-03-15 22:43:05,080 autosynth [INFO] > Running synthtool 2021-03-15 22:43:05,080 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--'] 2021-03-15 22:43:05,080 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/Google.Cloud.Billing.Budgets.V1Beta1/122/sponge_log.log 2021-03-15 22:43:05,083 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata synth.metadata synth.py -- 2021-03-15 22:43:05,331 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/google-cloud-dotnet/apis/Google.Cloud.Billing.Budgets.V1Beta1/synth.py. On branch autosynth-Google.Cloud.Billing.Budgets.V1Beta1-122 nothing to commit, working tree clean Skipping microgenerator fetch/build: already built, and running on Kokoro Building existing version of Google.Cloud.Billing.Budgets.V1Beta1 for compatibility checking Generating Google.Cloud.Billing.Budgets.V1Beta1 Stack overflow. --gapic_out: protoc-gen-gapic: Plugin killed by signal 6. rm: missing operand Try 'rm --help' for more information. 2021-03-15 22:43:10,271 synthtool [ERROR] > Failed executing /bin/bash generateapis.sh --check_compatibility Google.Cloud.Billing.Budgets.V1Beta1: None Traceback (most recent call last): File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module> main() File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__ return self.main(args, kwargs) File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main rv = self.invoke(ctx) File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke return ctx.invoke(self.callback, ctx.params) File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke return callback(args, **kwargs) File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main spec.loader.exec_module(synth_module) # type: ignore File "<frozen importlib._bootstrap_external>", line 678, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/home/kbuilder/.cache/synthtool/google-cloud-dotnet/apis/Google.Cloud.Billing.Budgets.V1Beta1/synth.py", line 26, in <module> hide_output = False) File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run raise exc File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run encoding="utf-8", File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '('/bin/bash', 'generateapis.sh', '--check_compatibility', 'Google.Cloud.Billing.Budgets.V1Beta1')' returned non-zero exit status 1. 2021-03-15 22:43:10,296 autosynth [ERROR] > Synthesis failed 2021-03-15 22:43:10,296 autosynth [DEBUG] > Running: git reset --hard HEAD HEAD is now at 1b5aa4306 chore: remove obsolete configuration file 2021-03-15 22:43:10,327 autosynth [DEBUG] > Running: git checkout autosynth-Google.Cloud.Billing.Budgets.V1Beta1 Switched to branch 'autosynth-Google.Cloud.Billing.Budgets.V1Beta1' Traceback (most recent call last): File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module> main() File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main return _inner_main(temp_dir) File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 334, in _inner_main commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer) File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 65, in synthesize_loop has_changes = toolbox.synthesize_version_in_new_branch(synthesizer, youngest) File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 259, in synthesize_version_in_new_branch synthesizer.synthesize(synth_log_path, self.environ) File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize synth_proc.check_returncode() # Raise an exception. File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode self.stderr) subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1. ``` Google internal developers can see the full log [here](http://sponge2/results/invocations/f1b7e0c2-a734-4c4b-ab01-5a91847bad42/targets/github%2Fsynthtool;config=default/tests;query=google-cloud-dotnet;failed=false).	priority	synthesis failed for google cloud billing budgets hello autosynth couldn t regenerate google cloud billing budgets broken heart please investigate and fix this issue within business days while it remains broken this library cannot be updated with changes to the google cloud billing budgets api and the library grows stale see for trouble shooting tips here s the output from running synth py autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git log pretty at autosynth running git checkout note checking out you are in detached head state you can look around make experimental changes and commit them and you can discard any commits you make in this state without impacting any branches by performing another checkout if you want to create a new branch to retain commits you create you may do so now or later by using b with the checkout command again example git checkout b head is now at chore remove obsolete configuration file autosynth running git checkout note checking out you are in detached head state you can look around make experimental changes and commit them and you can discard any commits you make in this state without impacting any branches by performing another checkout if you want to create a new branch to retain commits you create you may do so now or later by using b with the checkout command again example git checkout b head is now at chore use correct markdown for code block autosynth running git branch f autosynth google cloud billing budgets autosynth running git checkout autosynth google cloud billing budgets switched to branch autosynth google cloud billing budgets autosynth running synthtool autosynth autosynth log file path tmpfs src logs google cloud billing budgets sponge log log autosynth running tmpfs src github synthtool env bin m synthtool metadata synth metadata synth py synthtool executing home kbuilder cache synthtool google cloud dotnet apis google cloud billing budgets synth py on branch autosynth google cloud billing budgets nothing to commit working tree clean skipping microgenerator fetch build already built and running on kokoro building existing version of google cloud billing budgets for compatibility checking generating google cloud billing budgets stack overflow gapic out protoc gen gapic plugin killed by signal rm missing operand try rm help for more information synthtool failed executing bin bash generateapis sh check compatibility google cloud billing budgets none traceback most recent call last file home kbuilder pyenv versions lib runpy py line in run module as main main mod spec file home kbuilder pyenv versions lib runpy py line in run code exec code run globals file tmpfs src github synthtool synthtool main py line in main file tmpfs src github synthtool env lib site packages click core py line in call return self main args kwargs file tmpfs src github synthtool env lib site packages click core py line in main rv self invoke ctx file tmpfs src github synthtool env lib site packages click core py line in invoke return ctx invoke self callback ctx params file tmpfs src github synthtool env lib site packages click core py line in invoke return callback args kwargs file tmpfs src github synthtool synthtool main py line in main spec loader exec module synth module type ignore file line in exec module file line in call with frames removed file home kbuilder cache synthtool google cloud dotnet apis google cloud billing budgets synth py line in hide output false file tmpfs src github synthtool synthtool shell py line in run raise exc file tmpfs src github synthtool synthtool shell py line in run encoding utf file home kbuilder pyenv versions lib subprocess py line in run output stdout stderr stderr subprocess calledprocesserror command bin bash generateapis sh check compatibility google cloud billing budgets returned non zero exit status autosynth synthesis failed autosynth running git reset hard head head is now at chore remove obsolete configuration file autosynth running git checkout autosynth google cloud billing budgets switched to branch autosynth google cloud billing budgets traceback most recent call last file home kbuilder pyenv versions lib runpy py line in run module as main main mod spec file home kbuilder pyenv versions lib runpy py line in run code exec code run globals file tmpfs src github synthtool autosynth synth py line in main file tmpfs src github synthtool autosynth synth py line in main return inner main temp dir file tmpfs src github synthtool autosynth synth py line in inner main commit count synthesize loop x multiple prs change pusher synthesizer file tmpfs src github synthtool autosynth synth py line in synthesize loop has changes toolbox synthesize version in new branch synthesizer youngest file tmpfs src github synthtool autosynth synth toolbox py line in synthesize version in new branch synthesizer synthesize synth log path self environ file tmpfs src github synthtool autosynth synthesizer py line in synthesize synth proc check returncode raise an exception file home kbuilder pyenv versions lib subprocess py line in check returncode self stderr subprocess calledprocesserror command returned non zero exit status google internal developers can see the full log	1
807,932	30,026,143,474	IssuesEvent	2023-06-27 06:17:31	longhorn/longhorn	https://api.github.com/repos/longhorn/longhorn	closed	[BUG] Volume attachment related error logs in uninstaller pod	kind/bug area/install-uninstall-upgrade priority/0 severity/2	## Describe the bug (🐛 if you encounter this issue) A clear and concise description of what the bug is. ## To Reproduce Steps to reproduce the behavior: 1. Install Longhorn 1.5.0-rc2 2. Create a volume and attach it. 3. Set deletion confirmation flag: `kubectl -n longhorn-system patch -p '{"value": "true"}' --type=merge lhs deleting-confirmation-flag` 4. Uninstall Longhorn using [kubectl command](https://raw.githubusercontent.com/longhorn/longhorn/v1.5.0-rc3/uninstall/uninstall.yaml) 5. Check the uninstaller pod logs, they have error like below ``` W0626 20:39:03.417023 1 reflector.go:533] github.com/longhorn/longhorn-manager/k8s/pkg/client/informers/externalversions/factory.go:117: failed to list v1beta2.VolumeAttachment: volumeattachments.longhorn.io is forbidden: User "system:serviceaccount:longhorn-system:longhorn-uninstall-service-account" cannot list resource "volumeattachments" in API group "longhorn.io" at the cluster scope E0626 20:39:03.417071 1 reflector.go:148] github.com/longhorn/longhorn-manager/k8s/pkg/client/informers/externalversions/factory.go:117: Failed to watch v1beta2.VolumeAttachment: failed to list *v1beta2.VolumeAttachment: volumeattachments.longhorn.io is forbidden: User "system:serviceaccount:longhorn-system:longhorn-uninstall-service-account" cannot list resource "volumeattachments" in API group "longhorn.io" at the cluster scope ``` ## Expected behavior Uninstaller should have problem in getting/reading the volumeAttachment ## Log or Support bundle [uninstall.log](https://github.com/longhorn/longhorn/files/11874014/uninstall.log) ## Environment - Longhorn version: 1.5.0-rc2 - Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl	1.0	[BUG] Volume attachment related error logs in uninstaller pod - ## Describe the bug (🐛 if you encounter this issue) A clear and concise description of what the bug is. ## To Reproduce Steps to reproduce the behavior: 1. Install Longhorn 1.5.0-rc2 2. Create a volume and attach it. 3. Set deletion confirmation flag: `kubectl -n longhorn-system patch -p '{"value": "true"}' --type=merge lhs deleting-confirmation-flag` 4. Uninstall Longhorn using [kubectl command](https://raw.githubusercontent.com/longhorn/longhorn/v1.5.0-rc3/uninstall/uninstall.yaml) 5. Check the uninstaller pod logs, they have error like below ``` W0626 20:39:03.417023 1 reflector.go:533] github.com/longhorn/longhorn-manager/k8s/pkg/client/informers/externalversions/factory.go:117: failed to list v1beta2.VolumeAttachment: volumeattachments.longhorn.io is forbidden: User "system:serviceaccount:longhorn-system:longhorn-uninstall-service-account" cannot list resource "volumeattachments" in API group "longhorn.io" at the cluster scope E0626 20:39:03.417071 1 reflector.go:148] github.com/longhorn/longhorn-manager/k8s/pkg/client/informers/externalversions/factory.go:117: Failed to watch v1beta2.VolumeAttachment: failed to list *v1beta2.VolumeAttachment: volumeattachments.longhorn.io is forbidden: User "system:serviceaccount:longhorn-system:longhorn-uninstall-service-account" cannot list resource "volumeattachments" in API group "longhorn.io" at the cluster scope ``` ## Expected behavior Uninstaller should have problem in getting/reading the volumeAttachment ## Log or Support bundle [uninstall.log](https://github.com/longhorn/longhorn/files/11874014/uninstall.log) ## Environment - Longhorn version: 1.5.0-rc2 - Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl	priority	volume attachment related error logs in uninstaller pod describe the bug 🐛 if you encounter this issue a clear and concise description of what the bug is to reproduce steps to reproduce the behavior install longhorn create a volume and attach it set deletion confirmation flag kubectl n longhorn system patch p value true type merge lhs deleting confirmation flag uninstall longhorn using check the uninstaller pod logs they have error like below reflector go github com longhorn longhorn manager pkg client informers externalversions factory go failed to list volumeattachment volumeattachments longhorn io is forbidden user system serviceaccount longhorn system longhorn uninstall service account cannot list resource volumeattachments in api group longhorn io at the cluster scope reflector go github com longhorn longhorn manager pkg client informers externalversions factory go failed to watch volumeattachment failed to list volumeattachment volumeattachments longhorn io is forbidden user system serviceaccount longhorn system longhorn uninstall service account cannot list resource volumeattachments in api group longhorn io at the cluster scope expected behavior uninstaller should have problem in getting reading the volumeattachment log or support bundle environment longhorn version installation method e g rancher catalog app helm kubectl kubectl	1
153,046	12,133,051,843	IssuesEvent	2020-04-23 08:23:15	IntellectualSites/FastAsyncWorldEdit	https://api.github.com/repos/IntellectualSites/FastAsyncWorldEdit	opened	0 Blocks Affected	Requires Testing	# Bug report for FastAsyncWorldEdit 1.15.2 <!--- If you are using 1.13 or 1.14 consider updating to 1.15.2 before raising an issue --> <!--- The priority lays on 1.15 right now, so issues reported for 1.13 or 1.14 will be fixed for the 1.15 versions --> <!--- In order to create a valid issue report you have to follow this template. --> <!--- Remove this template if making a suggestion or asking a question. --> <!--- Incomplete reports will most likely be marked as invalid, and closed, with few exceptions.--> Link to info, plugins, config [./fawe report] [Info] (https://athion.net/ISPaster/paste/view/7a3ac301ad384d50b95bd1567fd5401f) Its not that important, but when i do whatever operation, it says 0 blocks affected or -1 blocks affected Checklist: <!--- Make sure you've completed the following steps (put an "X" between of brackets): --> - [X] I included all information required in the sections above - [X] I made sure there are no duplicates of this report [(Use Search)](https://github.com/IntellectualSites/FastAsyncWorldEdit/issues?q=is%3Aissue) - [X] I made sure I am using an up-to-date version of [FastAsyncWorldEdit for 1.15.2](https://ci.athion.net/job/FastAsyncWorldEdit-1.15/) - [X] I made sure the bug/error is not caused by any other plugin	1.0	0 Blocks Affected - # Bug report for FastAsyncWorldEdit 1.15.2 <!--- If you are using 1.13 or 1.14 consider updating to 1.15.2 before raising an issue --> <!--- The priority lays on 1.15 right now, so issues reported for 1.13 or 1.14 will be fixed for the 1.15 versions --> <!--- In order to create a valid issue report you have to follow this template. --> <!--- Remove this template if making a suggestion or asking a question. --> <!--- Incomplete reports will most likely be marked as invalid, and closed, with few exceptions.--> Link to info, plugins, config [./fawe report] [Info] (https://athion.net/ISPaster/paste/view/7a3ac301ad384d50b95bd1567fd5401f) Its not that important, but when i do whatever operation, it says 0 blocks affected or -1 blocks affected Checklist: <!--- Make sure you've completed the following steps (put an "X" between of brackets): --> - [X] I included all information required in the sections above - [X] I made sure there are no duplicates of this report [(Use Search)](https://github.com/IntellectualSites/FastAsyncWorldEdit/issues?q=is%3Aissue) - [X] I made sure I am using an up-to-date version of [FastAsyncWorldEdit for 1.15.2](https://ci.athion.net/job/FastAsyncWorldEdit-1.15/) - [X] I made sure the bug/error is not caused by any other plugin	non_priority	blocks affected bug report for fastasyncworldedit link to info plugins config its not that important but when i do whatever operation it says blocks affected or blocks affected checklist i included all information required in the sections above i made sure there are no duplicates of this report i made sure i am using an up to date version of i made sure the bug error is not caused by any other plugin	0
9,505	3,050,965,584	IssuesEvent	2015-08-12 03:52:53	hylang/hy	https://api.github.com/repos/hylang/hy	closed	defn has no tests	backend good-first-bug missing-tests	I can't seem to fin any tests of defn. I have found some defn behaviour that is at least weird: I should not be able to use anything but a HySymbol as name for a function. I can currently use: * a string (defn "hy" [] 1) (this at least can later be called withouth quotes, which might be seem as inconsistent) * a lambda list. (defn &hy [] 1) This can't later be called. * any other new HyType I define that is a string (see my keywords pr #295, it can be used too) e.g.: (defn %hy [] 1) * keywords. (defn :hy [] 1) Although this one fails due to other reasons. Insonsistent behaviour: * (defn if [] 1) should either fail or override if macro? currently it doesn't fail but behavior is the one from "if" macro. I was planning to add some tests, but I'm not sure where should be added and if any of those is a non-issue	1.0	defn has no tests - I can't seem to fin any tests of defn. I have found some defn behaviour that is at least weird: I should not be able to use anything but a HySymbol as name for a function. I can currently use: * a string (defn "hy" [] 1) (this at least can later be called withouth quotes, which might be seem as inconsistent) * a lambda list. (defn &hy [] 1) This can't later be called. * any other new HyType I define that is a string (see my keywords pr #295, it can be used too) e.g.: (defn %hy [] 1) * keywords. (defn :hy [] 1) Although this one fails due to other reasons. Insonsistent behaviour: * (defn if [] 1) should either fail or override if macro? currently it doesn't fail but behavior is the one from "if" macro. I was planning to add some tests, but I'm not sure where should be added and if any of those is a non-issue	non_priority	defn has no tests i can t seem to fin any tests of defn i have found some defn behaviour that is at least weird i should not be able to use anything but a hysymbol as name for a function i can currently use a string defn hy this at least can later be called withouth quotes which might be seem as inconsistent a lambda list defn hy this can t later be called any other new hytype i define that is a string see my keywords pr it can be used too e g defn hy keywords defn hy although this one fails due to other reasons insonsistent behaviour defn if should either fail or override if macro currently it doesn t fail but behavior is the one from if macro i was planning to add some tests but i m not sure where should be added and if any of those is a non issue	0
701,532	24,100,138,446	IssuesEvent	2022-09-19 23:14:05	googleapis/nodejs-contact-center-insights	https://api.github.com/repos/googleapis/nodejs-contact-center-insights	closed	GetOperation: should get an operation failed	type: bug priority: p1 flakybot: issue api: contactcenterinsights	This test failed! To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot). If I'm commenting on this issue too often, add the `flakybot: quiet` label and I will stop commenting. --- commit: 2ad948341bab9ad17955c2186d9f72a82d22bc98 buildURL: [Build Status](https://source.cloud.google.com/results/invocations/62d966a3-834a-4583-8337-7405fbe2f225), [Sponge](http://sponge2/62d966a3-834a-4583-8337-7405fbe2f225) status: failed <details><summary>Test output</summary><br><pre>Command failed: node ./getOperation.js projects/long-door-651/locations/us-central1/operations/12345 16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project. Error: Command failed: node ./getOperation.js projects/long-door-651/locations/us-central1/operations/12345 16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project. at checkExecSyncError (child_process.js:635:11) at Object.execSync (child_process.js:671:15) at execSync (test/getOperation.test.js:21:28) at Context.<anonymous> (test/getOperation.test.js:42:22) at processImmediate (internal/timers.js:461:21)</pre></details>	1.0	GetOperation: should get an operation failed - This test failed! To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot). If I'm commenting on this issue too often, add the `flakybot: quiet` label and I will stop commenting. --- commit: 2ad948341bab9ad17955c2186d9f72a82d22bc98 buildURL: [Build Status](https://source.cloud.google.com/results/invocations/62d966a3-834a-4583-8337-7405fbe2f225), [Sponge](http://sponge2/62d966a3-834a-4583-8337-7405fbe2f225) status: failed <details><summary>Test output</summary><br><pre>Command failed: node ./getOperation.js projects/long-door-651/locations/us-central1/operations/12345 16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project. Error: Command failed: node ./getOperation.js projects/long-door-651/locations/us-central1/operations/12345 16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project. at checkExecSyncError (child_process.js:635:11) at Object.execSync (child_process.js:671:15) at execSync (test/getOperation.test.js:21:28) at Context.<anonymous> (test/getOperation.test.js:42:22) at processImmediate (internal/timers.js:461:21)</pre></details>	priority	getoperation should get an operation failed this test failed to configure my behavior see if i m commenting on this issue too often add the flakybot quiet label and i will stop commenting commit buildurl status failed test output command failed node getoperation js projects long door locations us operations unauthenticated request had invalid authentication credentials expected oauth access token login cookie or other valid authentication credential see error command failed node getoperation js projects long door locations us operations unauthenticated request had invalid authentication credentials expected oauth access token login cookie or other valid authentication credential see at checkexecsyncerror child process js at object execsync child process js at execsync test getoperation test js at context test getoperation test js at processimmediate internal timers js	1
33,811	7,255,176,226	IssuesEvent	2018-02-16 14:01:19	jOOQ/jOOQ	https://api.github.com/repos/jOOQ/jOOQ	closed	H2 MetaTable's string column default values are wrong	C: Functionality P: Medium R: Fixed T: Defect	For a table like: ```sql CREATE TABLE t (i VARCHAR(10) DEFAULT 'abc'); ``` The reported default value is `'abc'` (including apostrophes), not `abc` as in other databases.	1.0	H2 MetaTable's string column default values are wrong - For a table like: ```sql CREATE TABLE t (i VARCHAR(10) DEFAULT 'abc'); ``` The reported default value is `'abc'` (including apostrophes), not `abc` as in other databases.	non_priority	metatable s string column default values are wrong for a table like sql create table t i varchar default abc the reported default value is abc including apostrophes not abc as in other databases	0
725,564	24,966,401,714	IssuesEvent	2022-11-01 19:47:35	dompdf/dompdf	https://api.github.com/repos/dompdf/dompdf	closed	Allowed memory size of 134217728 bytes exhausted (tried to allocate 7680 bytes)	bug imported Priority-Medium	_Original author: josueru...@gmail.com (October 03, 2011 23:24:18)_ <b>What steps will reproduce the problem?</b> 1.Pass the html to library <b>What is the expected output? What do you see instead?</b> I got that message Allowed memory size of 134217728 bytes exhausted (tried to allocate 7680 bytes) in /home7/prosysco/public_html/102011/dompdf/include/text_frame_reflower.cls.php(381) : runtime-created function on line 1 <b>What version of the product are you using? On what operating system?</b> DOMPDF 0.6.0 beta2 <b>Please provide any additional information below.</b> I've expando de memory on my server but I doesnt work I some times i get this error when I set the memory with 256 mb i need some help with this issue Thanks!! _Original issue: http://code.google.com/p/dompdf/issues/detail?id=358_	1.0	Allowed memory size of 134217728 bytes exhausted (tried to allocate 7680 bytes) - _Original author: josueru...@gmail.com (October 03, 2011 23:24:18)_ <b>What steps will reproduce the problem?</b> 1.Pass the html to library <b>What is the expected output? What do you see instead?</b> I got that message Allowed memory size of 134217728 bytes exhausted (tried to allocate 7680 bytes) in /home7/prosysco/public_html/102011/dompdf/include/text_frame_reflower.cls.php(381) : runtime-created function on line 1 <b>What version of the product are you using? On what operating system?</b> DOMPDF 0.6.0 beta2 <b>Please provide any additional information below.</b> I've expando de memory on my server but I doesnt work I some times i get this error when I set the memory with 256 mb i need some help with this issue Thanks!! _Original issue: http://code.google.com/p/dompdf/issues/detail?id=358_	priority	allowed memory size of bytes exhausted tried to allocate bytes original author josueru gmail com october what steps will reproduce the problem pass the html to library what is the expected output what do you see instead i got that message allowed memory size of bytes exhausted tried to allocate bytes in prosysco public html dompdf include text frame reflower cls php runtime created function on line what version of the product are you using on what operating system dompdf please provide any additional information below i ve expando de memory on my server but i doesnt work i some times i get this error when i set the memory with mb i need some help with this issue thanks original issue	1
117,379	4,714,585,840	IssuesEvent	2016-10-15 02:01:36	CS2103AUG2016-T16-C3/main	https://api.github.com/repos/CS2103AUG2016-T16-C3/main	closed	Mark task as done	priority.high type.story	`done` command Would need to be stored also - add Done TaskProperty to Tasks and in Storage	1.0	Mark task as done - `done` command Would need to be stored also - add Done TaskProperty to Tasks and in Storage	priority	mark task as done done command would need to be stored also add done taskproperty to tasks and in storage	1
34,549	6,345,275,297	IssuesEvent	2017-07-27 21:51:42	alexreardon/memoize-one	https://api.github.com/repos/alexreardon/memoize-one	closed	Add recipes	documentation	Add some recipes to demonstrate some of the use cases of this library. Some ones I can think of write now - `react-redux` state queries - how it can be used in combination with `reselect` - caching expensive function calls - storing a 'previous' value - TBD	1.0	Add recipes - Add some recipes to demonstrate some of the use cases of this library. Some ones I can think of write now - `react-redux` state queries - how it can be used in combination with `reselect` - caching expensive function calls - storing a 'previous' value - TBD	non_priority	add recipes add some recipes to demonstrate some of the use cases of this library some ones i can think of write now react redux state queries how it can be used in combination with reselect caching expensive function calls storing a previous value tbd	0
180,776	13,959,148,061	IssuesEvent	2020-10-24 15:12:35	cockroachdb/cockroach	https://api.github.com/repos/cockroachdb/cockroach	closed	workload/workloadsql: TestSplits failed	C-test-failure O-robot branch-master	[(workload/workloadsql).TestSplits failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2390323&tab=buildLog) on [master@33e3abc57cccedd86dd1b2e1d58feb075fcb8dd4](https://github.com/cockroachdb/cockroach/commits/33e3abc57cccedd86dd1b2e1d58feb075fcb8dd4): ``` github.com/cockroachdb/cockroach/pkg/sql.(DistSQLPlanner).PlanAndRun() /go/src/github.com/cockroachdb/cockroach/pkg/sql/distsql_running.go:996 +0x288 github.com/cockroachdb/cockroach/pkg/sql.(connExecutor).execWithDistSQLEngine() /go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:1002 +0x5e3 github.com/cockroachdb/cockroach/pkg/sql.(connExecutor).dispatchToExecutionEngine() /go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:873 +0xb73 github.com/cockroachdb/cockroach/pkg/sql.(connExecutor).execStmtInOpenState() /go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:639 +0x11a9 github.com/cockroachdb/cockroach/pkg/sql.(connExecutor).execStmt() /go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:114 +0xe79 github.com/cockroachdb/cockroach/pkg/sql.(connExecutor).execCmd.func1() /go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:1442 +0x48f github.com/cockroachdb/cockroach/pkg/sql.(connExecutor).execCmd() /go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:1444 +0x1c20 github.com/cockroachdb/cockroach/pkg/sql.(connExecutor).run() /go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:1367 +0x3ff github.com/cockroachdb/cockroach/pkg/sql.(Server).ServeConn() /go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:477 +0x131 github.com/cockroachdb/cockroach/pkg/sql/pgwire.(conn).processCommandsAsync.func1() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/conn.go:627 +0x39a Goroutine 407 (running) created at: github.com/cockroachdb/cockroach/pkg/sql/pgwire.(conn).processCommandsAsync() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/conn.go:555 +0x1e9 github.com/cockroachdb/cockroach/pkg/sql/pgwire.(conn).serveImpl() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/conn.go:281 +0x8d6 github.com/cockroachdb/cockroach/pkg/sql/pgwire.(Server).serveConn() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/conn.go:155 +0x307 github.com/cockroachdb/cockroach/pkg/sql/pgwire.(Server).ServeConn() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/server.go:589 +0xa79 github.com/cockroachdb/cockroach/pkg/server.(sqlServer).startServeSQL.func1.1() /go/src/github.com/cockroachdb/cockroach/pkg/server/server.go:1989 +0x19c github.com/cockroachdb/cockroach/pkg/util/netutil.(Server).ServeWith.func1() /go/src/github.com/cockroachdb/cockroach/pkg/util/netutil/net.go:147 +0x104 Goroutine 254 (running) created at: github.com/cockroachdb/cockroach/pkg/sql/pgwire.(conn).processCommandsAsync() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/conn.go:555 +0x1e9 github.com/cockroachdb/cockroach/pkg/sql/pgwire.(conn).serveImpl() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/conn.go:281 +0x8d6 github.com/cockroachdb/cockroach/pkg/sql/pgwire.(Server).serveConn() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/conn.go:155 +0x307 github.com/cockroachdb/cockroach/pkg/sql/pgwire.(Server).ServeConn() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/server.go:589 +0xa79 github.com/cockroachdb/cockroach/pkg/server.(sqlServer).startServeSQL.func1.1() /go/src/github.com/cockroachdb/cockroach/pkg/server/server.go:1989 +0x19c github.com/cockroachdb/cockroach/pkg/util/netutil.(Server).ServeWith.func1() /go/src/github.com/cockroachdb/cockroach/pkg/util/netutil/net.go:147 +0x104 ================== FAIL github.com/cockroachdb/cockroach/pkg/workload/workloadsql 22.498s ``` <details><summary>More</summary><p> Parameters: - GOFLAGS=-json ``` make stressrace TESTS=TestSplits PKG=./pkg/workload/workloadsql TESTTIMEOUT=5m STRESSFLAGS='-timeout 5m' 2>&1 ``` [See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2ATestSplits.%2A&sort=title&restgroup=false&display=lastcommented+project) <sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>	1.0	workload/workloadsql: TestSplits failed - [(workload/workloadsql).TestSplits failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2390323&tab=buildLog) on [master@33e3abc57cccedd86dd1b2e1d58feb075fcb8dd4](https://github.com/cockroachdb/cockroach/commits/33e3abc57cccedd86dd1b2e1d58feb075fcb8dd4): ``` github.com/cockroachdb/cockroach/pkg/sql.(DistSQLPlanner).PlanAndRun() /go/src/github.com/cockroachdb/cockroach/pkg/sql/distsql_running.go:996 +0x288 github.com/cockroachdb/cockroach/pkg/sql.(connExecutor).execWithDistSQLEngine() /go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:1002 +0x5e3 github.com/cockroachdb/cockroach/pkg/sql.(connExecutor).dispatchToExecutionEngine() /go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:873 +0xb73 github.com/cockroachdb/cockroach/pkg/sql.(connExecutor).execStmtInOpenState() /go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:639 +0x11a9 github.com/cockroachdb/cockroach/pkg/sql.(connExecutor).execStmt() /go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:114 +0xe79 github.com/cockroachdb/cockroach/pkg/sql.(connExecutor).execCmd.func1() /go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:1442 +0x48f github.com/cockroachdb/cockroach/pkg/sql.(connExecutor).execCmd() /go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:1444 +0x1c20 github.com/cockroachdb/cockroach/pkg/sql.(connExecutor).run() /go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:1367 +0x3ff github.com/cockroachdb/cockroach/pkg/sql.(Server).ServeConn() /go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:477 +0x131 github.com/cockroachdb/cockroach/pkg/sql/pgwire.(conn).processCommandsAsync.func1() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/conn.go:627 +0x39a Goroutine 407 (running) created at: github.com/cockroachdb/cockroach/pkg/sql/pgwire.(conn).processCommandsAsync() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/conn.go:555 +0x1e9 github.com/cockroachdb/cockroach/pkg/sql/pgwire.(conn).serveImpl() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/conn.go:281 +0x8d6 github.com/cockroachdb/cockroach/pkg/sql/pgwire.(Server).serveConn() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/conn.go:155 +0x307 github.com/cockroachdb/cockroach/pkg/sql/pgwire.(Server).ServeConn() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/server.go:589 +0xa79 github.com/cockroachdb/cockroach/pkg/server.(sqlServer).startServeSQL.func1.1() /go/src/github.com/cockroachdb/cockroach/pkg/server/server.go:1989 +0x19c github.com/cockroachdb/cockroach/pkg/util/netutil.(Server).ServeWith.func1() /go/src/github.com/cockroachdb/cockroach/pkg/util/netutil/net.go:147 +0x104 Goroutine 254 (running) created at: github.com/cockroachdb/cockroach/pkg/sql/pgwire.(conn).processCommandsAsync() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/conn.go:555 +0x1e9 github.com/cockroachdb/cockroach/pkg/sql/pgwire.(conn).serveImpl() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/conn.go:281 +0x8d6 github.com/cockroachdb/cockroach/pkg/sql/pgwire.(Server).serveConn() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/conn.go:155 +0x307 github.com/cockroachdb/cockroach/pkg/sql/pgwire.(Server).ServeConn() /go/src/github.com/cockroachdb/cockroach/pkg/sql/pgwire/server.go:589 +0xa79 github.com/cockroachdb/cockroach/pkg/server.(sqlServer).startServeSQL.func1.1() /go/src/github.com/cockroachdb/cockroach/pkg/server/server.go:1989 +0x19c github.com/cockroachdb/cockroach/pkg/util/netutil.(Server).ServeWith.func1() /go/src/github.com/cockroachdb/cockroach/pkg/util/netutil/net.go:147 +0x104 ================== FAIL github.com/cockroachdb/cockroach/pkg/workload/workloadsql 22.498s ``` <details><summary>More</summary><p> Parameters: - GOFLAGS=-json ``` make stressrace TESTS=TestSplits PKG=./pkg/workload/workloadsql TESTTIMEOUT=5m STRESSFLAGS='-timeout 5m' 2>&1 ``` [See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2ATestSplits.%2A&sort=title&restgroup=false&display=lastcommented+project) <sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>	non_priority	workload workloadsql testsplits failed on github com cockroachdb cockroach pkg sql distsqlplanner planandrun go src github com cockroachdb cockroach pkg sql distsql running go github com cockroachdb cockroach pkg sql connexecutor execwithdistsqlengine go src github com cockroachdb cockroach pkg sql conn executor exec go github com cockroachdb cockroach pkg sql connexecutor dispatchtoexecutionengine go src github com cockroachdb cockroach pkg sql conn executor exec go github com cockroachdb cockroach pkg sql connexecutor execstmtinopenstate go src github com cockroachdb cockroach pkg sql conn executor exec go github com cockroachdb cockroach pkg sql connexecutor execstmt go src github com cockroachdb cockroach pkg sql conn executor exec go github com cockroachdb cockroach pkg sql connexecutor execcmd go src github com cockroachdb cockroach pkg sql conn executor go github com cockroachdb cockroach pkg sql connexecutor execcmd go src github com cockroachdb cockroach pkg sql conn executor go github com cockroachdb cockroach pkg sql connexecutor run go src github com cockroachdb cockroach pkg sql conn executor go github com cockroachdb cockroach pkg sql server serveconn go src github com cockroachdb cockroach pkg sql conn executor go github com cockroachdb cockroach pkg sql pgwire conn processcommandsasync go src github com cockroachdb cockroach pkg sql pgwire conn go goroutine running created at github com cockroachdb cockroach pkg sql pgwire conn processcommandsasync go src github com cockroachdb cockroach pkg sql pgwire conn go github com cockroachdb cockroach pkg sql pgwire conn serveimpl go src github com cockroachdb cockroach pkg sql pgwire conn go github com cockroachdb cockroach pkg sql pgwire server serveconn go src github com cockroachdb cockroach pkg sql pgwire conn go github com cockroachdb cockroach pkg sql pgwire server serveconn go src github com cockroachdb cockroach pkg sql pgwire server go github com cockroachdb cockroach pkg server sqlserver startservesql go src github com cockroachdb cockroach pkg server server go github com cockroachdb cockroach pkg util netutil server servewith go src github com cockroachdb cockroach pkg util netutil net go goroutine running created at github com cockroachdb cockroach pkg sql pgwire conn processcommandsasync go src github com cockroachdb cockroach pkg sql pgwire conn go github com cockroachdb cockroach pkg sql pgwire conn serveimpl go src github com cockroachdb cockroach pkg sql pgwire conn go github com cockroachdb cockroach pkg sql pgwire server serveconn go src github com cockroachdb cockroach pkg sql pgwire conn go github com cockroachdb cockroach pkg sql pgwire server serveconn go src github com cockroachdb cockroach pkg sql pgwire server go github com cockroachdb cockroach pkg server sqlserver startservesql go src github com cockroachdb cockroach pkg server server go github com cockroachdb cockroach pkg util netutil server servewith go src github com cockroachdb cockroach pkg util netutil net go fail github com cockroachdb cockroach pkg workload workloadsql more parameters goflags json make stressrace tests testsplits pkg pkg workload workloadsql testtimeout stressflags timeout powered by	0
557,045	16,499,270,405	IssuesEvent	2021-05-25 13:19:54	zephyrproject-rtos/zephyr	https://api.github.com/repos/zephyrproject-rtos/zephyr	closed	[Coverity CID: 208195] Out-of-bounds read in /zephyr/include/generated/syscalls/gpio.h (Generated Code)	Coverity bug priority: medium	Static code scan issues found in file: https://github.com/zephyrproject-rtos/zephyr/tree/374629af906a24add294b1c3b945128cb6a486e8//zephyr/include/generated/syscalls/gpio.h Category: Memory - illegal accesses Function: `gpio_pin_interrupt_configure` Component: Drivers CID: [208195](https://scan9.coverity.com/reports.htm#v29726/p12996/mergedDefectId=208195) Details: Please fix or provide comments in coverity using the link: https://scan9.coverity.com/reports.htm#v29271/p12996. Note: This issue was created automatically. Priority was set based on classification of the file affected and the impact field in coverity. Assignees were set using the CODEOWNERS file.	1.0	[Coverity CID: 208195] Out-of-bounds read in /zephyr/include/generated/syscalls/gpio.h (Generated Code) - Static code scan issues found in file: https://github.com/zephyrproject-rtos/zephyr/tree/374629af906a24add294b1c3b945128cb6a486e8//zephyr/include/generated/syscalls/gpio.h Category: Memory - illegal accesses Function: `gpio_pin_interrupt_configure` Component: Drivers CID: [208195](https://scan9.coverity.com/reports.htm#v29726/p12996/mergedDefectId=208195) Details: Please fix or provide comments in coverity using the link: https://scan9.coverity.com/reports.htm#v29271/p12996. Note: This issue was created automatically. Priority was set based on classification of the file affected and the impact field in coverity. Assignees were set using the CODEOWNERS file.	priority	out of bounds read in zephyr include generated syscalls gpio h generated code static code scan issues found in file category memory illegal accesses function gpio pin interrupt configure component drivers cid details please fix or provide comments in coverity using the link note this issue was created automatically priority was set based on classification of the file affected and the impact field in coverity assignees were set using the codeowners file	1
478,937	13,788,735,191	IssuesEvent	2020-10-09 07:44:58	AY2021S1-CS2113T-W13-2/tp	https://api.github.com/repos/AY2021S1-CS2113T-W13-2/tp	closed	Add food intake and calories	priority.High type.Story	As a student I can enter my food intake and its calories so that I can log my calories.	1.0	Add food intake and calories - As a student I can enter my food intake and its calories so that I can log my calories.	priority	add food intake and calories as a student i can enter my food intake and its calories so that i can log my calories	1
637,649	20,674,289,994	IssuesEvent	2022-03-10 07:33:56	logseq/logseq	https://api.github.com/repos/logseq/logseq	closed	Advanced queries using `:yesterday` use UTC instead of local time	:type/bug priority-A query	### What happened? Advanced queries using `:yesterday` seem to use UTC instead of local time. ### Reproduce the Bug 1. ``` {:title [:h2.font-bold "⏲️ YESTERDAY SCHEDULED and DEADLINE"] :query [:find (pull ?b [* {:block/_parent ...}]) :in $ ?date ?pattern :where (or [?b :block/scheduled ?day] [?b :block/deadline ?day]) [(= ?day ?date)] [?b :block/marker ?marker] [(contains? #{"TODO" "DOING" "NOW" "LATER" "WAITING"} ?marker)] [?b :block/content ?desc] (not [(clojure.string/includes? ?desc ?pattern)])] :inputs [:yesterday "DAILY"] :result-transform (fn [result] (sort-by (fn [h] (get h :block/priority "Z")) result)) } ``` The query above shows the tasks based on UTC time. In other words, the results don't flip over at midnight localtime, but flip over at midnight UTC. ### Expected Behavior `:yesterday` should use local time. ### Screenshots _No response_ ### Desktop Platform Information Windows 10, Desktop version 0.5.9 ### Mobile Platform Information Android 10, apk 0.5.9, 0.6.2 ### Additional Context `:today` seems to correctly use local time.	1.0	Advanced queries using `:yesterday` use UTC instead of local time - ### What happened? Advanced queries using `:yesterday` seem to use UTC instead of local time. ### Reproduce the Bug 1. ``` {:title [:h2.font-bold "⏲️ YESTERDAY SCHEDULED and DEADLINE"] :query [:find (pull ?b [* {:block/_parent ...}]) :in $ ?date ?pattern :where (or [?b :block/scheduled ?day] [?b :block/deadline ?day]) [(= ?day ?date)] [?b :block/marker ?marker] [(contains? #{"TODO" "DOING" "NOW" "LATER" "WAITING"} ?marker)] [?b :block/content ?desc] (not [(clojure.string/includes? ?desc ?pattern)])] :inputs [:yesterday "DAILY"] :result-transform (fn [result] (sort-by (fn [h] (get h :block/priority "Z")) result)) } ``` The query above shows the tasks based on UTC time. In other words, the results don't flip over at midnight localtime, but flip over at midnight UTC. ### Expected Behavior `:yesterday` should use local time. ### Screenshots _No response_ ### Desktop Platform Information Windows 10, Desktop version 0.5.9 ### Mobile Platform Information Android 10, apk 0.5.9, 0.6.2 ### Additional Context `:today` seems to correctly use local time.	priority	advanced queries using yesterday use utc instead of local time what happened advanced queries using yesterday seem to use utc instead of local time reproduce the bug title query in date pattern where or not inputs result transform fn sort by fn get h block priority z result the query above shows the tasks based on utc time in other words the results don t flip over at midnight localtime but flip over at midnight utc expected behavior yesterday should use local time screenshots no response desktop platform information windows desktop version mobile platform information android apk additional context today seems to correctly use local time	1
522,322	15,158,376,250	IssuesEvent	2021-02-12 01:00:10	NOAA-GSL/MATS	https://api.github.com/repos/NOAA-GSL/MATS	closed	Difference curves in DailyModelCycle plots are occasionally wrong	Priority: Medium Project: MATS Status: Closed Type: Bug	--- Author Name: molly.b.smith (@mollybsmith-noaa) Original Redmine Issue: 81622, https://vlab.ncep.noaa.gov/redmine/issues/81622 Original Date: 2020-08-06 Original Assignee: molly.b.smith --- Stan noticed that once in a while, DailyModelCycle difference curves start producing incorrect values following a data gap.	1.0	Difference curves in DailyModelCycle plots are occasionally wrong - --- Author Name: molly.b.smith (@mollybsmith-noaa) Original Redmine Issue: 81622, https://vlab.ncep.noaa.gov/redmine/issues/81622 Original Date: 2020-08-06 Original Assignee: molly.b.smith --- Stan noticed that once in a while, DailyModelCycle difference curves start producing incorrect values following a data gap.	priority	difference curves in dailymodelcycle plots are occasionally wrong author name molly b smith mollybsmith noaa original redmine issue original date original assignee molly b smith stan noticed that once in a while dailymodelcycle difference curves start producing incorrect values following a data gap	1
14,138	3,228,075,985	IssuesEvent	2015-10-11 19:37:59	polygon-studios/master	https://api.github.com/repos/polygon-studios/master	opened	Trap Designs	design	Create final trap designs. Make one for unity, and one for mobile. Ask Ian and Reza what their requirements are for dimensions. You will have a two week period to work on this	1.0	Trap Designs - Create final trap designs. Make one for unity, and one for mobile. Ask Ian and Reza what their requirements are for dimensions. You will have a two week period to work on this	non_priority	trap designs create final trap designs make one for unity and one for mobile ask ian and reza what their requirements are for dimensions you will have a two week period to work on this	0
34,780	14,519,766,662	IssuesEvent	2020-12-14 03:43:22	MicrosoftDocs/azure-docs	https://api.github.com/repos/MicrosoftDocs/azure-docs	closed	Document need to update	cognitive-services/svc cxp product-question speech-service/subsvc triaged	[Create a keyword in Speech Studio](https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/custom-keyword-basics?pivots=programming-language-csharp#create-a-keyword-in-speech-studio) In step 3, there is no "Language" option, please help to update the doc. Thanks. ![image](https://user-images.githubusercontent.com/22313449/101714336-547eb580-3ad4-11eb-8160-a539ad1d46a4.png) --- #### Document Details ⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking. * ID: 02f19f0c-f14b-bac9-3706-93c888eb3bb2 * Version Independent ID: ed76fd34-0256-eb27-a55f-5d2735859f98 * Content: [Create Keyword quickstart - Speech service - Azure Cognitive Services](https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/custom-keyword-basics?pivots=programming-language-csharp) * Content Source: [articles/cognitive-services/Speech-Service/custom-keyword-basics.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/cognitive-services/Speech-Service/custom-keyword-basics.md) * Service: cognitive-services * Sub-service: speech-service * GitHub Login: @trevorbye * Microsoft Alias: trbye	2.0	Document need to update - [Create a keyword in Speech Studio](https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/custom-keyword-basics?pivots=programming-language-csharp#create-a-keyword-in-speech-studio) In step 3, there is no "Language" option, please help to update the doc. Thanks. ![image](https://user-images.githubusercontent.com/22313449/101714336-547eb580-3ad4-11eb-8160-a539ad1d46a4.png) --- #### Document Details ⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking. * ID: 02f19f0c-f14b-bac9-3706-93c888eb3bb2 * Version Independent ID: ed76fd34-0256-eb27-a55f-5d2735859f98 * Content: [Create Keyword quickstart - Speech service - Azure Cognitive Services](https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/custom-keyword-basics?pivots=programming-language-csharp) * Content Source: [articles/cognitive-services/Speech-Service/custom-keyword-basics.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/cognitive-services/Speech-Service/custom-keyword-basics.md) * Service: cognitive-services * Sub-service: speech-service * GitHub Login: @trevorbye * Microsoft Alias: trbye	non_priority	document need to update in step there is no language option please help to update the doc thanks 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 cognitive services sub service speech service github login trevorbye microsoft alias trbye	0
267,197	8,380,222,914	IssuesEvent	2018-10-07 12:35:26	dirkwhoffmann/virtualc64	https://api.github.com/repos/dirkwhoffmann/virtualc64	closed	CIA/cia-timer.prg fails for new CIAs	Priority-Medium V 3.0 bug	<img width="1053" alt="bildschirmfoto 2018-10-04 um 07 49 07" src="https://user-images.githubusercontent.com/12561945/46455467-7620db80-c7ab-11e8-91c6-7b5aaaf2d104.png">	1.0	CIA/cia-timer.prg fails for new CIAs - <img width="1053" alt="bildschirmfoto 2018-10-04 um 07 49 07" src="https://user-images.githubusercontent.com/12561945/46455467-7620db80-c7ab-11e8-91c6-7b5aaaf2d104.png">	priority	cia cia timer prg fails for new cias img width alt bildschirmfoto um src	1
19,815	10,534,744,704	IssuesEvent	2019-10-01 15:21:22	mozilla-frontend-infra/firefox-health-dashboard	https://api.github.com/repos/mozilla-frontend-infra/firefox-health-dashboard	opened	Add Chrome results for all benchmarks	P1 enhancement performance-team	Now that we're running all tests against Chrome we should plot these in the benchmarks, such as Speedometer: https://health.graphics/quantum/subtests?suite=Speedometer&platform=win64&past=month	True	Add Chrome results for all benchmarks - Now that we're running all tests against Chrome we should plot these in the benchmarks, such as Speedometer: https://health.graphics/quantum/subtests?suite=Speedometer&platform=win64&past=month	non_priority	add chrome results for all benchmarks now that we re running all tests against chrome we should plot these in the benchmarks such as speedometer	0
27,489	2,693,367,117	IssuesEvent	2015-04-01 14:24:54	cs2103jan2015-t13-4j/main	https://api.github.com/repos/cs2103jan2015-t13-4j/main	closed	A user can add task with specific time	priority.high type.story	...so it will be more efficient for the user to follow the tasks correctly	1.0	A user can add task with specific time - ...so it will be more efficient for the user to follow the tasks correctly	priority	a user can add task with specific time so it will be more efficient for the user to follow the tasks correctly	1
19,686	6,757,202,029	IssuesEvent	2017-10-24 09:55:40	godotengine/godot	https://api.github.com/repos/godotengine/godot	closed	VS 2013 compilation error (C1045: compiler limitations: the link specification is too nested)	bug platform:windows topic:buildsystem	C:\MyWork\godot\modules\gdnative\godot/vector3.h (34): fatal, error, C1045: compiler Limitations: the link specification is too nested	1.0	VS 2013 compilation error (C1045: compiler limitations: the link specification is too nested) - C:\MyWork\godot\modules\gdnative\godot/vector3.h (34): fatal, error, C1045: compiler Limitations: the link specification is too nested	non_priority	vs compilation error compiler limitations the link specification is too nested c mywork godot modules gdnative godot h fatal error compiler limitations the link specification is too nested	0
14,918	5,013,047,692	IssuesEvent	2016-12-13 13:25:41	jyrgenn/lingo	https://api.github.com/repos/jyrgenn/lingo	closed	data-driven arguments type check	code improvement research	Try arguments type check for builtins like in Lis.pl using an arguments type descriptor. While letters/enums would work, perhaps a slice of function pointers (to functions that do the actual check of one argument or, say, set an optional/rest flag) might even be faster than the current scheme.	1.0	data-driven arguments type check - Try arguments type check for builtins like in Lis.pl using an arguments type descriptor. While letters/enums would work, perhaps a slice of function pointers (to functions that do the actual check of one argument or, say, set an optional/rest flag) might even be faster than the current scheme.	non_priority	data driven arguments type check try arguments type check for builtins like in lis pl using an arguments type descriptor while letters enums would work perhaps a slice of function pointers to functions that do the actual check of one argument or say set an optional rest flag might even be faster than the current scheme	0
2,968	10,677,235,074	IssuesEvent	2019-10-21 15:06:07	ansible/ansible	https://api.github.com/repos/ansible/ansible	closed	iam_user module fails to remove an AWS user	affects_2.8 aws bug cloud has_pr module needs_maintainer python3 support:community traceback	<!--- Verify first that your issue is not already reported on GitHub --> <!--- Also test if the latest release and devel branch are affected too --> <!--- Complete all sections as described, this form is processed automatically --> ##### SUMMARY <!--- Explain the problem briefly below --> `iam_user` module fails to remove am AWS user if it has: a group membership, console password (login profile), access keys, MFA device, etc.. ##### ISSUE TYPE - Bug Report ##### COMPONENT NAME <!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure --> iam_user ##### ANSIBLE VERSION <!--- Paste verbatim output from "ansible --version" between quotes --> ```paste below ansible 2.8.2 config file = /etc/ansible/ansible.cfg configured module search path = ['/home/agustin/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = .../venv/lib/python3.5/site-packages/ansible executable location =.../venv/bin/ansible python version = 3.5.7 (default, Mar 30 2019, 01:05:18) [GCC 7.3.0] ``` ##### CONFIGURATION <!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes --> ```paste below ``` ##### OS / ENVIRONMENT <!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. --> ##### STEPS TO REPRODUCE <!--- Describe exactly how to reproduce the problem, using a minimal test-case --> Create an AWS user `test` with password or access keys <!--- Paste example playbooks or commands between quotes below --> ```yaml - hosts: localhost tasks: - iam_user: name: test state: absent ``` <!--- HINT: You can paste gist.github.com links for larger files --> ##### EXPECTED RESULTS <!--- Describe what you expected to happen when running the steps above --> User's state = absent ##### ACTUAL RESULTS <!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) --> <!--- Paste verbatim command output between quotes --> ```paste below TASK [iam_user] ************************************************************************************************************************************** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: botocore.errorfactory.DeleteConflictException: An error occurred (DeleteConflict) when calling the DeleteUser operation: Cannot delete entity, must delete login profile first. fatal: [localhost]: FAILED! => {"changed": false, "error": {"code": "DeleteConflict", "message": "Cannot delete entity, must delete login profile first.", "type": "Sender"}, "msg": "Unable to delete user test: An error occurred (DeleteConflict) when calling the DeleteUser operation: Cannot delete entity, must delete login profile first.", "response_metadata": {"http_headers": {"content-length": "300", "content-type": "text/xml", "date": "Sun, 14 Jul 2019 18:34:25 GMT", "x-amzn-requestid": "01da0109-a666-11e9-adeb-83c56b62b76d"}, "http_status_code": 409, "request_id": "01da0109-a666-11e9-adeb-83c56b62b76d", "retry_attempts": 0}} ```	True	iam_user module fails to remove an AWS user - <!--- Verify first that your issue is not already reported on GitHub --> <!--- Also test if the latest release and devel branch are affected too --> <!--- Complete all sections as described, this form is processed automatically --> ##### SUMMARY <!--- Explain the problem briefly below --> `iam_user` module fails to remove am AWS user if it has: a group membership, console password (login profile), access keys, MFA device, etc.. ##### ISSUE TYPE - Bug Report ##### COMPONENT NAME <!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure --> iam_user ##### ANSIBLE VERSION <!--- Paste verbatim output from "ansible --version" between quotes --> ```paste below ansible 2.8.2 config file = /etc/ansible/ansible.cfg configured module search path = ['/home/agustin/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = .../venv/lib/python3.5/site-packages/ansible executable location =.../venv/bin/ansible python version = 3.5.7 (default, Mar 30 2019, 01:05:18) [GCC 7.3.0] ``` ##### CONFIGURATION <!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes --> ```paste below ``` ##### OS / ENVIRONMENT <!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. --> ##### STEPS TO REPRODUCE <!--- Describe exactly how to reproduce the problem, using a minimal test-case --> Create an AWS user `test` with password or access keys <!--- Paste example playbooks or commands between quotes below --> ```yaml - hosts: localhost tasks: - iam_user: name: test state: absent ``` <!--- HINT: You can paste gist.github.com links for larger files --> ##### EXPECTED RESULTS <!--- Describe what you expected to happen when running the steps above --> User's state = absent ##### ACTUAL RESULTS <!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) --> <!--- Paste verbatim command output between quotes --> ```paste below TASK [iam_user] ************************************************************************************************************************************** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: botocore.errorfactory.DeleteConflictException: An error occurred (DeleteConflict) when calling the DeleteUser operation: Cannot delete entity, must delete login profile first. fatal: [localhost]: FAILED! => {"changed": false, "error": {"code": "DeleteConflict", "message": "Cannot delete entity, must delete login profile first.", "type": "Sender"}, "msg": "Unable to delete user test: An error occurred (DeleteConflict) when calling the DeleteUser operation: Cannot delete entity, must delete login profile first.", "response_metadata": {"http_headers": {"content-length": "300", "content-type": "text/xml", "date": "Sun, 14 Jul 2019 18:34:25 GMT", "x-amzn-requestid": "01da0109-a666-11e9-adeb-83c56b62b76d"}, "http_status_code": 409, "request_id": "01da0109-a666-11e9-adeb-83c56b62b76d", "retry_attempts": 0}} ```	non_priority	iam user module fails to remove an aws user summary iam user module fails to remove am aws user if it has a group membership console password login profile access keys mfa device etc issue type bug report component name iam user ansible version paste below ansible config file etc ansible ansible cfg configured module search path ansible python module location venv lib site packages ansible executable location venv bin ansible python version default mar configuration paste below os environment steps to reproduce create an aws user test with password or access keys yaml hosts localhost tasks iam user name test state absent expected results user s state absent actual results paste below task an exception occurred during task execution to see the full traceback use vvv the error was botocore errorfactory deleteconflictexception an error occurred deleteconflict when calling the deleteuser operation cannot delete entity must delete login profile first fatal failed changed false error code deleteconflict message cannot delete entity must delete login profile first type sender msg unable to delete user test an error occurred deleteconflict when calling the deleteuser operation cannot delete entity must delete login profile first response metadata http headers content length content type text xml date sun jul gmt x amzn requestid adeb http status code request id adeb retry attempts	0
163,172	13,912,433,453	IssuesEvent	2020-10-20 18:51:53	Kajabi/sage	https://api.github.com/repos/Kajabi/sage	closed	Base print styles for documentation	OLD documentation low priority	## Description Low-hanging fruit for print media: - Standardize padding for pages - Adjust typography as needed, add borders to separate headings from content - Remove extraneous items (navigation, icons)	1.0	Base print styles for documentation - ## Description Low-hanging fruit for print media: - Standardize padding for pages - Adjust typography as needed, add borders to separate headings from content - Remove extraneous items (navigation, icons)	non_priority	base print styles for documentation description low hanging fruit for print media standardize padding for pages adjust typography as needed add borders to separate headings from content remove extraneous items navigation icons	0
17,161	10,606,823,083	IssuesEvent	2019-10-11 01:04:03	microsoft/vscode-cpptools	https://api.github.com/repos/microsoft/vscode-cpptools	closed	C++11 'alignof' keyword not recognized	Language Service external	<img width="220" alt="screen shot 2017-08-01 at 20 15 36" src="https://user-images.githubusercontent.com/18319900/28856161-32c6c40a-76f6-11e7-883f-183eb5df35b9.png"> I know I could've tweak with the language setting file but updates can overwrite my modification...	1.0	C++11 'alignof' keyword not recognized - <img width="220" alt="screen shot 2017-08-01 at 20 15 36" src="https://user-images.githubusercontent.com/18319900/28856161-32c6c40a-76f6-11e7-883f-183eb5df35b9.png"> I know I could've tweak with the language setting file but updates can overwrite my modification...	non_priority	c alignof keyword not recognized img width alt screen shot at src i know i could ve tweak with the language setting file but updates can overwrite my modification	0

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.