Technical Debt and it Types Datasets
Collection
24 items
•
Updated
•
1
Dataset Viewer
Unnamed: 0
int64 3
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 2
430
| labels
stringlengths 4
347
| body
stringlengths 5
237k
| index
stringclasses 7
values | text_combine
stringlengths 96
237k
| label
stringclasses 2
values | text
stringlengths 96
219k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
13,686 | 16,375,895,669 | IssuesEvent | 2021-05-16 04:23:48 | zlib-ng/zlib-ng | https://api.github.com/repos/zlib-ng/zlib-ng | closed | Building breaks when both _FILE_OFFSET_BITS=64 and ZLIB_COMPAT are defined | Compatibility | With the `develop` branch (`9f78490`) or the latest release version 2.0.2:
When both `ZLIB_COMPAT` and `_FILE_OFFSET_BITS=64` are defined, building breaks due to `Z_WANT64` getting defined and activating the definition of the macros that rename some function names to be suffixed with "64" which causes compiler errors due to multiple definitions of these functions.
On Solaris (SunOS 5.10, using GCC 5.2.0, at least), `_FILE_OFFSET_BITS` is automatically defined by the system headers when it is not already defined (`/usr/include/sys/feature_tests.h`), and so building for 64-bit breaks on Solaris currently.
It also breaks on Linux (Ubuntu 18.04 at least) if you do `-D_FILE_OFFSET_BITS=64`.
If I interpret the Large File Support specs correctly, explicitly defining `_FILE_OFFSET_BITS` is permitted, and so building with that should work.
E.g., here is one of the errors:
```
In file included from adler32.c:6:0:
adler32.c:132:32: error: redefinition of ‘adler32_combine64’
unsigned long Z_EXPORT PREFIX4(adler32_combine)(unsigned long adler1, unsigned long adler2, z_off64_t len2) {
^
zbuild.h:17:22: note: in definition of macro ‘PREFIX4’
# define PREFIX4(x) x ## 64
^
zlib.h:1802:29: note: previous definition of ‘adler32_combine64’ was here
# define adler32_combine adler32_combine64
^
zbuild.h:14:21: note: in definition of macro ‘PREFIX’
# define PREFIX(x) x
^
adler32.c:128:31: note: in expansion of macro ‘adler32_combine’
unsigned long Z_EXPORT PREFIX(adler32_combine)(unsigned long adler1, unsigned long adler2, z_off_t len2) {
^~~~~~~~~~~~~~~
Makefile:258: recipe for target 'adler32.o' failed
make: *** [adler32.o] Error 1
```
The problem is that after `PREFIX(ident)` expands to `ident` then `ident` refers to one of the renaming macros defined due to `Z_WANT64` and so `ident` then expands to `ident64`, but there is already another definition of `ident64`.
This can be reproduced in Ubuntu 18 (and I assume other Linux distros) by doing either:
```bash
cmake -D "CMAKE_C_FLAGS=-D_FILE_OFFSET_BITS=64" -D ZLIB_COMPAT=ON ../zlib-ng
cmake --build .
```
or
```bash
CFLAGS="-D_FILE_OFFSET_BITS=64" ../zlib-ng/configure --zlib-compat
make
```
And can be reproduced in Solaris 10 by simply trying to build without giving `-D_FILE_OFFSET_BITS=64` (and with giving `-m64` if needed). | True | Building breaks when both _FILE_OFFSET_BITS=64 and ZLIB_COMPAT are defined - With the `develop` branch (`9f78490`) or the latest release version 2.0.2:
When both `ZLIB_COMPAT` and `_FILE_OFFSET_BITS=64` are defined, building breaks due to `Z_WANT64` getting defined and activating the definition of the macros that rename some function names to be suffixed with "64" which causes compiler errors due to multiple definitions of these functions.
On Solaris (SunOS 5.10, using GCC 5.2.0, at least), `_FILE_OFFSET_BITS` is automatically defined by the system headers when it is not already defined (`/usr/include/sys/feature_tests.h`), and so building for 64-bit breaks on Solaris currently.
It also breaks on Linux (Ubuntu 18.04 at least) if you do `-D_FILE_OFFSET_BITS=64`.
If I interpret the Large File Support specs correctly, explicitly defining `_FILE_OFFSET_BITS` is permitted, and so building with that should work.
E.g., here is one of the errors:
```
In file included from adler32.c:6:0:
adler32.c:132:32: error: redefinition of ‘adler32_combine64’
unsigned long Z_EXPORT PREFIX4(adler32_combine)(unsigned long adler1, unsigned long adler2, z_off64_t len2) {
^
zbuild.h:17:22: note: in definition of macro ‘PREFIX4’
# define PREFIX4(x) x ## 64
^
zlib.h:1802:29: note: previous definition of ‘adler32_combine64’ was here
# define adler32_combine adler32_combine64
^
zbuild.h:14:21: note: in definition of macro ‘PREFIX’
# define PREFIX(x) x
^
adler32.c:128:31: note: in expansion of macro ‘adler32_combine’
unsigned long Z_EXPORT PREFIX(adler32_combine)(unsigned long adler1, unsigned long adler2, z_off_t len2) {
^~~~~~~~~~~~~~~
Makefile:258: recipe for target 'adler32.o' failed
make: *** [adler32.o] Error 1
```
The problem is that after `PREFIX(ident)` expands to `ident` then `ident` refers to one of the renaming macros defined due to `Z_WANT64` and so `ident` then expands to `ident64`, but there is already another definition of `ident64`.
This can be reproduced in Ubuntu 18 (and I assume other Linux distros) by doing either:
```bash
cmake -D "CMAKE_C_FLAGS=-D_FILE_OFFSET_BITS=64" -D ZLIB_COMPAT=ON ../zlib-ng
cmake --build .
```
or
```bash
CFLAGS="-D_FILE_OFFSET_BITS=64" ../zlib-ng/configure --zlib-compat
make
```
And can be reproduced in Solaris 10 by simply trying to build without giving `-D_FILE_OFFSET_BITS=64` (and with giving `-m64` if needed). | comp | building breaks when both file offset bits and zlib compat are defined with the develop branch or the latest release version when both zlib compat and file offset bits are defined building breaks due to z getting defined and activating the definition of the macros that rename some function names to be suffixed with which causes compiler errors due to multiple definitions of these functions on solaris sunos using gcc at least file offset bits is automatically defined by the system headers when it is not already defined usr include sys feature tests h and so building for bit breaks on solaris currently it also breaks on linux ubuntu at least if you do d file offset bits if i interpret the large file support specs correctly explicitly defining file offset bits is permitted and so building with that should work e g here is one of the errors in file included from c c error redefinition of ‘ ’ unsigned long z export combine unsigned long unsigned long z t zbuild h note in definition of macro ‘ ’ define x x zlib h note previous definition of ‘ ’ was here define combine zbuild h note in definition of macro ‘prefix’ define prefix x x c note in expansion of macro ‘ combine’ unsigned long z export prefix combine unsigned long unsigned long z off t makefile recipe for target o failed make error the problem is that after prefix ident expands to ident then ident refers to one of the renaming macros defined due to z and so ident then expands to but there is already another definition of this can be reproduced in ubuntu and i assume other linux distros by doing either bash cmake d cmake c flags d file offset bits d zlib compat on zlib ng cmake build or bash cflags d file offset bits zlib ng configure zlib compat make and can be reproduced in solaris by simply trying to build without giving d file offset bits and with giving if needed | 1 |
33,146 | 6,159,874,354 | IssuesEvent | 2017-06-29 02:18:34 | randdusing/cordova-plugin-bluetoothle | https://api.github.com/repos/randdusing/cordova-plugin-bluetoothle | closed | Where is the example? | documentation | Hi, I'm trying to use this plugin, but i can't find one single example how to use connect() or startScan() functions. Can u provide us some examples? Thank you. | 1.0 | Where is the example? - Hi, I'm trying to use this plugin, but i can't find one single example how to use connect() or startScan() functions. Can u provide us some examples? Thank you. | non_comp | where is the example hi i m trying to use this plugin but i can t find one single example how to use connect or startscan functions can u provide us some examples thank you | 0 |
3,044 | 5,953,293,855 | IssuesEvent | 2017-05-27 06:12:22 | LibertyForce-Gmod/Weapon-Properties-Editor | https://api.github.com/repos/LibertyForce-Gmod/Weapon-Properties-Editor | opened | Incompatible with "Manual Weapon Pickup" | incompatibility | Incompatible with [Manual Weapon Pickup](http://steamcommunity.com/sharedfiles/filedetails/?id=167545348).
[User report](http://steamcommunity.com/workshop/filedetails/discussion/933160196/1291817208490965521/#c1291817208493344026):
> This addon isn't compatible with replacements, it make replacements useless. For example, you replace hl2 pistol with some other custom weapon, but this addon will make you pick up hl2 pistol anyway.
Weapon replacements doesn't work. | True | Incompatible with "Manual Weapon Pickup" - Incompatible with [Manual Weapon Pickup](http://steamcommunity.com/sharedfiles/filedetails/?id=167545348).
[User report](http://steamcommunity.com/workshop/filedetails/discussion/933160196/1291817208490965521/#c1291817208493344026):
> This addon isn't compatible with replacements, it make replacements useless. For example, you replace hl2 pistol with some other custom weapon, but this addon will make you pick up hl2 pistol anyway.
Weapon replacements doesn't work. | comp | incompatible with manual weapon pickup incompatible with this addon isn t compatible with replacements it make replacements useless for example you replace pistol with some other custom weapon but this addon will make you pick up pistol anyway weapon replacements doesn t work | 1 |
17,678 | 24,370,860,360 | IssuesEvent | 2022-10-03 19:09:25 | bitcoindevkit/bdk-ffi | https://api.github.com/repos/bitcoindevkit/bdk-ffi | closed | Add ability to retrieve private master key from a BIP39 seed | ldk-compatibility | This can be used to seed an LDK [KeysManager](https://docs.rs/lightning/0.0.110/lightning/chain/keysinterface/struct.KeysManager.html) with the first 32 bytes from this 64-byte seed.
This enables the entropy we give to LDK to be within the backup system of the on-chain wallet, and allow for 12-to-24-word mnemonics with optional passphrases. | True | Add ability to retrieve private master key from a BIP39 seed - This can be used to seed an LDK [KeysManager](https://docs.rs/lightning/0.0.110/lightning/chain/keysinterface/struct.KeysManager.html) with the first 32 bytes from this 64-byte seed.
This enables the entropy we give to LDK to be within the backup system of the on-chain wallet, and allow for 12-to-24-word mnemonics with optional passphrases. | comp | add ability to retrieve private master key from a seed this can be used to seed an ldk with the first bytes from this byte seed this enables the entropy we give to ldk to be within the backup system of the on chain wallet and allow for to word mnemonics with optional passphrases | 1 |
94,695 | 8,513,837,074 | IssuesEvent | 2018-10-31 16:59:44 | friendica/friendica | https://api.github.com/repos/friendica/friendica | closed | PHP 7.0 Tests: Could not load mock Friendica\Database\DBStructure, class already exists | Bug Tests | See https://travis-ci.org/friendica/friendica/jobs/448349959
Paging @nupplaphil | 1.0 | PHP 7.0 Tests: Could not load mock Friendica\Database\DBStructure, class already exists - See https://travis-ci.org/friendica/friendica/jobs/448349959
Paging @nupplaphil | non_comp | php tests could not load mock friendica database dbstructure class already exists see paging nupplaphil | 0 |
9,820 | 11,862,761,445 | IssuesEvent | 2020-03-25 18:29:25 | ldtteam/minecolonies | https://api.github.com/repos/ldtteam/minecolonies | closed | Add Rack Compatibility with Mouse Tweaks | Compatibility: Mod | I'd like to use Mouse Tweaks to sort (usually with my middle-click) the inventory of a Rack.
Please and thanks! | True | Add Rack Compatibility with Mouse Tweaks - I'd like to use Mouse Tweaks to sort (usually with my middle-click) the inventory of a Rack.
Please and thanks! | comp | add rack compatibility with mouse tweaks i d like to use mouse tweaks to sort usually with my middle click the inventory of a rack please and thanks | 1 |
40,536 | 16,502,630,145 | IssuesEvent | 2021-05-25 15:44:14 | microsoft/vscode-cpptools | https://api.github.com/repos/microsoft/vscode-cpptools | closed | Extension causes high cpu load | Language Service more info needed performance | - Issue Type: `Performance`
- Extension Name: `cpptools`
- Extension Version: `1.3.1`
- OS Version: `Windows_NT x64 10.0.19042`
- VS Code version: `1.56.2`
:warning: Make sure to **attach** this file from your *home*-directory:
:warning:`d:\Users\Cuneyt.000\AppData\Local\Temp\ms-vscode.cpptools-unresponsive.cpuprofile.txt`
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-
[ms-vscode.cpptools-unresponsive.cpuprofile.txt](https://github.com/microsoft/vscode-cpptools/files/6501656/ms-vscode.cpptools-unresponsive.cpuprofile.txt)
[austin.code-gnu-global-unresponsive.cpuprofile.txt](https://github.com/microsoft/vscode-cpptools/files/6501660/austin.code-gnu-global-unresponsive.cpuprofile.txt)
high-cpu-load | 1.0 | Extension causes high cpu load - - Issue Type: `Performance`
- Extension Name: `cpptools`
- Extension Version: `1.3.1`
- OS Version: `Windows_NT x64 10.0.19042`
- VS Code version: `1.56.2`
:warning: Make sure to **attach** this file from your *home*-directory:
:warning:`d:\Users\Cuneyt.000\AppData\Local\Temp\ms-vscode.cpptools-unresponsive.cpuprofile.txt`
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-
[ms-vscode.cpptools-unresponsive.cpuprofile.txt](https://github.com/microsoft/vscode-cpptools/files/6501656/ms-vscode.cpptools-unresponsive.cpuprofile.txt)
[austin.code-gnu-global-unresponsive.cpuprofile.txt](https://github.com/microsoft/vscode-cpptools/files/6501660/austin.code-gnu-global-unresponsive.cpuprofile.txt)
high-cpu-load | non_comp | extension causes high cpu load issue type performance extension name cpptools extension version os version windows nt vs code version warning make sure to attach this file from your home directory warning d users cuneyt appdata local temp ms vscode cpptools unresponsive cpuprofile txt find more details here high cpu load | 0 |
12,425 | 14,677,312,120 | IssuesEvent | 2020-12-30 22:53:06 | scylladb/scylla | https://api.github.com/repos/scylladb/scylla | opened | Frozen set may be created out-of-order via a prepared statement | CQL bug cassandra 2.2 compatibility | In Scylla, "set" collections are sorted - by the element type's natural order.
Although this is not clearly documented as far as I can tell (?), clients may assume that this the case also for a **frozen** set, for example used as a partition key.
It appears that Scylla can forget to sort the frozen set when inserted using a prepared statement, although does sort it as expected when inserted inline in the statement. It appears that Cassandra correctly sorts the frozen set also for prepared statement.
Here is one subtle and elaborate test case which breaks using a Python driver like an ordinary client. Take a look at this test code:
```python
@pytest.fixture(scope="session")
def table1(cql, test_keyspace):
table = test_keyspace + "." + unique_name()
cql.execute(f"CREATE TABLE {table} (k frozen<map<set<int>, int>> PRIMARY KEY)")
yield table
cql.execute("DROP TABLE " + table)
def test_broken(cql, table1):
insert = cql.prepare(f"INSERT INTO {table1} (k) VALUES (?)")
cql.execute(insert, [{tuple([8, 9, 7]): 1}])
for row in cql.execute(f"SELECT * from {table1}"):
k = row.k
print(k)
if isinstance(k, OrderedMapSerializedKey):
print(k._index)
print(list(k.items())) # This line throws when run on Scylla, but works fine on Cassandra
```
The test has a nested frozen collection - a map of sets. When run against Cassandra this test works, but when run against Scylla, the `k.items()` call throws. The reason is very subtle: It appears that the Python driver keeps the frozen map keys - each itself is a set - serialized in the way it got them from the server. The items() function appears to do a wasteful back-and-forth conversion - it deserializes each key (resulting in a SortedSet object) and then serializes it again to look it up in the map. Somehow during these conversions, the driver re-sorts the elements, and it fails to look it up in the map. Concretely, the serialized key stored in the map is the wrongly sorted (note \0x08, \t, 0x07 - which means 8, 9, 7):
```
\x00\x00\x00\x03\x00\x00\x00\x04\x00\x00\x00\x08\x00\x00\x00\x04\x00\x00\x00\t\x00\x00\x00\x04\x00\x00\x00\x07
```
but the key the code looks up (and fails) is the sorted one (note \0x07, \x08, \t - meaning 7, 8, 9):
```
\x00\x00\x00\x03\x00\x00\x00\x04\x00\x00\x00\x07\x00\x00\x00\x04\x00\x00\x00\x08\x00\x00\x00\x04\x00\x00\x00\t
```
The test passes if instead of `tuple([8, 9, 7])` we pass `tuple([7, 8, 9])` to the prepared statement!
The test also passes if instead of prepared statement, we use an inline statement. Both commands below work the same:
```
cql.execute("INSERT INTO " + table1 + " (k) VALUES ({{7, 8, 9}: 1})")
cql.execute("INSERT INTO " + table1 + " (k) VALUES ({{8, 9, 7}: 1})")
```
Note that this test appears very contrived, but it is actually a greatly simplified version of a real test I tried to run (translated, perhaps not very well, from a Java test from Cassandra) which failed on Scylla, and this is a simplified example showing why. But I will try to create an even simpler test which only needs a `frozen<set>` without nesting. | True | Frozen set may be created out-of-order via a prepared statement - In Scylla, "set" collections are sorted - by the element type's natural order.
Although this is not clearly documented as far as I can tell (?), clients may assume that this the case also for a **frozen** set, for example used as a partition key.
It appears that Scylla can forget to sort the frozen set when inserted using a prepared statement, although does sort it as expected when inserted inline in the statement. It appears that Cassandra correctly sorts the frozen set also for prepared statement.
Here is one subtle and elaborate test case which breaks using a Python driver like an ordinary client. Take a look at this test code:
```python
@pytest.fixture(scope="session")
def table1(cql, test_keyspace):
table = test_keyspace + "." + unique_name()
cql.execute(f"CREATE TABLE {table} (k frozen<map<set<int>, int>> PRIMARY KEY)")
yield table
cql.execute("DROP TABLE " + table)
def test_broken(cql, table1):
insert = cql.prepare(f"INSERT INTO {table1} (k) VALUES (?)")
cql.execute(insert, [{tuple([8, 9, 7]): 1}])
for row in cql.execute(f"SELECT * from {table1}"):
k = row.k
print(k)
if isinstance(k, OrderedMapSerializedKey):
print(k._index)
print(list(k.items())) # This line throws when run on Scylla, but works fine on Cassandra
```
The test has a nested frozen collection - a map of sets. When run against Cassandra this test works, but when run against Scylla, the `k.items()` call throws. The reason is very subtle: It appears that the Python driver keeps the frozen map keys - each itself is a set - serialized in the way it got them from the server. The items() function appears to do a wasteful back-and-forth conversion - it deserializes each key (resulting in a SortedSet object) and then serializes it again to look it up in the map. Somehow during these conversions, the driver re-sorts the elements, and it fails to look it up in the map. Concretely, the serialized key stored in the map is the wrongly sorted (note \0x08, \t, 0x07 - which means 8, 9, 7):
```
\x00\x00\x00\x03\x00\x00\x00\x04\x00\x00\x00\x08\x00\x00\x00\x04\x00\x00\x00\t\x00\x00\x00\x04\x00\x00\x00\x07
```
but the key the code looks up (and fails) is the sorted one (note \0x07, \x08, \t - meaning 7, 8, 9):
```
\x00\x00\x00\x03\x00\x00\x00\x04\x00\x00\x00\x07\x00\x00\x00\x04\x00\x00\x00\x08\x00\x00\x00\x04\x00\x00\x00\t
```
The test passes if instead of `tuple([8, 9, 7])` we pass `tuple([7, 8, 9])` to the prepared statement!
The test also passes if instead of prepared statement, we use an inline statement. Both commands below work the same:
```
cql.execute("INSERT INTO " + table1 + " (k) VALUES ({{7, 8, 9}: 1})")
cql.execute("INSERT INTO " + table1 + " (k) VALUES ({{8, 9, 7}: 1})")
```
Note that this test appears very contrived, but it is actually a greatly simplified version of a real test I tried to run (translated, perhaps not very well, from a Java test from Cassandra) which failed on Scylla, and this is a simplified example showing why. But I will try to create an even simpler test which only needs a `frozen<set>` without nesting. | comp | frozen set may be created out of order via a prepared statement in scylla set collections are sorted by the element type s natural order although this is not clearly documented as far as i can tell clients may assume that this the case also for a frozen set for example used as a partition key it appears that scylla can forget to sort the frozen set when inserted using a prepared statement although does sort it as expected when inserted inline in the statement it appears that cassandra correctly sorts the frozen set also for prepared statement here is one subtle and elaborate test case which breaks using a python driver like an ordinary client take a look at this test code python pytest fixture scope session def cql test keyspace table test keyspace unique name cql execute f create table table k frozen int primary key yield table cql execute drop table table def test broken cql insert cql prepare f insert into k values cql execute insert for row in cql execute f select from k row k print k if isinstance k orderedmapserializedkey print k index print list k items this line throws when run on scylla but works fine on cassandra the test has a nested frozen collection a map of sets when run against cassandra this test works but when run against scylla the k items call throws the reason is very subtle it appears that the python driver keeps the frozen map keys each itself is a set serialized in the way it got them from the server the items function appears to do a wasteful back and forth conversion it deserializes each key resulting in a sortedset object and then serializes it again to look it up in the map somehow during these conversions the driver re sorts the elements and it fails to look it up in the map concretely the serialized key stored in the map is the wrongly sorted note t which means t but the key the code looks up and fails is the sorted one note t meaning t the test passes if instead of tuple we pass tuple to the prepared statement the test also passes if instead of prepared statement we use an inline statement both commands below work the same cql execute insert into k values cql execute insert into k values note that this test appears very contrived but it is actually a greatly simplified version of a real test i tried to run translated perhaps not very well from a java test from cassandra which failed on scylla and this is a simplified example showing why but i will try to create an even simpler test which only needs a frozen without nesting | 1 |
4,183 | 4,958,486,721 | IssuesEvent | 2016-12-02 09:56:57 | w3c/html | https://api.github.com/repos/w3c/html | closed | Get rid of cross domain ressources and requests | Needs incubation security | For security, privacy and efficiency reasons cross domain requests should be phased out from html.
Reason for this:
Modern webpages include various resources from all over the internet instead of serving the content from a domain local URL. This helps with XSS, CSRF, script injection de-anonymisation, user tracking etc.
For a more secure web this bad habit should be discouraged or better be abolished in the not too distant future.
| True | Get rid of cross domain ressources and requests - For security, privacy and efficiency reasons cross domain requests should be phased out from html.
Reason for this:
Modern webpages include various resources from all over the internet instead of serving the content from a domain local URL. This helps with XSS, CSRF, script injection de-anonymisation, user tracking etc.
For a more secure web this bad habit should be discouraged or better be abolished in the not too distant future.
| non_comp | get rid of cross domain ressources and requests for security privacy and efficiency reasons cross domain requests should be phased out from html reason for this modern webpages include various resources from all over the internet instead of serving the content from a domain local url this helps with xss csrf script injection de anonymisation user tracking etc for a more secure web this bad habit should be discouraged or better be abolished in the not too distant future | 0 |
191,866 | 22,215,857,933 | IssuesEvent | 2022-06-08 01:30:47 | Nivaskumark/kernel_v4.1.15 | https://api.github.com/repos/Nivaskumark/kernel_v4.1.15 | reopened | CVE-2022-22764 (High) detected in linuxlinux-4.6 | security vulnerability | ## CVE-2022-22764 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.6</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Nivaskumark/kernel_v4.1.15/commit/00db4e8795bcbec692fb60b19160bdd763ad42e3">00db4e8795bcbec692fb60b19160bdd763ad42e3</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Mozilla developers Paul Adenot and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 96 and Firefox ESR 91.5. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.
<p>Publish Date: 2022-01-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22764>CVE-2022-22764</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: High
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2022-22764">https://nvd.nist.gov/vuln/detail/CVE-2022-22764</a></p>
<p>Release Date: 2022-01-07</p>
<p>Fix Resolution: linux-libc-headers - 5.14;linux-yocto - 5.4.20+gitAUTOINC+c11911d4d1_f4d7dbafb1,4.8.26+gitAUTOINC+1c60e003c7_27efc3ba68</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-22764 (High) detected in linuxlinux-4.6 - ## CVE-2022-22764 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.6</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Nivaskumark/kernel_v4.1.15/commit/00db4e8795bcbec692fb60b19160bdd763ad42e3">00db4e8795bcbec692fb60b19160bdd763ad42e3</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Mozilla developers Paul Adenot and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 96 and Firefox ESR 91.5. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.
<p>Publish Date: 2022-01-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22764>CVE-2022-22764</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: High
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2022-22764">https://nvd.nist.gov/vuln/detail/CVE-2022-22764</a></p>
<p>Release Date: 2022-01-07</p>
<p>Fix Resolution: linux-libc-headers - 5.14;linux-yocto - 5.4.20+gitAUTOINC+c11911d4d1_f4d7dbafb1,4.8.26+gitAUTOINC+1c60e003c7_27efc3ba68</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_comp | cve high detected in linuxlinux cve high severity vulnerability vulnerable library linuxlinux the linux kernel library home page a href found in head commit a href found in base branch master vulnerable source files vulnerability details mozilla developers paul adenot and the mozilla fuzzing team reported memory safety bugs present in firefox and firefox esr some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction required 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 linux libc headers linux yocto gitautoinc gitautoinc step up your open source security game with whitesource | 0 |
237,376 | 26,084,105,293 | IssuesEvent | 2022-12-25 21:26:17 | MValle21/oathkeeper | https://api.github.com/repos/MValle21/oathkeeper | opened | CVE-2022-46175 (High) detected in json5-2.1.3.tgz, json5-1.0.1.tgz | security vulnerability | ## CVE-2022-46175 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>json5-2.1.3.tgz</b>, <b>json5-1.0.1.tgz</b></p></summary>
<p>
<details><summary><b>json5-2.1.3.tgz</b></p></summary>
<p>JSON for humans.</p>
<p>Library home page: <a href="https://registry.npmjs.org/json5/-/json5-2.1.3.tgz">https://registry.npmjs.org/json5/-/json5-2.1.3.tgz</a></p>
<p>Path to dependency file: /docs/package.json</p>
<p>Path to vulnerable library: /docs/node_modules/json5/package.json</p>
<p>
Dependency Hierarchy:
- core-2.0.0-alpha.415a7973f.tgz (Root Library)
- core-7.12.9.tgz
- :x: **json5-2.1.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>json5-1.0.1.tgz</b></p></summary>
<p>JSON for humans.</p>
<p>Library home page: <a href="https://registry.npmjs.org/json5/-/json5-1.0.1.tgz">https://registry.npmjs.org/json5/-/json5-1.0.1.tgz</a></p>
<p>Path to dependency file: /docs/package.json</p>
<p>Path to vulnerable library: /docs/node_modules/react-dev-utils/node_modules/json5/package.json,/docs/node_modules/loader-utils/node_modules/json5/package.json</p>
<p>
Dependency Hierarchy:
- core-2.0.0-alpha.415a7973f.tgz (Root Library)
- react-dev-utils-10.2.1.tgz
- loader-utils-1.2.3.tgz
- :x: **json5-1.0.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/MValle21/oathkeeper/commit/43c00a05bdb772edb5194a57f42ee834b37f3774">43c00a05bdb772edb5194a57f42ee834b37f3774</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
JSON5 is an extension to the popular JSON file format that aims to be easier to write and maintain by hand (e.g. for config files). The `parse` method of the JSON5 library before and including version `2.2.1` does not restrict parsing of keys named `__proto__`, allowing specially crafted strings to pollute the prototype of the resulting object. This vulnerability pollutes the prototype of the object returned by `JSON5.parse` and not the global Object prototype, which is the commonly understood definition of Prototype Pollution. However, polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations. This vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from `JSON5.parse`. The actual impact will depend on how applications utilize the returned object and how they filter unwanted keys, but could include denial of service, cross-site scripting, elevation of privilege, and in extreme cases, remote code execution. `JSON5.parse` should restrict parsing of `__proto__` keys when parsing JSON strings to objects. As a point of reference, the `JSON.parse` method included in JavaScript ignores `__proto__` keys. Simply changing `JSON5.parse` to `JSON.parse` in the examples above mitigates this vulnerability. This vulnerability is patched in json5 version 2.2.2 and later.
<p>Publish Date: 2022-12-24
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-46175>CVE-2022-46175</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: Low
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-46175">https://www.cve.org/CVERecord?id=CVE-2022-46175</a></p>
<p>Release Date: 2022-12-24</p>
<p>Fix Resolution: json5 - 2.2.2</p>
</p>
</details>
<p></p>
| True | CVE-2022-46175 (High) detected in json5-2.1.3.tgz, json5-1.0.1.tgz - ## CVE-2022-46175 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>json5-2.1.3.tgz</b>, <b>json5-1.0.1.tgz</b></p></summary>
<p>
<details><summary><b>json5-2.1.3.tgz</b></p></summary>
<p>JSON for humans.</p>
<p>Library home page: <a href="https://registry.npmjs.org/json5/-/json5-2.1.3.tgz">https://registry.npmjs.org/json5/-/json5-2.1.3.tgz</a></p>
<p>Path to dependency file: /docs/package.json</p>
<p>Path to vulnerable library: /docs/node_modules/json5/package.json</p>
<p>
Dependency Hierarchy:
- core-2.0.0-alpha.415a7973f.tgz (Root Library)
- core-7.12.9.tgz
- :x: **json5-2.1.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>json5-1.0.1.tgz</b></p></summary>
<p>JSON for humans.</p>
<p>Library home page: <a href="https://registry.npmjs.org/json5/-/json5-1.0.1.tgz">https://registry.npmjs.org/json5/-/json5-1.0.1.tgz</a></p>
<p>Path to dependency file: /docs/package.json</p>
<p>Path to vulnerable library: /docs/node_modules/react-dev-utils/node_modules/json5/package.json,/docs/node_modules/loader-utils/node_modules/json5/package.json</p>
<p>
Dependency Hierarchy:
- core-2.0.0-alpha.415a7973f.tgz (Root Library)
- react-dev-utils-10.2.1.tgz
- loader-utils-1.2.3.tgz
- :x: **json5-1.0.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/MValle21/oathkeeper/commit/43c00a05bdb772edb5194a57f42ee834b37f3774">43c00a05bdb772edb5194a57f42ee834b37f3774</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
JSON5 is an extension to the popular JSON file format that aims to be easier to write and maintain by hand (e.g. for config files). The `parse` method of the JSON5 library before and including version `2.2.1` does not restrict parsing of keys named `__proto__`, allowing specially crafted strings to pollute the prototype of the resulting object. This vulnerability pollutes the prototype of the object returned by `JSON5.parse` and not the global Object prototype, which is the commonly understood definition of Prototype Pollution. However, polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations. This vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from `JSON5.parse`. The actual impact will depend on how applications utilize the returned object and how they filter unwanted keys, but could include denial of service, cross-site scripting, elevation of privilege, and in extreme cases, remote code execution. `JSON5.parse` should restrict parsing of `__proto__` keys when parsing JSON strings to objects. As a point of reference, the `JSON.parse` method included in JavaScript ignores `__proto__` keys. Simply changing `JSON5.parse` to `JSON.parse` in the examples above mitigates this vulnerability. This vulnerability is patched in json5 version 2.2.2 and later.
<p>Publish Date: 2022-12-24
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-46175>CVE-2022-46175</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: Low
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-46175">https://www.cve.org/CVERecord?id=CVE-2022-46175</a></p>
<p>Release Date: 2022-12-24</p>
<p>Fix Resolution: json5 - 2.2.2</p>
</p>
</details>
<p></p>
| non_comp | cve high detected in tgz tgz cve high severity vulnerability vulnerable libraries tgz tgz tgz json for humans library home page a href path to dependency file docs package json path to vulnerable library docs node modules package json dependency hierarchy core alpha tgz root library core tgz x tgz vulnerable library tgz json for humans library home page a href path to dependency file docs package json path to vulnerable library docs node modules react dev utils node modules package json docs node modules loader utils node modules package json dependency hierarchy core alpha tgz root library react dev utils tgz loader utils tgz x tgz vulnerable library found in head commit a href found in base branch master vulnerability details is an extension to the popular json file format that aims to be easier to write and maintain by hand e g for config files the parse method of the library before and including version does not restrict parsing of keys named proto allowing specially crafted strings to pollute the prototype of the resulting object this vulnerability pollutes the prototype of the object returned by parse and not the global object prototype which is the commonly understood definition of prototype pollution however polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations this vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from parse the actual impact will depend on how applications utilize the returned object and how they filter unwanted keys but could include denial of service cross site scripting elevation of privilege and in extreme cases remote code execution parse should restrict parsing of proto keys when parsing json strings to objects as a point of reference the json parse method included in javascript ignores proto keys simply changing parse to json parse in the examples above mitigates this vulnerability this vulnerability is patched in version and later publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact low availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution | 0 |
16,481 | 22,304,514,522 | IssuesEvent | 2022-06-13 11:50:48 | hanubeki/dake | https://api.github.com/repos/hanubeki/dake | closed | Added mines not colored as additions | incompatibility 5.2 | No black border, they are still white regardless if they are addition note or not.
| True | Added mines not colored as additions - No black border, they are still white regardless if they are addition note or not.
| comp | added mines not colored as additions no black border they are still white regardless if they are addition note or not | 1 |
218,029 | 7,330,287,442 | IssuesEvent | 2018-03-05 09:25:35 | geosolutions-it/MapStore2 | https://api.github.com/repos/geosolutions-it/MapStore2 | opened | Measure tool, initial mispositioning of tooltip while drawing | LeafLetJS Priority: Medium bug | ### Description
When you start drawing something the tooltip starts in the top left corner
### In case of Bug (otherwise remove this paragraph)
*Browser Affected*
(use this site: https://www.whatsmybrowser.org/ for non expert users)
- [ ] Internet Explorer
- [x] Chrome 64.0.3282.186
- [ ] Firefox
- [ ] Safari
*Browser Version Affected*
*Steps to reproduce*
- open new map with leaflet
- open measure tool
- choose any tool
*Expected Result*
The tool selected gets enabled and no tooltip is shown in the map
*Current Result*
The tool selected gets enabled and a tooltip appear in the top left corner
### Other useful information (optional):
| 1.0 | Measure tool, initial mispositioning of tooltip while drawing - ### Description
When you start drawing something the tooltip starts in the top left corner
### In case of Bug (otherwise remove this paragraph)
*Browser Affected*
(use this site: https://www.whatsmybrowser.org/ for non expert users)
- [ ] Internet Explorer
- [x] Chrome 64.0.3282.186
- [ ] Firefox
- [ ] Safari
*Browser Version Affected*
*Steps to reproduce*
- open new map with leaflet
- open measure tool
- choose any tool
*Expected Result*
The tool selected gets enabled and no tooltip is shown in the map
*Current Result*
The tool selected gets enabled and a tooltip appear in the top left corner
### Other useful information (optional):
| non_comp | measure tool initial mispositioning of tooltip while drawing description when you start drawing something the tooltip starts in the top left corner in case of bug otherwise remove this paragraph browser affected use this site for non expert users internet explorer chrome firefox safari browser version affected steps to reproduce open new map with leaflet open measure tool choose any tool expected result the tool selected gets enabled and no tooltip is shown in the map current result the tool selected gets enabled and a tooltip appear in the top left corner other useful information optional | 0 |
66,534 | 14,788,917,207 | IssuesEvent | 2021-01-12 09:52:23 | andygonzalez2010/store | https://api.github.com/repos/andygonzalez2010/store | opened | CVE-2019-16303 (High) detected in generator-jhipster-6.0.1.tgz | security vulnerability | ## CVE-2019-16303 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>generator-jhipster-6.0.1.tgz</b></p></summary>
<p>Spring Boot + Angular/React in one handy generator</p>
<p>Library home page: <a href="https://registry.npmjs.org/generator-jhipster/-/generator-jhipster-6.0.1.tgz">https://registry.npmjs.org/generator-jhipster/-/generator-jhipster-6.0.1.tgz</a></p>
<p>Path to dependency file: store/package.json</p>
<p>Path to vulnerable library: store/node_modules/generator-jhipster/package.json</p>
<p>
Dependency Hierarchy:
- :x: **generator-jhipster-6.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/andygonzalez2010/store/commit/84990bf9d6b7cdf76851573df077d70766b08e91">84990bf9d6b7cdf76851573df077d70766b08e91</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A class generated by the Generator in JHipster before 6.3.0 and JHipster Kotlin through 1.1.0 produces code that uses an insecure source of randomness (apache.commons.lang3 RandomStringUtils). This allows an attacker (if able to obtain their own password reset URL) to compute the value for all other password resets for other accounts, thus allowing privilege escalation or account takeover.
<p>Publish Date: 2019-09-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16303>CVE-2019-16303</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16303">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16303</a></p>
<p>Release Date: 2019-09-14</p>
<p>Fix Resolution: 6.3.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2019-16303 (High) detected in generator-jhipster-6.0.1.tgz - ## CVE-2019-16303 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>generator-jhipster-6.0.1.tgz</b></p></summary>
<p>Spring Boot + Angular/React in one handy generator</p>
<p>Library home page: <a href="https://registry.npmjs.org/generator-jhipster/-/generator-jhipster-6.0.1.tgz">https://registry.npmjs.org/generator-jhipster/-/generator-jhipster-6.0.1.tgz</a></p>
<p>Path to dependency file: store/package.json</p>
<p>Path to vulnerable library: store/node_modules/generator-jhipster/package.json</p>
<p>
Dependency Hierarchy:
- :x: **generator-jhipster-6.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/andygonzalez2010/store/commit/84990bf9d6b7cdf76851573df077d70766b08e91">84990bf9d6b7cdf76851573df077d70766b08e91</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A class generated by the Generator in JHipster before 6.3.0 and JHipster Kotlin through 1.1.0 produces code that uses an insecure source of randomness (apache.commons.lang3 RandomStringUtils). This allows an attacker (if able to obtain their own password reset URL) to compute the value for all other password resets for other accounts, thus allowing privilege escalation or account takeover.
<p>Publish Date: 2019-09-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16303>CVE-2019-16303</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16303">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16303</a></p>
<p>Release Date: 2019-09-14</p>
<p>Fix Resolution: 6.3.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_comp | cve high detected in generator jhipster tgz cve high severity vulnerability vulnerable library generator jhipster tgz spring boot angular react in one handy generator library home page a href path to dependency file store package json path to vulnerable library store node modules generator jhipster package json dependency hierarchy x generator jhipster tgz vulnerable library found in head commit a href found in base branch master vulnerability details a class generated by the generator in jhipster before and jhipster kotlin through produces code that uses an insecure source of randomness apache commons randomstringutils this allows an attacker if able to obtain their own password reset url to compute the value for all other password resets for other accounts thus allowing privilege escalation or account takeover publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
44,200 | 23,519,903,309 | IssuesEvent | 2022-08-19 04:00:36 | rtCamp/wp-themes-performance-measurement | https://api.github.com/repos/rtCamp/wp-themes-performance-measurement | opened | Performance Report for gridbox theme | performance-report gh-runner | ## THEME: gridbox
- MEASURING TOOL: Lighthouse CI
- LIGHTHOUSE VERSION: 0.9.0
- TIMESTAMP: 2022-08-19T04:00:35
- HTML REPORT ARTIFACTS: https://github.com/rtCamp/wp-themes-performance-measurement/actions/runs/2886953782
> Note: To see full Performance report download artifacts as zip and unzip them to destination folder `.lighthouseci` and use command `npm run lhci open`. | True | Performance Report for gridbox theme - ## THEME: gridbox
- MEASURING TOOL: Lighthouse CI
- LIGHTHOUSE VERSION: 0.9.0
- TIMESTAMP: 2022-08-19T04:00:35
- HTML REPORT ARTIFACTS: https://github.com/rtCamp/wp-themes-performance-measurement/actions/runs/2886953782
> Note: To see full Performance report download artifacts as zip and unzip them to destination folder `.lighthouseci` and use command `npm run lhci open`. | non_comp | performance report for gridbox theme theme gridbox measuring tool lighthouse ci lighthouse version timestamp html report artifacts note to see full performance report download artifacts as zip and unzip them to destination folder lighthouseci and use command npm run lhci open | 0 |
543 | 2,978,551,546 | IssuesEvent | 2015-07-16 07:28:21 | facebook/hhvm | https://api.github.com/repos/facebook/hhvm | closed | mysqli_stmt_bind_result only returning last row from query | php5 incompatibility | ```
if($stmt->num_rows > 0){
//id,body,title,tags,owner,create_date,search_weight,type
$stmt->bind_result($result['id'],$result['body'],$result['title'],$result['tags'],$result['owner'],$result['create_date'],$result['search_weight'],$result['type'],$result['city'],$result['country'],$result['state']);
while($stmt->fetch()){
$data[] = $result;
}
$stmt->close();
}
``` | True | mysqli_stmt_bind_result only returning last row from query - ```
if($stmt->num_rows > 0){
//id,body,title,tags,owner,create_date,search_weight,type
$stmt->bind_result($result['id'],$result['body'],$result['title'],$result['tags'],$result['owner'],$result['create_date'],$result['search_weight'],$result['type'],$result['city'],$result['country'],$result['state']);
while($stmt->fetch()){
$data[] = $result;
}
$stmt->close();
}
``` | comp | mysqli stmt bind result only returning last row from query if stmt num rows id body title tags owner create date search weight type stmt bind result result result result result result result result result result result result while stmt fetch data result stmt close | 1 |
732,184 | 25,247,976,019 | IssuesEvent | 2022-11-15 12:37:46 | vaticle/typedb-studio | https://api.github.com/repos/vaticle/typedb-studio | closed | Shift+End selects to end of file, not end of line | type: bug priority: medium domain: text-editor | ## Description
When doing Shift+End in a tab with multiple lines of queries/text, it will select up until the end of the file instead of up until the end of the line.
Same is true when doing the opposite with Shift+Home.
This doesn't match the standard behavior seen in most/all text editors.
I'm wondering if that's a WIndows only thing.
## Environment
1. TypeDB version: 2.10
2. OS of TypeDB server: Windows 11
3. Studio version: 2.10-alpha-4
4. OS of Studio: Windows 11
5. Other environment details:
## Reproducible Steps
Steps to create the smallest reproducible scenario:
- Enter two lines of text in the editor
- Place your cursor at the beginning of the first line
- Hit Shift-End
## Expected Output
Select text up until the end of the current line.
## Actual Output
All text is selected.
## Additional information
| 1.0 | Shift+End selects to end of file, not end of line - ## Description
When doing Shift+End in a tab with multiple lines of queries/text, it will select up until the end of the file instead of up until the end of the line.
Same is true when doing the opposite with Shift+Home.
This doesn't match the standard behavior seen in most/all text editors.
I'm wondering if that's a WIndows only thing.
## Environment
1. TypeDB version: 2.10
2. OS of TypeDB server: Windows 11
3. Studio version: 2.10-alpha-4
4. OS of Studio: Windows 11
5. Other environment details:
## Reproducible Steps
Steps to create the smallest reproducible scenario:
- Enter two lines of text in the editor
- Place your cursor at the beginning of the first line
- Hit Shift-End
## Expected Output
Select text up until the end of the current line.
## Actual Output
All text is selected.
## Additional information
| non_comp | shift end selects to end of file not end of line description when doing shift end in a tab with multiple lines of queries text it will select up until the end of the file instead of up until the end of the line same is true when doing the opposite with shift home this doesn t match the standard behavior seen in most all text editors i m wondering if that s a windows only thing environment typedb version os of typedb server windows studio version alpha os of studio windows other environment details reproducible steps steps to create the smallest reproducible scenario enter two lines of text in the editor place your cursor at the beginning of the first line hit shift end expected output select text up until the end of the current line actual output all text is selected additional information | 0 |
708,680 | 24,349,794,753 | IssuesEvent | 2022-10-02 20:01:04 | Roguelike-Celebration/azure-mud | https://api.github.com/repos/Roguelike-Celebration/azure-mud | closed | "Make speaker" endpoint should actually work | do for 2022 high priority | It hits a 404 not found despite theoretically existing | 1.0 | "Make speaker" endpoint should actually work - It hits a 404 not found despite theoretically existing | non_comp | make speaker endpoint should actually work it hits a not found despite theoretically existing | 0 |
16,223 | 2,612,762,569 | IssuesEvent | 2015-02-27 16:33:19 | crowell/modpagespeed | https://api.github.com/repos/crowell/modpagespeed | closed | CSS Filter: Incorrectly minification not-quoted font-family names with spaces | bug imported Priority-High | _From [[email protected]](https://code.google.com/u/100124221215842728449/) on November 03, 2010 18:24:07_
this style:
font-family: trebuchet ms;
is being minified to:
font-family: trebuchetms;
while it should be:
font-family: "trebuchet ms";
or remain untouched
_Original issue: http://code.google.com/p/modpagespeed/issues/detail?id=5_ | 1.0 | CSS Filter: Incorrectly minification not-quoted font-family names with spaces - _From [[email protected]](https://code.google.com/u/100124221215842728449/) on November 03, 2010 18:24:07_
this style:
font-family: trebuchet ms;
is being minified to:
font-family: trebuchetms;
while it should be:
font-family: "trebuchet ms";
or remain untouched
_Original issue: http://code.google.com/p/modpagespeed/issues/detail?id=5_ | non_comp | css filter incorrectly minification not quoted font family names with spaces from on november this style font family trebuchet ms is being minified to font family trebuchetms while it should be font family trebuchet ms or remain untouched original issue | 0 |
16,779 | 23,138,857,101 | IssuesEvent | 2022-07-28 16:27:38 | NEZNAMY/TAB | https://api.github.com/repos/NEZNAMY/TAB | closed | Magma DO NOT work | Wontfix Compatibility Error | ### Server version
Magma 1.18.2
### TAB version
3.1.2
### Stack trace
[22:11:54] [Server thread/INFO] [/]: [TAB] Server version: 1.18.2 (v1_18_R2)
[22:11:54] [Server thread/INFO] [/]: [TAB] Your server version is marked as compatible, but a compatibility issue was found. Please report the error below (include your server version & fork too)
[22:11:54] [Server thread/ERROR] [me.ne.ta.pl.bu.Main/]: [TAB]
java.lang.ClassNotFoundException: No class found with possible names [net.minecraft.EnumChatFormat, EnumChatFormat]
at me.neznamy.tab.platforms.bukkit.nms.NMSStorage.getNMSClass(NMSStorage.java:456) ~[?:?] {}
at me.neznamy.tab.platforms.bukkit.nms.NMSStorage.<init>(NMSStorage.java:38) ~[?:?] {}
at me.neznamy.tab.platforms.bukkit.Main.isVersionSupported(Main.java:78) ~[?:?] {}
at me.neznamy.tab.platforms.bukkit.Main.onEnable(Main.java:32) ~[?:?] {}
at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:264) ~[forge-1.18.2-40.1.54-universal.jar%2365!/:?] {re:classloading}
at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:342) ~[forge-1.18.2-40.1.54-universal.jar%2365!/:?] {re:classloading}
at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:480) ~[forge-1.18.2-40.1.54-universal.jar%2365!/:?] {re:classloading}
at org.bukkit.craftbukkit.v1_18_R2.CraftServer.enablePlugin(CraftServer.java:434) ~[forge-1.18.2-40.1.54-universal.jar%2365!/:?] {re:classloading}
at org.bukkit.craftbukkit.v1_18_R2.CraftServer.enablePlugins(CraftServer.java:348) ~[forge-1.18.2-40.1.54-universal.jar%2365!/:?] {re:classloading}
at net.minecraft.server.MinecraftServer.m_129815_(MinecraftServer.java:448) ~[server-1.18.2-20220404.173914-srg.jar%2360!/:?] {re:classloading,pl:accesstransformer:B}
at net.minecraft.server.MinecraftServer.loadLevel(MinecraftServer.java:357) ~[server-1.18.2-20220404.173914-srg.jar%2360!/:?] {re:classloading,pl:accesstransformer:B}
at net.minecraft.server.dedicated.DedicatedServer.m_7038_(DedicatedServer.java:244) ~[server-1.18.2-20220404.173914-srg.jar%2360!/:?] {re:classloading,pl:accesstransformer:B}
at net.minecraft.server.MinecraftServer.m_130011_(MinecraftServer.java:757) ~[server-1.18.2-20220404.173914-srg.jar%2360!/:?] {re:classloading,pl:accesstransformer:B}
at net.minecraft.server.MinecraftServer.m_177918_(MinecraftServer.java:253) ~[server-1.18.2-20220404.173914-srg.jar%2360!/:?] {re:classloading,pl:accesstransformer:B}
at java.lang.Thread.run(Thread.java:833) [?:?] {}
[22:11:54] [Server thread/INFO] [me.ne.ta.pl.bu.Main/]: [TAB] Disabling TAB v3.1.2
### Steps to reproduce (if known)
Just launch server
### Additional info
Using Magma Hybrid Core. When starting server (1.18.2) it just enables and disables plugin.
I tried some past versions that support 1.18.2, they have same problem
### Checklist
- [X] I am running latest version of the plugin
- [X] I have included a paste of the error
- [X] I have read the Compatibility wiki page and am not trying to run the plugin on an unsupported server version / platform | True | Magma DO NOT work - ### Server version
Magma 1.18.2
### TAB version
3.1.2
### Stack trace
[22:11:54] [Server thread/INFO] [/]: [TAB] Server version: 1.18.2 (v1_18_R2)
[22:11:54] [Server thread/INFO] [/]: [TAB] Your server version is marked as compatible, but a compatibility issue was found. Please report the error below (include your server version & fork too)
[22:11:54] [Server thread/ERROR] [me.ne.ta.pl.bu.Main/]: [TAB]
java.lang.ClassNotFoundException: No class found with possible names [net.minecraft.EnumChatFormat, EnumChatFormat]
at me.neznamy.tab.platforms.bukkit.nms.NMSStorage.getNMSClass(NMSStorage.java:456) ~[?:?] {}
at me.neznamy.tab.platforms.bukkit.nms.NMSStorage.<init>(NMSStorage.java:38) ~[?:?] {}
at me.neznamy.tab.platforms.bukkit.Main.isVersionSupported(Main.java:78) ~[?:?] {}
at me.neznamy.tab.platforms.bukkit.Main.onEnable(Main.java:32) ~[?:?] {}
at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:264) ~[forge-1.18.2-40.1.54-universal.jar%2365!/:?] {re:classloading}
at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:342) ~[forge-1.18.2-40.1.54-universal.jar%2365!/:?] {re:classloading}
at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:480) ~[forge-1.18.2-40.1.54-universal.jar%2365!/:?] {re:classloading}
at org.bukkit.craftbukkit.v1_18_R2.CraftServer.enablePlugin(CraftServer.java:434) ~[forge-1.18.2-40.1.54-universal.jar%2365!/:?] {re:classloading}
at org.bukkit.craftbukkit.v1_18_R2.CraftServer.enablePlugins(CraftServer.java:348) ~[forge-1.18.2-40.1.54-universal.jar%2365!/:?] {re:classloading}
at net.minecraft.server.MinecraftServer.m_129815_(MinecraftServer.java:448) ~[server-1.18.2-20220404.173914-srg.jar%2360!/:?] {re:classloading,pl:accesstransformer:B}
at net.minecraft.server.MinecraftServer.loadLevel(MinecraftServer.java:357) ~[server-1.18.2-20220404.173914-srg.jar%2360!/:?] {re:classloading,pl:accesstransformer:B}
at net.minecraft.server.dedicated.DedicatedServer.m_7038_(DedicatedServer.java:244) ~[server-1.18.2-20220404.173914-srg.jar%2360!/:?] {re:classloading,pl:accesstransformer:B}
at net.minecraft.server.MinecraftServer.m_130011_(MinecraftServer.java:757) ~[server-1.18.2-20220404.173914-srg.jar%2360!/:?] {re:classloading,pl:accesstransformer:B}
at net.minecraft.server.MinecraftServer.m_177918_(MinecraftServer.java:253) ~[server-1.18.2-20220404.173914-srg.jar%2360!/:?] {re:classloading,pl:accesstransformer:B}
at java.lang.Thread.run(Thread.java:833) [?:?] {}
[22:11:54] [Server thread/INFO] [me.ne.ta.pl.bu.Main/]: [TAB] Disabling TAB v3.1.2
### Steps to reproduce (if known)
Just launch server
### Additional info
Using Magma Hybrid Core. When starting server (1.18.2) it just enables and disables plugin.
I tried some past versions that support 1.18.2, they have same problem
### Checklist
- [X] I am running latest version of the plugin
- [X] I have included a paste of the error
- [X] I have read the Compatibility wiki page and am not trying to run the plugin on an unsupported server version / platform | comp | magma do not work server version magma tab version stack trace server version your server version is marked as compatible but a compatibility issue was found please report the error below include your server version fork too java lang classnotfoundexception no class found with possible names at me neznamy tab platforms bukkit nms nmsstorage getnmsclass nmsstorage java at me neznamy tab platforms bukkit nms nmsstorage nmsstorage java at me neznamy tab platforms bukkit main isversionsupported main java at me neznamy tab platforms bukkit main onenable main java at org bukkit plugin java javaplugin setenabled javaplugin java re classloading at org bukkit plugin java javapluginloader enableplugin javapluginloader java re classloading at org bukkit plugin simplepluginmanager enableplugin simplepluginmanager java re classloading at org bukkit craftbukkit craftserver enableplugin craftserver java re classloading at org bukkit craftbukkit craftserver enableplugins craftserver java re classloading at net minecraft server minecraftserver m minecraftserver java re classloading pl accesstransformer b at net minecraft server minecraftserver loadlevel minecraftserver java re classloading pl accesstransformer b at net minecraft server dedicated dedicatedserver m dedicatedserver java re classloading pl accesstransformer b at net minecraft server minecraftserver m minecraftserver java re classloading pl accesstransformer b at net minecraft server minecraftserver m minecraftserver java re classloading pl accesstransformer b at java lang thread run thread java disabling tab steps to reproduce if known just launch server additional info using magma hybrid core when starting server it just enables and disables plugin i tried some past versions that support they have same problem checklist i am running latest version of the plugin i have included a paste of the error i have read the compatibility wiki page and am not trying to run the plugin on an unsupported server version platform | 1 |
2,165 | 4,927,477,188 | IssuesEvent | 2016-11-26 19:23:36 | csf-dev/CSF.Core | https://api.github.com/repos/csf-dev/CSF.Core | closed | In new repo: Add InMemoryQuery | breaks-compatibility enhancement | Firstly, break `CSF.Data` away to a new repository. Secondly add a new type named `InMemoryQuery`. This will implement `IQuery` backed with an in-memory collection.
This will be an `ICollection` of `Tuple<Type,object,object>` where:
* The `Type` is the item's original type exposed via `GetType` when it was first added.
* The first object is the item's value
* There second object is the item's key value
It will have a method named `Add` which takes two object parameters (an item and it's key value) but returns itself so that calls may be chained.
It will also have a method named `AddMany` which takes a collection of typed objects and a lambda (selecting an instance of those objects) to get the key value. This also returns itself in order to chain calls.
The get/theorise calls will use the passed type in order to filter the big collection by types (anything which is assignable from the desired type), and then will look for a key value match.
The query method will just filter on type (anything assignable) and then apply the query predicate to the remaining objects. | True | In new repo: Add InMemoryQuery - Firstly, break `CSF.Data` away to a new repository. Secondly add a new type named `InMemoryQuery`. This will implement `IQuery` backed with an in-memory collection.
This will be an `ICollection` of `Tuple<Type,object,object>` where:
* The `Type` is the item's original type exposed via `GetType` when it was first added.
* The first object is the item's value
* There second object is the item's key value
It will have a method named `Add` which takes two object parameters (an item and it's key value) but returns itself so that calls may be chained.
It will also have a method named `AddMany` which takes a collection of typed objects and a lambda (selecting an instance of those objects) to get the key value. This also returns itself in order to chain calls.
The get/theorise calls will use the passed type in order to filter the big collection by types (anything which is assignable from the desired type), and then will look for a key value match.
The query method will just filter on type (anything assignable) and then apply the query predicate to the remaining objects. | comp | in new repo add inmemoryquery firstly break csf data away to a new repository secondly add a new type named inmemoryquery this will implement iquery backed with an in memory collection this will be an icollection of tuple where the type is the item s original type exposed via gettype when it was first added the first object is the item s value there second object is the item s key value it will have a method named add which takes two object parameters an item and it s key value but returns itself so that calls may be chained it will also have a method named addmany which takes a collection of typed objects and a lambda selecting an instance of those objects to get the key value this also returns itself in order to chain calls the get theorise calls will use the passed type in order to filter the big collection by types anything which is assignable from the desired type and then will look for a key value match the query method will just filter on type anything assignable and then apply the query predicate to the remaining objects | 1 |
15,949 | 20,995,188,782 | IssuesEvent | 2022-03-29 12:57:51 | spring-projects-experimental/spring-native | https://api.github.com/repos/spring-projects-experimental/spring-native | closed | commandlinerunner-log4j2 fails with GraalVM 22.1 | type: compatibility | ```
openjdk version "17.0.3" 2022-04-19
OpenJDK Runtime Environment GraalVM CE 22.1.0-dev (build 17.0.3+4-jvmci-22.1-b03)
OpenJDK 64-Bit Server VM GraalVM CE 22.1.0-dev (build 17.0.3+4-jvmci-22.1-b03, mixed mode, sharing)
```
```
========================================================================================================================
GraalVM Native Image: Generating 'commandlinerunner-log4j2' (executable)...
========================================================================================================================
[1/7] Initializing... (0,0s @ 0,07GB)
Error: ImageSingletons do not contain key com.oracle.svm.hosted.LinkAtBuildTimeSupport
Error: Use -H:+ReportExceptionStackTraces to print stacktrace of underlying exception
------------------------------------------------------------------------------------------------------------------------
0,1s (6,4% of total time) in 8 GCs | Peak RSS: 0,59GB | CPU load: 5,14
========================================================================================================================
Failed generating 'commandlinerunner-log4j2' after 1,4s.
```
Looks like https://github.com/spring-projects-experimental/spring-native/issues/1546 | True | commandlinerunner-log4j2 fails with GraalVM 22.1 - ```
openjdk version "17.0.3" 2022-04-19
OpenJDK Runtime Environment GraalVM CE 22.1.0-dev (build 17.0.3+4-jvmci-22.1-b03)
OpenJDK 64-Bit Server VM GraalVM CE 22.1.0-dev (build 17.0.3+4-jvmci-22.1-b03, mixed mode, sharing)
```
```
========================================================================================================================
GraalVM Native Image: Generating 'commandlinerunner-log4j2' (executable)...
========================================================================================================================
[1/7] Initializing... (0,0s @ 0,07GB)
Error: ImageSingletons do not contain key com.oracle.svm.hosted.LinkAtBuildTimeSupport
Error: Use -H:+ReportExceptionStackTraces to print stacktrace of underlying exception
------------------------------------------------------------------------------------------------------------------------
0,1s (6,4% of total time) in 8 GCs | Peak RSS: 0,59GB | CPU load: 5,14
========================================================================================================================
Failed generating 'commandlinerunner-log4j2' after 1,4s.
```
Looks like https://github.com/spring-projects-experimental/spring-native/issues/1546 | comp | commandlinerunner fails with graalvm openjdk version openjdk runtime environment graalvm ce dev build jvmci openjdk bit server vm graalvm ce dev build jvmci mixed mode sharing graalvm native image generating commandlinerunner executable initializing error imagesingletons do not contain key com oracle svm hosted linkatbuildtimesupport error use h reportexceptionstacktraces to print stacktrace of underlying exception of total time in gcs peak rss cpu load failed generating commandlinerunner after looks like | 1 |
226,210 | 24,946,724,346 | IssuesEvent | 2022-11-01 01:21:26 | Nivaskumark/G3_kernel_4.19.72 | https://api.github.com/repos/Nivaskumark/G3_kernel_4.19.72 | closed | CVE-2021-45480 (Medium) detected in linuxlinux-4.19.257 - autoclosed | security vulnerability | ## CVE-2021-45480 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.19.257</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Nivaskumark/G3_kernel_4.19.72/commit/ffd4e521bae27768fd4a5f0b6f78bc7799e0feec">ffd4e521bae27768fd4a5f0b6f78bc7799e0feec</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/rds/connection.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/rds/connection.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in the Linux kernel before 5.15.11. There is a memory leak in the __rds_conn_create() function in net/rds/connection.c in a certain combination of circumstances.
<p>Publish Date: 2021-12-24
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-45480>CVE-2021-45480</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45480">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45480</a></p>
<p>Release Date: 2021-12-24</p>
<p>Fix Resolution: v5.15.11</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-45480 (Medium) detected in linuxlinux-4.19.257 - autoclosed - ## CVE-2021-45480 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.19.257</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Nivaskumark/G3_kernel_4.19.72/commit/ffd4e521bae27768fd4a5f0b6f78bc7799e0feec">ffd4e521bae27768fd4a5f0b6f78bc7799e0feec</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/rds/connection.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/rds/connection.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in the Linux kernel before 5.15.11. There is a memory leak in the __rds_conn_create() function in net/rds/connection.c in a certain combination of circumstances.
<p>Publish Date: 2021-12-24
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-45480>CVE-2021-45480</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45480">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45480</a></p>
<p>Release Date: 2021-12-24</p>
<p>Fix Resolution: v5.15.11</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_comp | cve medium detected in linuxlinux autoclosed cve medium severity vulnerability vulnerable library linuxlinux the linux kernel library home page a href found in head commit a href found in base branch master vulnerable source files net rds connection c net rds connection c vulnerability details an issue was discovered in the linux kernel before there is a memory leak in the rds conn create function in net rds connection c in a certain combination of circumstances publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
16,078 | 21,443,649,672 | IssuesEvent | 2022-04-25 02:16:51 | nervosnetwork/godwoken-web3 | https://api.github.com/repos/nervosnetwork/godwoken-web3 | opened | `instant finality` transactions not in filter changes | Not compatible | When I send a transaction to web3, transaction's receipt will available soon because of instant finality.
But when I `eth_getFilterChanges` now, this transaction will not included, it's not submitted to a block. | True | `instant finality` transactions not in filter changes - When I send a transaction to web3, transaction's receipt will available soon because of instant finality.
But when I `eth_getFilterChanges` now, this transaction will not included, it's not submitted to a block. | comp | instant finality transactions not in filter changes when i send a transaction to transaction s receipt will available soon because of instant finality but when i eth getfilterchanges now this transaction will not included it s not submitted to a block | 1 |
18,951 | 26,345,150,638 | IssuesEvent | 2023-01-10 21:18:20 | OpenMDAO/OpenMDAO | https://api.github.com/repos/OpenMDAO/OpenMDAO | opened | Deprecation removal: `assert_rel_error` → `assert_near_equal` | backwards_incompatible | ### Desired capability or behavior.
Removed the deprecated `assert_rel_error` in favor of `assert_near_equal` as of 3.25.0.
### Associated POEM
_No response_ | True | Deprecation removal: `assert_rel_error` → `assert_near_equal` - ### Desired capability or behavior.
Removed the deprecated `assert_rel_error` in favor of `assert_near_equal` as of 3.25.0.
### Associated POEM
_No response_ | comp | deprecation removal assert rel error → assert near equal desired capability or behavior removed the deprecated assert rel error in favor of assert near equal as of associated poem no response | 1 |
19,001 | 26,425,352,131 | IssuesEvent | 2023-01-14 04:38:47 | zer0Kerbal/KeridianDynamics | https://api.github.com/repos/zer0Kerbal/KeridianDynamics | closed | [compatibility] TETRIX tech tree | issue: compatibility/patch contributions-welcome | [compatibility] TETRIX tech tree
In the TETRIX TechTree the
* [ ] OASIS would be a Tier 7 part
* [ ] , same as the MobileVAB
* [ ] CAMPER would be a Tier 5 part
* [ ] The Hitchhiker is a Tier 3 part. | True | [compatibility] TETRIX tech tree - [compatibility] TETRIX tech tree
In the TETRIX TechTree the
* [ ] OASIS would be a Tier 7 part
* [ ] , same as the MobileVAB
* [ ] CAMPER would be a Tier 5 part
* [ ] The Hitchhiker is a Tier 3 part. | comp | tetrix tech tree tetrix tech tree in the tetrix techtree the oasis would be a tier part same as the mobilevab camper would be a tier part the hitchhiker is a tier part | 1 |
207,855 | 15,839,051,132 | IssuesEvent | 2021-04-06 23:54:09 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | roachtest: activerecord failed | C-test-failure O-roachtest O-robot branch-63154 release-blocker | [(roachtest).activerecord failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2853861&tab=buildLog) on [63154@15caa1367f0ecbff409d52bf4156a5086a2a3fbd](https://github.com/cockroachdb/cockroach/commits/15caa1367f0ecbff409d52bf4156a5086a2a3fbd):
```
The test failed on branch=63154, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/activerecord/run_1
orm_helpers.go:228,orm_helpers.go:154,activerecord.go:227,activerecord.go:239,test_runner.go:768:
Tests run on Cockroach v21.1.0-alpha.3-2101-g15caa1367f
Tests run against activerecord 6.1
6587 Total Tests Run
6585 tests passed
2 tests failed
17 tests skipped
0 tests ignored
0 tests passed unexpectedly
1 test failed unexpectedly
0 tests expected failed but skipped
0 tests expected failed but not run
---
--- PASS: SerializedAttributeTest#test_unexpected_serialized_type (expected)
--- FAIL: InsertAllTest#test_upsert_all_works_with_partitioned_indexes (unexpected)
For a full summary look at the activerecord artifacts
An updated blocklist (activeRecordBlockList21_1) is available in the artifacts' activerecord log
```
<details><summary>More</summary><p>
Artifacts: [/activerecord](https://teamcity.cockroachdb.com/viewLog.html?buildId=2853861&tab=artifacts#/activerecord)
Related:
- #61970 roachtest: activerecord failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-release-20.2](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-release-20.2)
- #61935 roachtest: activerecord failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-release-21.1](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-release-21.1)
- #61931 roachtest: activerecord failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-master](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-master)
- #53730 roachtest: activerecord failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-release-20.1](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-release-20.1)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Aactiverecord.%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>
| 2.0 | roachtest: activerecord failed - [(roachtest).activerecord failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2853861&tab=buildLog) on [63154@15caa1367f0ecbff409d52bf4156a5086a2a3fbd](https://github.com/cockroachdb/cockroach/commits/15caa1367f0ecbff409d52bf4156a5086a2a3fbd):
```
The test failed on branch=63154, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/activerecord/run_1
orm_helpers.go:228,orm_helpers.go:154,activerecord.go:227,activerecord.go:239,test_runner.go:768:
Tests run on Cockroach v21.1.0-alpha.3-2101-g15caa1367f
Tests run against activerecord 6.1
6587 Total Tests Run
6585 tests passed
2 tests failed
17 tests skipped
0 tests ignored
0 tests passed unexpectedly
1 test failed unexpectedly
0 tests expected failed but skipped
0 tests expected failed but not run
---
--- PASS: SerializedAttributeTest#test_unexpected_serialized_type (expected)
--- FAIL: InsertAllTest#test_upsert_all_works_with_partitioned_indexes (unexpected)
For a full summary look at the activerecord artifacts
An updated blocklist (activeRecordBlockList21_1) is available in the artifacts' activerecord log
```
<details><summary>More</summary><p>
Artifacts: [/activerecord](https://teamcity.cockroachdb.com/viewLog.html?buildId=2853861&tab=artifacts#/activerecord)
Related:
- #61970 roachtest: activerecord failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-release-20.2](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-release-20.2)
- #61935 roachtest: activerecord failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-release-21.1](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-release-21.1)
- #61931 roachtest: activerecord failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-master](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-master)
- #53730 roachtest: activerecord failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-release-20.1](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-release-20.1)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Aactiverecord.%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_comp | roachtest activerecord failed on the test failed on branch cloud gce test artifacts and logs in home agent work go src github com cockroachdb cockroach artifacts activerecord run orm helpers go orm helpers go activerecord go activerecord go test runner go tests run on cockroach alpha tests run against activerecord total tests run tests passed tests failed tests skipped tests ignored tests passed unexpectedly test failed unexpectedly tests expected failed but skipped tests expected failed but not run pass serializedattributetest test unexpected serialized type expected fail insertalltest test upsert all works with partitioned indexes unexpected for a full summary look at the activerecord artifacts an updated blocklist is available in the artifacts activerecord log more artifacts related roachtest activerecord failed roachtest activerecord failed roachtest activerecord failed roachtest activerecord failed powered by | 0 |
2,093 | 4,820,325,697 | IssuesEvent | 2016-11-04 22:22:52 | Polymer/polymer | https://api.github.com/repos/Polymer/polymer | closed | Touch devices: No mouse events on elements for 2.5s when overlaid by elements using gestures | 1.x 1.x-2.x compatibility bug p1 | ### Description
On touch devices, when a `<button>` is covered by a Polymer element that uses gestures (e.g. one with a `down` listener) and the Polymer element is moved, the `<button>` does not receive mouse events for 2.5s since `POINTERSTATE.mouse.target` is not cleared.
#### Live Demo
http://jsbin.com/runayep/edit?html,output
#### Steps to Reproduce
1. On a touch device (or mobile emulation in Chrome), tap the button to open the drawer
2. Tap the button to close the drawer
3. Immediately, tap the button to open the drawer again
#### Expected Results
The drawer opens
#### Actual Results
The drawer does not open, but clicking the button after 2.5s does.
### Browsers Affected
All
### Versions
- Polymer: v1.7.0
| True | Touch devices: No mouse events on elements for 2.5s when overlaid by elements using gestures - ### Description
On touch devices, when a `<button>` is covered by a Polymer element that uses gestures (e.g. one with a `down` listener) and the Polymer element is moved, the `<button>` does not receive mouse events for 2.5s since `POINTERSTATE.mouse.target` is not cleared.
#### Live Demo
http://jsbin.com/runayep/edit?html,output
#### Steps to Reproduce
1. On a touch device (or mobile emulation in Chrome), tap the button to open the drawer
2. Tap the button to close the drawer
3. Immediately, tap the button to open the drawer again
#### Expected Results
The drawer opens
#### Actual Results
The drawer does not open, but clicking the button after 2.5s does.
### Browsers Affected
All
### Versions
- Polymer: v1.7.0
| comp | touch devices no mouse events on elements for when overlaid by elements using gestures description on touch devices when a is covered by a polymer element that uses gestures e g one with a down listener and the polymer element is moved the does not receive mouse events for since pointerstate mouse target is not cleared live demo steps to reproduce on a touch device or mobile emulation in chrome tap the button to open the drawer tap the button to close the drawer immediately tap the button to open the drawer again expected results the drawer opens actual results the drawer does not open but clicking the button after does browsers affected all versions polymer | 1 |
177,887 | 13,751,825,613 | IssuesEvent | 2020-10-06 13:49:08 | ayumi-cloud/oc2-security-module | https://api.github.com/repos/ayumi-cloud/oc2-security-module | closed | Add negative labels to bad search engines with dns confirmation | Add to Blacklist Enhancement FINSIHED Firewall Priority: Medium Testing - Passed | ### Enhancement idea
- [x] Add negative labels to bad search engines with dns confirmation.
| 1.0 | Add negative labels to bad search engines with dns confirmation - ### Enhancement idea
- [x] Add negative labels to bad search engines with dns confirmation.
| non_comp | add negative labels to bad search engines with dns confirmation enhancement idea add negative labels to bad search engines with dns confirmation | 0 |
20,137 | 28,136,248,944 | IssuesEvent | 2023-04-01 12:18:01 | MarketSquare/robotframework-robocop | https://api.github.com/repos/MarketSquare/robotframework-robocop | closed | Add rules for BREAK, CONTINUE | rule RF compatibility | Handle BREAK and CONTINUE. Possible rules (update old or create new):
1. Do not name keyword after reserved words (#570)
2. Do not use BREAK, CONTINUE outside FOR, WHILE or TRY EXCEPT (check how it works - possibly prohibit in finally) (#562)
3. Recommend to use them inside IF statement (otherwise the code after them will be dead)
4. Label `Exit For Loop`, `Exit For Loop If`, `Continue For Loop`, `Continue For Loop If` as deprecated and suggest using BREAK or CONTINUE. (#576) | True | Add rules for BREAK, CONTINUE - Handle BREAK and CONTINUE. Possible rules (update old or create new):
1. Do not name keyword after reserved words (#570)
2. Do not use BREAK, CONTINUE outside FOR, WHILE or TRY EXCEPT (check how it works - possibly prohibit in finally) (#562)
3. Recommend to use them inside IF statement (otherwise the code after them will be dead)
4. Label `Exit For Loop`, `Exit For Loop If`, `Continue For Loop`, `Continue For Loop If` as deprecated and suggest using BREAK or CONTINUE. (#576) | comp | add rules for break continue handle break and continue possible rules update old or create new do not name keyword after reserved words do not use break continue outside for while or try except check how it works possibly prohibit in finally recommend to use them inside if statement otherwise the code after them will be dead label exit for loop exit for loop if continue for loop continue for loop if as deprecated and suggest using break or continue | 1 |
6,486 | 8,774,214,730 | IssuesEvent | 2018-12-18 19:08:25 | cleverness/widget-css-classes | https://api.github.com/repos/cleverness/widget-css-classes | closed | Not working in Storefront Mega Menu widgets | compatibility | The plugin is not working when I add widgets in Storefront Mega Menu but works with the widgets in the sidebar. | True | Not working in Storefront Mega Menu widgets - The plugin is not working when I add widgets in Storefront Mega Menu but works with the widgets in the sidebar. | comp | not working in storefront mega menu widgets the plugin is not working when i add widgets in storefront mega menu but works with the widgets in the sidebar | 1 |
340 | 2,774,453,750 | IssuesEvent | 2015-05-04 09:02:55 | mapbox/polyclip | https://api.github.com/repos/mapbox/polyclip | opened | Handle more edge overlapping cases | compatibility | Currently we only handle the first 6 cases, 3 left to implement:
```
---x---
---x---
------
---x-----
------
---x----x---
---x---
----
------
------
------
-----x---
---x--x---
----
---x---
----
---x---
---x---
``` | True | Handle more edge overlapping cases - Currently we only handle the first 6 cases, 3 left to implement:
```
---x---
---x---
------
---x-----
------
---x----x---
---x---
----
------
------
------
-----x---
---x--x---
----
---x---
----
---x---
---x---
``` | comp | handle more edge overlapping cases currently we only handle the first cases left to implement x x x x x x x x x x x x | 1 |
4,623 | 5,217,501,676 | IssuesEvent | 2017-01-26 14:07:10 | w3c/sensors | https://api.github.com/repos/w3c/sensors | closed | Frequency readout allows fingerprinting sensors, privacy. | ED-ready privacy resolved security | Hi,
I will put it here just not to forget, we should consider writing something specifying that it will be possible to poll the supported frequencies (hardware/implementation related).
1. Loop through the polled frequencies (e.g. 0 .. 500)
2. Inspect the sensor readout, take into account the readout's timestamp
3. Verify how many readouts per second are supported
4. In the end, it could be possible to inspect the actually supported frequencies.
We could add something:
"Frequency polling in periodic reporting mode might allow the fingerprinting of hardware or implementation types, by probing which actual frequencies are supported by the platform."
| True | Frequency readout allows fingerprinting sensors, privacy. - Hi,
I will put it here just not to forget, we should consider writing something specifying that it will be possible to poll the supported frequencies (hardware/implementation related).
1. Loop through the polled frequencies (e.g. 0 .. 500)
2. Inspect the sensor readout, take into account the readout's timestamp
3. Verify how many readouts per second are supported
4. In the end, it could be possible to inspect the actually supported frequencies.
We could add something:
"Frequency polling in periodic reporting mode might allow the fingerprinting of hardware or implementation types, by probing which actual frequencies are supported by the platform."
| non_comp | frequency readout allows fingerprinting sensors privacy hi i will put it here just not to forget we should consider writing something specifying that it will be possible to poll the supported frequencies hardware implementation related loop through the polled frequencies e g inspect the sensor readout take into account the readout s timestamp verify how many readouts per second are supported in the end it could be possible to inspect the actually supported frequencies we could add something frequency polling in periodic reporting mode might allow the fingerprinting of hardware or implementation types by probing which actual frequencies are supported by the platform | 0 |
308,197 | 23,237,421,121 | IssuesEvent | 2022-08-03 13:01:03 | contentauth/c2pa-js | https://api.github.com/repos/contentauth/c2pa-js | closed | Update pull request template | documentation | The default pull request template is quite long and complex. We might want to use something closer to the one that c2pa-rs uses:
```markdown
## Changes in This Pull Request
_Give a narrative description of what has been changed._
## Checklist
- [ ] This PR represents a single feature, fix, or change.
- [ ] All applicable changes have been documented.
- [ ] Any `TO DO` items (or similar) have been entered as GitHub issues and the link to that issue has been included in a comment.
``` | 1.0 | Update pull request template - The default pull request template is quite long and complex. We might want to use something closer to the one that c2pa-rs uses:
```markdown
## Changes in This Pull Request
_Give a narrative description of what has been changed._
## Checklist
- [ ] This PR represents a single feature, fix, or change.
- [ ] All applicable changes have been documented.
- [ ] Any `TO DO` items (or similar) have been entered as GitHub issues and the link to that issue has been included in a comment.
``` | non_comp | update pull request template the default pull request template is quite long and complex we might want to use something closer to the one that rs uses markdown changes in this pull request give a narrative description of what has been changed checklist this pr represents a single feature fix or change all applicable changes have been documented any to do items or similar have been entered as github issues and the link to that issue has been included in a comment | 0 |
10,958 | 12,974,050,316 | IssuesEvent | 2020-07-21 14:53:37 | grondag/canvas | https://api.github.com/repos/grondag/canvas | closed | No Overlays from other mods | compatibility | Canvas does not allow other mods to render overlays (LightOverlay, Bounding Box Outline Reloaded, MiniHUD's shapes).
[latest.log](https://github.com/grondag/canvas/files/4926288/latest.log)
| True | No Overlays from other mods - Canvas does not allow other mods to render overlays (LightOverlay, Bounding Box Outline Reloaded, MiniHUD's shapes).
[latest.log](https://github.com/grondag/canvas/files/4926288/latest.log)
| comp | no overlays from other mods canvas does not allow other mods to render overlays lightoverlay bounding box outline reloaded minihud s shapes | 1 |
14,093 | 10,602,805,250 | IssuesEvent | 2019-10-10 14:50:55 | dotnet/wpf | https://api.github.com/repos/dotnet/wpf | opened | Enabling Roslyn analyzers | area-infrastructure up-for-grabs | As a team, we'd like to get a core set of Roslyn code analyzers fully integrated into our build to help ensure the long term health of the code base. Much of WPF was written 10+ years ago and doesn't necessarily follow the best practices. It's important to understand what can and can't change, **no change as part of this work should change the behavior**.
### Scope of work
- [ ] Determine which rules should and shouldn't be enabled.
- [ ] If a rule should be suppressed entirely, add the suppression to the code analysis ruleset in eng\WpfArcadeSdk\tools\CodeAnalysis\WpfCodeAnalysis.ruleset
- [ ] If a rule needs to be suppressed, but will never be fixed (i.e. for compat reasons) put the suppression in a GlobalSuppressions.cs file.
- [ ] If a rule needs to be suppressed, but should be addressed a later time, put the suppression at the callsite.
- [ ] If a rule is to be fixed, use the associated code-fixer to make the changes, instead of by hand.
### Projects to enable
Here are the assemblies that we should focus on. Ideally done one at a time so that PR's are easy to read and understand. They can follow what we did with `System.Xaml` for an example. It's recommended to start with one of the smaller projects first :)
- [ ] System.Windows.Controls.Ribbon
- [ ] ReachFramework
- [ ] UIAutomationClient
- [ ] UIAutomationProvider
- [ ] UIAutomationTypes
- [ ] PresentationBuildTasks
- [ ] PresentationCore
- [ ] PresentationFramework
- [ ] WindowsBase
**Note: this work isn't necessary for test projects**
### Methodology
- To make this work easier to understand for the maintainers, it should be easy to differentiate at the commit/pr level what was a suppression versus what was a fix. This is not a hard requirement, but it will make the life of anyone reviewing the code much easier.
- Add `<EnableAnalyzers>true</EnableAnalyzers>` to the .csproj file and build. There will most likely be a lot of errors, this is where the fun begins :)
- Part of determining the proper rules is based on the current state of the code, and not necessarily what is ideal. Too many changes to the code will result in PR's that are too lengthy and cumbersome to review, which isn't ideal for anyone. Separate issues can be filed if there are certain rules we want to enable in the future.
### Code-fixers
We should run the code-fixers for each analyzer with the enabled rules and auto-update the source code, rather than making the edits by hand. Some of the fixers may not be implemented, and it would be extra valuable to go and add the fixer so that everyone in the .NET community can benefit from it. I did this for one of the fixers early on, and here is an example PR: https://github.com/dotnet/roslyn-analyzers/pull/2166
All the analyzers and associated code-fixers are in this repo:
https://github.com/dotnet/roslyn-analyzers
Running the code-fixers can be done when the solution is loaded in Visual Studio, or by using this tool (I don't know what state this tool is in or if it works, there may be bugs)
https://github.com/stevenbrix/AnalyzerRunner
This is work that we've had on our backlog for a while, but isn't the highest priority at the moment for us. There have been a lot of code cleanup/beautification PR's to the WPF code base since it's been open-sourced (thank you everyone!), and so I'm hoping to formalize this work a bit and open it up to anyone that is interested in defining the best-practices in this code base, as well as learn a bit about Roslyn analyzers while doing it!
/cc @YoshihiroIto who expressed interest in learning more about Roslyn analyzers.
| 1.0 | Enabling Roslyn analyzers - As a team, we'd like to get a core set of Roslyn code analyzers fully integrated into our build to help ensure the long term health of the code base. Much of WPF was written 10+ years ago and doesn't necessarily follow the best practices. It's important to understand what can and can't change, **no change as part of this work should change the behavior**.
### Scope of work
- [ ] Determine which rules should and shouldn't be enabled.
- [ ] If a rule should be suppressed entirely, add the suppression to the code analysis ruleset in eng\WpfArcadeSdk\tools\CodeAnalysis\WpfCodeAnalysis.ruleset
- [ ] If a rule needs to be suppressed, but will never be fixed (i.e. for compat reasons) put the suppression in a GlobalSuppressions.cs file.
- [ ] If a rule needs to be suppressed, but should be addressed a later time, put the suppression at the callsite.
- [ ] If a rule is to be fixed, use the associated code-fixer to make the changes, instead of by hand.
### Projects to enable
Here are the assemblies that we should focus on. Ideally done one at a time so that PR's are easy to read and understand. They can follow what we did with `System.Xaml` for an example. It's recommended to start with one of the smaller projects first :)
- [ ] System.Windows.Controls.Ribbon
- [ ] ReachFramework
- [ ] UIAutomationClient
- [ ] UIAutomationProvider
- [ ] UIAutomationTypes
- [ ] PresentationBuildTasks
- [ ] PresentationCore
- [ ] PresentationFramework
- [ ] WindowsBase
**Note: this work isn't necessary for test projects**
### Methodology
- To make this work easier to understand for the maintainers, it should be easy to differentiate at the commit/pr level what was a suppression versus what was a fix. This is not a hard requirement, but it will make the life of anyone reviewing the code much easier.
- Add `<EnableAnalyzers>true</EnableAnalyzers>` to the .csproj file and build. There will most likely be a lot of errors, this is where the fun begins :)
- Part of determining the proper rules is based on the current state of the code, and not necessarily what is ideal. Too many changes to the code will result in PR's that are too lengthy and cumbersome to review, which isn't ideal for anyone. Separate issues can be filed if there are certain rules we want to enable in the future.
### Code-fixers
We should run the code-fixers for each analyzer with the enabled rules and auto-update the source code, rather than making the edits by hand. Some of the fixers may not be implemented, and it would be extra valuable to go and add the fixer so that everyone in the .NET community can benefit from it. I did this for one of the fixers early on, and here is an example PR: https://github.com/dotnet/roslyn-analyzers/pull/2166
All the analyzers and associated code-fixers are in this repo:
https://github.com/dotnet/roslyn-analyzers
Running the code-fixers can be done when the solution is loaded in Visual Studio, or by using this tool (I don't know what state this tool is in or if it works, there may be bugs)
https://github.com/stevenbrix/AnalyzerRunner
This is work that we've had on our backlog for a while, but isn't the highest priority at the moment for us. There have been a lot of code cleanup/beautification PR's to the WPF code base since it's been open-sourced (thank you everyone!), and so I'm hoping to formalize this work a bit and open it up to anyone that is interested in defining the best-practices in this code base, as well as learn a bit about Roslyn analyzers while doing it!
/cc @YoshihiroIto who expressed interest in learning more about Roslyn analyzers.
| non_comp | enabling roslyn analyzers as a team we d like to get a core set of roslyn code analyzers fully integrated into our build to help ensure the long term health of the code base much of wpf was written years ago and doesn t necessarily follow the best practices it s important to understand what can and can t change no change as part of this work should change the behavior scope of work determine which rules should and shouldn t be enabled if a rule should be suppressed entirely add the suppression to the code analysis ruleset in eng wpfarcadesdk tools codeanalysis wpfcodeanalysis ruleset if a rule needs to be suppressed but will never be fixed i e for compat reasons put the suppression in a globalsuppressions cs file if a rule needs to be suppressed but should be addressed a later time put the suppression at the callsite if a rule is to be fixed use the associated code fixer to make the changes instead of by hand projects to enable here are the assemblies that we should focus on ideally done one at a time so that pr s are easy to read and understand they can follow what we did with system xaml for an example it s recommended to start with one of the smaller projects first system windows controls ribbon reachframework uiautomationclient uiautomationprovider uiautomationtypes presentationbuildtasks presentationcore presentationframework windowsbase note this work isn t necessary for test projects methodology to make this work easier to understand for the maintainers it should be easy to differentiate at the commit pr level what was a suppression versus what was a fix this is not a hard requirement but it will make the life of anyone reviewing the code much easier add true to the csproj file and build there will most likely be a lot of errors this is where the fun begins part of determining the proper rules is based on the current state of the code and not necessarily what is ideal too many changes to the code will result in pr s that are too lengthy and cumbersome to review which isn t ideal for anyone separate issues can be filed if there are certain rules we want to enable in the future code fixers we should run the code fixers for each analyzer with the enabled rules and auto update the source code rather than making the edits by hand some of the fixers may not be implemented and it would be extra valuable to go and add the fixer so that everyone in the net community can benefit from it i did this for one of the fixers early on and here is an example pr all the analyzers and associated code fixers are in this repo running the code fixers can be done when the solution is loaded in visual studio or by using this tool i don t know what state this tool is in or if it works there may be bugs this is work that we ve had on our backlog for a while but isn t the highest priority at the moment for us there have been a lot of code cleanup beautification pr s to the wpf code base since it s been open sourced thank you everyone and so i m hoping to formalize this work a bit and open it up to anyone that is interested in defining the best practices in this code base as well as learn a bit about roslyn analyzers while doing it cc yoshihiroito who expressed interest in learning more about roslyn analyzers | 0 |
214,375 | 16,583,539,370 | IssuesEvent | 2021-05-31 15:01:55 | ManimCommunity/ManimPango | https://api.github.com/repos/ManimCommunity/ManimPango | closed | Don't depend on Manim for testing | tests | Currently, for testing, we require ManimCE to be installed, but that causes a circular dependency even though it is just for testing. My suggestion is not to depend on Manim, instead implement those classes in the test suite. | 1.0 | Don't depend on Manim for testing - Currently, for testing, we require ManimCE to be installed, but that causes a circular dependency even though it is just for testing. My suggestion is not to depend on Manim, instead implement those classes in the test suite. | non_comp | don t depend on manim for testing currently for testing we require manimce to be installed but that causes a circular dependency even though it is just for testing my suggestion is not to depend on manim instead implement those classes in the test suite | 0 |
95,703 | 19,750,636,807 | IssuesEvent | 2022-01-15 03:16:04 | decentralized-identity/sidetree | https://api.github.com/repos/decentralized-identity/sidetree | closed | Make applyFirstValidOperation in Resolver return previous did state instead of undefined | code refactoring | - Make sure no side effects if this change is taken.
- Make applyFirstValidOperation in Resolver return previous did state instead of undefined when no operation can be applied. | 1.0 | Make applyFirstValidOperation in Resolver return previous did state instead of undefined - - Make sure no side effects if this change is taken.
- Make applyFirstValidOperation in Resolver return previous did state instead of undefined when no operation can be applied. | non_comp | make applyfirstvalidoperation in resolver return previous did state instead of undefined make sure no side effects if this change is taken make applyfirstvalidoperation in resolver return previous did state instead of undefined when no operation can be applied | 0 |
8,497 | 10,518,204,168 | IssuesEvent | 2019-09-29 09:07:35 | Johni0702/BetterPortals | https://api.github.com/repos/Johni0702/BetterPortals | closed | Mobs are rendered but not properly processed through a portal | bug compatibility | I tried building a farming setup for pigmen where they would fall through a nether portal, to die to fall damage on the other side.
What I noticed was that mobs properly fall through the portal, up to a certain distance at which point they froze in midair. If I made them hit a floor before that, they could die normally, but their corpses froze aswell.
Mobs seem to have no AI ‘on the other side’, but I guess they are somewhat being processed still. I can drop an item through and see it fall.
If I pass through the portal myself, all the frozen corpses properly disintegrate into smoke and drops, aswell as mobs moving.
Now this all might be an intentional, but maybe undesired limitation to loading the other dimension remotely.
(Same results for with or without using a cubic world)
| True | Mobs are rendered but not properly processed through a portal - I tried building a farming setup for pigmen where they would fall through a nether portal, to die to fall damage on the other side.
What I noticed was that mobs properly fall through the portal, up to a certain distance at which point they froze in midair. If I made them hit a floor before that, they could die normally, but their corpses froze aswell.
Mobs seem to have no AI ‘on the other side’, but I guess they are somewhat being processed still. I can drop an item through and see it fall.
If I pass through the portal myself, all the frozen corpses properly disintegrate into smoke and drops, aswell as mobs moving.
Now this all might be an intentional, but maybe undesired limitation to loading the other dimension remotely.
(Same results for with or without using a cubic world)
| comp | mobs are rendered but not properly processed through a portal i tried building a farming setup for pigmen where they would fall through a nether portal to die to fall damage on the other side what i noticed was that mobs properly fall through the portal up to a certain distance at which point they froze in midair if i made them hit a floor before that they could die normally but their corpses froze aswell mobs seem to have no ai ‘on the other side’ but i guess they are somewhat being processed still i can drop an item through and see it fall if i pass through the portal myself all the frozen corpses properly disintegrate into smoke and drops aswell as mobs moving now this all might be an intentional but maybe undesired limitation to loading the other dimension remotely same results for with or without using a cubic world | 1 |
101,415 | 16,509,924,984 | IssuesEvent | 2021-05-26 01:51:34 | kijunb33/c | https://api.github.com/repos/kijunb33/c | opened | CVE-2019-17563 (High) detected in tomcat-embed-core-7.0.90.jar | security vulnerability | ## CVE-2019-17563 - High 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: c/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/c/commits/7dc3b09e73910975c94cebd1e54f33c4097c695b">7dc3b09e73910975c94cebd1e54f33c4097c695b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
When using FORM authentication with Apache Tomcat 9.0.0.M1 to 9.0.29, 8.5.0 to 8.5.49 and 7.0.0 to 7.0.98 there was a narrow window where an attacker could perform a session fixation attack. The window was considered too narrow for an exploit to be practical but, erring on the side of caution, this issue has been treated as a security vulnerability.
<p>Publish Date: 2019-12-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17563>CVE-2019-17563</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: High
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17563">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17563</a></p>
<p>Release Date: 2019-12-23</p>
<p>Fix Resolution: org.apache.tomcat.embed:tomcat-embed-core:7.0.99,8.5.50,9.0.30;org.apache.tomcat:tomcat-catalina:7.0.99,8.5.50,9.0.30</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-17563 (High) detected in tomcat-embed-core-7.0.90.jar - ## CVE-2019-17563 - High 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: c/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/c/commits/7dc3b09e73910975c94cebd1e54f33c4097c695b">7dc3b09e73910975c94cebd1e54f33c4097c695b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
When using FORM authentication with Apache Tomcat 9.0.0.M1 to 9.0.29, 8.5.0 to 8.5.49 and 7.0.0 to 7.0.98 there was a narrow window where an attacker could perform a session fixation attack. The window was considered too narrow for an exploit to be practical but, erring on the side of caution, this issue has been treated as a security vulnerability.
<p>Publish Date: 2019-12-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17563>CVE-2019-17563</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: High
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17563">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17563</a></p>
<p>Release Date: 2019-12-23</p>
<p>Fix Resolution: org.apache.tomcat.embed:tomcat-embed-core:7.0.99,8.5.50,9.0.30;org.apache.tomcat:tomcat-catalina:7.0.99,8.5.50,9.0.30</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_comp | cve high detected in tomcat embed core jar cve high severity vulnerability vulnerable library tomcat embed core jar core tomcat implementation library home page a href path to vulnerable library c 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 when using form authentication with apache tomcat to to and to there was a narrow window where an attacker could perform a session fixation attack the window was considered too narrow for an exploit to be practical but erring on the side of caution this issue has been treated as a security vulnerability publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction required 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 org apache tomcat embed tomcat embed core org apache tomcat tomcat catalina step up your open source security game with whitesource | 0 |
135,780 | 19,663,401,473 | IssuesEvent | 2022-01-10 19:30:17 | department-of-veterans-affairs/va.gov-team | https://api.github.com/repos/department-of-veterans-affairs/va.gov-team | closed | [Design] My VA: Update copy on My VA to align with Content direction | design my-va-dashboard vsa-authenticated-exp needs-grooming | ## Background
Per comment on [ticket #33839](https://github.com/department-of-veterans-affairs/va.gov-team/issues/33839), we should align better with the advisement from our Content partners.
- We need to update the header for "Claims & Appeals" to replace the ampersand
- We need to update the Health Care section for unread messages to reword and move the URL to different text
## Tasks
**Design changes**
- [ ] Update design documentation to reflect the changes needed
- Update header "Claims & appeals" to read "**Claims and appeals**"
- Update Health care section on the messages text
- Replace [You have n unread messages] with new verbiage "**You have n unread messages. [View your messages].**"
## Acceptance Criteria
- My VA page reflects the updates in accordance with Content advisement
| 1.0 | [Design] My VA: Update copy on My VA to align with Content direction - ## Background
Per comment on [ticket #33839](https://github.com/department-of-veterans-affairs/va.gov-team/issues/33839), we should align better with the advisement from our Content partners.
- We need to update the header for "Claims & Appeals" to replace the ampersand
- We need to update the Health Care section for unread messages to reword and move the URL to different text
## Tasks
**Design changes**
- [ ] Update design documentation to reflect the changes needed
- Update header "Claims & appeals" to read "**Claims and appeals**"
- Update Health care section on the messages text
- Replace [You have n unread messages] with new verbiage "**You have n unread messages. [View your messages].**"
## Acceptance Criteria
- My VA page reflects the updates in accordance with Content advisement
| non_comp | my va update copy on my va to align with content direction background per comment on we should align better with the advisement from our content partners we need to update the header for claims appeals to replace the ampersand we need to update the health care section for unread messages to reword and move the url to different text tasks design changes update design documentation to reflect the changes needed update header claims appeals to read claims and appeals update health care section on the messages text replace with new verbiage you have n unread messages acceptance criteria my va page reflects the updates in accordance with content advisement | 0 |
16,681 | 22,959,742,163 | IssuesEvent | 2022-07-19 14:29:12 | MetaMask/metamask-mobile | https://api.github.com/repos/MetaMask/metamask-mobile | closed | Window.ethereum not being injected on Android (again?) | bug dapp-compatibility severity2-normal community | I'm aware of this having been a previous issue, but it still seems to be happening with Android 11 (and I just updated to August 5 security update).
As an example of my implementation, you can check https://tossaneth.com/eth, where pressing the send button uses window.ethereum for the transaction if it exists, otherwise it serves as a deep link to the same url. It works fine on iOS. | True | Window.ethereum not being injected on Android (again?) - I'm aware of this having been a previous issue, but it still seems to be happening with Android 11 (and I just updated to August 5 security update).
As an example of my implementation, you can check https://tossaneth.com/eth, where pressing the send button uses window.ethereum for the transaction if it exists, otherwise it serves as a deep link to the same url. It works fine on iOS. | comp | window ethereum not being injected on android again i m aware of this having been a previous issue but it still seems to be happening with android and i just updated to august security update as an example of my implementation you can check where pressing the send button uses window ethereum for the transaction if it exists otherwise it serves as a deep link to the same url it works fine on ios | 1 |
14,797 | 18,234,248,899 | IssuesEvent | 2021-10-01 03:41:18 | gambitph/Stackable | https://api.github.com/repos/gambitph/Stackable | closed | [Toolset Integration] When Toolset is activated, the advancedSelectControl is huge | bug need more info [version] V3 v2 compatibility | <!--
Before posting, make sure that:
1. you are running the latest version of Stackable, and
2. you have searched whether your issue has already been reported
-->
**To Reproduce**
Steps to reproduce the behavior:
1. Activate Toolset Blocks / Types
2. Add a v2 / v3 Card
3. Go to Advanced tab
4. Collapse the General panel - see bug
**Screenshots**
https://user-images.githubusercontent.com/28699204/134893927-4323cafc-8da6-49f5-9f53-bf9aefa55acb.mov
| True | [Toolset Integration] When Toolset is activated, the advancedSelectControl is huge - <!--
Before posting, make sure that:
1. you are running the latest version of Stackable, and
2. you have searched whether your issue has already been reported
-->
**To Reproduce**
Steps to reproduce the behavior:
1. Activate Toolset Blocks / Types
2. Add a v2 / v3 Card
3. Go to Advanced tab
4. Collapse the General panel - see bug
**Screenshots**
https://user-images.githubusercontent.com/28699204/134893927-4323cafc-8da6-49f5-9f53-bf9aefa55acb.mov
| comp | when toolset is activated the advancedselectcontrol is huge before posting make sure that you are running the latest version of stackable and you have searched whether your issue has already been reported to reproduce steps to reproduce the behavior activate toolset blocks types add a card go to advanced tab collapse the general panel see bug screenshots | 1 |
1,979 | 3,226,529,310 | IssuesEvent | 2015-10-10 10:50:04 | adobe/brackets | https://api.github.com/repos/adobe/brackets | closed | RESEARCH: Measure performance against other editors | performance release-14 STORY | ## Areas to measure
* Find in Files
* Switching between / opening files
* Typing (https://github.com/adobe/brackets/issues/11104)
* Scrolling (https://github.com/adobe/brackets/issues/11105)
* Startup time
These can be categorized as mostly rendering (Typing & Scrolling),
mostly JavaScript (Find in Files), and a mix of the two (Switching between / opening files)
Out of scope:
* Ways to track key performance metrics regularly (per build or per sprint) and graph them -- see [story #357 (Performance Automation)](https://trello.com/c/RWwPlSeO/357-2-performance-automation)
* Ways we could automatically gather performance stats from Brackets in the field as metrics -- fold into Brackets Health Report story
## Which editors should we compare against?
- Sublime
- Atom
- Visual Studio Code
- (Out of scope: Visual Studio, XCode, Notepad++, etc.)
## Measurement approach
- High speed camera: Typing, Scrolling, Switching between files
- Stopwatch: Find in Files (other editors)
- PerfUtils instrumentation: Find in Files (Brackets)
## Project Size
We want to test these features across small, medium and large projects. Large project is defined 30,000+ files.
What do we consider a small, medium and large Project? Large file? Should we test typing with code hints (and if so which kind), or without?
Do we have example projects that we could leverage for this data collection? Using real world projects would make it definitely more representative.
## Environment
Must use the same machine for all tests to ensure comparable results. Run all tests twice, on:
- Windows 7
- OSX 10.10.3 Retina
- (Out of scope: Windows 8, Mac OSX 10.10 non-Retina, etc.)
## Tasks
- [ ] Define test file(s) for Scrolling/Typing testing
- [ ] Define test project for Find in Files testing
- [ ] Define specific test steps for Typing
- [ ] Define specific test steps for Scrolling
- [ ] Define specific test steps for Switching editors
- [ ] Define specific test steps for Find in Files
- [ ] Decide test hardware for both OSes
- [ ] Install all editors on the test machines
- [ ] Capture high speed camera data (Typing, Scrolling, Switching)
- [ ] Analyze high-speed camera data (Typing, Scrolling, Switching)
- [ ] Find in Files measurements
- [ ] Write up summary report & suggested areas of focus | True | RESEARCH: Measure performance against other editors - ## Areas to measure
* Find in Files
* Switching between / opening files
* Typing (https://github.com/adobe/brackets/issues/11104)
* Scrolling (https://github.com/adobe/brackets/issues/11105)
* Startup time
These can be categorized as mostly rendering (Typing & Scrolling),
mostly JavaScript (Find in Files), and a mix of the two (Switching between / opening files)
Out of scope:
* Ways to track key performance metrics regularly (per build or per sprint) and graph them -- see [story #357 (Performance Automation)](https://trello.com/c/RWwPlSeO/357-2-performance-automation)
* Ways we could automatically gather performance stats from Brackets in the field as metrics -- fold into Brackets Health Report story
## Which editors should we compare against?
- Sublime
- Atom
- Visual Studio Code
- (Out of scope: Visual Studio, XCode, Notepad++, etc.)
## Measurement approach
- High speed camera: Typing, Scrolling, Switching between files
- Stopwatch: Find in Files (other editors)
- PerfUtils instrumentation: Find in Files (Brackets)
## Project Size
We want to test these features across small, medium and large projects. Large project is defined 30,000+ files.
What do we consider a small, medium and large Project? Large file? Should we test typing with code hints (and if so which kind), or without?
Do we have example projects that we could leverage for this data collection? Using real world projects would make it definitely more representative.
## Environment
Must use the same machine for all tests to ensure comparable results. Run all tests twice, on:
- Windows 7
- OSX 10.10.3 Retina
- (Out of scope: Windows 8, Mac OSX 10.10 non-Retina, etc.)
## Tasks
- [ ] Define test file(s) for Scrolling/Typing testing
- [ ] Define test project for Find in Files testing
- [ ] Define specific test steps for Typing
- [ ] Define specific test steps for Scrolling
- [ ] Define specific test steps for Switching editors
- [ ] Define specific test steps for Find in Files
- [ ] Decide test hardware for both OSes
- [ ] Install all editors on the test machines
- [ ] Capture high speed camera data (Typing, Scrolling, Switching)
- [ ] Analyze high-speed camera data (Typing, Scrolling, Switching)
- [ ] Find in Files measurements
- [ ] Write up summary report & suggested areas of focus | non_comp | research measure performance against other editors areas to measure find in files switching between opening files typing scrolling startup time these can be categorized as mostly rendering typing scrolling mostly javascript find in files and a mix of the two switching between opening files out of scope ways to track key performance metrics regularly per build or per sprint and graph them see ways we could automatically gather performance stats from brackets in the field as metrics fold into brackets health report story which editors should we compare against sublime atom visual studio code out of scope visual studio xcode notepad etc measurement approach high speed camera typing scrolling switching between files stopwatch find in files other editors perfutils instrumentation find in files brackets project size we want to test these features across small medium and large projects large project is defined files what do we consider a small medium and large project large file should we test typing with code hints and if so which kind or without do we have example projects that we could leverage for this data collection using real world projects would make it definitely more representative environment must use the same machine for all tests to ensure comparable results run all tests twice on windows osx retina out of scope windows mac osx non retina etc tasks define test file s for scrolling typing testing define test project for find in files testing define specific test steps for typing define specific test steps for scrolling define specific test steps for switching editors define specific test steps for find in files decide test hardware for both oses install all editors on the test machines capture high speed camera data typing scrolling switching analyze high speed camera data typing scrolling switching find in files measurements write up summary report suggested areas of focus | 0 |
16,286 | 21,923,041,486 | IssuesEvent | 2022-05-22 21:22:49 | raiguard/krastorio-2 | https://api.github.com/repos/raiguard/krastorio-2 | closed | Compatability issue with angelspetrochem_0.9.21 Error Non-contiguous Technology levels. CTD on launch. Possible solution? | bug compatibility | ### Description
Error ModManager.cpp:1578: Technology chlorine-processing: Non-contiguous levels: 2, followed by 4
Mod settings wiped, fresh install.
Likely caused by a possible oversight in compatability script:
compatibility-scripts/data-final-fixes/angels/angelspetrochem.lua line 57
Following the condition in line 55 technology "chlorine-processing-3" is removed (line 57), yet "chlorine-processing-4" presumably added by angelspetrochem still exists and unchanged which causes an error.
Adding the following code fixed the crash, yet I am not sure if this fix is final.
`data.raw.technology["chlorine-processing-4"] = nil`
`krastorio.technologies.convertPrerequisiteFromAllTechnologies(
"chlorine-processing-4",
"chlorine-processing-2",
true
)`
[factorio-current.log](https://github.com/raiguard/krastorio-2/files/8653600/factorio-current.log)
### Reproduction
1. Install:
angelsrefining 0.12.1
angelspetrochem 0.9.21
Krastorio2 1.2.25
2. Launch the game
### Factorio version
1.1.57
### In-game username
SilentGraph | True | Compatability issue with angelspetrochem_0.9.21 Error Non-contiguous Technology levels. CTD on launch. Possible solution? - ### Description
Error ModManager.cpp:1578: Technology chlorine-processing: Non-contiguous levels: 2, followed by 4
Mod settings wiped, fresh install.
Likely caused by a possible oversight in compatability script:
compatibility-scripts/data-final-fixes/angels/angelspetrochem.lua line 57
Following the condition in line 55 technology "chlorine-processing-3" is removed (line 57), yet "chlorine-processing-4" presumably added by angelspetrochem still exists and unchanged which causes an error.
Adding the following code fixed the crash, yet I am not sure if this fix is final.
`data.raw.technology["chlorine-processing-4"] = nil`
`krastorio.technologies.convertPrerequisiteFromAllTechnologies(
"chlorine-processing-4",
"chlorine-processing-2",
true
)`
[factorio-current.log](https://github.com/raiguard/krastorio-2/files/8653600/factorio-current.log)
### Reproduction
1. Install:
angelsrefining 0.12.1
angelspetrochem 0.9.21
Krastorio2 1.2.25
2. Launch the game
### Factorio version
1.1.57
### In-game username
SilentGraph | comp | compatability issue with angelspetrochem error non contiguous technology levels ctd on launch possible solution description error modmanager cpp technology chlorine processing non contiguous levels followed by mod settings wiped fresh install likely caused by a possible oversight in compatability script compatibility scripts data final fixes angels angelspetrochem lua line following the condition in line technology chlorine processing is removed line yet chlorine processing presumably added by angelspetrochem still exists and unchanged which causes an error adding the following code fixed the crash yet i am not sure if this fix is final data raw technology nil krastorio technologies convertprerequisitefromalltechnologies chlorine processing chlorine processing true reproduction install angelsrefining angelspetrochem launch the game factorio version in game username silentgraph | 1 |
92 | 2,551,382,605 | IssuesEvent | 2015-02-02 09:08:10 | stapelberg/my-issue-test | https://api.github.com/repos/stapelberg/my-issue-test | closed | hotkey configuration doesn't respect alternating keyboard layouts | C: compatibility R: duplicate | **Reported by dothebart@… on 26 Aug 2009 08:43 UTC**
Being a user of the dvorak layout, http://dvorak.mwbrooks.com/; I found out the hard way that Mod1-E is exit, since my ';' is there and I wanted to test the tiling.
Check out with
setxkbmap dvorak
or change the layout in the xorg.conf | True | hotkey configuration doesn't respect alternating keyboard layouts - **Reported by dothebart@… on 26 Aug 2009 08:43 UTC**
Being a user of the dvorak layout, http://dvorak.mwbrooks.com/; I found out the hard way that Mod1-E is exit, since my ';' is there and I wanted to test the tiling.
Check out with
setxkbmap dvorak
or change the layout in the xorg.conf | comp | hotkey configuration doesn t respect alternating keyboard layouts reported by dothebart … on aug utc being a user of the dvorak layout i found out the hard way that e is exit since my is there and i wanted to test the tiling check out with setxkbmap dvorak or change the layout in the xorg conf | 1 |
156,654 | 13,652,660,128 | IssuesEvent | 2020-09-27 08:43:27 | AzureAD/microsoft-authentication-extensions-for-dotnet | https://api.github.com/repos/AzureAD/microsoft-authentication-extensions-for-dotnet | closed | link to linux fallback configuration example does not work | Fixed bug documentation | I'm trying to test whether token caching works for our desktop app on linux, but I can't do it over ssh. I noticed the wiki states
> KeyRings does not work in headless mode (e.g. when connected over SSH or when running Linux in a container) due to a dependency on X11. To overcome this, a fallback to a plaintext file can be configured. See this example for how to configure it.
But when I click the link to the example, I get a github 404 error. Can the wiki please be updated? | 1.0 | link to linux fallback configuration example does not work - I'm trying to test whether token caching works for our desktop app on linux, but I can't do it over ssh. I noticed the wiki states
> KeyRings does not work in headless mode (e.g. when connected over SSH or when running Linux in a container) due to a dependency on X11. To overcome this, a fallback to a plaintext file can be configured. See this example for how to configure it.
But when I click the link to the example, I get a github 404 error. Can the wiki please be updated? | non_comp | link to linux fallback configuration example does not work i m trying to test whether token caching works for our desktop app on linux but i can t do it over ssh i noticed the wiki states keyrings does not work in headless mode e g when connected over ssh or when running linux in a container due to a dependency on to overcome this a fallback to a plaintext file can be configured see this example for how to configure it but when i click the link to the example i get a github error can the wiki please be updated | 0 |
280,138 | 8,678,339,458 | IssuesEvent | 2018-11-30 19:36:06 | googleapis/google-cloud-python | https://api.github.com/repos/googleapis/google-cloud-python | closed | Synthesis failed for kms | autosynth failure priority: p1 type: bug | Hello! Autosynth couldn't regenerate kms. :broken_heart:
Here's the output from running `synth.py`:
```
Cloning into 'working_repo'...
Switched to branch 'autosynth-kms'
[35msynthtool > [31m[43mYou are running the synthesis script directly, this will be disabled in a future release of Synthtool. Please use python3 -m synthtool instead.[0m
[35msynthtool > [36mEnsuring dependencies.[0m
[35msynthtool > [36mPulling artman image.[0m
latest: Pulling from googleapis/artman
Digest: sha256:2f6b261ee7fe1aedf238991c93a20b3820de37a343d0cacf3e3e9555c2aaf2ea
Status: Image is up to date for googleapis/artman:latest
[35msynthtool > [36mCloning googleapis.[0m
[35msynthtool > [36mRunning generator for google/cloud/kms/artman_cloudkms.yaml.[0m
[35msynthtool > [32mGenerated code into /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/kms-v1.[0m
.coveragerc
.flake8
MANIFEST.in
noxfile.py.j2
setup.cfg
Traceback (most recent call last):
File "synth.py", line 44, in <module>
s.shell.run(["nox", "-s", "blacken"], hide_output=False)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/shell.py", line 33, in run
encoding="utf-8",
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 403, in run
with Popen(*popenargs, **kwargs) as process:
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 707, in __init__
restore_signals, start_new_session)
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 1326, in _execute_child
raise child_exception_type(errno_num, err_msg)
FileNotFoundError: [Errno 2] No such file or directory: 'nox'
[35msynthtool > [36mCleaned up 2 temporary directories.[0m
Synthesis failed
```
Google internal developers can see the full log [here](https://sponge/3abb58ef-0652-4854-846e-e1d9be78e73e).
| 1.0 | Synthesis failed for kms - Hello! Autosynth couldn't regenerate kms. :broken_heart:
Here's the output from running `synth.py`:
```
Cloning into 'working_repo'...
Switched to branch 'autosynth-kms'
[35msynthtool > [31m[43mYou are running the synthesis script directly, this will be disabled in a future release of Synthtool. Please use python3 -m synthtool instead.[0m
[35msynthtool > [36mEnsuring dependencies.[0m
[35msynthtool > [36mPulling artman image.[0m
latest: Pulling from googleapis/artman
Digest: sha256:2f6b261ee7fe1aedf238991c93a20b3820de37a343d0cacf3e3e9555c2aaf2ea
Status: Image is up to date for googleapis/artman:latest
[35msynthtool > [36mCloning googleapis.[0m
[35msynthtool > [36mRunning generator for google/cloud/kms/artman_cloudkms.yaml.[0m
[35msynthtool > [32mGenerated code into /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/kms-v1.[0m
.coveragerc
.flake8
MANIFEST.in
noxfile.py.j2
setup.cfg
Traceback (most recent call last):
File "synth.py", line 44, in <module>
s.shell.run(["nox", "-s", "blacken"], hide_output=False)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/shell.py", line 33, in run
encoding="utf-8",
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 403, in run
with Popen(*popenargs, **kwargs) as process:
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 707, in __init__
restore_signals, start_new_session)
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 1326, in _execute_child
raise child_exception_type(errno_num, err_msg)
FileNotFoundError: [Errno 2] No such file or directory: 'nox'
[35msynthtool > [36mCleaned up 2 temporary directories.[0m
Synthesis failed
```
Google internal developers can see the full log [here](https://sponge/3abb58ef-0652-4854-846e-e1d9be78e73e).
| non_comp | synthesis failed for kms hello autosynth couldn t regenerate kms broken heart here s the output from running synth py cloning into working repo switched to branch autosynth kms are running the synthesis script directly this will be disabled in a future release of synthtool please use m synthtool instead dependencies artman image latest pulling from googleapis artman digest status image is up to date for googleapis artman latest googleapis generator for google cloud kms artman cloudkms yaml code into home kbuilder cache synthtool googleapis artman genfiles python kms coveragerc manifest in noxfile py setup cfg traceback most recent call last file synth py line in s shell run hide output false file tmpfs src git autosynth env lib site packages synthtool shell py line in run encoding utf file home kbuilder pyenv versions lib subprocess py line in run with popen popenargs kwargs as process file home kbuilder pyenv versions lib subprocess py line in init restore signals start new session file home kbuilder pyenv versions lib subprocess py line in execute child raise child exception type errno num err msg filenotfounderror no such file or directory nox up temporary directories synthesis failed google internal developers can see the full log | 0 |
86,857 | 10,519,432,997 | IssuesEvent | 2019-09-29 17:57:42 | palavatv/palava | https://api.github.com/repos/palavatv/palava | closed | No man pages for palava-machine and palava-machine-daemon | documentation | <a href="https://github.com/ajaissle"><img src="https://avatars.githubusercontent.com/u/2892835?v=3" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [ajaissle](https://github.com/ajaissle)**
_Thursday Jan 16, 2014 at 13:27 GMT_
_Originally opened as https://github.com/palavatv/palava-machine/issues/3_
---
Hi,
please provide man pages for the following executables:
palava-machine
palava-machine-daemon
Each executable in standard binary directories should have a man page.
| 1.0 | No man pages for palava-machine and palava-machine-daemon - <a href="https://github.com/ajaissle"><img src="https://avatars.githubusercontent.com/u/2892835?v=3" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [ajaissle](https://github.com/ajaissle)**
_Thursday Jan 16, 2014 at 13:27 GMT_
_Originally opened as https://github.com/palavatv/palava-machine/issues/3_
---
Hi,
please provide man pages for the following executables:
palava-machine
palava-machine-daemon
Each executable in standard binary directories should have a man page.
| non_comp | no man pages for palava machine and palava machine daemon issue by thursday jan at gmt originally opened as hi please provide man pages for the following executables palava machine palava machine daemon each executable in standard binary directories should have a man page | 0 |
11,559 | 3,007,456,886 | IssuesEvent | 2015-07-27 16:09:00 | javaslang/javaslang | https://api.github.com/repos/javaslang/javaslang | closed | Harmonize static factory methods of collections | design/refactoring | Now that [Seq will also have static factory methods](https://github.com/javaslang/javaslang/issues/341#issuecomment-125161860), including `Seq.empty()`, which will return the empty `List`, the user will expect to find this method in all collections. List currently has `List.nil()`. I'm no friend of redundant methods, so we will add `List.empty()` and `List.nil()` will be removed.
Same for `Stream`. Queue already has `empty`. The existing `Stack.nil()` made no sense from the beginning... | 1.0 | Harmonize static factory methods of collections - Now that [Seq will also have static factory methods](https://github.com/javaslang/javaslang/issues/341#issuecomment-125161860), including `Seq.empty()`, which will return the empty `List`, the user will expect to find this method in all collections. List currently has `List.nil()`. I'm no friend of redundant methods, so we will add `List.empty()` and `List.nil()` will be removed.
Same for `Stream`. Queue already has `empty`. The existing `Stack.nil()` made no sense from the beginning... | non_comp | harmonize static factory methods of collections now that including seq empty which will return the empty list the user will expect to find this method in all collections list currently has list nil i m no friend of redundant methods so we will add list empty and list nil will be removed same for stream queue already has empty the existing stack nil made no sense from the beginning | 0 |
201,661 | 15,216,913,651 | IssuesEvent | 2021-02-17 16:01:36 | kbase/execution_engine2 | https://api.github.com/repos/kbase/execution_engine2 | opened | Remove travis.yml | testing | Doesn't seem like it's necessary to run both travis and gha integrations.
Discuss with Boris when he gets back | 1.0 | Remove travis.yml - Doesn't seem like it's necessary to run both travis and gha integrations.
Discuss with Boris when he gets back | non_comp | remove travis yml doesn t seem like it s necessary to run both travis and gha integrations discuss with boris when he gets back | 0 |
289,085 | 24,958,355,018 | IssuesEvent | 2022-11-01 13:42:39 | usethesource/rascal | https://api.github.com/repos/usethesource/rascal | closed | [RELEASE] version 0.18.2 (and intermediate 0.18.1 release) | release testing | # Preliminaries
* Every time this document says "release X" ; we mean to execute the instructions of this Wiki page: https://github.com/usethesource/rascal/wiki/How-to-make-a-release-of-a-Rascal-implemenation-project
* The current release instructions are focused on the Rascal commandline tools and the Eclipse IDE plugin
* If you edit this template, then please push relevant improvements to the template itself for future reference.
# Pre-releasing dependent tools in unstable
First a "pre-release" of the supporting compiler/typechecker tools must be done, so we know we are releasing a consistently compiled standard library.
- [x] typepal and rascal-core compile in the continuous integration environment and no tests fail
- [x] release typepal
- [x] make intermediate rascal release for rascal-core to depend on
- [x] release rascal-core
- [x] bump typepal and rascal-core versions in rascal-maven-plugin to latest releases
- [x] bump typepal and rascal-core versions in rascal-eclipse to latests SNAPSHOT releases
- [x] release rascal-maven-plugin
- [x] bump rascal-maven-plugin dependency in rascal and rascal-eclipse project
- [x] fix new errors and warnings in rascal and rascal-eclipse project
# Manual version checks
- [x] Continuous Integration runs all unit and integration tests and fails no test
- [x] Maximum number of compiler warnings are resolved
- [x] Version numbers are verified manually
# Manual feature tests
- [x] Eclipse download and install latest unstable release from update site https://update.rascal-mpl.org/unstable
- [x] Open a Rascal REPL using the toolbar button
- [x] Can create new Rascal project using the wizard
- [x] Can create new Rascal module using the wizard
- [x] Can edit Rascal file in Rascal project
- [x] Save on Rascal file triggers type-checker
- [x] Rascal outline works
- [x] Rascal navigator works
- [x] Rascal navigator displays working sets
- [x] Rascal navigator displays interpreter's search path
- [x] Clicking links in REPL opens editors and websites
- [x] `rascal>1 + 1` on the REPL
- [x] `import IO; println("Hello Rascal!");`
- [x] in editor, click on use of name jumps to definition
- [x] jump-to-definition also works to library modules and inside library modules
- [x] clicking in outline jumps to editor to right position
- [x] syntax highlighting in editor works
- [x] add dependency on another project by editing `RASCAL.MF`: `Required-Libraries: |lib://otherProject|`, import a module and test the type-checker as well as the interpreter for correct resolution
- [x] `import demo::lang::Pico::Plugin; registerPico();` and test the editor of the example pico files (syntax highlighting, menu options)
- [x] open tutor view and test the search box
- [x] open tutor view and test browsing the documentation
- [x] `import demo::lang::Pico::Plugin; rascal>:edit demo::lang::Pico::Plugin` (not possible yet, see #1418)
- [ ] edit a .concept file, save it and watch the preview in the Tutor Preview view
- [ ] Tutor Preview "edit" button opens the corresponding concept file of the currently visited Concept URL
- [ ] Tutor Preview Forward/Back/Refresh buttons work
# Actual release
- [x] release rascal project (when resolving SNAPSHOT dependencies choose the right versions of vallang etc, and make sure to bump the new rascal SNAPSHOT release one minor version)
- [x] release rascal-eclipse project (take care to choose the right release versions of typepal and rascal-core you release earlier and choose their new SNAPSHOT dependencies to the latest)
- [x] change the configuration of the stable version in `update-site-nexus-link-script/refresh-nexus-data` to the released version
- [x] test the stable update site at https://update.rascal-mpl.org/stable
- [ ] write release notes and publish on the usethesource.io blog
# Downstream implications
The following items can be executed asynchronously, but are nevertheless not to be forgotten:
- [ ] change dependencies on rascal-eclipse and rascal in rascal-eclipse-libraries and the projects it depends on
- [ ] change dependencies of typepal to latest rascal and rascal-eclipse
- [ ] change dependency of rascal-core to latest stable rascal
| 1.0 | [RELEASE] version 0.18.2 (and intermediate 0.18.1 release) - # Preliminaries
* Every time this document says "release X" ; we mean to execute the instructions of this Wiki page: https://github.com/usethesource/rascal/wiki/How-to-make-a-release-of-a-Rascal-implemenation-project
* The current release instructions are focused on the Rascal commandline tools and the Eclipse IDE plugin
* If you edit this template, then please push relevant improvements to the template itself for future reference.
# Pre-releasing dependent tools in unstable
First a "pre-release" of the supporting compiler/typechecker tools must be done, so we know we are releasing a consistently compiled standard library.
- [x] typepal and rascal-core compile in the continuous integration environment and no tests fail
- [x] release typepal
- [x] make intermediate rascal release for rascal-core to depend on
- [x] release rascal-core
- [x] bump typepal and rascal-core versions in rascal-maven-plugin to latest releases
- [x] bump typepal and rascal-core versions in rascal-eclipse to latests SNAPSHOT releases
- [x] release rascal-maven-plugin
- [x] bump rascal-maven-plugin dependency in rascal and rascal-eclipse project
- [x] fix new errors and warnings in rascal and rascal-eclipse project
# Manual version checks
- [x] Continuous Integration runs all unit and integration tests and fails no test
- [x] Maximum number of compiler warnings are resolved
- [x] Version numbers are verified manually
# Manual feature tests
- [x] Eclipse download and install latest unstable release from update site https://update.rascal-mpl.org/unstable
- [x] Open a Rascal REPL using the toolbar button
- [x] Can create new Rascal project using the wizard
- [x] Can create new Rascal module using the wizard
- [x] Can edit Rascal file in Rascal project
- [x] Save on Rascal file triggers type-checker
- [x] Rascal outline works
- [x] Rascal navigator works
- [x] Rascal navigator displays working sets
- [x] Rascal navigator displays interpreter's search path
- [x] Clicking links in REPL opens editors and websites
- [x] `rascal>1 + 1` on the REPL
- [x] `import IO; println("Hello Rascal!");`
- [x] in editor, click on use of name jumps to definition
- [x] jump-to-definition also works to library modules and inside library modules
- [x] clicking in outline jumps to editor to right position
- [x] syntax highlighting in editor works
- [x] add dependency on another project by editing `RASCAL.MF`: `Required-Libraries: |lib://otherProject|`, import a module and test the type-checker as well as the interpreter for correct resolution
- [x] `import demo::lang::Pico::Plugin; registerPico();` and test the editor of the example pico files (syntax highlighting, menu options)
- [x] open tutor view and test the search box
- [x] open tutor view and test browsing the documentation
- [x] `import demo::lang::Pico::Plugin; rascal>:edit demo::lang::Pico::Plugin` (not possible yet, see #1418)
- [ ] edit a .concept file, save it and watch the preview in the Tutor Preview view
- [ ] Tutor Preview "edit" button opens the corresponding concept file of the currently visited Concept URL
- [ ] Tutor Preview Forward/Back/Refresh buttons work
# Actual release
- [x] release rascal project (when resolving SNAPSHOT dependencies choose the right versions of vallang etc, and make sure to bump the new rascal SNAPSHOT release one minor version)
- [x] release rascal-eclipse project (take care to choose the right release versions of typepal and rascal-core you release earlier and choose their new SNAPSHOT dependencies to the latest)
- [x] change the configuration of the stable version in `update-site-nexus-link-script/refresh-nexus-data` to the released version
- [x] test the stable update site at https://update.rascal-mpl.org/stable
- [ ] write release notes and publish on the usethesource.io blog
# Downstream implications
The following items can be executed asynchronously, but are nevertheless not to be forgotten:
- [ ] change dependencies on rascal-eclipse and rascal in rascal-eclipse-libraries and the projects it depends on
- [ ] change dependencies of typepal to latest rascal and rascal-eclipse
- [ ] change dependency of rascal-core to latest stable rascal
| non_comp | version and intermediate release preliminaries every time this document says release x we mean to execute the instructions of this wiki page the current release instructions are focused on the rascal commandline tools and the eclipse ide plugin if you edit this template then please push relevant improvements to the template itself for future reference pre releasing dependent tools in unstable first a pre release of the supporting compiler typechecker tools must be done so we know we are releasing a consistently compiled standard library typepal and rascal core compile in the continuous integration environment and no tests fail release typepal make intermediate rascal release for rascal core to depend on release rascal core bump typepal and rascal core versions in rascal maven plugin to latest releases bump typepal and rascal core versions in rascal eclipse to latests snapshot releases release rascal maven plugin bump rascal maven plugin dependency in rascal and rascal eclipse project fix new errors and warnings in rascal and rascal eclipse project manual version checks continuous integration runs all unit and integration tests and fails no test maximum number of compiler warnings are resolved version numbers are verified manually manual feature tests eclipse download and install latest unstable release from update site open a rascal repl using the toolbar button can create new rascal project using the wizard can create new rascal module using the wizard can edit rascal file in rascal project save on rascal file triggers type checker rascal outline works rascal navigator works rascal navigator displays working sets rascal navigator displays interpreter s search path clicking links in repl opens editors and websites rascal on the repl import io println hello rascal in editor click on use of name jumps to definition jump to definition also works to library modules and inside library modules clicking in outline jumps to editor to right position syntax highlighting in editor works add dependency on another project by editing rascal mf required libraries lib otherproject import a module and test the type checker as well as the interpreter for correct resolution import demo lang pico plugin registerpico and test the editor of the example pico files syntax highlighting menu options open tutor view and test the search box open tutor view and test browsing the documentation import demo lang pico plugin rascal edit demo lang pico plugin not possible yet see edit a concept file save it and watch the preview in the tutor preview view tutor preview edit button opens the corresponding concept file of the currently visited concept url tutor preview forward back refresh buttons work actual release release rascal project when resolving snapshot dependencies choose the right versions of vallang etc and make sure to bump the new rascal snapshot release one minor version release rascal eclipse project take care to choose the right release versions of typepal and rascal core you release earlier and choose their new snapshot dependencies to the latest change the configuration of the stable version in update site nexus link script refresh nexus data to the released version test the stable update site at write release notes and publish on the usethesource io blog downstream implications the following items can be executed asynchronously but are nevertheless not to be forgotten change dependencies on rascal eclipse and rascal in rascal eclipse libraries and the projects it depends on change dependencies of typepal to latest rascal and rascal eclipse change dependency of rascal core to latest stable rascal | 0 |
End of preview. Expand
in Data Studio
- Downloads last month
- 20
Size of downloaded dataset files:
70.8 MB
Size of the auto-converted Parquet files:
70.8 MB
Number of rows:
35,042